On Mon, 10 Mar 2025 10:43:52 +0100, Emilio Pozuelo Monfort wrote: > On 10/03/2025 01:36, Gabriel F. T. Gomes wrote: > > I'm seeing autopkgtest failures for libdevice-cdio-perl in the tracker > > for libcdio (excuses panel): > > https://tracker.debian.org/pkg/libcdio > > The failures are in 32-bits architectures, e.g., for i386: > > > > https://ci.debian.net/packages/libd/libdevice-cdio-perl/testing/i386/58673931/
> Did you run it against testing packages, except for libcdio from unstable? > I'm not sure what the failing test is actually doing, as I can't find a > debian/tests/control file, but it's installing build-deps from testing, > which means that it's using/mixing the old libcdio. Right, running the autopkgtest with libdevice-cdio-perl from testing against libcdio from unstable doesn't make sense. From what I see, libdevice-cdio-perl has been binNMUd: https://buildd.debian.org/status/package.php?p=libdevice-cdio-perl and has picked up the right new dependencies: https://release.debian.org/transitions/html/auto-libcdio.html (Note that the same tests passed during the rebuild.) I assume that libcdio and its reverse dependencies have to migrate together; why these autopkgtest in the current form are tried, and if some manual intervention is needed are questions which confuse me for each transition :) Cheers, gregor -- .''`. 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 `- BOFH excuse #244: Your cat tried to eat the mouse.
