Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem has been stated in the subject. Wanted to test something and downloaded http://ftp.drupal.org/files/projects/drupal-5.x-dev.tar.gz several times - the version missing several files in main directory, including such and important file as index.php. Sitting since morning and waiting for the file to be updated, but eventually had to create this thread. Please upload missing files.
Comments
Comment #1
vm commentedMay happen at the next rolling of tar's which on my time is 8pm EST.
Comment #2
vm commentedchanged component as the installation system is not really what the problem is here with the 5.x-dev version rolled this morning.
Comment #3
webernet commentedComment #4
yngens commentedVeryMisunderstood, unfortunately it did not happen at 8pm EST. It is 9.45 pm PST at my place now. Still missing files in dev.tar.gz file :(
Comment #5
yngens commentedwebernet, I am not sure, but I don't think this problem is about Drupal.org infrastructure. So changed back to Drupal project. And still waiting that the missing files will be uploaded. Does anyone know how to get previous (of yesterday) dev.tar.gz, since today's one is corrupted?
Comment #6
merlinofchaos commentedIt's missing a lot more than just index.php.
This file is automatically generated. Something must be messed up with the packager, perhaps the cvs update isn't running right for this project.
Why did you change the project back? webernet moved it to the right place.
Comment #7
dwwVery strange. There was no evidence of a failure (though I'll admit that the packaging script doesn't propagate errors very well). I just re-generated the file and it looks fine now.
If I had more time, I'd try to investigate what caused the partial package to get created in the first place, but alas, my day job calls.
Comment #8
emsearcy commenteddww: the problem may have been caused by the fact that cvs was acting sporadically between 22:39 and 23:28 UTC. Those problems were dealt with, and the cron job shouldn't have ran until 24:00, so it should have worked, but I expect it was related to this somehow.
I'm guessing the one that ran earlier at 12:00 UTC ran okay, and if the next one up in :40 more minutes completes, I'd say it was a one-time problem.
Comment #9
yngens commentedthank you dww very much. i was waiting for the missing files to test some new modules.
Comment #10
(not verified) commented