#42339: Failed to install ghostscript ----------------------------+-------------------------------- Reporter: daniel.miau@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: ghostscript | ----------------------------+-------------------------------- Changes (by ryandesign@…): * cc: takanori@… (added) Old description:

I was not able to install ghostscript (using the command sudo port install ghostscript) on two Macs (both OSX 10.9.1). I checked the error log and find the following line strange (please also see the attached error log):

---------------------- :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 - ----------------------

The -dc option of gzip seems to decompress the package to standard output as opposed to the file system, is it something expected?

I have tried to manually decompressed the package located at '/opt/local/var/macports/distfiles/ghostscript/ghostscript-9.10.tar.gz' and the package seems to be ok.

The sudo command gives the permission to write to the directory '/opt/local/var/macports/build/_private_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work' too.

New description: I was not able to install ghostscript (using the command `sudo port install ghostscript`) on two Macs (both OSX 10.9.1). I checked the error log and find the following line strange (please also see the attached error log): {{{ :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 - }}} The `-dc` option of `gzip` seems to decompress the package to standard output as opposed to the file system, is it something expected? I have tried to manually decompressed the package located at '/opt/local/var/macports/distfiles/ghostscript/ghostscript-9.10.tar.gz' and the package seems to be ok. The `sudo` command gives the permission to write to the directory '/opt/local/var/macports/build/_private_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work' too. -- Comment: Yes, MacPorts is designed to decompress archives to stdout, which is then fed via a pipe (`|`) to tar which extracts the files. This is the same for most ports. Something unique is happening on your system that's causing the problem you're experiencing. I have no problem extracting ghostscript on Mavericks, and the port doesn't do anything special at extract time. Do other ports exhibit the same failure for you or just ghostscript? The log you attached is not from a clean attempt; as it says at the very top of our ticket filing instructions, that [http://guide.macports.org/chunked/project.html#project.tickets.prerequisites could very well cause problems]. Clean ghostscript and try again. If that doesn't help, check that the /usr/bin/tar and /usr/bin/gzip programs function correctly. -- Ticket URL: <https://trac.macports.org/ticket/42339#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#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

#42339: Extract fails when MacPorts prefix is a symlink ----------------------------+-------------------------------- Reporter: daniel.miau@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: duplicate | Keywords: Port: | ----------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => duplicate -- Ticket URL: <https://trac.macports.org/ticket/42339#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X