Package: autoconf2.69 Version: 2.69-3 Severity: important Justification: breaking change, not in NEWS, makes draft packages FTBFS Control: block 994770 by -1 Control: block 985563 by -1 Hi, I'm working on packaging binutils-sh-elf, and I know of someone else working on updating binutils-m68hc1x. We're trying to provide these Binutils builds using the best practices recommended at https://wiki.debian.org/PackagingLessCommonBinutilsTargets (which I realize you did not write). To avoid reinventing the wheel, our packages have been using Debhelper, which passes --runstatedir via dh_auto_configure. The most recent changelog entry doesn't indicate that the backport was dropped to resolve any sort of bug, so could it please be reverted for the buildability of our packages? If this won't be reverted, feel free to mark it wontfix and close it. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (2, 'unstable- debug'), (2, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_USER, TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autoconf2.69 depends on: ii autoconf 2.71-2 ii debianutils 4.11.2 ii m4 1.4.18-5 ii perl 5.32.1-5 ii perl-base [libfile-temp-perl] 5.32.1-5 autoconf2.69 recommends no packages. autoconf2.69 suggests no packages. -- no debconf information
Attachment:
signature.asc
Description: This is a digitally signed message part