Bug#1058046: marked as done (systemd: unable to run fsck at boot)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 01:49:55 +0100
with message-id <1e4b078b-4707-4b9b-86fa-623954d670bb at debian.org>
and subject line Re: Bug#1058046: systemd: unable to run fsck at boot
has caused the Debian Bug report #1058046,
regarding systemd: unable to run fsck at boot
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.)


-- 
1058046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058046
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Alessandro -oggei- Ogier <alessandro.ogier at gmail.com>
Subject: systemd: unable to run fsck at boot
Date: Mon, 11 Dec 2023 18:30:25 +0100
Size: 2113913
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20231218/91b27522/attachment-0002.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#1058046: systemd: unable to run fsck at boot
Date: Mon, 18 Dec 2023 01:49:55 +0100
Size: 10145
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20231218/91b27522/attachment-0003.eml>