Comment 6 for bug 1614191

This bug was fixed in the package apt-listchanges - 3.13

---------------
apt-listchanges (3.13) unstable; urgency=low

  * Fix changelog parser to mark files as being in the Debian changelog
    format *before* checking if the latest version has been seen already.
  * Refactor apt-listchanges.py to remove duplicated code.
  * Rewrite main loop of program in order to limit a number of calls to
    `apt-get changelog':
    1. First group packages by the source package and next process all binary
       packages from the same source package at once.
    2. Sort the packages in each group by their binary versions descending.
    3. Exclude those of them whose versions were already seen or are lower
       (except for the binnmu suffix) than the maximal version, i.e. the
       version of the first package in the group.
    4. Process the remaining packages until valid changelog or news entries
       are found, and call `apt-get changelog' on the first package if and
       only if no such changelog entries are found, and apt-listchanges is
       not configured to display the news entries only.
  * Override the LESS environment variable to make sure it does not contain
    certain flags like -F that might cause less program to quit before even
    user is able to see the files generated by the program.
  * Fix an issue with showing changelog entries with unrecognised urgencies
    (see #866358): map such an urgency to a non-zero value and use proper
    `is None' check for testing the mapped value.
  * Fix an exception, introduced in 2.87, occurring when the `--since' option
    is used with the invalid number of `.deb' files. Clarify the error message
    shown in such a case.
  * In the `--verbose' mode when apt-listchanges is configured to display
    `news' only append the informational notes to the news entries instead
    of creating changelog entries.
  * Don't permit `--since' and `--show-all' to be used together. Also make
    sure that passing one of them in the command line overrides any eventual
    config file setting related to the other one.
  * Fix a spelling typo in `retrieve' (closes: #866644).

 -- Robert Luberda <email address hidden> Sat, 01 Jul 2017 13:30:25 +0200