[Bug 819928] Re: upstart-udev-bridge claims to emit events it does not emit

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.3-0ubuntu6

---------------
upstart (1.3-0ubuntu6) oneiric; urgency=low

  [ Steve Langasek ]
  * Fix maintainer field to be compliant with policy definition

  [ Clint Byrum ]
  * conf/rc.conf: document events that are emitted by sysvinit
    jobs to quiet 'initctl check-config'
  * extra/conf/upstart-udev-bridge.conf: narrow definition to
    only the events actually emitted. (LP: #819928)
  * debian/conf/failsafe.conf: new job for critical services to
    start on.
  * conf/rc-sysinit.conf: start after static-network-up or failsafe
    so that runlevel 2 is only entered with all static net interfaces
    up. (LP: #580319)
 -- Clint Byrum <clint at ubuntu.com>   Wed, 10 Aug 2011 08:44:43 -0500

** Changed in: upstart (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/819928

Title:
  upstart-udev-bridge claims to emit events it does not emit

Status in “ifupdown” package in Ubuntu:
  In Progress
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  upstart-udev-bridge says

  emits *-device-*

  But it does not actually emit net-device-up for instance.

  It only emits

  *-device-added

  and

  *-device-removed

  Changing this to be correct and running initctl check-config reveals
  that net-device-up is not emitted  (should be in the 'networking' and
  'network-interface' jobs).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/819928/+subscriptions