Bug#1015015: marked as done (unable to upgrade due to elogind vs systemd conflict)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jan 2026 15:08:02 +0000
with message-id <aXzJUobcKknQ9gSd at hindley.org.uk>
and subject line Closing
has caused the Debian Bug report #1015015,
regarding unable to upgrade due to elogind vs systemd conflict
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
1015015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015015
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Craig Sanders <cas at taz.net.au>
Subject: unable to upgrade due to elogind vs systemd conflict
Date: Sat, 16 Jul 2022 18:34:35 +1000
Size: 4285
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20260130/aaafab67/attachment-0002.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Mark Hindley <mark at hindley.org.uk>
Subject: Closing
Date: Fri, 30 Jan 2026 15:08:02 +0000
Size: 1937
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20260130/aaafab67/attachment-0003.eml>