Package: dpkg Version: 1.20.5 Severity: normal Dear Maintainer,
When I attempt to file a bug report against dpkg with reportbug, I get the following output: The package bug script /usr/share/bug/dpkg exited with an error status (return code = 256). Do you still want to file a report? [y|N|q|?]? It is not clear whether this reflects a problem that will manifest itself in the resulting bug report, but at the minimum, it is clearly suboptimal UX. If it does reflect a real problem, that problem should be fixed; if it does not, it should be streamlined so that this notice does not appear in routine bug-report attempts. As things stand, I have another bug report which I would like to file (which might belong either to dpkg or to locales-all, or even somewhere else I can't identify at a glance, but I think fits dpkg as the most likely candidate) which is on hold because of this. I'm not sure where to look on my system for anything that might be contributing to the problem; I've already checked the script itself, and tried running various commands and scripts based on what I find there, without reproducing the 256 exit code as of yet. If there's anything I can do to help track this down, don't hesitate to ask. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages dpkg depends on: ii libbz2-1.0 1.0.8-4 ii libc6 2.31-3 ii liblzma5 5.2.4-1+b1 ii libselinux1 3.1-2 ii tar 1.30+dfsg-7 ii zlib1g 1:1.2.11.dfsg-2 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 2.1.10 pn debsig-verify <none> -- no debconf information
