Dear Maintainer,

After reading list of changes decided not to upgrade, so chose 'n' when
asked. As such apt-listchanges aborted as it should, only issue is that
after that it would output error message

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
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 --apt || test $? -lt 10

There is no issues in functionality after that if run again.

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 --apt || test $? -lt 10

I believe I have found the issue and have a fix ready to go.  I'll
set the status to pending.

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, clearer error message should resolve any confusion.

I will CC you Tia.

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.

I am confused about why this is filed against apt-listchanges rather
than apt. It's apt that's generating the error message when the
apt-listchanges command exits with a non-zero status. There's no way
apt-listchanges can influence what the error looks like; if we want it
to be prettier, we'll have to change apt. Am I missing something?