Opened 15 years ago

Last modified 12 years ago

#20683 new defect

port upgrade does nothing with a downgraded package — at Version 1

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 (1)

comment:1 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

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

port installed autoconf

say?

Note: See TracTickets for help on using tickets.