#20683: port upgrade does nothing with a downgraded package --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.8.99 Keywords: | Port: --------------------------------+------------------------------------------- Old description:
Specifically, in the following sequence {{{ # port outdated The following installed ports are outdated: autoconf 2.63_0 < 2.64_0 # port deactivate autoconf @2.64_0 # port deactivate autoconf @2.63_0 # port upgrade autoconf # port outdated The following installed ports are outdated: autoconf 2.63_0 < 2.64_0 }} 'port upgrade' does nothing and says nothing about the situation. It seems to me that port *should* do the upgrade. However, if there's a reason not to do that, it should report that it isn't doing it and suggest a deactivate ... activate cycle instead.
New description: Specifically, in the following sequence {{{ # port outdated The following installed ports are outdated: autoconf 2.63_0 < 2.64_0 # port deactivate autoconf @2.64_0 # port deactivate autoconf @2.63_0 # port upgrade autoconf # port outdated The following installed ports are outdated: autoconf 2.63_0 < 2.64_0 }}} 'port upgrade' does nothing and says nothing about the situation. It seems to me that port *should* do the upgrade. However, if there's a reason not to do that, it should report that it isn't doing it and suggest a deactivate ... activate cycle instead. -- Comment(by ryandesign@…): I'm also surprised "port deactivate" did not seem to deactivate anything (unless you snipped the output). What does {{{ port installed autoconf }}} say? -- Ticket URL: <http://trac.macports.org/ticket/20683#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS