#42339: Extract fails when MacPorts prefix is a symlink ----------------------------+-------------------------------- Reporter: daniel.miau@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | ----------------------------+-------------------------------- Changes (by ryandesign@…): * cc: takanori@… (removed) * cc: ryandesign@… (added) * component: ports => base * port: ghostscript => Comment: Replying to [ticket:42339 daniel.miau@…]:
{{{ :debug:extract Executing command line: cd "/opt/local/var/macports/build/_private_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/ghostscript/ghostscript-9.10.tar.gz' | /usr/bin/tar -xf - }}}
I neglected to notice originally that this line shows that MacPorts is in ''/private''/opt/local instead of just /opt/local, presumably with /opt being a symlink to /private/opt. This could happen if you installed an ancient version of Cisco VPN. We had a FAQ entry for this problem, but removed it from the FAQ over 7 years ago because at that time it was already old news (Cisco had already fixed the problem in newer versions of their installer), but you can follow those instructions to set things right to put MacPorts back into /opt proper: wiki:FAQ?version=1#IjustinstalledMacPorts1.2fromthe.dmgandIseemtohavelostallmyinstalledportsakaCiscoVPNatemyMacPorts The reason this situation is now an actual problem is that recent versions of MacPorts have a bug when the configured prefix is a symlink. I can't find the ticket about that at the moment. It may already have been fixed in trunk (which will become MacPorts 2.3). -- Ticket URL: <https://trac.macports.org/ticket/42339#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X