| 1 |
felix@×××××××.com wrote: |
| 2 |
> On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote: |
| 3 |
> |
| 4 |
>> On Thu, Jun 4, 2009 at 11:02 AM, <felix@×××××××.com> wrote: |
| 5 |
>> |
| 6 |
>>> I have a shell script which loops on failure from emerge to use |
| 7 |
>>> --skipfirst --resume to continue as much as possible. Every once in a |
| 8 |
>>> while, it gets forgetful and picks up an emerge from several days |
| 9 |
>>> previous to try to resume instead of the one that just failed. This |
| 10 |
>>> is pretty annoying. It started several months ago, sporadically, and |
| 11 |
>>> seems to be happening more and more often, but not always, and not in |
| 12 |
>>> any pattern I can discern. |
| 13 |
>>> |
| 14 |
>>> This is sys-apps/portage-2.1.6.13 on ~amd64. |
| 15 |
>>> |
| 16 |
>> It may be easier to use the --keep-going switch instead. It allows |
| 17 |
>> emerge to continue emerging everything else (when possible) and |
| 18 |
>> skipping unresolved dependencies caused by the failed merges. |
| 19 |
>> |
| 20 |
> |
| 21 |
> Good grief. That's *zackly* what I have wanted for a long time. When |
| 22 |
> did it get added? |
| 23 |
> |
| 24 |
> I will certainly try that next merge. Heck, I might try the most |
| 25 |
> recent one again anyway just to see miracles in action :-) |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
|
| 30 |
You can also add that option to make.conf so it will do it even if you |
| 31 |
forget to type it in. I did that a while back when I found out about it. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives