Re: gnupg2 autopkgtest uses multi-arch which seems fragile
Hi Ian,
Thanks for helping out.
On 09-07-18 15:02, Ian Jackson wrote:
> Ian Jackson writes ("Re: gnupg2 autopkgtest uses multi-arch which seems
> fragile"):
>> I looked in:
>>
>> * debian/tests/control in the gnupg2 source tree.
>> One test, of gpgv-win32. Depends on gpgv-win32, gnupg2,
>
> I have found it:
>
> debian/tests/gpgv-win32 manually installs wine32 using apt.
I noticed my original e-mail wasn't very clear because I thought the
above was obvious.
> This seems quite wrong. If a package needs to be installed, it should
> be handled via Depends in debian/tests/control. Otherwise all of the
> machinery to select which packages are being tested is utterly
> defeated.
Some packages have the purpose of installing stuff, so they may want to
do so I guess (e.g. apt does that). So I nearly agree with your
argument, but not fully. But as an example of your argument we already
have bug #900470 where syslog-ng tries to upgrade upgrade itself but
fails to do so due to our setup. The argument should be that in
autopkgtests the setup may be weird and tests should not need to know. I
guess what gnupg2 wants/needs is a way to either declare multi-arch
(maybe a new restriction?) with semantics to declare the dependencies
there or maybe they would be happy with an i386 test only, but ci.d.n
doesn't have that yet.
Paul
signature.asc
Description: OpenPGP digital signature
Re: gnupg2 autopkgtest uses multi-arch which seems fragile
Ian Jackson writes ("Re: gnupg2 autopkgtest uses multi-arch which seems
fragile"):
> I looked in:
>
> * debian/tests/control in the gnupg2 source tree.
> One test, of gpgv-win32. Depends on gpgv-win32, gnupg2,
I have found it:
debian/tests/gpgv-win32 manually installs wine32 using apt.
This seems quite wrong. If a package needs to be installed, it should
be handled via Depends in debian/tests/control. Otherwise all of the
machinery to select which packages are being tested is utterly
defeated.
Ian.
Re: gnupg2 autopkgtest uses multi-arch which seems fragile
Paul Gevers writes ("gnupg2 autopkgtest uses multi-arch which seems fragile"):
> The following packages have unmet dependencies:
> wine32:i386 : Depends: libc6:i386 (>= 2.17) but it is not going to be
> installed
I am at a loss to understand why anything is trying to install wine32
here.
I looked in:
* debian/tests/control in the gnupg2 source tree.
One test, of gpgv-win32. Depends on gpgv-win32, gnupg2,
* debian/control
gpg-win32 Suggests wine. No stronger dependency apparent.
* https://packages.debian.org/sid/gpgv-win32
One dependency: the Suggests on wine.
* ci.d.n "test log" and "test artifacts" from 2018-07-09 04:35:19 UTC.
The artifacts.tar.gz contains only these hits for wine:
$ zgrep wine *
gpgv-win32-stderr.gz:dpkg-query: package 'wine32' is not installed and no
information is available
gpgv-win32-stdout.gz: wine32:i386 : Depends: libc6:i386 (>= 2.17) but it
is not going to be installed
gpgv-win32-stdout.gz: Depends: libwine:i386 (= 3.0.2-1) but
it is not going to be installed
$
The test log is no more informative.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
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. Paul ¹ https://qa.debian.org/excuses.php?package=glibc https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnupg2/580042/log.gz 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 installed 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: ---] signature.asc Description: OpenPGP digital signature
