Bug#1035076: plymouth: Plymouth package has defective hard-dependency on systemd
john faulk
Version: 22.02.122-3
Severity: normal
X-Debbugs-Cc: johnny....@yahoo.com
Dear Maintainer,
The Plymouth Package has a hard-dependency on systemd for installation. This
should not be the case, seeing as there are initscripts present for it. I have
tested a simple fix where elogind is added in the source control file as an
alternative to systemd's dependency, and it has worked every time I have tried
it. This will allow non-systemd users to use plymouth, and is a very simple
fix.
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages plymouth depends on:
ii elogind 246.10-1debian1
ii init-system-helpers 1.65.2
ii initramfs-tools 0.142
ii libc6 2.36-9
ii libdrm2 2.4.114-1+b1
ii libplymouth5 22.02.122-3
ii sysvinit-utils [lsb-base] 3.06-4
ii udev 252.6-1
plymouth recommends no packages.
Versions of packages plymouth suggests:
ii desktop-base 12.0.5
ii plymouth-themes 22.02.122-3
-- Configuration Files:
/etc/plymouth/plymouthd.conf changed [not included]
-- no debconf information
Laurent Bigonville
thanks
Le 29/04/23 à 00:10, john faulk a écrit :
> Dear Maintainer,
Hello,
> should not be the case, seeing as there are initscripts present for it. I have
> tested a simple fix where elogind is added in the source control file as an
> alternative to systemd's dependency, and it has worked every time I have tried
> it. This will allow non-systemd users to use plymouth, and is a very simple
> fix.
plymouth package doesn't mean you cannot use it with an other initsystem
on debian, the package that actually changes the default initsystem is
"systemd-sysv", not "systemd"
Removing the dependency might break plymouth at it requires some udev
rules files that are shipped by the systemd package (the rules are used
to tag the framebuffer devices/heads installed on the machines).
So removing that could break some setup
Kind regards,
Laurent Bigonville
Manuel Rosa
Dear Maintainer,
I am writing to you regarding the reported bug in the Plymouth package for Debian. As a member of the development team, I would like to reinforce the request made by one of our team members regarding the review of the code.
We understand that you may receive a large number of bug reports, but we believe that this particular issue deserves attention. It is affecting the user experience and, as a result, may discourage some users from using the Debian operating system.
We appreciate your hard work and dedication to maintaining the Plymouth package, and we understand that reviewing the code may take some time. However, we kindly request that you prioritize this issue and keep us updated on its progress.
Thank you for your time and consideration.
Best regards, Manuel Rosa
Laurent Bigonville
I am not saying to remove the systemd dependency. I am saying that changing "systemd," to "systemd | elogind" under the control section for the plymouth package in particular, NOT the build dependencies, thus allowing installation on (and forcing a dependency on) either one of them. Those who use a no-systemd system know full well there is a risk, seeing as it's a pretty deliberate act to begin with in Debian. Changing it as described above would have no affect at all on systemd systems, as it would still pull in systemd and enforce that need. Please reconsider this course of action.
The fact that plymouth package is depending on systemd has nothing to do with the fact that it requires (e)logind (it actually doesn't, plymouth runs at early boot and has nothing to do with a user session).
As said the dependency is needed because plymouth requires some
udev rules (namely /usr/lib/udev/rules.d/71-seat.rules) and tags
to properly detect the framebuffer/drm devices.
So as long at the rules file is shipped, in systemd package,
plymouth will have that dependency.
On Sat, Apr 29, 2023 at 6:25 AM, Laurent Bigonville