Bug#831113: marked as done (qbittorrent: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 05:19:30 +
with message-id 
and subject line Bug#831113: fixed in qbittorrent 3.3.6-1
has caused the Debian Bug report #831113,
regarding qbittorrent: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: 
No such file or directory
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.)


-- 
831113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qbittorrent
Version: 3.3.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

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[3]: Entering directory '/«PKGBUILDDIR»/build-nox/src'
> compiling ../../src/app/qtsingleapplication/qtsinglecoreapplication.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/QCoreApplication:1,
>  from 
> ../../src/app/qtsingleapplication/qtsinglecoreapplication.h:44,
>  from 
> ../../src/app/qtsingleapplication/qtsinglecoreapplication.cpp:42:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [qtsinglecoreapplication.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qbittorrent_3.3.4-1_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 welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: qbittorrent
Source-Version: 3.3.6-1

We believe that the bug you reported is fixed in the latest version of
qbittorrent, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated qbittorrent 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 08 Aug 2016 22:53:15 -0400
Source: qbittorrent
Binary: qbittorrent qbittorrent-nox qbittorrent-dbg
Architecture: source amd64
Version: 3.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Cristian Greco 
Changed-By: Andrew Starr-Bochicchio 
Description:
 qbittorrent - bittorrent client based on libtorrent-rasterbar with a Qt4 GUI
 qbittorrent-dbg - debug symbols for qbittorrent and qbittorrent-nox
 qbittorrent-nox - bittorrent client based on libtorrent-rasterbar (without X 
suppor
Closes: 831113
Changes:
 qbittorrent (3.3.6-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #831113).
   * Bump Standards-Version to 3.9.8, no changes.
Checksums-Sha1:
 7c66726ad59940fb190f5a78f9d97579c2013a87 2158 qbittorrent_3.3.6-1.dsc
 68ad73a2afdac6356ea74635918f749487032382 2881284 qbittorrent_3.3.6.orig.tar.xz
 d6ceb2d0a239f3947be0c95533d83969630e855c 120480 
qbittorrent_3.3.6-1.debian.tar.xz
 a6ee592e54d7775a3e2b5ec81bae446aa6689545 19565766 
qbittorrent-dbg_3.3.6-1_amd64.deb
 15308991555a0776f28e19f64c06c58fe3968f42 3064822 
qbittorrent-nox_3.3.6-1_amd64.deb
 67e2d0e7157d4754c33239ecb0da3057975690f4 3585508 qbittorrent_3.3.6-1_amd64.deb
Checksums-Sha256:
 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 815319 patch
Bug #815319 [isc-dhcp-server] After update dhcpd server don't start
Added tag(s) patch.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
815319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#831228: flashplugin-nonfree: Signature status

[Elliott Mitchell]

Sorry to be the bearer of bad news, but:

$ wget 
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.22.0.0.209.sha512.amd64.pgp.asc
--2016-08-08 16:48:41--  
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.22.0.0.209.sha512.amd64.pgp.asc
Resolving people.debian.org (people.debian.org)... 5.153.231.30, 
2001:41c8:1000:21::21:30
Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2016-08-08 16:48:41 ERROR 404: Not Found.

$ 

While alas the signature at 
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc
is still the one for 11.2.202.632.  Seems the webserver or 
isn't working quite the way you expected.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#833679: BitPaddedInt import error

[mike winsor]

compatid3 mutagen.id3 ImportError: cannot import name BitPaddedInt

puddletag and  picard same error , Quod Libet and Ex Falso both load, run OK


puddletag
Traceback (most recent call last):
  File "/usr/bin/puddletag", line 328, in 
migrate_settings()
  File "/usr/bin/puddletag", line 86, in migrate_settings
_migrate_action_shortcuts()
  File "/usr/bin/puddletag", line 92, in _migrate_action_shortcuts
from puddlestuff.puddleobjects import PuddleConfig
  File "/usr/lib/python2.7/dist-packages/puddlestuff/puddleobjects.py",
line 17, in 
import audioinfo
  File
"/usr/lib/python2.7/dist-packages/puddlestuff/audioinfo/__init__.py", line
104, in 
import id3, vorbis, apev2, mp4
  File "/usr/lib/python2.7/dist-packages/puddlestuff/audioinfo/id3.py",
line 19, in 
from _compatid3 import CompatID3
  File
"/usr/lib/python2.7/dist-packages/puddlestuff/audioinfo/_compatid3.py",
line 25, in 
from mutagen.id3 import ID3, Frame, Frames, Frames_2_2, TextFrame,
TORY, \
ImportError: cannot import name BitPaddedInt

 picard
Traceback (most recent call last):
  File "/usr/bin/picard", line 2, in 
from picard.tagger import main; main('/usr/share/locale', True)
  File "/usr/lib/picard/picard/tagger.py", line 65, in 
from picard.formats import open as open_file
  File "/usr/lib/picard/picard/formats/__init__.py", line 157, in 
from picard.formats.id3 import (
  File "/usr/lib/picard/picard/formats/id3.py", line 30, in 
from picard.formats.mutagenext import compatid3
  File "/usr/lib/picard/picard/formats/mutagenext/compatid3.py", line 25,
in 
from mutagen.id3 import ID3, Frames, Frames_2_2, TextFrame, TORY, \
ImportError: cannot import name BitPaddedInt

Warning i am not a programmer, but i would like to help, if your requests
for me are easy to copy into my Terminal.

Bug#833812: Prevent possible stack overflow

[Bastien ROUCARIES]

Package: src:imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org




Prevent possible stack overflow

Prevent stack overflow by checking if string is null

(cherry picked from commit 6ea4d4e9eeac1e287bdbfda84f67fb1e50242fb5)

origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/6ea4d4e9eeac1e287bdbfda84f67fb1e50242fb5

Bug#833810: picon-users: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-users
Version: 2016.01.02-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-users_2016.01.02-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833809: picon-usenix: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-usenix
Version: 1995.04.13-8
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-usenix_1995.04.13-8_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833655: metar: NOAA changed server weather.noaa.gov to tgftp.nws.noaa.gov (metar.h in source)

[Mariusz Gruszka]

https://github.com/keesL/metar
updated source

2016-08-08 9:57 GMT+02:00 Paul Wise :

> On Sun, 07 Aug 2016 16:59:26 +0200 Mariusz Gruszka wrote:
>
> > NOAA changed server weather.noaa.gov to tgftp.nws.noaa.gov (metar.h in
> source)
> > package is not working with old server
>
> Here is a workaround for this issue:
>
> env METARURL=http://tgftp.nws.noaa.gov/data/observations/metar/stations
> metar lows
>
> The NOAA folks have a redirect in place, but metar's use of libcurl
> does not enable following redirects, which is not the default.
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>

Bug#833790: lvm2: behevaiour change: lvremove on cached device removed origin device, potential data loss

[Bastian Blank]

Control: tags -1 unreproducible
Control: severity -1 important

On Mon, Aug 08, 2016 at 06:22:17PM +0200, Marc Lehmann wrote:
> After upgrading, the manpage didn't change, but the behaviour changed:
> now lvremove removes the origin device as well, while lvconvert --uncache
> works as before.

I can't reproduce this:

Setup:

|# lvcreate --type cache-pool -n test_cache -L 1G vg
|  Logical volume "test_cache" created.
|# lvcreate --cache -n vg/test -L 1G --cachepool vg/test_cache vg
|  Logical volume "test" created.
|# lvs --all
|  LV VG Attr   LSize   Pool Origin Data%  Meta%  
Move Log Cpy%Sync Convert
|  test   vg Cwi-a-C---   1,00g [test_cache]0,00
   100,00
|  [test_cache]   vg Cwi---C---   1,00g
|  [test_cache_cdata] vg Cwi-ao   1,00g
|  [test_cache_cmeta] vg ewi-ao   1,00g
|  [test_corig]   vg owi-aoC---   1,00g

Removing the target volume "test" removes everything:

|# lvremove vg0_devel/test
|Do you really want to remove active logical volume vg0_devel/test? [y/n]: y
|  Logical volume "test_cache" successfully removed
|  Logical volume "test" successfully removed

However, as document, removing the cache-volume only removes the cache
itself, not the origin:

|# lvremove vg/test_cache
|  Logical volume "test_cache" successfully removed
|# lvs --all
|  LV   VG Attr   LSize   Pool Origin Data%  Meta%  Move 
Log Cpy%Sync Convert
|  test vg -wi-a-   1,00g

> This is a rather unexpected and dangerous behaviour change. While
> normally, these actions could be undone with vgcfgrestore, I have discard
> enabled in my lvm2.conf, which cannot be undone. (By sheer luck did I not
> lose any data, because I wanted to decomission the volume anyway).

There is a reason why discard is of by default.

Bastian

-- 
Immortality consists largely of boredom.
-- Zefrem Cochrane, "Metamorphosis", stardate 3219.8

Processed: [bts-link] source package src:bedtools

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:bedtools
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #831833 (http://bugs.debian.org/831833)
> # Bug title: bedtools groupby broken; will break users pipelines.
> #  * https://github.com/arq5x/bedtools2/issues/418
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 831833 + fixed-upstream
Bug #831833 [src:bedtools] bedtools groupby broken; will break users pipelines.
Added tag(s) fixed-upstream.
> usertags 831833 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 831833 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
831833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#832275: marked as done (wine: FTBFS against gnutls 3.5)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2016 17:31:31 +
with message-id 
and subject line Bug#832275: fixed in wine 1.8.3-3
has caused the Debian Bug report #832275,
regarding wine: FTBFS against gnutls 3.5
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.)


-- 
832275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine
Version: 1.8.3-2
Severity: important

Hello,

wine FTBFS against libgnutls28-dev 3.5.2-1 (avainable in experimental:

gcc -m64 -c -o schannel_gnutls.o schannel_gnutls.c -I. -I../../include 
-I/usr/include/p11-kit-1 -D__WINESRC__ \
  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wempty-body \
  -Wignored-qualifiers -Wstrict-prototypes -Wtype-limits 
-Wunused-but-set-parameter -Wvla \
  -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 -gstrict-dwarf -Werror 
-Wdate-time \
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-error
../../tools/winegcc/winegcc -o sensapi.dll.fake -B../../tools/winebuild -m64 
-fasynchronous-unwind-tables -shared sensapi.spec \
  sensapi.o -lwine ../../libs/port/libwine_port.a -Wl,-z,relro -Wl,-z,now 
-Wl,-rpath,/usr/lib/x86_64-linux-gnu/wine
schannel_gnutls.c:45:12: error: conflicting types for 
'gnutls_cipher_get_block_size'
 extern int gnutls_cipher_get_block_size(gnutls_cipher_algorithm_t algorithm);
^
In file included from schannel_gnutls.c:28:0:
/usr/include/gnutls/crypto.h:59:10: note: previous declaration of 
'gnutls_cipher_get_block_size' was here
 unsigned gnutls_cipher_get_block_size(gnutls_cipher_algorithm_t algorithm) 
__GNUTLS_CONST__;
  ^
Makefile:284: recipe for target 'schannel_gnutls.o' failed
make[2]: *** [schannel_gnutls.o] Error 1

This does not apply to wine-development 1.9.14-1, I guess 
http://source.winehq.org/git/wine.git/commitdiff/bf5ac531a030bce9e798ab66bc53e84a65ca8fdb
 fixed the issue.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: wine
Source-Version: 1.8.3-3

We believe that the bug you reported is fixed in the latest version of
wine, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jens Reyer  (supplier of updated wine package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 08 Aug 2016 14:36:29 +0200
Source: wine
Binary: wine wine-binfmt wine32 wine64 wine32-preloader wine64-preloader 
wine32-tools wine64-tools fonts-wine libwine libwine-dev
Architecture: source
Version: 1.8.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Jens Reyer 
Description:
 fonts-wine - Windows API implementation - fonts
 libwine- Windows API implementation - library
 libwine-dev - Windows API implementation - development files
 wine   - Windows API implementation - standard suite
 wine-binfmt - Windows API implementation - binfmt support
 wine32 - Windows API implementation - 32-bit binary loader
 wine32-preloader - Windows API implementation - prelinked 32-bit binary loader
 wine32-tools - Windows API implementation - 32-bit developer tools
 wine64 - Windows API implementation - 64-bit binary loader
 wine64-preloader - Windows API implementation - prelinked 64-bit binary loader
 wine64-tools - Windows API implementation - 64-bit developer tools
Closes: 832041 832275
Changes:
 wine (1.8.3-3) unstable; urgency=medium
 .
   * Cherrypick changes from master:
 - Fix wineserver manpages for Debian's default persistence value (see:
   #816020).
 - Drop alternative depends on perl:any (now handled by debhelper).
   Bump build-dep on debhelper version to >= 9.20160702.
 - Add removal instructions for binfmt support to README.debian.
 - Add Recommends g++ or g++-multilib to the -tools (closes: #832041).
   * 

Bug#833773: freeorion: FTBFS with boost1.61

[Markus Koschany]

clone -1
reassign -1 src:boost1.61
retitle -1 error: no type named 'types' in 'boost
found -1 1.61.0+dfsg-2.1
forwarded -1 https://svn.boost.org/trac/boost/ticket/12349
affects -1 freeorion
forwarded 833773 https://github.com/freeorion/freeorion/issues/777
thanks

On Mon, 8 Aug 2016 15:19:14 + Mattia Rizzolo  wrote:
> source: freeorion
> version: 0.4.5+git20160707-1
> severity: serious
> 
> Dear maintainer,
> 
> your package failed to build on buildds during a rebuild for the
> boost1.61 transition, using gcc6 as a compiler.
> You can see the failed build log at
> https://buildd.debian.org/status/logs.php?pkg=freeorion=0.4.5%2Bgit20160707-1%2Bb1

Hello Mattia,

thanks for your report. This is apparently a regression in Boost 1.61.
At least FreeOrion's upstream thinks so and there is already an open bug
report for this issue on the Boost issue tracker.

https://svn.boost.org/trac/boost/ticket/12349

Upstream bug report for FreeOrion:

https://github.com/freeorion/freeorion/issues/777

I think this issue should be reassigned to src:boost1.61 but I'm just
cloning the bug report for now to allow the Boost maintainer and others
to get involved in the discussion. We can always merge the bugs again later.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: bug 833681 is forwarded to http://tickets.musicbrainz.org/browse/PICARD-833, merging 833679 833681

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 833681 http://tickets.musicbrainz.org/browse/PICARD-833
Bug #833681 [picard] picard fails on start
Set Bug forwarded-to-address to 
'http://tickets.musicbrainz.org/browse/PICARD-833'.
> merge 833679 833681
Bug #833679 [picard] BitPaddedInt import error
Bug #833679 [picard] BitPaddedInt import error
Marked as found in versions picard/1.3.2-3.
Bug #833681 [picard] picard fails on start
Merged 833679 833681
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833679
833681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833783: marked as done (cdbs: please invoke perl build processes with -I. [CVE-2016-1238])

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2016 16:53:26 +0100
with message-id <20160808155326.gh27...@urchin.earth.li>
and subject line duplicate
has caused the Debian Bug report #833783,
regarding cdbs: please invoke perl build processes with -I. [CVE-2016-1238]
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.)


-- 
833783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdbs
Version: 0.4.142
Severity: serious
Justification: https://lists.debian.org/debian-release/2016/07/msg00476.html
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal

As per the referenced thread, we are going to remove '.' from @INC,
the perl module search path, by default, shortly. Please can you apply
something like the attached patches (which were uploaded as a security
update 0.4.130+deb8u1) at your earliest convenience? This will fix
a substantial number of FTBFS bugs resulting from such a change.

The attachments are from my local git repository which I used to 
prepare the jessie-security update, to import into the official repo
should you wish. This should make merging/cherry-picking easier.

Thanks,
Dominic.
>From 494b17cb191b0ba216194b38182f69105811e33b Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Sat, 9 Jul 2016 11:24:41 +0200
Subject: [PATCH 1/2] Invoke Makefile.PL and Build.PL with perl -I. as part of
 the fixes for CVE-2016-1238

---
 1/class/perl-build.mk.in  | 2 +-
 1/class/perl-makemaker-vars.mk.in | 2 +-
 1/class/perlmodule-vars.mk.in | 2 +-
 debian/changelog  | 8 
 4 files changed, 11 insertions(+), 3 deletions(-)

diff --git a/1/class/perl-build.mk.in b/1/class/perl-build.mk.in
index 41615fc..1b459df 100644
--- a/1/class/perl-build.mk.in
+++ b/1/class/perl-build.mk.in
@@ -56,7 +56,7 @@ export AUTOMATED_TESTING = $(DEB_PERL_AUTOMATED_TESTING)
 common-configure-arch common-configure-indep:: $(DEB_PERL_SRCDIR)/Build
 $(DEB_PERL_SRCDIR)/Build:
 	$(cdbs_perl_srcdir_check)
-	cd $(cdbs_perl_curbuilddir) && perl Build.PL $(DEB_PERL_BUILD_CONFIGURE_TARGET) $(DEB_PERL_CONFIGURE_ARGS) $(DEB_PERL_CONFIGURE_FLAGS)
+	cd $(cdbs_perl_curbuilddir) && perl -I. Build.PL $(DEB_PERL_BUILD_CONFIGURE_TARGET) $(DEB_PERL_CONFIGURE_ARGS) $(DEB_PERL_CONFIGURE_FLAGS)
 
 common-build-arch common-build-indep:: debian/stamp-perl-build
 debian/stamp-perl-build:
diff --git a/1/class/perl-makemaker-vars.mk.in b/1/class/perl-makemaker-vars.mk.in
index 17b2a25..6bc05fb 100644
--- a/1/class/perl-makemaker-vars.mk.in
+++ b/1/class/perl-makemaker-vars.mk.in
@@ -44,7 +44,7 @@ DEB_MAKE_EXTRA_ARGS = \
 		$(cdbs_perl_lddlflags))" \
 	$(DEB_MAKE_PARALLEL)
 
-DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl Makefile.PL \
+DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl -I. Makefile.PL \
 	$(DEB_MAKEMAKER_NORMAL_ARGS) \
 	$(DEB_MAKEMAKER_USER_FLAGS) \
 	INSTALLDIRS=vendor
diff --git a/1/class/perlmodule-vars.mk.in b/1/class/perlmodule-vars.mk.in
index 9c69e9a..02e01ef 100644
--- a/1/class/perlmodule-vars.mk.in
+++ b/1/class/perlmodule-vars.mk.in
@@ -49,7 +49,7 @@ DEB_MAKE_EXTRA_ARGS = \
 # Unset for standard debhelper rules (use debian/tmp if multiple packages).
 DEB_MAKEMAKER_PACKAGE ?= $(firstword $(if $(_cdbs_rules_debhelper),$(shell dh_listpackages),$(shell $(_cdbs_scripts_path)/list-packages)))
 
-DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl Makefile.PL $(DEB_MAKEMAKER_USER_FLAGS) INSTALLDIRS=vendor
+DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl -I. Makefile.PL $(DEB_MAKEMAKER_USER_FLAGS) INSTALLDIRS=vendor
 
 # Set some MakeMaker defaults
 # FIXME: Restructure to allow early override
diff --git a/debian/changelog b/debian/changelog
index 994bee2..bc16d84 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+cdbs (0.4.130+deb8u1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Invoke Makefile.PL and Build.PL with perl -I. as part of the fixes
+for CVE-2016-1238
+
+ -- Dominic Hargreaves   Sat, 09 Jul 2016 11:24:14 +0200
+
 cdbs (0.4.130) unstable; urgency=medium
 
   * Fix quoting of compiler flags in perlmodule-vars.mk.
-- 
2.1.4

>From 25c61ff13ca959dd53380ad3ea8a01f7e6c49407 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Mon, 25 Jul 2016 09:34:18 +0100
Subject: [PATCH 2/2] releasing package cdbs version 0.4.130+deb8u1

---
 debian/changelog | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index bc16d84..5bc4c42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,10 @@
-cdbs (0.4.130+deb8u1) 

Bug#833781: marked as done (debhelper: please invoke perl build processes with -I. [CVE-2016-1238])

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2016 16:52:52 +0100
with message-id <20160808155252.gg27...@urchin.earth.li>
and subject line duplicate
has caused the Debian Bug report #833781,
regarding debhelper: please invoke perl build processes with -I. [CVE-2016-1238]
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.)


-- 
833781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 9.20160709
Severity: serious
Justification: https://lists.debian.org/debian-release/2016/07/msg00476.html
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal

As per the referenced thread, we are going to remove '.' from @INC,
the perl module search path, by default, shortly. Please can you apply
something like the attached patches (which were uploaded as a security
update 9.20150101+deb8u2) at your earliest convenience? This will fix
a substantial number of FTBFS bugs resulting from such a change.

The attachments are from my local git repository which I used to 
prepare the jessie-security update, to import into the official repo
should you wish. This should make merging/cherry-picking easier.

Thanks,
Dominic.
>From d4ac7680af8f2d9c265bf96b9cb96942c7fe54a7 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Thu, 7 Jul 2016 16:54:15 +0200
Subject: [PATCH 1/4] Invoke Makefile.PL and Build.PL with perl -I. as part of
 the fixes for CVE-2016-1238

---
 Debian/Debhelper/Buildsystem/perl_build.pm | 2 +-
 Debian/Debhelper/Buildsystem/perl_makemaker.pm | 2 +-
 debian/changelog   | 8 
 3 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/Debian/Debhelper/Buildsystem/perl_build.pm b/Debian/Debhelper/Buildsystem/perl_build.pm
index 4cfbcb4..6b2ef8b 100644
--- a/Debian/Debhelper/Buildsystem/perl_build.pm
+++ b/Debian/Debhelper/Buildsystem/perl_build.pm
@@ -48,7 +48,7 @@ sub configure {
 	if ($ENV{LDFLAGS} && ! compat(8)) {
 		push @flags, "--config", "ld=$Config{ld} $ENV{CFLAGS} $ENV{LDFLAGS}";
 	}
-	$this->do_perl("Build.PL", "--installdirs", "vendor", @flags, @_);
+	$this->do_perl("-I.", "Build.PL", "--installdirs", "vendor", @flags, @_);
 }
 
 sub build {
diff --git a/Debian/Debhelper/Buildsystem/perl_makemaker.pm b/Debian/Debhelper/Buildsystem/perl_makemaker.pm
index 60cda3d..c4f6b42 100644
--- a/Debian/Debhelper/Buildsystem/perl_makemaker.pm
+++ b/Debian/Debhelper/Buildsystem/perl_makemaker.pm
@@ -54,7 +54,7 @@ sub configure {
 		push @flags, "LD=$Config{ld} $ENV{CFLAGS} $ENV{LDFLAGS}";
 	}
 
-	$this->doit_in_sourcedir("perl", "Makefile.PL", "INSTALLDIRS=vendor",
+	$this->doit_in_sourcedir("perl", "-I.", "Makefile.PL", "INSTALLDIRS=vendor",
 		# if perl_build is not tested first, need to pass packlist
 		# option to handle fallthrough case
 		(compat(7) ? "create_packlist=0" : ()),
diff --git a/debian/changelog b/debian/changelog
index a6408c7..d1455c4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+debhelper (9.20150101+deb8u1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Invoke Makefile.PL and Build.PL with perl -I. as part of the fixes for
+CVE-2016-1238
+
+ -- Dominic Hargreaves   Thu, 07 Jul 2016 16:53:02 +0200
+
 debhelper (9.20150101) unstable; urgency=medium
 
   [ Niels Thykier ]
-- 
2.1.4

>From 142436ea9b345e35c70c55cb3163b6dfe4c32385 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Wed, 20 Jul 2016 00:25:25 +0100
Subject: [PATCH 2/4] Export PERL_USE_UNSAFE_INC to fix a further set of
 packages which fail to build with . removed from @INC

---
 Debian/Debhelper/Dh_Lib.pm | 5 +
 debian/changelog   | 2 ++
 2 files changed, 7 insertions(+)

diff --git a/Debian/Debhelper/Dh_Lib.pm b/Debian/Debhelper/Dh_Lib.pm
index 0519d20..64ea4ac 100644
--- a/Debian/Debhelper/Dh_Lib.pm
+++ b/Debian/Debhelper/Dh_Lib.pm
@@ -982,6 +982,11 @@ sub set_buildflags {
 	return if $ENV{DH_INTERNAL_BUILDFLAGS} || compat(8);
 	$ENV{DH_INTERNAL_BUILDFLAGS}=1;
 
+	# Export PERL_USE_UNSAFE_INC as a transitional step to allow us
+	# to remove . from @INC by default without breaking packages which
+	# rely on this [CVE-2016-1238]
+	$ENV{PERL_USE_UNSAFE_INC}=1;
+
 	eval "use Dpkg::BuildFlags";
 	if ($@) {
 		warning "unable to load build flags: $@";
diff --git a/debian/changelog b/debian/changelog
index d1455c4..c5d2a6d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ debhelper (9.20150101+deb8u1) UNRELEASED; urgency=medium
   * Non-maintainer upload.
   * Invoke Makefile.PL and 

Bug#833783: cdbs: please invoke perl build processes with -I. [CVE-2016-1238]

[Dominic Hargreaves]

Package: cdbs
Version: 0.4.142
Severity: serious
Justification: https://lists.debian.org/debian-release/2016/07/msg00476.html
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal

As per the referenced thread, we are going to remove '.' from @INC,
the perl module search path, by default, shortly. Please can you apply
something like the attached patches (which were uploaded as a security
update 0.4.130+deb8u1) at your earliest convenience? This will fix
a substantial number of FTBFS bugs resulting from such a change.

The attachments are from my local git repository which I used to 
prepare the jessie-security update, to import into the official repo
should you wish. This should make merging/cherry-picking easier.

Thanks,
Dominic.
>From 494b17cb191b0ba216194b38182f69105811e33b Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Sat, 9 Jul 2016 11:24:41 +0200
Subject: [PATCH 1/2] Invoke Makefile.PL and Build.PL with perl -I. as part of
 the fixes for CVE-2016-1238

---
 1/class/perl-build.mk.in  | 2 +-
 1/class/perl-makemaker-vars.mk.in | 2 +-
 1/class/perlmodule-vars.mk.in | 2 +-
 debian/changelog  | 8 
 4 files changed, 11 insertions(+), 3 deletions(-)

diff --git a/1/class/perl-build.mk.in b/1/class/perl-build.mk.in
index 41615fc..1b459df 100644
--- a/1/class/perl-build.mk.in
+++ b/1/class/perl-build.mk.in
@@ -56,7 +56,7 @@ export AUTOMATED_TESTING = $(DEB_PERL_AUTOMATED_TESTING)
 common-configure-arch common-configure-indep:: $(DEB_PERL_SRCDIR)/Build
 $(DEB_PERL_SRCDIR)/Build:
 	$(cdbs_perl_srcdir_check)
-	cd $(cdbs_perl_curbuilddir) && perl Build.PL $(DEB_PERL_BUILD_CONFIGURE_TARGET) $(DEB_PERL_CONFIGURE_ARGS) $(DEB_PERL_CONFIGURE_FLAGS)
+	cd $(cdbs_perl_curbuilddir) && perl -I. Build.PL $(DEB_PERL_BUILD_CONFIGURE_TARGET) $(DEB_PERL_CONFIGURE_ARGS) $(DEB_PERL_CONFIGURE_FLAGS)
 
 common-build-arch common-build-indep:: debian/stamp-perl-build
 debian/stamp-perl-build:
diff --git a/1/class/perl-makemaker-vars.mk.in b/1/class/perl-makemaker-vars.mk.in
index 17b2a25..6bc05fb 100644
--- a/1/class/perl-makemaker-vars.mk.in
+++ b/1/class/perl-makemaker-vars.mk.in
@@ -44,7 +44,7 @@ DEB_MAKE_EXTRA_ARGS = \
 		$(cdbs_perl_lddlflags))" \
 	$(DEB_MAKE_PARALLEL)
 
-DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl Makefile.PL \
+DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl -I. Makefile.PL \
 	$(DEB_MAKEMAKER_NORMAL_ARGS) \
 	$(DEB_MAKEMAKER_USER_FLAGS) \
 	INSTALLDIRS=vendor
diff --git a/1/class/perlmodule-vars.mk.in b/1/class/perlmodule-vars.mk.in
index 9c69e9a..02e01ef 100644
--- a/1/class/perlmodule-vars.mk.in
+++ b/1/class/perlmodule-vars.mk.in
@@ -49,7 +49,7 @@ DEB_MAKE_EXTRA_ARGS = \
 # Unset for standard debhelper rules (use debian/tmp if multiple packages).
 DEB_MAKEMAKER_PACKAGE ?= $(firstword $(if $(_cdbs_rules_debhelper),$(shell dh_listpackages),$(shell $(_cdbs_scripts_path)/list-packages)))
 
-DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl Makefile.PL $(DEB_MAKEMAKER_USER_FLAGS) INSTALLDIRS=vendor
+DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl -I. Makefile.PL $(DEB_MAKEMAKER_USER_FLAGS) INSTALLDIRS=vendor
 
 # Set some MakeMaker defaults
 # FIXME: Restructure to allow early override
diff --git a/debian/changelog b/debian/changelog
index 994bee2..bc16d84 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+cdbs (0.4.130+deb8u1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Invoke Makefile.PL and Build.PL with perl -I. as part of the fixes
+for CVE-2016-1238
+
+ -- Dominic Hargreaves   Sat, 09 Jul 2016 11:24:14 +0200
+
 cdbs (0.4.130) unstable; urgency=medium
 
   * Fix quoting of compiler flags in perlmodule-vars.mk.
-- 
2.1.4

>From 25c61ff13ca959dd53380ad3ea8a01f7e6c49407 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Mon, 25 Jul 2016 09:34:18 +0100
Subject: [PATCH 2/2] releasing package cdbs version 0.4.130+deb8u1

---
 debian/changelog | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index bc16d84..5bc4c42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,10 @@
-cdbs (0.4.130+deb8u1) UNRELEASED; urgency=medium
+cdbs (0.4.130+deb8u1) jessie-security; urgency=high
 
   * Non-maintainer upload.
   * Invoke Makefile.PL and Build.PL with perl -I. as part of the fixes
 for CVE-2016-1238
 
- -- Dominic Hargreaves   Sat, 09 Jul 2016 11:24:14 +0200
+ -- Dominic Hargreaves   Mon, 25 Jul 2016 09:34:18 +0100
 
 cdbs (0.4.130) unstable; urgency=medium
 
-- 
2.1.4

Bug#833781: debhelper: please invoke perl build processes with -I. [CVE-2016-1238]

[Dominic Hargreaves]

Package: debhelper
Version: 9.20160709
Severity: serious
Justification: https://lists.debian.org/debian-release/2016/07/msg00476.html
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal

As per the referenced thread, we are going to remove '.' from @INC,
the perl module search path, by default, shortly. Please can you apply
something like the attached patches (which were uploaded as a security
update 9.20150101+deb8u2) at your earliest convenience? This will fix
a substantial number of FTBFS bugs resulting from such a change.

The attachments are from my local git repository which I used to 
prepare the jessie-security update, to import into the official repo
should you wish. This should make merging/cherry-picking easier.

Thanks,
Dominic.
>From d4ac7680af8f2d9c265bf96b9cb96942c7fe54a7 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Thu, 7 Jul 2016 16:54:15 +0200
Subject: [PATCH 1/4] Invoke Makefile.PL and Build.PL with perl -I. as part of
 the fixes for CVE-2016-1238

---
 Debian/Debhelper/Buildsystem/perl_build.pm | 2 +-
 Debian/Debhelper/Buildsystem/perl_makemaker.pm | 2 +-
 debian/changelog   | 8 
 3 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/Debian/Debhelper/Buildsystem/perl_build.pm b/Debian/Debhelper/Buildsystem/perl_build.pm
index 4cfbcb4..6b2ef8b 100644
--- a/Debian/Debhelper/Buildsystem/perl_build.pm
+++ b/Debian/Debhelper/Buildsystem/perl_build.pm
@@ -48,7 +48,7 @@ sub configure {
 	if ($ENV{LDFLAGS} && ! compat(8)) {
 		push @flags, "--config", "ld=$Config{ld} $ENV{CFLAGS} $ENV{LDFLAGS}";
 	}
-	$this->do_perl("Build.PL", "--installdirs", "vendor", @flags, @_);
+	$this->do_perl("-I.", "Build.PL", "--installdirs", "vendor", @flags, @_);
 }
 
 sub build {
diff --git a/Debian/Debhelper/Buildsystem/perl_makemaker.pm b/Debian/Debhelper/Buildsystem/perl_makemaker.pm
index 60cda3d..c4f6b42 100644
--- a/Debian/Debhelper/Buildsystem/perl_makemaker.pm
+++ b/Debian/Debhelper/Buildsystem/perl_makemaker.pm
@@ -54,7 +54,7 @@ sub configure {
 		push @flags, "LD=$Config{ld} $ENV{CFLAGS} $ENV{LDFLAGS}";
 	}
 
-	$this->doit_in_sourcedir("perl", "Makefile.PL", "INSTALLDIRS=vendor",
+	$this->doit_in_sourcedir("perl", "-I.", "Makefile.PL", "INSTALLDIRS=vendor",
 		# if perl_build is not tested first, need to pass packlist
 		# option to handle fallthrough case
 		(compat(7) ? "create_packlist=0" : ()),
diff --git a/debian/changelog b/debian/changelog
index a6408c7..d1455c4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+debhelper (9.20150101+deb8u1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Invoke Makefile.PL and Build.PL with perl -I. as part of the fixes for
+CVE-2016-1238
+
+ -- Dominic Hargreaves   Thu, 07 Jul 2016 16:53:02 +0200
+
 debhelper (9.20150101) unstable; urgency=medium
 
   [ Niels Thykier ]
-- 
2.1.4

>From 142436ea9b345e35c70c55cb3163b6dfe4c32385 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Wed, 20 Jul 2016 00:25:25 +0100
Subject: [PATCH 2/4] Export PERL_USE_UNSAFE_INC to fix a further set of
 packages which fail to build with . removed from @INC

---
 Debian/Debhelper/Dh_Lib.pm | 5 +
 debian/changelog   | 2 ++
 2 files changed, 7 insertions(+)

diff --git a/Debian/Debhelper/Dh_Lib.pm b/Debian/Debhelper/Dh_Lib.pm
index 0519d20..64ea4ac 100644
--- a/Debian/Debhelper/Dh_Lib.pm
+++ b/Debian/Debhelper/Dh_Lib.pm
@@ -982,6 +982,11 @@ sub set_buildflags {
 	return if $ENV{DH_INTERNAL_BUILDFLAGS} || compat(8);
 	$ENV{DH_INTERNAL_BUILDFLAGS}=1;
 
+	# Export PERL_USE_UNSAFE_INC as a transitional step to allow us
+	# to remove . from @INC by default without breaking packages which
+	# rely on this [CVE-2016-1238]
+	$ENV{PERL_USE_UNSAFE_INC}=1;
+
 	eval "use Dpkg::BuildFlags";
 	if ($@) {
 		warning "unable to load build flags: $@";
diff --git a/debian/changelog b/debian/changelog
index d1455c4..c5d2a6d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ debhelper (9.20150101+deb8u1) UNRELEASED; urgency=medium
   * Non-maintainer upload.
   * Invoke Makefile.PL and Build.PL with perl -I. as part of the fixes for
 CVE-2016-1238
+  * Export PERL_USE_UNSAFE_INC to fix a further set of packages which
+fail to build with . removed from @INC
 
  -- Dominic Hargreaves   Thu, 07 Jul 2016 16:53:02 +0200
 
-- 
2.1.4

>From 4ba75eee566c3a6af6c75c2119d938e3fb7796b9 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves 
Date: Sun, 24 Jul 2016 19:12:52 +0100
Subject: [PATCH 3/4] releasing package debhelper version 9.20150101+deb8u1

---
 debian/changelog | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c5d2a6d..dcaa609 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-debhelper (9.20150101+deb8u1) UNRELEASED; urgency=medium
+debhelper (9.20150101+deb8u1) jessie-security; urgency=high
 
   * 

Bug#833776: gnash: FTBFS with boost1.61

[Mattia Rizzolo]

source: gnash
version: 0.8.11~git20160608-1
severity: serious

Dear maintianer,

your package failed to build during a rebuild for the boost1.61
transition using gcc-6 as a compiler.
You can see the failed build logs at
https://buildd.debian.org/status/logs.php?pkg=gnash=0.8.11~git20160608-1%2Bb1

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: reopening 833609

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 833609
Bug #833609 {Done: Alexandre Viau } [ring] ring: Crashes on 
startup after showing popup - triggered by missing dring?
Bug reopened
Ignoring request to alter fixed versions of bug #833609 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: mopidy-podcast: FTBFS under some timezones (eg. GMT-14)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 833774 https://github.com/tkem/mopidy-podcast/pull/40
Bug #833774 [src:mopidy-podcast] mopidy-podcast: FTBFS under some timezones 
(eg. GMT-14)
Set Bug forwarded-to-address to 
'https://github.com/tkem/mopidy-podcast/pull/40'.
> tags 833774 + patch
Bug #833774 [src:mopidy-podcast] mopidy-podcast: FTBFS under some timezones 
(eg. GMT-14)
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 833609 to ring

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 833609 ring
Bug #833609 {Done: Alexandre Viau } [ring-daemon] ring: 
Crashes on startup after showing popup - triggered by missing dring?
Bug reassigned from package 'ring-daemon' to 'ring'.
No longer marked as found in versions ring/20160729.2.7a7dbd6~dfsg1-1.
No longer marked as fixed in versions ring/20160729.2.7a7dbd6~dfsg1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unmerging 833609

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 833609
Bug #833609 {Done: Alexandre Viau } [ring-daemon] ring: 
Crashes on startup after showing popup - triggered by missing dring?
Bug #833571 {Done: Salvatore Bonaccorso } [ring-daemon] 
ring-deamon: dring missing
Bug #833704 {Done: Alexandre Viau } [ring-daemon] ring: not 
starting
Disconnected #833609 from all other report(s).
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833571
833609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833609
833704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833609: unmerging 833609

[Alexandre Viau]

Hello,

> Really?  That bug seem to be about the dring binary being missing,
> not about accessing released memory and crashing, which was the issue
> I reported. Providing the binary do not really fix the code that is
> accessing released memory and crashing, just hides the problem until >
it bites someone later.

Oh, right.

In that case, this bug would be about using the software in a way that
is not meant to be, so I think that we should reduce the severity to
'normal'. Do you agree?

I will unmerge the bug, and reassign it to 'ring'.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#833775: frogatto: FTBFS with boost1.61

[Mattia Rizzolo]

source: frogatto
version: 1.3.1+dfsg-2
severity: serious

Dear maintainer,

your package failed to build on buildds during a rebuild for the
boost.161 transition.
you can see the failur logs at
https://buildd.debian.org/status/logs.php?pkg=frogatto=1.3.1%2Bdfsg-2%2Bb7
(and some elsewhere, the +bX number is not sync across architectures…)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#833773: freeorion: FTBFS with boost1.61

[Mattia Rizzolo]

source: freeorion
version: 0.4.5+git20160707-1
severity: serious

Dear maintainer,

your package failed to build on buildds during a rebuild for the
boost1.61 transition, using gcc6 as a compiler.
You can see the failed build log at
https://buildd.debian.org/status/logs.php?pkg=freeorion=0.4.5%2Bgit20160707-1%2Bb1

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#833493: cufflinks fails to build from source with gcc-6

[Andreas Tille]

Hi,

the cufflinks package in Debian received a bug report that it does not
build with gcc version 6 which will be the new default compiler inside
Debian.  Some analysis has shown[1] that the problematic code is in an
old code copy of liblemon which is verbosely copied into cufflinks
source code.  The suggested procedure was to link cufflinks against the
latest version of liblemon.  Unfortunately the interface of liblemon
has changed and its not a simple rebuild.

I wonder whether you intend to port cufflinks to the latest liblemon
version to make future versions of your code sustainable.  This would
be really helpful.

Kind regards

   Andreas.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833493#15

-- 
http://fam-tille.de

Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Mattia Rizzolo]

source: avogadro
version: 1.0.3-13
severity: serious

Dear maintainer,

your package failed to build on buildd during rebuilds for boost1.61
using gcc6 as a compiler.

you can see the build log for the failures at
https://buildd.debian.org/status/logs.php?pkg=avogadro=1.0.3-13.1%2Bb1=sid

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#833760: cufflinks: please use the default boost version

[Andreas Tille]

Hi Mattia,

On Mon, Aug 08, 2016 at 01:59:52PM +, Mattia Rizzolo wrote:
> your package depend on boost1.60, while we're transition to boost1.61
> (from 1.58).  1.60 never was the default.
> 
> We would like to remove 1.60, so please either bump the dependency to
> 1.61 or (preferred) use the unversioned stuff as provided by
> src:boost-defaults.

This issue was discussed in #833493.  Currently I can't upload since
cufflinks does not build.  If the new version of liblemon would not have
been rejected by ftpmaster for a reason others do not agree with[2] we
could have started to port cufflinks to the new liblemon library (which
is definitely not a trivial change but seems to me a promising way to
deal with the issue anyway - probably in connection with upstream).

Kind regards

  Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833493#15
[2] https://lists.debian.org/debian-devel/2016/08/msg00099.html

-- 
http://fam-tille.de

Processed: reassign 833704 to ring-daemon

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 833704 ring-daemon
Bug #833704 {Done: Alexandre Viau } [ring] ring: not starting
Bug reassigned from package 'ring' to 'ring-daemon'.
No longer marked as found in versions ring/20160729.2.7a7dbd6~dfsg1-1.
Ignoring request to alter fixed versions of bug #833704 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#832415: Further information: upstream software works fine

[Rafael Laboissière]

* Eric S Fraga  [2016-08-07 18:30]:


On Wednesday,  3 Aug 2016 at 12:17, Rafael Laboissière wrote:

* Eric S Fraga  [2016-07-25 17:50]:

Just a quick update: building the latest upstream version of octave 
along with the parallel package results in a system that works as it 
should.  No errors at all.


You mean, building Octave from source?

Which version?


Yes, from source.  4.0.3.


Ok, thanks.

Could you please provide a script that triggers the bug, as I asked in a 
previous message?


Best,

Rafael Laboissière

Bug#833764: libalog: build-dep on gnat-4.9

[Mattia Rizzolo]

source: libalog
version: 0.5.0-1
severity: serious

Dear maintainer,

your package has a build-depends on gnat-4.9.
We aim to not ship gnat-4.9 in stretch.  Besides, the default gnat is
not gnat-6.

Please remove that build-dep.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Felipe Sateler]

On 8 August 2016 at 02:59, Pete Batard  wrote:
> Thanks Felipe.
>
> I'm afraid it's still not completing successfully though:

Gah, I'm terribly sorry. I have a fix here, but I'm testbuilding first
before asking you to do that again. I'll let you know as soon as I
have built it.

-- 

Saludos,
Felipe Sateler

Bug#833759: deal.ii: please use the default boost version

[Mattia Rizzolo]

source: deal.ii
version: 8.4.1-1
severity: serious

Dear maintainer,

your package depend on boost1.60, while we're transition to boost1.61
(from 1.58).  1.60 never was the default.

We would like to remove 1.60, so please either bump the dependency to
1.61 or (preferred) use the unversioned stuff as provided by
src:boost-defaults.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: found 832908 in 2.0.6-1, fixed 832908 in 2.0.6-1+deb7u1, found 833087 in 2.0.6-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # add LTS versions
> found 832908 2.0.6-1
Bug #832908 [mongodb-clients] mongodb: CVE-2016-6494: world-readable .dbshell 
history file
There is no source info for the package 'mongodb-clients' at version '2.0.6-1' 
with architecture ''
Unable to make a source version for version '2.0.6-1'
Marked as found in versions 2.0.6-1.
> fixed 832908 2.0.6-1+deb7u1
Bug #832908 [mongodb-clients] mongodb: CVE-2016-6494: world-readable .dbshell 
history file
There is no source info for the package 'mongodb-clients' at version 
'2.0.6-1+deb7u1' with architecture ''
Unable to make a source version for version '2.0.6-1+deb7u1'
Marked as fixed in versions 2.0.6-1+deb7u1.
> found 833087 2.0.6-1
Bug #833087 [mongodb-server] bruteforcable challenge responses in unprotected 
logfile
There is no source info for the package 'mongodb-server' at version '2.0.6-1' 
with architecture ''
Unable to make a source version for version '2.0.6-1'
Marked as found in versions 2.0.6-1.
> fixed 833087 2.0.6-1+deb7u1
Bug #833087 [mongodb-server] bruteforcable challenge responses in unprotected 
logfile
There is no source info for the package 'mongodb-server' at version 
'2.0.6-1+deb7u1' with architecture ''
Unable to make a source version for version '2.0.6-1+deb7u1'
Marked as fixed in versions 2.0.6-1+deb7u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
832908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832908
833087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833756: marked as done (mapnik: FTBFS with gcc6/boost1.61/icu57)

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2016 15:46:18 +0200
with message-id <58e61452-5c28-ff4d-e69c-7115e5bb0...@xs4all.nl>
and subject line Re: Bug#833756: mapnik: FTBFS with gcc6/boost1.61/icu57
has caused the Debian Bug report #833756,
regarding mapnik: FTBFS with gcc6/boost1.61/icu57
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.)


-- 
833756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: mapnik
version: 3.0.11+ds-1
severity: serious

Dear maintainer,

your package failed to build on buildds during the transition to
boost1.61 and icu57 using gcc6 as a compiler.
you can see the failed build logs at
https://buildd.debian.org/status/logs.php?pkg=mapnik=3.0.11%2Bds-1%2Bb6=sid

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
fixed 833756 mapnik/3.0.12~rc1+ds-1~exp1
thanks

Hi Mattia,

Thanks for caring about these transitions.

I'm well aware of the mapnik build failure with Boost 1.61 as I've been
following the transitions closely.

Mapnik 3.0.12-rc1 has support for Boost 1.61 and is available in
experimental along with the rest of the Mapnik family which needed to be
rebuilt with Mapnik 3.0.12 (along with changes for the new Mapnik).

I'm going to wait at least a week before moving the packages from
experimental to unstable. Hopefully Mapnik 3.0.12 final will be released
by then, along with a new node-mapnik that officially support 3.0.12. I
prefer to not have pre-releases in unstable. Ubuntu as usual has not
bothered to coordinate with the maintainers in Debian, and has already
synced the updated Mapnik packages from experimental, which I think is
premature.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: Bug#833756: mapnik: FTBFS with gcc6/boost1.61/icu57

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 833756 mapnik/3.0.12~rc1+ds-1~exp1
Bug #833756 [mapnik] mapnik: FTBFS with gcc6/boost1.61/icu57
Marked as fixed in versions mapnik/3.0.12~rc1+ds-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833753: ledger: FTBFS on buildds after gcc6/icu57/boost1.61

[David Bremner]

Mattia Rizzolo  writes:

> [ Unknown signature status ]
> source: ledger
> version:  3.1.1+dfsg1-1
> severity: serious
>
> Dear maintainer,
>
> your package failed to build on buildds during a transition rebuild
> using gcc-6 boost1.61 and icu57.
> One or more of those changed toolchain packages caused the failure, see
> https://buildd.debian.org/status/logs.php?pkg=ledger=3.1.1%2Bdfsg1-1%2Bb2=sid

Thanks for the report. I had previously passed on the failing build log
to upstream; hopefully they will figure something out.

I also tried a pre-release snapshot of 3.1.2, and it fails in the same
way.

d

Bug#833655: ftp server update

[Kees Leune]

I'll try to crank out an update, but I'm not sure when I'll have the time
to do so. The environment variable workaround should indeed work.

-- 
http://about.me/keesleune

Bug#833753: ledger: FTBFS on buildds after gcc6/icu57/boost1.61

[Mattia Rizzolo]

source: ledger
version:  3.1.1+dfsg1-1
severity: serious

Dear maintainer,

your package failed to build on buildds during a transition rebuild
using gcc-6 boost1.61 and icu57.
One or more of those changed toolchain packages caused the failure, see
https://buildd.debian.org/status/logs.php?pkg=ledger=3.1.1%2Bdfsg1-1%2Bb2=sid

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Bug#814905: liblog4cplus-1.1-9: C++11 methods missing from the binary

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #814905 [liblog4cplus-1.1-9] liblog4cplus-1.1-9: C++11 methods missing from 
the binary
Severity set to 'grave' from 'critical'
> tags -1 pending
Bug #814905 [liblog4cplus-1.1-9] liblog4cplus-1.1-9: C++11 methods missing from 
the binary
Added tag(s) pending.

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

Bug#814905: liblog4cplus-1.1-9: C++11 methods missing from the binary

[James Cowgill]

Control: severity -1 grave
Control: tags -1 pending

Hi,

I have uploaded the following NMU to DELAYED/2 which fixes this bug,
based on the earlier patch by Jochen Sprickerhof. Please tell me if I
should cancel / delay it longer.

Now that GCC 6 is the default, this bug is RC because any users of this
package will very likely run into this linker error. While it could be
fixed by simply binNMUing it, I think patching it to use --std=c++11 is
more correct and also allows the package to be backported later if
that's ever wanted.

The NMU is attached.

Thanks,
James
diff -Nru log4cplus-1.1.2/debian/changelog log4cplus-1.1.2/debian/changelog
--- log4cplus-1.1.2/debian/changelog	2015-12-10 14:53:03.0 +
+++ log4cplus-1.1.2/debian/changelog	2016-08-08 11:06:16.0 +
@@ -1,3 +1,10 @@
+log4cplus (1.1.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Ensure C++11 methods are present in the library. (Closes: #814905)
+
+ -- James Cowgill   Mon, 08 Aug 2016 11:06:16 +
+
 log4cplus (1.1.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru log4cplus-1.1.2/debian/rules log4cplus-1.1.2/debian/rules
--- log4cplus-1.1.2/debian/rules	2015-12-10 14:56:15.0 +
+++ log4cplus-1.1.2/debian/rules	2016-08-08 11:04:48.0 +
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+export DEB_CXXFLAGS_MAINT_APPEND := --std=c++11
+
 %:
 	dh $@ --with autoreconf
 


signature.asc
Description: OpenPGP digital signature

Processed: merge grpc duplicate bug reports

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 812845 831250
Bug #812845 [src:grpc] grpc: FTBFS: httpscli_test: failed to connect to 
'ipv6:[::1]:54383': socket error: connection refused
Bug #812845 [src:grpc] grpc: FTBFS: httpscli_test: failed to connect to 
'ipv6:[::1]:54383': socket error: connection refused
Added tag(s) stretch and sid.
Bug #831250 [src:grpc] grpc: FTBFS: test httpscli_test failed
Merged 812845 831250
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812845
831250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#832834: Can't reproduce

[Martín Ferrari]

tags 832834 + moreinfo unreproducible
thanks

Hi Lucas,

I have tried to reproduce this problem in an up-to-date sid chroot, but
I get no errors. I also tried to run it with high CPU contention, in
case there was some timing issue, and the tests still pass correctly.

Can you please retry building this package and update the bug report?

Thanks.

-- 
Martín Ferrari (Tincho)

Bug#833743: Segfault in ReadRLEImage

[Bastien ROUCARIES]

Package: src:imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org


commit 68c13e10ab0415f1215f1e869ee851b373a3db70
Author: Cristy 
Date:   Tue May 17 15:05:03 2016 -0400

Segfault in ReadRLEImage

Trigger by corrupted RLE file. Buffer overflow class

bug: https://www.imagemagick.org/discourse-server/viewtopic.php?f=3=29710
origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/3e9165285eda6e1bb71172031d3048b51bb443a4

(cherry picked from commit 3e9165285eda6e1bb71172031d3048b51bb443a4)

Bug#828653: marked as done (FTBFS under Django 1.10)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2016 11:20:49 +
with message-id 
and subject line Bug#828653: fixed in django-pipeline 1.6.8-2
has caused the Debian Bug report #828653,
regarding FTBFS under Django 1.10
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.)


-- 
828653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-pipeline
Version: 1.6.8-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-pipeline FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


django-pipeline_1.6.8-1.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-pipeline
Source-Version: 1.6.8-2

We believe that the bug you reported is fixed in the latest version of
django-pipeline, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 828...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated django-pipeline package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Aug 2016 11:32:23 +
Source: django-pipeline
Binary: python-django-pipeline python3-django-pipeline 
python-django-pipeline-doc
Architecture: source all
Version: 1.6.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python-django-pipeline - Asset packaging library for Django
 python-django-pipeline-doc - Documentation for Django Pipeline library
 python3-django-pipeline - Asset packaging library for Django (Python3 version)
Closes: 828653
Changes:
 django-pipeline (1.6.8-2) unstable; urgency=medium
 .
   * Team upload.
   * Wrote patch to fix tests, which FTBFS with Django 1.10 (Closes: #828653).
 - 0003-Define-kwarg_name-in-pipeline_settings-class.patch
   * Standards-Version: 3.9.8 (no change).
Checksums-Sha1:
 a7d037c26e7dd9421a29675b929ffd098d3ee0f9 2408 django-pipeline_1.6.8-2.dsc
 d2a4ae70830a1b882de37ec62a4703a19071ed1f 4976 
django-pipeline_1.6.8-2.debian.tar.xz
 e82c1d80e4bb3dc96969a99bd54457f796ed311d 40020 
python-django-pipeline-doc_1.6.8-2_all.deb
 9694b3214c5e9fa0726e9a1e384cb19ae6237af3 22178 
python-django-pipeline_1.6.8-2_all.deb
 2eef157c34cd6065e53bd19b5283901a9a9d3612 21978 
python3-django-pipeline_1.6.8-2_all.deb
Checksums-Sha256:
 1f33eb0d71b2ff2ad16a5b915d0f4a90ca47ba3179b037510ffd11df4add5d98 2408 
django-pipeline_1.6.8-2.dsc
 634d1a9d905b09df3e838a38a2c68cd83e9a19c0074c6530952ca3faa177969d 4976 
django-pipeline_1.6.8-2.debian.tar.xz
 62d85e2034642faa070b3a078bf5426af24bbbe1d887ac2b0cfcb1e13f4154c5 40020 
python-django-pipeline-doc_1.6.8-2_all.deb
 e46e27a858e58c007404e1fc5464518c7baaab960757109902cc3ef11cd4419f 22178 
python-django-pipeline_1.6.8-2_all.deb
 d9046ab05cf868ec45186728f42581640ff9dc7dd3e8aa293379a00b2b457bf7 21978 
python3-django-pipeline_1.6.8-2_all.deb
Files:
 67772169b805afebbf9924552055aabe 2408 python optional 
django-pipeline_1.6.8-2.dsc
 ab294ef77694f46ae1648f37352320a1 4976 python optional 
django-pipeline_1.6.8-2.debian.tar.xz
 350ae6d148d5cb6143e7329ce42e40b4 40020 doc optional 
python-django-pipeline-doc_1.6.8-2_all.deb
 1f28a654789423bd2278a20caa420016 22178 python optional 
python-django-pipeline_1.6.8-2_all.deb
 411a9268bb820fbf44b5c8bb72120378 21978 python optional 
python3-django-pipeline_1.6.8-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#833738: python-popcon: assumes all-popcon-results.txt.gz is UTF-8

[Chris Lamb]

Source: python-popcon
Version: 1.3
Severity: serious
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Since (at least) 07-Aug-2016 14:04, the all-popcon-results.txt.gz file
contains an invalid line:

Package: libfyba0-dbg   0 2 0 0
--> Package: libf erdp-ommon0 0 0 1
Package: libg++2.8.1.3-dbg  0 0 0 1

That's (currently) line 54869. The "space" on the second line is actually
a 0xa0 character. This is making the package unusable.

$ python3
Python 3.5.2+ (default, Aug  5 2016, 08:07:14) 
[GCC 6.1.1 20160724] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import popcon
>>> popcon.package("foo")
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/popcon.py", line 145, in package
raw = package_raw(*packages)
  File "/usr/lib/python3/dist-packages/popcon.py", line 189, in package_raw
data = _fetch()
  File "/usr/lib/python3/dist-packages/popcon.py", line 108, in _fetch
txt = _decompress(txt)
  File "/usr/lib/python3/dist-packages/popcon.py", line 134, in _decompress
data = data.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 3574857: 
invalid start byte

You can see this happening here:

  
https://jenkins.debian.net/view/reproducible/view/problems/job/reproducible_html_notes/


Patch attached. NB. the comment in the lookup section.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/src/popcon.py b/src/popcon.py
index 4f089f0..670c514 100644
--- a/src/popcon.py
+++ b/src/popcon.py
@@ -115,7 +115,7 @@ def _parse(results):
 results = results.splitlines()
 for line in results:
 elems = line.split()
-if elems[0] != "Package:":
+if elems[0] != b"Package:":
 continue
 ans[elems[1]] = Package(*(int(i) for i in elems[2:]))
 return ans
@@ -131,7 +131,6 @@ def _decompress(compressed):
 gzippedstream = io.BytesIO(compressed)
 gzipper = gzip.GzipFile(fileobj=gzippedstream)
 data = gzipper.read()
-data = data.decode()
 return data
 
 
@@ -206,8 +205,11 @@ def package_raw(*packages):
 cached_timestamp = time.time()
 ans = dict()
 for pkg in packages:
-if pkg in data:
-ans[pkg] = data[pkg]
+# Lookup using bytestrings, but always index results by the original so
+# that callsites can look it up.
+lookup = pkg if isinstance(pkg, bytes) else pkg.encode('utf-8')
+if lookup in data:
+ans[pkg] = data[lookup]
 if KEEP_DATA:
 cached_data = data
 return ans

Processed: Re: [Reproducible-builds] [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 833695
Bug #833695 {Done: Bill Allombert } [popularity-contest] 
popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz contains 
invalid data
Bug reopened
Ignoring request to alter fixed versions of bug #833695 to the same values 
previously set
> severity 833695 important
Bug #833695 [popularity-contest] popularity-contest: 
http://popcon.debian.org/all-popcon-results.txt.gz contains invalid data
Severity set to 'important' from 'serious'
> clone 833695 -1
Bug #833695 [popularity-contest] popularity-contest: 
http://popcon.debian.org/all-popcon-results.txt.gz contains invalid data
Bug 833695 cloned as bug 833739
> reassign -1 python-popcon
Bug #833739 [popularity-contest] popularity-contest: 
http://popcon.debian.org/all-popcon-results.txt.gz contains invalid data
Bug reassigned from package 'popularity-contest' to 'python-popcon'.
No longer marked as found in versions popularity-contest/1.64.
Ignoring request to alter fixed versions of bug #833739 to the same values 
previously set
> severity -1 normal
Bug #833739 [python-popcon] popularity-contest: 
http://popcon.debian.org/all-popcon-results.txt.gz contains invalid data
Severity set to 'normal' from 'important'
> retitle -1 python-popcon must not crash on invalid data
Bug #833739 [python-popcon] popularity-contest: 
http://popcon.debian.org/all-popcon-results.txt.gz contains invalid data
Changed Bug title to 'python-popcon must not crash on invalid data' from 
'popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz 
contains invalid data'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833695
833739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833695: [Reproducible-builds] [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

[Holger Levsen]

reopen 833695
severity 833695 important
clone 833695 -1
reassign -1 python-popcon
severity -1 normal
retitle -1 python-popcon must not crash on invalid data
thanks

On Mon, Aug 08, 2016 at 11:34:43AM +0200, Chris Lamb wrote:
> > Please reassign to python-popcon.
> 
> Well, there are perhaps two bugs here, so simply reassigning won't be
> sufficient:
> 
> Firstly, all-popcon-results.txt.gz contains invalid data. I agree that
> the client should not be removed from testing but I could not find a
> suitable pseudo-package for the popcon "web" service.
>
> (The code that generates this file appears to be in the popularity-contest
> source package, hence why I filed it here)

Bill, following this I have reopened the bug and downgraded the
severity. 
 
> Where should this issue be raised? I don't care about the severity, more
> that it gets fixed. How can I help? :)

I also disagree with merely tracking an issue which breaks Debian
infrastrcuture on a mailinglist instead of a proper bug tracker.

Bill, if you really insist #833695 should not be assigned at
popularity-contest then please reassign it to qa.debian.org
pseudo-package.

> Secondly, src:python-popcon assumes valid data. Perhaps. But it would
> still have to raise an error if it could not parse the file so there's
> not much it could reasonably do. It *could* print a nicer exception so
> its easier to track down the problem, but that's purely aesthetic..

agreed, but that still would be nice, thus the cloned bug.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: found 833735 in 8:6.7.7.10-4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # mark as found in common anchestor
> found 833735 8:6.7.7.10-4
Bug #833735 [src:imagemagick] Coder path transversal
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#821471: adminer: PHP 7.0 Transition

[Chris Lamb]

Hi,

> I've prepared an NMU for adminer (versioned as 4.2.4-0.1) and
> attached a debdiff.

What happened with this NMU? :)

+  * Update d/watch to use github, which also directly provides tarballs.

Usually not polite to do in an NMU..


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#833735: Coder path transversal

[Bastien ROUCARIES]

Package: src:imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org


Imagemagick arbitrary module loading due to not escaping relative path



commit 3ed665639d7665fabdff33d77e3b8428854726da
Author: Cristy 
Date:   Thu Jun 2 13:44:20 2016 -0400

Coder path traversal is not authorized

Bug report provided by Masaaki Chida

Commit mix two thing, fix only the module problem

Fix loading arbitrary module from user side

origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/fc6080f1321fd21e86ef916195cc110b05d9effb

Bug#833732: memory leak

[Bastien ROUCARIES]

Package: src:imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org



commit d0422250c0577e6cdacfba63560065886276209b
Author: Cristy 
Date:   Thu Jun 2 13:44:20 2016 -0400

Fix small memory leak in XML file traversal

Commit mix two thing, fix only the xml problem

origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/fc6080f1321fd21e86ef916195cc110b05d9effb

Bug#811998: marked as done (gamera: FTBFS with GCC 6: misc errors)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2016 10:20:22 +
with message-id 
and subject line Bug#811998: fixed in gamera 1:3.4.2+git20160808.1725654-1
has caused the Debian Bug report #811998,
regarding gamera: FTBFS with GCC 6: misc errors
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.)


-- 
811998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gamera
Version: 3.4.2+svn1437-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> creating build/temp.linux-x86_64-2.7-pydebug/src
> x86_64-linux-gnu-gcc -pthread -g -O0 -Wall -Wstrict-prototypes 
> -fno-strict-aliasing -g -Og -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Iinclude 
> -I/usr/include/python2.7_d -c src/gameramodule.cpp -o 
> build/temp.linux-x86_64-2.7-pydebug/src/gameramodule.o -Wall
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++
> In file included from /usr/include/python2.7/Python.h:19:0,
>  from include/gameramodule.hpp:24,
>  from src/gameramodule.cpp:21:
> /usr/include/vigra/numerictraits.hxx:645:43: error: overflow in constant 
> expression [-fpermissive]
>  static const unsigned char maxConst = UCHAR_MAX;
>^
> 
> /usr/include/vigra/numerictraits.hxx:645:43: error: overflow in constant 
> expression [-fpermissive]
> /usr/include/vigra/numerictraits.hxx:645:43: error: overflow in constant 
> expression [-fpermissive]
> /usr/include/vigra/numerictraits.hxx:645:43: error: overflow in constant 
> expression [-fpermissive]
> /usr/include/vigra/numerictraits.hxx:723:48: error: overflow in constant 
> expression [-fpermissive]
>  static const short unsigned int maxConst = USHRT_MAX;
> ^
> 
> /usr/include/vigra/numerictraits.hxx:723:48: error: overflow in constant 
> expression [-fpermissive]
> /usr/include/vigra/numerictraits.hxx:723:48: error: overflow in constant 
> expression [-fpermissive]
> /usr/include/vigra/numerictraits.hxx:723:48: error: overflow in constant 
> expression [-fpermissive]
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> debian/rules:59: recipe for target 'build/build-stamp-python2.7' failed
> make[1]: *** [build/build-stamp-python2.7] Error 1

> x86_64-linux-gnu-gcc -pthread -g -O0 -Wall -Wstrict-prototypes 
> -fno-strict-aliasing -g -Og -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Iinclude 
> -I/usr/include/python2.7_d -c src/imageobject.cpp -o 
> build/temp.linux-x86_64-2.7-pydebug/src/imageobject.o -Wall
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++
> In file included from include/gamera.hpp:62:0,
>  from include/gameramodule.hpp:38,
>  from src/imageobject.cpp:22:
> include/rle_data.hpp: In instantiation of 'void 
> Gamera::RleDataDetail::RleVector::set(size_t, 
> Gamera::RleDataDetail::RleVector::value_type, typename 
> Gamera::RleDataDetail::RleVector::list_type::iterator) [with Data = 
> short unsigned int; size_t = long unsigned int; 
> Gamera::RleDataDetail::RleVector::value_type = short unsigned int; 
> typename Gamera::RleDataDetail::RleVector::list_type::iterator = 
> std::_List_iterator]':
> include/rle_data.hpp:423:2:   required from 'void 
> Gamera::RleDataDetail::RleVectorIteratorBase ListIterator>::set(const value_type&) [with V = 
> Gamera::RleDataDetail::RleVector; Iterator = 
> Gamera::RleDataDetail::RleVectorIterator >; ListIterator = 
> std::_List_iterator; 
> Gamera::RleDataDetail::RleVectorIteratorBase ListIterator>::value_type = short unsigned int]'
> include/accessor.hpp:55:7:   required from 'void 
> 

Bug#831442: mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order

[Thibaut Paumard]

Hi have open a new bug against libc-bin (ldconfig) to follow that up on
that side: 833728

Processed (with 1 error): severity of 833679 is grave, merging 833679 833681

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 833679 grave
Bug #833679 [picard] BitPaddedInt import error
Severity set to 'grave' from 'normal'
> merge 833679 833681
Bug #833679 [picard] BitPaddedInt import error
Unable to merge bugs because:
forwarded of #833681 is '' not 
'http://tickets.musicbrainz.org/browse/PICARD-833'
Failed to merge 833679: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833679
833681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833695: [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

[Chris Lamb]

> Please reassign to python-popcon.

Well, there are perhaps two bugs here, so simply reassigning won't be
sufficient:

Firstly, all-popcon-results.txt.gz contains invalid data. I agree that
the client should not be removed from testing but I could not find a
suitable pseudo-package for the popcon "web" service.

(The code that generates this file appears to be in the popularity-contest
source package, hence why I filed it here)

Where should this issue be raised? I don't care about the severity, more
that it gets fixed. How can I help? :)


Secondly, src:python-popcon assumes valid data. Perhaps. But it would
still have to raise an error if it could not parse the file so there's
not much it could reasonably do. It *could* print a nicer exception so
its easier to track down the problem, but that's purely aesthetic..


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#833695: [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

[Bill Allombert]

On Mon, Aug 08, 2016 at 01:07:18AM +0200, Chris Lamb wrote:
> Package: popularity-contest
> Version: 1.64
> Severity: serious
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Hi,
> 
> Since (at least) 07-Aug-2016 14:04, the all-popcon-results.txt.gz file
> contains an invalid line:
> 
> Package: libfyba0-dbg   0 2 0 0
> --> Package: libf erdp-ommon0 0 0 1
> Package: libg++2.8.1.3-dbg  0 0 0 1
> 
> That's (currently) line 54869. The "space" on the second line is actually
> a 0xa0 character. This results in a few issues in dependent packages,
> hence the RC severity.

Hello Chris,

Please do not inflate bug severity.

This is not a bug in the Debian package since it only provide the client side.
It would be pointless to remove it from testing due to this.

The popcon server neer promised that all-popcon-results.txt.gz was a
valid UTF8 file. Software must not assume that.

Please reassign to python-popcon.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#831113: qbittorrent: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

[bruno zanetti]

This bug is very likely upstream bug #5237 [1] which has been solved since
version 3.3.5. So packaging the current version (3.3.6) should be enough to
get rid of it. I did it myself and it built fine in a current sid chroot,
whereas 3.3.4 failed with the compiler error above.

Regards

BZ

[1] https://github.com/qbittorrent/qBittorrent/issues/5237

Bug#833714: ucto: FTBFS: libucto.so: undefined reference to `folia::UnicodeToUTF8[abi:cxx11](icu_57::UnicodeString const&)'

[Chris Lamb]

Source: ucto
Version: 0.8.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ucto fails to build from source in unstable/amd64:

  [..]

  libtool: link: ( cd ".libs" && rm -f "libucto.la" && ln -s "../libucto.la" 
"libucto.la" )
  g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2 
-DSYSCONF_PATH=\"/etc\" -I/usr/include/libxml2 -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160808092914.EeWNGCIr8D.ucto/ucto-0.8.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include  
-I/usr/include/libxml2 -fopenmp -c -o ucto.o ucto.cxx
  /bin/bash ../libtool  --tag=CXX   --mode=link g++ -DSYSCONF_PATH=\"/etc\" 
-I/usr/include/libxml2 -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160808092914.EeWNGCIr8D.ucto/ucto-0.8.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include  
-I/usr/include/libxml2 -fopenmp  -Wl,-z,relro -o ucto ucto.o libucto.la -lfolia 
-L/usr/lib/x86_64-linux-gnu  -licui18n -licuuc -licudata   -licuio   -lxml2 
-lticcutils
  libtool: link: g++ -DSYSCONF_PATH=\"/etc\" -I/usr/include/libxml2 -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160808092914.EeWNGCIr8D.ucto/ucto-0.8.0=.
 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include 
-I/usr/include/libxml2 -fopenmp -Wl,-z -Wl,relro -o .libs/ucto ucto.o  
./.libs/libucto.so -lfolia -L/usr/lib/x86_64-linux-gnu -licui18n -licuuc 
-licudata -licuio -lxml2 -lticcutils -fopenmp
  /usr/bin/ld: warning: libicui18n.so.55, needed by 
/usr/lib/x86_64-linux-gnu/libfolia.so, may conflict with libicui18n.so.57
  /usr/bin/ld: warning: libicuuc.so.55, needed by 
/usr/lib/x86_64-linux-gnu/libfolia.so, may conflict with libicuuc.so.57
  /usr/bin/ld: warning: libicudata.so.55, needed by 
/usr/lib/x86_64-linux-gnu/libfolia.so, may conflict with libicudata.so.57
  /usr/bin/ld: warning: libicuio.so.55, needed by 
/usr/lib/x86_64-linux-gnu/libfolia.so, may conflict with libicuio.so.57
  /usr/lib/x86_64-linux-gnu/libfolia.so: undefined reference to 
`TiCC::split_at(std::__cxx11::basic_string const&, std::vector, 
std::allocator > >&, std::__cxx11::basic_string const&)'
  ./.libs/libucto.so: undefined reference to 
`folia::UnicodeToUTF8[abi:cxx11](icu_57::UnicodeString const&)'
  /usr/lib/x86_64-linux-gnu/libfolia.so: undefined reference to 
`TiCC::split_at_first_of(std::__cxx11::basic_string const&, 
std::vector, std::allocator > >&, 
std::__cxx11::basic_string 
const&)'
  collect2: error: ld returned 1 exit status
  Makefile:665: recipe for target 'ucto' failed
  make[3]: *** [ucto] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160808092914.EeWNGCIr8D.ucto/ucto-0.8.0/src'
  Makefile:481: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160808092914.EeWNGCIr8D.ucto/ucto-0.8.0'
  Makefile:388: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160808092914.EeWNGCIr8D.ucto/ucto-0.8.0'
  /usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
  make: *** [debian/stamp-makefile-build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ucto.0.8.0-2.unstable.amd64.log.txt.gz
Description: Binary data

Processed: Re: Bug#831442: mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Severity set to 'serious' from 'important'

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

Bug#806661: marked as done (tor: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2016 08:44:31 +
with message-id <20160808084431.ga8...@sarek.noreply.org>
and subject line Re: Bug#806661: tagging 806661
has caused the Debian Bug report #806661,
regarding tor: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
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.)


-- 
806661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tor
Version: 0.2.7.5-1
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh \
build-indep \
--with quilt \
--with autoreconf \
--with systemd \
--builddirectory=build \
--parallel
   dh_testdir -i -O--builddirectory=build -O--parallel
   dh_quilt_patch -i -O--builddirectory=build -O--parallel
Applying patch 20-upstream-syslog-identity
patching file changes/bug17194

[... snipped ...]

rm -f micro-revision.tmp; \
if test -d "../.git" && \
test -x "`which git 2>&1;true`"; then \
HASH="`cd ".." && git rev-parse --short=16 HEAD`"; \
echo \"$HASH\" > micro-revision.tmp; \
fi; \
if test ! -f micro-revision.tmp; then \
if test ! -f micro-revision.i; then \
echo '""' > micro-revision.i; \
fi; \
elif test ! -f micro-revision.i || \
test x"`cat micro-revision.tmp`" != x"`cat micro-revision.i`"; 
then \
mv micro-revision.tmp micro-revision.i; \
fi; \
rm -f micro-revision.tmp; \
true
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
  /usr/bin/install -c src/or/tor src/tools/tor-resolve src/tools/tor-gencert 
'/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c ../contrib/client-tools/torify 
'/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/etc/tor'
 /usr/bin/install -c -m 644 src/config/torrc.sample 
'/<>/debian/tmp/etc/tor'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/doc/tor'
 /usr/bin/install -c -m 644 doc/tor.html doc/tor-gencert.html 
doc/tor-resolve.html doc/torify.html 
'/<>/debian/tmp/usr/share/doc/tor'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 doc/tor.1 doc/tor-gencert.1 doc/tor-resolve.1 
doc/torify.1 '/<>/debian/tmp/usr/share/man/man1'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/tor'
 /usr/bin/install -c -m 644 ../src/config/geoip ../src/config/geoip6 
'/<>/debian/tmp/usr/share/tor'
make[2]: Leaving directory '/<>/build'
make[1]: Leaving directory '/<>/build'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install --fail-missing
mv debian/tor/etc/tor/torrc.sample debian/tor/etc/tor/torrc
mv: cannot stat 'debian/tor/etc/tor/torrc.sample': No such file or directory
debian/rules:63: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:23: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.2.7.6-2

On Wed, 13 Jul 2016, Peter Palfrader wrote:

> On Wed, 13 Jul 2016, Santiago Vila wrote:
> > I'm going to wait a week before raising severities, but since this bug
> > is in pending state, I'd appreciate if you could make an upload
> > before that.
> 
> It's fixed in 0.2.7.6-2, which hasn't been uploaded to unstable but
> which is included in 0.2.8.5-rc-1 from experimental.
> 
> I expect the version from experimental will make it to unstable in the
> next few weeks.

The 0.2.8.x tree is now in unstable.

-- 
|  .''`.   ** Debian **
  Peter Palfrader  

Bug#831918:

[Gerrit Pape]

On Thu, Aug 04, 2016 at 03:17:47PM +0200, Santiago Vila wrote:
> owner 831918 sanv...@debian.org
> thanks
> 
> I plan to make a QA upload to fix this.

Thank you!

Processed: Severity for horizon back to serious, as django 1.10 is in Unstable

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 832338 serious
Bug #832338 [openstack-dashboard] FTBFS & runtime crash with Django 1.10
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
832338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 833515

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 833515 alter-sequence-alignment
Bug #833515 [ant-contrib] alter-sequence-alignment: FTBFS: failed to create 
task or type foreach
Added indication that 833515 affects alter-sequence-alignment
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 833515

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 833515 scala
Bug #833515 [ant-contrib] alter-sequence-alignment: FTBFS: failed to create 
task or type foreach
Added indication that 833515 affects scala
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#833655: metar: NOAA changed server weather.noaa.gov to tgftp.nws.noaa.gov (metar.h in source)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 833655 grave
Bug #833655 [metar] metar: NOAA changed server weather.noaa.gov to 
tgftp.nws.noaa.gov (metar.h in source)
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833515: alter-sequence-alignment: FTBFS: failed to create task or type foreach

[Emmanuel Bourg]

Le 7/08/2016 à 11:56, Markus Koschany a écrit :

> Emmanuel will probably chime in here. I suggest to wait until then.

Perfect analysis, thank you Markus. Scala is also affected by this
issue, the path to ant-contrib is wrong in the build but the symlink to
ant-contrib.jar in /usr/share/ant/lib used to hide the mistake.

I'm going to fix ant-contrib, sorry for the trouble.

Emmanuel Bourg

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Pete Batard]

Thanks Felipe.

I'm afraid it's still not completing successfully though:

../src/test/test-execute.c: In function ‘test_exec_systemcallfilter’:
../src/test/test-execute.c:120:14: error: implicit declaration of 
function ‘is_seccomp_enabled’ [-Werror=implicit-function-declaration]

 if (!is_seccomp_enabled())
  ^
../src/test/test-execute.c:120:9: warning: nested extern declaration of 
‘is_seccomp_enabled’ [-Wnested-externs]

 if (!is_seccomp_enabled())
 ^
../src/test/test-execute.c: In function 
‘test_exec_systemcall_system_mode_with_user’:

../src/test/test-execute.c:141:9: error: expected expression before ‘if’
 if (getpwnam("nobody"))
 ^
../src/test/test-execute.c:141:9: warning: ‘return’ with a value, in 
function returning void

cc1: some warnings being treated as errors
Makefile:20308: recipe for target 'src/test/test_execute-test-execute.o' 
failed

make[4]: *** [src/test/test_execute-test-execute.o] Error 1
Makefile:21743: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
Makefile:9783: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/root/systemd-231/build-deb'
dh_auto_build: make -j1 returned exit code 2
debian/rules:194: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/root/systemd-231'
debian/rules:376: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Regards,

/Pete

Bug#833335: marked as done (namazu2-index-tools and namazu2: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2016 07:12:17 +
with message-id 
and subject line Bug#85: fixed in namazu2 2.0.21-16
has caused the Debian Bug report #85,
regarding namazu2-index-tools and namazu2: error when trying to install together
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.)


-- 
85: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=85
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: namazu2,namazu2-index-tools
Version: namazu2/2.0.21-15
Version: namazu2-index-tools/2.0.21-15
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-08-03
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package libfile-mmagic-perl.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../libfile-mmagic-perl_1.30-1_all.deb ...
Unpacking libfile-mmagic-perl (1.30-1) ...
Selecting previously unselected package libnmz7.
Preparing to unpack .../libnmz7_2.0.21-15_amd64.deb ...
Unpacking libnmz7 (2.0.21-15) ...
Selecting previously unselected package namazu2-common.
Preparing to unpack .../namazu2-common_2.0.21-15_all.deb ...
Unpacking namazu2-common (2.0.21-15) ...
Selecting previously unselected package namazu2.
Preparing to unpack .../namazu2_2.0.21-15_amd64.deb ...
Unpacking namazu2 (2.0.21-15) ...
Selecting previously unselected package namazu2-index-tools.
Preparing to unpack .../namazu2-index-tools_2.0.21-15_all.deb ...
Unpacking namazu2-index-tools (2.0.21-15) ...
dpkg: error processing archive 
/var/cache/apt/archives/namazu2-index-tools_2.0.21-15_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/mknmz.1.gz', which is also in package 
namazu2 2.0.21-15
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-4) ...
Errors were encountered while processing:
 /var/cache/apt/archives/namazu2-index-tools_2.0.21-15_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/man/man1/mknmz.1.gz

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: namazu2
Source-Version: 2.0.21-16

We believe that the bug you reported is fixed in the latest version of
namazu2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
NOKUBI Takatsugu  (supplier of updated namazu2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 08 Aug 2016 06:55:46 +
Source: namazu2
Binary: namazu2 namazu2-index-tools namazu2-common libnmz7 libnmz7-dev
Architecture: source i386 all
Version: 2.0.21-16
Distribution: unstable
Urgency: medium
Maintainer: NOKUBI Takatsugu 

Bug#831129: kcollectd: FTBFS with GCC 6: graph.cc:567:37: error: 'isnan' was not declared in this scope

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * kcollectd/{graph,misc}.cc: Prefix isnan with std namespace to fix FTBFS
with GCC 6.

Thanks for considering the patch.

Logan Rosen
diff -u kcollectd-0.9/debian/control kcollectd-0.9/debian/control
--- kcollectd-0.9/debian/control
+++ kcollectd-0.9/debian/control
@@ -1,8 +1,7 @@
 Source: kcollectd
 Section: utils
 Priority: extra
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: M G Berberich 
+Maintainer: M G Berberich 
 Build-Depends: debhelper (>= 7), cmake, kdelibs5-dev, shared-mime-info, libboost-filesystem-dev, librrd-dev
 Standards-Version: 3.8.4
 Homepage: http://www.forwiss.uni-passau.de/~berberic/Linux/kcollectd.html
only in patch2:
unchanged:
--- kcollectd-0.9.orig/kcollectd/graph.cc
+++ kcollectd-0.9/kcollectd/graph.cc
@@ -564,9 +564,9 @@
   paint.setPen(Qt::NoPen);
   paint.setBrush(QBrush(color_minmax[color_nr++ % 8]));
   for(int i=0; i min_data[i]) min = min_data[i];
   if (max < min_data[i]) max = min_data[i];

Bug#832845: marked as done (libbio-das-lite-perl: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2016 06:34:31 +
with message-id 
and subject line Bug#832845: fixed in libbio-das-lite-perl 2.11-5
has caused the Debian Bug report #832845,
regarding libbio-das-lite-perl: FTBFS: Tests failures
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.)


-- 
832845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbio-das-lite-perl
Version: 2.11-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> 1..2
> ok 1 - Whole-response-mode gave correct number of sources returned
> ok 2 - Got maintainers email
> ok
> 
> Test Summary Report
> ---
> t/60-features_chunked.t   (Wstat: 65280 Tests: 0 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 1 tests but ran 0.
> Files=16, Tests=49,  0 wallclock secs ( 0.03 usr  0.02 sys +  0.69 cusr  0.04 
> csys =  0.78 CPU)
> Result: FAIL
> Failed 1/16 test programs. 0/49 subtests failed.
> dh_auto_test: perl Build test --verbose 1 --test_files=t/00-critic.t 
> t/00-pod.t t/00-podcoverage.t t/06-singledsn-singleseg.t 
> t/20-authentication.t t/21-proxy.t t/40-dna.t t/45-sequence.t 
> t/50-entry_points.t t/60-features.t t/60-features_chunked.t 
> t/60-features_empty.t t/61-features_group.t t/70-alignment.t t/80-structure.t 
> t/90-sources.t returned exit code 255
> make[1]: *** [override_dh_auto_test] Error 255
> debian/rules:9: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/28/libbio-das-lite-perl_2.11-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libbio-das-lite-perl
Source-Version: 2.11-5

We believe that the bug you reported is fixed in the latest version of
libbio-das-lite-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbio-das-lite-perl 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 08 Aug 2016 08:27:05 +0200
Source: libbio-das-lite-perl
Binary: libbio-das-lite-perl
Architecture: source all
Version: 2.11-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libbio-das-lite-perl - implementation of the BioDas protocol
Closes: 832845
Changes:
 libbio-das-lite-perl (2.11-5) unstable; urgency=medium
 .
   * Fix test suite (thanks for the patch to Alex Muntada )
 Closes: #832845
   * cme fix dpkg-control
Checksums-Sha1:
 06181ab1dd7a185232f539f7de31becb44bd9dcc 2268 libbio-das-lite-perl_2.11-5.dsc
 0a4930e5b787316aaafe43571cef7d9df021fb1b 3360 
libbio-das-lite-perl_2.11-5.debian.tar.xz
 8cef165d4ace494e369b99d05ee1e1576e00cb84 25850 
libbio-das-lite-perl_2.11-5_all.deb
Checksums-Sha256:
 4385daef6f325dbb38df0ad228ae31381124ab2bb3ed4ba76ac2e9d4f15bf2f5 2268 
libbio-das-lite-perl_2.11-5.dsc
 a7d3f1e0d535a11a915f6047e56856df69db58a332597154e390407f6985f5d1 3360 
libbio-das-lite-perl_2.11-5.debian.tar.xz
 34e5dcd7115a70e53a51d1cce5abf21bce8bc06b967666a5a22f3cb1cdbab07c 25850 
libbio-das-lite-perl_2.11-5_all.deb
Files:
 a917425946245c0dfc56c1af336777ad 2268 perl optional 
libbio-das-lite-perl_2.11-5.dsc
 0576e9a65defb86772aa1d8f9a5ab7a1 3360 perl optional 
libbio-das-lite-perl_2.11-5.debian.tar.xz
 9478655502408a70c29b2f446f15aa84 25850 perl optional