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
<package>` 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
