Re: [gentoo-user] emerge -e and --resume
On Fri, Jan 05 2018, Daniel Frey wrote: > On 01/05/18 18:50, allan gottlieb wrote: >> On Fri, Jan 05 2018, Daniel Frey wrote: >> >>> On 01/05/18 13:15, Neil Bothwick wrote: On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: > I am finally moving my production machine the the 17.0 profile. > Currently running is > > emerge -e --keep-going @world > > So far there is one failure (libcryptui, the fix is easy). > > Am I correct that when the above emerge completes, I should run > simply > > emerge --resume If the emerge has completed, there is nothing to resume. Just make a note of the packages that failed to build ans emerge --oneshot them, with any necessary fixes. >>> >>> You may also want to check for dependencies (as in: `equery depends >>> ` and rebuild the dependencies of the failed package as well. >>> >>> Dan >> >> I don't understand. If the dependencies didn't fail, why should I >> rebuild them? >> >> thanks, >> allan >> > > If you're transitioning over to the new profile, that means the > dependencies would be built and linked to the old profile's > binaries. This was merely a suggestion, as I've had some mighty > strange things happen after upgrades to gcc in the past, all solved by > `emerge -e > world`, although... I didn't have packages fail back then. > > When I switched over to the 17 profile I had one rebuild failure, and > it didn't have any direct dependencies fail. > > Dan Now I understand that you mean packages that depend on failed builds. I was mistakenly thinking of packages on which the failed build depends. You are right and thanks again. allan
Re: [gentoo-user] emerge -e and --resume
On Sat, 06 Jan 2018 09:40:32 +, Peter Humphrey wrote: > > > If the emerge has completed, there is nothing to resume. Just make a > > > note > > > of the packages that failed to build ans emerge --oneshot them, > > > with any necessary fixes. > > > > Thank you. So far (only 104 to go) just the one failure. Will the > > emerge --keep-going > > print a list of failed pkgs at the end? > > Yes, it will; it'll give you the same output from each failure as you > would have got separately. It will also include any reverse dependencies (I think this is what Dan was getting at) that were skipped because a package failed to build. -- Neil Bothwick At any event, the people whose seats are furthest from the aisle arrive last. pgpGLNEfevDgf.pgp Description: OpenPGP digital signature
Re: [gentoo-user] emerge -e and --resume
On Saturday, 6 January 2018 02:49:53 GMT allan gottlieb wrote: > On Fri, Jan 05 2018, Neil Bothwick wrote: > > On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: > >> I am finally moving my production machine the the 17.0 profile. > >> Currently running is > >> > >> emerge -e --keep-going @world > >> > >> So far there is one failure (libcryptui, the fix is easy). > >> > >> Am I correct that when the above emerge completes, I should run > >> simply > >> > >> emerge --resume > > > > If the emerge has completed, there is nothing to resume. Just make a > > note > > of the packages that failed to build ans emerge --oneshot them, with any > > necessary fixes. > > Thank you. So far (only 104 to go) just the one failure. Will the > emerge --keep-going > print a list of failed pkgs at the end? Yes, it will; it'll give you the same output from each failure as you would have got separately. -- Regards, Peter.
Re: [gentoo-user] emerge -e and --resume
On 01/05/18 18:50, allan gottlieb wrote: On Fri, Jan 05 2018, Daniel Frey wrote: On 01/05/18 13:15, Neil Bothwick wrote: On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: I am finally moving my production machine the the 17.0 profile. Currently running is emerge -e --keep-going @world So far there is one failure (libcryptui, the fix is easy). Am I correct that when the above emerge completes, I should run simply emerge --resume If the emerge has completed, there is nothing to resume. Just make a note of the packages that failed to build ans emerge --oneshot them, with any necessary fixes. You may also want to check for dependencies (as in: `equery depends ` and rebuild the dependencies of the failed package as well. Dan I don't understand. If the dependencies didn't fail, why should I rebuild them? thanks, allan If you're transitioning over to the new profile, that means the dependencies would be built and linked to the old profile's binaries. This was merely a suggestion, as I've had some mighty strange things happen after upgrades to gcc in the past, all solved by `emerge -e world`, although... I didn't have packages fail back then. When I switched over to the 17 profile I had one rebuild failure, and it didn't have any direct dependencies fail. Dan
Re: [gentoo-user] emerge -e and --resume
On Fri, Jan 05 2018, Neil Bothwick wrote: > On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: > >> I am finally moving my production machine the the 17.0 profile. >> Currently running is >> >> emerge -e --keep-going @world >> >> So far there is one failure (libcryptui, the fix is easy). >> >> Am I correct that when the above emerge completes, I should run >> simply >> >> emerge --resume > > If the emerge has completed, there is nothing to resume. Just make a note > of the packages that failed to build ans emerge --oneshot them, with any > necessary fixes. Thank you. So far (only 104 to go) just the one failure. Will the emerge --keep-going print a list of failed pkgs at the end? thanks again, allan
Re: [gentoo-user] emerge -e and --resume
On 01/05/18 13:15, Neil Bothwick wrote: On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: I am finally moving my production machine the the 17.0 profile. Currently running is emerge -e --keep-going @world So far there is one failure (libcryptui, the fix is easy). Am I correct that when the above emerge completes, I should run simply emerge --resume If the emerge has completed, there is nothing to resume. Just make a note of the packages that failed to build ans emerge --oneshot them, with any necessary fixes. You may also want to check for dependencies (as in: `equery depends ` and rebuild the dependencies of the failed package as well. Dan
Re: [gentoo-user] emerge -e and --resume
On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: > I am finally moving my production machine the the 17.0 profile. > Currently running is > > emerge -e --keep-going @world > > So far there is one failure (libcryptui, the fix is easy). > > Am I correct that when the above emerge completes, I should run > simply > > emerge --resume If the emerge has completed, there is nothing to resume. Just make a note of the packages that failed to build ans emerge --oneshot them, with any necessary fixes. -- Neil Bothwick SITCOM: Single Income, Two Children, Oppressive Mortgage pgp7pyrRpZVGo.pgp Description: OpenPGP digital signature
[gentoo-user] emerge -e and --resume
I am finally moving my production machine the the 17.0 profile. Currently running is emerge -e --keep-going @world So far there is one failure (libcryptui, the fix is easy). Am I correct that when the above emerge completes, I should run simply emerge --resume Thanks, allan PS in make.conf I have EMERGE_DEFAULT_OPTS="--ask --deep --tree --jobs --load-average=5" MAKEOPTS="--jobs=8 --load-average=5"
[gentoo-user] emerge -e world / --resume
If I do an emerge -e world , and interrupt it, will I be able to --resume it? Including after a reboot? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -e world / --resume
On Mon, 12 Sep 2005 14:43:31 -0400, fire-eyes wrote: If I do an emerge -e world , and interrupt it, will I be able to --resume it? Including after a reboot? Yes. -- Neil Bothwick ABORT: Drivel filter is compromised! pgp4hmfp5UyID.pgp Description: PGP signature
