Bug#1085288: libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl

gregor herrmann gregoa at debian.org
Thu Oct 17 21:20:04 BST 2024


On Thu, 17 Oct 2024 21:47:46 +0200, Paul Gevers wrote:

> Currently this regression is blocking the migration of perl to testing [1].

Ouch.

> Of course, perl shouldn't just break your autopkgtest (or even worse, your
> package), but it seems to me that the change in perl was intended and your
> package needs to update to the new situation. This appears to me the test
> fails on a new warning.

I think this is an unfortunate artifact; and the warning has nothing
to do with perl 5.40 itself, AFAICS.

The warning comes from:

% grep -r "Using UUID::Tiny"
lib/Test2/Util/UUID.pm:    warn "Using UUID::Tiny for uuid generation. UUID::Tiny is significantly slower than the 'UUID' or 'Data::UUID::MT' modules, please install 'UUID' or 'Data::UUID::MT' if possible. If you insist on using UUID::Tiny you can set the TEST2_UUID_NO_WARN environment variable.\n"

This module can use all kinds of UUID* modules, and that's why it has
Depends: …
         libuuid-perl (>= 0.35) | libdata-uuid-mt-perl | libuuid-tiny-perl | libdata-uuid-perl | libossp-uuid-perl
in d/control.

What seems to be happening here is that the first two are not yet
installable in testing (arch:any packages which are part of the
transition and haven't migrated yet), [0] so the third one -- libuuid-tiny-perl --
gets installed which causes this warning. [1]

All going as planned, just that we are running into some corner case
of the Debian machinery (testing migration during transitions vs.
autopkgtests with a mixture of testing and unstable and different
dependency resolution [1]).

So I guess this needs either
- some friendly hint for the autopkgtest system
- or we can add the TEST2_UUID_NO_WARN env variable, which I didn't
  know about before this bug report

I'm happy to do the latter, as it seems fair in general.


Cheers,
gregor

[0] Cf. for the first test -- which needs build dependencies:
130s Some packages could not be installed. This may mean that you have
130s requested an impossible situation or if you are using the unstable
130s distribution that some required packages have not yet been created
130s or been moved out of Incoming.
130s The following information may help to resolve the situation:
130s 
130s The following packages have unmet dependencies:
130s  satisfy:command-line : Depends: libdata-uuid-mt-perl but it is not installable
130s                         Depends: libdata-uuid-perl or
130s                                  libossp-uuid-perl but it is not installable
130s                         Depends: libuuid-perl (>= 0.35) but it is not installable
130s E: Unable to correct problems, you have held broken packages.
131s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from unstable

[1] which doesn't happen at build time as AFAIK buildds only use the
    first alternative

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20241017/57dd1458/attachment-0001.sig>


More information about the pkg-perl-maintainers mailing list