#44764: coreutils 8.23_0 failed to upgrade -------------------------+-------------------------- Reporter: jschnide@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: coreutils | -------------------------+-------------------------- Comment (by jschnide@…): Replying to [comment:12 ryandesign@…]:
The only problem with the portfile is that it does not allow itself to be used as root. Admittedly this is an unusual restriction and I could revert r124489 to allow this again. However it seems that users are unaware that they are running as root and are unaware of the security implications of doing that, so perhaps that's what we should fix instead.
jschnide, your log does not include the usual privilege-dropping lines. Usually one starts MacPorts with `sudo`, thus giving it root privileges. MacPorts then quickly gives up those privileges and switches to the unprivileged `macports` user, but in your log, that's not happening. Do you have any idea why? Since you're running MacPorts on a system for which we don't provide binaries yet, I presume you compiled MacPorts from source. What configure arguments did you use?
I did nothing unusual. I first used the uninstall instructions on the macports web pages. I then did copy and paste from the install page on how to install from source on the macports web pages. My standard process is to sudo bash, port -d selfupdate, port upgrade outdated and then port -f uninstall inactive. Just to clarify, what process should be followed whenever macports is updated? Should users should replace macports.conf with macports.conf.defaults? I've been macports for many years as what aware of this step. Thanks -- Ticket URL: <https://trac.macports.org/ticket/44764#comment:13> MacPorts <http://www.macports.org/> Ports system for OS X