On Oct 12, 2015, at 6:24 PM, Bill Christensen wrote: > I'm seeing similar on several machines when trying to selfupdate MacPorts: > > > sudo port -d -v selfupdate > DEBUG: Copying /Users/billc/Library/Preferences/com.apple.dt.Xcode.plist to > /opt/local/var/macports/home/Library/Preferences > DEBUG: MacPorts sources location: > /opt/local/var/macports/sources/rsync.macports.org/release/tarballs > ---> Updating MacPorts base sources using rsync > receiving file list ... done > > sent 36 bytes received 69 bytes 4.29 bytes/sec > total size is 27013120 speedup is 257267.81 > receiving file list ... done > > sent 36 bytes received 76 bytes 4.57 bytes/sec > total size is 512 speedup is 4.57 > DEBUG: failed verification with key > /opt/local/share/macports/macports-pubkey.pem > DEBUG: openssl output: Verification Failure > child process exited abnormally > 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! > _______________________________________________
That's a problem verifying the signature of MacPorts base source when doing a selfupdate. That's reported here: https://trac.macports.org/ticket/49233 It likely has to do with the rsync server's current problems. That's different to Sepideh Razavi's problem which is a failure to verify a port archive's signature. Port archives don't have anything to do with rsync so this will have a different reason, and we need to see the debug output from his system to determine what it is. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users