freeimage_3.15.4-5_source.changes ACCEPTED into unstable

2015-09-18 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Sep 2015 22:50:49 +0200 Source: freeimage Binary: libfreeimage-dev libfreeimage3 libfreeimage3-dbg Architecture: source Version: 3.15.4-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed

Bug#797165: marked as done (CVE-2015-0852: integer overflow in PluginPCX.cpp)

2015-09-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Sep 2015 19:50:37 + with message-id and subject line Bug#797165: fixed in freeimage 3.15.4-5 has caused the Debian Bug report #797165, regarding CVE-2015-0852: integer overflow in PluginPCX.cpp to be marked as done. This means that you claim that the problem has bee

rafkill_1.2.2-5_source.changes ACCEPTED into unstable

2015-09-18 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Sep 2015 18:09:14 +0200 Source: rafkill Binary: rafkill rafkill-data Architecture: source Version: 1.2.2-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Santiago Vila Descripti

Processing of rafkill_1.2.2-5_source.changes

2015-09-18 Thread Debian FTP Masters
rafkill_1.2.2-5_source.changes uploaded successfully to localhost along with the files: rafkill_1.2.2-5.dsc rafkill_1.2.2-5.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

Bug#784859: Workaround considered annoying at best

2015-09-18 Thread Andreas Beckmann
On 2015-09-18 11:36, "David Prévot" wrote: >> Package: ampache > > You’re not even looking at the right package, and no: > > Package: ampache-common Oops ... right, that tells a different story. At least this "workaround" seems to have worked in the past. I don't mind doing rebuild-only QA uplo

Bug#784859: Workaround considered annoying at best

2015-09-18 Thread David Prévot
Hi, > On Wed, 16 Sep 2015 10:23:24 -0400 David =?UTF-8?Q?Pr=C3=A9vot?= > wrote: >> unarchive 784859 >> # Rebuilding is a workaround, it does *not* address the problem. >> reopen 784859 > > AFAICT rebuilding with an updated toolchain actually got rid of the > strict versioning (without changing so