Opened 17 years ago

Closed 16 years ago

#12288 closed defect (fixed)

BUG: port upgrade outdated error when no ports outdated

Reported by: tim.lahey@… Owned by: macports-tickets@…
Priority: Low Milestone: MacPorts 1.7.0
Component: base Version: 1.5.0
Keywords: Cc: jberry@…, ryandesign (Ryan Carsten Schmidt)
Port:

Description

If no ports need upgrading, using the command port upgrade outdated gives the following error on Macports 1.5: 

Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/username").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.
(you might also see this message if a pseudo-port such as
outdated or installed expands to no ports).
Error: No port  found.

In earlier versions it just failed silently. It would be nice if this old behaviour were restored.

Change History (6)

comment:1 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)

Component: ports → base

comment:2 Changed 17 years ago by nox@…

Priority: Nice to have → Low
Version: 1.5 → 1.5.0

comment:3 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)

Cc: jberry@… added
Milestone: MacPorts 1.5 → MacPorts base bugs

Wasn't this fixed already, James?

-jmpp

comment:4 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

I just tested in MacPorts 1.6.0 and also in trunk r34285 and the problem remains in both.

comment:5 Changed 16 years ago by jmroot (Joshua Root)

As of trunk @ r40402, the error message given is Error: No ports found.

comment:6 in reply to:  5 Changed 16 years ago by blb@…

Milestone: MacPorts base bugs → MacPorts 1.7.0
Resolution: → fixed
Status: new → closed

Replying to jmr@…:

As of trunk @ r40402, the error message given is Error: No ports found.

So fixed for 1.7.0, noted in ChangeLog in r42055.

Note: See TracTickets for help on using tickets.