On Sun, Jan 26, 2025 at 12:39:52AM +0500, Andrey Rakhmatullin wrote: > On Sat, Jan 25, 2025 at 07:17:52PM +0000, Tim Woodall wrote: > > I know this is experimental and so breakage is expected but it seems to > > have been like this for a while now so I'm reporting it here in case > > it's been missed. > > You may be confused, as perl 5.40.1-1 was only uploaded to experimental a > week ago, but also in general it's expected that stuff with a new ABI in > experimental is not installable in unstable. That's why we have > transitions. It also shouldn't be unique to libclass-xsaccessor-perl, > there are several packages in unstable that aren't coinstallable with a > too new perl.
Yes, this is indeed expected behaviour. We're using experimental as a staging ground for testing out new upstream Perl releases to ensure that the actual transition will be as painless as possible. Updating all required reverse dependencies in experimental accordingly and keeping them up to date would be too much of a burden however (and step on other maintainers' toes), so we're using a separate test repository [1] for that. This is mostly geared for major Perl upstream releases, where 600+ packages need rebuilds. The minor Perl upstream releases (like 5.40.1 here) are ABI compatible, so most packages stay installable, but there's still a handful of packages depending on the specific upstream version they were built with for various reasons [2]. libclass-xsaccessor-perl is one of these and will be rebuilt for Perl 5.40.1 when that enters unstable. FWIW my tests with 5.40.1 look good so far (both rebuilds and autopkgtest), but I'm not quite finished yet. [1] https://perl.debian.net/ [2] https://wiki.debian.org/PerlMaintenance#Point_releases_only > I'd say you are just not supposed to install random packages from > experimental... Indeed. -- Niko Tyni nt...@debian.org
