Bug#923244: [Pkg-utopia-maintainers] Bug#923244: Bug#923244: libelogind ABI compatibility pending

Michael Biebl biebl at debian.org
Wed Mar 6 13:31:09 GMT 2019

Am 06.03.19 um 10:07 schrieb Mark Hindley:
> On Tue, Mar 05, 2019 at 09:11:28PM +0100, Michael Biebl wrote:
>>>> This has the potential for some interesting breakage, like the real
>>>> systemd being installed and used together with libelogind0.
>>>> We would need to make sure something like that can never happen (ideas
>>>> how to solve that?)
>>> Obviously that wouldn't work.
>>> At the moment elogind conflicts with systemd and depends on libelogind0. So you
>>> either end up with systemd + libsystemd0 or elogind + libelogind0. 
>> If the versions of elogind and systemd match up, you could end up with
>> systemd + libelogind0.
>> But to be
>>> sure we could add libelogind0 conflicts systemd?
>> This would need some testing if apt would do the right thing when
>> switching from sysvinit-core + elogind to systemd-sysv + systemd.
>> I've seen too many weird apt errors that were caused by Conflicts...
> I have just tested this: starting with sysvinit +  elogind
> test at DebianUnstable:~$ sudo apt-get install default-logind
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> Note, selecting 'libpam-systemd' instead of 'default-logind'
> The following additional packages will be installed:
>   libargon2-1 libcryptsetup12 libnss-systemd libsystemd0 systemd systemd-sysv
> Suggested packages:
>   systemd-container
> The following packages will be REMOVED:
>   elogind libelogind0 libpam-elogind libpam-elogind-compat sysvinit-core
> The following NEW packages will be installed:
>   libargon2-1 libcryptsetup12 libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv
> 0 upgraded, 7 newly installed, 5 to remove and 0 not upgraded.
> Need to get 4,536 kB of archives.
> After this operation, 12.6 MB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Looks right to me. The installation proceeds without problems.

Once you involve other packages (e.g. daemons that link against
libsystemd0), having a time window where libelogind0 has been removed
but libsystemd0 not yet being available, restarting such a daemon in
between would be fatal. Let's hope, apt (or aptitude) always gets the
ordering right.

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20190306/5a02ff52/attachment.sig>

More information about the Debian-init-diversity mailing list