atlas @3.10.2_1: checksum failure for binary archive

[spark1631@…]

I try to use macports to install octave. but it keeps telling me that it failed to do checksum for this file atlas-3.10.2_1+clang.darwin_14.x86_64.tbz2.

when i check the sites where macports looks for this file, i have found that this file is even not there.

So is there anything wrong, or i am missing something?

[ryandesign (Ryan Carsten Schmidt)]

Could you please show us the exact error message you are getting?

The file you are referring to, atlas-3.10.2_1+clang.darwin_14.x86_64.tbz2, is a binary package. MacPorts will look for binary packages on our server and use them if available, but if not available, this is not a problem; MacPorts will instead build the port on your system from source. It is possible however that the source distfile has a checksum mismatch for some reason. If that's what's happening, the first thing I'd try is to remove the distfile with the checksum mismatch (by running "sudo port clean --all atlas") and then try again; maybe the download was truncated or corrupted.

atlas used to be a special case: it deliberately disabled the use of binary packages (in r104549). My understanding is that this was because atlas builds itself differently depending on the machine's hardware. However this was reverted in r111734 and now atlas will use binary packages again, if available. Vince, was this change intentional?

[Ionic (Mihai Moldovan)]

Thank you. Next time, please remember to CC the port maintainer(s), if any.

When in doubt, don't set keywords, but make sure to list ports in the "Port" field.

I'm not sure the maintainer can help here, though.

It seems you either downloaded a corrupt binary archive, or something corrupted on our side.

Run sudo port clean --all atlas and try installing octave again.

[spark1631@…]

sorry about the ticket's misconfiguration.

I have tried "sudo port clean --all atlas", but nothing changes when issuing "sudo port install octave".

the attached image is what i got.

any idea?

[Ionic (Mihai Moldovan)]

You should have read MisbehavingServers as outlined in the output...

[Veence (Vincent)]

There is a priori no binary package for Atlas, because the gist of Atlas is to be optimised exactly for the CPU you're using. Building a binary package would either be suboptimal or may result in a crash, should you have a processor older than the one used to create the binary package. Therefore, unless I made a mistake, installing Atlas (a four hour process circa) should always happen from source.

[spark1631@…]

So i tried what the MisbehavingServers suggests, that is downloading the source tarball manually. And it has worked..

Thanks you guys.

One last thing, why doesn't "sudo port install atlas" try the distfile mirror that macports maintained? if i can download the file from there, macports could too.

[ryandesign (Ryan Carsten Schmidt)]

Replying to vince@…:

Therefore, unless I made a mistake, installing Atlas (a four hour process circa) should always happen from source.

Read the last paragraph of my comment:1 above.

Replying to spark1631@…:

One last thing, why doesn't "sudo port install atlas" try the distfile mirror that macports maintained? if i can download the file from there, macports could too.

MacPorts tries servers in order of which ones are closest to you (i.e. by ping times). If a server doesn't have the file, it moves on to the next. In your case, the server MacPorts reached claimed to have the file, so MacPorts used it. But it was the wrong file, because the server it reached was not the right server, because of your DNS server's misconfiguration.

[Ionic (Mihai Moldovan)]

vince: to re-iterate: currently, atlas is NOT built from source but installed from archives, if available. You disabled the clearing of archive_sites in a previous commit. Was this a mistake?

[Ionic (Mihai Moldovan)]

Ping. Especially now that buildbot is (half) working again.

[Veence (Vincent)]

• Not relevant anymore -