[arch-dev-public] systemd - move to base group and expect it to be installed?

[andyrtr at archlinux.org]

Morning.

I've cleaned systemd-sysvcompat long time ago from all my systems. I didn't know it is still alive and is meant to pull in main systemd.

Lately cups-filters failed to install when building in a clean chroot due to missing "lp" group. Having systemd-sysvcompat in base should have pulled in systemd and allow "lp" group creation. Maybe this is another trigger of the systemd bug.
We should continue talking on the list. Maybe we should stop splitting systemd and simply make it part of "base" group to make sure all Arch users have all its parts installed.

-Andy

> Sébastien Luttringer <seblu at seblu.net> hat am 12. September 2017 um 22:14 geschrieben:
>
>
> On Tue, 2017-09-12 at 22:09 +0200, Andreas Radke wrote:
> > Am Tue, 12 Sep 2017 22:02:54 +0200
> > schrieb Sébastien Luttringer <seblu at seblu.net>:
> >
> > > Hello,
> > >
> > > Systemd is in the base group since October 2012. Not sure to
> > > understand if your problem is about base or base-devel.
> > > Most of our packages moved to systemd-sysusers. Would make sense to
> > > not have filesystem do the same?
> > >
> > > Regards,
> >
> > It's in the core repo but not in "base" group.
> >
> > root at laptop64:/root # LANG=C pacman -Qi systemd | grep Groups
> > Groups : base-devel
> >
> > And chroots and Arch installation media simply install the full base
> > group. So far systemd is not included and we now have a problem with
> > user/group creation.
>
> systemd-sysvcompat is in base group, and it pulls systemd.Do a pacstrap, you
> will see systemd installed.
> Devtools use base-devel, which prevent linux or others non necessary packages
> to be pulled to only build packages.
>
> Sébastien "Seblu" Luttringer
>