Your message dated Fri, 2 Mar 2018 23:38:55 +0100
with message-id <20180302223854.kuqravgryq4rk...@mail.manty.net>
and subject line This bug is fixed
has caused the Debian Bug report #818845,
regarding bridge-utils breaks ifupdown hooks for child interfaces
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.)


-- 
818845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.5-9

The bridge-utils features an explicit call to `/etc/network/if-*.d/vlan`,
but this has the effect of breaking all other ifupdown hook scripts
called on interfaces that are bridged together.  The case I'm looking at
is a device where extra commands are needed before a given interface
becomes available.  Doing something like `ifquery $iface >/dev/null 2>&1`
and running `ifup` if true might alleviate this.

My case is an interface has an attached switch chip and if the commands
to configure the switch chip aren't run beforehand Bad Things(tm) can
happen.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sig...@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

--- End Message ---
--- Begin Message ---
This has already been fixed
-- 
Manty/BestiaTester -> http://manty.net

--- End Message ---

Reply via email to