Bug#1012458: marked as done (No network connection: systemd-resolved fails to start on read-only filesystem)

[Debian Bug Tracking System]

Your message dated Thu, 9 Jun 2022 23:35:38 +0200
with message-id <83507436-5171-88ff-4145-b6528ad158aa at debian.org>
and subject line Re: No network connection: systemd-resolved fails to start on read-only filesystem
has caused the Debian Bug report #1012458,
regarding No network connection: systemd-resolved fails to start on read-only filesystem
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.)


-- 
1012458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012458
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: dmorandi101 at tuta.io
Subject: No network connection: systemd-resolved fails to start on read-only filesystem
Date: Tue, 7 Jun 2022 19:37:09 +0200 (CEST)
Size: 4235
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220609/f90f193c/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: No network connection: systemd-resolved fails to start on read-only filesystem
Date: Thu, 9 Jun 2022 23:35:38 +0200
Size: 6635
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220609/f90f193c/attachment-0001.eml>