Your message dated Sat, 12 Jul 2025 23:22:12 +0200
with message-id <ahlsbokwvzzhh...@per.namespace.at>
and subject line Re: Bug#777423: ifupdown not marked as essential
has caused the Debian Bug report #777423,
regarding ifupdown not marked as essential
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 ow...@bugs.debian.org
immediately.)
--
777423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown
Version: 0.7.51
ifupdown not marked as essential although it's removal breaks network
configuration completely.
--- End Message ---
--- Begin Message ---
On Sun, Feb 08, 2015 at 04:23:31AM +0200, Alex Kuklin wrote:
> Package: ifupdown
> Version: 0.7.51
>
> ifupdown not marked as essential although it's removal breaks network
> configuration completely.
Marking it as Essential would be wrong for many reasons, one of them
is that it is popular to switch the network management stack to
something that is not ifupdown.
--- End Message ---
