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

dww’s picture

Title: Packaging not running since 2 days?! » Packaging not running since 2 days?

From my email to the infrastruture list in reply to the same question a few days ago...

On Aug 3, 2007, at 3:04 PM, Jeremy Andrews wrote:

Have the packaging scripts that used to run every 5 minutes for contrib projects been disabled?

Yes, but for no good reason.

They were disabled on wednesday when the site moved to PHP5 and there was an evil PHP5 bug that caused much trouble. I fixed that, so they should have been enabled again.

However, at the same time, the OSUOSL wanted to move them from one of the web nodes to the other, and generally tweak the cron configuration that triggers them. Unfortunately, this move doesn't seem to have been completed, and the cron jobs still aren't running...

Killes and I are working with the OSUOSL folks to try to resolve this.

-Derek (dww)

hass’s picture

Tonight 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?

GoofyX’s picture

This 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...

mcurry’s picture

** subscribe **

msameer’s picture

subscribe. sorry for the spam!

GoofyX’s picture

Any status update for this issue?

Thanks.

dww’s picture

When 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

drewish’s picture

subscribing.

JohnAlbin’s picture

Thanks for the update, Derek! I look forward to the fix. It’s frustrating seeing the -dev releases updated, but not the official releases.

tonyn’s picture

this 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.

JohnAlbin’s picture

The 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!

JohnAlbin’s picture

Hmm… 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.

GoofyX’s picture

No, it's fine for me here. I suppose it's fixed now...(?)

JohnAlbin’s picture

Nevermind. I hate browser caches. :-(

dww’s picture

Right. 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.

dww’s picture

Status: Active » Fixed

The lingering, minor issues aren't worth keeping this open over... "Victory". ;)

Anonymous’s picture

Status: Fixed » Closed (fixed)