[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

gnupg2 autopkgtest uses multi-arch which seems fragile

Hi gnupg2 maintainers, all,

I am investigating the autopkgtest regressions of glibc¹ (2 left after
some retries). I notice that gnupg2 fails (also in the retry) with the
error below. I don't fully understand yet, but I think this is due to
some requirement that only unstable can fulfill at the moment (also, the
test passes there). Because the autopkgtest of gnupg2 does this, the
regular fall-back isn't available and the test errors out.

Does anybody see what goes wrong? And how should this be solved? If not
I recommend to add a "flaky" restriction to the restrictions of the
autopktest of gnupg2 as it seems to me that this isn't suitable for
unstable-to-testing migration checks.


¹ https://qa.debian.org/excuses.php?package=glibc


Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wine32:i386 : Depends: libc6:i386 (>= 2.17) but it is not going to be
               Depends: libwine:i386 (= 3.0.2-1) but it is not going to
be installed
E: Unable to correct problems, you have held broken packages.
autopkgtest [04:35:17]: test gpgv-win32: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: