#19253: port clean aborts with error if port has been removed from collection but is installed -----------------------------------+---------------------------------------- Reporter: febeling@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.1 Keywords: upgrade obsolete | Port: -----------------------------------+---------------------------------------- Comment(by febeling@…): Replying to [comment:3 raimue@…]:
Removing ports on upgrade could be bad as we also allow installation of ports not in the PortIndex by using the `current` pseudo-port or `-D portdir`.
good point. So then ignoring them is in fact the right behaviour.
I can't think of a way how that could happen with the recommended `port upgrade outdated` as a removed port is never in the outdated set, so I assume you used `port upgrade installed` as gail is still in the installed set?
But that's what I did, actually, port upgrade outdated. And I was just assuming that this was not properly handled. I will run a test and report later. I had the same exact behaviour later with render, which was removed/renamed as well, so I was quite confident that this was always the case with removed ports. -- Ticket URL: <http://trac.macports.org/ticket/19253#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS