libgpg-error/1.45-2 fails autopkgtest on i386

Bug #1975673 reported by Lukas Märdian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgpg-error (Ubuntu)
New
Undecided
Unassigned

Bug Description

The failure was introduced by this change in Debian:
https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628

It started to fail for i386 on autopkgtest.u.c:
https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz

The relevant log is this:
```
The following packages have unmet dependencies:
 builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable
E: Unable to correct problems, you have held broken packages.
win64 FAIL badpkg
[...]
autopkgtest [11:49:03]: @@@@@@@@@@@@@@@@@@@@ summary
win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed.
win64 FAIL badpkg
blame: libgpg-error
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
build PASS
```

As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386".

=========

Even if that can be fixed (https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176), the "win64" test is skipped now and "win32" executed, "win32" fails with a "badpkg" error, which probably needs solving in the archive.

$ PYTHONPATH=lib/ runner/autopkgtest libgpg-error --apt-pocket=proposed=src:libgpg-error -a i386 -U -- qemu /data/autopkgtest-kinetic-amd64.img
[...]
win64 SKIP Test lists explicitly supported architectures, but the current architecture i386 isn't listed.
[...]
The following packages have unmet dependencies:
 builddeps:/tmp/autopkgtest.8Maso6/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-i686:i386 but it is not installable
                                                                   Depends: wine32:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
win32 FAIL badpkg
blame: libgpg-error
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

Full log: https://paste.ubuntu.com/p/JYHrJpMGbn/

Revision history for this message
Alexandre Ghiti (alexghiti) wrote :

I think there's another problem: it fails to install gcc-mingw-w64-i686 because autopkgtest tries to install gcc-mingw-w64-i686:i386 which does not exist since it only exists as gcc-mingw-w64-i686:all.

I added :all to the test dependency, and then it works, the test passes correctly on i386 \o/

But I'll come up with the proper patch in autopkgtest: it should try :$arch first and then :all in case it does not work.

Revision history for this message
Lukas Märdian (slyon) wrote :

After the autopkgtest branch was merged, we're now testing a Multi-Arch fix:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13655308/+listing-archive-extra

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.