Calling apt-listchanges with a non-package argument causes this crash.
apt-listchanges is meant to be called from apt (during upgrade) or manually, but then you'll have to pass a .deb as argument to it.
Just calling apt-listchanges without any arguments will tell you how to use it:
Usage: apt-listchanges [options] {--apt | filename.deb ...}
There are two issues here:
1. do not crash when e.g. called with "foo" as argument.
2. support package names as arguments, e.g. "apt-listchanges -a apt" would list the changes for apt. However, this is not trivial (using this without "-a" makes not much sense AFAICS and with -a is lists just the whole changelog)
This bug report should be about case 1, the crash (and improved help). Please create a new bug, if you thing "apt-listchanges <package>" makes sense. Thanks.
Calling apt-listchanges with a non-package argument causes this crash.
apt-listchanges is meant to be called from apt (during upgrade) or manually, but then you'll have to pass a .deb as argument to it.
Just calling apt-listchanges without any arguments will tell you how to use it:
Usage: apt-listchanges [options] {--apt | filename.deb ...}
There are two issues here:
1. do not crash when e.g. called with "foo" as argument.
2. support package names as arguments, e.g. "apt-listchanges -a apt" would list the changes for apt. However, this is not trivial (using this without "-a" makes not much sense AFAICS and with -a is lists just the whole changelog)
This bug report should be about case 1, the crash (and improved help). Please create a new bug, if you thing "apt-listchanges <package>" makes sense. Thanks.