unsure how to handle an autopkgtest issue

Michael Hudson-Doyle michael.hudson at canonical.com
Wed Mar 9 20:59:07 UTC 2022

On Tue, 8 Mar 2022 at 17:01, Michael Hudson-Doyle <
michael.hudson at canonical.com> wrote:

> Hi all,
> Last week I uploaded glibc to jammy-proposed. This gummed up the
> autopkgtest queues a good deal as usual but once all is done there are two
> regressions (well three currently but I think one will go away on retry):
> libassuan/2.5.5-1 and libgpg-error/1.43-3. These fail in the same way: they
> have a test that tries to install wine32.
> wine32 depends on libc6:i386. The pinning set up by autopkgtest means that
> the native libc6 from proposed is installable (is already installed in
> fact) but libc6:i386 from proposed is not. This sounds like a bug in
> autopkgtest but anyway, it causes autopkgtest to flip into "try all
> packages from proposed" mode, so wine32 is installed from proposed
> whereupon the tests fail because of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006827 (fallout from
> fixing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006539).


> I'll have a poke at fixing autopkgtest but that might take a little while
> to get anywhere.

Turns out this was pretty easy, thanks to Julian for the quick review and
deploy. glibc has migrated now.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20220310/fc2bf954/attachment.html>

More information about the Ubuntu-release mailing list