[gentoo-user] Skipping world rebuild with profile 23.0 upgrade?

[gentoo-user] Skipping world rebuild with profile 23.0 upgrade?

[Nikos Chantziaras]

So what happens if I skip the very last step in the profile 23.0 upgrade 
guide, which is:

6. Rebuild world:
    emerge --ask --emptytree @world

Is this just a security concern due to the new hardening flags, or are 
there ABI concerns?

Re: [gentoo-user] Skipping world rebuild with profile 23.0 upgrade?

[Michael Orlitzky]

On Tue, 2024-06-25 at 17:05 +0300, Nikos Chantziaras wrote:
> So what happens if I skip the very last step in the profile 23.0 upgrade 
> guide, which is:
> 
> 6. Rebuild world:
>     emerge --ask --emptytree @world
> 
> Is this just a security concern due to the new hardening flags, or are 
> there ABI concerns?
> 

I think this is akin to saying "reboot" rather than trying to carefully
describe how to restart every process on every running system.

You can probably get away with it, but at the risk of causing some
obscure issue that nobody will be able to help you with. It took me
three days of computer time to rebuild everything, but the subsequent
zero days of human time debugging was worth it (YMMV).

Re: [gentoo-user] Skipping world rebuild with profile 23.0 upgrade?

[Eli Schwartz]

[-- Attachment #1.1.1: Type: text/plain, Size: 951 bytes --]

On 6/25/24 10:05 AM, Nikos Chantziaras wrote:
> So what happens if I skip the very last step in the profile 23.0 upgrade
> guide, which is:
> 
> 6. Rebuild world:
>    emerge --ask --emptytree @world
> 
> Is this just a security concern due to the new hardening flags, or are
> there ABI concerns?


If you use the binhost packages built for profile 23.0 then you can
simply reinstall those without any compilation.

If your profile upgrade fell under the category of CHOST changes then
that's probably a worst-case scenario with regard to trying to skip an
emptytree rebuild. I would recommend NOT skipping the emptytree if you
are a musl / ppc64le / mips.

On other configurations this may be safe, but I still wouldn't skip it
unless you can describe exactly what changed and why you are confident
mixing old/new binaries is safe. Even then I strongly advise rebuilding
all toolchain-related packages.

-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]