NEW changes in stable-new

2016-04-25 Thread Debian FTP Masters 
Processing changes file: libreoffice_4.3.3-2+deb8u4_mips.changes
  ACCEPT

NEW changes in oldstable-new

2016-04-25 Thread Debian FTP Masters 
Processing changes file: eglibc_2.13-38+deb7u10_all.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_amd64.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_armel.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_armhf.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_i386.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_ia64.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_kfreebsd-i386.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_mips.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_mipsel.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_powerpc.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_s390.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_s390x.changes
  ACCEPT
Processing changes file: eglibc_2.13-38+deb7u10_sparc.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_amd64.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_armel.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_armhf.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_i386.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_ia64.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_kfreebsd-i386.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_mipsel.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_powerpc.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_s390.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_s390x.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u1_sparc.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_amd64.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_armel.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_armhf.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_i386.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_ia64.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_kfreebsd-i386.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_mips.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_mipsel.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_powerpc.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_s390.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_s390x.changes
  ACCEPT
Processing changes file: imlib2_1.4.5-1+deb7u2_sparc.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_armel.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_armhf.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_i386.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_ia64.changes
  ACCEPT
Processing changes file: 
libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_kfreebsd-i386.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_mips.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_mipsel.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_powerpc.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_s390.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_s390x.changes
  ACCEPT
Processing changes file: libgd2_2.0.36~rc1~dfsg-6.1+deb7u2_sparc.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_amd64.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_armel.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_armhf.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_i386.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_ia64.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_kfreebsd-i386.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_mips.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_mipsel.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_powerpc.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_s390.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_s390x.changes
  ACCEPT
Processing changes file: tiff_4.0.2-6+deb7u5_sparc.changes
  ACCEPT

Bug#818908: jessie-pu: package dpkg/1.17.27

2016-04-25 Thread Guillem Jover 
Hi!

On Tue, 2016-04-19 at 20:34:19 +0100, Adam D. Barratt wrote:
> Apologies for the delays in getting back to you. Please go ahead.

No problem! Uploaded now too.

Thanks,
Guillem

Bug#818906: wheezy-pu: package dpkg/1.16.18

2016-04-25 Thread Guillem Jover 
Hi!

On Tue, 2016-04-19 at 20:36:32 +0100, Adam D. Barratt wrote:
> Control: tags -1 -moreinfo +confirmed
> 
> On Sun, 2016-03-27 at 12:07 +0200, Guillem Jover wrote:
> > On Wed, 2016-03-23 at 18:07:46 +0100, Guillem Jover wrote:
> > > On Mon, 2016-03-21 at 16:36:16 +0100, Guillem Jover wrote:
> [...]
> > > > Here's a proposed dpkg 1.16.18, with cherry picked fixes from master
> > > > (already in unstable). These include fixes for regressions, memory 
> > > > leaks,
> > > > segmentation faults, portability and interaction with tools such as
> > > > GNU tar or the system shell.
> [...]
> > > The same reply as the one for jessie applies here. I've also taken out
> > > the git log fix here, and I'm attaching the compressed full diff. Let
> > > me know if anything else needs clarification, etc.
> > 
> > Same as for the 1.17.x release, I've removed the string changes in the
> > man page and rerolled the release. Attached the new patch.
> 
> Apologies for the delay in getting back to you. Please go ahead.

No problem! Uploaded now.

Thanks,
Guillem

Bug#822616: jessie-pu: package poppler/0.26.5-2+deb8u1

2016-04-25 Thread Pino Toscano 
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi,

simple jessie-pu for poppler, just fixed in unstable, which fixes
CVE-2015-8868; attached debdiff.

I guess I need to do binary uploads in (old-)stable, right?

