[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted apt-listchanges 3.13 (source all) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 01 Jul 2017 13:30:25 +0200
Source: apt-listchanges
Binary: apt-listchanges
Architecture: source all
Version: 3.13
Distribution: unstable
Urgency: low
Maintainer: Robert Luberda <robert@debian.org>
Changed-By: Robert Luberda <robert@debian.org>
Description:
 apt-listchanges - package change history notification tool
Closes: 866644
Changes:
 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).
Checksums-Sha1:
 fa7daeaf1380aff0ab187b31d979f34b01b7c1c8 1725 apt-listchanges_3.13.dsc
 3e3cf8295cd6a22c459a2d615c51280046314bd9 121824 apt-listchanges_3.13.tar.xz
 46c88dce6d354809cc6cb74c00376876984fdb75 122264 apt-listchanges_3.13_all.deb
 7bdc18d79bf596bc695a1af3ca6079ecc02fceb9 6121 apt-listchanges_3.13_amd64.buildinfo
Checksums-Sha256:
 67a86e79671400d8e5faa5ec078095b3f39482a4df25616c7d7dfbae6410981e 1725 apt-listchanges_3.13.dsc
 1bb7924c5c5b109583e784e610a170e2fa8ae72d64cbb0a8b3cea15ec34e1cb1 121824 apt-listchanges_3.13.tar.xz
 f8916a09cbb5b11668bac9083a10a6fdfa6cc9fedacf3138ecc386aae9193ac8 122264 apt-listchanges_3.13_all.deb
 9354bc22e10694de11a09f579149b32059c11c66dc63df268912d447f48e624f 6121 apt-listchanges_3.13_amd64.buildinfo
Files:
 1ab4b2d4dda8415e136aa9bc0db52eb6 1725 utils standard apt-listchanges_3.13.dsc
 0357d8d30a054fca2361e33617bf3c1d 121824 utils standard apt-listchanges_3.13.tar.xz
 b8d1dc6ade3fea42dcc442625a4d1328 122264 utils standard apt-listchanges_3.13_all.deb
 58b878f260c6c5e55203efcccc82c93b 6121 utils standard apt-listchanges_3.13_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENeh2+rTTcy6TtNI3Yx3nVTvor9QFAllXiEYACgkQYx3nVTvo
r9RcWQ//aCnjZfCgFpJYm7nz7Ee8sebyx4cnN995K/qBt6BeuQqwO90ux1m7pNlT
meq15LstXzBJnrv0CcMLIq/8qDcHHzMyO1g3KzsIyQxaRpzuoJZKtSmKOw2izLa4
83Zi3uz94sn+KPgEFYp7naGiCtBvvZ5HN6tvI0QqQZa/w1jQGlaJmABbbH0nlHfu
YFK9rO7AOcGU1pu+vWCtOltWlpV0TvFO9bNs9mZbee5oqLoq/zL5dC1ap9PJvyrj
sc+eHh6Ch4UXQJ3bolweEaJC/PX3FJjmg33D8GllqAGOa89U6vnJ0nseZ9BbECy4
iu8PEC0cvICqq1KdR0xydCI7NKB8uM5rnCAYqZGbfG249VKCVvjz1ih1msOIoSYX
t+nOQrBkqUqY9FxngJdIgsCPvizWkzOD7fO9yyuQXL79+I8USxX+FHgIyvTqWu4M
Nb2xkd8/lS97E3xZ0+l4WEHM/X1k3waguQRYIVTqcXBVMUr3hmsWbIVi+ZSJ9OIT
gLxpqUj837CUp2e6V1+mH7L4WQwZf2x0QvIJMQHShkb9XflepW7lMt5Yu3Egx+fh
pC60ybGJyX8KZ3pL+leyEeo1T8HiojQ+eZA1Zw4I/rD46Tmj/XK2mAMiB0XuhkG2
SAtmEOqGmxtM+cjSdBZB3GGJO/ZgfzkSYPGY5dTPDyC4Rqizu4E=
=X0KX
-----END PGP SIGNATURE-----


Reply to: