Friday 30 November 2018

help with sbuild dep8 failures on i386/bionic

Hi,

I have a couple of SRUs that are triggering sbuild DEP8 runs on bionic
and these are only failing on i386:

http://autopkgtest.ubuntu.com/packages/s/sbuild/bionic/i386
http://autopkgtest.ubuntu.com/packages/s/sbuild/bionic/amd64

I triggered those using debootstrap from proposed, otherwise we hit
another bug where "disco" is unknown.

I can reproduce the failure on bionic i386, but I cannot explain how
it is even supposed to work in any architecture.

The test basically uses sbuild to build procenv on the current devel
version of ubuntu. Today, that's disco. At the end of the build, it
tries to install the built package on the host, and this is the first
red flag.

From debian/tests/build-procenv:
...
# We should probably only attempt to install and run procenv if the release of
# the build chroot is equal to the host, but lets be brave and try anyway
if true
#if [ "$release" = "$host_release" ]
then
echo "INFO: Installing package '$pkg' from '$deb'"

That is why it's failing on i386:
The following packages have unmet dependencies:
procenv : Depends: libc6 (>= 2.28) but 2.27-3ubuntu1 is to be installed
E: Unable to correct problems, you have held broken packages.

bionic has libc6 2.27, disco has libc6 2.28. So the above error makes sense.

But in the amd64 build, this does not happen. The built package has
this Depends line:
Depends: libc6 (>= 2.17), libcap2 (>= 1:2.10), libnuma1 (>= 2.0.11),
libselinux1 (>= 1.32)


How?? Going up in the dep8 logs even shows that it used libc6-dev-2.28
in the sbuild :)

I'm baffled.

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel