On Thu, Jun 04, 2009 at 09:18:14AM -0700, [email protected] wrote:
> On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
> > On Thu, Jun 4, 2009 at 11:02 AM, <[email protected]> wrote:
> > > I have a shell script which loops on failure from emerge to use
> > > --skipfirst --resume to continue as much as possible. Every once in a
> > > while, it gets forgetful and picks up an emerge from several days
> > > previous to try to resume instead of the one that just failed. This
> > > is pretty annoying. It started several months ago, sporadically, and
> > > seems to be happening more and more often, but not always, and not in
> > > any pattern I can discern.
> > >
> > > This is sys-apps/portage-2.1.6.13 on ~amd64.
> >
> > It may be easier to use the --keep-going switch instead. It allows
> > emerge to continue emerging everything else (when possible) and
> > skipping unresolved dependencies caused by the failed merges.
>
> Good grief. That's *zackly* what I have wanted for a long time. When
> did it get added?
>
> I will certainly try that next merge. Heck, I might try the most
> recent one again anyway just to see miracles in action :-)
Unfortunately, it does exactly the same thing.
*** Resuming merge...
Calculating dependencies ..^H^H... done!
* One or more packages are either masked or have missing dependencies:
and it picks up the same several day old failed emerge instead of the
one it was running.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / [email protected]
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
