nplan 0.32~16.04.4 source package in Ubuntu

Changelog

nplan (0.32~16.04.4) xenial; urgency=medium

  [ Oliver Grawert ]
  * Prevent unbinding ath6kl_sdio, driver does not support it correctly.
    (LP: #1741910)

  [ Mathieu Trudel-Lapierre ]
  * Re-add snap support patch. (LP: #1747714)
  * Fix syntax for IPv6 addresses in doc. (LP: #1735317)
  * doc: routes are not top-level but per-interface. (LP: #1726695)
  * Implement bridge port-priority parameter. (LP: #1735821)
  * Implement "optional: true" to correctly write systemd network definitions
    with "RequiredForOnline=false", such that these networks do not block boot.
    (LP: #1664844)
  * Various documentation fixes. (LP: #1751814)

 -- Mathieu Trudel-Lapierre <email address hidden>  Fri, 02 Mar 2018 17:02:03 -0500

Upload details

Uploaded by:
Mathieu Trudel-Lapierre on 2018-03-02
Uploaded to:
Xenial
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
net
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial updates on 2018-04-12 universe net

Downloads

File Size SHA-256 Checksum
nplan_0.32~16.04.4.tar.gz 71.8 KiB e15c66ba75ebdc6e24fdcc8fb3ae7bfc612780ce637672c0eee5642c55445cce
nplan_0.32~16.04.4.dsc 1.7 KiB af655944c2f02b25f4d6c29605236667260f05a9bb3345d6f04439d6cf67439b

Available diffs

View changes file

Binary packages built by this source

nplan: YAML network configuration abstraction for various backends

 netplan reads YAML network configuration files which are written
 by administrators, installers, cloud image instantiations, or other OS
 deployments. During early boot it then generates backend specific
 configuration files in /run to hand off control of devices to a particular
 networking daemon.
 .
 Currently supported backends are networkd and NetworkManager.

nplan-dbgsym: debug symbols for package nplan

 netplan reads YAML network configuration files which are written
 by administrators, installers, cloud image instantiations, or other OS
 deployments. During early boot it then generates backend specific
 configuration files in /run to hand off control of devices to a particular
 networking daemon.
 .
 Currently supported backends are networkd and NetworkManager.