El Tue, 22 de Jul 2014 a las 4:39 PM, Vincent Lefevre
<vinc...@vinc17.net> escribió:
On 2014-07-23 01:24:53 +0200, Vincent Lefevre wrote:
On 2014-07-22 22:54:55 +0100, Julian Gilbey wrote:
> I just tried updating testing on my system. I currently use
> sysvinit-core (reasons below), but aptitude is telling me that I
> should remove this in favour of systemd-sysv. Hmm, why is that?
> Well, because the new version of libpam-systemd, 208-6, now
depends on
> systemd-sysv rather than systemd-sysv | systemd-shim.
As you can see with this dependency, you just need to install
systemd-shim. No need to install systemd-sysv!
The default (systemd-sysv) was just a poor choice from aptitude.
Sorry, I mixed up with another problem that occurred with previous
versions. I have no problems on my Debian/unstable machines
(libpam-systemd still depends on systemd-sysv | systemd-shim),
but I've just realized that the reason is that I temporarily
blocked systemd upgrades for another reason. This is probably
the best thing to do because seeing how things evolve.
I used this apt preferences part to keep systemd back to version 204
until systemd-shim is updated:
Package: systemd libsystemd-* libpam-systemd
Pin: version 204*
Pin-Priority: 1001
I noticed that not doing the libraries cause apt to try to upgrade them
on dist-upgrade and do some weird operations like try to remove my
current init system and install systemd-sysv or remove all of systemd,
as well as NM and udisks and a lot of other packages.
Best wishes,
--
Cameron Norman
