Summary: | >=sys-apps/systemd-197: stabilize in order to unmask USE="systemd" for polkit, upower, udisks and others | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christoph Brill (egore) (RESIGNED) <egore> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | alexander, arne.flagge, egorov_egor, nikoli, pacho, radist.morse |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=447090 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 457568 | ||
Bug Blocks: |
Description
Christoph Brill (egore) (RESIGNED)
2012-10-21 08:27:02 UTC
As a sidenote: I don't have consolekit installed anymore, so I'm sure that polkit picks systemd. You can use /etc/portage/profile/use.mask entry of: -systemd consolekit That should unmask the flag in global basis, and you could mask consolekit with it... To unmask the flag, systemd would have to be stabilized first, for KEYWORDS to match. I don't know the status of systemd stabilization. Let's ask the maintainers. @systemd: How do you want to handle this? (In reply to comment #3) > @systemd: How do you want to handle this? That's a hard question. Nobody requested systemd stable yet, so I didn't consider it. I'm not running any stable system myself so I'm not sure how it works there. One issue I see is that it would be hard to find a good systemd version with at least those 30 days of lifetime. Although -194 is free of bugs known to me so far, it's quite fresh. At the same time I'm afraid that older versions had some minor issues. The other issue is that we'd have to have the corresponding udev stable first. As far as I'm aware, people are not really happy with them (mostly due to the firmware loading conflict with Linus). @udev folks, do you have anything to add? Masked USE=systemd for sys-power/upower too since it's going stable now, expecting it to be masked for a lot more as time goes by *** Bug 438696 has been marked as a duplicate of this bug. *** (In reply to comment #5) > Masked USE=systemd for sys-power/upower too since it's going stable now, > expecting it to be masked for a lot more as time goes by Then adding the -systemd to the use.mask should become the official recommendation for the systemd users. Otherwise they'll end up with broken system. @Michał Górny: You're the author of the official systemd installation guide, can you mention it there? (In reply to comment #5) > Masked USE=systemd for sys-power/upower too since it's going stable now, > expecting it to be masked for a lot more as time goes by Please do not mask flags like that. Please do fork (revbump) ebuilds instead, and remove the flag from the to-go-stable ebuild, leaving it in the eternally-testing revbump. It's not great, it's hell of additional work, but it's what can work now. If you believe things shouldn't work like that, feel free to try to support bug 447090 which people seem to ignore. depends on bug (In reply to comment #9) > depends on bug Er, the bug is about newer udev version. If it helps, I normally run a stable base system. I have added the following packages to package.keywords in my conversion to systemd; most of them are due to blockers on udev. net-wireless/bluez sys-apps/hwids sys-apps/systemd sys-apps/dbus sys-apps/shadow sys-auth/pambase sys-fs/lvm2 sys-fs/udev sys-fs/udev-init-scripts sys-libs/gpm virtual/udev sys-fs/udisks sys-apps/baselayout Is this still necessary when USE=systemd is stable-masked? There are 2 critical bugs which need to be fixed before stabilization of systemd. lvm support is very important imho. bug 453594 bug 451452 Well, I think the major reason for quick stabilization has been fixed and there's no need for it to go stable now. If someone would really want for systemd to go stable, I think we should set some kind of plan ;). (In reply to comment #14) > Well, I think the major reason for quick stabilization has been fixed and > there's no need for it to go stable now. If someone would really want for > systemd to go stable, I think we should set some kind of plan ;). Do you mean the new package.use.stable support? Yet we have entry/entries like this in tree? What to do with them? Some are with # and some without. Not entirely clear to me how to unmask USE=systemd for an package only for ~arch so that it can also be stabilized without repoman complaining... # Robert Piasek <dagger@gentoo.org> (26 Apr 2012) # Packages with optional systemd support. Masked in base and unmasked on arches # where sys-apps/systemd is available. # Samuli Suominen <ssuominen@gentoo.org> (07 Sep 2012) # Masked again because this was never allowed before systemd is marked stable. #sys-auth/polkit -systemd (sorry for the reopen but profiles/ needs to be handled based on ^above) *** This bug has been marked as a duplicate of bug 465870 *** |