Wheezy update of libuser?

2016-05-04 Thread Markus Koschany
Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of libuser: https://security-tracker.debian.org/tracker/CVE-2015-3246 https://security-tracker.debian.org/tracker/CVE-2015-3245 Would you like to take care of this yo

Xen 4.1.6.1 backport + Ubuntu patches ready for testing (take 3)

2016-05-04 Thread Antoine Beaupré
Hi, TL;DR: debdiff below, features only changes to debian/changelog and debian/patches (apart from the upstream upgrade of course). Binary packages in: https://people.debian.org/~anarcat/debian/wheezy-lts/ Long story follows... So I *believe* I have correctly completed the backport of

Wheezy update of librsvg?

2016-05-04 Thread Markus Koschany
Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of librsvg: https://security-tracker.debian.org/tracker/CVE-2016-4348 https://security-tracker.debian.org/tracker/CVE-2016-4347 Would you like to take care of this yo

Re: About debian-security-support

2016-05-04 Thread Markus Koschany
Am 04.05.2016 um 21:07 schrieb Raphael Hertzog: [...] >> 2. Should it be uploaded to wheezy-security even if it doesn't fix any >>security fix? Or does the wheezy queue in ftp-master still works >>(with ftp-masters' participation)? > > We were aware that we would have some non-security upl

Re: Please remove non-lts architectures from wheezy-security

2016-05-04 Thread Ben Hutchings
On Wed, 2016-05-04 at 19:42 +0100, Adam D. Barratt wrote: > On Wed, 2016-05-04 at 18:51 +0100, Ben Hutchings wrote: > > > > As I understand it, packages are never moved directly from oldstable- > > security to archive.debian.org.  Normally they are copied to oldstable > > in a final point release,

Re: About debian-security-support

2016-05-04 Thread Raphael Hertzog
Hi, On Wed, 04 May 2016, Santiago Ruano Rincón wrote: > 1. I had included in the pu/wheezy-lts branch changes to close >https://bugs.debian.org/818843 thinking that it was useful for >wheezy-lts users. But uploads to wheezy (and stable) should be >limited to updating the status list fi

Re: Please remove non-lts architectures from wheezy-security

2016-05-04 Thread Adam D. Barratt
On Wed, 2016-05-04 at 18:51 +0100, Ben Hutchings wrote: > As I understand it, packages are never moved directly from oldstable- > security to archive.debian.org. Normally they are copied to oldstable > in a final point release, and then moved to archive.debian.org. In > this case, there was a poi

Re: Please remove non-lts architectures from wheezy-security

2016-05-04 Thread Ben Hutchings
On Wed, 2016-05-04 at 16:48 +0200, Tom Turelinckx wrote: > Hello Paul, > > This approach works fine, thanks for the suggestion: > > deb http://ftp.be.debian.org/debian wheezy main contrib non-free > deb-src http://ftp.be.debian.org/debian wheezy main contrib non-free > > deb http://ftp.be.debian

My Debian LTS activities in April 2016

2016-05-04 Thread Santiago Ruano Rincón
Hi everybody, The last month of April, I had available 15 hours in total paid by Freexian to work on LTS, but I have only spent 7.5. This is mainly what I did: * mysql-5.5: handle the new upstream version of the package prepared by Lars Tangvald, test it, and upload the [DLA 447-1](https://l

About debian-security-support

2016-05-04 Thread Santiago Ruano Rincón
Hi, After uploading a debian-security-support release to unstable, I have some doubts about what we are able to upload to wheezy, and I prefer to ask :) 1. I had included in the pu/wheezy-lts branch changes to close https://bugs.debian.org/818843 thinking that it was useful for wheezy-lts u

Re: Re: Wheezy update of roundcube?

2016-05-04 Thread Adrian Zaugg
> On Tue, 03 May 2016 at 10:47:31 -0400, Antoine Beaupré wrote: >> I agree, however I suspect most people using roundcube in production are >> probably using the backport... There's even a dangling backport in >> wheezy right now (0.9)... a little messy. > Am 03.05.2016 um 17:49 schrieb Guilhem Mo

RE: Please remove non-lts architectures from wheezy-security

2016-05-04 Thread Tom Turelinckx
Hello Paul, This approach works fine, thanks for the suggestion: deb http://ftp.be.debian.org/debian wheezy main contrib non-free deb-src http://ftp.be.debian.org/debian wheezy main contrib non-free deb http://ftp.be.debian.org/debian wheezy-updates main contrib non-free deb-src http://ftp.be.de

Debian LTS: uploaded packages to wheezy-security not available

2016-05-04 Thread Markus Koschany
Hi Ansgar, In preparation for the default Java switch I have uploaded more packages to wheezy-security yesterday and most of them are available in the archive now. However some of them never showed up there, although I made sure to build with -sa. I guess there is an issue with dak again. The fol

Re: Wheezy update of roundcube?

2016-05-04 Thread Gabriel Moreau
For instance, I run the unstable wordpress on a wheezy machine. And each wordpress upgrade is painless, but a full upgrade to jessie would be much more time consuming. I agree for wordpress. But roundcube is a litle different. You don't have to run it on the email serveur. It's just a box wi

Re: Wheezy update of roundcube?

2016-05-04 Thread Raphael Hertzog
Hi, On Tue, 03 May 2016, Moritz Muehlenhoff wrote: > What's the point in updating a server package like roundcube in LTS > to the version from LTS+1? I creates significant churn on the sysadmin's > side, which is better spent on upgrading the entire VM/machine to LTS+1. I don't think this is enti