Since yesterday, I'm getting this error in using drush make: "File drupal-7.22.tar.gz is corrupt (wrong md5 checksum)"

Drush version is 5.7. I also got a similar error with comment notify awhile back that my co-worker posted to their issue queue and got it for days, so we just commented that out of the profile for now.

Any ideas?

Files: 
CommentFileSizeAuthor
#21 xml.diff1.49 KBmoshe weitzman

Comments

I just wanted to follow up and say I'm still getting this error, but running drush make with the option '--no-cache' solved it temporarily. So, I guess this is an issue with drush make storing incorrect info during a window of time when a new release is put out there? I want to leave the ticket open as it seems to me the fact that drush make references an incorrect checksum in the first place could still be a problem.

This happened to me this morning as well.

>> File file_entity-7.x-2.x-dev.tar.gz?date=1374367521 is corrupt [error]
(wrong md5 checksum)

'--no-cache' solved the issue.
However, after running drush make with no cache option, and run it the second time without no cache option, the issue came back.

We're experiencing this issue with an invalid checksum on the OG module as part of packaging the Commons distribution: #2047677: Unable to package Commons: invalid checksum on OG..

Experiencing this same issue with running a local drush makefile. Cleared out ~/.drush/cache and ran with --no-cache. Problem persists.

Error below.

File file_entity-7.x-2.x-dev.tar.gz?date=1374454907 is corrupt (wrong md5 checksum).

file_entity has a dev release from today. I'm guessing this is likely a caching issue or a failure to rebuild/reset the XML at the correct time.

EDIT: As of Wed Jul 24 18:04:39 UTC 2013 XML at http://updates.drupal.org/release-history/file_entity/7.x indicates md5sum should be fbf654f4c6324e076586991cb36b9312 for http://ftp.drupal.org/files/projects/file_entity-7.x-2.x-dev.tar.gz, actual md5sum is bdd6d0fbfada75154fcf0ccad05e1456

Using --ignore-checksums and --force-complete flags are non-functional, checksums still checked build still fails. These details are likely drush issues, the bad checksum is d.o infrastructure.

We're experiencing this with the Commons nightly dev snapshot, this time with:

ERROR: >> File commons_origins-7.x-3.x-dev.tar.gz?date=1375229187 is corrupt (wrong md5 checksum).

I'm experiencing the following this morning.

File l10n_update-7.x-1.x-dev.tar.gz_date=1361970686 is corrupt (wrong    [error]
md5 checksum).
File hierarchical_select-7.x-3.x-dev.tar.gz_date=1339849269 is           [error]
corrupt (wrong md5 checksum).
BUILD FAILED
Drush exited with code 1

It seems to be affecting most frequently with the dev modules.
I've used --no-cache option, but the error still occurs.

I too was getting this error with any module I specified to use the -dev branch:

File ckeditor-7.x-1.x-dev.tar.gz_date=1366763925 is corrupt (wrong   [error]
md5 checksum).

Building with the --no-cache option did fix the issue for me.

Priority:Normal» Major

I'm seeing it too with the dev snapshot of Drupal 8.x. When I download that tarball and run md5_file() on it, I get checksum of 97545a881b63c7c16c48db35b79883a0. The Update XML right now has different checksum. See the last [release] element:

<?xml version="1.0" encoding="utf-8"?>
<project xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>Drupal core</title>
<short_name>drupal</short_name>
<dc:creator>Drupal</dc:creator>
<api_version>8.x</api_version>
<project_status>unsupported</project_status>
<link>http://drupal.org/project/drupal</link>
  <terms>
   <term><name>Projects</name><value>Drupal core</value></term>
   <term><name>Development status</name><value>Under active development</value></term>
   <term><name>Maintenance status</name><value>Actively maintained</value></term>
  </terms>
<releases>
<release>
  <name>drupal 8.0-alpha3</name>
  <version>8.0-alpha3</version>
  <tag>8.0-alpha3</tag>
  <version_major>8</version_major>
  <version_patch>0</version_patch>
  <version_extra>alpha3</version_extra>
  <status>published</status>
  <release_link>http://drupal.org/node/2081595</release_link>
  <download_link>http://ftp.drupal.org/files/projects/drupal-8.0-alpha3.tar.gz</download_link>
  <date>1378303307</date>
  <mdhash>c786a027b87428fef5ddd7a946dcf07c</mdhash>
  <filesize>7647641</filesize>
  <files>
   <file>
    <url>http://ftp.drupal.org/files/projects/drupal-8.0-alpha3.tar.gz</url>
    <archive_type>tar.gz</archive_type>
    <md5>c786a027b87428fef5ddd7a946dcf07c</md5>
    <size>7647641</size>
    <filedate>1378303307</filedate>
   </file>
   <file>
    <url>http://ftp.drupal.org/files/projects/drupal-8.0-alpha3.zip</url>
    <archive_type>zip</archive_type>
    <md5>2ac8bc2b9f28c2602257ad6a5d817351</md5>
    <size>12987824</size>
    <filedate>1378303309</filedate>
   </file>
  </files>
  <terms>
   <term><name>Release type</name><value>New features</value></term>
   <term><name>Release type</name><value>Bug fixes</value></term>
  </terms>
