I just tried to drush dl realname-7.x-1.x and I got the error "File realname-7.x-1.x-dev.tar.gz is corrupt (wrong md5 checksum). "
Sure enough, the MD5 hash listed on the release page is:
6cb69f17eb6c10361c5892bc3648c9f1
When I run md5sum realname-7.x-1.x-dev.tar.gz I get:
3f7ef0af08c03f50addd6facca0d2212
This is pretty major since it blocks drush and download verifications completely.
Comments
Comment #1
dave reidIn addition, on the dev release node, it says it was last generated 'November 9th', but I made a commit yesterday, Nov 18 at 16:52 CST, and I know the download contains the new commit so it was actually rebuilt.
Comment #2
dave reidI can also currently confirm the same problem with views 7.x-3.x-dev.
Comment #3
dave reidAlso confirmed from #975996: Drush dl views that this also is a problem for media_mover-6.x-1.x-dev, webform-6.x-3.x-dev, views_charts-6.x-1.x-dev
Comment #4
longwavePerhaps related to the issues at http://drupal.org/node/381704#comment-3728096 onwards, as uc_views-6.x-3.x-dev is also affected by this.
Comment #5
nnewton commentedThis is solved for now, but -dev releases will need to be regenerated for problem release nodes.
-N
Comment #6
longwaveThis is still occuring for uc_views-6.x-3.x - I made a commit yesterday in the hope that it would cause the release to be regenerated, but this hasn't happened; http://drupal.org/node/534290 was last updated on November 18, how do I trigger an update?
Comment #7
dave reidYep, still occurring for me as well even after I committed code to the following branch/dev release:
http://drupal.org/node/964794
- Still says "Last updated: November 9, 2010 - 06:19" when it was Nov 19th (from timestamps in the .tar.gz)
- Still says the file hash is 6cb69f17eb6c10361c5892bc3648c9f1
Comment #8
longwaveDave Reid's realname-7.x-1.x has apparently updated now, but uc_views-6.x-3.x still refuses to update for some reason, and the hash still does not match.
whereas f4c06b250e8052572949a40ff8f527e2 is the hash given on the release page.
Comment #9
hunmonk commentedthat branch shows a last commit date of 2010-Nov-18 . i suspect that a new commit to the branch will solve the problem on the next packaging run. please try that.
Comment #10
longwaveI did make a commit on November 22 which deleted a file from the branch, but I guess that doesn't trigger an update. Another commit seems to have solved the problem, thanks for responding.
Comment #11
dave reidThis is back again with the Views 7.x-3.x dev release, which has had lots of activity and the last view days (last generated Dec 7)
http://drupal.org/node/608852
Comment #12
gerhard killesreiter commentedSeems this is fixed now.
Comment #14
boabjohn commentedSorry to touch this one fellas, but I suspect there's something still amiss.
In an Ubuntu Hardy Heron environment with PHP=5.2.4-2ubuntu5.17 (64M limit) , I have a multisite installation provisioned through aegir...
I checked status with drush up and needed to run a half dozen up dates (ckeditor, ctools, panels, token, views, drupal core 7.4 > 7.7)
Giving Drush the go-ahead, I immediately got an MD5 error with ckeditor. I thought strange, but ckeditor can be like that, so I ran drush command: drush up ctools panels (etc) and bang, go the MD5 error again, on ctools.
Baffled, did a d.o search and found this (and other) threads.
Went back to the site and, over the course of between 1 and 4 attempts *per module* managed to get each one to update. Views was the last one...I just kept repeating the drush up views command and ignoring the MD5 error (see below) until it just updated like normal.
Apologies in advance if this is just all local messiness...but I've never had it happen before in ~2 years of happily using drush.
Comment #15
nnewton commentedCan you retest with views-7.x-3.x-dev. I cannot currently reproduce this. (or point to another release with this issue)
-N
Comment #16
pauljr8 commentedRunning drush pm-update hangs on "File views-7.x-3.x-dev.tar.gz is corrupt (wrong md5 checksum)."
Installed version: Views 7.x-3.x-dev (2011-Sep-19)
Available version: 7.x-3.x-dev (2011-Sep-26)
Comment #17
dasrecht commentedClosing old issues. Please re-open if needed.