[ubuntu/quantal] ifupdown 0.7.1ubuntu3 (Accepted)

[Steve Langasek]

ifupdown (0.7.1ubuntu3) quantal; urgency=low

  * Add a 'stop on' rule for the networking service, so that we tear the
    network down at the correct point in the shutdown sequence (after remote
    filesystems have been unmounted).  This is mostly needed when using
    insserv upstart integration (not yet in Ubuntu) to ensure the shutdown
    doesn't hang waiting for an unsatisfiable init script dependency, but it
    also addresses the need for shutting down networking on runlevel changes
    - provided that umountnfs.sh itself is called for runlevel 1, which it
    currently is not.
  * Also start the job on runlevel [2345].  This is a no-op during a normal
    boot since the network will be started *before* runlevel is emitted, but
    is needed to restart the network after a change from runlevel 1.
    LP: #752481.

Date: Thu, 06 Sep 2012 15:05:32 -0400
Changed-By: Steve Langasek <steve.langasek at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Signed-By: =?utf-8?q?St=C3=A9phane_Graber?= <stgraber at stgraber.org>
https://launchpad.net/ubuntu/quantal/+source/ifupdown/0.7.1ubuntu3
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 06 Sep 2012 15:05:32 -0400
Source: ifupdown
Binary: ifupdown
Architecture: source
Version: 0.7.1ubuntu3
Distribution: quantal
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Steve Langasek <steve.langasek at ubuntu.com>
Description: 
 ifupdown   - high level tools to configure network interfaces
Launchpad-Bugs-Fixed: 752481
Changes: 
 ifupdown (0.7.1ubuntu3) quantal; urgency=low
 .
   * Add a 'stop on' rule for the networking service, so that we tear the
     network down at the correct point in the shutdown sequence (after remote
     filesystems have been unmounted).  This is mostly needed when using
     insserv upstart integration (not yet in Ubuntu) to ensure the shutdown
     doesn't hang waiting for an unsatisfiable init script dependency, but it
     also addresses the need for shutting down networking on runlevel changes
     - provided that umountnfs.sh itself is called for runlevel 1, which it
     currently is not.
   * Also start the job on runlevel [2345].  This is a no-op during a normal
     boot since the network will be started *before* runlevel is emitted, but
     is needed to restart the network after a change from runlevel 1.
     LP: #752481.
Checksums-Sha1: 
 8623502c5ad4b0f83dd785a8260e59bef4e2cd58 1690 ifupdown_0.7.1ubuntu3.dsc
 05cf6a871f50b82672a489fc8e050302d3576262 123422 ifupdown_0.7.1ubuntu3.tar.gz
Checksums-Sha256: 
 995d7231312c011dc1a54b73e615a0caadab9bad241461aff85da3940b516020 1690 ifupdown_0.7.1ubuntu3.dsc
 809a1bc53ef2ec3067b9809110db3c9f405a28c2287f8b901ce8bd9755b28f45 123422 ifupdown_0.7.1ubuntu3.tar.gz
Files: 
 85599ade4c62e3acaf882573860babe9 1690 admin important ifupdown_0.7.1ubuntu3.dsc
 39dc26eced4aedc18203a5574dd74f19 123422 admin important ifupdown_0.7.1ubuntu3.tar.gz
Original-Maintainer: Andrew O. Shadura <bugzilla at tut.by>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCgAGBQJQSPRGAAoJEMY4l01keS1nGN8P/At35H90fnOJY7uAb/gywnWP
PHwJQa3c6HQ+yCjA1NjIXwQilip2H2ciLLAL9cNFhncjUVeTBC/c320UOdbA3nWU
Fj4NQKDs3wkUebZ2PeUUIXxSwcr09zsN9bfWfMHX0bbjrG9/nPHXZoBLHNUNKZWG
9Zb8ZRxBNzhEklMow6iTRHOzBia0weJ/2O9++zJg4CIkHZRQWDLJysUwC4RfPXPB
42kE1BoS4MWrfcHWn3jEmGwPHTzwMQ/CM0XIHzCJ6BPFiUQ2/DX5Ts7nebMJwvY6
BkeH1ChbsbcimNChfkiRoIWgbGnG4NT79nWobW/wf/ykC8wNBRguSmDUzaJDI56/
Bljmbqg5ctVBxsOVBMH7+6W85gH3M1L55ySmErHGnticCTs7Ko+LXUmHPYqGBK9W
dqFYpfCdWGpr07R/cvKa4c1lcbl2wWj2elnc9++5w4zcxMTbVkyLwwCdVAqHlkmW
FJU4nmMURJGiVw2yv/VbUyrAKrbvuK2vh0AR0TbSl2b0q3QsJnFpV3aWsYpoV+f+
NWHqETawceD2EAZE1V7FeDKEEj0EOwxDyzmP+UL9JF5zFJPBC89IOdjPmEdSKaFi
Vc4UjlmTmLuL8dnLaJ0VGi0v0M+o1fQ2+wi9VOwpgnIS3aIyNiwJugInhJebypTf
3DOekyQRngMqms0oOJL8
=iYKF
-----END PGP SIGNATURE-----