Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

Adam Borowski kilobyte at angband.pl
Wed Oct 9 00:14:29 BST 2019


On Mon, Oct 07, 2019 at 10:44:12PM +0200, Thorsten Glaser wrote:
> On Mon, 7 Oct 2019, Jean-Marc LACROIX wrote:
> > It seems that now all is ok, because sysvinit is correctly installed on Debian
> > 10.1
> 
> Yes, but the other packages are not yet ready for elogind
> in Debian 10.anything and never will, because Debian 10.x
> was released in April 2019, and this will not get updated.
> 
> (Backporting elogind once everything works will help, but
> not enough, because other packages hard-depend on (usually)
> libpam-systemd and lack the | logind alternative.)

And that's basically the only problem.

elogind in buster uses a separate libelogind which makes it immune to the
libsystemd alternative problem that haunts unstable.  That makes grabbing
libpam-elogind-compat or bolting it upon buster's libpam-elogind enough
to satisfy dependencies.

I don't remember if that's enough or not for policykit-1 to work adequately,
though.

> If you wish to use elogind, either be prepared to do
> unspeakably evil things (such as editing the internal
> dpkg status database, which I did to great success on
> an RPi last week) or upgrade to unstable (in which the
> only missing piece polkit-qt is).

Editing dpkg status is bad.  An equivs package (which libpam-elogind-compat
essentially is) is a much cleaner option.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄⠀⠀⠀⠀ etc), let the drink age at least 3-6 months.




More information about the Debian-init-diversity mailing list