drupal-composer / drupal-packagist

:package: Drupal Packagist server to automatically build package information from projects on drupal.org
http://packagist.drupal-composer.org
28 stars 4 forks source link

Project with dev-release was not created #6

Closed webflo closed 8 years ago

webflo commented 9 years ago

From @derhasi on January 13, 2015 8:7

My project https://www.drupal.org/project/drutils is not available as drupal/drutils.

What is the procedure to create those projects that have no release yet and did not get any attention via commitlog?

Copied from original issue: webflo/packagist#9

webflo commented 9 years ago

Looks like commit log parsing is broken atm.

webflo commented 9 years ago

From @derhasi on January 13, 2015 11:15

As the last code change was from September, I do not think packagist could have recognized it via the commitlog. As there is no release, releases.tsv is not a source either. So I'm wondering where packagist could have got the information from to get to know that dev release. Maybe you can point me to the relevant code, so I can look for the problem on my own.

webflo commented 9 years ago

From @derhasi on January 14, 2015 16:25

Now I even got the case, that a dev release that existsed is not present anymore: see http://drupal-packagist.webflo.io/packages/drupal/master . Two days ago 7.3.x-dev was available, which is not the case anymore.

  • The requested package drupal/master 7.3.x-dev could not be found.
webflo commented 9 years ago

From @derhasi on January 20, 2015 15:23

I just recognized that anonymous users in the commitlog get different results than logged in users, see screenshot:

Logged in vs logged out

I recognized the problem while looking after the my latest commit I pushed in my master 3.x-dev dev branch. There is still not such a branch in the packagist.