After discussion in IRC, I now understand that a bug can be closed more than once, which seems a little counter-intuitive at first, but I get why. Here's the updated debdiff with the bug close included. Hopefully this is the final one. Apologies for the extra noise. sney On Mon, Apr 11, 2016 at 12:07 PM, Jesse Rhodes <sney@drubo.net> wrote: > The relevant debian bug was already closed (by some guy named Mattia > Rizzolo ;), so I've just done the latter 2 suggestions. > > Please see the attached debdiff and let me know if there's anything else. > > On Thu, Apr 7, 2016 at 3:41 AM, Mattia Rizzolo <mattia@debian.org> wrote: >> On Thu, Mar 31, 2016 at 10:31:13AM -0600, Jesse Rhodes wrote: >>> Debdiff attached. >> >> You should also close the relevant bug in the BTS; and now there is also >> (finally!) a CVE id, please add it to the changelog (and why not to the >> patch description can't harm too). >> >> #818009 aka CVE-2013-7449 >> >> -- >> regards, >> Mattia Rizzolo >> >> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. >> more about me: http://mapreri.org : :' : >> Launchpad user: https://launchpad.net/~mapreri `. `'` >> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
hexchat-2.10.1-1+deb8u1.debdiff
Description: Binary data