Package: src:extrepo-data Version: 1.0.4 User: debian...@lists.debian.org Usertags: ftbfs-during-trixie-support-period Tags: ftbfs
Dear maintainer: During a rebuild of all packages in unstable in the year 2028, your package failed to build: -------------------------------------------------------------------------------- [...] debian/rules build dh build dh_update_autotools_config dh_autoreconf create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary dh_testroot dh_prep dh_auto_install --destdir=debian/extrepo-offline-data/ debian/rules override_dh_install make[1]: Entering directory '/<<PKGBUILDDIR>>' /<<PKGBUILDDIR>>/tools/process Distribution data outdated. Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details. at /usr/share/perl5/Debian/DistroInfo.pm line 159. Unknown Debian release: forky at /<<PKGBUILDDIR>>/tools/process line 30. make[1]: *** [debian/rules:7: override_dh_install] Error 255 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:4: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 -------------------------------------------------------------------------------- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/ftbfs-future/ Note: For this particular package, since it build-depends on distro-info-data, I also tried updating the line in debian.csv about trixie in this way: -13,Trixie,trixie,2023-06-10 +13,Trixie,trixie,2023-06-10,2025-06-10,2028-06-11,2030-06-30,2035-06-30 but that didn't fix the problem. About the archive rebuild: This is an effort to keep trixie free from FTBFS bugs during its lifetime as a supported distribution, as explained here: https://lists.debian.org/debian-devel/2024/05/msg00414.html (While they are not yet, please note that the bugs will be RC for trixie) The build was made using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
