Ticket #13065 (closed defect: duplicate)
'port -Rp upgrade' attempts to rebuild the same failed package forever
| Reported by: | william.allen.simpson@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.5.2 |
| Keywords: | Cc: | jmr@… | |
| Port: |
Description
As seen in #12960, an upgrade with a failed build can endlessly loop -- in that case 77 times (6 hours) before I killed it. Presumably, the build list should be sorted, with a single entry in the list, rather than multiple recursive entries.
Probably dependent on the build list described in #10827 and others, reported a year ago, that was supposed to be in Milestone 1.5!
However, not exactly a duplicate, as this is an application of different parameters that creates (and always creates) an infinite loop.
Change History
comment:2 Changed 5 years ago by jmr@…
- Status changed from new to closed
- Cc jmr@… added; william.allen.simpson@… removed
- Resolution set to duplicate
- Priority changed from High to Normal
As far as I can tell, you can never get an unlimited number of upgrade attempts for any one port, but you can get very large numbers of them. (Also, it doesn't appear that -p could have any effect on this behaviour.)
I'm calling this a duplicate of #10827. This particular case was probably exacerbated by the large number of dependency relationships involved in gnome, and quite possibly also by duplicate dependency entries (#8763).
FYI, a dependency build list might also be useful for solving the uninstall problem described in #8431 (two years old, and once scheduled for 1.4).