On 2026-03-11 01:38 AM, "Katalin Rebhan" <[email protected]> wrote:
> On Monday, 9 March 2026 03:19:39 CET Peter Humphrey wrote:
> > I was following the handbook to install a new system, but installing
> > systemd- utils seemed to require systemd as well. I've tried masking
> > systemd, and --excluding it on the command line, but to little avail, by
> > which I mean that the whole installation process seemed to revolve around
> > systemd.
>
> That doesn't make sense. systemd-utils specifically conflicts with systemd:
>
> RDEPEND="... !sys-apps/systemd"
>
> I don't know how you managed to get both installed at once.
>
> > > Try removing the package.mask entry and then re-running emerge -pcv
> > > systemd.
> >
> > I only put it in there to try to resolve the impasse.
>
> What does it say regardless? Does it still actually conflict? Systemd must
> have gotten installed in some configuration where it didn't conflict with
> anything, right? Can you still reproduce that so that you can e.g. run
> emerge -auDU @world without any dependency errors, and then retry
> emerge -pcv systemd?
>
> > I'm beginning to wonder about the hardware. You know: when all other
> > possibilities have been eliminated...
>
> It's most certainly not the hardware. I'd much rather pin it on some binpkgs
> oddity but I'm not familiar with those at all (can't use them since I'm
> running the LLVM profile). Might be another thing to try temporarily disabling
> until you've got this fixed to rule it out.
I think I was the victim of my own muddled thinking: I had conflicting USE flags. I got it right the second time.
A good night's sleep always helps. :)
--
Regards
Peter.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.