Bug#1056321: elogind conflicts with same version libelogind0

[Mark Hindley]

Hi Thorsten,

On Tue, Nov 21, 2023 at 12:58:40AM +0100, Thorsten Glaser wrote:
> Did you forget to not build the libelogind0 binary package any more
> then?

It was a conscious decision on my part to keep it for now. I see 2 benefits:-

 1. If we need to revert this approach, it will save a trip through NEW

 2. I suppose somebody may have a use for libelogind0 or libelogind-dev, and I
    didn't want to remove that option.

Is that reasonable?

Thanks and best wishes

Mark