touch-packages team mailing list archive

[Launchpad Bug Tracker <1492129@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 225-1ubuntu3

---------------
systemd (225-1ubuntu3) wily; urgency=medium

  * Enable libseccomp support for mips64, mips64el, and x32. (Closes: #797403)
  * debian/tests/networkd: Add hotplug tests.
  * Make networkd call if-up.d/ scripts when it brings up interfaces, to
    become compatible with ifupdown and NetworkManager for packages shipping
    hooks. (LP: #1492129)
    - Add debian/extra/units/networkd-if-up.d@.service: Wait for a particular
      interface to be up, and call if-up.d/ for it if it is managed by
      networkd. Correspondingly, call if-post-down.d/ scripts when stopping.
    - debian/extra/udev-helpers/net.agent: Start/stop
      networkd-if-up.d@.service when interfaces appear/go away.
    - debian/tests/networkd: Verify that if-up.d/ and if-post-down.d/ scripts
      get run for a networkd managed interface.
    - Note that if-pre-up.d/ and if-down.d/ scripts are *not* being called, as
      they are often not applicable for networkd (if-pre-up.d) and unreliable
      (if-down.d).
  * Drop udev-finish. We needed this for the autogenerated CD and network
    interface names, but both are gone now.
  * Drop debian/udev.udev-fallback-graphics.upstart. The vesafb module has
    been compiled into the kernel in both Debian and Ubuntu for a fair while,
    this never had a systemd equivalent, and Debian never shipped the
    accompanying rules for determining $PRIMARY_DEVICE_FOR_DISPLAY.
  * debian/control: Remove some boilerplate from the long descriptions, to
    more easily get to the point what a specific package actually does.
  * debian/README.Debian: As systemd is the default init now, replace the
    documentation how to switch to systemd with how to switch back
    (temporarily or permanently) to SysV init. Also move that paragraph to the
    bottom as it's now less important.
  * debian/README.Debian: Add a hint why you may want to enable persistent
    journal, and suggest to uninstall system-log-daemon to avoid duplicate
    logging.
  * debian/README.Debian: Add documentation about networkd integration.

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Wed, 09 Sep 2015 07:56:03
+0200

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492129

Title:
  FFE: integrate networkd with /etc/network/if-*.d/ scripts

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w
  -networkd-vs-ifupdown we want to provide networkd as a viable option
  for Ubuntu, in particular server/cloud land. This requires some
  integration with existing packages, in particular calling the
  /etc/network/if-up.d/ and if-post-down.d/ scripts, similar to what
  NetworkManager does.

  I would like to land this in wily still, so that people can experiment
  it and we still have some time to tweak it  for 16.04 LTS:

      http://anonscm.debian.org/cgit/pkg-
  systemd/systemd.git/commit/?id=27f7cc9f9f32

  As we don't currently use (or even advertise) networkd in Ubuntu, the
  risk of this is very low IMHO. The main regression risk is if that
  would somehow influence/break interfaces managed by ifupdown or
  NetworkManager, but the above changes test if the interface is managed
  by networkd.

  We also want to provide integration with "resolvconf". This does not
  exist yet, but an FFE for this might come for wily as well.

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