This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~17.10.1
---
nplan (0.32~17.10.1) artful; urgency=medium
* Backport 0.32 to Ubuntu 17.10. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces
Verification-done:
xenial: 0.32~16.04.3
zesty: 0.32~17.04.1
artful: 0.32~17.10.1
In all cases the autopkgtests are successful (remaining failures appear
to be limitations of the test infrastructure: s390x and arm64 missing
modules / installed packages for wireless (iw, cfg80211) which should be
a
Hello Jeremy, or anyone else affected,
Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Jeremy, or anyone else affected,
Accepted nplan into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Autopktests still failing for xenial; the test is still not being
skipped (we know it won't work on Xenial due to the version of NM
shipped there). Marking verification-failed-xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug n
Hello Jeremy, or anyone else affected,
Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the
code skipping the test_routes_v6 test in the NetworkManager case.
Therefore, it can't possibly pass SRU verification.
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received thi
Hello Jeremy, or anyone else affected,
Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Jeremy, or anyone else affected,
Accepted nplan into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
The autopkgtests are still failing, so marking v-failed.
(They are failing for both xenial and zesty, but Adam added a badtest
hint overriding the failures in xenial - which seems improper for an SRU
that is explicitly supposed to be fixing the autopkgtests.)
** Tags removed: verification-needed-
Hello Jeremy, or anyone else affected,
Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.29~16.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Jeremy, or anyone else affected,
Accepted nplan into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.29~17.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
** Description changed:
+ [Impact]
+ New versions of NetworkManager require more precise handling of the network
interfaces. If not already configured to be ignored, bridges may be managed if
no previous configuration exists, even if NetworkManager has not created the
bridge.
+
+ [Test case]
+
Mathieu, the MTU issue might have been fixed in NM 1.8.2 now in artful:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-8&id=588841
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
This bug was fixed in the package nplan - 0.25
---
nplan (0.25) artful; urgency=medium
* tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
* tests/integration.py: clean up after br0 in networkd's test_bridge_mac;
nplan was clearly not cleaning up after itself in the tests, and left
behind a br0 device that NM would try to manage (and just spin forever,
because there is no IP to be had there, and no DHCP server, etc).
There could still be a real regression in NM though; seems like it
really should not be ma
** Changed in: nplan (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699371
Title:
nplan autopkgtests are failing in artful (NM 1.8?)
To manage n
** Changed in: nplan (Ubuntu)
Status: New => In Progress
** Changed in: nplan (Ubuntu)
Importance: Undecided => High
** Changed in: nplan (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubunt
20 matches
Mail list logo