Re: squeeze update of gtk+2.0?

i can test the uploads, what must be doit? how, i'm using squeze on many of my hardware due wheeze and jeesie are very slowly for the older hardware 2016-02-23 18:38 GMT-04:30, Michael Biebl : > Am 23.02.2016 um 23:59 schrieb Santiago Ruano Rincón: >> Hello dear maintainer(s),

Re: squeeze update of gtk+2.0?

Am 23.02.2016 um 23:59 schrieb Santiago Ruano Rincón: > Hello dear maintainer(s), > > the Debian LTS team would like to fix the security issues which are > currently open in the Squeeze version of gtk+2.0 and relate to > gdk-pixbuf: >

squeeze update of gtk+2.0?

Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of gtk+2.0 and relate to gdk-pixbuf: https://security-tracker.debian.org/tracker/source-package/gtk+2.0 A user have noticed me about these issues, originally filed

Re: squeeze update of libssh2?

On Tue, 2016-02-23 at 16:34 +0100, Chris Lamb wrote: > Hello dear maintainer(s), > > the Debian LTS team would like to fix the security issues which are > currently open in the Squeeze version of libssh2: > https://security-tracker.debian.org/tracker/CVE-2016-0787 [...] I already fixed both

Re: squeeze update of libssh2?

Hi. I'm very busy IRL right now, please proceed on your own. Thanks. On 23 Feb 2016, at 16:34, Chris Lamb wrote: Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of libssh2:

squeeze update of libssh?

Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of libssh: https://security-tracker.debian.org/tracker/CVE-2016-0739 Would you like to take care of this yourself? If yes, please follow the workflow we have

[SECURITY] [DLA 426-1] libssh2 security update

Package: libssh2 Version: 1.2.6-1+deb6u2 CVE ID : CVE-2016-0787 Andreas Schneider reported that libssh2, an SSH2 protocol implementation used by many applications, did not generate sufficiently long Diffie-Hellman secrets. This vulnerability could be exploited by an

squeeze update of tomcat6?

Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of tomcat6: https://security-tracker.debian.org/tracker/CVE-2015-5174 https://security-tracker.debian.org/tracker/CVE-2015-5345

squeeze update of websvn?

Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of websvn: https://security-tracker.debian.org/tracker/CVE-2016-2511 Would you like to take care of this yourself? If yes, please follow the workflow we have

Re: Upgrading from Debian 6.0 LTS to 7

On Mon, 22 Feb 2016, Alexis Grigoriou wrote: This is the approach I took and all went well, except for a few packages that I needed to install manually and a message from mysql "Could not perform immediate configuration on 'mysql-server-5.5" Which I had to install manually with it's

Re: wheezy-security to wheezy-lts transition

On Mon, 22 Feb 2016, Holger Levsen wrote: > does that even work? AIUI this would require LTS uploaders > to have access to security.d.o, which won't happen because > of embargoed issues… Access to security.d.o is only needed if you have to approve the uploads. Here the suite will be

Re: wheezy-security to wheezy-lts transition

Hi, On Tue, 23 Feb 2016, Guido Günther wrote: > > > > > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=prep-wheezy-lts;users=debian-lts@lists.debian.org > > > > While these two are long-standing enhancement bugs which would make > > the security team work much easier, they are

Re: wheezy-security to wheezy-lts transition

Hi, On Montag, 22. Februar 2016, Guido Günther wrote: > > As I understand it, the plan is for wheezy-lts to re- use > > security.d.o:wheezy/updates directly, rather than a separate suite on > > ftp-master. Is that correct? > > I think so. See > > >