Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
See the title... Drupal D6 hasn't been re-packaged for 2 days and tons of other modules / translations with updates, too.
What's wrong?
Comments
Comment #1
dwwFrom my email to the infrastruture list in reply to the same question a few days ago...
Comment #2
hass CreditAttribution: hass commentedTonight packaging has rebuild the dev's, but my tagged release is staying in queue.
Aside - i haven't seen yet that the packaging is building 5 minutes after a commit or release!? Last week it took nearly 12-24 hours to get something packaged.
Is there any way to remove a already tagged release (robotstxt-5.x-1.0) staying in queue - if this hasn't been build and isn't official - to add some additional patches and release later as 1.0 or am i made to name this now 1.1? Or better to ask - is code that has been tagged - untagable until the release is build?
Comment #3
GoofyX CreditAttribution: GoofyX commentedThis is a serious issue. Shouldn't there be a statement warning all developers of contrib modules/translations/themes, etc. until the problem is fixed? It will surely avoid the creation of issues...
Comment #4
mcurry CreditAttribution: mcurry commented** subscribe **
Comment #5
msameer CreditAttribution: msameer commentedsubscribe. sorry for the spam!
Comment #6
GoofyX CreditAttribution: GoofyX commentedAny status update for this issue?
Thanks.
Comment #7
dwwWhen the OSUOSL gets the cron jobs working again, either one of them or myself will mark this issue fixed.
I even tried running the scripts manually last night, but the special user that these cron jobs runs as no longer exists on the servers. This is completely out of my hands...
-Derek
Comment #8
drewish CreditAttribution: drewish commentedsubscribing.
Comment #9
JohnAlbinThanks for the update, Derek! I look forward to the fix. It’s frustrating seeing the -dev releases updated, but not the official releases.
Comment #10
tonyn CreditAttribution: tonyn commentedthis one has been eating at me for a bit. it was kind of confusing, because the day I first got cvs was the same time we had the drupal.org infrastructure upgrades. i don't mind the minor inconvenience, as having a speedier site in the end game will be well worth it.
Comment #11
JohnAlbinThe official releases that were sitting in the queue have been processed. I also did a new official release and it was packaged in less than a minute.
I hope that means everything is fixed!
Comment #12
JohnAlbinHmm… I take it back. The official release I just created ( http://drupal.org/node/165049 ) shows up on the project page but the downloadable file is missing, even though it was “packaged” 2 hours ago.
Comment #13
GoofyX CreditAttribution: GoofyX commentedNo, it's fine for me here. I suppose it's fixed now...(?)
Comment #14
JohnAlbinNevermind. I hate browser caches. :-(
Comment #15
dwwRight. After a few more private email exchanges with OSUOSL, things seemed to be mostly working again. However, I didn't want to declare victory just yet since there are a few minor issues lingering. However, by and large, the packaging scripts seem to be working fine again.
Also, keep in mind that there's a 5 minute race condition right after the tarball is generated before it's available on ftp.drupal.org. See this issue for why: http://drupal.org/node/106399 -- again, I'd like to fix it, but it's out of my hands.
Comment #16
dwwThe lingering, minor issues aren't worth keeping this open over... "Victory". ;)
Comment #17
(not verified) CreditAttribution: commented