|Summary:||sys-apps/systemd-201 stabilization request|
|Product:||Gentoo Linux||Reporter:||Michał Górny <mgorny>|
|Component:||[OLD] Keywording and Stabilization||Assignee:||Gentoo systemd Team <systemd>|
|Severity:||enhancement||CC:||alexander, arne.flagge, egore, egorov_egor, franz.trischberger, nikoli, rorgoroth|
|Package list:||Runtime testing required:||---|
|Bug Depends on:||453086, 469668, 469836|
Description Michał Górny 2013-04-14 08:58:11 UTC
@systemd, please do not remove this ebuild, if nothing new pops up, it will be our first stable target in, say, 14 days.
Comment 1 Franz Trischberger 2013-04-14 16:09:14 UTC
How will all those missing Units be handled? I tried to switch to systemd and was left with a barely functional laptop: no network, no sshd, no cups, ...). I did not try testing ebuilds (cups-1.6, openssh-6.*), if they offer systemd unit files. If they do will they get stabilized before systemd? When I tried systemd the last time (january this year, I think) all was working, seems through init-files. But now they don't work: # /etc/init.d/cupsd start * WARNING: cupsd is already starting And nothing happens...
Comment 2 Mike Gilbert 2013-04-14 16:27:16 UTC
net-misc/openssh-5.9_p1-r4 is stable and installs systemd units. net-print/cups-1.5.3 seems to have full systemd support; just needs a stablereq. I have a number of other packages in /etc/portage/package.keywords/systemd; I'll file some stablereq bugs and make them block this.
Comment 3 Michał Górny 2013-04-14 16:34:10 UTC
(In reply to comment #1) > How will all those missing Units be handled? I tried to switch to systemd > and was left with a barely functional laptop: no network, no sshd, no cups, > ...). I did not try testing ebuilds (cups-1.6, openssh-6.*), if they offer > systemd unit files. If they do will they get stabilized before systemd? The 'missing units' will be handled on their own manner. For quite a long time, a number of people are successfully using systemd on their stable systems. The main goal of stablereq is to help those people by having a known, well-working systemd version. Units are somehow tangential to this. We will still work on improving the situation but missing unit in package B shouldn't really matter on stabilizing loosely related package A which is systemd. > When I tried systemd the last time (january this year, I think) all was > working, seems through init-files. But now they don't work: > # /etc/init.d/cupsd start > * WARNING: cupsd is already starting > > And nothing happens... You aren't really supposed to launch openrc scripts when using systemd... systemctl start cups.service, but you should really read some docs or guides on how to use systemd if you want to use it.
Comment 4 Franz Trischberger 2013-04-15 08:55:01 UTC
@Mike: Thx! I usually first look for a systemd-USE-Flag, then search by "cave contents <pkg> | grep systemd", so there probably was a typo when doing so for openssh. cups from ~amd64 also works fine with systemd now. @Michał: I thought it was clear from the context that I am talking about packages NOT delivering systemd-Units. systemd-docs, Gentoo-docs etc. mention a compatibility with init files. I also read several posts about "easy migration" to system with "ExecStart=/etc/init.d/<service> start". So I thought this really should work.
Comment 5 Michał Górny 2013-05-13 08:40:14 UTC
Arches, please stabilize -201. This one's in sync with current ebuilds, hasn't seen issues and is mature enough.
Comment 6 Agostino Sarubbo 2013-05-13 10:02:15 UTC
I can't boot with systemd for each arches, so, if for you a compile test is enough, I can go ahead.
Comment 7 Samuli Suominen 2013-05-13 13:14:09 UTC
*** Bug 439130 has been marked as a duplicate of this bug. ***
Comment 8 Michał Górny 2013-05-13 13:34:11 UTC
(In reply to comment #6) > I can't boot with systemd for each arches, so, if for you a compile test is > enough, I can go ahead. It should be enough.
Comment 9 Tomáš "tpruzina" Pružina (amd64 [ex]AT) 2013-05-15 16:21:14 UTC
What about these udev blockages? Shouldn't virtual/udev support systemd as udev implementation?
Comment 10 Michał Górny 2013-05-15 18:09:39 UTC
(In reply to comment #9) > What about these udev blockages? Shouldn't virtual/udev support systemd as > udev implementation? The virtual does support systemd.
Comment 11 Damien Granger 2013-05-15 18:39:20 UTC
Maybe this bug should depend on https://bugs.gentoo.org/show_bug.cgi?id=424637 shouldn't it? Because of bug 424637 systemd can't boot a root-on-lvm system correctly, if I understand it well.
Comment 12 Enrico Tagliavini 2013-05-16 08:08:38 UTC
(In reply to comment #11) > Maybe this bug should depend on > https://bugs.gentoo.org/show_bug.cgi?id=424637 shouldn't it? > > Because of bug 424637 systemd can't boot a root-on-lvm system correctly, if > I understand it well. There is also bug #453594 about lvm. Fixing genkernel alone is not enough, the lvm2 ebuild must be changed to install the systemd stuff [included in the upstream package and just not installed on gentoo ATM]. An alternative to genkernel is dracut
Comment 13 Agostino Sarubbo 2013-05-20 11:53:44 UTC
(In reply to comment #6) > I can't boot with systemd for each arches, so, if for you a compile test is > enough, I can go ahead. I had a chance to test it in a real system. I played with it for few days, it works well. We know that are missing some unit files but systemd itself is fine. I'd prefer to resolve the kdebase-pam stabilization before this.
Comment 14 Fabio Erculiani (RETIRED) 2013-05-20 11:56:31 UTC
You can use sys-kernel/genkernel-next if you need a working initramfs able to boot systemd+lvm properly. Make sure to call genkernel with --udev. It also supports plymouth (--plymouth), since fbsplash and systemd don't play nice together. You can't use mdev in the initramfs if you boot with systemd and use LVM.
Comment 15 Damien Granger 2013-05-23 16:48:42 UTC
I managed to boot several amd64 boxes using systemd. No problem on Xfce or Gnome 3, can't log into kdm though (problem with system bus, did not dig into it, it may be related to pam or consolekit, I don't really use this system ATM). I had to use genkernel-next for udev inclusion in initramfs. Maybe this one should also get stablereq'ed or included in core genkernel. Other than this, I can say I have two stable environments using systemd (with bits of systemd-love overlay for lvm2 ebuild and lightdm service file), both on amd64.
Comment 16 Agostino Sarubbo 2013-05-25 20:18:47 UTC
Comment 17 Tomáš "tpruzina" Pružina (amd64 [ex]AT) 2013-05-26 03:24:37 UTC
amd64: ok (with respect to comments below) ^kdm log support: systemd-system.conf supports "syslog-or-kmsg" or "kmsg" log target which should work fine (not set by default) several .service files are missing (compared to fedora, arch), but this should not stop stabilization.
Comment 18 Agostino Sarubbo 2013-06-30 19:54:21 UTC
Comment 19 Agostino Sarubbo 2013-06-30 19:54:34 UTC
Comment 20 Agostino Sarubbo 2013-07-04 13:43:42 UTC
ppc64 stable. Last arch, closing
Comment 21 Nikoli 2013-07-04 14:04:05 UTC
Why you did not remove USE systemd from profiles/eapi-5-files/use.stable.mask ?