From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Date: Sun, 07 Jan 2018 13:39:59 +0100 [thread overview]
Message-ID: <2377664.vnCB3aCcJc@thetick> (raw)
In-Reply-To: <m3fu849fq9.wl-covici@ccs.covici.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Am Donnerstag, 21. Dezember 2017, 18:02:22 CET schrieb John Covici:
> I have been doing explicit packages as stated in another thread here
> and I just delete all the lines before the one that fails. I did not
> want to use --keep-going because I really did want to fix things as
> they came up, in case they might effect some packages further down on
> the list. What I did was to do
> emerge -ep @world | awk '/ebuild/ {print "="$4}' >a
>
> Once I had that a file, I just put emerge -1a before the first line
> and put \ at the end of each line and I was off to the slow races!
> Its been about a week with the bugs I had to research and the ebuilds
> I had to patch, etc. but its going now and there is only 1-200
> packages to go out of 1500 or so.
Fair enough, I suppose I've simply been overly irritable lately.
Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-07 12:40 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 [this message]
2017-12-21 17:13 ` Jörg Schaible
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=2377664.vnCB3aCcJc@thetick \
--to=marcec@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