#20881 closed defect (invalid)
"port upgrade outdated" stops on first build failure
Reported by: | fracai | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.8.0 |
Keywords: | upgrade, outdated | Cc: | |
Port: |
Description
Previously (v1.7), "port upgrade outdated" would build each outdated port in sequence, only failing to upgrade a port if a dependency failed. With v1.8 upgrade outdated stops upgrading ports after the first failure, even if remaining ports would otherwise build successfully.
For example:
$ port echo outdated port1 port2 port3 $ port upgrade outdated ---> Computing dependencies for port1 ---> Building port1 ---> Activating port1 ---> Computing dependencies for port2 ---> Building port2 Error: Unable to upgrade port: 1 $ port echo outdated port2 port3 $ port upgrade port3 ---> Computing dependencies for port3 ---> Building port3 ---> Activating port3 $ port echo outdated port2
Desired behavior:
$ port echo outdated port1 port2 port3 $ port upgrade outdated ---> Computing dependencies for port1 ---> Building port1 ---> Activating port1 ---> Computing dependencies for port2 ---> Building port2 Error: Unable to upgrade port: 1 ---> Computing dependencies for port3 ---> Building port3 ---> Activating port3 $ port echo outdated port2
Change History (3)
comment:1 Changed 15 years ago by blb@…
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 Changed 15 years ago by jmroot (Joshua Root)
Component: | ports → base |
---|
Note: See
TracTickets for help on using
tickets.
That's intentional (see ticket #13918). If you really want it to continue, you want to use the -p switch:
as in