Your message dated Mon, 19 Feb 2018 11:24:53 +0100
with message-id 
<20180219112453.horde.4akuxp-f_ov6sfzf51jr...@webmail.in-berlin.de>
and subject line Done: Please update to recent git version
has caused the Debian Bug report #870053,
regarding Please update to recent git version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
870053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstrophe
Version: 0.9.1-1
Severity: important
Tags: security

Dear maintainer,

On 4 July 2017 libstrophe has got a security update (see changelog in [1]). Due to missing it, profanity was thrown out from Debian Stable. Please consider updating libstrophe to a recent 0.9.1+git... version (bug fixes, new OpenSSL 1.1.0 support, compilation fix with GCC 7), which will also resolve [2].

[1] https://github.com/strophe/libstrophe/commit/666995531afc610e9fb48049c7134fe45bde0c13 [2] https://bugs.debian.org/857546 (profanity: Server certificates are not verified)

Thanks,
Andrey


P.S. Please reply-all or bugnumber-submit...@bugs.debian.org, so that I also get a reply. P.P.S. I still cannot find what field I must set during submission to tell BTS to subscribe me, reporter, for this new bug, without knowing yet the bug number or sending additional messages later.
--- End Message ---
--- Begin Message ---
Tomasz just updated the package.

--- End Message ---

Reply via email to