libsdl 1.2.14 checksum failed

[senz@…]

--->  Attempting to fetch SDL-1.2.14.tar.gz from http://www.libsdl.org/tmp/
--->  Verifying checksum(s) for libsdl
Error: Checksum (md5) mismatch for SDL-1.2.14.tar.gz
Error: Checksum (sha1) mismatch for SDL-1.2.14.tar.gz
Error: Checksum (rmd160) mismatch for SDL-1.2.14.tar.gz
Error: Target org.macports.checksum returned: Unable to verify file checksums

[jan.hosang@…]

I can confirm this issue. More details:

--->  Checksumming SDL-1.2.14.tar.gz
Error: Checksum (md5) mismatch for SDL-1.2.14.tar.gz
Portfile checksum: SDL-1.2.14.tar.gz md5 6726575f6c6a799e24210e22ee751052
Distfile checksum: SDL-1.2.14.tar.gz md5 b916b29ece2c4f3618e51318003e4cc3
Error: Checksum (sha1) mismatch for SDL-1.2.14.tar.gz
Portfile checksum: SDL-1.2.14.tar.gz sha1 db9a714fe9c00163e2708111a64f065861e95464
Distfile checksum: SDL-1.2.14.tar.gz sha1 c15e75aafc6394f296050c8f87f87ef65c04ff2b
Error: Checksum (rmd160) mismatch for SDL-1.2.14.tar.gz
Portfile checksum: SDL-1.2.14.tar.gz rmd160 f5e2b01c48ce1087e97d8074674989437dc3a26c
Distfile checksum: SDL-1.2.14.tar.gz rmd160 402abd5842b43357d04bf74c0fa0e23daa772dca
The correct checksum line may be:
checksums           md5     b916b29ece2c4f3618e51318003e4cc3 \
                    sha1    c15e75aafc6394f296050c8f87f87ef65c04ff2b \
                    rmd160  402abd5842b43357d04bf74c0fa0e23daa772dca
Error: Target org.macports.checksum returned: Unable to verify file checksums

[jan.hosang@…]

Cc Me!

[gale@…]

Cc Me!

[ryandesign@…]

Toby, in r58082 you updated the port to 1.2.14 but also changed the download location from /release to /tmp. The homepage still mentions 1.2.13 as the latest version available. Are we sure 1.2.14 is ready to be used? Perhaps you can compare the currently-available SDL-1.2.14.tar.gz with the one you received yesterday and see what's different.

[toby@…]

I've since reformatted the machine I installed it on. Just commit a fix for it

[ryandesign@…]

Fixed in r58114. Let me know if it happens again.

[software@…]

The checksums have changed again. However, since I can not reopen the bug, I submitted a new one: #21569

[ryandesign@…]

Replying to ryandesign@…:

The homepage still mentions 1.2.13 as the latest version available. Are we sure 1.2.14 is ready to be used?

The answer seems to be no. Fixed the latest checksum mismatch in r58178 by downgrading to 1.2.13. This reopens #20235.

[toby@…]

Reverted r58178 in r58179. A completely broken libsdl does not do any good - upgrading daily is an inconvenience, but working is better than not working.

[js-macports@…]

It's happening again:

Error: Checksum (md5) mismatch for SDL-1.2.14.tar.gz
Portfile checksum: SDL-1.2.14.tar.gz md5 18895c7865c971e7e6c00bdd97e697ca
Distfile checksum: SDL-1.2.14.tar.gz md5 1c4203d2dffbde5a333fa6e9620e38b8
Error: Checksum (sha1) mismatch for SDL-1.2.14.tar.gz
Portfile checksum: SDL-1.2.14.tar.gz sha1 cb2239860b41821150f4208435aee08987bec0cd
Distfile checksum: SDL-1.2.14.tar.gz sha1 8e083e9dcaff346f5bec143fc5f1808488dc99f5
Error: Checksum (rmd160) mismatch for SDL-1.2.14.tar.gz
Portfile checksum: SDL-1.2.14.tar.gz rmd160 e4faaf504b2c05d9ce6aec79ed55ab1ef7cb8e95
Distfile checksum: SDL-1.2.14.tar.gz rmd160 2e3bca08655a27c542445aa9275b08da7f9ce306
The correct checksum line may be:
checksums           md5     1c4203d2dffbde5a333fa6e9620e38b8 \
                    sha1    8e083e9dcaff346f5bec143fc5f1808488dc99f5 \
                    rmd160  2e3bca08655a27c542445aa9275b08da7f9ce306

Is it safe to just update the checksums? Wouldn't it make more sense to just backport the fix from .14 to .13?

[blb@…]

Cc reporter of dup #21655.

[blb@…]

Updated in r58357.

[mas@…]

Cc Me!

[domiman@…]

can the SDL SVN be bumped again? I tried to compile the SVN of SDL 1.2 myself but didn't succeed. Not urgent but it would be nice if it could be bumped every couple of days, since we ARE using the SVN version...

[domiman@…]

Cc Me!

[toby@…]

We're not using the svn version, and if the port doesn't build that's a separate issue - it apparently builds fine for most people. Please don't comment in closed tickets, it's basically just extra noise.

[domiman@…]

Sorry for commenting in a closed ticket, it's just that this fits the issue more than a new ticket and it has been discussed here. And true, this is not the SVN but a snapshot of the SVN, so my request would be to use a more up to date snapshot. I have no problem with this port but with building either the newest snapshot of the SVN or the newest SVN, take your pick, both fail...

[toby@…]

Oh, the newer snapshots fail to build? All the more reason to stick with the current one.