[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On 2017-12-18, John Blinka wrote: > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards > wrote: >> >> How do I skip grub and continue? > > > emerge --skipfirst --resume Thanks, I just seconds ago finally tumbled across that in Google. Oddly, the failing package (grub:0) wasn't the first one: it was about 5-6 packags down the list. So I used --exclude instead. We'll see how far that gets... -- Grant
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On 2017-12-18, Grant Edwards wrote: > On 2017-12-18, John Blinka wrote: >> On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards >> wrote: >> >>> How do I skip grub and continue? >> >> emerge --skipfirst --resume [...] > Oddly, the failing package (grub:0) wasn't the first one: it was about > 5-6 packags down the list. So I used --exclude instead. We'll see > how far that gets... It took a couple days, but after "resuming" the emerge three times, it finished. The three failures were grub:0, matplotlib, and crrcsim. Each time the failed package was around 5th on the list when I did a resume. And, each time emerge insisted on rebuilding gcc and glibc first. [I don't remember what else preceded the failed packages when I did the resumes.] I think I'll postpone upgrading to profile 17 on my "real work" computers where I have a lot more packages installed. -- Grant Edwards grant.b.edwardsYow! I hope something GOOD at came in the mail today so gmail.comI have a REASON to live!!
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Hi, Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka: > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards > 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. > I had to do that several times in my 17.0 upgrades. Maybe more times than necessary ;-) Cheers, Jörg
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
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 >> > >> > 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
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On 2017-12-21, Marc Joliet wrote: > Really, sometimes I wonder why I keep seeing people on this list who > clearly haven't heard of the --keep-going option. I know about the option and choose not to use it. I don't want it to "keep going" until I've looked at what failed and why. > It's there for a reason. And don't tell me anybody actually *likes* > having to manually continue the emerge process, because that's just > so, so tedious. You think manually controlling things is "tedious" and you run Gentoo? -- Grant
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Grant Edwards wrote: > On 2017-12-18, John Blinka wrote: >> On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards >> wrote: >>> How do I skip grub and continue? >> >> emerge --skipfirst --resume > Thanks, I just seconds ago finally tumbled across that in Google. > > Oddly, the failing package (grub:0) wasn't the first one: it was about > 5-6 packags down the list. So I used --exclude instead. We'll see > how far that gets... > > -- > Grant > You tried it and it does work with --exclude. lol Now we know. ;-) Dale :-) :-)
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Grant Edwards wrote: > On 2017-12-18, Grant Edwards wrote: >> On 2017-12-18, John Blinka wrote: >>> On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards >>> wrote: >>> How do I skip grub and continue? >>> emerge --skipfirst --resume > [...] > >> Oddly, the failing package (grub:0) wasn't the first one: it was about >> 5-6 packags down the list. So I used --exclude instead. We'll see >> how far that gets... > It took a couple days, but after "resuming" the emerge three times, it > finished. The three failures were grub:0, matplotlib, and crrcsim. > > Each time the failed package was around 5th on the list when I did a > resume. And, each time emerge insisted on rebuilding gcc and glibc > first. [I don't remember what else preceded the failed packages when > I did the resumes.] > > I think I'll postpone upgrading to profile 17 on my "real work" > computers where I have a lot more packages installed. > I'm not sure why or what all this involves but there is a thread on -dev about a 17.1 profile coming at some point. One may want to consider waiting to do to much for that. Some of the messages make it seem to be a really large process to upgrade to it. I'm hoping some or even most of it is just the devs testing things. o_O Just a thought. Dale :-) :-)
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On K, 2017-12-20 at 17:28 -0600, Dale wrote: > Grant Edwards wrote: > > On 2017-12-18, Grant Edwards wrote: > > > On 2017-12-18, John Blinka wrote: > > > > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards > > > > wrote: > > > > > > > > > How do I skip grub and continue? > > > > emerge --skipfirst --resume > > [...] > > > > > Oddly, the failing package (grub:0) wasn't the first one: it was > > > about > > > 5-6 packags down the list. So I used --exclude instead. We'll > > > see > > > how far that gets... > > It took a couple days, but after "resuming" the emerge three times, > > it > > finished. The three failures were grub:0, matplotlib, and crrcsim. > > > > Each time the failed package was around 5th on the list when I did > > a > > resume. And, each time emerge insisted on rebuilding gcc and glibc > > first. [I don't remember what else preceded the failed packages > > when > > I did the resumes.] > > > > I think I'll postpone upgrading to profile 17 on my "real work" > > computers where I have a lot more packages installed. > > > > > I'm not sure why or what all this involves but there is a thread on > -dev > about a 17.1 profile coming at some point. One may want to consider > waiting to do to much for that. Some of the messages make it seem to > be > a really large process to upgrade to it. I'm hoping some or even > most > of it is just the devs testing things. o_O > > Just a thought. It's about making /usr/lib not be a symlink to lib64 anymore on amd64. I wouldn't wait for it, could get complicated and messy to do both at once. If 17.1 pans out (or well, maybe "18.0" when going out of experimental testing phase next year..), it won't need a full rebuild, at most only things that have /usr/lib/ entries (instead of /usr/lib64 or /usr/lib32) in portage CONTENTS file in VDB to fix those things up after the migration tool. And I don't see anything overeager in --depclean. Maybe a dependency was removed later, so with still default "--dynamic-deps y" you get them removed now. If this breaks something, then there's an automagic dep involved (which should have a bug report and be fixed), or some changes done to some ebuild without proper revbump. I think --with-bdeps toggling might let it remove build-time only deps, though. I didn't observe that being used in the thread here in a way that lets these build-time only deps get removed, for that to be it.
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
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 > > > > 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? > > I had to do that several times in my 17.0 upgrades. > > Maybe more times than necessary ;-) Really, sometimes I wonder why I keep seeing people on this list who clearly 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 emerge process, because that's just so, so tedious. > Cheers, > Jörg Greetings -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On Thu, 21 Dec 2017 07:00:47 -0500,
Marc Joliet wrote:
>
> [1 ]
> [1.1 ]
> [1.2 ]
> 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
>
> > >
>
> > > 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?
>
> > > I had to do that several times in my 17.0 upgrades.
>
> >
>
> > Maybe more times than necessary ;-)
>
> Really, sometimes I wonder why I keep seeing people on this list who clearly
> 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 emerge
> process,
> because that's just so, so tedious.
>
> > Cheers,
>
> > Jörg
>
> Greetings
>
> --
>
> Marc Joliet
>
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.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
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
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Am Donnerstag, 21. Dezember 2017, 18:13:21 CET schrieb Jörg Schaible: > 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 > >> > > >> > 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 ... Ah, but I *don't* use "--resume --skipfirst", so I'm in the clear :-) . But if this is truly something that happens, have you filed a bug yet (if you haven't done so already)? Greetings -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup signature.asc Description: This is a digitally signed message part.
