Hi. Is 'port upgrade outdated' the wrong command to upgrade all my obsolete ports? It gives:
sudo port upgrade outdated Can't map the URL 'file://.' to a port description file (Could not find Portfile in .). Please verify that the directory and portfile syntax are correct. Error: To use the current port, you must be in a port's directory Error: No port found.
The man page looks like it should work. Michael
Michael, This is an unfortunately accident, which I believe means you don't have any outdated ports. What does "port outdated" show? James On Sep 21, 2006, at 9:21 AM, Michael Stevens wrote:
Hi.
Is 'port upgrade outdated' the wrong command to upgrade all my obsolete ports? It gives:
sudo port upgrade outdated Can't map the URL 'file://.' to a port description file (Could not find Portfile in .). Please verify that the directory and portfile syntax are correct. Error: To use the current port, you must be in a port's directory Error: No port found.
The man page looks like it should work.
Michael _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
James Berry wrote:
Michael,
This is an unfortunately accident, which I believe means you don't have any outdated ports.
What does "port outdated" show?
mstevens@michael-stevens-computer:/opt/local/bin
sudo port outdated Password: The following installed ports are outdated: mstevens@michael-stevens-computer:/opt/local/bin
So it looks like, yes, all my ports are up to date. I'm, umm, not convinced the message I got is a good way to indicate that, though. Michael
On Sep 21, 2006, at 11:49 AM, Michael Stevens wrote:
James Berry wrote:
Michael, This is an unfortunately accident, which I believe means you don't have any outdated ports. What does "port outdated" show?
So it looks like, yes, all my ports are up to date.
I'm, umm, not convinced the message I got is a good way to indicate that, though.
Yes, you're absolutely right. It's a bug that it's confusing. I'll try to fix it before too long. If you could file a bug against it, that would be great. I think the easiest fix is to improve the wording of the error message to be more clear about what happened: basically, when the pseudo-port "outdated" expands to no ports, then the upgrade action (and many others) tries to use the port in the current directory. Since there is no port in the current directory, it gives the error about no ports. As a more complex fix, we should somehow know the difference between no expression, and the case where we have an expression that evaluates to nothing: this would be the really right thing, but might be more difficult. James
On 9/21/06, James Berry <jberry@macports.org> wrote:
On Sep 21, 2006, at 11:49 AM, Michael Stevens wrote:
James Berry wrote:
Michael, This is an unfortunately accident, which I believe means you don't have any outdated ports. What does "port outdated" show?
So it looks like, yes, all my ports are up to date.
I'm, umm, not convinced the message I got is a good way to indicate that, though.
Yes, you're absolutely right. It's a bug that it's confusing.
I'll try to fix it before too long. If you could file a bug against it, that would be great. I think the easiest fix is to improve the wording of the error message to be more clear about what happened: basically, when the pseudo-port "outdated" expands to no ports, then the upgrade action (and many others) tries to use the port in the current directory. Since there is no port in the current directory, it gives the error about no ports.
As a more complex fix, we should somehow know the difference between no expression, and the case where we have an expression that evaluates to nothing: this would be the really right thing, but might be more difficult.
was michael referring to the misleading output from 'port outdated'? i filed the following and attached a diff to resolve in early may: RFE: 'port oudated' should provide different output when no outdated ports http://trac.macosforge.org/projects/macports/ticket/8723 it was demoted from 'bug' to 'enhancement' yesterday... cheers, jean-pierre
jeanpierre@gmail.com wrote:
was michael referring to the misleading output from 'port outdated'?
i filed the following and attached a diff to resolve in early may:
RFE: 'port oudated' should provide different output when no outdated ports http://trac.macosforge.org/projects/macports/ticket/8723
it was demoted from 'bug' to 'enhancement' yesterday...
I was talking about the even more misleading output from 'port upgrade outdated' - if there are no outdated ports, it attempts to upgrade a port located in the current directory, and gives an error if it can't find it. Michael
participants (3)
-
James Berry
-
jeanpierre＠gmail.com
-
Michael Stevens