Opened 11 years ago

Closed 10 years ago

#24870 closed defect (worksforme)

perl5.8 checksum mismatch

Reported by: 78@… Owned by: ghosthound
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: ryandesign (Ryan Schmidt)
Port: perl5.8

Description (last modified by ryandesign (Ryan Schmidt))

--->  Computing dependencies for perl5.8
--->  Verifying checksum(s) for perl5.8
--->  Checksumming perl-5.8.9.tar.bz2
Portfile checksum: perl-5.8.9.tar.bz2 md5 1cb52a76ce77fa300218da96577793ec
Distfile checksum: perl-5.8.9.tar.bz2 md5 055b83bb5dd801e3b7cbcb130529e3f0
Portfile checksum: perl-5.8.9.tar.bz2 sha1 19843b5a7585cf35d96c07dbcd419bbdd5813617
Distfile checksum: perl-5.8.9.tar.bz2 sha1 90c9d9feb84f87858ad23b491741ca06c7e82e2f
Portfile checksum: perl-5.8.9.tar.bz2 rmd160 680004238d626ec985075e1b4519b7f0b34f57e5
Distfile checksum: perl-5.8.9.tar.bz2 rmd160 6958a862b1ef422300b610d06a1763a190367fa4
The correct checksum line may be:
checksums           md5     055b83bb5dd801e3b7cbcb130529e3f0 \
                    sha1    90c9d9feb84f87858ad23b491741ca06c7e82e2f \
                    rmd160  6958a862b1ef422300b610d06a1763a190367fa4
Warning: the following items did not execute (for perl5.8): org.macports.activate org.macports.extract org.macports.checksum org.macports.patch org.macports.configure org.macports.destroot org.macports.install
To report a bug, see <>

Change History (5)

comment:1 Changed 11 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added; 78@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to ricci@…
Port: perl5.8 added
Priority: HighNormal
Summary: Cannot install Perlperl5.8 checksum mismatch

Please remember to use WikiFormatting, to fill in the port field, and to Cc the maintainer. You don't need to Cc yourself. High priority tickets should only be created by MacPorts team members.

We have a FAQ entry about checksum mismatches. Have you read it?

comment:2 Changed 11 years ago by 78@…

I did read the checksum mismatches and thought it seemed to indicate that you needed to manually update them when the src package was updated?

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

I am not convinced the source package was updated. Instead I think you just got a bad download. Go back to the FAQ and follow the steps at the top (selfupdate, clean --all, install) and if it fails again, show us the output, which should include the line that says where the problem file was downloaded from; we can then investigate what's up with that server.

comment:4 Changed 10 years ago by ryandesign (Ryan Schmidt)

Any news?

comment:5 Changed 10 years ago by ryandesign (Ryan Schmidt)

Resolution: worksforme
Status: newclosed

Closing due to lack of response.

Note: See TracTickets for help on using tickets.