Opened 9 years ago

Closed 9 years ago

#49371 closed defect (duplicate)

Error: org.macports.checksum for port help2man returned: Unable to verify file checksums

Reported by: metamathematics@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: server/hosting Version: 2.3.4
Keywords: Cc: jatin.kala.jk@…
Port: help2man

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Failure of upgrade outdated - help2man-2.47.2

--->  Computing dependencies for help2man
--->  Verifying checksums for help2man
Error: Checksum (rmd160) mismatch for help2man-1.47.2.tar.xz
Error: Checksum (sha256) mismatch for help2man-1.47.2.tar.xz
Error: org.macports.checksum for port help2man returned: Unable to verify file checksums
Please see the log file for port help2man for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_help2man/help2man/main.log
Error: Problem while installing help2man
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
john-hatherleys-computer:~ TheBunker$ 

Change History (5)

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

Description: modified (diff)
Keywords: help2man removed

Did you read wiki:FAQ#checksums and try to determine which situation applies?

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

Can you provide any information to help us diagnose this problem? If there is a server out there delivering the wrong file to you, we need to know what that server is. Or, if it was a problem on your end, we need to know that so that we can close the ticket.

comment:3 Changed 9 years ago by jatin.kala.jk@…

Hi, I am having the same problem. I did a clean and re-install, but that did not fix it. All other ports are updating fine, so i don't think this is an issue on my machine per se. The port is being downloaded from: http://jog.id.packages.macports.org

$ sudo port clean help2man
Password:
--->  Cleaning help2man
$ sudo port install help2man
--->  Computing dependencies for help2man
--->  Fetching archive for help2man
--->  Attempting to fetch help2man-1.47.2_0.darwin_15.x86_64.tbz2 from http://packages.macports.org/help2man
--->  Attempting to fetch help2man-1.47.2_0.darwin_15.x86_64.tbz2 from http://lil.fr.packages.macports.org/help2man
--->  Attempting to fetch help2man-1.47.2_0.darwin_15.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/help2man
--->  Fetching distfiles for help2man
--->  Verifying checksums for help2man
Error: Checksum (rmd160) mismatch for help2man-1.47.2.tar.xz
Error: Checksum (sha256) mismatch for help2man-1.47.2.tar.xz
Error: org.macports.checksum for port help2man returned: Unable to verify file checksums
Please see the log file for port help2man for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_help2man/help2man/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port help2man failed

comment:4 in reply to:  1 Changed 9 years ago by metamathematics@…

Replying to ryandesign@…:

Did you read wiki:FAQ#checksums and try to determine which situation applies?

My installs usually come from internode or aarnet or nue.de. In this particular case it came from nue.de. There is no problem at my end. Everything works fine except help2man. Thanks for your trouble, it is appreciated. JLH

comment:5 in reply to:  3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: jatin.kala.jk@… added
Component: portsserver/hosting
Resolution: duplicate
Status: newclosed

Replying to jatin.kala.jk@…:

The port is being downloaded from: http://jog.id.packages.macports.org

No, it is not. MacPorts tried to download a precompiled package from three servers including that one, but didn't find it, so it then proceeded to try to build from source. It had already downloaded the source from a previous attempt, but the file it downloaded was not the correct one. We don't know where the incorrect file came from because your log doesn't show it, but I'm going to assume this is a duplicate of the aarnet server misconfiguration being tracked in #49416.

Note: See TracTickets for help on using tickets.