[Bug 1975673] [NEW] libgpg-error/1.45-2 fails autopkgtest on i386

[Lukas Märdian]

Public bug reported:

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/

** Affects: libgpg-error (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: update-excuse

** Merge proposal linked:
   https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libgpg-error in Ubuntu.
https://bugs.launchpad.net/bugs/1975673

Title:
  libgpg-error/1.45-2 fails autopkgtest on i386

Status in libgpg-error package in Ubuntu:
  New

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/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673/+subscriptions