Opened 11 years ago

Closed 11 years ago

#41785 closed defect (worksforme)

gettext @0.18.3.1_1 (devel) Install Error - failure to verify signature for archive!

Reported by: geoffsamuels@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc:
Port: gettext

Description (last modified by mf2k (Frank Schima))

I have just done a new install of MacPorts (version 2.2.1-10.9) from the disk image for Mac 10.9 (Mavericks). I have previously installed the latest version of Xtools and the command line tools. The fetched archive fails verification with key /opt/local/share/macports/macports-pubkey.pem; MacPorts then attempts to fetch a zipped archive from the ftp.gnu.org site but this archive fails the checksum test. Here is what I see:

--->  Computing dependencies for gettext
--->  Fetching archive for gettext
--->  Attempting to fetch gettext-0.18.3.1_1.darwin_13.x86_64.tbz2 from http://packages.macports.org/gettext
--->  Attempting to fetch gettext-0.18.3.1_1.darwin_13.x86_64.tbz2.rmd160 from http://packages.macports.org/gettext
Warning: Failed to verify signature for archive!
--->  Fetching distfiles for gettext
--->  Attempting to fetch gettext-0.18.3.1.tar.gz from ftp://ftp.gnu.org/gnu/gettext
--->  Verifying checksums for gettext
Error: Checksum (rmd160) mismatch for gettext-0.18.3.1.tar.gz
Error: Checksum (sha256) mismatch for gettext-0.18.3.1.tar.gz
Error: org.macports.checksum for port gettext returned: Unable to verify file checksums

I'm going to attempt to attach the log file - I'm wondering if this is Mavericks problem or something else.

Attachments (1)

main.log (7.3 KB) - added by geoffsamuels@… 11 years ago.

Download all attachments as: .zip

Change History (8)

Changed 11 years ago by geoffsamuels@…

Attachment: main.log added

comment:1 Changed 11 years ago by mf2k (Frank Schima)

Cc: ryandesign@… removed
Description: modified (diff)
Keywords: mavericks removed
Owner: changed from macports-tickets@… to ryandesign@…

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

I don't know why the signature of the binary archive would fail to verify.

I checked the distfile on ftp.gnu.org; its checksums match those in the Portfile. Maybe you got a truncated or corrupted download. "sudo port clean --all gettext" and try again.

comment:3 in reply to:  2 ; Changed 11 years ago by geoffsamuels@…

Replying to ryandesign@…:

I don't know why the signature of the binary archive would fail to verify.

I checked the distfile on ftp.gnu.org; its checksums match those in the Portfile. Maybe you got a truncated or corrupted download. "sudo port clean --all gettext" and try again.

I've done the clean --all gettext thing six or seven times and still get the same result. Has anyone tried a port install gettext on Mac OS 10.9 (Mavericks) system? The signature verify failure and the checksum failures seem to be related.

comment:4 in reply to:  3 ; Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to geoffsamuels@…:

I've done the clean --all gettext thing six or seven times and still get the same result. Has anyone tried a port install gettext on Mac OS 10.9 (Mavericks) system? The signature verify failure and the checksum failures seem to be related.

The failures may be related, but not for the reason you think; you may be experiencing network issues. The upstream distfiles and the signatures for our binary archives have absolutely nothing to do with each other. And I can verify that the GNU distfiles are fine.

Are the files you’re downloading actually tarballs? What does

% file /opt/local/var/macports/distfiles/gettext/gettext-0.18.3.1.tar.gz

say? (Adjust the path for your MacPorts installation as necessary.)

comment:5 in reply to:  4 Changed 11 years ago by geoffsamuels@…

Replying to larryv@…:

Replying to geoffsamuels@…:

I've done the clean --all gettext thing six or seven times and still get the same result. Has anyone tried a port install gettext on Mac OS 10.9 (Mavericks) system? The signature verify failure and the checksum failures seem to be related.

The failures may be related, but not for the reason you think; you may be experiencing network issues. The upstream distfiles and the signatures for our binary archives have absolutely nothing to do with each other. And I can verify that the GNU distfiles are fine.

Are the files you’re downloading actually tarballs? What does

% file /opt/local/var/macports/distfiles/gettext/gettext-0.18.3.1.tar.gz

say? (Adjust the path for your MacPorts installation as necessary.)

Thanks for checking on this - it probably is a network issue; I'll try again today. As a precaution I disabled my Intego virus checker (may not have anything to with with things but can't hurt). I checked the gettext tarball with file and it's gzip compressed data, from Unix as expected.

comment:6 Changed 11 years ago by geoffsamuels@…

Problem solved? Perhaps it was that the tenth time was the charm but on a hunch I temporarily turned off my firewall and the gettext port installed. Perhaps this is a quirk of the Mac OS 10.9 (Mavericks) firewall. Thanks to those at MacPorts who checked things for me.

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

Resolution: worksforme
Status: newclosed

I am on Mavericks, have the firewall on, and have not seen this problem before.

Note: See TracTickets for help on using tickets.