</release>
<release>
  <name>drupal 8.0-alpha2</name>
  <version>8.0-alpha2</version>
  <tag>8.0-alpha2</tag>
  <version_major>8</version_major>
  <version_patch>0</version_patch>
  <version_extra>alpha2</version_extra>
  <status>published</status>
  <release_link>http://drupal.org/node/2026719</release_link>
  <download_link>http://ftp.drupal.org/files/projects/drupal-8.0-alpha2.tar.gz</download_link>
  <date>1372069563</date>
  <mdhash>01f5589dcfd851c7d65c040f455bad19</mdhash>
  <filesize>7319631</filesize>
  <files>
   <file>
    <url>http://ftp.drupal.org/files/projects/drupal-8.0-alpha2.tar.gz</url>
    <archive_type>tar.gz</archive_type>
    <md5>01f5589dcfd851c7d65c040f455bad19</md5>
    <size>7319631</size>
    <filedate>1372069563</filedate>
   </file>
   <file>
    <url>http://ftp.drupal.org/files/projects/drupal-8.0-alpha2.zip</url>
    <archive_type>zip</archive_type>
    <md5>54ad7978910d4aab1f3f44367b0b68f5</md5>
    <size>12323909</size>
    <filedate>1372069564</filedate>
   </file>
  </files>
</release>
<release>
  <name>Drupal 8.x-dev</name>
  <version>8.x-dev</version>
  <tag>8.x</tag>
  <version_major>8</version_major>
  <version_extra>dev</version_extra>
  <status>published</status>
  <release_link>http://drupal.org/node/572834</release_link>
  <download_link>http://ftp.drupal.org/files/projects/drupal-8.x-dev.tar.gz</download_link>
  <date>1379768130</date>
  <mdhash>9e260d27c7e82299fec01c432314e4bb</mdhash>
  <filesize>7696363</filesize>
  <files>
   <file>
    <url>http://ftp.drupal.org/files/projects/drupal-8.x-dev.tar.gz</url>
    <archive_type>tar.gz</archive_type>
    <md5>9e260d27c7e82299fec01c432314e4bb</md5>
    <size>7696363</size>
    <filedate>1379768130</filedate>
   </file>
   <file>
    <url>http://ftp.drupal.org/files/projects/drupal-8.x-dev.zip</url>
    <archive_type>zip</archive_type>
    <md5>7b1a60ba9312b18ad08aa30aa4e443af</md5>
    <size>13055083</size>
    <filedate>1379768133</filedate>
   </file>
  </files>
</release>
</releases>
</project>

I think the problem is that Moshe looked at the XML when Drupal-dev had already been recreated but the packaging job was still running and the XML wasn't rebuilt yet. The timestamp of his comment would support this. (roughly)

This is a problem, especially since the job regularly runs over 2 hours and sometimes it gets stuck and is killed after 4 with the XML in an undefined state.

However, it only affects dev releases.

If somebody wants to resolve this, function package_releases is your friend. It would probably suffice to move the XML rebuilding of packaged projects up a bit and not do a whole-sale XML rebuilding at the end. This would minimize the time gap.

I am seeing same behavior right now. Is packaging running?

Where is package_releases(). I'm looking in project but don't see it in 7.x-2.x

package-release-nodes.php

has the function.

http://ftp.drupal.org/files/projects/versioncontrol_project-6.x-2.x-dev....

and yes, packaging is running..

I notice that this code has been ported to Drush in D7 as per #1800186: Update package-release-nodes.php to D7 in Drush. Yet I still see package-release-nodes.php in D7 so I'm confused about where to start for fixing this. Fix in D7 first? If so, what function?

Facing the same problem with bootstrap theme and cer project

Same here with job-scheduler module.

please provide detailed info on how to reproduce the problem. The XML files are update regularly.

They are all updated every 6 hours, so there is plenty of opportunity for them to get stale. Updating the release XML per-project as a queued operation.

Would be great if someone could answer my question in #14. Thanks.

The drush command, http://drupalcode.org/project/project.git/blob/refs/heads/7.x-2.x:/relea..., is the place to fix this.

Where do you see package-release-nodes.php now?

Issue summary:View changes
Status:Active» Needs review
StatusFileSize
new1.49 KB

Attached patch changes the meaning of release-package-run so that it both creates package files AND writes update XML. It does both jobs before moving on to the next project. I don't know how these commands are scheduled on drupal.org, so this might not be the optimal fix.

I also removed some redundant help.

Project:Drupal.org infrastructure» Project
Version:» 7.x-2.x-dev
Component:Packaging» Releases
Status:Needs review» Needs work

Committed http://drupalcode.org/project/project.git/commit/2b588e2 and deploying.

As a follow-up, we need to make the if (is_null($project_id)) code path optional, and not do it unless you specified --all on the command line. We no longer need or want to regenerate all history every 6 hours.

For anyone listening here, there are also upgrade related problems with dev snapshots. While the bug here is fixed, we won't see the benefit until we make progress at #2132659: [META] Problems with Project Release Packaging

I'm having this issue too, all of a sudden. A previously working makefile is now not downloading any of the dev releases anymore.
The issue mentioned in #23 is marked as fixed, what is the guidance on this issue now? I'm running Aegir and with this issue in place the platform creation workflow, which is a very important part, is basically broken.

@AlfTheCat: This could also just be your Drush cache getting corrupt. Try deleting the specific cached files (or even the whole cache) from ~/.drush/cache/download (where ~ is probably /var/aegir for Aegir).

Installing drush via git (master branch/HEAD), on a fresh new server, and running drush dl drupal-8.x, gives me this error:

File drupal-8.x-dev.tar.gz_date=1390624108 is corrupt (wrong md5 checksum)

This same command did work on Monday, but hasn't been working tonight, and I'm guessing it's because the XML is out of sync with the actual release tarballs, correct? Using the --no-cache option did work. Weird.