[Bug 1686064] Re: sbuild ADT test can only pass in devel series
Brian Murray
brian at ubuntu.com
Thu Aug 31 21:51:11 UTC 2017
Hello Dimitri, or anyone else affected,
Accepted sbuild into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sbuild/0.71.0-2ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: sbuild (Ubuntu Zesty)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-zesty
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sbuild in Ubuntu.
https://bugs.launchpad.net/bugs/1686064
Title:
sbuild ADT test can only pass in devel series
Status in sbuild package in Ubuntu:
Fix Released
Status in sbuild source package in Xenial:
Fix Released
Status in sbuild source package in Yakkety:
Won't Fix
Status in sbuild source package in Zesty:
Fix Committed
Bug description:
[Impact]
* sbuild adt tests assume that the test is running on the host, which
is the current devel series, which is not the case when adt tests are
running as part of SRU regression testing.
[Test Case]
* ADT test should pass
[Regression Potential]
* sbuild itself is not modified, only the autopkgtest themself are
fixed to not make unrealistic assumptions
[Other Info]
* Original bug report / problem description
src:sbuild has test build-procenv which can only pass in devel series,
as it assumes that the release test is running is the devel series.
This was true, until we started to run adt tests for stable releases
and SRUs.
Here is the detailed log of running build-procenv on xenial, whilst
devel series is called artful:
# ADTTMP=$(mktemp -d) sh -x debian/tests/build-procenv
+ set -e
+ pkg=procenv
+ components=
+ lsb_release -is
+ tr [A-Z] [a-z]
+ distro=ubuntu
+ [ -z ubuntu ]
+ lsb_release -cs
+ host_release=xenial
+ [ -z xenial ]
+ [ ubuntu = ubuntu ]
+ distro-info --devel
+ release=artful
+ components=main,universe
+ dpkg --print-architecture
+ url=http://archive.ubuntu.com/ubuntu
+ dpkg --print-architecture
+ arch=amd64
+ [ -z amd64 ]
+ [ -z /tmp/tmp.QYJvzqYkbV ]
+ dir=/tmp/tmp.QYJvzqYkbV/schroot-artful
+ chroot=artful-amd64-sbuild
+ schroot -l
+ schroots=
+ [ -n ]
+ [ -z ]
+ apt-config shell http_proxy Acquire::http::Proxy
+ RES=
+ eval
+ export http_proxy
+ echo INFO: using proxy: (none)
INFO: using proxy: (none)
+ echo INFO: Downloading source for package 'procenv' from release 'artful'
INFO: Downloading source for package 'procenv' from release 'artful'
+ apt-get source --download-only -o APT::Sandbox::User=root procenv/artful
Reading package lists... Done
E: Unable to find a source package for procenv
There are a couple of options here depending what we want to test. We
can either build procenv from $current on $current release -> this
will test that e.g. SRUs in xenial, do not break building packages for
xenial on xenial.
Or we can try to always build procenv from $devel in $devel chroot ->
this will test that all currently supported releases, can build
packages for $devel series.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1686064/+subscriptions
More information about the foundations-bugs
mailing list