Opened 7 years ago

Closed 7 years ago

#35721 closed defect (fixed)

muttils: checksum mismatch

Reported by: bxf4@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: checksum Cc:
Port: muttils

Description

packages.macports.org/muttils doesn't exist

distfiles.macports.org/muttils is empty

:msg:archivefetch --->  Attempting to fetch muttils-1.1_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/muttils
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404
:msg:archivefetch --->  Attempting to fetch muttils-1.1_0.darwin_11.x86_64.tbz2 from http://macports.packages.ionic.de/muttils
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404

Is this a configuration problem in the port, or has the port been removed? If the latter, should it be removed from the list of available ports? Project does appear to still be at http://bitbucket.org/blacktrash/muttils

Change History (3)

comment:1 in reply to:  description Changed 7 years ago by ryandesign (Ryan Schmidt)

Summary: muttils @1.1 -- no files to download?muttils: checksum mismatch

Replying to bxf4@…:

packages.macports.org/muttils doesn't exist

That just means we don't have any precompiled binaries available for this port. There are numerous reasons why that might be, but it's not a problem. MacPorts should then try to download the source and build it on your computer.

distfiles.macports.org/muttils is empty

That just means we haven't mirrored the distfile(s). There are numerous reasons why that might be, including that the server was down when we tried to mirror, or that the checksums didn't match. The latter appears to be the case, as I currently get a checksum mismatch when I try this port. There are numerous reasons why a checksum mismatch might be occurring, so we need to analyze and determine which it is.

comment:2 Changed 7 years ago by ryandesign (Ryan Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

We should just update the port to version 1.3 which will fix the problem.

comment:3 Changed 7 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.