public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Heiko Baums <lists@baums-on-web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New profile 17: How urgent is the rebuild of world technically?
Date: Sun, 3 Dec 2017 15:36:58 +0100	[thread overview]
Message-ID: <20171203153658.488488d9@lexx> (raw)
In-Reply-To: <20171203140936.GA2375@inspiron.homenetwork>

Am Sun, 3 Dec 2017 09:09:37 -0500
schrieb "Spackman, Chris" <chris@osugisakae.com>:

> emerge --resume --skipfirst

`emerge --resume --skipfirst` is necessary if you don't use --keep-going
y, a package fails to build and you want to manually resume the actual
emerge. Not using --skipfirst wouldn't make much sense, because the
broken package will fail to build again anyway.

Maybe Dales suggestion would work here. In this case you shouldn't use
--skipfirst after fixing the reasons why the package failed to build.

If you run `emerge -e @world` e.g. and get a power failure then you
shouldn't use --skipfirst because then you want to build the package
which was currently built during the power failure again.

If you want to do have emerge doing a --resume --skipfirst
automatically then you should use --keep-going y in the original emerge
command like `emerge -e --keep-going y @world` or `emerge -uDN
--keep-going y @world`.

Heiko


  parent reply	other threads:[~2017-12-03 14:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03  2:15 [gentoo-user] New profile 17: How urgent is the rebuild of world technically? tuxic
2017-12-03  2:30 ` Michael Orlitzky
2017-12-03  2:32   ` Adam Carter
2017-12-03  2:44     ` Michael Orlitzky
2017-12-03  3:26   ` tuxic
2017-12-03  3:35     ` Heiko Baums
2017-12-03  3:45       ` tuxic
2017-12-03  4:15         ` Heiko Baums
2017-12-03  9:53           ` Peter Humphrey
2017-12-03 11:56             ` Heiko Baums
2017-12-03 12:55               ` Dale
2017-12-03 14:09                 ` Spackman, Chris
2017-12-03 14:16                   ` tuxic
2017-12-03 14:39                     ` Heiko Baums
2017-12-03 15:25                       ` Peter Humphrey
2017-12-03 15:57                       ` Neil Bothwick
2017-12-03 14:36                   ` Heiko Baums [this message]
2017-12-03 14:27                 ` Heiko Baums
2017-12-04  1:08                   ` Dale
2017-12-04  1:18                     ` Heiko Baums
2017-12-04  1:48                       ` Walter Dnes
2017-12-03  5:26         ` Adam Carter
2017-12-03 10:51         ` Neil Bothwick
2017-12-03  3:47     ` Heiko Baums
2017-12-06 23:59     ` Frank Steinmetzger
2017-12-07  8:08       ` Neil Bothwick
2017-12-04 17:48   ` Stefan G. Weichinger
2017-12-04 20:21     ` Michael Orlitzky
2017-12-05  9:16       ` Stefan G. Weichinger

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=20171203153658.488488d9@lexx \
    --to=lists@baums-on-web.de \
    --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