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

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

[SECURITY] [DLA 457-1] mplayer security update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: mplayer Version: 2:1.0~rc4.dfsg1+svn34540-1+deb7u2 CVE ID : CVE-2016-4352 Mplayer is crashing when playing a fuzzed gif file. The gif demuxes assumes in many places that width*height is <= INT_MAX; this might not

Wheezy update of librsvg?

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

Re: About debian-security-support

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

Re: About debian-security-support

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

Accepted mplayer 2:1.0~rc4.dfsg1+svn34540-1+deb7u2 (source i386 all) into oldstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 May 2016 12:03:02 +0200 Source: mplayer Binary: mplayer-gui mencoder mplayer mplayer-dbg mplayer-doc Architecture: source i386 all Version: 2:1.0~rc4.dfsg1+svn34540-1+deb7u2 Distribution: wheezy-security Urgency: high

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

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

My Debian LTS activities in April 2016

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

Re: Re: Wheezy update of roundcube?

> 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

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

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

[SECURITY] default-java switch to OpenJDK 7 and java-common update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: java-common Version: 0.47+deb7u1 In preparation for the upcoming default-java switch to OpenJDK 7 on 26 June 2016, the java-common package was updated to inform users about the intended change. The news will be

Accepted neobio 0.0.20030929-1+deb7u2 (source all) into oldstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 May 2016 14:37:16 +0200 Source: neobio Binary: neobio Architecture: source all Version: 0.0.20030929-1+deb7u2 Distribution: wheezy-security Urgency: high Maintainer: Debian Med Packaging Team

Accepted java-common 0.47+deb7u1 (source all amd64) into oldstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 May 2016 14:53:46 +0200 Source: java-common Binary: java-common default-jre default-jre-headless default-jdk default-jdk-doc gcj-native-helper Architecture: source all amd64 Version: 0.47+deb7u1 Distribution:

Debian LTS: uploaded packages to wheezy-security not available

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

Re: Wheezy update of roundcube?

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

Re: Wheezy update of roundcube?

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