du problem: policykit-1 libpam-systemd systemd

[hightime]

Recently du began failing with an error telling me that it couldn't install policykit-1 because the package depended on libpam-systemd which wasn't going to be installed. libpam-systemd in turn needs systemd. If I try to manually upgrade systemd it wants to remove 94 packages.
I haven't seen any discussion about this and I'm wondering what the problem is.

[melmarker]

The problem is the lack of patience.

[hightime]

Ah, the old lack of patience problem. I did see mention of that. 

[DeepDayze]

Yup good ol' dependency hell. Patience is the watchword

[dibl]

I feel so alone!  Why do I not have the problem?

Code Auswählen Erweitern

root@n5110:/# apt policy policykit-1
policykit-1:
  Installed: 0.105-21
  Candidate: 0.105-21
  Version table:
*** 0.105-21 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
root@n5110:/# apt policy libpam-systemd
libpam-systemd:
  Installed: 239-10
  Candidate: 239-10
  Version table:
*** 239-10 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     239-5.6 500
        500 http://packages.siduction.org/fixes unstable/main amd64 Packages
root@n5110:/# apt policy systemd
systemd:
  Installed: 239-10
  Candidate: 239-10
  Version table:
*** 239-10 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     239-5.6 500
        500 http://packages.siduction.org/fixes unstable/main amd64 Packages

[tommy2]

@dibl, your not alone mine says the same thing 0.105-21, candidate and installed. 

[paco]

Everything is fine here, too 

[samoht]

@dibl, @tommy2, @paco
+1