Control: found -1 1.20.1 Hi!
On Fri, 2020-08-14 at 10:00:23 -0400, The Wanderer wrote: > Package: dpkg > Version: 1.20.5 > Severity: normal > 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|?]? Oh, so I guess this is due to you not having a tainted usr-merged system and the readlink failing, due to some recent refactoring. I'll fix that. > 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. This would be reportbug noticing that the bug script failed and reporting that. > 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 assume that until the problem has been fixed in the bug-script, just replying 'y' would do. > 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. The 256 would usually come from the return code of something like a system() call (originally from something like wait(2)), where the code would need to mask the value to get the actual command's exit status. Thanks, Guillem
