Re: Re: Systemd getting in the way

On Sunday, 8 March 2026 16:46:13 CET [email protected] wrote:
> I've had to abandon my favourite systemd-boot, having been unable to get it
> to work (it doesn't behave the way the handbook describes). Instead, I've
> had to fall back on the dreaded grub.
> 
> The point of this gripe, though, is that I cannot run an 'emerge -e @world'
> any more, because systemd insists on being included. Well, being masked
> stops it, but being explicitly excluded on the command line does not.

What's the issue you're having with systemd-boot?

On Monday, 9 March 2026 01:14:53 CET Peter Humphrey wrote:
> $ eselect profile show
> Current /etc/portage/make.profile symlink:
>   default/linux/amd64/23.0/desktop/plasma

If you're using the systemd profile, it should pull in sys-apps/systemd. But 
since you're *not* using the systemd profile, you should get systemd-boot from 
sys-apps/systemd-utils and systemd should not be pulled in the first place. So 
FWIW I don't think this has to do with systemd-boot.

Are you perhaps switching from the systemd profile to the non-systemd profile 
here?

On Sunday, 8 March 2026 17:37:31 CET [email protected] wrote:
> I didn't get a tree, just the usual block of packages that were supposed to
> require systemd. This was the block:
> 
> !!! All ebuilds that could satisfy "sys-apps/systemd:0/2=" have been masked.
> !!! One of the following masked packages is required to complete your
> request:

Try removing the package.mask entry and then re-running emerge -pcv systemd.

--
Cheers,
Katalin

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQRZnaWI8gLWxkaKIHnv4LcrvDUVFwUCaa4WNhsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQ7+C3K7w1FReWaAEAoepjpe5ZFuOAcwtIkaLg
ylIOG7NjzChJenTnU2ooIuEA/RqnskYnFB1OwxEEzj84ivd9Nu4D1i8KKOwoJMro
iAMC
=AsDa
-----END PGP SIGNATURE-----