[Pkg-xmpp-devel] Bug#1016751: gsasl: autopkgtest regression on armel: new test has dependency that isn't available

[Simon Josefsson]

Paul Gevers <elbrus at debian.org> writes:

> Dear maintainer(s),
>
> With a recent upload of gsasl the autopkgtest of gsasl fails in
> testing when that autopkgtest is run with the binary packages of gsasl
> from unstable on armel. It passes when run with only packages from
> testing. In tabular form:
>
>                        pass            fail
> gsasl                  from testing    2.0.1-2
> all others             from testing    from testing
>
> After checking your changelog, I noticed you added a test and exactly
> this test fails because the test dependencies can't be
> installed. Please add a "Architecture: !armel" line to the third test
> definition.

Hi.  Reading the test log, it looks like the problem is that 'valgrind'
wasn't available on that architecture.  Rather than !armel locally, the
package now use the 'valgrind-if-available' package instead -- what do
you think?  Let's see if it builds now.

/Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 255 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-xmpp-devel/attachments/20220806/a9b76d32/attachment.sig>