From: "Jörg Schaible" <joerg.schaible@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Date: Thu, 21 Dec 2017 17:13:21 +0000 (UTC) [thread overview]
Message-ID: <p1gq3h$s04$2@blaine.gmane.org> (raw)
In-Reply-To: 3361019.6EC3TbqQLz@thetick
Am Thu, 21 Dec 2017 13:00:47 +0100 schrieb Marc Joliet:
> Am Donnerstag, 21. Dezember 2017, 10:45:41 CET schrieb Jörg Schaible:
>> Hi,
>>
>> Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka:
>> > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards
>> >
>> > <grant.b.edwards@gmail.com> wrote:
>> >> How do I skip grub and continue?
>> >
>> > emerge --skipfirst --resume
>>
>> This is unfortunately really dangerous, because "emerge --resume" will
>> recalculate the order of the outstanding packages and you have no
>> guarantee that the first one will be the one that failed the last run.
>> In that case you skip an arbitrary package and you may increase your
>> problems.
>>
>> You can use --skipfirst only if you have restarted emerge with --resume
>> only and you have ensured that it will really continue with the failing
>> package. You may abort the build then with CTRL-C and restart emerge
>> with both options.
>
> That clashes with my understanding, so I looked it up, and it turns out
> I was right. From emerge(1):
>
>> --skipfirst
>>
>> This option is only valid when used with --resume. It
>> removes the first package in the resume list.
>> Dependencies are recalculated for remaining packages and
>> any that have unsatisfied dependencies or are masked will
>> be automatically dropped. Also see the related
>> --keep-going option.
>
> Note the "remaining dependencies" part. Otherwise, what would be the
> point of --skipfirst if it were so unpredictable?
Well, that's the difference between theory and practice. I've been bitten more than once, but you may do as
you want, it's your system ...
Cheers,
Jörg
next prev parent reply other threads:[~2017-12-21 17:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 16:00 [gentoo-user] How to resume 'emerge -e @world' after grub fails? Grant Edwards
2017-12-18 16:07 ` John Blinka
2017-12-18 16:14 ` [gentoo-user] " Grant Edwards
2017-12-18 16:45 ` Dale
2017-12-20 20:16 ` Grant Edwards
2017-12-20 23:28 ` Dale
2017-12-21 8:43 ` Mart Raudsepp
2017-12-21 9:45 ` Jörg Schaible
2017-12-21 12:00 ` Marc Joliet
2017-12-21 17:02 ` John Covici
2018-01-07 12:39 ` Marc Joliet
2017-12-21 17:13 ` Jörg Schaible [this message]
2018-01-07 12:41 ` Marc Joliet
2017-12-21 17:32 ` Grant Edwards
2017-12-18 16:14 ` [gentoo-user] " Dale
2017-12-18 17:55 ` Mick
2017-12-18 19:02 ` David Haller
2017-12-18 19:31 ` Francisco Ares
2017-12-18 20:05 ` David Haller
2017-12-18 22:49 ` Dale
2017-12-18 23:05 ` Adam Carter
2017-12-18 23:38 ` Dale
2017-12-19 3:06 ` David Haller
2017-12-19 4:03 ` Dale
2017-12-20 22:54 ` David Haller
2017-12-21 4:49 ` Dale
2017-12-19 5:51 ` Adam Carter
2017-12-19 9:15 ` Neil Bothwick
2017-12-19 15:45 ` Helmut Jarausch
2017-12-19 18:13 ` Bas Zoutendijk
2017-12-20 8:08 ` Helmut Jarausch
2017-12-20 22:27 ` David Haller
2017-12-19 17:45 ` Dale
2017-12-19 20:22 ` Neil Bothwick
2017-12-20 2:04 ` Adam Carter
2017-12-20 23:18 ` David Haller
2017-12-19 9:21 ` Neil Bothwick
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='p1gq3h$s04$2@blaine.gmane.org' \
--to=joerg.schaible@gmx.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