[Bug 1881077] Re: [SRU] openvswitch 2.9.6

Robie Basak 1881077 at bugs.launchpad.net
Wed Jul 29 16:08:47 UTC 2020


Thank you for preparing the revised upload.

I've spent some time trying to reduce the review size here, but despite
some help from James in #ubuntu-devel I've not managed to understand how
the current orig tarball in the queue comes about.

I found https://www.openvswitch.org/releases/openvswitch-2.9.6.tar.gz
but that mismatches the uploaded orig tarball quite a bit - mostly in
autoconf, including in the areas of some (I think autoconf-) generated
testsuites. It looks like the upstream tarball hasn't had autoconf run,
but the uploaded orig tarball has had this done. Or are you using a
different source?

I'm not confident in reviewing this without understanding how the orig
tarball comes about. Please could you provide steps to reproduce the
orig tarball?

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1881077

Title:
  [SRU] openvswitch 2.9.6

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in openvswitch package in Ubuntu:
  Invalid
Status in openvswitch source package in Bionic:
  Triaged

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our
  supported customers have access to these improvements.
  The update contains the following package updates:

     * openvswitch 2.9.6

  [Test Case]

  The following SRU process was followed:

  https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

  In order to avoid regression of existing consumers, the OpenStack team will
  run their continuous integration test against the packages that are in
  -proposed. A successful run of all available tests will be required before the
  proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary of the
  executed tests. The OpenStack team members will not mark ‘verification-done’ until
  this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1881077/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list