Julien,

Thank you.

On Wed, Sep 11, 2019 at 02:48:19PM +0200, Julien Cristau wrote:
> -UID: 41176                                                  
> 
> Package: libelogind0
> Version: 241.3-1+debian1
> Severity: serious
> 
> I wrote this in #934132 but that is being ignored so I'll repeat here.

I don't think it was being ignored, rather I had already answered it there.

> I don't think it's reasonable to ship this package with C/R/P
> libsystemd0.

I understand that you don't like it. However, for libelogind0 to export the same
symbols as libsystemd0 so that it could C/R/P libsystemd0 was the agreed
solution to bug #923244.

Do you have another suggestion as to how we could have resolved that? Other
solutions were discounted at the time.

> I think it opens you (and, more importantly, users) up to issues like
> #934491.  Even if #935910 were to be fixed in the package manager in          
>                                                                             > 
> bullseye, it would still mean libelogind0 couldn't ship with the C/R/P
> until bullseye+1.

I think it seems likely from discussions on #debian-dpkg that #935910 will be
fixed in APT and #934491 can be addressed by adding Breaks: << fixed APT.

> But beyond that particular issue, I'm sorry to say I think fundamentally
> attempting to provide a drop-in replacement for libsystemd0 while
> conflicting with systemd is doomed.  The replacement of sysvinit with
> systemd was careful to keep both init systems co-installable, and I
> think that's something to preserve to avoid providing users with a
> loaded footgun with alternative init systems.

I think this is where we will just have to disagree. I think choice in software
is important. That choice is precious and can be exercised in many ways. Most
importantly,  you are free to choose not to use something that you don't like or
don't want.

Best wishes

Mark

Reply via email to