Your message dated Thu, 02 Oct 2014 19:59:45 +0200
with message-id <542d9291.1050...@debian.org>
and subject line Re: Bug#763784: libsystemd0: is this sane?
has caused the Debian Bug report #763784,
regarding libsystemd0: is this sane?
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.)
--
763784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsystemd0
Version: 215-5+b1
Severity: critical
Justification: breaks the whole system
Looking deeper:
Broken policykit-1:amd64 Depends on dbus [ amd64 ] < 1.8.8-1+b1 | 1.9.0-1 > ( ad
Considering dbus:amd64 51 as a solution to policykit-1:amd64 16
Reinst Failed early because of systemd:amd64
Reinst Failed because of libpam-systemd:amd64
Yes, I have policykit-1 on hold, as it attempts to make me install
systemd, and I have (currently) no use for it. I do _not_ want _any_
systemd packages installed on my system. I'm not interested.
The current systemd plague is crippling my system and I don't like it
(understatement). Please, pretty please, make this smoother!
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--
Cristian
--- End Message ---
--- Begin Message ---
On 02/10/14 19:04, Cristian Ionescu-Idbohrn wrote:
Source: libsystemd0
Version: 215-5+b1
Severity: critical
Justification: breaks the whole system
Looking deeper:
Broken policykit-1:amd64 Depends on dbus [ amd64 ] < 1.8.8-1+b1 | 1.9.0-1 > ( ad
Considering dbus:amd64 51 as a solution to policykit-1:amd64 16
Reinst Failed early because of systemd:amd64
Reinst Failed because of libpam-systemd:amd64
Yes, I have policykit-1 on hold, as it attempts to make me install
systemd, and I have (currently) no use for it. I do _not_ want _any_
systemd packages installed on my system. I'm not interested.
The current systemd plague is crippling my system and I don't like it
(understatement). Please, pretty please, make this smoother!
I don't know what you want changed, but there's certainly no critical bug on
systemd. If you don't want packages to depend on systemd, that'd be bugs in
those packages, not on systemd (but honestly I'll probably close any such bugs
on any of my packages).
Anyway, you can install systemd, libpam-systemd and systemd-shim and keep
running any init system. But if you don't want to install those, that's fine.
Just don't. But don't complain if some package links with libsystemd0 in order
to be able to talk to some systemd service if that's available.
Emilio
--- End Message ---
