#39864: port installation fails during extraction after update -------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by ryandesign@…): So the problem is: {{{ :debug:extract Executing command line: cd "$prefix/var/macports/build/_prefix_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_autoconf/autoconf/work" && $prefix/bin/xz -dc '$prefix/var/macports/distfiles/autoconf/autoconf-2.69.tar.xz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract /usr/bin/gnutar: autoconf-2.69: Cannot mkdir: Operation not permitted }}} Somehow $prefix isn't getting expanded. Any idea why that is? Have you made any unusual changes to your macports.conf? What's the value of prefix in macports.conf? -- Ticket URL: <https://trac.macports.org/ticket/39864#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#39864: port installation fails during extraction after update -------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by ryandesign@…): Oh. Ok. Well then the problem is that you're running "port install coreutils" instead of "sudo port install coreutils". Unless you've installed MacPorts from source with a different user, MacPorts needs to run with elevated privileges. -- Ticket URL: <https://trac.macports.org/ticket/39864#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#39864: port installation fails during extraction after update -------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by ryandesign@…): Do you remember exactly what arguments you supplied to the ./configure script? -- Ticket URL: <https://trac.macports.org/ticket/39864#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#39864: port installation fails during extraction after update -------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by rharwood@…): No, it's not symlinked. Those are real directories. My command would have been something like {{{ ./configure --with-no-root-privileges --prefix=$prefix }}} I should note that previous selfupdates have gone off without a hitch. -- Ticket URL: <https://trac.macports.org/ticket/39864#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#39864: port installation fails during extraction after update -------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by ryandesign@…): If you're going to use --with-no-root-privileges you probably need to set --with-install-user and --with-install-group too. I'm not sure if you also need to set --with-macports-user. -- Ticket URL: <https://trac.macports.org/ticket/39864#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X

#39864: port installation fails during extraction after update -------------------------+-------------------------------- Reporter: rharwood@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Resolution: | Keywords: Port: | -------------------------+-------------------------------- Comment (by rharwood@…): Replying to [comment:10 larryv@…]:

Replying to [comment:7 rharwood@…]:

...

I should note that previous selfupdates have gone off without a hitch.

Could you try again after adding `sandbox_enable no` to macports.conf?

Alright, that worked. This is an Server install, with homedirs off a disk in /Volumes. Server has decided that the best way to present this information is to hand me my homedir as /Network/Servers/<servername>/Volumes/<drivename>/<diskname>/<my homedir> rather than just the path in /Volumes. As a result, <servername> is a symlink to /. The fix for #39850 will probably work. Sorry for the trouble; now off to bother root… -- Ticket URL: <https://trac.macports.org/ticket/39864#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X