Opened 15 years ago
Last modified 13 years ago
#20683 new defect
port upgrade does nothing with a downgraded package
Reported by: | yaseppochi (Stephen J. Turnbull) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.8.99 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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.
Change History (3)
comment:1 follow-up: 2 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:2 Changed 15 years ago by yaseppochi (Stephen J. Turnbull)
Replying to ryandesign@…:
I'm also surprised "port deactivate" did not seem to deactivate anything (unless you snipped the output). What does
port installed autoconfsay?
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.
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
I confirmed this issue is still relevant in MacPorts 2.0.3.
I'm also surprised "port deactivate" did not seem to deactivate anything (unless you snipped the output). What does
say?