lp:ubuntu/oneiric/bridge-utils

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

16. By Steve Langasek on 2011-05-08

* Merge from Debian unstable (LP: #483427, LP: #377474). Remaining changes:
  - Add an upstart job which triggers on each net-device-added event, to
    see whether we need to add this to a bridge.
* Changes merged in Debian:
  - debian/rules, debian/bridge-utils.sh, debian/dirs, debian/ifupdown.sh:
    factor out the parsing of bridge_ports into a reusable shell library.
* Replace the upstart job with a udev rule instead; thanks to Manty for
  the suggestion.

15. By Steve Langasek on 2010-02-11

bridge-utils.bridge-network-interface.upstart: adjust the matching so that
bridges pointed at vlans on a physical interface are started when the
physical interface is up, since there's no udev event for the vlan.

14. By Steve Langasek on 2010-02-11

releasing version 1.4-5ubuntu2

13. By Steve Langasek on 2010-02-11

bridge-utils.bridge-network-interface.upstart: adjust the matching so that
bridges pointed at vlans on a physical interface are started when the
physical interface is up, since there's no udev event for the vlan.

12. By Steve Langasek on 2010-02-11

releasing version 1.4-5ubuntu1

11. By Steve Langasek on 2010-02-05

on second thought, don't pass --force; instead, the upstart job should
explicitly add the corresponding port to the bridge

10. By Steve Langasek on 2010-02-05

pass --force to ifup, otherwise the first interface will bring up the bridge
without all the ports

9. By Steve Langasek on 2010-02-05

update the maintainer field

8. By Steve Langasek on 2010-02-05

pass --noscripts to dh_installinit, there's nothing to start on package install

7. By Steve Langasek on 2010-02-05

Add an upstart job which triggers on each net-device-added event, to
see whether we need to add this to a bridge.