On Sat, 07 Nov 2020 16:22:24 -0300, Eike wrote in message
<1632636.6XzDy3geBR@lxcl01>:

> On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière wrote:
> > Hi Eike,
> >
> > Install libelogind0 first, so it takes precedence over systemd, then
> > elogind.
> Thanks - but ->
> That is impossible because of a catch-22.It is not even possible to
> deinstall/purge libsystemd0it seems to be there to haunt me.
>
> Copy and paste off aptitude introduced some not-so-nice esc-sequences
> into the text. I hope that it will not mess-up the message too much.

..2 main ways: use aptitude to pick the version you want.

..if aptitude's error handling fails to find a solution, try apt
and apt-get, they do things differently, and if those fail, we have
rpm-style nuclear --force purge options to find with dpkg --help
and dpkg --force-help, just line or pile 'em up. ;o)

..once you've thrown out the trump you want out, refer back to
Ludovic's advice. ;o)

> *libsystemd0 (remove, 241-7~deb10u4)* will be removed. The following
> packages depend on *libsystemd0 (remove, 241-7~deb10u4)* and will be
> broken by its removal:
> * * *libaccountsservice0 (held/unchanged, 0.6.45-2) *depends on*
> libsystemd0 (>= 209) (provided by libelogind0 241.4-2)
> * * *libapt-pkg5.0 (held/unchanged, 1.8.2.1) *depends on* libsystemd0
> (>= 221) (provided by libelogind0 241.4-2)
> * * *libpulse0 (held/unchanged, 12.2-4+deb10u1) *depends on*
> libsystemd0 (provided by libelogind0 241.4-2)
> * * *network-manager (held/unchanged, 1.14.6-2+deb10u1) *depends on*
> libsystemd0 (>= 221) (provided by libelogind0 241.4-2)
> * * *openssh-server (held/unchanged, 1:7.9p1-10+deb10u2) *depends on*
> libsystemd0 (provided by libelogind0 241.4-2)
> * * *pulseaudio (held/unchanged, 12.2-4+deb10u1) *depends on*
> libsystemd0 (provided by libelogind0 241.4-2)
> * * *rsyslog (held/unchanged, 8.1901.0-1+devuan3~beowulf1) *depends
> on* libsystemd0 (provided by libelogind0 241.4-2)
> * * *samba-libs (held/unchanged, 2:4.9.5+dfsg-5+deb10u1) *depends on*
> libsystemd0 (provided by libelogind0 241.4-2)
> * * *sane-utils (held/unchanged, 1.0.27-3.2) *depends on*
> libsystemd0 (provided by libelogind0 241.4-2)
> * * *sddm (held/unchanged, 0.18.0-1+deb10u1) *depends on* libsystemd0
> (provided by libelogind0 241.4-2)
> * * *vlc-plugin-base (held/unchanged, 3.0.11-0+deb10u1) *depends on*
> libsystemd0 (provided by libelogind0 241.4-2)
> * * *xserver-xorg-core (held/unchanged, 2:1.20.4-1+deb10u1) *depends
> on* libsystemd0 (provided by libelogind0 241.4-2)
> >
> I have no idea how or why this situation came to be.
>
>
> > On Sat, 07 Nov 2020 10:41:47 -0300
> > Eike Lantzsch via Dng <dng@???> wrote:
> >
> >
> > > Hi!Maybe somebody can add some cheese to my whine:
> > > For months I am not able to resolve this catch-22 in Beowulf:
> > > The following packages have been kept back:
> > > Description: user, seat and session management library
> > > Homepage: https://github.com/elogind/elogind
> > > Multi-Arch: same
> > > Priority: optional
> > > Section: libs
> > > Maintainer: Mark Hindley <mark@???>
> > > Architecture: amd64
> > > Compressed Size: 224 k
> > > Uncompressed Size: 852 k
> > > Source Package: elogind
> > > Label: Devuan
> > > Origin: Devuan:3.0/stable [amd64]
> > > Origin URI:
> > > http://deb.devuan.org/merged/pool/DEVUAN/main/e/elogind/
> > >

> > > libelogind0_241.4-2_amd64.deb
> > >   --\ Depends (2)
> > >     --- libc6 (>= 2.28)
> > >     --- libcap2 (>= 1:2.10)
> > >   --\ Conflicts (2)
> > >     --- libsystemd0 (UNSATISFIED)
> > >     --- libsystemd0 (UNSATISFIED)
> > >   --\ Breaks (1)
> > >     --- libelogind0 (!= 241.4-2)
> > >   --\ Replaces (3)
> > >     --- libelogind0 (< 241.4-2)
> > >     --- libsystemd0
> > >     --- libsystemd0
> > >   --- Package names provided by libelogind0 (1)
> > >   --- Packages which depend on libelogind0 (5)
> > >   --\ Versions of libelogind0 (2)
> > > i    234.4-2
> > > p    241.4-2

> > >
> > > I had similar situations with Debian Sid and Testing during mayor
> > > changes and upgrades but was always able to resolve the issues by
> > > patience and diligently purging and reinstalling packges - but
> > > with Devuan Beowulf: NOT - no way.
> > >
> > > I am about to ditch my Beowulf installation and install from
> > > scratch.
> Before I do this, has anybody have a hint what I still
> > > might do over which solution I didn't happen to stumble or I
> > > overlooked?
>


--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.