This bug was fixed in the package curtin - 0.1.0~bzr399-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr399-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* SRU current curtin
- curtin/net: fix inet value for subnets, don't add interface attributes
to alias (LP: #1588547)
- i
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-failed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Hello Scott, or anyone else affected,
Accepted curtin into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr399-0ubuntu1~14.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
We do not want this released to trusty because it will expose another
known bug.We have a newer SRU in unapproved queue that will fix things
up.
** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty
** Changed in: curtin (Ubuntu Trusty)
Status: Fix Committed
This bug was fixed in the package curtin - 0.1.0~bzr389-0ubuntu1~16.04.1
---
curtin (0.1.0~bzr389-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* New upstream snapshot.
* Detect and remove legacy /etc/network/interfaces.d/eth0.cfg from
target (LP: #1582410)
curtin (0.
If you want to leave curtin in -proposed in Trusty, then the tags should
be verification-needed-trusty and verification-done-xenial. As it
stands with just a verification-done tag the SRU team might release it
into Trusty's -updates.
** Tags removed: verification-done
** Tags added: verification-
The MAAS team regularly tests on both Trusty and Xenial, for MAAS 1.9
and 2.x (respectively). I'm confident in the earlier statement of
`verification-done`, especially as it relates to Xenial.
That said, I'm 80% confident in Trusty, only because we have MAAS 1.5.4
in -security, MAAS 1.7.6 in -upda
Andres, which release did you test? Resetting to v-needed as it's
unclear what you did and wheter it was for trusty, xenial, or both.
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: curtin (Ubuntu Wily)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577872
Title:
[SRU] curtin in yakkety to supported releases
To manage notifi
Tested this and works as expected!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577872
Title:
[SRU] curtin in yakkety to supp
Martin, I suggested wily SRU really only because otherwise it is older than
trusty.
I'm OK with your position as SRU team member saying its not important.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577872
Title:
[SRU] curtin in yakkety to supported releases
To manage notifications
** Branch linked: lp:~smoser/ubuntu/xenial/curtin/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577872
Title:
[SRU] curtin in yakkety to supported releases
To manage notifications about this b
** Description changed:
== Begin SRU Template ==
- [Impact]
+ [Impact]
This update to curtin is required to support features of MAAS 1.9 that is
being SRU'd to trusty and wily under bug 1509147. There are also numerous bug
fixes that affect the code path used with older maas as well. See
Hello Scott, or anyone else affected,
Accepted curtin into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr387-0ubuntu1~14.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
Does this SRU to wily actually make sense? Non-LTS releases aren't very
interesting on servers in the first place, and now that Xenial is out
and wily only has two more months to live the effort/benefit ratio is
even higher.
--
You received this bug notification because you are a member of Ubuntu
Hello Scott, or anyone else affected,
Accepted curtin into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr387-0ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
** Description changed:
+ == Begin SRU Template ==
+ [Impact]
+ This update to curtin is required to support features of MAAS 1.9 that is
being SRU'd to trusty and wily under bug 1509147. There are also numerous bug
fixes that affect the code path used with older maas as well. See the
change
I've just uploaded 0.1.0~bzr387-0ubuntu1~YY.MM.1 to each xenial wily and trusty.
yakkety does not yet have 387 due to LP: #1560134.
** Description changed:
- In order to support MAAS sru of 1.9 into trusty, we need a newer version
- of curtin.
+ In order to support MAAS sru of 1.9 into trusty, we
19 matches
Mail list logo
