Your message dated Mon, 25 Jan 2016 14:09:28 +0100 with message-id <56a61e88.1060...@ralfj.de> and subject line Re: [Pkg-kde-extras] Bug#812592: Requires systemd on Jessie for no particular reason has caused the Debian Bug report #812592, regarding Requires systemd on Jessie for no particular reason to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 812592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: k3b Version: 2.0.2-8 Hello, I find that on Jessie the k3b package requires running a systemd-based OS. k3b depends on: udisks2 udisks2 depends on: libpam-systemd libpam-systemd depends on: systemd This is even more baffling when you consider that the Jessie version of k3b is 2.0.2-8, whereas the Wheezy version is 2.0.2-6. So there are probably no actual systemd-using changes in the program to mandate its requirement. Running non-systemd init systems such as 'sysvinit' and 'upstart' is also a supported configuration in Debian Jessie. But their users can't currently install k3b without breaking their systems. Can you please reconsider to update the dependencies so that systemd is not required to use k3b. Thanks! -- With respect, Roman
Description: PGP signature
--- End Message ---
--- Begin Message ---Hi, > I find that on Jessie the k3b package requires running a systemd-based OS. > > k3b depends on: udisks2 > udisks2 depends on: libpam-systemd > libpam-systemd depends on: systemd > Running non-systemd init systems such as 'sysvinit' and 'upstart' is also > a supported configuration in Debian Jessie. But their users can't currently > install k3b without breaking their systems. You are mistaken. "systemd" just installs the binaries, it does not force you to actually use systemd as your init system. This is explained in the package description: Installing the systemd package will not switch your init system unless you boot with init=/bin/systemd or install systemd-sysv in addition. Notice the following dependency of libpam-systemd: systemd-shim (>= 8-2) | systemd-sysv This is what allows you to pick between using systemd as your init, or another init system + the systemd-shim compatibility layer. In particular, using upstart or sysvinit works just fine. If it does not, that's a bug in systemd-shim that you should report there. As you can see, systemd-shim is even listed as the default, preferred alternative. Kind regards, Ralf
--- End Message ---
_______________________________________________ pkg-kde-extras mailing list firstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras