port upgrade does nothing with a downgraded package

[yaseppochi (Stephen J. Turnbull)]

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.

[ryandesign (Ryan Carsten Schmidt)]

I'm also surprised "port deactivate" did not seem to deactivate anything (unless you snipped the output). What does

port installed autoconf

say?

[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 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.

[ryandesign (Ryan Carsten Schmidt)]

I confirmed this issue is still relevant in MacPorts 2.0.3.