Bug #2030
your-initfreedom conflicts systemd-dummy
100%
Description
Hello,
I am migrating from systemd to OpenRC, and many applications (including octopi) don't work without some flavour of systemd. I tried to install systemd-dummy, but I would like to make sure that systemd is not installed. I thought of installing your-initfreedom, but it conflicts with systemd-dummy. I was trying to update my system, and it is trying to install systemd- packages (systemd-nss-*). Is it fine to have those packages removed (with pacman -Rdds)?
Alternatively, should I keep systemd-libsystemd and other systemd- libraries?
History
Updated by josealberto4444 over 5 years ago
I can see this same behaviour happening in a fresh openrc installation. It conflicts with systemd-dummy and libsystemd-dummy, but those are dummy packages that (I think) should be excluded from the blacklist.
When trying to install your-initfreedom, it tries to remove {,lib}systemd-dummy and then a lot of dependencies are broken, like device-mapper, lvm2 and a lot of essential stuff, so there is no way to install your-initfreedom right now.
Updated by Megver83 over 5 years ago
- Assignee set to Megver83
The problem it that your-initfreedom conflicts anything that provides 'systemd' and 'libsystemd'.
I think that the best would be to conflict 'systemd-tools' (which is what systemd/notsystemd provides) and libsystemd.so (because 'libsystemd' is a metapackage, which separately installs systemd-libsystemd, which provides libsystemd.so).
And also re-add libsystemd-dummy, which was removed from the repos, or make systemd-dummy to provide libsystemd too.
Updated by Megver83 over 5 years ago
- % Done changed from 0 to 100
- Status changed from open to fixed
OK. I've added libsystemd-dummy and updated the blacklist accordingly (and also the package)
I tested it myself, and now your-initfreedom is completely usable.