[Pkg-utopia-maintainers] Bug#747105: Now, really... (policykit-1: depends on systemd)

[Cristian Ionescu-Idbohrn]

I made a (user) choice.  Am I entitled to do so?
I'm not a believer, yet.
I thought debian all about that.
Got disapointed :/

I don't want any systemd infested packages on my system.
But I didn't pay enough attention :(  I find myself in this situation
(with policykit-1 on hold):

$ dpkg --get-selections | grep 'systemd'
libsystemd-daemon0:amd64                        install
libsystemd-id128-0:amd64                        install
libsystemd-id128-0:i386                         install
libsystemd-journal0:amd64                       install
libsystemd-journal0:i386                        install
libsystemd-login0:amd64                         install

# apt-get --purge remove libsystemd-daemon0:amd64 \
libsystemd-id128-0:amd64 libsystemd-id128-0:i386 \
libsystemd-journal0:amd64 libsystemd-journal0:i386 \
libsystemd-login0:amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 policykit-1 : Depends: libpolkit-agent-1-0 (>= 0.105) but it is not going to be installed
               Depends: libpolkit-backend-1-0 (>= 0.99) but it is not going to be installed
               Depends: libpolkit-gobject-1-0 (>= 0.101) but it is not going to be installed
               Depends: consolekit but it is not going to be installed
               Depends: dbus
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

What choice do I have now?  Is that freedom?
Come on...  That shouldn't happen!
Is this the new debian policy (break users systems)?


Cheers,

-- 
Cristian