[12:27] <serge_> jhunt: hey are you around?
[12:38] <jhunt> serge_: hi
[12:45] <serge_> jhunt: oh, hey.  I wanted to get your input on bug 495394
[12:45] <serge_> jhunt: in particular, as to whether the /etc/init/networking-up.conf' should be shipped with libvirt
[12:45] <serge_> (and called libvirt-networking-up), or with something more general?
[12:46] <jhunt> k - looking at bug...
[12:49] <serge_> ignore comment 30, i'm basically going to use the debdiff attached to comment 24
[13:07] <jhunt> serge_: first question is why bridge-network-interface.conf is no longer in bridge-utils. The oneiric changelog suggests it should (still) be by the looks of it.
[13:35] <serge_> i thought they were suggesting a udev rule took its place
[13:35]  * serge_ goes to look more closely
[13:37] <serge_> yeah, it's covered
[13:37] <serge_> by bridge-utils.bridge-network-interface.udev and bridge-network-interface.sh
[13:45] <serge_> jhunt: and really the explanation of its interaction doesn't make sense to me.  THe net-device-up should still have been sent.
[13:45] <serge_> all that job did was bring up the bridge_ports
[13:54] <serge_> jhunt: so, en fin, what i'm wondering is whether networking-up.conf should ship with ifupdown or something
[13:54] <serge_> i'm happy to put it into libvirt, just don't want to put it in only to pull it out next week :)
=== JanC_ is now known as JanC