On Thu, Jun 04, 2009 at 06:30:37PM +0100, Neil Bothwick wrote:
> On Thu, 4 Jun 2009 09:55:59 -0700, fe...@crowfix.com wrote:
>
> > and it picks up the same several day old failed emerge instead of the
> > one it was running.
>
> Try "emaint -f cleanresume"
Same result. emain did something, but
On Thu, 4 Jun 2009 09:55:59 -0700, fe...@crowfix.com wrote:
> and it picks up the same several day old failed emerge instead of the
> one it was running.
Try "emaint -f cleanresume"
--
Neil Bothwick
A computer without Microsoft is like a chocolate cake without mustard.
signature.asc
Descrip
fe...@crowfix.com wrote:
> On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
>
>> On Thu, Jun 4, 2009 at 11:02 AM, 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
On Thu, Jun 04, 2009 at 09:18:14AM -0700, fe...@crowfix.com wrote:
> On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
> > On Thu, Jun 4, 2009 at 11:02 AM, wrote:
> > > I have a shell script which loops on failure from emerge to use
> > > --skipfirst --resume to continue as much as po
On Thu, Jun 4, 2009 at 11:18 AM, wrote:
> Good grief. That's *zackly* what I have wanted for a long time. When
> did it get added?
>From bug 12768 it looks like it was added by Zac Medico on 2008-06-27 :)
On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
> On Thu, Jun 4, 2009 at 11:02 AM, 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 emerg
On Thu, Jun 4, 2009 at 11:02 AM, 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 tha
On Thu, Jun 04, 2009 at 09:02:21AM -0700, Penguin Lover fe...@crowfix.com
squawked:
> I have a shell script which loops on failure from emerge to use
> --skipfirst --resume to continue as much as possible.
May I suggest using the --keep-going option for emerge to do what you
want to do instead
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 start
9 matches
Mail list logo
