#48501: has this file gone atlas-3.10.2_1+clang.darwin_14.x86_64.tbz2? --------------------------+--------------------- Reporter: spark1631@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => vince@… * keywords: atlas, octave => * port: => atlas Comment: 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? -- Ticket URL: <https://trac.macports.org/ticket/48501#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#48501: atlas @3.10.2_1: checksum failure for binary archive --------------------------+--------------------- Reporter: spark1631@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Comment (by 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? -- Ticket URL: <https://trac.macports.org/ticket/48501#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#48501: atlas @3.10.2_1: checksum failure for binary archive --------------------------+--------------------- Reporter: spark1631@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Comment (by vince@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/48501#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X

#48501: atlas @3.10.2_1: checksum failure for binary archive --------------------------+--------------------- Reporter: spark1631@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Comment (by ryandesign@…): Replying to [comment:5 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 [comment:6 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. -- Ticket URL: <https://trac.macports.org/ticket/48501#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

#48501: atlas @3.10.2_1: checksum failure for binary archive --------------------------+--------------------- Reporter: spark1631@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Comment (by ionic@…): Ping. Especially now that buildbot is (half) working again. -- Ticket URL: <https://trac.macports.org/ticket/48501#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X