group.of.nepali.translators team mailing list archive

[Stéphane Graber <stgraber@xxxxxxxxxxxx>]

Local test rebuild worked fine, autopkgtest looks happy, releasing.

** Changed in: lxd (Ubuntu Yakkety)
       Status: Triaged => Fix Released

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647017

Title:
  [SRU] Update xenial and yakkety to match zesty version

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  == Rationale ==
  Update go-lxc to match in all supported Ubuntu releases. This includes adding a couple more bindings related to attach which will be used as the basis for an attach bugfix in the upcoming LXD bugfix release.

  == Test case ==
  Current LXD from the target series and the current upstream LXD should be rebuilt against this and the testsuite run. This on top of the autopkgtests included in the go-lxc package will validate that this didn't cause regressions and that the new bindings work properly (as used in current upstream LXD).

  == Regression potential ==
  go-lxc is only used by LXD at this point and LXD CI runs against the latest go-lxc upstream. This is also the version of go-lxc which is in the current development release and so has effectively received the most stress testing by LXD upstream.

  The risk of regression is therefore very low and the content of this
  new snapshot is basically limited to clean additions or
  straightforward bugfixes.


  go-lxc is used by LXD as the way to interact with liblxc.
  As a result, upstream changes for it are usually restricted to bugfixes or minor improvements (for things like CRIU support). To make our lives easier, we like to keep go-lxc in sync in all supported Ubuntu releases to match the LXC version that we also keep in sync there.

  To do so, we need to SRU a new version of go-lxc to xenial and yakkety, with the following upstream changelog:
   - bindings C: check for LXC_DEVEL in version.h file
   - bindings go: check for LXC_DEVEL in version.h
   - lxc-binding: add binding for c->attach()
   - container: add RunCommandNoWait()
   - lxc_test: add test for RunCommandNoWait()
   - Move LXC_DEVEL define to after version.h include
   - c/r: make sure container is running before doing a dump
   - container, error: return correct error
   - Fix TestRunCommandNoWait failure
   - tests: Skip architecture test on !x86
   - tests: Make skip messages consistent
   - Run "go fmt"

  The xenial SRU will not require any extra work. The next LXD upload
  will simply pick up the new go-lxc at build time.

  For the yakkety SRU, we will need to upload a no change rebuild of LXD
  to build against the new go-lxc and we'll need them both to be
  released at the same time. That's because of the addition of the
  "attach()" function which changes the Go shared library hash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-gopkg-lxc-go-lxc.v2/+bug/1647017/+subscriptions