Bug#989496: Tagging wontfix

Since this is expected behavior, I am tagging as "wontfix". I don't think it's a good idea to suppress the error message. apt-listchanges gives an "Aborting" message prior to throwing the error. -- Best regards, Brian T B.S. Computer Science 2014 (Truman State University) signature.asc Descri

Bug#869748: Cloned and assigned to aptitude

I cloned this bug and assigned it to the aptitude maintainers. The bug number is #990747. -- Best regards, Brian T B.S. Computer Science 2014 (Truman State University) Minor Stasitics Minor Chemistry Minor Mathematics signature.asc Description: PGP signature

Bug#989496: Looking to change the subject

It was brought to my attention by David K. (thank you, David), that the what you are seeing is intended functionality. I proposed in the email thread with David that we could improve the error message, since right now it may be confusing to users that it is actually expected behavior. A cleaner, c

Bug#939287: Add urgency level separators

On Tue, 03 Sep 2019 03:37:58 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Man page says 'The groups are sorted by the urgency of the most urgent > change, and than by the package name.' > > Alas, that looks like > > A > B > C > A > B > A > B > > to the user. So perhaps add > > --ur

Bug#986840: apt-listchanges fails to parse status files with ^M characters; should use apt_pkg.TagFile, not write its own parser

Julian, I didn't see that you cloned this bug and assigned it to dpkg and that the bug is no longer in apt-listchanges. I still think that your original proposal for apt-listchanges is relevant and is a change worth making. -- Best regards, Brian T signature.asc Description: PGP signature

Bug#986840: apt-listchanges fails to parse status files with ^M characters; should use apt_pkg.TagFile, not write its own parser

> As reported in > https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1854772, > apt-listchanges > fails to parse status files that contain carriage return characters, as > Python normalizes the line endings. I'm tracking the downstream bug in Ubuntu as well as this one. > Instead of

Bug#989496: apt-listchanges: Error output if choosing to not continue after reading list of changes

Tia, Thank you for reporting this bug. I can confirm that this is an issue: apt-listchanges: Do you want to continue? [Y/n] n apt-listchanges: Aborting E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 returned an error code (1) E: Failure running script /usr/bin/apt-listchanges --

Bug#990427: apt-listchanges: Invalid format text for mutt

Package: apt-listchanges Version: 3.24 Severity: normal Dear Maintainer, After performing an installation of a previously uninstalled package, apt-listchanges reported an error: "Invalid format text for mutt" The package still installed, but no changelog or NEWS was shown or emailed out. The e

Bug#926175: tag moreinfo 926175

tags 926175 moreinfo thanks -- Best regards, Brian T signature.asc Description: PGP signature

Bug#926175: apt-listchanges: only a single changelog is shown when multiple packages are updated

Every unexpected behavior is a potential bug. We shouldn't close this bug yet. Nicholas, are you still seeing this behavior? -- Best regards, Brian T signature.asc Description: PGP signature