Thanks,
-- 
Pino
diff -Nru poppler-0.26.5/debian/changelog poppler-0.26.5/debian/changelog
--- poppler-0.26.5/debian/changelog	2014-10-19 18:24:18.0 +0200
+++ poppler-0.26.5/debian/changelog	2016-04-25 19:02:20.0 +0200
@@ -1,3 +1,11 @@
+poppler (0.26.5-2+deb8u1) stable; urgency=medium
+
+  * Backport upstream commit b3425dd3261679958cd56c0f71995c15d2124433 to fix
+a crash on invalid files, reported also as CVE-2015-8868; patch
+upstream_Do-not-crash-on-invalid-files.patch. (Closes: #822578)
+
+ -- Pino Toscano   Mon, 25 Apr 2016 19:02:11 +0200
+
 poppler (0.26.5-2) unstable; urgency=medium
 
   * Backport upstream commit 01723aa17e836e818158dbdc56df642a290be300 to map
diff -Nru poppler-0.26.5/debian/patches/series poppler-0.26.5/debian/patches/series
--- poppler-0.26.5/debian/patches/series	2014-10-19 17:45:40.0 +0200
+++ poppler-0.26.5/debian/patches/series	2016-04-25 18:39:35.0 +0200
@@ -1,2 +1,3 @@
 upstream_Map-Standard-Expert-encoding-ligatures-to-AGLFN-name.patch
 qt-visibility.diff
+upstream_Do-not-crash-on-invalid-files.patch
diff -Nru poppler-0.26.5/debian/patches/upstream_Do-not-crash-on-invalid-files.patch poppler-0.26.5/debian/patches/upstream_Do-not-crash-on-invalid-files.patch
--- poppler-0.26.5/debian/patches/upstream_Do-not-crash-on-invalid-files.patch	1970-01-01 01:00:00.0 +0100
+++ poppler-0.26.5/debian/patches/upstream_Do-not-crash-on-invalid-files.patch	2016-04-25 18:39:35.0 +0200
@@ -0,0 +1,28 @@
+From b3425dd3261679958cd56c0f71995c15d2124433 Mon Sep 17 00:00:00 2001
+From: Albert Astals Cid 
+Date: Tue, 22 Dec 2015 22:50:33 +0100
+Subject: [PATCH] Do not crash on invalid files
+
+Bug #93476
+---
+ poppler/Function.cc | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/poppler/Function.cc b/poppler/Function.cc
+index 67283df..ee5afc1 100644
+--- a/poppler/Function.cc
 b/poppler/Function.cc
+@@ -577,6 +577,10 @@ ExponentialFunction::ExponentialFunction(Object *funcObj, Dict *dict) {
+   goto err2;
+ }
+ n = obj1.arrayGetLength();
++if (unlikely(n > funcMaxOutputs)) {
++  error(errSyntaxError, -1, "Function's C0 array is wrong length");
++  n = funcMaxOutputs;
++}
+ for (i = 0; i < n; ++i) {
+   obj1.arrayGet(i, );
+   if (!obj2.isNum()) {
+-- 
+2.8.0.rc3
+

Bug#797074: libical2 transition ftbfs bugs now filed

2016-04-25 Thread Andreas Henriksson 
Control: block -1 by 822565 822569 822572

Hello!

The FTBFS bugs for the libical2 transition has now been filed
including trivial patches for all of them.

(Waiting for libical to get through binary-NEW and then likely
follow up with an arm build fix before removing the moreinfo tag.)

Regards,
Andreas Henriksson

Processed: libical2 transition ftbfs bugs now filed

2016-04-25 Thread Debian Bug Tracking System 
Processing control commands:

> block -1 by 822565 822569 822572
Bug #797074 [release.debian.org] transition: libical2
797074 was not blocked by any bugs.
797074 was blocking: 797003
Added blocking bug(s) of 797074: 822569, 822572, and 822565

-- 
797074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#821239: jessie-pu: package ledgersmb/1.3.47-1~deb8u1

2016-04-25 Thread Robert James Clay 
On Friday, April 22, 2016 06:32:15 PM Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
> 
> On Sat, Apr 16, 2016 at 06:52:45PM -0400, Robert James Clay wrote:
> > Please accept ledgersmb_1.3.47-1~deb8u1 for the next Jessie point release.
> > It resolves the issues with the current version of ledgersmb in 'jessie'
> > (1.3.40-1) of the package failing to complete an install without errors.
> Could you expand on the details please? The proposed patch is 139K and:
> 
>  97 files changed, 1286 insertions(+), 623 deletions(-)
> 
> Quite a lot, and the changelog includes words like "New upstream release"
> which immediately rings alarm bells.

Admittedly, the upstream changes come to about 70% of the diff but all of 
those changes between LedgerSMB v1.3.40 and v1.3.47 were bug fixes, not feature 
changes (which didn't happen until the now released but not yet uploaded to 
Debian v1.4.x series), and were unrelated to the issues with the package 
installation errors. And of the upstream versions between those two, only 
v1.3.46-1 was uploaded to Debian and that also turned out to have an package 
installation error, albeit not one as serious as with the 1.3.40-1 package.  
The only way I can see to avoid all that is by creating a 1.3.40-2 package for 
jessie-pu, and backporting the packaging changes as necessary but newer 
upstream versions have already been uploaded so such a package version would 
not be able to go through the usual sequence of unstable -> testing -> jessie-
pu. 

A long standing installation related issue had been that the package 
installation process failed to configure the Ledgersmb DB admin user with the 
necessary credentials when the non-default option to do so was selected.  With 
1.3.40-1 when the debconf option was selected, there was also a "syntax error" 
that came up during the package installation (Debian bug #698298).  That could 
be aborted and one could then run the install/upgrade again, not doing the 
package configuration;  but one would then have to set the user name & password 
for the LedgerSMB Database Admin manually in any case and there were also then 
apache2 related errors that come up resulting from the LedgerSMB Apache 
configuration, which ones depending on if the apache2 package is already 
installed and what modules might already be configured.

With 1.3.46-1, the issue with configuring the LedgerSMB database admin user 
was resolved by dropping the use of dbconfig-common and adding a script 
installed by the package that would directly set user name and password for 
it.  It was also intended to resolve the issues with the LedgerSMB Apache 
configuration but it turned out there was still such an issue, related to 
enabling the Apache rewrite module as necessary with the ledgersmb package 
install.  That in turn was resolved with the 1.3.47-1 package version.

There were other package related changes between 1.3.40-1 and 1.3.47-1 but 
the above summarizes the ones related to the package installation errors, 
which is what I feel is needed to resolve the issue with such errors being 
seen with the current version of LedgerSMB in the current Debian Stable 
('Jessie'). If you have any other questions, please let me know.



Regards,
   Robert James Clay
   j...@rocasa.us


signature.asc
Description: This is a digitally signed message part.

Bug#822540: marked as done (nmu: libapache2-mod-qos_11.25-1)

2016-04-25 Thread Debian Bug Tracking System 
Your message dated Mon, 25 Apr 2016 11:33:12 +0200
with message-id <571de458.30...@debian.org>
and subject line Re: Bug#822540: nmu: libapache2-mod-qos_11.25-1
has caused the Debian Bug report #822540,
regarding nmu: libapache2-mod-qos_11.25-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
822540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Maintainer obviously not built on an up-to-date system.

nmu libapache2-mod-qos_11.25-1 . amd64 . -m "Rebuild against libpng1.6"

Dear Sergey,

This bug could have been easily avoided. 

please make sure that you *always* build on an updated system; even better
use tools like pbuilder or sbuild or like to *ensure* that you have the latest
packages installed.

BEST is, of course, to do source-only uploads, which are possible since ~1.5 
years.
See https://wiki.debian.org/SourceOnlyUpload for details.

Thanks!

-- 
tobi


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On 25/04/16 10:34, Tobias Frost wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> Maintainer obviously not built on an up-to-date system.
> 
> nmu libapache2-mod-qos_11.25-1 . amd64 . -m "Rebuild against libpng1.6"

Scheduled.

Cheers,
Emilio--- End Message ---

Bug#822540: nmu: libapache2-mod-qos_11.25-1

2016-04-25 Thread Emilio Pozuelo Monfort 
On 25/04/16 10:59, Holger Levsen wrote:
> On Mon, Apr 25, 2016 at 10:34:57AM +0200, Tobias Frost wrote:
>> Dear Sergey,
>>
>> This bug could have been easily avoided. 
>>
>> please make sure that you *always* build on an updated system; even better
>> use tools like pbuilder or sbuild or like to *ensure* that you have the 
>> latest
>> packages installed.
> 
> Dear Debian, 
> 
> this bug could have been easily avoided if we wouldn't trust humans to
> not make mistakes: by always throwing away binary uploads by the
> maintainers.
> 
> (SCNR to point this out. But I find it wrong, to blame someone for some
> mistakes, if the bigger mistake is not having structures to prevent such 
> mistakes systematically.)

While throwing away the binaries or rejecting binary uploads would be a nice
thing, it's not the solution to all the problems that building against old
version of packages (or even old releases) have. In any case this is the wrong
place for this discussion...

Cheers,
Emilio

Bug#820193: jessie-pu: package quota/4.01-8

2016-04-25 Thread Michael Meskes 
On Fri, Apr 22, 2016 at 11:53:28PM +0100, Jonathan Wiltshire wrote:
> Could you add Closes for appropriate bugs please?

Sure, new debdiff attached.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
diff -u quota-4.01/debian/changelog quota-4.01/debian/changelog
--- quota-4.01/debian/changelog
+++ quota-4.01/debian/changelog
@@ -1,3 +1,11 @@
+quota (4.01-8+deb8u1) stable-proposed-updates; urgency=medium
+
+  * Change invocation of quota services, so systemd takes over most of the 
work.
+Only the initial check is still performed by the service file provide by
+quota. (Closes: #753939, #788963)
+
+ -- Michael Meskes   Wed, 06 Apr 2016 14:12:06 +0200
+
 quota (4.01-8) unstable; urgency=medium
 
   * Use libtirpc include files to prevent a segfault due to incompatible
diff -u quota-4.01/debian/install quota-4.01/debian/install
--- quota-4.01/debian/install
+++ quota-4.01/debian/install
@@ -4,6 +4,7 @@
 debian/quotaon.sh  /usr/share/quota/
 debian/quotaoff.sh /usr/share/quota/
 debian/quotarpc.sh /usr/share/quota/
+debian/quota-initial-check.sh  /usr/share/quota/
 
 ldap-scripts/applySystemQuotas.pl  /usr/share/quota/ldap
 ldap-scripts/edquota_editor/usr/share/quota/ldap
diff -u quota-4.01/debian/quota.service quota-4.01/debian/quota.service
--- quota-4.01/debian/quota.service
+++ quota-4.01/debian/quota.service
@@ -1,19 +1,15 @@
 [Unit]
-Description=Check And Enable File System Quotas
-Documentation=man:quotaon(8)
+Description=Initial Check File System Quotas
+Documentation=man:quotacheck(8)
 DefaultDependencies=no
-After=systemd-readahead-collect.service systemd-readahead-replay.service 
systemd-remount-fs.service
-Before=sysinit.target shutdown.target
-ConditionPathExists=/usr/share/quota/quotaon.sh
-
-# Make sure quota is correctly stopped.
-Conflicts=shutdown.target
+After=systemd-remount-fs.service
+Before=systemd-quotacheck.service shutdown.target
+ConditionPathExists=/usr/share/quota/quota-initial-check.sh
 
 [Service]
 Type=oneshot
 RemainAfterExit=yes
-ExecStart=/usr/share/quota/quotaon.sh
-ExecStop=/usr/share/quota/quotaoff.sh
+ExecStart=/usr/share/quota/quota-initial-check.sh
 StandardOutput=journal+console
 
 [Install]
only in patch2:
unchanged:
--- quota-4.01.orig/debian/quota-initial-check.sh
+++ quota-4.01/debian/quota-initial-check.sh
@@ -0,0 +1,34 @@
+#!/bin/sh
+
+# names of binaries
+check=/sbin/quotacheck
+on=/sbin/quotaon
+quotaisnew=/var/lib/quota/new
+
+ALLFLAGS=-aug
+CHECKALLFLAGS=${ALLFLAGS}m
+
+set -e
+
+. /lib/lsb/init-functions
+
+# Check if quota has been enabled already
+LC_MESSAGES=C $on -ap|grep -q "is on" && exit 0
+
+# option 'skip' takes precedence even for newly installed quota package 
+skip="no"
+if grep "quotacheck.mode=skip" /proc/cmdline >/dev/null 2>&1; then
+   skip="yes"
+fi
+
+# Check all filesystems if quota is new
+if [ -x $check -a $skip = "no" -a -f $quotaisnew ] ; then
+   log_action_begin_msg 'Checking quotas';
+   $check -c $CHECKALLFLAGS
+   log_action_end_msg 0
+fi
+
+# Remove special file
+rm -f $quotaisnew
+
+exit 0


signature.asc
Description: PGP signature

Bug#822540: nmu: libapache2-mod-qos_11.25-1

2016-04-25 Thread Holger Levsen 
On Mon, Apr 25, 2016 at 10:34:57AM +0200, Tobias Frost wrote:
> Dear Sergey,
> 
> This bug could have been easily avoided. 
> 
> please make sure that you *always* build on an updated system; even better
> use tools like pbuilder or sbuild or like to *ensure* that you have the latest
> packages installed.

Dear Debian, 

this bug could have been easily avoided if we wouldn't trust humans to
not make mistakes: by always throwing away binary uploads by the
maintainers.

(SCNR to point this out. But I find it wrong, to blame someone for some
mistakes, if the bigger mistake is not having structures to prevent such 
mistakes systematically.)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#822540: nmu: libapache2-mod-qos_11.25-1

2016-04-25 Thread Tobias Frost 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Maintainer obviously not built on an up-to-date system.

nmu libapache2-mod-qos_11.25-1 . amd64 . -m "Rebuild against libpng1.6"

Dear Sergey,

This bug could have been easily avoided. 

please make sure that you *always* build on an updated system; even better
use tools like pbuilder or sbuild or like to *ensure* that you have the latest
packages installed.

BEST is, of course, to do source-only uploads, which are possible since ~1.5 
years.
See https://wiki.debian.org/SourceOnlyUpload for details.

Thanks!

-- 
tobi


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#822531: marked as done (nmu: swftools_0.9.2+git20130725-4)

2016-04-25 Thread Debian Bug Tracking System 
Your message dated Mon, 25 Apr 2016 08:40:25 +0200
with message-id <571dbbd9.2080...@debian.org>
and subject line Re: Bug#822531: nmu: swftools_0.9.2+git20130725-4
has caused the Debian Bug report #822531,
regarding nmu: swftools_0.9.2+git20130725-4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
822531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

swftools correctly build-depends on libjpeg-dev, but the amd64 version
(coming from the binary upload by the maintainer) depends on libjpeg8.
Rebuilding in a clean up-to-date environment should fix this.

@Christian Welzel: you are CC'ed because you are the maintainer of
swftools, although there is no action required on your side.
In future uploads, either do source-only uploads (preferred), or at
least upload binaries built in a clean and up-to-date unstable chroot
(e.g. with pbuilder/sbuild/etc).

nmu swftools_0.9.2+git20130725-4 . amd64 . unstable . -m "Rebuild in clean 
environment"

Thanks,
-- 
Pino
--- End Message ---
--- Begin Message ---
On 25/04/16 08:33, Pino Toscano wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> swftools correctly build-depends on libjpeg-dev, but the amd64 version
> (coming from the binary upload by the maintainer) depends on libjpeg8.
> Rebuilding in a clean up-to-date environment should fix this.
> 
> @Christian Welzel: you are CC'ed because you are the maintainer of
> swftools, although there is no action required on your side.
> In future uploads, either do source-only uploads (preferred), or at
> least upload binaries built in a clean and up-to-date unstable chroot
> (e.g. with pbuilder/sbuild/etc).
> 
> nmu swftools_0.9.2+git20130725-4 . amd64 . unstable . -m "Rebuild in clean 
> environment"

Scheduled.

Emilio--- End Message ---

Bug#822531: nmu: swftools_0.9.2+git20130725-4

2016-04-25 Thread Pino Toscano 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

swftools correctly build-depends on libjpeg-dev, but the amd64 version
(coming from the binary upload by the maintainer) depends on libjpeg8.
Rebuilding in a clean up-to-date environment should fix this.

@Christian Welzel: you are CC'ed because you are the maintainer of
swftools, although there is no action required on your side.
In future uploads, either do source-only uploads (preferred), or at
least upload binaries built in a clean and up-to-date unstable chroot
(e.g. with pbuilder/sbuild/etc).

nmu swftools_0.9.2+git20130725-4 . amd64 . unstable . -m "Rebuild in clean 
environment"

Thanks,
-- 
Pino