Opened 10 years ago

Closed 10 years ago

#47767 closed defect (invalid)

port selfupdate failed: Failed to verify signature for MacPorts source

Reported by: franck.bonin@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.3.3
Keywords: Cc:
Port:

Description

Unable to update macport since today :

$ sudo port -d selfupdate
Password:
DEBUG: sw_vers exists but running it failed: couldn't create error file for command: no such file or directory
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
--->  Updating MacPorts base sources using rsync
receiving file list ... done
base.tar

sent 31276 bytes  received 236823 bytes  48745.27 bytes/sec
total size is 27013120  speedup is 100.76
receiving file list ... done
base.tar.rmd160

sent 64 bytes  received 635 bytes  466.00 bytes/sec
total size is 512  speedup is 0.73
DEBUG: failed verification with key /opt/local/share/macports/macports-pubkey.pem
DEBUG: openssl output: couldn't create error file for command: no such file or directory
DEBUG: Failed to verify signature for MacPorts source!
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: Failed to verify signature for MacPorts source!
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

I don't now if it's a local or a remote error with certificates.

Change History (4)

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

Component: portsbase

Replying to franck.bonin@…:

DEBUG: sw_vers exists but running it failed: couldn't create error file for command: no such file or directory
DEBUG: openssl output: couldn't create error file for command: no such file or directory

Well those messages aren't normal. Does running sw_vers at the command line work?

comment:2 in reply to:  1 Changed 10 years ago by franck.bonin@…

Replying to ryandesign@…:

Replying to franck.bonin@…:

DEBUG: sw_vers exists but running it failed: couldn't create error file for command: no such file or directory
DEBUG: openssl output: couldn't create error file for command: no such file or directory

Well those messages aren't normal. Does running sw_vers at the command line work?

Yes, and sw_cers output is :

ProductName:	Mac OS X
ProductVersion:	10.6.8
BuildVersion:	
10K549

I think there is someting wrong on this particular system, since I succefully "selfupdated" another macport installation on a 10.6.8 system. But I can't figure what is this particular problem.

I beleive /opt/local/share/macports/macports-pubkey.pem is the good one on this system I try to clean up downloaded things under /opt/local/var/macports/sources/rsync.macports.org/release/tarballs and repair system permissions but nothing worked

comment:3 Changed 10 years ago by franck.bonin@…

Every things are back to normal this morning after a complete system reboot.

If only Mac OS X could avoid Windows behaviour ...

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

Resolution: invalid
Status: newclosed

Alright, good to hear.

Note: See TracTickets for help on using tickets.