Hi Raphael,
On Tuesday, 20 June 2017 16:38:12 CEST Raphael Hertzog wrote:
> The Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of apache2:
> https://security-tracker.debian.org/tracker/CVE-2017-3167
> https://security-tracker.debian.org/track
Hello Raphael and LTS team,
I am on holidays without access to a Debian machine and my keys until June
25th.
If you have time and resources please go on and even fix unstable. In case
you do, please upload your git repo changes to the collab-maint gbp based
c-ares repo. For the last c-ares releas
Hello Christoph & Peter,
The Debian LTS team recently reviewed the security issue(s) affecting your
package in Wheezy:
https://security-tracker.debian.org/tracker/CVE-2016-0767
https://security-tracker.debian.org/tracker/CVE-2016-0768
https://security-tracker.debian.org/tracker/CVE-2016-2192
We d
Hello ruby maintainers,
The Debian LTS team recently reviewed the security issue(s) affecting
ruby1.8 and ruby1.9.1 in Wheezy:
https://security-tracker.debian.org/tracker/CVE-2015-9096
We decided that we would not prepare a wheezy security update because
the issue assumes that malicious content c
Hello Arno & Stefan,
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of apache2:
https://security-tracker.debian.org/tracker/CVE-2017-3167
https://security-tracker.debian.org/tracker/CVE-2017-3169
https://security-tracker.debian.org/tracker/
Hello Gregor,
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of c-ares:
https://security-tracker.debian.org/tracker/CVE-2017-1000381
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined here:
ht
On 20.06.2017 14:30, Raphael Hertzog wrote:
> Hello Matthias,
>
> The Debian LTS team would like to fix the security issue which is
> currently open in the Wheezy version of libffi:
> https://security-tracker.debian.org/tracker/CVE-2017-1000376
>
> Would you like to take care of this yourself?
>
Hello Matthias,
The Debian LTS team would like to fix the security issue which is
currently open in the Wheezy version of libffi:
https://security-tracker.debian.org/tracker/CVE-2017-1000376
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined here:
ht
Hello Andreas,
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of exim4:
https://security-tracker.debian.org/tracker/CVE-2017-1000369
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined here:
ht
Hi,
On Tue, Jun 20, 2017 at 12:56:03PM +0200, Rene Engelhard wrote:
> On Tue, Jun 20, 2017 at 12:16:17PM +0200, Raphael Hertzog wrote:
> > The Debian LTS team would like to fix the security issues which are
> > currently open in the Wheezy version of graphite2:
> > https://security-tracker.debian.
Hi,
On Tue, Jun 20, 2017 at 12:16:17PM +0200, Raphael Hertzog wrote:
> The Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of graphite2:
> https://security-tracker.debian.org/tracker/source-package/graphite2
>
> Last time we had issues, it lo
Dear maintainer(s),
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of graphite2:
https://security-tracker.debian.org/tracker/source-package/graphite2
Last time we had issues, it looks like we switched to a new upstream
release in jessie an
Dear maintainer(s),
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of icedove:
https://security-tracker.debian.org/tracker/source-package/icedove
I expect that Guido will take care of this by switching to a newer
upstream version. Is that
13 matches
Mail list logo
