Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
Package: systemd-sysv Version: 204-14 Severity: serious systemd-sysv conflicts with sysvinit-core, which is required. This is particularly problematic since libpam-systemd alternatively depends on systemd-sysv. On my testing install, APT's solution when asked to upgrade systemd is to remove sysvinit-core: # LANG=C apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following packages were automatically installed and are no longer required: libcolamd2.8.0 lp-solve xulrunner-29 Use 'apt-get autoremove' to remove them. Done The following packages will be REMOVED: sysvinit-core The following NEW packages will be installed: systemd-sysv The following packages will be upgraded: libpam-systemd libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0 libsystemd-login0 systemd 6 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Removing libpam-systemd isn't too tempting neither: # LANG=C apt-get remove libpam-systemd Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libcolamd2.8.0 libmodemmanagerqt1 libnetworkmanagerqt1 lp-solve xulrunner-29 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: colord hplip kde-plasma-desktop libpam-systemd network-manager plasma-nm plasma-widget-networkmanagement policykit-1 policykit-1-gnome printer-driver-postscript-hp udisks2 0 upgraded, 0 newly installed, 11 to remove and 5 not upgraded. I managed to solve this safely by installing systemd-shim. I was surprised to see APT propose the removal of a required package. I didn't test how that would go, but if that's not a problem, something must be wrong with its priority field. I'll save my system from such an experimentation and let others decide if this needs to be reassigned. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
reopen 754059 thanks On 2014-07-07 07:09, Michael Biebl wrote: Am 07.07.2014 08:56, schrieb Filipus Klutiero: Package: systemd-sysv Version: 204-14 Severity: serious systemd-sysv conflicts with sysvinit-core, which is required. Correct, systemd-sysv has a Conflicts/Replaces against sysvinit-core so it is actually possible to switch between different init systems. This is not a bug but intentional and necessary. Thus closing the bug report. Michael I suppose there's a reason why a conflict was declared. I didn't mean declaring a conflict with sysvinit-core is a bug *per se*. The bug is to conflict with a package of required priority, namely sysvinit-core. If it's necessary to conflict with a required package, then something's very wrong with the package. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
Am 07.07.2014 18:50, schrieb Filipus Klutiero: I suppose there's a reason why a conflict was declared. I didn't mean declaring a conflict with sysvinit-core is a bug *per se*. The bug is to conflict with a package of required priority, namely sysvinit-core. If it's necessary to conflict with a required package, then something's very wrong with the package. Nope, it's not. See also other init systems, like the upstart package, which declare the same Conflicts/Replaces. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#754059: [systemd-sysv] Conflicts with sysvinit-core
On 2014-07-07 13:04, Michael Biebl wrote: Am 07.07.2014 18:50, schrieb Filipus Klutiero: I suppose there's a reason why a conflict was declared. I didn't mean declaring a conflict with sysvinit-core is a bug *per se*. The bug is to conflict with a package of required priority, namely sysvinit-core. If it's necessary to conflict with a required package, then something's very wrong with the package. Nope, it's not. See also other init systems, like the upstart package, which declare the same Conflicts/Replaces. I did specify If it's necessary to conflict with a required package. I assume you're implying that's not the case for systemd-sysv and will report a bug regarding sysvinit-core's priority. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
