Bug#1075757: elogind's conflict with libelogind0 precludes upgrade

[Benjamin Cama]

Hi Mark,

Le Thu, Jul 04, 2024 at 03:14:10PM +0100, Mark Hindley a écrit :
>On Thu Jul??  4 12:57:00 2024 Benjamin Cama <benoar at dolka.fr> wrote:
>> Package: elogind
>> Version: 246.10-1debian1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> I tried to upgrade to the latest 255 version of elogind, but I do not
>> understand the recent "Conflicts" addition with libelogind0: it renders
>> it uninstallable together with latest libelogind0, and thus ask me to
>> install libsystemd instead, which I do not want.
>
>That is the correct solution. Recent versions use libsystemd0 
>compatible cgroups. You need to let libelogind0 be uninstalled.  See 
>changelog and NEWS.

Ho, OK then, but I could not read the NEWS until the package is getting 
installed, so I did not get it. Installation went well this way.  But:

>libelogind0 itself will probably disppear or become a transitional 
>package.

So is libelogind0 deprecated then? I could understand that this subset 
of a library may be a bit too much work for the size reduction (I 
witnessed 670kB vs. 930kB, no big deal) and no difference in dependency, 
but I see nowhere that it is abandonned. Did I understand correctly? Or 
is it only Debian that abandon it? May I suggest to put an explaination 
somewhere on the reasons why?

>(Sorry for the brevity -- we are away atm)

No problem, thanks for the quick answer.

Regards.
-- Benjamin