checksum (sha1) mismatch for postgis-1.3.3.tar.gz

[aaabbbdddde@…]

I installed a postgresql83-server some time ago and need postgis support now. While Installing postgis (port install postgis) the following error occured after autodownloading the tar.gz file from:

Error: Checksum (sha1) missmatch for postgis-1.3.3.tar.gz

after cleaning postgis I tried to download it from a mirror with the command "port mirror postgis" but the result was the same

I installed the whole thing some weeks ago without any problems. Now I am stuck at this point. Seems like the version from postgis.refractions.net/download is corrupted or the checksum from org.macports.checksum is wrong ....

[jmr@…]

Assigning to maintainer.

[jan@…]

Some additional info: The checksum of the current version would be 96342effdf6fd79e8deb148916cd3f97724ddd4d (replacing the checksum in the portfile with this number makes it install for me, but a little more fact-checking might be advisable).

I skimmed (albeit superficially) through the postgis-devel mailing list (to be found at ​http://postgis.refractions.net/pipermail/postgis-devel/ ), but did find no notice of any unplanned-in-release update and the date stated on the download page (​http://postgis.refractions.net/download/ ) is the same as the original announcement date (12th of April), so no clues here either.

Best strategy would be (IMHO) to ask on the mailinglist (assuming that the package maintainer is on that list anyway, I'll leave that to her/him), or, second best, to assume that the postgis servers are safe and simply change the checksum. I'll upload a patch that does that. :)

[jan@…]

Patch to change the checksum to the current 1.3.3 checksum (see comment)

[jmr@…]

The file on distfiles.macports.org has the checksum in the portfile, so you can use the workaround described in ProblemHotlist.

[blb@…]

A quick look into the original and new tarballs suggests the new one (at over twice the size) has gained weight through .svn directories...

[sasha.aickin@…]

It looks like the new tarball doesn't just have .svn directories but also has .o files next to the .c files, which made it impossible to install on my new MacPro, even after I changed the SHA checksum locally. If you do

sudo port -v install postgis

you'll see that the make command has several complaints from ld about the .o files being for the wrong architecture.

I filed this issue against the postgis folks at ​http://code.google.com/p/postgis/issues/detail?id=60 .

I was able to build on my local machine by adding the following to the portfile:

build.target clean all

after the build.args line.

[jmr@…]

I've set our distfiles mirror as the first entry in postgis's master_sites in r40782, which should hopefully take care of this until they fix the tarball.

[blb@…]

FYI, looks like they've cut a new 1.3.3 tarball, this time without the object files and .svn stuff, but it appears configure has been run on the new one, so it doesn't match the original 1.3.3...but still much smaller in size than the one with object files and subversion.

[ryandesign@…]

Replying to jmr@…:

I've set our distfiles mirror as the first entry in postgis's master_sites in r40782, which should hopefully take care of this until they fix the tarball.

MacPorts 1.7.0 and later try master_sites in order of ping time, not in the order listed in the Portfile, so this workaround is no longer effective. The port needs to be updated for this upstream distfile change.

[anonymous]

Milestone Port Bugs deleted

[blb@…]

Cc reporter of dup #19993.

[raimue@…]

Superseded by #20827.