On 2017-09-07 05:32 +0200, Salvatore Bonaccorso wrote:

> Not a must, and note that is just a comment on my side, I'm not a SRM:
> if possible add a bug closer as well to the changelog entry so that
> when the point release happends, the correct fixed version is as well
> propagated to the BTS bugs.

Heh, it was you who had marked these bugs as found in 6.0+20170715-2 in
the first place. ;-)  Anyway, I have updated the changelog and also
fixed a typo in it.

diff --git a/debian/changelog b/debian/changelog
index 160b2cb1..a75f99e6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,11 +7,12 @@ ncurses (6.0+20161126-1+deb9u1) stretch; urgency=medium
     regression from the above security fixes (see #868266).
   * Cherry-pick upstream fixes from the 20170826 patchlevel for more
     crash bugs in the tic library (CVE-2017-13728, CVE-2017-13729,
-    CVE-2017-13730, CVE-2017-13731, CVE-2017-13732, CVE-2017-13734).
-  * Cerry-pick upstream fixes from the 20170902 patchlevel to fix
-    another crash bug in the tic program (CVE-2017-13733).
+    CVE-2017-13730, CVE-2017-13731, CVE-2017-13732, CVE-2017-13734,
+    Closes: #873723).
+  * Cherry-pick upstream fixes from the 20170902 patchlevel to fix
+    another crash bug in the tic program (CVE-2017-13733, Closes: #873746).
 
- -- Sven Joachim <svenj...@gmx.de>  Mon, 04 Sep 2017 22:04:15 +0200
+ -- Sven Joachim <svenj...@gmx.de>  Thu, 07 Sep 2017 19:05:43 +0200
 
 ncurses (6.0+20161126-1) unstable; urgency=low
 
If a new full debdiff is wanted, please say so.

Cheers,
       Sven

Reply via email to