public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge world
Date: Tue, 24 Apr 2007 11:06:11 +0100	[thread overview]
Message-ID: <20070424110611.02d20db7@hactar.digimed.co.uk> (raw)
In-Reply-To: <200704240430.49744.bss03@volumehost.net>

[-- Attachment #1: Type: text/plain, Size: 795 bytes --]

On Tue, 24 Apr 2007 04:30:43 -0500, Boyd Stephen Smith Jr. wrote:

> > From time to time an emerge world fails to update every possible
> > package because of a failure with one that causes the whole process
> > to fail. I remember reading about a tool which would continue to
> > upgrade/install packages whether some failed or not and then pipe the
> > list of problematic packages to a file. Does anyone know what the the
> > name of that tool is or any other tool that might have a similar
> > behavior to the one I just described?  
> 
> emerge <options> world || until emerge --resume --skipfirst; do :; done

Add "; emerge <options> -p world" to the end and you'll also get a list of
the packages that failed.


-- 
Neil Bothwick

Top Oxymorons Number 31: Small crowd

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-04-24 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24  9:30 [gentoo-user] Re: emerge world Boyd Stephen Smith Jr.
2007-04-24 10:06 ` Neil Bothwick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-28 13:06 [gentoo-user] " Arnau Bria
2007-09-28 13:25 ` [gentoo-user] " Alexander Skwar
2007-09-28 15:01   ` Steve Dommett
2007-09-28 15:50   ` Arnau Bria
2007-09-28 15:57     ` Steve Dommett
2007-09-28 16:21       ` Arnau Bria
2007-09-28 16:38         ` Steve Dommett
2007-10-01 18:53           ` Arnau Bria

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070424110611.02d20db7@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox