Bug#831365: ITP: lepton -- tool to compress JPEGs losslessly

[Tomasz Buchert]

On 15/07/16 09:20, ChangZhuo Chen (陳昌倬) wrote:
> [...]

Hi Chen,
if you need help with this, let me know. I wanted to package this
myself. There are some issues that I encountered, but these patches
from FreeBSD [1] should be helpful.

Cheers,
Tomasz

[1] https://svnweb.freebsd.org/ports/head/graphics/lepton/files/


signature.asc
Description: PGP signature

Bug#831365: ITP: lepton -- tool to compress JPEGs losslessly

[陳昌倬]

On Fri, Jul 15, 2016 at 08:46:22AM +0200, Tomasz Buchert wrote:
> On 15/07/16 09:20, ChangZhuo Chen (陳昌倬) wrote:
> Hi Chen,
> if you need help with this, let me know. I wanted to package this
> myself. There are some issues that I encountered, but these patches
> from FreeBSD [1] should be helpful.

Hi Tomasz,

The repo is in http://anonscm.debian.org/git/collab-maint/lepton.git/.
Feel free to commit to it.


-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#830308: d-i.debian.org: l10n-sync script breaks headers in individual package files in some situations

[Christian PERRIER]

Quoting Steve McIntyre (st...@einval.com):

> Arg, sorry. :-( It's very easy to make mistakes when editing large
> numbers of files like this by hand. I double-checked the diffs,
> even. Could we add some commit-time checking to run msgfmt etc. and
> warn on errors?

Yes, this is exactly what I did in l10n-sync before reverting the
changes. It has been tested locally with the "broken" files in place
and the script stopped as expected before committing.

Indeed, the breakage happened when the 5 "sublevels" PO files for
Banish and Belarusian are temporarily concatenated into one single PO
file, which "msgcat". The single PO file is then used for synchronize
the PO files in individual packages.

The "msgcat" command (line 585 in l10n-sync) was indeed not protected
by error handling in our scripts, while most gettext commands are.

The fix I committed added a prior test of merged PO files with "msgfmt
-c" (and exiting if that fails) and I just added one more error
handling in the "msgcat" command itself.




signature.asc
Description: PGP signature

Bug#831004: procps: FTBFS on hurd-i386: mv: cannot stat 'kill'

[Sven Joachim]

Control: tags -1 + patch

On 2016-07-13 13:12 -0400, Aaron M. Ucko wrote:

> The hurd-i386 build of procps gets farther now (thanks!) but still fails:
>
>   mv /«PKGBUILDDIR»/debian/tmp/bin/kill /«PKGBUILDDIR»/debian/tmp/bbin/
>   [...]
>   (cd /«PKGBUILDDIR»/debian/tmp/bin && mv kill kill.procps )
>   mv: cannot stat 'kill': No such file or directory
>   debian/rules:44: recipe for target 'override_dh_auto_install' failed
>
> The problem appears to be interference from the bbin/ setup, which
> alas doesn't work as (presumably) intended anyway because dh_install
> always treats destinations as directories:

It seems that debian/rules does everything correctly for hurd and only
the install file is broken.  I have attached a fix for it.

>Package: procps
>Version: 2:3.3.12-2
>Architecture: kfreebsd-i386
>   [...]
>   
>   drwxr-xr-x root/root 0 2016-07-13 11:20 ./
>   drwxr-xr-x root/root 0 2016-07-13 11:20 ./bin/
>   drwxr-xr-x root/root 0 2016-07-13 11:20 ./bin/kill.procps/
>   -rwxr-xr-x root/root 21920 2016-07-13 11:20 ./bin/kill.procps/kill

Reported separately as #831348.

Cheers,
   Sven

>From 0b60ee5dfb6c2485157e7f4826e07a0331f5146f Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Fri, 15 Jul 2016 07:43:31 +0200
Subject: [PATCH] Fix install file on hurd

The kill and ps programs are already renamed in debian/rules, no need
to do that in the install file which does not work correctly anyway.
---
 debian/procps.install.hurd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/procps.install.hurd b/debian/procps.install.hurd
index 77ac1e2..df864c7 100644
--- a/debian/procps.install.hurd
+++ b/debian/procps.install.hurd
@@ -1,4 +1,4 @@
 # Files to install for hurd systems
-bbin/kill bin/kill.procps
-bbin/ps bin/ps.procps
+bbin/kill.procps bin
+bbin/ps.procps bin
 bin/* /usr/bin
-- 
2.8.1

Bug#831348: procps: includes /bin/kill.procps/kill on kfreebsd

[Sven Joachim]

Control: tags -1 + patch

On 2016-07-14 21:25 +0200, Sven Joachim wrote:

> Package: procps
> Version: 2:3.3.12-2
>
> After the fix for bug #816237, the procps.install files for kfreebsd and
> hurd install kill(1) as /bin/kill.procps/kill.  I suppose that is not
> what has been intended, but sadly it is not possible to rename files
> with dh_install (unless you make them executable and run them via
> dh_exec, that is).

Attached is a patch which should fix that.  I am fairly confident that
it works, but as I don't have a kfreebsd system it is not tested.

Cheers,
   Sven

>From eca4ea81fd9c81142fb575df6a40ca44e05969af Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Fri, 15 Jul 2016 07:38:17 +0200
Subject: [PATCH] Fix path for kill on kfreebsd systems

Use the same code as for hurd in debian/rules and rename kill to
kill.procps there rather than trying to do it in the install file
which does not work as intended.  This has the additional advantage
that there will be a manpage for kill.procs.
---
 debian/procps.install.kfreebsd |  2 +-
 debian/rules   | 13 -
 2 files changed, 5 insertions(+), 10 deletions(-)

diff --git a/debian/procps.install.kfreebsd b/debian/procps.install.kfreebsd
index 186d81b..0dcae1a 100644
--- a/debian/procps.install.kfreebsd
+++ b/debian/procps.install.kfreebsd
@@ -1,4 +1,4 @@
 # Files to install for kfreebsd systems
-bbin/kill bin/kill.procps
+bbin/kill.procps bin
 bbin/ps bin
 bin/* /usr/bin
diff --git a/debian/rules b/debian/rules
index 111491e..0414541 100755
--- a/debian/rules
+++ b/debian/rules
@@ -59,21 +59,16 @@ ifneq ($(DEB_HOST_ARCH_OS), linux)
 		$(DEBROOT)/usr/share/man/man8/sysctl.8 \
 		$(DEBROOT)/usr/share/man/man5/sysctl.conf.5 \
 		$(NULL)
-endif
-ifeq ($(DEB_HOST_ARCH_OS), kfreebsd)
-	rm -f \
-		$(DEBROOT)/bin/kill \
-		$(DEBROOT)/usr/share/man/man1/kill.1 \
-		$(NULL)
+
+# Rename kill as there are two of them
+	(cd $(DEBROOT)/bin && mv kill kill.procps )
+	(cd $(DEBROOT)/usr/share/man/man1 && mv kill.1 kill.procps.1 )
 endif
 ifeq ($(DEB_HOST_ARCH_OS), hurd)
 	rm -f \
 		$(DEBROOT)/bin/pmap \
 		$(DEBROOT)/usr/share/man/man1/pmap.1 \
 		$(NULL)
-# Rename kill as there are two of them
-	(cd $(DEBROOT)/bin && mv kill kill.procps )
-	(cd $(DEBROOT)/usr/share/man/man1 && mv kill.1 kill.procps.1 )
 
 	# Rename vmstat as there are two of them
 	(cd $(DEBROOT)/bin && mv vmstat vmstat.procps )
-- 
2.8.1

Bug#829088: ccache may silently miscompile symlinked source files

[Jaap Keuter]

Don't the release notes of the next version address this?
https://ccache.samba.org/releasenotes.html#_ccache_3_2_6

On Thu, 30 Jun 2016 23:08:05 +0200 Joel Rosdahl  wrote:
> Thanks for the bug report. I have reproduced the issue, see the attached
> script. Yes, to trigger the bug, the source file path must be absolute and
> CCACHE_BASEDIR must be enabled.
> 
> The behavior change in question comes from this commit: <
> https://github.com/ccache/ccache/commit/2df269a3121889ebcdfa5d98dfb4d675f690e039>.
> It's included in ccache 3.1.8 and newer.
> 
> Not sure what to do, though. Have to think about it some more.
> 
> -- Joel
> 
> On 30 June 2016 at 14:15, Stefan Fritsch  wrote:
> 
> > found 829088 3.2.5-1
> > thanks
> >
> > Version 3.2.5-1 is also affected by this issue.
> >
> > Attached is a log file from that version.
> >
> > Since the path names are rather complicated in the examples: The dir with
> > the symlinked source files is (note the obj in the 3rd component):
> >
> >
> > /changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc-minimal/libc/src/libc/stdlib/malloc-standard/free.c
> >
> > The path to the source file with all symlinks resolved is (there is no
> > obj/ and no amd64/ in this path):
> >
> >
> > /changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/contrib/uclibc/libc/stdlib/malloc-standard/free.c

Bug#831368: live-wrapper: output live.iso not isohybrid, cannot be booted from thumb drive

[Michael .]

Wow I'm impressed you got that far.
All I get is an empty folder and a log file that I cant read.
I was going to test it tomorrow morning and if nothing different occurs was
going to file a bug report then.

On 15 July 2016 at 12:16, Ben Caradoc-Davies  wrote:

> Package: live-wrapper
> Version: 0.3
> Severity: normal
>
> Dear Maintainer,
>
> the output live.iso produced by lwr has neither MBR nor any partitions
> (MBR or
> GPT). It appears to be a plain ISO image. It cannot be booted from a thumb
> drive.
>
> Kind regards,
> Ben.
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages live-wrapper depends on:
> ii  python-cliapp  1.20160316-1
> pn  python:any 
> ii  vmdebootstrap  1.5-1
>
> live-wrapper recommends no packages.
>
> live-wrapper suggests no packages.
>
> -- no debconf information
>
>

Bug#828733: ITP: python-osc-lib -- OpenStackClient Library

[Jeremy Bicha]

Control: forcemerge 830874 828733

This package has already been uploaded by the Debian OpenStack packagers team.

https://tracker.debian.org/pkg/python-osc-lib

Thanks,
Jeremy Bicha

Bug#817375: bibcursed: Removal of debhelper compat 4

[Logan Rosen]

Package: bibcursed
Version: 2.0.0-6
Followup-For: Bug #817375
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 9.
  * debian/control: Build-depend on debhelper (>= 9).
  * debian/rules:
- Add recommended build-arch and build-indep targets.
- Use dh_prep instead of dh_clean -k.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u bibcursed-2.0.0/debian/compat bibcursed-2.0.0/debian/compat
--- bibcursed-2.0.0/debian/compat
+++ bibcursed-2.0.0/debian/compat
@@ -1 +1 @@
-4
+9
diff -u bibcursed-2.0.0/debian/control bibcursed-2.0.0/debian/control
--- bibcursed-2.0.0/debian/control
+++ bibcursed-2.0.0/debian/control
@@ -1,9 +1,8 @@
 Source: bibcursed
 Section: tex
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: John Wright 
-Build-Depends: debhelper (>= 4), libncurses5-dev
+Maintainer: John Wright 
+Build-Depends: debhelper (>= 9), libncurses5-dev
 Standards-Version: 3.7.2
 
 Package: bibcursed
diff -u bibcursed-2.0.0/debian/rules bibcursed-2.0.0/debian/rules
--- bibcursed-2.0.0/debian/rules
+++ bibcursed-2.0.0/debian/rules
@@ -34,7 +34,9 @@
 	dh_clean
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -46,7 +48,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	install -D -m 0755 $(CURDIR)/bibcursed \

Bug#830948: NOT fixed in plasma-discover 5.7.0-3

[Andrew DeMarsh]

This bug is not fixed in plasma-discover 5.7.0-3.
See below:

Unpacking plasma-discover-common (5.7.0-3) over (5.6.5-1) ...
dpkg: error processing archive
/var/cache/apt/archives/plasma-discover-common_5.7.0-3_all.deb
(--unpack):
 trying to overwrite
'/usr/share/libdiscover/backends/knsplasmoids-backend.desktop', which
is also in package plasma-discover-private 5.6.5-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Bug#827649: gitlab: Git pull/push over ssh fails with: "fatal: protocol error: bad line length character: API"

[Pirate Praveen]

Another possibility is a bug in addressable 2.4.

https://github.com/sporkmonger/addressable/issues/234

Can you try with addressable 2.3.8?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing

[Diederik de Haas]

> It looks like -17 reached linux-firmware.git a few hours ago. Maybe
> it's time to update firmware-nonfree?

Yes please, as it also contains iwlwifi-7265D-21.ucode which was needed for my 
ASUS ZenBook UX305CA.
I managed to workaround it, but I doubt the average user would.

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

Bug#817374: bbmail: Removal of debhelper compat 4

[Logan Rosen]

Package: bbmail
Version: 0.8.3-6
Followup-For: Bug #817374
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 9.
  * debian/control: Build-depend on debhelper (>= 9).
  * debian/rules:
- Add recommended build-arch and build-indep targets.
- Use dh_prep instead of dh_clean -k.
  * debian/control: Add Homepage field with working URL (and remove old one
from description).
  * debian/copyright: Don't point to symlink GPL.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u bbmail-0.8.3/config.guess bbmail-0.8.3/config.guess
--- bbmail-0.8.3/config.guess
+++ bbmail-0.8.3/config.guess
@@ -1,14 +1,12 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-#   2011 Free Software Foundation, Inc.
+#   Copyright 1992-2015 Free Software Foundation, Inc.
 
-timestamp='2011-05-11'
+timestamp='2015-08-20'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# the Free Software Foundation; either version 3 of the License, or
 # (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful, but
@@ -17,26 +15,22 @@
 # General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
-# 02110-1301, USA.
+# along with this program; if not, see .
 #
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-
-# Originally written by Per Bothner.  Please send patches (context
-# diff format) to  and include a ChangeLog
-# entry.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 #
-# This script attempts to guess a canonical system name similar to
-# config.sub.  If it succeeds, it prints the system name on stdout, and
-# exits with 0.  Otherwise, it exits with 1.
+# Originally written by Per Bothner; maintained since 2000 by Ben Elliston.
 #
 # You can get the latest version of this script from:
 # http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
+#
+# Please send patches to .
+
 
 me=`echo "$0" | sed -e 's,.*/,,'`
 
@@ -56,9 +50,7 @@
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free
-Software Foundation, Inc.
+Copyright 1992-2015 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -140,12 +132,33 @@
 UNAME_SYSTEM=`(uname -s) 2>/dev/null`  || UNAME_SYSTEM=unknown
 UNAME_VERSION=`(uname -v) 2>/dev/null` || UNAME_VERSION=unknown
 
+case "${UNAME_SYSTEM}" in
+Linux|GNU|GNU/*)
+	# If the system lacks a compiler, then just pick glibc.
+	# We could probably try harder.
+	LIBC=gnu
+
+	eval $set_cc_for_build
+	cat <<-EOF > $dummy.c
+	#include 
+	#if defined(__UCLIBC__)
+	LIBC=uclibc
+	#elif defined(__dietlibc__)
+	LIBC=dietlibc
+	#else
+	LIBC=gnu
+	#endif
+	EOF
+	eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC' | sed 's, ,,g'`
+	;;
+esac
+
 # Note: order is significant - the case branches are not exclusive.
 
 case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
 *:NetBSD:*:*)
 	# NetBSD (nbsd) targets should (where applicable) match one or
-	# more of the tupples: *-*-netbsdelf*, *-*-netbsdaout*,
+	# more of the tuples: *-*-netbsdelf*, *-*-netbsdaout*,
 	# *-*-netbsdecoff* and *-*-netbsd*.  For targets that recently
 	# switched to ELF, *-*-netbsd* would select the old
 	# object file format.  This provides both forward
@@ -155,20 +168,27 @@
 	# N

Bug#831369: audacity: In LADSPA effect settings, sliders cannot handle negative integers

[Kyanos]

Package: audacity
Version: 2.1.2-1+b1
Severity: minor

Dear Maintainer,

In the settings window for LADSPA effects, the sliders do not move to
negative integers. If, for example, an integer option ranges from -3 to
3 (inclusive), the slider will only move within one half of the bar.

What is interesting is that negative values can still be entered
manually, and the slider will even move to the appropriate position in
the negative part! But trying to adjust the slider will cause it to jump
back to the 0 position.

Also, the lower-bound label for the slider is incorrect when negative
integers are involved: It is one greater than the true lower bound. So,
if the range were from -3 to 3, the lower-bound label would be -2.
However, the slider seems to behave as if the lower bound is correct.

I first discovered these issues while using Tom Baran's Autotalent
plugin (packaged as "autotalent"), so that may be used to reproduce
these issues. I have also attached a test plugin which may help.

Thank you for your consideration.

Kyanos

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'oldstable-updates'), (300,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages audacity depends on:
ii  audacity-data   2.1.2-1
ii  libasound2  1.1.1-2
ii  libavcodec577:3.0.2-4
ii  libavformat57   7:3.0.2-4
ii  libavutil55 7:3.0.2-4
ii  libc6   2.23-1
ii  libexpat1   2.2.0-1
ii  libflac++6v51.3.1-4
ii  libflac81.3.1-4
ii  libgcc1 1:6.1.1-9
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libglib2.0-02.48.1-1
ii  libgtk2.0-0 2.24.30-2
ii  libid3tag0  0.15.1b-11
ii  liblilv-0-0 0.22.0~dfsg0-1
ii  libmad0 0.15.1b-8
ii  libmp3lame0 3.99.5+repack1-9+b1
ii  libogg0 1.3.2-1
ii  libportaudio2   19+svn20140130-1
ii  libportsmf0 0.1~svn20101010-4
ii  libsbsms10  2.0.2-1
ii  libsndfile1 1.0.25-10
ii  libsoundtouch1  1.9.2-2
ii  libsoxr00.1.2-1
ii  libstdc++6  6.1.1-9
ii  libsuil-0-0 0.8.2~dfsg0-1
ii  libtwolame0 0.3.13-1.2
ii  libvamp-hostsdk3v5  2.6~repack0-2
ii  libvorbis0a 1.3.5-3
ii  libvorbisenc2   1.3.5-3
ii  libvorbisfile3  1.3.5-3
ii  libwxbase3.0-0v53.0.2+dfsg-1.4
ii  libwxgtk3.0-0v5 3.0.2+dfsg-1.4

audacity recommends no packages.

Versions of packages audacity suggests:
ii  autotalent [ladspa-plugin]   0.2-5
ii  caps [ladspa-plugin] 0.9.24-2
ii  ladspa-sdk [ladspa-plugin]   1.13-2+b1
ii  swh-plugins [ladspa-plugin]  0.4.16+git20160602~repack1-2
ii  tap-plugins [ladspa-plugin]  0.7.3-1

-- no debconf information
#include 
#include 
#include 

/*
 * This is a LADSPA plugin that merely copies the audio input to the output.
 * The primary purpose of this plugin is to test hosts' handling of control
 * inputs.
 *
 * To the extent possible under law, Kyanos has waived all copyright and
 * related or neighboring rights to this work, using Creative Commons
 * CC0 1.0 Universal. For more information, please visit:
 * https://creativecommons.org/publicdomain/zero/1.0/
 */

/* Port count (1 audio in, 1 audio out, 1 control in) */
#define LT_PORTS_COUNT 3

/* Port numbers */
#define LT_PORT_AUDIO_IN 0
#define LT_PORT_AUDIO_OUT 1
#define LT_PORT_CONTROL_IN 2

typedef struct lt_instance_s {
	LADSPA_Data* connections[LT_PORTS_COUNT];
} lt_instance;

const LADSPA_PortDescriptor lt_port_descs[] = {
	LADSPA_PORT_AUDIO | LADSPA_PORT_INPUT,
	LADSPA_PORT_AUDIO | LADSPA_PORT_OUTPUT,
	LADSPA_PORT_CONTROL | LADSPA_PORT_INPUT,
};
const char* lt_port_names[] = {
	"Audio In",
	"Audio Out",
	"Test Option",
};
const LADSPA_PortRangeHint lt_port_range_hints[] = {
	/* Dummy hints for audio ports */
	{0, 0, 0},
	{0, 0, 0},
	/* Hints for control port */
	{
		LADSPA_HINT_BOUNDED_BELOW | LADSPA_HINT_BOUNDED_ABOVE
			| LADSPA_HINT_INTEGER | LADSPA_HINT_DEFAULT_0
		,
		-0.1,
		3.1
	},
};

LADSPA_Handle lt_instantiate(
	const struct _LADSPA_Descriptor * Descriptor, unsigned long SampleRate
);

void lt_connect_port(
	LADSPA_Handle Instance, unsigned long Port, LADSPA_Data * DataLocation
);

void lt_run(LADSPA_Handle Instance, unsigned long SampleCount);

void lt_cleanup(LADSPA_Handle Instance);

/* Descriptor for this plugin */
const LADSPA_Descriptor lt_descriptor = {
	/*
	 * Unique ID.
	 *
	 * "Plugin IDs 1-1000 are reserved for development use"
	 * (LADSPA SDK documentation)
	 */
	1,

	/* Label */
	"ladspatest",

	/* Properties */
	LADSPA_PROPERTY_REALTIME | LADSPA_PROPERTY_HARD_RT_CAPABLE,

	/* Name */
	"LADSPA Test Plugin",

	/* Maker */
	"Kyanos ",

	/* Copyright */
	"Public Domain (CC0 1.0 Universal)",

	/* Port count (1 audio in, 1 audio out, 1 contro

Bug#817373: bb: Removal of debhelper compat 4

[Logan Rosen]

Package: bb
Version: 1.3rc1-8.4
Followup-For: Bug #817373
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
  * debian/rules:
- Add recommended build-arch and build-indep targets.
- Don't ignore all distclean errors.
- Replace dh_clean -k with dh_prep.
  * debian/copyright: Don't point to symlink GPL.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u bb-1.3rc1/config.guess bb-1.3rc1/config.guess
--- bb-1.3rc1/config.guess
+++ bb-1.3rc1/config.guess
@@ -1,8 +1,8 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
-#   Copyright 1992-2014 Free Software Foundation, Inc.
+#   Copyright 1992-2015 Free Software Foundation, Inc.
 
-timestamp='2014-03-23'
+timestamp='2015-08-20'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
@@ -24,12 +24,12 @@
 # program.  This Exception is an additional permission under section 7
 # of the GNU General Public License, version 3 ("GPLv3").
 #
-# Originally written by Per Bothner.
+# Originally written by Per Bothner; maintained since 2000 by Ben Elliston.
 #
 # You can get the latest version of this script from:
 # http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
 #
-# Please send patches with a ChangeLog entry to config-patc...@gnu.org.
+# Please send patches to .
 
 
 me=`echo "$0" | sed -e 's,.*/,,'`
@@ -50,7 +50,7 @@
 GNU config.guess ($timestamp)
 
 Originally written by Per Bothner.
-Copyright 1992-2014 Free Software Foundation, Inc.
+Copyright 1992-2015 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -168,20 +168,27 @@
 	# Note: NetBSD doesn't particularly care about the vendor
 	# portion of the name.  We always set it to "unknown".
 	sysctl="sysctl -n hw.machine_arch"
-	UNAME_MACHINE_ARCH=`(/sbin/$sysctl 2>/dev/null || \
-	/usr/sbin/$sysctl 2>/dev/null || echo unknown)`
+	UNAME_MACHINE_ARCH=`(uname -p 2>/dev/null || \
+	/sbin/$sysctl 2>/dev/null || \
+	/usr/sbin/$sysctl 2>/dev/null || \
+	echo unknown)`
 	case "${UNAME_MACHINE_ARCH}" in
 	armeb) machine=armeb-unknown ;;
 	arm*) machine=arm-unknown ;;
 	sh3el) machine=shl-unknown ;;
 	sh3eb) machine=sh-unknown ;;
 	sh5el) machine=sh5le-unknown ;;
+	earmv*)
+		arch=`echo ${UNAME_MACHINE_ARCH} | sed -e 's,^e\(armv[0-9]\).*$,\1,'`
+		endian=`echo ${UNAME_MACHINE_ARCH} | sed -ne 's,^.*\(eb\)$,\1,p'`
+		machine=${arch}${endian}-unknown
+		;;
 	*) machine=${UNAME_MACHINE_ARCH}-unknown ;;
 	esac
 	# The Operating System including object format, if it has switched
 	# to ELF recently, or will in the future.
 	case "${UNAME_MACHINE_ARCH}" in
-	arm*|i386|m68k|ns32k|sh3*|sparc|vax)
+	arm*|earm*|i386|m68k|ns32k|sh3*|sparc|vax)
 		eval $set_cc_for_build
 		if echo __ELF__ | $CC_FOR_BUILD -E - 2>/dev/null \
 			| grep -q __ELF__
@@ -197,6 +204,13 @@
 		os=netbsd
 		;;
 	esac
+	# Determine ABI tags.
+	case "${UNAME_MACHINE_ARCH}" in
+	earm*)
+		expr='s/^earmv[0-9]/-eabi/;s/eb$//'
+		abi=`echo ${UNAME_MACHINE_ARCH} | sed -e "$expr"`
+		;;
+	esac
 	# The OS release
 	# Debian GNU/NetBSD machines have a different userland, and
 	# thus, need a distinct triplet. However, they do not need
@@ -207,13 +221,13 @@
 		release='-gnu'
 		;;
 	*)
-		release=`echo ${UNAME_RELEASE}|sed -e 's/[-_].*/\./'`
+		release=`echo ${UNAME_RELEASE} | sed -e 's/[-_].*//' | cut -d. -f1,2`
 		;;
 	esac
 	# Since CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM:
 	# contains redundant information, the shorter form:
 	# CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM is used.
-	echo "${machine}-${os}${release}"
+	echo "${machine}-${os}${release}${abi}"
 	exit ;;
 *:Bitrig:*:*)
 	UNAME_MACHINE_ARCH=`arch | sed 's/Bitrig.//'`
@@ -235,6 +249,9 @@
 *:MirBSD:*:*)
 	echo ${UNAME_MACHINE}-unknown-mirbsd${UNAME_RELEASE}
 	exit ;;
+*:Sortix:*:*)
+	echo ${UNAME_MACHINE}-unknown-sortix
+	exit ;;
 alpha:OSF1:*:*)
 	case $UNAME_RELEASE in
 	*4.0)
@@ -579,8 +596,9 @@
 	else
 		IBM_ARCH=powerpc
 	fi
-	if [ -x /usr/bin/oslevel ] ; then
-		IBM_REV=`/usr/bin/oslevel`
+	if [ -x /usr/bin/lslpp ] ; then
+		IBM_REV=`/usr/bin/lslpp

Bug#831368: live-wrapper: output live.iso not isohybrid, cannot be booted from thumb drive

[Ben Caradoc-Davies]

Package: live-wrapper
Version: 0.3
Severity: normal

Dear Maintainer,

the output live.iso produced by lwr has neither MBR nor any partitions (MBR or
GPT). It appears to be a plain ISO image. It cannot be booted from a thumb
drive.

Kind regards,
Ben.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages live-wrapper depends on:
ii  python-cliapp  1.20160316-1
pn  python:any 
ii  vmdebootstrap  1.5-1

live-wrapper recommends no packages.

live-wrapper suggests no packages.

-- no debconf information

Bug#831367: live-wrapper: Missing dependencies on isolinux and xorriso

[Ben Caradoc-Davies]

Package: live-wrapper
Version: 0.3
Severity: normal

Dear Maintainer,

if isolinux and xorriso are not installed, lwr fails with:

ERROR: [Errno 2] No such file or directory: '/usr/lib/ISOLINUX/isolinux.bin'

After manually installing isolinux, lwr still fails with:

ERROR: No such file or directory

This is resolved by installing xorriso. I deduce that live-wrapper has
undeclared dependencies on isolinux and xorriso.

Kind regards,
Ben.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages live-wrapper depends on:
ii  python-cliapp  1.20160316-1
pn  python:any 
ii  vmdebootstrap  1.5-1

live-wrapper recommends no packages.

live-wrapper suggests no packages.

-- no debconf information

Bug#831366: courier-mlm: message bouncing with NOBOZOS=1 (default setting), false positives

[Fred Drueck]

Package: courier-mlm
Version: 0.73.1-1.6
Severity: normal

Dear Maintainer,

I've encountered some bugs in couriermlm, when a list is setup the
option 'NOBOZOS=1' is set by default, which should bounce bad ctl
command messages sent to user-list@domain instead of
user-list-command@domain.

What's supposed to be happening is that messages like:

cat <

Bug#831365: ITP: lepton -- tool to compress JPEGs losslessly

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: lepton
  Version : 1.0
  Upstream Author : Copyright (c) 2016 Dropbox, Inc.
* URL : https://github.com/dropbox/lepton
* License : Apache-2
  Programming Lang: C
  Description : tool to compress JPEGs losslessly

 Lepton is a tool and file format for losslessly compressing JPEGs by an
 average of 22%.
 .
 This can be used to archive large photo collections, or to serve images
 live and save 22% bandwidth.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#803456: Digikam 5.0.0 uploaded

[Steve M. Robbins]

On Monday, July 11, 2016 5:38:52 PM CDT Lisandro Damián Nicanor Pérez Meyer 
wrote:
> On domingo, 10 de julio de 2016 2:01:04 P. M. ART Steve M. Robbins wrote:
> > Hi,
> > 
> > I wanted to make people aware that I have uploaded Digikam 5.0.0 packages
> > to Debian earlier today.
> 
> First of all: thanks a lot.

Another thing I'd like to do is move the packaging from SVN to GIT.  Earlier 
[1] you had indicated there are scripts to help this migration.  Can point me 
at them?

Thanks,
-Steve

[1] http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2015-December/
002227.html




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

Bug#831359: opendkim: Starting OpenDKIM: install: invalid group ‘’

[Scott Kitterman]

On Friday, July 15, 2016 12:09:46 AM Valentin Lorentz wrote:
> Package: opendkim
> Version: 2.10.3-5
> Severity: grave
> 
> Dear maintainer,
> 
> After a recent upgrade of my system, I get this whenever I try to start
> opendkim (including when run by dpkg while configuring it):
> 
> root@Hydrogen:~# LANG=C /etc/init.d/opendkim start
> Starting OpenDKIM: install: invalid group ‘’
> 
> I believe the issue lies in the init script: if $RUNDIR does not exist,
> then this command is run:
> 
> install -o "$USER" -g "$GROUP" -m 755 -d "$RUNDIR"
> 
> with $GROUP defined like this:
> 
> GROUP=$GROUP
> 
> But $GROUP does not exist prior to the line.

First, downgrading to important since this does not apply to users of the 
default Debian init system.

Second, /etc/default/opendkim is sourced before that line in the init script 
and the current version of the defaults file has GROUP defined, so it does.

Please check the contents of /etc/default/opendkim.  The last part of it 
should look like:

USER=opendkim
GROUP=opendkim
PIDFILE=$RUNDIR/$NAME.pid
EXTRAAFTER=

If it's not there, when the package was upgraded your system (either manually 
or automatically, depending on how it is configured), kept the old version.  
If you add those at the bottom of the file and restart, it should work.

If it is there, then there's a bug that needs investigating.  I don't have any 
Testing/Unstable systems using the init script, so I may need help with 
testing.

Scott K

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

Bug#820627: ttf-mscorefonts-installer: Does not update font cache

[Tony Houghton]

Package: ttf-mscorefonts-installer
Version: 3.6
Followup-For: Bug #820627

Same problem here, on a system I installed earlier today.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ttf-mscorefonts-installer depends on:
ii  cabextract 1.6-1
ii  debconf [debconf-2.0]  1.5.59
ii  wget   1.18-2
ii  xfonts-utils   1:7.7+3

Versions of packages ttf-mscorefonts-installer recommends:
ii  fonts-liberation  1.07.4-1

ttf-mscorefonts-installer suggests no packages.

-- debconf information:
  msttcorefonts/baddldir:
  msttcorefonts/http_proxy:
  msttcorefonts/dldir:
  msttcorefonts/savedir:
  msttcorefonts/dlurl:

Bug#831364: say a short overview, not this short overview

[積丹尼 Dan Jacobson]

Package: libgraph-easy-perl
Version: 0.76-1
Severity: wishlist
File: /usr/bin/graph-easy

Change this
<   --helpPrint the full documentation, not just this short overview.
>   --helpPrint the full documentation, not just a short overview.
else doesn't make sense in many contexts!

Bug#806092: [Pkg-electronics-devel] Bug#806092: pcb: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Bdale Garbee]

Santiago Vila  writes:

> I have the ok from the Release Managers to consider this issue as RC
> for stretch. I'm going to wait at least one week before raising
> this to "serious".

Go ahead and raise the severity whenever you want.

I'll be happy to take a look at this, but I really don't have time this
week.  I've got huge amounts of airplane seat time in the following two
weeks, though... /o\

Bdale


signature.asc
Description: PGP signature

Bug#831102: rquantlib: FTBFS with GCC 6: caught segfault, address 0x7f8a97bed6a0, cause 'invalid permissions'

[Dirk Eddelbuettel]

On 14 July 2016 at 09:50, Lucas Nussbaum wrote:
| Source: rquantlib
| Version: 0.4.2-2
| Severity: serious
| Tags: stretch sid
| User: debian...@lists.debian.org
| Usertags: qa-ftbfs-20160713 qa-ftbfs
| Justification: FTBFS with GCC 6 on amd64

Please see _extended_ discussion with Martin and doko in #812286.

The _entire_ related C++ stack needs a rebuild: Rcpp as well as QuantLib as
well as RQuantLib.

Poking at packages individually will do no good.

Dirk

| 
| Hi,
| 
| During a rebuild of all packages in sid using the gcc-defaults package
| available in experimental to make GCC default to version 6, your package 
failed
| to build on amd64. For more information about GCC 6 and Stretch, see:
| - https://wiki.debian.org/GCC6
| - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
| 
| Relevant part (hopefully):
| > make[1]: Entering directory '/«PKGBUILDDIR»/src'
| > make[1]: Leaving directory '/«PKGBUILDDIR»/src'
| > installing to 
/«PKGBUILDDIR»/debian/r-cran-rquantlib/usr/lib/R/site-library/RQuantLib/libs
| > ** R
| > ** demo
| > ** inst
| > ** preparing package for lazy loading
| > ** help
| > *** installing help indices
| > ** building package indices
| > ** testing if installed package can be loaded
| > 
| >  *** caught segfault ***
| > address 0x7f8a97bed6a0, cause 'invalid permissions'
| > 
| > Traceback:
| >  1: dyn.load(file, DLLpath = DLLpath, ...)
| >  2: library.dynam(lib, package, package.lib)
| >  3: loadNamespace(package, lib.loc)
| >  4: doTryCatch(return(expr), name, parentenv, handler)
| >  5: tryCatchOne(expr, names, parentenv, handlers[[1L]])
| >  6: tryCatchList(expr, classes, parentenv, handlers)
| >  7: tryCatch(expr, error = function(e) {call <- conditionCall(e)if 
(!is.null(call)) {if (identical(call[[1L]], quote(doTryCatch))) 
call <- sys.call(-4L)dcall <- deparse(call)[1L]prefix <- 
paste("Error in", dcall, ": ")LONG <- 75Lmsg <- 
conditionMessage(e)sm <- strsplit(msg, "\n")[[1L]]w <- 14L + 
nchar(dcall, type = "w") + nchar(sm[1L], type = "w")if (is.na(w))   
  w <- 14L + nchar(dcall, type = "b") + nchar(sm[1L], type 
= "b")if (w > LONG) prefix <- paste0(prefix, "\n  ")}   
 else prefix <- "Error : "msg <- paste0(prefix, conditionMessage(e), "\n")  
  .Internal(seterrmessage(msg[1L]))if (!silent && 
identical(getOption("show.error.messages"), TRUE)) {cat(msg, 
file = stderr()).Internal(printDeferredWarnings())}
invisible(structure(msg, class = "try-error", condition = e))})
| >  8: try({attr(package, "LibPath") <- which.lib.locns <- 
loadNamespace(package, lib.loc)env <- attachNamespace(ns, pos = pos, deps)})
| >  9: library(pkg_name, lib.loc = lib, character.only = TRUE, logical.return 
= TRUE)
| > 10: withCallingHandlers(expr, packageStartupMessage = function(c) 
invokeRestart("muffleMessage"))
| > 11: suppressPackageStartupMessages(library(pkg_name, lib.loc = lib, 
character.only = TRUE, logical.return = TRUE))
| > 12: doTryCatch(return(expr), name, parentenv, handler)
| > 13: tryCatchOne(expr, names, parentenv, handlers[[1L]])
| > 14: tryCatchList(expr, classes, parentenv, handlers)
| > 15: tryCatch(expr, error = function(e) {call <- conditionCall(e)if 
(!is.null(call)) {if (identical(call[[1L]], quote(doTryCatch))) 
call <- sys.call(-4L)dcall <- deparse(call)[1L]prefix <- 
paste("Error in", dcall, ": ")LONG <- 75Lmsg <- 
conditionMessage(e)sm <- strsplit(msg, "\n")[[1L]]w <- 14L + 
nchar(dcall, type = "w") + nchar(sm[1L], type = "w")if (is.na(w))   
  w <- 14L + nchar(dcall, type = "b") + nchar(sm[1L], type 
= "b")if (w > LONG) prefix <- paste0(prefix, "\n  ")}   
 else prefix <- "Error : "msg <- paste0(prefix, conditionMessage(e), "\n")  
  .Internal(seterrmessage(msg[1L]))if (!silent && 
identical(getOption("show.error.messages"), TRUE)) {cat(msg, 
file = stderr()).Internal(printDeferredWarnings())}
invisible(structure(msg, class = "try-error", condition = e))})
| > 16: try(suppressPackageStartupMessages(library(pkg_name, lib.loc = lib, 
character.only = TRUE, logical.return = TRUE)))
| > 17: tools:::.test_load_package("RQuantLib", 
"/«PKGBUILDDIR»/debian/r-cran-rquantlib/usr/lib/R/site-library")
| > An irrecoverable exception occurred. R is aborting now ...
| > Segmentation fault
| > ERROR: loading failed
| > * removing 
'/«PKGBUILDDIR»/debian/r-cran-rquantlib/usr/lib/R/site-library/RQuantLib'
| > make: *** [R_any_arch] Error 1
| 
| The full build log is available from:
|
http://people.debian.org/~lucas/logs/2016/07/13/rquantlib_0.4.2-2_unstable_gcc6.log
| 
| A list of current common problems and possible solutions is available at
| http://wiki.debian.org/qa.debian.org/FTBFS . You're welcom

Bug#831363: jquery-goodies: Update to PHP7.0 dependencies

[Nishanth Aravamudan]

Package: jquery-goodies
Version: 11-2
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

- Update to PHP7.0 dependencies (LP #1544352).

Thanks for considering the patch.

*** /tmp/tmp3yXe_I/jquery-goodies_11-2ubuntu1.debdiff
diff -Nru jquery-goodies-11/debian/control jquery-goodies-11/debian/control
--- jquery-goodies-11/debian/control2016-05-21 19:02:33.0 -0700
+++ jquery-goodies-11/debian/control2016-07-14 16:45:58.0 -0700
@@ -58,7 +58,7 @@
 Package: libjs-jquery-jfeed
 Architecture: all
 Depends: ${misc:Depends}, libjs-jquery
-Recommends: javascript-common, php5
+Recommends: javascript-common, php
 Homepage: http://hovinne.com/articles/jfeed-jquery-rss-atom-feed-parser-plugin
 Description: jQuery RSS/Atom feed parser plugin
  jFeed is a generic RSS/Atom feed parser, currently parses RSS 0.91, 0.92,


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#831362: support building libcap-ng without python extensions

[Helmut Grohne]

Source: libcap-ng
Version: 0.7.7-3
Severity: wishlist
Tags: patch

Hi,

libcap-ng is part of the build-closure of essential and thus needs to be
able to be cross built. On the other hand, cross building python
extensions is currenty non-trivial as the python policy is not yet fully
fleshed out wrt cross building. So to make cross building libcap-ng work
today, I am proposing to make those python extensions optional via a
nopython build profile. Refer to
https://lists.debian.org/debian-cross/2016/04/msg4.html for a
rationale on the profile name.

I am attaching a patch that adds the requested support and I hope that
it is not a big maintenance cost. After applying it, libcap-ng cross
builds just fine under the nopython profile. Please consider applying
it.

Helmut
--- libcap-ng-0.7.7/debian/changelog
+++ libcap-ng-0.7.7/debian/changelog
@@ -1,3 +1,10 @@
+libcap-ng (0.7.7-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add nopython build profile (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 15 Jul 2016 00:46:48 +0200
+
 libcap-ng (0.7.7-3) unstable; urgency=high
 
   * Install libcap-ng so file to /lib (Closes: #829126, #828992)
--- libcap-ng-0.7.7/debian/control
+++ libcap-ng-0.7.7/debian/control
@@ -3,13 +3,13 @@
 Maintainer: Pierre Chifflier 
 Build-Depends: debhelper (>= 9),
 dh-autoreconf,
-dh-python,
+dh-python ,
 autotools-dev,
 libattr1-dev,
 linux-kernel-headers,
-swig,
-python-all-dev,
-python3-dev
+swig ,
+python-all-dev ,
+python3-dev 
 Standards-Version: 3.9.8
 Section: libs
 X-Python-Version: >= 2.6
@@ -65,6 +65,7 @@
 Section: python
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
+Build-Profiles: 
 Description: Python bindings for libcap-ng
  This library implements the user-space interfaces to the POSIX
  1003.1e capabilities available in Linux kernels.  These capabilities are
@@ -81,6 +82,7 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
 Provides: ${python3:Provides}
+Build-Profiles: 
 Description: Python3 bindings for libcap-ng
  This library implements the user-space interfaces to the POSIX
  1003.1e capabilities available in Linux kernels.  These capabilities are
--- libcap-ng-0.7.7/debian/rules
+++ libcap-ng-0.7.7/debian/rules
@@ -8,6 +8,11 @@
 
 export DEB_BUILD_HARDENING=1
 
+ifneq ($(filter nopython,$(DEB_BUILD_PROFILES)),)
+override_dh_auto_configure:
+   dh_auto_configure -- --without-python --without-python3
+endif
+
 override_dh_install:
mkdir -p $(CURDIR)/debian/tmp/lib/$(DEB_HOST_MULTIARCH) && \
mv $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/lib*.so.0* 
$(CURDIR)/debian/tmp/lib/$(DEB_HOST_MULTIARCH)/; \
@@ -24,5 +29,8 @@
:
 
 %:
+ifeq ($(filter nopython,$(DEB_BUILD_PROFILES)),)
dh $@ --with=python2,python3,autoreconf
-
+else
+   dh $@ --with=autoreconf
+endif

Bug#830353: ruby-kgio: FTBFS: ERROR: Test "ruby2.3" failed.

[Eric Wong]

Antonio Terceiro  wrote:
> On Fri, Jul 08, 2016 at 06:53:29PM +, Eric Wong wrote:
> > Thanks for the report.  Can you try the patch below?
> 
> Didn't help.
> 
> I can't, however, reproduce this locally on my workstation.

Thanks for following up.

> > I'd be interested to know what non-standard sysctl knobs are set
> > for kernel socket buffer sizes (in /proc/sys/net/{core,ipv4}/*mem*)
 
> ==> /proc/sys/net/ipv4/tcp_rmem <==
> 40961258291216777216
> 
> ==> /proc/sys/net/ipv4/tcp_wmem <==
> 40961258291216777216

Yikes at the gigantic default (middle) values.  Anyways, I've
set those locally and notice the problem with my previous patch:
I missed some spots where temporary strings/arrays were created
inside the tests themselves.

> In Debian we don't even have 2.2 anymore. The only things using kgio are
> unicorn and rainbows. Maybe if their dependency on kgio could be skipped on
> Ruby 2.3, we could drop kgio from Debian.

Yes, I still have to check and make sure I don't introduce
performance regressions and such when dropping kgio.
I still need to support Ruby 1.9.3 and 2.0.0 outside of Debian
(or on wheezy LTS/jessie)

The following ought to work (I tested locally with those sysctl
values) but I'll see about making the tests more robust against
larger kernel buffers.

---8<
--- a/test/lib_read_write.rb
+++ b/test/lib_read_write.rb
@@ -7,7 +7,12 @@ $-w = true
 require 'kgio'
 
 module LibReadWriteTest
-  RANDOM_BLOB = File.open("/dev/urandom") { |fp| fp.read(10 * 1024 * 1024) }
+  RANDOM_BLOB = File.open("/dev/urandom") do |fp|
+nr = 31
+buf = fp.read(nr)
+# get roughly a 20MB block of random data
+(buf * (20 * 1024 * 1024 / nr)) + (buf * rand(123))
+  end
 
   def teardown
 @rd.close if defined?(@rd) && ! @rd.closed?
@@ -369,7 +374,7 @@ module LibReadWriteTest
   @nr += 1
   IO.select(nil, [self])
 end
-buf = "." * 1024 * 1024 * 10
+buf = RANDOM_BLOB
 thr = Thread.new { @wr.kgio_write(buf) }
 Thread.pass until thr.stop?
 readed = @rd.read(buf.size)
@@ -385,7 +390,7 @@ module LibReadWriteTest
   @nr += 1
   IO.select(nil, [self])
 end
-buf = ["." * 1024] * 1024 * 10
+buf = [ RANDOM_BLOB, RANDOM_BLOB ]
 buf_size = buf.inject(0){|c, s| c + s.size}
 thr = Thread.new { @wr.kgio_writev(buf) }
 Thread.pass until thr.stop?
-- 
EW

Bug#831140: Bug fixed in upstream: 831140

[Markus Koschany]

On 15.07.2016 01:09, Mark Vejvoda wrote:
> I pushed a fix for the new GCC in our git repo in the develop branch.
> 
> https://github.com/MegaGlest/megaglest-source/commit/daf1dac128515d9fc535018c9c4d19b9ac45a1a4
> 
> Thanks

Thanks Mark. I was just about to upload the new revision.

Cheers,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#831140: Bug fixed in upstream: 831140

[Mark Vejvoda]

I pushed a fix for the new GCC in our git repo in the develop branch.

https://github.com/MegaGlest/megaglest-source/commit/daf1dac128515d9fc535018c9c4d19b9ac45a1a4

Thanks

Bug#805955: [pcp] Bug#805955: pcp: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Nathan Scott]

Hi Santiago,

- Original Message -
> Greetings.
> 
> I have the ok from the Release Managers to consider this issue as RC
> for stretch. I'm going to wait at least one week before raising
> this to "serious".
> 
> If you need help to fix this bug, please tag it as "help".
> 

I have a build with another pending fix to upload too, so will look into
this first and push both up this weekend.

cheers.

--
Nathan

Bug#830992: pulseaudio: no sound with snd_hda_codec_realtek ALC880

[Felipe Sateler]

Control: reassign -1 linux-image-4.6.0-1-686-pae

On 14 July 2016 at 12:36, Loris e Anna  wrote:
> Hi Filipe,
> as your request, in attach the verbose log.

For some reason, your kernel is not creating a proper alsa device, and
ALSA does not appear to know about it. Therefore reassigning to the
kernel.

-- 

Saludos,
Felipe Sateler

Bug#720606: imapproxy no longer starts successfully

[Iain McFarlane]

log states
Daemonize(): Configured to run in foreground mode.

even although in the config file it states:
foreground_mode no

only since upgrading to  1.2.7-1.2

Bug#775185: Proposed patch to fix bug #775185 and bug #759763

[Kevin Hilman]

The systemd service file doesn't work for any conmux config file with a hyphen.

I filed a separate bug for this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831358

But the short version is it should use %i instead of %I so that conmux
configs of the form foo-bar.cf don't get translated in the systemd
world as foo/bar.cf.

Bug#831358: conmux-daemon@service prevents config files with hyphens

[Kevin Hilman]

On Thu, 14 Jul 2016 14:10:20 -0700 Kevin Hilman  wrote:

> I've encountered this bug both on Debian jessie and Ubuntu xenial, and
> in both cases this change fixes the problem.

Correction:  Debian jessie does not have this problem since it doesn't
have the systemd init files.

Bug#830997: release.debian.org: Permission to consider dpkg-buildpackage -A bugs as RC

[Santiago Vila]

On Wed, 13 Jul 2016, Emilio Pozuelo Monfort wrote:

> Great. We can handle that for Stretch. You can send a ping to the bug reports
> saying that these are going to be RC for Stretch and that you will bump them
> after a week, and then do that.

Hi. The pings have been sent. Bugs of type "pending upload" and "patch 
available"
yesterday, bugs of type "unclassified" today. Will probably bump severities
during the weeking of next week.

Thanks a lot.

Bug#830681: trilinos-all-dev: Updating binutils breaks trilinos

[Helmut Grohne]

On Sun, Jul 10, 2016 at 01:04:13PM +0200, Felix Salfelder wrote:
> if that's correct, we shouldn't link libtrilinos_teuchoscore.so to a
> particular revision of libbfd-2.26-system.so. how would that be
> possible?
> 
> otoh, if libbfd-2.26.1-system.so
> - is meant to replace libbfd-2.26-system.so, shouldn't there be a
>   symlink?
> - is NOT meant to provide libbfd-2.26-system.so, then why are these not
>   coinstallable?

Dynamically linking libbfd-*-system.so is no allowed. This is explicitly
stated in the package description of binutils-dev.

If you absolutely must link libbfd, link it statically and add an
appropriate Built-Using header.

Helmut

Bug#831361: /usr/bin/tarantool must not link libbfd-*-system.so dynamically

[Helmut Grohne]

Package: tarantool
Version: 1.6.7.588.g76bbd9c-1+b1
Severity: grave

/usr/bin/tarantool currently links libbfd dynamically. Since binutils
2.26.1, that library went away but lush's dependency is still satisfied
resulting in a broken binary. Dynamically linking libbfd is not allowed
(see package description of binutils-dev).

Helmut

Bug#821176: libcrypto++: FTBFS when built with dpkg-buildpackage -A (Command not found)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#830985: tulip: error while loading shared libraries: libbfd-2.26-system.so

[Helmut Grohne]

Control: severity -1 grave

On Wed, Jul 13, 2016 at 04:49:40PM +0200, Yuri D'Elia wrote:
> Seems like tulip depends on libbfd-2.26-system.so, but only 
> libbfd-2.26-system.so.1 is available on my system.

Linking libbfd dynamically is explicitly disallowed (see package
description of binutils-dev). Please do not close this bug without
removing the dynamic linking entirely. If you link libbfd statically,
please ensure to add an appropriate Built-Using header.

Helmut

Bug#806660: taglib: FTBFS when built with dpkg-buildpackage -A (unable to chdir to builddir)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806865: ppl: FTBFS when built with dpkg-buildpackage -A (No rule to make ppl_c.h)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806879: xsp: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#816987: plplot: FTBFS when built with dpkg-buildpackage -A (Error copying file)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#831059: lists.debian.org: Permanently banned users cannot send positive contributions to lists.debian.org

[Javier Serrano Polo]

El dj 14 de 07 de 2016 a les 07:40 +0100, Adam D. Barratt va escriure:
> For avoidance of doubt, "this user" appears to be you. I'm not sure
> why you didn't just say that.

"This user" is me, Javier Serrano Polo. I was abstracting the problem
from the specific user (me).

El dj 14 de 07 de 2016 a les 10:08 +0200, Alexander Wirt va escriure:
> I don't think that it is acceptable to write a mail in that way and to make
> the impression that you are asking for someone else.

Sorry for the confusion. Although my question was about generic "banned
users", the example user is me. I hope you believe that I was not asking
for someone else when the first link says "jav...@jasp.net", which is my
address.

> That, together with the reason for what you have been banned for (mails like
> [1]) don't make me think that lifting the ban is a good idea.

I would like to contextualize the message [1]. It was sent on the feast
of the holy innocents [2] (it is in Spanish, I cannot find a good
English resource).

I sent that message. I was just trying to help and I thought I was doing
the right thing. I am trying to move forward and continue helping. I can
explain myself again and answer all your questions about what I did. But
I did not open this bug report to talk about the past or to question the
listmaster (Alex) that banned me; I understand that listmasters do their
role as best as they can. I am here to talk about my future behavior.

I made jokes that some people did not like. It is easy for me to not
make any more jokes. I believe that banned users should have a way to
redeem themselves and make positive contributions. IMHO, I think I
deserve an opportunity; is there something I can do?

> That is my personal oppinion as listmaster. Lets see what other listmaster
> have to say.

Alex, your opinion is important to me. I would like to know if I have
convinced you that you can give me a chance.

[2] 
https://es.wikipedia.org/wiki/D%C3%ADa_de_los_Santos_Inocentes#Conmemoraci.C3.B3n.2C_bromas_e_inocentadas


smime.p7s
Description: S/MIME cryptographic signature

Bug#806874: stormbaancoureur: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#831360: /usr/bin/lush must not link libbfd-*-system.so dynamically

[Helmut Grohne]

Package: lush
Version: 1.2.1-9+cvs20110227+nmu1+b4
Severity: grave

/usr/bin/lush currently links libbfd dynamically. Since binutils 2.26.1,
that library went away but lush's dependency is still satisfied
resulting in a broken binary. Dynamically linking libbfd is not allowed
(see package description of binutils-dev).

Helmut

Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#817810: emscripten: FTBFS when built with dpkg-buildpackage -A (ln: failed to create symbolic link)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#821018: asterisk: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#819416: shibboleth-sp2: FTBFS when built with dpkg-buildpackage -A (dh_install: missing files, aborting)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#816988: seqan: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#809119: libvsqlitepp: FTBFS when built with dpkg-buildpackage -A (invalid package/library name)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806657: love: FTBFS when built with dpkg-buildpackage -A (dh_install: love-doc missing files)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A (@include: could not find version.texi)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806867: python-scipy: FTBFS when built with dpkg-buildpackage -A (No module named scipy)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806658: sofia-sip: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806659: sushi: FTBFS when built with dpkg-buildpackage -A (mv: target is not a directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806209: jsonm: FTBFS when built with dpkg-buildpackage -A (dh_ocamldoc -i fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806624: ikvm: FTBFS when built with dpkg-buildpackage -A (mkdir: File exists)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806102: qt-gstreamer: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806069: linkchecker: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806613: eclipse: FTBFS when built with dpkg-buildpackage -A (dh_install: eclipse-jdt missing files)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806210: uutf: FTBFS when built with dpkg-buildpackage -A (dh_ocamldoc -i fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806621: haskell-ghc-events: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806617: freeradius: FTBFS when built with dpkg-buildpackage -A (dh_install: freeradius-common missing files)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806127: zope2.13: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806606: basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806629: libkarma: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806625: lablgtk2: FTBFS when built with dpkg-buildpackage -A (dh_ocamldoc fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806087: ocaml: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806616: fftw3: FTBFS when built with dpkg-buildpackage -A (build-indep fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806117: the: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806602: ace: FTBFS when built with dpkg-buildpackage -A (override_dh_install fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806100: pyviennacl: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806092: pcb: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806116: tagua: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806089: openmprtl: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806081: mpqc: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806067: lilypond: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806060: libopendbx: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806028: galax: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806055: libaria: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806037: gnumail: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806049: indigo: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#805962: witty: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806042: guile-2.0: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806020: ecj: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806005: charmap.app: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806040: gtkglext: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806045: heimdal: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806011: cython: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806035: gnome-commander: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806012: db5.3: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806018: docbook-xsl-saxon: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#805988: aboot: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#805953: noiz2sa: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#806000: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#805946: libapreq2: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Bug#805955: pcp: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.