#50867: port upgrade outdated fails with checksum error but checksum is OK. ------------------------+-------------------------------- Reporter: orcioni@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by orcioni@…): Replying to [comment:4 ryandesign@…]:
Replying to [comment:3 orcioni@…]:
Replying to [comment:2 ryandesign@…]:
The log says:
{{{ DEBUG: openssl output: couldn't create error file for command: permission denied }}}
With a little more research, I've found that this is a Tcl error message, generated when Tcl is trying to launch a program, but cannot create a temporary file to store that program's error output. The problem is not specific to the openssl command. This explains why running the openssl command on the command line, outside of Tcl, succeeds.
I agree that is not a porblem of openssl. On another computer I get the same error by upgrading hdf5: Warning: Failed to verify signature for archive! Error: org.macports.archivefetch for port hdf5 returned: archivefetch failed for hdf5 @1.8.16_2+cxx+hl Please see the log file for port hdf5 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_hdf5/hdf5/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets
{{{ bash-3.2# ls -ld /tmp lrwxr-xr-x@ 1 root wheel 11 15 Nov 2014 /tmp -> private/tmp }}}
This only shows us the permissions of the /tmp symlink, not the
permissions of the /private/tmp directory that the symlink points to. Can you try:
{{{ ls -ld /private/tmp }}}
As said, I have the same problem on two computers. In the following you can find the result of the command execution on both of them: drwxrwxrwt 7 root wheel 238 1 Apr 19:37 /private/tmp drwxr-xr-x@ 19 sim staff 646 2 Apr 04:07 /private/tmp On the first one, I work around the problem by completely uninstalling macport and reinstalling it. On the second I maintain the old macport. [[BR]] thanks [[BR]] S. -- Ticket URL: <https://trac.macports.org/ticket/50867#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X