Your message dated Sat, 3 Jun 2017 20:52:05 +0100
with message-id <[email protected]>
and subject line Re: Bug#863974: hplip should not require systemd
has caused the Debian Bug report #863974,
regarding policykit-1: There should be a variant of policykit-1 which doesn't
depend on systemd
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 [email protected]
immediately.)
--
863974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863974
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: policykit-1
Version: 0.105-8
Severity: normal
Policykit has been around for a while and many packages required it long before
systemd appeared on the scene (in my case, blueman, lightdm-gtk-greeter, colord,
hplip to name a few). It's companion, ConsoleKit, now comes in two "flavors",
one being systemd-logind, the other the original ConsoleKit, and the
dependencies
across the Debian packages have been set up to depend on either one of them.
What I'm proposing is to use a similar solution for policyit. For example, there
could be two packages: systemd-policykit-1 and policykit-1, the former one
compiled with --enable-systemd, the latter compiled with --disable-systemd. Or,
since we're talking about a release already out, the packages could be named
policykit-1 (with systemd) and policykit-1-nosystemd (without systemd). Or
something around those lines - you get the picture :)
-- System Information:
Debian Release: 8.1
APT prefers stable
APT policy: (700, 'stable'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.7-ckt11-amd64-cm1.4 (SMP w/6 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages policykit-1 depends on:
ii dbus 1.8.18-0+deb8u1
ii libc6 2.19-18
ii libglib2.0-0 2.42.1-1
ii libpam0g 1.1.8-3.1
ii libpolkit-agent-1-0 0.105-8
ii libpolkit-backend-1-0 0.105-8
ii libpolkit-gobject-1-0 0.105-8
policykit-1 recommends no packages.
policykit-1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri 02 Jun 2017 at 10:10:57 -0400, Mark Murawski wrote:
> Package: hplip
> Version: 3.16.11+repack0-3
> Severity: important
>
> * What led up to the situation?
> # apt-get install hplip
>
> Outcome:
> Building dependency tree
> Reading state information... Done
> The following additional packages will be installed:
> hplip-data libhpmud0 libpam-systemd libsane-hpaio policykit-1
> printer-driver-hpcups printer-driver-postscript-hp systemd
> Suggested packages:
> hplip-doc hplip-gui python3-notify2 system-config-printer systemd-ui
> systemd-container
> The following NEW packages will be installed:
> hplip libpam-systemd policykit-1 printer-driver-postscript-hp systemd
> The following packages will be upgraded:
> hplip-data libhpmud0 libsane-hpaio printer-driver-hpcups
> 4 upgraded, 5 newly installed, 0 to remove and 2119 not upgraded.
>
> My distribution is set up with sysvinit. There is no reason that
> installing a printer driver should require switching init systems
Installation of hplip does not change the init system. Closing.
--
Brian
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
