Bug #2556
Packaging Request #2506: arch introduced a base metapackage to replace the meta group
Housekeeping #2549: move non-systemd packages to [nonsystemd]
Conflict updating openrc - libelogind and systemd-libsystemd are in conflict
0%
Description
When trying to run pacman -Syu today (last -Syu was 2019-10-28), pacman asked to replace some packages with a version coming from nonsystemd (dbus service and binary, elogind, openrc and polkit), but after accepting all of them, it printed "libelogind and systemd-libsystemd are in conflict" (depended on by elogind and dbus-elogind, and systemd-libs-dummy respectively on my machine without upgrading). What is the reason for this conflict and is there a way to solve it?
:: Synchronizing package databases... nonprism is up to date nonsystemd is up to date libre is up to date core is up to date extra is up to date community is up to date pcr-testing is up to date pcr is up to date :: Starting full system upgrade... :: Replace dbus-elogind with nonsystemd/dbus? [Y/n] y :: Replace dbus-openrc with nonsystemd/dbus? [Y/n] y :: Replace kmod-openrc with nonsystemd/openrc? [Y/n] y resolving dependencies... looking for conflicting packages... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: libelogind and systemd-libsystemd are in conflict
History
Updated by bill-auger over 3 years ago
- Priority changed from bug to broken
- Assignee set to Megver83
megver made some changes recently to sort out initsystem conflicts; but they may not be complete
the original arrangement was troublesome - it allowed openrc to be installed while [nonsystemd] was not enabled; which led to openrc plus some parts of systemd being installed - thats what we are trying to sort out now
the plan is to make them mutually-exclusive - so that, from now on, [nonsystemd] will be mandatory in order to use openrc
- anyone using systemd, will need to ensure that [nonsystemd] is disabled
- anyone using openrc, who did not already have [nonsystemd] enabled, will need to enable it, and pacman -Syyuu may be required
this could be related to a similar bug report on the mailing list
https://lists.parabola.nu/pipermail/assist/2019-November/001442.html
in that instance, megver has advised to wait until this is sorted out better
Updated by bill-auger over 3 years ago
- Related to Packaging Request #2506: arch introduced a base metapackage to replace the meta group added
Updated by BetaRays over 3 years ago
I forgot to mention the machine where this happened did have [nonsystemd] enabled, which is why other packages were pulled from it to replace others. But the conflict still happened.
Updated by Megver83 over 3 years ago
Read about my plans here
I'm replacing all -elogind and some -openrc pkgs in [nonsystemd], so those replacements will have full elogind and openrc by default without having to install anything from [pcr]. I'll eventually deprecate/move stuff in [pcr] and publish a news about, but I still have to do more test, because after all of these I'll launch a new OpenRC ISO
Updated by bill-auger over 3 years ago
- Status changed from unconfirmed to confirmed
i was able to reproduce this in a VM
$ sudo pacman -Syyuu
:: Synchronizing package databases...
nonsystemd 15.4 KiB 0.00 B/s 00:00 [###################] 100%
libre 353.0 KiB 630 KiB/s 00:01 [###################] 100%
core 121.5 KiB 2.24 MiB/s 00:00 [###################] 100%
extra 1494.8 KiB 2.21 MiB/s 00:01 [###################] 100%
community 4.5 MiB 2.32 MiB/s 00:02 [###################] 100%
pcr 558.9 KiB 2.37 MiB/s 00:00 [###################] 100%
:: Starting full system upgrade...
:: Replace dbus-elogind with nonsystemd/dbus? [Y/n]
:: Replace dbus-openrc with nonsystemd/dbus? [Y/n]
:: Replace elogind-openrc with nonsystemd/elogind? [Y/n]
:: Replace kmod-openrc with nonsystemd/openrc? [Y/n]
:: Replace networkmanager-elogind with nonsystemd/networkmanager? [Y/n]
:: Replace networkmanager-openrc with nonsystemd/networkmanager? [Y/n]
:: Replace polkit-elogind with nonsystemd/polkit? [Y/n]
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libelogind and systemd-libsystemd are in conflict
$ sudo pacman -R systemd-libsystemd
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing systemd-libsystemd breaks dependency 'libsystemd.so' required by systemd-libs-dummy
$ sudo pacman -R libelogind
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing libelogind breaks dependency 'libelogind' required by dbus-elogind
:: removing libelogind breaks dependency 'libelogind' required by elogind
$ sudo pacman -Ss libsystemd.so
nonsystemd/libelogind 241.3-1 (base-devel) [installed: 238.1.0-2.1]
elogind client libraries
libre/systemd-libsystemd 243.162-2.parabola1 [installed: 243.78-1.par1]
systemd client library
$ sudo pacman -Si libelogind | grep -E 'Repository|Provides'
Repository : nonsystemd
Provides : libelogind.so=0-64 libelogind=241.3 libsystemd=241.3 systemd-libs=241.3 libsystemd.so=0-64
Repository : pcr
Provides : libelogind.so=0-64
$ sudo pacman -Ss libelogind
nonsystemd/libelogind 241.3-1 (base-devel) [installed: 238.1.0-2.1]
elogind client libraries
pcr/libelogind 238.1.0-2.1 [installed]
elogind client libraries
pcr/libelogind-manpages 238.1.0-2.1
Manual pages for libelogind
pcr/polkit-elogind 0.114-1.parabola1 [installed]
Application development toolkit for controlling system-wide privileges,
with libelogind support
$ sudo pacman -Ss systemd-libsystemd
libre/systemd-debug 243.162-2.parabola1
Detached debugging symbols for systemd
libre/systemd-libsystemd 243.162-2.parabola1 [installed: 243.78-1.par1]
systemd client library
Updated by bill-auger over 3 years ago
for anyone who has this problem today, the conflict can be resolved with this command:
$ sudo pacman -S libelogind resolving dependencies... looking for conflicting packages... :: libelogind and systemd-libsystemd are in conflict. Remove systemd-libsystemd? [y/N] y
megver, presumably the permanent solution is to remove libelogind from [pcr] ?
Updated by bill-auger over 3 years ago
- Subject changed from Conflict when updating openrc install to Conflict updating openrc - libelogind and systemd-libsystemd are in conflict