[MacPorts] #20683: port upgrade does nothing with a downgraded package
#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: --------------------------------+------------------------------------------- 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. -- Ticket URL: <http://trac.macports.org/ticket/20683> MacPorts <http://www.macports.org/> Ports system for Mac OS
#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
#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: --------------------------------+------------------------------------------- Comment(by stephen@…): Replying to [comment:1 ryandesign@…]:
I'm also surprised "port deactivate" did not seem to deactivate anything (unless you snipped the output). What does {{{ port installed autoconf }}} say?
I was presenting a recipe for reproduction, recovered from shell {{{history | grep port | tail}}}, not a log. The terminal buffer was a huge mess because of intervening error spew from port when configure or build stages broke. At the time port installed autoconf probably reported: {{{ wideload:src/MacPorts 10:59$ port installed autoconf The following ports are currently installed: autoconf @2.63_0 autoconf @2.64_0 }}} because the reason I noticed this was downgrading to 2.63 to work around the 2.64 bugs. There mght have been some earlier versions still hanging around though. -- Ticket URL: <http://trac.macports.org/ticket/20683#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#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: --------------------------------+------------------------------------------- Comment(by ryandesign@…): I confirmed this issue is still relevant in MacPorts 2.0.3. -- Ticket URL: <https://trac.macports.org/ticket/20683#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts