[MacPorts] #20683: port upgrade does nothing with a downgraded package

MacPorts noreply at macports.org
Sun Aug 30 19:32:04 PDT 2009


#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


More information about the macports-tickets mailing list