nplan 0.32~16.04.6 source package in Ubuntu
Changelog
nplan (0.32~16.04.6) xenial; urgency=medium [ Mathieu Trudel-Lapierre ] * tests/integration.py: Fix autopkgtests involving bonds/bridges to do proper cleanup every time, so later tests don't unnecessarily wait for an interface not configured to be up. (LP: #1775097) [ Daniel Axtens ] * Generate udev rules files to rename devices (LP: #1770082) Due to a systemd issue[1], using link files to rename interfaces doesn't work as expected. Link files will not rename an interface if it was already renamed, and interfaces are renamed in initrd, so set-name will often not work as expected when rebooting. However, rules files will cause a renaming, even if the interface has been renamed in initrd. -- Mathieu Trudel-Lapierre <email address hidden> Tue, 03 Jul 2018 12:55:11 -0400
Upload details
- Uploaded by:
- Mathieu Trudel-Lapierre
- Uploaded to:
- Xenial
- Original maintainer:
- Ubuntu Developers
- Architectures:
- any
- Section:
- net
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
nplan_0.32~16.04.6.tar.gz | 74.4 KiB | 3be723534b4b6ea78a4693f4f8f83834a970531e478eff998f1904e3e4172861 |
nplan_0.32~16.04.6.dsc | 1.7 KiB | c2171c6165c79cce57833aa0d23d726d509695763cfcf86472bda627c1b489b1 |
Available diffs
- diff from 0.32~16.04.5 to 0.32~16.04.6 (4.7 KiB)
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.