On Thu, Dec 01, 2016 at 10:43:18AM +0100, Thomas Goirand wrote: > > If so, yeah, that broke for most nontrivial installations in stretch. > After some tests, it is libpam-systemd that is pulling systemd-shim.
This is a bug in the dependency resolver in debootstrap. The easiest fix is to not use it but call apt-get install with all the stuff. > 1/ Do we really need libpam-systemd? If you want login, yes. > 3/ If systemd-shim and systemd-sysv are conflicting, how come this isn't > declared in the packages? > > Finally, does anyone have a trick to fix this issue? The easiest fix is to not use it but call apt-get install with all the stuff. Or drop debootstrap in favor of cdebootstrap which is more stable in dependency resolving. Regards, Bastian -- Yes, it is written. Good shall always destroy evil. -- Sirah the Yang, "The Omega Glory", stardate unknown