| 1 |
On 06/22/2016 12:31 PM, Neil Bothwick wrote: |
| 2 |
> On Wed, 22 Jun 2016 08:39:59 -0500, Dan Douglas wrote: |
| 3 |
>> --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when |
| 4 |
>> that fails for whatever reason, --resume (with or without |
| 5 |
>> --skip-first) always fails too. |
| 6 |
> On 06/22/2016 12:31 PM, Neil Bothwick wrote: |
| 7 |
> That makes sense, --keep-going has already made sure that all updates |
| 8 |
> that are not dependant on the failing one have emerged, so there's |
| 9 |
> nothing left to emerge until you fix the broken package. |
| 10 |
|
| 11 |
|
| 12 |
That's what it should do but it clearly doesn't quite work that way. |
| 13 |
It's easy to prove it's broken by finding any package on the resume list |
| 14 |
that can merge on its own without pulling in a previously failed package. |
| 15 |
|
| 16 |
I've had completely up-to-date systems where no possible failure could |
| 17 |
result in an unsatisfied dependency and portage refuses to resume an |
| 18 |
`emerge -e @world` with hundreds of possible packages on the resume list |
| 19 |
that would work in isolation. That's the problem. |
Archives