axel @2.13.1: Checksum error

[rickyzhang82 (Ricky Zhang)]

I did update in Tiger 10.4 PPC. I encountered the following error:

--->  Computing dependencies for axel
--->  Fetching archive for axel
--->  Attempting to fetch axel-2.13.1_0.darwin_8.ppc.tbz2 from http://packages.macports.org/axel
--->  Attempting to fetch axel-2.13.1_0.darwin_8.ppc.tbz2 from http://sea.us.packages.macports.org/macports/packages/axel
--->  Attempting to fetch axel-2.13.1_0.darwin_8.ppc.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/axel
--->  Fetching distfiles for axel
--->  Attempting to fetch axel-2.13.1.tar.gz from https://github.com/eribertomota/axel/tarball/2.13.1
--->  Verifying checksums for axel
Error: Checksum (rmd160) mismatch for axel-2.13.1.tar.gz
Error: Checksum (sha256) mismatch for axel-2.13.1.tar.gz
Error: Failed to checksum axel: Unable to verify file checksums

[rickyzhang82 (Ricky Zhang)]

I believe the culprit is openssl package. But I haven't figured it out how to fix it.

[Updated] I was wrong. The true culprit is that no one compile and build from source anymore. Thus the hash didn't get updated. In my Intel Mac, it download binary directly from macport website.

After I fixed checksum and download site from github, it can proceed to compile.

github.setup        axel-download-accelerator axel 2.13.1

checksums           rmd160  da91494471f039818b93bff76327a67c12f099bb \
                    sha256  e22dce8c03ad64357cbebf54f7ea76dcc7de5b707db66a4cea56c87ae6c9c079

Although the compile failed due to C99 problem, that's another issue. I don't understand why macport didn't document that github.setup or download binary directly or support binary for Tiger.

This sucks.

[rickyzhang82 (Ricky Zhang)]

Finally, I got it all fixed. See my PR in ​https://github.com/kencu/TigerPorts/pull/4

[kencu (Ken)]

Ricky mentions Tiger, but this port is currently broken for building on all systems, I believe.

I can confirm that Ricky's Portfile fixes axel on 10.4, 10.6, and 10.12.

Ricky - do you want to go ahead and submit a PR to MacPorts for this? In doing so, it will run Travis builds on 10.10, 10.11, and 10.12 to verify those systems as well.

[rickyzhang82 (Ricky Zhang)]

My Intel Mac get the binary directly from macports. Thus it never build it from scratch.

I wonder how this works. I don't see this in MacPort documentation.

BTW, I don't mind send a PR to macports github. But what's the point if yours are for Tiger and only Tigers build it from scratch. I don't even notice axel is downloaded as binary in my Intel Mac.

[kencu (Ken)]

Oh, I find the same problem trying to build axel on all my machines, when building from source. You do it like this, to force a build from source even if a binary exists: sudo port -v -s install axel . So it would be general fix for all of MacPorts.

[ryandesign (Ryan Carsten Schmidt)]

Checksum mismatches will occur when projects move from one GitHub user or organization to another, as happened here when axel moved from the eribertomota user to the axel-download-accelerator organization.

If this problem is handled on its own (without a version update), it needs to be handled as a stealth update, not just by changing the checksums.

Since version 2.14 was just released, I'll instead fix it by updating the port to that version.

[ryandesign (Ryan Carsten Schmidt)]

In 09d8557defb6a8574279d49177bfaab93fbb567c/macports-ports:

axel: Update to 2.14

Closes: #54784