From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9BBDE139083 for ; Thu, 21 Dec 2017 17:02:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9EE60E0FAB; Thu, 21 Dec 2017 17:02:24 +0000 (UTC) Received: from mail0157.smtp25.com (mail0157.smtp25.com [75.126.84.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 44349E0F1E for ; Thu, 21 Dec 2017 17:02:23 +0000 (UTC) Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id vBLH2MIJ025565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 21 Dec 2017 12:02:22 -0500 Received: (from covici@localhost) by ccs.covici.com (8.14.9/8.13.7/Submit) id vBLH2M3r025564; Thu, 21 Dec 2017 12:02:22 -0500 Date: Thu, 21 Dec 2017 12:02:22 -0500 Message-ID: From: John Covici To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails? In-Reply-To: <3361019.6EC3TbqQLz@thetick> References: <3361019.6EC3TbqQLz@thetick> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/25.3 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Organization: Covici Computer Systems Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-SpamH-Filter: d-out-001.smtp25.com-vBLH2MPU001571 X-SpamH-OriginatingIP: 70.109.53.110 X-Archives-Salt: 01d36a51-6529-4bec-88ab-4df430b1358a X-Archives-Hash: f5bfef7d370eb75df7af7ef610926819 On Thu, 21 Dec 2017 07:00:47 -0500, Marc Joliet wrote: >=20 > [1 ] > [1.1 ] > [1.2 ] > Am Donnerstag, 21. Dezember 2017, 10:45:41 CET schrieb J=F6rg Schaible: >=20 > > Hi, >=20 > >=20 >=20 > > Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka: >=20 > > > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards >=20 > > >=20 >=20 > > > wrote: >=20 > > >> How do I skip grub and continue? >=20 > > >=20 >=20 > > > emerge --skipfirst --resume >=20 > >=20 >=20 > > This is unfortunately really dangerous, because "emerge --resume" will >=20 > > recalculate the order of the outstanding packages and you have no guara= ntee >=20 > > that the first one will be the one that failed the last run. In that ca= se >=20 > > you skip an arbitrary package and you may increase your problems. >=20 > >=20 >=20 > > You can use --skipfirst only if you have restarted emerge with --resume= only >=20 > > and you have ensured that it will really continue with the failing pack= age. >=20 > > You may abort the build then with CTRL-C and restart emerge with both >=20 > > options. >=20 > That clashes with my understanding, so I looked it up, and it turns out I= was right. From emerge(1): >=20 > > --skipfirst >=20 > >=20 >=20 > > This option is only valid when used with --resume. It removes >=20 > > the first package in the resume list. Dependencies are >=20 > > recalculated for remaining packages and any that have >=20 > > unsatisfied dependencies or are masked will be automatically >=20 > > dropped. Also see the related --keep-going option. >=20 > Note the "remaining dependencies" part. Otherwise, what would be the poin= t of --skipfirst if it were so unpredictable? >=20 > > > I had to do that several times in my 17.0 upgrades. >=20 > >=20 >=20 > > Maybe more times than necessary ;-) >=20 > Really, sometimes I wonder why I keep seeing people on this list who clea= rly haven't heard of the --keep-going option. It's there for a reason. And = don't tell me anybody actually *likes* having to manually continue the emer= ge process, > because that's just so, so tedious. >=20 > > Cheers, >=20 > > J=F6rg >=20 > Greetings >=20 > --=20 >=20 > Marc Joliet >=20 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 "=3D"$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. --=20 Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici@ccs.covici.com