Bug#831406: yorick FTBFS - linked to mpich

[Nicholas Breen]

block 831406 by 831442
thanks


The same bug is hitting one of my packages, seems to be an issue with mpich.
Filed as https://bugs.debian.org/831442 .



-- 
Nicholas Breen
nbr...@debian.org

Bug#817038: transifex-client: Use python-six instead of the embedded version of python-urllib3

[Petter Reinholdtsen]

[Christos Trochalakis 2016-03-07]
> Transifex imports six from urlilib3 embedded version.
> Since python-urllib3 (1.13.1-1) debian dropped the
> embedded six module which, although it makes sense, broke
> transifex-client.
> 
> Please consider applying the attached patch that switches
> imports to python-six.

[Sebastian Ramacher 2016-04-18]
> Raising the severity as this makes transifex-client unusable:

Thank you.  I was bit by the same issue just now when I needed to use the
tx client in unsable.

Is there something wrong with the proposed patch, or is there some other
reason the RC issue have not been adressed since March?

-- 
Happy hacking
Petter Reinholdtsen

Bug#823675: marked as done (cloud-init: FTBFS: /usr/bin/python3: No module named pyflakes)

[Debian Bug Tracking System]

Your message dated Sat, 16 Jul 2016 13:52:19 +0900
with message-id <20160716045219.ga32...@falafel.plessy.net>
and subject line Re: Bug#823675: cloud-init: FTBFS: /usr/bin/python3: No module 
named pyflakes
has caused the Debian Bug report #823675,
regarding cloud-init: FTBFS: /usr/bin/python3: No module named pyflakes
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.)


-- 
823675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cloud-init
Version: 0.7.7~bzr1215-1
Severity: serious
Justification: fails to build from source

Hi,

cloud-init FTBFS in sid:

https://buildd.debian.org/status/fetch.php?pkg=cloud-init=all=0.7.7~bzr1215-1=1462532671

   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
make PYVER=3 check
make[2]: Entering directory '/«PKGBUILDDIR»'
Running:  pep8 cloudinit/ bin/ tests/ tools/
Running:  python3 -m pyflakes cloudinit/ bin/ tests/ tools/
/usr/bin/python3: No module named pyflakes
Makefile:42: recipe for target 'pyflakes3' failed
make[2]: *** [pyflakes3] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:9: recipe for target 'override_dh_auto_test' failed

Looks like a new Build-Depends is needed.


Andreas
--- End Message ---
--- Begin Message ---
Version: 0.7.7~bzr1215-2

Fixed by Bastian Blank in version 0.7.7~bzr1215-2.

-- 
Charles--- End Message ---

Bug#830459: log4cpp: FTBFS: configure.in:44: error: required file 'config/compile' not found

[A . Maitland Bottoms]

It seemed to me that a bit of modernization in log4cpp packaging would
help fix this. I noticed upstream states that the 1.1.1 is the newest
stable release, and refactored the packaging around dh and
dh-autoreconf.

(I have not had time yet to build and test my packages with this
newer log4cpp, and I do hope that I can run abi-compliance-checker
soon and not be too surprised.)

Hope this helps,
-Maitland


log4cpp_1.1.1-1.debian.tar.xz
Description: log4cpp_1.1.1-1.debian.tar.xz

Bug#811647: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Sat, 16 Jul 2016 04:25:08 +
with message-id 
and subject line Bug#811647: fixed in scorched3d 44+dfsg-1
has caused the Debian Bug report #811647,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scorched3d
Version: 43.3.d+dfsg-1.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"scorched3d\" -DVERSION=\"43\" -DHAVE_OGG=1 -DHAVE_VSNPRINTF=1 
> -DHAVE_SNPRINTF=1 -DHAVE_VASPRINTF=1 -DHAVE_ASPRINTF=1 -DHAVE_ICONV=1 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ICONV_H=1 -I.  
> -I../../common/porting -I../../common -I../../client -I../../server  
> -I/usr/include -I/usr/include -I/usr/include/AL -I/usr/include/AL 
> -I/usr/include/freetype2 -I/usr/include -I/usr/include -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/X11R6/include -I/usr/X11R6 -I/usr/local/include  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -DS3D_DOCDIR=\"/usr/share/doc/scorched3d\" 
> -DS3D_DATADIR=\"/usr/share/games/scorched3d\" -DS
> 3D_BINDIR=\"/usr/games\" -MT WeaponDelay.o -MD -MP -MF .deps/WeaponDelay.Tpo 
> -c -o WeaponDelay.o `test -f '../../common/weapons/WeaponDelay.cpp' || echo 
> './'`../../common/weapons/WeaponDelay.cpp
> ../../common/weapons/AccessoryStore.cpp: In member function 'AccessoryPart* 
> AccessoryStore::createAccessoryPart(AccessoryCreateContext&, Accessory*, 
> XMLNode*)':
> ../../common/weapons/AccessoryStore.cpp:158:64: error: cannot convert 'bool' 
> to 'AccessoryPart*' in return
>   if (!currentNode->getNamedParameter("type", typeNode)) return false;
> ^
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: scorched3d
Source-Version: 44+dfsg-1

We believe that the bug you reported is fixed in the latest version of
scorched3d, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated scorched3d 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: Sat, 16 Jul 2016 04:41:26 +0200
Source: scorched3d
Binary: scorched3d scorched3d-data
Architecture: source
Version: 44+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 scorched3d - 3D artillery game similar to Scorched Earth
 scorched3d-data - data files for Scorched3D game
Closes: 782624 811647
Changes:
 scorched3d (44+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Phil Morrell ]
   * use https and update vcs urls
   * remove .menu file now .desktop files expected
   * simplify watch file using version 4
   * add myself to uploaders in preparation
   * make debian/copyright machine-readable (DEP-5)
   * update dependency on {ttf,fonts}-dejavu
   * remove fonts-dejavu embedded copy from orig source
   * remove scorched3d-dbg in favour of automatic dgbsym
   * use Files-Excluded for uscan repacking
   * replace custom 

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

[Aliaksey Kandratsenka]

Thanks for reporting the issue. I just tried to reproduce the problem
on my sid laptop in cleanly deboostrap-ed sid chroot and was unable to
hit this issue. This maybe indicates that kernel matters or maybe
there is something else in the host that is relevant. Can you please
share more details on how I can reproduce this? Also let me note once
again that 2.2.1 is much outdated and latest upstream is 2.4, although
I don't think we fixed anything related to death tests recently.


On Thu, Jul 14, 2016 at 3:06 AM, Lucas Nussbaum  wrote:
> Source: google-perftools
> Version: 2.2.1-0.3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160714 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):
>> PASS: malloc_extension_debug_test
>> PASS
>> PASS: memalign_debug_unittest
>> PASS
>> PASS: realloc_debug_unittest
>> make[2]: *** wait: No child processes.  Stop.
>> make[2]: *** Waiting for unfinished jobs
>> make[2]: *** wait: No child processes.  Stop.
>> make[1]: *** wait: No child processes.  Stop.
>> make[1]: *** Waiting for unfinished jobs
>> make[1]: *** wait: No child processes.  Stop.
>> make: *** wait: No child processes.  Stop.
>> make: *** Waiting for unfinished jobs
>> make: *** wait: No child processes.  Stop.
>> E: Caught signal ‘Terminated’: terminating immediately
>> Running death test 0Build killed with signal TERM after 150 minutes of 
>> inactivity
>
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/07/14/google-perftools_2.2.1-0.3_unstable_gcc5.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.
>

Bug#830329: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Lisandro Damián Nicanor Pérez Meyer]

On viernes, 15 de julio de 2016 10:36:27 P. M. ART Lisandro Damián Nicanor 
Pérez Meyer wrote:
[snip] 
> I really *love* them (I haven't used cme before, someday I'll need to
> investigate that one). Sadly I think applying them without the maintainer's
> approval it's a bad idea.

It is worth to note here that the last upload was marked as "Team upload" 
because it was prepared by Gudjon and I while we where working towards pushin 
qwt with qt5 support to unstable and I just coordinated with Gudjon to do the 
upload.

I'm really not too interested in maintaining qwt myself, I just happen to have 
another package that requires it too.


-- 
$ make war
make: *** No rule to make target `war'.  Stop.  Try `love' instead
  David Gravereaux

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#830329: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Lisandro Damián Nicanor Pérez Meyer]

Hi Bas!


On sábado, 16 de julio de 2016 2:57:42 A. M. ART Sebastiaan Couwenberg wrote:
> Hi Lisandro,
[snip]
> On 07/16/2016 02:50 AM, Sebastiaan Couwenberg wrote:
> > As the uploader of the last couple qwt revisions, can you upload a new
> > revision to fix this issue?

I was planning to do so in case Gudjon didn't reply, so I guess yes :)
 
> > I'd like to prevent the removal of the qwt reverse dependencies, so I've
> > updated the package to resolve this RC bug and fix a bunch of unrelated
> > issues along the way.
>
> > From the attached patches only the first three are needed to fix this RC
> > bug, specifically the third.

Actually the third patch is really not desired when maintaining a lib that 
tends to break api/abi like qwt did in the last version, so I won't apply it.

I've looked at the symbols changes and I'll apply the first two patches and 
add some optional tags to prevent further FTBFSs. The ones you marked in amd64 
will surely happen on other archs. But they are destructors added by the 
compiler, so they are safe to be marked as optional.

> > The other patches are general improvements
> > to the packaging, please consider applying them as well.

I really *love* them (I haven't used cme before, someday I'll need to 
investigate that one). Sadly I think applying them without the maintainer's 
approval it's a bad idea.

Gudjon: please consider patches starting from 0004-...

Kinds regards, Lisandro.

-- 
Passwords are like underwear. You shouldn’t leave them out where people can
see them. You should change them regularly. And you shouldn’t loan them out
to strangers.
  Anonymous

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#831124: guitarix: FTBFS with GCC 6: ../libgxwmm/gxwmm/gainline.h:25:110: error: call of overloaded 'abs(double)' is ambiguous

[Hermann Meyer]

Hi

This is already fixed in upstream on 2016-05-16
here is the fix commit:
https://sourceforge.net/p/guitarix/git/ci/975b3b5cbd6b7b8a74f4da9eb687c9af8538178c/

regards
hermann

Bug#830329: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Sebastiaan Couwenberg]

Hi Lisandro,

The patches now actually attached.

On 07/16/2016 02:50 AM, Sebastiaan Couwenberg wrote:
> As the uploader of the last couple qwt revisions, can you upload a new
> revision to fix this issue?
> 
> I'd like to prevent the removal of the qwt reverse dependencies, so I've
> updated the package to resolve this RC bug and fix a bunch of unrelated
> issues along the way.
> 
> From the attached patches only the first three are needed to fix this RC
> bug, specifically the third. The other patches are general improvements
> to the packaging, please consider applying them as well.

Kind Regards,

Bas

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


0001-Update-symbols-for-sparc64-x32.patch
Description: inode/symlink


0002-Update-symbols-for-amd64.patch
Description: inode/symlink


0003-Override-dh_makeshlibs-to-not-fail-on-symbols-change.patch
Description: inode/symlink


0004-Enable-bindnow-hardening-buildflags.patch
Description: inode/symlink


0005-Update-Vcs-Browser-URL-to-use-HTTPS.patch
Description: inode/symlink


0006-Update-copyright-file-using-copyright-format-1.0.patch
Description: inode/symlink


0007-Bump-debhelper-compatibility-to-9.patch
Description: inode/symlink


0008-Override-dh_install-to-use-list-missing-instead-of-a.patch
Description: inode/symlink


0009-Override-dh_installman-to-remove-_tmp_-files.patch
Description: inode/symlink


0010-Discard-manpages-installed-by-buildsystem-use-dh_ins.patch
Description: inode/symlink


0011-Install-pkg-config-files-in-their-respective-dev-pac.patch
Description: inode/symlink


0012-Restructure-control-file-with-cme.patch
Description: inode/symlink


0013-Drop-unused-substitution-variables.patch
Description: inode/symlink


0014-Update-03_fix_spelling.patch-to-fix-additional-spell.patch
Description: inode/symlink


0015-Bump-Standards-Version-to-3.9.8-changes-copyright-fo.patch
Description: inode/symlink

Processed: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #830329 [src:qwt] qwt: FTBFS: dh_makeshlibs: failing due to earlier errors
Added tag(s) patch.

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

Bug#830329: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Sebastiaan Couwenberg]

Control: tags -1 patch

Hi Lisandro,

As the uploader of the last couple qwt revisions, can you upload a new
revision to fix this issue?

I'd like to prevent the removal of the qwt reverse dependencies, so I've
updated the package to resolve this RC bug and fix a bunch of unrelated
issues along the way.

>From the attached patches only the first three are needed to fix this RC
bug, specifically the third. The other patches are general improvements
to the packaging, please consider applying them as well.

Kind Regards,

Bas

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

Bug#819856: dnsmasq: diff for NMU version 2.76-1.2

[zeha]

Control: tags 819856 + patch
Control: tags 819856 + pending

Dear maintainer,

I've prepared an NMU for dnsmasq (versioned as 2.76-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Best,
Chris


diff -u dnsmasq-2.76/debian/changelog dnsmasq-2.76/debian/changelog
--- dnsmasq-2.76/debian/changelog
+++ dnsmasq-2.76/debian/changelog
@@ -1,3 +1,11 @@
+dnsmasq (2.76-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * dnsmasq: Install marker file to determine package installed state,
+for the benefit of the init script. (Closes: #819856)
+
+ -- Christian Hofstaedtler   Sat, 16 Jul 2016 00:17:57 +
+
 dnsmasq (2.76-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u dnsmasq-2.76/debian/init dnsmasq-2.76/debian/init
--- dnsmasq-2.76/debian/init
+++ dnsmasq-2.76/debian/init
@@ -33,7 +33,7 @@
 # The following test ensures the dnsmasq service is not started, when the
 # package 'dnsmasq' is removed but not purged, even if the dnsmasq-base 
 # package is still in place.
-test -d /usr/share/doc/dnsmasq || exit 0
+test -e /usr/share/dnsmasq/installed-marker || exit 0
  
 test -x $DAEMON || exit 0
 
diff -u dnsmasq-2.76/debian/rules dnsmasq-2.76/debian/rules
--- dnsmasq-2.76/debian/rules
+++ dnsmasq-2.76/debian/rules
@@ -105,6 +105,7 @@
-d debian/daemon/etc/dnsmasq.d \
-d debian/daemon/etc/resolvconf/update.d \
-d debian/daemon/usr/lib/resolvconf/dpkg-event.d \
+   -d debian/daemon/usr/share/dnsmasq \
-d debian/daemon/etc/default \
-d debian/daemon/lib/systemd/system \
 -d debian/daemon/etc/insserv.conf.d
@@ -113,6 +114,7 @@
install -m 755 debian/init debian/daemon/etc/init.d/dnsmasq
install -m 755 debian/resolvconf 
debian/daemon/etc/resolvconf/update.d/dnsmasq
install -m 755 debian/resolvconf-package 
debian/daemon/usr/lib/resolvconf/dpkg-event.d/dnsmasq
+   install -m 644 debian/installed-marker debian/daemon/usr/share/dnsmasq
install -m 644 debian/default debian/daemon/etc/default/dnsmasq
install -m 644 dnsmasq.conf.example debian/daemon/etc/dnsmasq.conf
install -m 644 debian/readme.dnsmasq.d 
debian/daemon/etc/dnsmasq.d/README
only in patch2:
unchanged:
--- dnsmasq-2.76.orig/debian/installed-marker
+++ dnsmasq-2.76/debian/installed-marker
@@ -0,0 +1,2 @@
+# This file indicates dnsmasq (and not just dnsmasq-base) is installed.
+# It is an implementation detail of the dnsmasq init script.

Processed: dnsmasq: diff for NMU version 2.76-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 819856 + patch
Bug #819856 [dnsmasq] dnsmasq: removing /etc/dnsmasq.d/README prevents dnsmasw 
from starting
Added tag(s) patch.
> tags 819856 + pending
Bug #819856 [dnsmasq] dnsmasq: removing /etc/dnsmasq.d/README prevents dnsmasw 
from starting
Added tag(s) pending.

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

Bug#830995: marked as done (python-apt: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 16 Jul 2016 00:20:47 +
with message-id 
and subject line Bug#830995: fixed in python-apt 1.1.0~beta4
has caused the Debian Bug report #830995,
regarding python-apt: FTBFS: Test 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.)


-- 
830995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-apt
Version: 1.1.0~beta3
Severity: serious

>From my pbuilder build log:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-apt-1.1.0~beta3'
set -e; for python in python2.7 python3.5 ; do \
$python tests/test_all.py -q || [ "linux" = "hurd" ]; \
done;
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
[tests] Running on 2.7.12 (default, Jun 30 2016, 00:12:23) [GCC 6.1.1 20160620]
Using library_dir:
'/build/python-apt-1.1.0~beta3/build/lib.linux-x86_64-2.7'WARNING:
Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
==
ERROR: test_survive_reqreinst (test_lp659438.RegressionTestCase)
Test that we survive a package in require reinstallation state
--
Traceback (most recent call last):
  File "/build/python-apt-1.1.0~beta3/tests/test_lp659438.py", line 60, in setUp
self.cache.update(sources_list=sources_list_path)
  File "/build/python-apt-1.1.0~beta3/build/lib.linux-x86_64-2.7/apt/cache.py",
line 464, in update
raise FetchFailedException(e)
FetchFailedException: E:The repository
'copy:/build/python-apt-1.1.0~beta3/tests/data/test-repo  Release'
does not have a Release file.

==
ERROR: test_apt_cache (test_apt_cache.TestAptCache)
--
Traceback (most recent call last):
  File "/build/python-apt-1.1.0~beta3/tests/test_apt_cache.py", line
32, in wrapper
f(*args, **kwargs)
  File "/build/python-apt-1.1.0~beta3/tests/test_apt_cache.py", line
68, in test_apt_cache
cache = apt.Cache()
  File "/build/python-apt-1.1.0~beta3/build/lib.linux-x86_64-2.7/apt/cache.py",
line 113, in __init__
self.open(progress)
  File "/build/python-apt-1.1.0~beta3/build/lib.linux-x86_64-2.7/apt/cache.py",
line 165, in open
self._depcache = apt_pkg.DepCache(self._cache)
Error: W:Unable to read /tmp/tmp2qVmxI/etc/apt/preferences.d/ -
DirectoryExists (2: No such file or directory), E:The package abrowser
needs to be reinstalled, but I can't find an archive for it.

==
ERROR: test_apt_update (test_apt_cache.TestAptCache)
--
Traceback (most recent call last):
  File "/build/python-apt-1.1.0~beta3/tests/test_apt_cache.py", line
32, in wrapper
f(*args, **kwargs)
  File "/build/python-apt-1.1.0~beta3/tests/test_apt_cache.py", line
209, in test_apt_update
cache = apt.Cache()
  File "/build/python-apt-1.1.0~beta3/build/lib.linux-x86_64-2.7/apt/cache.py",
line 113, in __init__
self.open(progress)
  File "/build/python-apt-1.1.0~beta3/build/lib.linux-x86_64-2.7/apt/cache.py",
line 165, in open
self._depcache = apt_pkg.DepCache(self._cache)
Error: W:Unable to read /tmp/tmp2qVmxI/etc/apt/preferences.d/ -
DirectoryExists (2: No such file or directory), E:The package abrowser
needs to be reinstalled, but I can't find an archive for it.

==
ERROR: test_cache_close_download_fails (test_apt_cache.TestAptCache)
--
Traceback (most recent call last):
  File "/build/python-apt-1.1.0~beta3/tests/test_apt_cache.py", line
32, in wrapper
f(*args, 

Bug#830729: [pkg-go] Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

[Tianon Gravi]

On 10 July 2016 at 13:30, Chris Lamb  wrote:
> go install -v github.com/mitchellh/go-homedir
>   github.com/mitchellh/go-homedir
>  debian/rules override_dh_auto_test
>   make[1]: Entering directory 
> '/home/lamby/temp/cdt.20160710222637.V3OyQr9oAG.golang-github-mitchellh-go-homedir/golang-github-mitchellh-go-homedir-0.0~git20150831.0.df55a15'
>   # explicitly unset HOME to force tests to shell out
>   HOME= dh_auto_test
> go test -v github.com/mitchellh/go-homedir
>   === RUN   TestDir
>   --- FAIL: TestDir (0.00s)
> homedir_test.go:44: "/home/lamby" != "~"
>   === RUN   TestExpand
>   --- FAIL: TestExpand (0.00s)
> homedir_test.go:97: Input: "~/foo"
>
> Output: "~/foo"
>   FAIL
>   exit status 1
>   FAIL  github.com/mitchellh/go-homedir 0.005s
>   dh_auto_test: go test -v github.com/mitchellh/go-homedir returned exit code 
> 1
>   debian/rules:4: recipe for target 'override_dh_auto_test' failed
>   make[1]: *** [override_dh_auto_test] Error 1
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160710222637.V3OyQr9oAG.golang-github-mitchellh-go-homedir/golang-github-mitchellh-go-homedir-0.0~git20150831.0.df55a15'

I can't seem to reproduce this failure. :(


   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
# explicitly unset HOME to force tests to shell out
HOME= dh_auto_test
go test -v -p 1 github.com/mitchellh/go-homedir
=== RUN   TestDir
--- PASS: TestDir (0.00s)
=== RUN   TestExpand
--- PASS: TestExpand (0.00s)
PASS
ok   github.com/mitchellh/go-homedir 0.010s
make[1]: Leaving directory '/<>'
 fakeroot debian/rules binary
dh binary --buildsystem=golang --with=golang
   dh_testroot -O--buildsystem=golang
   dh_prep -O--buildsystem=golang
   dh_auto_install -O--buildsystem=golang


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#811670: FTBFS with GCC 6: cannot convert x to y

[Andreas Steigmiller]

Hi Jonas,

Many thanks for maintaining the packaging of Konclude for Debian and for 
reporting this problem. I fixed the compilation errors and zipped a new source 
code package of version 0.6.2 that can be downloaded with the following link 
(it is also available on Konclude's webpage):

http://www.derivo.de/fileadmin/externe_websites/ext.derivo/KoncludeReleases/v0.6.2-544/Konclude-v0.6.2-544-SourceCode-GCC6Fixes.zip

Of course, we will also include the fixes in the next release.

Best,

Andreas

Am 15.07.2016 um 12:43 schrieb Jonas Smedegaard:
> Hi Konclude Developer Team,
>
> I maintail the packaging of Konclude for Debian.
>
> My fellow developer, Martin, have discovered that Konclude fails to 
> compile succesfully with the most recent GNU compiler, GCC 6.
>
> Any help resolving this is quite appreciated.
>
> Quoting Martin Michlmayr (2016-01-20 01:48:28)
>> 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.
>>
>>> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
>> ...
>>> g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
>>> -fstack-protector-strong -Wformat -Werror=format-security -Wall -w 
>>> -D_REENTRANT -DQT_XML_LIB -DQT_NETWORK_LIB 
>>> -DKONCLUDE_FORCE_ALL_DEBUG_DEACTIVATED -DQT_NO_DEBUG -DQT_GUI_LIB 
>>> -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
>>> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
>>> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 
>>> -I./generatedfiles -I./GeneratedFiles/Release -ISource -I. 
>>> -IGeneratedFiles/release -o release/CQueryError.o 
>>> Source/Reasoner/Query/CQueryError.cpp
>>> g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
>>> -fstack-protector-strong -Wformat -Werror=format-security -Wall -w 
>>> -D_REENTRANT -DQT_XML_LIB -DQT_NETWORK_LIB 
>>> -DKONCLUDE_FORCE_ALL_DEBUG_DEACTIVATED -DQT_NO_DEBUG -DQT_GUI_LIB 
>>> -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
>>> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
>>> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 
>>> -I./generatedfiles -I./GeneratedFiles/Release -ISource -I. 
>>> -IGeneratedFiles/release -o release/CQueryInconsitentOntologyError.o 
>>> Source/Reasoner/Query/CQueryInconsitentOntologyError.cpp
>>> Source/Reasoner/Query/CQueryInconsitentOntologyError.cpp: In static member 
>>> function 'static Konclude::Reasoner::Query::CQueryInconsitentOntologyError* 
>>> Konclude::Reasoner::Query::CQueryInconsitentOntologyError::getInconsistentOntologyError(Konclude::Reasoner::Query::CQueryError*)':
>>> Source/Reasoner/Query/CQueryInconsitentOntologyError.cpp:57:12: error: 
>>> cannot convert 'bool' to 
>>> 'Konclude::Reasoner::Query::CQueryInconsitentOntologyError*' in return
>>>  return false;
>>> ^
>>>
>>> Makefile:10326: recipe for target 
>>> 'release/CQueryInconsitentOntologyError.o' failed
>
> Kind regards,
>
>  - Jonas
>

Processed: tagging 811849

[Debian Bug Tracking System]

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

> tags 811849 + sid stretch
Bug #811849 [pion] pion: FTBFS with GCC 6: no match for
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#830090: marked as done (Could not find 'bacon')

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 22:19:49 +
with message-id 
and subject line Bug#830090: fixed in ruby-em-spec 0.2.7-1
has caused the Debian Bug report #830090,
regarding Could not find 'bacon'
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.)


-- 
830090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-em-spec
Version: 0.2.6-3
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

% ruby -e 'gem "em-spec"'
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'bacon' (>= 0) among 136 total gem(s) (Gem::LoadError)
[...]

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-em-spec
Source-Version: 0.2.7-1

We believe that the bug you reported is fixed in the latest version of
ruby-em-spec, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Albuquerque Medeiros de Moura  (supplier of 
updated ruby-em-spec 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, 15 Jul 2016 14:35:20 -0300
Source: ruby-em-spec
Binary: ruby-em-spec
Architecture: source
Version: 0.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Albuquerque Medeiros de Moura 
Description:
 ruby-em-spec - BDD for Ruby/EventMachine
Closes: 830090
Changes:
 ruby-em-spec (0.2.7-1) unstable; urgency=medium
 .
   [ Lucas Albuquerque Medeiros de Moura ]
   * Team upload.
   * New upstream release (Closes: #830090)
   * Update ruby-em-spec.docs
   * Remove unused lintian override
   * Add patch to remove git ls-files command from gemspec
   * debian/control: Bump standards-version to 3.9.8
   * debian/rules: Add check-dependencies command
 .
   [ Antonio Terceiro ]
   * debian/control: add Testsuite: field
Checksums-Sha1:
 7fd2d4bd37a88e5a4a8186df2a73369e864c98c8 2085 ruby-em-spec_0.2.7-1.dsc
 46cdf3960c0fb506cb0221bf4e770a7f8c97d433 6568 ruby-em-spec_0.2.7.orig.tar.gz
 7db12acf5732352a54fb35fe46b4a1564f8eb913 3804 
ruby-em-spec_0.2.7-1.debian.tar.xz
Checksums-Sha256:
 e376693a77dd57cb699822b6d87e972b066e8c538e673982de04ca70993cb427 2085 
ruby-em-spec_0.2.7-1.dsc
 ea79f315e72174e97d9c5a98cb251b5cef5b356ff28c5235153359af06ae4801 6568 
ruby-em-spec_0.2.7.orig.tar.gz
 b6655b01885cea3e7efae9b865f36dccad36a052f4d5150f6cec2a295e7c061c 3804 
ruby-em-spec_0.2.7-1.debian.tar.xz
Files:
 88c933b6b674c2a4aca8849d5f91c666 2085 ruby optional ruby-em-spec_0.2.7-1.dsc
 b806b391ecb543b322f35cb662fba5d5 6568 ruby optional 
ruby-em-spec_0.2.7.orig.tar.gz
 8a97bd09a2624a966204f1b3b3049bbb 3804 ruby optional 
ruby-em-spec_0.2.7-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXiUPtAAoJEPwNsbvNRgve3voQAOQcr0UUA6SMoT2ILBeBbhwI
uKXT/26bmXgwdeFkwC71NxA8ri7Gz6gfkn4iOMgM8O/2eIR+NEku5CXyqELt+Ea/
6JTq6x3Qm1WTEghLmPpFR9ShL1OVjZCiFFuVgNEoK7w9gRYaKBz7hsxgnUF8koEV
Ed5wiSaY0azeCnedoNdObZDXCyd69Wx6SAKukRlQ+W7CZrKoI8iSo9YVoiIRDe+2
awab+BBtmw1AhtJZHZMufPEsy2gns/1gqDh/YSCjOdW41q/HqzDoA1+qV3eNOKUh
/rBPcQCaAbJCSzCz+WBW41DOzGscju2JxaESN6+Pa/M0KY6DOpuxI+S+HFfq386g
RySr0l5l5J92Q2G1v8hsL60X/fBIE+vqdITOCWGsI/HS1E8x25mGzmaGhrr0zWFX
bVjclKQ+GsH0X04t+CQAGurKwQU3nv0gkUX6QlgqTZEdNtIt9lRbpwmtIKA30mRY
n4j7zKa8aZHPNOH7Rb92toXkIb3d6zZIJF2eSL8E0JEhSwoA8nZtrxUy7VY5L/+y
WRVSsVECt7eF53DY/MzIfHKvU0cZ80QIwVGhUEwUvTgsYSxenzftzxtd4aiKSBOE
PkHfnExUmaiP8itfCvdSNtNCID0cakyULDYWj854LudpObVNJN+HrvV3jqyleBxO
L6XaMwkXvoAnUeYMMc25
=8Ov7
-END PGP SIGNATURE End Message ---

Bug#831109: marked as done (mathic: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 22:16:31 +
with message-id 
and subject line Bug#831109: fixed in mathic 1.0~git20160320-4
has caused the Debian Bug report #831109,
regarding mathic: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier 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.)


-- 
831109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mathic
Version: 1.0~git20160320-3
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[1]: Entering directory '/«PKGBUILDDIR»'
> dh_strip --dbgsym-migration='libmathic-dbg (<< 1.0~git20160320-1~)'
> make[1]: Leaving directory '/«PKGBUILDDIR»'
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libmathic0v5/DEBIAN/symbols doesn't match 
> completely debian/libmathic0v5.symbols
> --- debian/libmathic0v5.symbols (libmathic0v5_1.0~git20160320-3_amd64)
> +++ dpkg-gensymbols3hUTVg 2016-07-13 19:29:21.32400 +
> @@ -102,7 +102,7 @@
>   _ZNK6mathic10HelpAction5topicB5cxx11Ev@Base 1.0~git20160320
>   _ZNK6mathic11BitTriangle12getMemoryUseEv@Base 1.0~git20130827
>   
> _ZNK6mathic11NameFactoryINS_6ActionEE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
>  1.0~git20160320
> - 
> (optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
>  1.0~git20160320
> +#MISSING: 1.0~git20160320-3# 
> (optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
>  1.0~git20160320
>   _ZNK6mathic13BoolParameter12argumentTypeB5cxx11Ev@Base 1.0~git20160320
>   _ZNK6mathic13BoolParameter13valueAsStringB5cxx11Ev@Base 1.0~git20160320
>   _ZNK6mathic13ColumnPrinter14getColumnCountEv@Base 1.0~git20130827
> @@ -118,15 +118,15 @@
>   
> _ZNK6mathic9CliParser29pushBackRegisteredActionNamesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base
>  1.0~git20160320
>   
> _ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED1Ev@Base
>  1.0~git20160320
>   
> _ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED2Ev@Base
>  1.0~git20160320
> - 
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
>  1.0~git20160320
> +#MISSING: 1.0~git20160320-3# 
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
>  1.0~git20160320
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
>  1.0~git20160320
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
>  1.0~git20160320
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
>  1.0~git20160320
> - 
> _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
>  1.0~git20130827
> +#MISSING: 1.0~git20160320-3# 
> _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
>  1.0~git20130827
>   
> _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
>  1.0~git20130827
>   
> _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED1Ev@Base
>  1.0~git20130827
>   
> _ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED2Ev@Base
>  1.0~git20130827
> - 
> _ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base
>  1.0~git20160320
> +#MISSING: 1.0~git20160320-3# 
> 

Bug#830434: marked as done (diffoscope: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 22:06:24 +
with message-id 
and subject line Bug#830434: fixed in diffoscope 55
has caused the Debian Bug report #830434,
regarding diffoscope: FTBFS: dh_auto_test: pybuild --test --test-pytest -i 
python{version} -p 3.5 returned exit code 13
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.)


-- 
830434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diffoscope
Version: 54
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 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):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope
> copying diffoscope/config.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope
> copying diffoscope/difference.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope
> copying diffoscope/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope
> copying diffoscope/changes.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope
> copying diffoscope/__main__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/debian_fallback.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/xz.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/dex.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/zip.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/ppu.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/rpm.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/mono.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/haskell.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/utils.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/symlink.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/binary.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/tar.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/gzip.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/ps.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/device.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/rpm_fallback.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/squashfs.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/icc.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/gettext.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/image.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/bzip2.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/macho.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying diffoscope/comparators/elf.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators
> copying 

Bug#827835: What's the status of this RC bug?

[Francesco Poli]

Hello,
I must confess that I am beginning to be mildly worried about
bug #827835: this serious bug report was filed back on June,
the 21st and appears to be still unaddressed without any
visible activity.

Package ruby-xmlparser risks to be autoremoved (along with its
reverse dependencies, among which apt-listbugs, which I maintain),
because of this bug.

Could you please clarify what is the status of this RC bug?
Is it going to be fixed soon?

Please let me know.
Thanks for your time and dedication!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpLHlIHmUmhW.pgp
Description: PGP signature

Bug#831106: build with other mpich lib

[Thorsten Alteholz]

Hi Lucas,

according to the logfile the problem is:
 configure:4194: checking for mpi.h
 configure:4207: mpic++ -c -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/hdf5/mpich 
conftest.cpp >&5
 In file included from /usr/include/mpich/mpi.h:2231:0,
  from conftest.cpp:11:
 /usr/include/mpich/mpicxx.h:21:4: error: #error 'Please use the same version 
of GCC and g++ for compiling MPICH and user MPI programs'

So can you please redo the test with the version of mpich that is compiled 
with gcc6?


  Thorsten

Bug#830151: xorgs: Do not have a human maintainer/uploader listed

[Julien Cristau]

Control: severity -1 normal

On Wed, Jul  6, 2016 at 19:02:53 +0200, Tobias Frost wrote:

> Package: xorg
> Version: 1:7.7+15
> Severity: serious
> Justification: Policy 3.3 / 5.6.3
> 
https://release.debian.org/stretch/rc_policy.txt doesn't list this as
release critical.  If you want to be listed in xorg's Uploaders, feel
free.

Cheers,
Julien

Processed: Re: Bug#830151: xorgs: Do not have a human maintainer/uploader listed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #830151 [xorg] xorgs: Do not have a human maintainer/uploader listed
Severity set to 'normal' from 'serious'

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

Processed: Re: jquery-goodies: Update to PHP7.0 dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #831363 [jquery-goodies] jquery-goodies: Update to PHP7.0 dependencies
Severity set to 'serious' from 'wishlist'

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

Bug#830356: marked as done (libhttp-oai-perl: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 19:20:22 +
with message-id 
and subject line Bug#830356: fixed in libhttp-oai-perl 4.03-2
has caused the Debian Bug report #830356,
regarding libhttp-oai-perl: accesses the internet during build
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.)


-- 
830356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhttp-oai-perl
Version: 4.03-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst libhttp-oai-perl builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 3958ed5935b9.50691 > dnscache.uct.ac.za.domain: 21668+ A? 
domain.invalid. (32)
  00:00:00.49 IP 3958ed5935b9.50691 > dnscache.uct.ac.za.domain: 32332+ 
? domain.invalid. (32)
  00:00:00.156406 IP dnscache.uct.ac.za.domain > 3958ed5935b9.50691: 21668 
NXDomain 0/1/0 (107)
  00:00:00.158388 IP dnscache.uct.ac.za.domain > 3958ed5935b9.50691: 32332 
NXDomain 0/1/0 (107)
  00:00:00.158556 IP 3958ed5935b9.49431 > dnscache.uct.ac.za.domain: 14715+ A? 
domain.invalid.uct.ac.za. (42)
  00:00:00.158627 IP 3958ed5935b9.49431 > dnscache.uct.ac.za.domain: 30397+ 
? domain.invalid.uct.ac.za. (42)

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


libhttp-oai-perl.4.03-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libhttp-oai-perl
Source-Version: 4.03-2

We believe that the bug you reported is fixed in the latest version of
libhttp-oai-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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libhttp-oai-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: SHA512

Format: 1.8
Date: Fri, 15 Jul 2016 21:00:09 +0200
Source: libhttp-oai-perl
Binary: libhttp-oai-perl
Architecture: source
Version: 4.03-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 830356
Description: 
 libhttp-oai-perl - API for the OAI-PMH
Changes:
 libhttp-oai-perl (4.03-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ gregor herrmann ]
   * Rename autopkgtest configuration file(s) as per new pkg-perl-
 autopkgtest schema.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * debian/upstream/metadata: use HTTPS for GitHub URLs.
   * Add patch to skip tests which do a DNS query.
 Thanks to Chris Lamb for the bug report. (Closes: #830356)
   * Add a patch to fix spelling mistakes in the POD.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 7010555a2562d4563917941a39c06dda8e726d51 2415 libhttp-oai-perl_4.03-2.dsc
 ec70f49d9f9ea1e741e85f5a52d23455fde768d7 4892 
libhttp-oai-perl_4.03-2.debian.tar.xz
Checksums-Sha256: 
 e19acc5ff19256f76f56eb8ef85e60e2b969464b8a3cf6478e615f120eb845b3 2415 
libhttp-oai-perl_4.03-2.dsc
 c3673e4be56f6a8bfb230220c24a4e74c694b084eda570f2d4619e9b97ee3706 4892 
libhttp-oai-perl_4.03-2.debian.tar.xz
Files: 
 49f82360fbf600c4314d865bfed4cfae 2415 perl optional libhttp-oai-perl_4.03-2.dsc
 e4a74b9749db039cf0c4c9973ccce9b5 4892 perl optional 
libhttp-oai-perl_4.03-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXiTMYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGk6MQAJ+k4u4cD+mn8kJGCpwkydAA
+5IHLRVFkUp+FbVq4bzJr5MbRZZKHGoR/X0UOiswQx7GR0evPq/jP0tfNo9DhlRp
DGwIal3PmGMopemi3ygfENw5OaiSdjXBGiw2yYAw9m48kvmyOMKouU3XgHuv6OM5

Bug#830715: musescore: just rebuilding from source package fixes this

[Giacomo Mulas]

Package: musescore
Version: 2.0.2+dfsg-2
Followup-For: Bug #830715

Dear Maintainer,

musescore became uninstallable when qtquick1 was removed. 
However, it builds flawlessly from the source package: I just did it 
locally and obtained an installable and perfectly working musescore
package. Please just rebuild it ignoring (or removing) the 
build-depends: qtquick1-5-dev and you will get a working package.

Thanks, bye
Giacomo

Bug#831418: EOL: not to be released with Stretch

[David Prévot]

Source: zendframework
Severity: serious
Tags: security sid stretch

Hi,

Upstream recently stated [0] that “Zend Framework 1 reaches its End of
Life (EOL) […] on 28 September 2016.”

0: https://framework.zend.com/blog/2016-06-28-zf1-eol.html

Therefore, we should not release it with Stretch (and we’ll do our best
to support it during Jessie lifetime). Reverse dependencies already had
an important bug report about zendframework removal for Stretch a while
ago.

Regards

David


signature.asc
Description: PGP signature

Bug#830356: Pending fixes for bugs in the libhttp-oai-perl package

[pkg-perl-maintainers]

tag 830356 + pending
thanks

Some bugs in the libhttp-oai-perl package are closed in revision
f2a70ebff0f524a0a5bea71f551a44f98df6f27d in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libhttp-oai-perl.git/commit/?id=f2a70eb

Commit message:

Add patch to skip tests which do a DNS query.

Thanks: Chris Lamb for the bug report.
Closes: #830356

Processed: Pending fixes for bugs in the libhttp-oai-perl package

[Debian Bug Tracking System]

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

> tag 830356 + pending
Bug #830356 [src:libhttp-oai-perl] libhttp-oai-perl: accesses the internet 
during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811796: marked as done (jigzo: FTBFS with GCC 6: error: reference is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 18:35:06 +
with message-id 
and subject line Bug#811796: fixed in jigzo 0.6.1-7
has caused the Debian Bug report #811796,
regarding jigzo: FTBFS with GCC 6: error: reference is ambiguous
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.)


-- 
811796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jigzo
Version: 0.6.1-6
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-reference-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
...
> g++ -g -I/usr/include/SDL -DENABLE_SOUND -Wall -c src/main.cxx -o 
> obj/main.LINUX.o
> src/main.cxx: In function 'void Randomize()':
> src/main.cxx:987:3: warning: statement is indented as if it were guarded 
> by... [-Wmisleading-indentation]
>float cx = 0.f;
>^
> 
> src/main.cxx:985:2: note: ...this 'for' clause, but it is not
>   for (int i = 0; i < n; i++)
>   ^~~
> 
> src/main.cxx: In function 'int main(int, char**)':
> src/main.cxx:1597:16: error: reference to 'end' is ambiguous
>while (mode!=end) {
> ^~~
> 
> src/main.cxx:168:2: note: candidates are: Mode end
>   end
>   ^~~
> 
> In file included from /usr/include/c++/6/list:62:0,
>  from src/main.cxx:58:
> /usr/include/c++/6/bits/range_access.h:107:37: note: 
> template const _Tp* std::end(const std::valarray<_Tp>&)
>template const _Tp* end(const valarray<_Tp>&);
>  ^~~
> 
> /usr/include/c++/6/bits/range_access.h:106:31: note: 
> template _Tp* std::end(std::valarray<_Tp>&)
>template _Tp* end(valarray<_Tp>&);
>^~~
> 
> /usr/include/c++/6/bits/range_access.h:97:5: note: 
> template constexpr _Tp* std::end(_Tp 
> (&)[_Nm])
>  end(_Tp (&__arr)[_Nm])
>  ^~~
> 
> /usr/include/c++/6/bits/range_access.h:78:5: note: 
> template decltype (__cont.end()) std::end(const _Container&)
>  end(const _Container& __cont) -> decltype(__cont.end())
>  ^~~
> 
> /usr/include/c++/6/bits/range_access.h:68:5: note: 
> template decltype (__cont.end()) std::end(_Container&)
>  end(_Container& __cont) -> decltype(__cont.end())
>  ^~~
> 
> In file included from /usr/include/c++/6/bits/range_access.h:36:0,
>  from /usr/include/c++/6/list:62,
>  from src/main.cxx:58:
> /usr/include/c++/6/initializer_list:99:5: note: 
> template constexpr const _Tp* std::end(std::initializer_list<_Tp>)
>  end(initializer_list<_Tp> __ils) noexcept
>  ^~~
> 
> src/main.cxx:1636:27: error: reference to 'end' is ambiguous
>FadeOutTo(end_intro,end);
>^~~
> 
> src/main.cxx:168:2: note: candidates are: Mode end
>   end
>   ^~~
> 
> In file included from /usr/include/c++/6/list:62:0,
>  from src/main.cxx:58:
> /usr/include/c++/6/bits/range_access.h:107:37: note: 
> template const _Tp* std::end(const std::valarray<_Tp>&)
>template const _Tp* end(const valarray<_Tp>&);
>  ^~~
> 
> /usr/include/c++/6/bits/range_access.h:106:31: note: 
> template _Tp* std::end(std::valarray<_Tp>&)
>template _Tp* end(valarray<_Tp>&);
>^~~
> 
> /usr/include/c++/6/bits/range_access.h:97:5: note: 
> template constexpr _Tp* std::end(_Tp 
> (&)[_Nm])
>  end(_Tp (&__arr)[_Nm])
>  ^~~
> 
> /usr/include/c++/6/bits/range_access.h:78:5: note: 
> template decltype (__cont.end()) std::end(const _Container&)
>  end(const _Container& __cont) -> decltype(__cont.end())
>  ^~~
> 
> /usr/include/c++/6/bits/range_access.h:68:5: note: 
> template decltype (__cont.end()) std::end(_Container&)
>  end(_Container& __cont) -> decltype(__cont.end())
>  ^~~
> 
> In file included from /usr/include/c++/6/bits/range_access.h:36:0,
>  from /usr/include/c++/6/list:62,
>   

Bug#831403: marked as done (xmlgraphics-commons: FTBFS: Could not initialize class org.mockito.Mockito)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 18:23:10 +
with message-id 
and subject line Bug#831403: fixed in mockito 1.10.19-2
has caused the Debian Bug report #831403,
regarding xmlgraphics-commons: FTBFS: Could not initialize class 
org.mockito.Mockito
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.)


-- 
831403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmlgraphics-commons
Version: 2.1-1
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,

xmlgraphics-commons fails to build from source in unstable/amd64:

  [..]

  [junit] 
  [junit] - Standard Output ---
  [junit] Skipping endianness test for ImageIO-based TIFF writer because 
JAI ImageIO Tools is not available!
  [junit] Skipping endianness test for ImageIO-based TIFF writer because 
JAI ImageIO Tools is not available!
  [junit] -  ---
  [junit] Testsuite: 
org.apache.xmlgraphics.io.TempResourceURIGeneratorTestCase
  [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.071 sec
  [junit] 
  [junit] Testsuite: org.apache.xmlgraphics.io.URIResolverAdapterTestCase
  [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 
0.087 sec
  [junit] 
  [junit] Testcase: 
testCatalogResolver(org.apache.xmlgraphics.io.URIResolverAdapterTestCase):SKIPPED:
 Literally no idea why this doesn't work... Gonna look at the catalog resolver 
source
  [junit] Testcase: 
testCatalogResolverInAdapter(org.apache.xmlgraphics.io.URIResolverAdapterTestCase):SKIPPED:
 Literally no idea why this doesn't work... Gonna look at the catalog resolver 
source
  [junit] Testsuite: org.apache.xmlgraphics.io.XmlSourceUtilTestCase
  [junit] Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed: 
0.113 sec
  [junit] 
  [junit] Testcase: 
testCloseQuietlyStreamSource(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):  
Caused an ERROR
  [junit] net/sf/cglib/proxy/Callback
  [junit] java.lang.NoClassDefFoundError: net/sf/cglib/proxy/Callback
  [junit]   at java.lang.Class.forName0(Native Method)
  [junit]   at java.lang.Class.forName(Class.java:264)
  [junit]   at 
org.mockito.internal.configuration.plugins.PluginLoader.loadPlugin(PluginLoader.java:33)
  [junit]   at 
org.mockito.internal.configuration.plugins.PluginRegistry.(PluginRegistry.java:13)
  [junit]   at 
org.mockito.internal.configuration.plugins.Plugins.(Plugins.java:11)
  [junit]   at org.mockito.internal.util.MockUtil.(MockUtil.java:24)
  [junit]   at org.mockito.internal.MockitoCore.(MockitoCore.java:44)
  [junit]   at org.mockito.Mockito.(Mockito.java:975)
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] Caused by: java.lang.ClassNotFoundException: 
net.sf.cglib.proxy.Callback
  [junit]   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
  [junit]   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
  [junit]   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
  [junit]   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
  [junit] 
  [junit] 
  [junit] Testcase: 
testNeedInputStreamFailureCaseStreamImage(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):
 Caused an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] 
  [junit] 
  [junit] Testcase: 
testHasInputStream(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):Caused 
an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] 
  [junit] 
  [junit] Testcase: 
testCloseQuietlyImageSource(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):   
Caused an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 

Processed: closing 830403

[Debian Bug Tracking System]

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

> close 830403 2.048-1
Bug #830403 [src:libconfig-model-lcdproc-perl] libconfig-model-lcdproc-perl: 
FTBFS: Attribute (instance) does not pass the type constraint because: 
Validation failed for 'Config::Model::Instance' with value undef at 
/usr/lib/x86_64-linux-gnu/perl5/5.22/Mouse/Util.pm line 386.
Marked as fixed in versions libconfig-model-lcdproc-perl/2.048-1.
Bug #830403 [src:libconfig-model-lcdproc-perl] libconfig-model-lcdproc-perl: 
FTBFS: Attribute (instance) does not pass the type constraint because: 
Validation failed for 'Config::Model::Instance' with value undef at 
/usr/lib/x86_64-linux-gnu/perl5/5.22/Mouse/Util.pm line 386.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#830403: closing 830403

[Dominique Dumont]

close 830403 2.048-1
thanks

Got the wrong number in changelog

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Processed: Re: Processed: Re: Bug#822717: flann: FTBFS with GCC 6: call of overloaded 'abs(

[Debian Bug Tracking System]

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

> # On 2016-07-15 Debian Bug Tracking System  wrote:
> # > Processing control commands:
> #
> # > > tags -1 fixed upstream
> # > Bug #822717 [flann] flann: FTBFS with GCC 6: call of overloaded 'abs(
> # > Added tag(s) fixed and upstream.
> #fix typo
> tags 822717 - fixed
Bug #822717 [flann] flann: FTBFS with GCC 6: call of overloaded 'abs(
Removed tag(s) fixed.
> tags 822717 - upstream
Bug #822717 [flann] flann: FTBFS with GCC 6: call of overloaded 'abs(
Removed tag(s) upstream.
> tags 822717 fixed-upstream
Bug #822717 [flann] flann: FTBFS with GCC 6: call of overloaded 'abs(
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Bug#822717: flann: FTBFS with GCC 6: call of overloaded 'abs(

[Andreas Metzler]

Control: tags -1 fixed upstream

On 2016-04-26 Martin Michlmayr  wrote:
> Package: flann
> Version: 1.8.4-4.1
[...]
> > /<>/examples/flann_example.cpp:36:1:   required from here
> > /<>/src/cpp/flann/algorithms/kdtree_index.h:666:39: error: 
> > call of overloaded 'abs(flann::KDTreeIndex > >::ElementType)' is ambiguous
[...]

This is fixed in 1.8.5.

http://github.com/mariusmuja/flann/releases
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'

Processed: Re: Bug#822717: flann: FTBFS with GCC 6: call of overloaded 'abs(

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed upstream
Bug #822717 [flann] flann: FTBFS with GCC 6: call of overloaded 'abs(
Added tag(s) fixed and upstream.

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

Processed: patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #831181 [src:odin] odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: 
call of overloaded 'sqrt(funcMode&)' is ambiguous
Added tag(s) patch.
> tags -1 pending
Bug #831181 [src:odin] odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: 
call of overloaded 'sqrt(funcMode&)' is ambiguous
Added tag(s) pending.

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

Bug#831181: patch

[Gianfranco Costamagna]

control: tags -1 patch
control: tags -1 pending

Hi maintainer, the patch for this issue has been uploaded on deferred/5, and 
attached
to this email.

G.


debdiff
Description: Binary data

Bug#830234: marked as done (rb_sysopen - /usr/lib/ruby/vendor_ruby/../VERSION)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 17:30:06 +
with message-id 
and subject line Bug#830234: fixed in ruby-webfinger 1.0.2-2
has caused the Debian Bug report #830234,
regarding rb_sysopen - /usr/lib/ruby/vendor_ruby/../VERSION
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.)


-- 
830234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-webfinger
Version: 1.0.2-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

% ruby -e 'require "webfinger"'
/usr/lib/ruby/vendor_ruby/webfinger.rb:7:in `read': No such file or directory @ 
rb_sysopen - /usr/lib/ruby/vendor_ruby/../VERSION (Errno::ENOENT)
  from /usr/lib/ruby/vendor_ruby/webfinger.rb:7:in `'
  from /usr/lib/ruby/vendor_ruby/webfinger.rb:6:in `'
  from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from -e:1:in `'

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-webfinger
Source-Version: 1.0.2-2

We believe that the bug you reported is fixed in the latest version of
ruby-webfinger, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-webfinger 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, 15 Jul 2016 21:35:34 +0530
Source: ruby-webfinger
Binary: ruby-webfinger
Architecture: source
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-webfinger - Ruby WebFinger client library
Closes: 830234
Changes:
 ruby-webfinger (1.0.2-2) unstable; urgency=medium
 .
   * Install as gem (Closes: #830234)
Checksums-Sha1:
 0de3f0026a9927d0a641f9bf19dbc0fcbcd22058 2163 ruby-webfinger_1.0.2-2.dsc
 fb0af2b118551ec659b4d3d53f76de82a98da97b 2300 
ruby-webfinger_1.0.2-2.debian.tar.xz
Checksums-Sha256:
 088f25ae57761ce2a3d38b7ed269518157414ae04359e689bf9c6d6f27c279cc 2163 
ruby-webfinger_1.0.2-2.dsc
 e0de6cfa9eb06b05645ff882db149c4a4044c8eac752912d9d51f5970870fdab 2300 
ruby-webfinger_1.0.2-2.debian.tar.xz
Files:
 c1d7386f6edbe59af2c726ee9928f0a1 2163 ruby optional ruby-webfinger_1.0.2-2.dsc
 c57e24975584c22ddea4b222e8b96fa1 2300 ruby optional 
ruby-webfinger_1.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXiQy7AAoJEM4fnGdFEsIqGCYP/16F7UuZJl5S7r2frkuq8xyW
d+JK2BrHdn7lC6GMulNx4Ykk47QHXl9SkYdQcHxg1DFEOz27F4K3ijKYp3lgEj9P
D/vQM6gSi6Jf+ZKdyZTQ7S8Aw5Q+W90bvOdahhIs0A3KbkOTShb0+hMPVQhooL2T
GcWawOLLruzgqEDvCq7tM5X1noGgb29QRRYQB5SaCfVIRwPsA0UBYY6KeQCcDffJ
yEGop9MiFcuv93diA9Dn6YIt8+rQCHvEyGqt4zRLbBo0N1rhFRd+l1fCHKwkUM5n
0v3cCsx8D1MJzhy1J4xcZ11pC93Wiw8Juzak+g+7+os0XbRAeX6fguYmHDwt9Qrk
u/GPKL0WzBGf6gEaSJnFuDHp5YmPxrvV/wzrwwnwWBnk6HqAB+sOPO6FD1OeCcpT
0x2cn2TM+vz3gDeIJNNOCjY7j2Obl7o0OdEXVmZOsOKDVlrQTvYiX1ndL9Ox/tkY
BIFI6lwKrU3UFfM/r1U3yMJvPMdeVjgSnMtb0V4PdCglFPwUUcXCDgZro8uKmQgX
8sdwuEAN3DRTivwOeRmcd9kOq/oOVjG60IUEkvyIN22/j9sc0MQJg6SFpMiEYG8I
gCYKn0fwwadDKtkZTA7KyAgWNVv8zVJyGiwCs5Pj0i7l5KYdRPlqR2y8xKIyvEZ6
ZcrRaolQ6dchrvCEL0IO
=etdM
-END PGP SIGNATURE End Message ---

Bug#831155: marked as done (vdr-plugin-sudoku: FTBFS with GCC 6: cstdlib:124:11: error: '::div_t' has not been declared)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 17:30:25 +
with message-id 
and subject line Bug#831155: fixed in vdr-plugin-sudoku 0.3.5-20
has caused the Debian Bug report #831155,
regarding vdr-plugin-sudoku: FTBFS with GCC 6: cstdlib:124:11: error: '::div_t' 
has not been declared
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.)


-- 
831155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-sudoku
Version: 0.3.5-19
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):
> g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
> -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -D_LARGEFILE64_SOURCE -Wl,-z,relro -I/usr/include/vdr/include -D_GNU_SOURCE 
> -DPLUGIN_NAME_I18N='"sudoku"' -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
> generator.o generator.cpp
> In file included from /usr/include/c++/6/stdlib.h:36:0,
>  from sudoku.h:35,
>  from generator.h:24,
>  from generator.cpp:22:
> /usr/include/c++/6/cstdlib:124:11: error: '::div_t' has not been declared
>using ::div_t;
>^
> /usr/include/c++/6/cstdlib:125:11: error: '::ldiv_t' has not been declared
>using ::ldiv_t;
>^~
> /usr/include/c++/6/cstdlib:127:11: error: '::abort' has not been declared
>using ::abort;
>^
> /usr/include/c++/6/cstdlib:128:11: error: '::abs' has not been declared
>using ::abs;
>^~~
> /usr/include/c++/6/cstdlib:129:11: error: '::atexit' has not been declared
>using ::atexit;
>^~
> /usr/include/c++/6/cstdlib:132:11: error: '::at_quick_exit' has not been 
> declared
>using ::at_quick_exit;
>^
> /usr/include/c++/6/cstdlib:135:11: error: '::atof' has not been declared
>using ::atof;
>^~~~
> /usr/include/c++/6/cstdlib:136:11: error: '::atoi' has not been declared
>using ::atoi;
>^~~~
> /usr/include/c++/6/cstdlib:137:11: error: '::atol' has not been declared
>using ::atol;
>^~~~
> /usr/include/c++/6/cstdlib:138:11: error: '::bsearch' has not been declared
>using ::bsearch;
>^~~
> /usr/include/c++/6/cstdlib:139:11: error: '::calloc' has not been declared
>using ::calloc;
>^~
> /usr/include/c++/6/cstdlib:140:11: error: '::div' has not been declared
>using ::div;
>^~~
> /usr/include/c++/6/cstdlib:141:11: error: '::exit' has not been declared
>using ::exit;
>^~~~
> /usr/include/c++/6/cstdlib:142:11: error: '::free' has not been declared
>using ::free;
>^~~~
> /usr/include/c++/6/cstdlib:143:11: error: '::getenv' has not been declared
>using ::getenv;
>^~
> /usr/include/c++/6/cstdlib:144:11: error: '::labs' has not been declared
>using ::labs;
>^~~~
> /usr/include/c++/6/cstdlib:145:11: error: '::ldiv' has not been declared
>using ::ldiv;
>^~~~
> /usr/include/c++/6/cstdlib:146:11: error: '::malloc' has not been declared
>using ::malloc;
>^~
> /usr/include/c++/6/cstdlib:148:11: error: '::mblen' has not been declared
>using ::mblen;
>^
> /usr/include/c++/6/cstdlib:149:11: error: '::mbstowcs' has not been declared
>using ::mbstowcs;
>^~~~
> /usr/include/c++/6/cstdlib:150:11: error: '::mbtowc' has not been declared
>using ::mbtowc;
>^~
> /usr/include/c++/6/cstdlib:152:11: error: '::qsort' has not been declared
>using ::qsort;
>^
> /usr/include/c++/6/cstdlib:155:11: error: '::quick_exit' has not been declared
>using ::quick_exit;
>^~
> /usr/include/c++/6/cstdlib:158:11: error: '::rand' has not been declared
>using ::rand;
>^~~~
> /usr/include/c++/6/cstdlib:159:11: error: '::realloc' has not been declared
>using ::realloc;
>^~~
> /usr/include/c++/6/cstdlib:160:11: error: 

Bug#830218: marked as done (licenseutils: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 17:28:16 +
with message-id 
and subject line Bug#830218: fixed in licenseutils 0.0.7-7
has caused the Debian Bug report #830218,
regarding licenseutils: accesses the internet during build
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.)


-- 
830218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: licenseutils
Version: 0.0.7-6
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst licenseutils builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 6bdfa88468c7.34989 > dnscache.uct.ac.za.domain: 46155+ A? 
gnu.org. (25)
  00:00:00.158125 IP dnscache.uct.ac.za.domain > 6bdfa88468c7.34989: 46155 
1/3/5 A 208.118.235.148 (199)
  00:00:00.158271 IP 6bdfa88468c7 > wildebeest.gnu.org: ICMP echo request, id 
17456, seq 0, length 64
  00:00:00.386610 IP wildebeest.gnu.org > 6bdfa88468c7: ICMP echo reply, id 
17456, seq 0, length 64

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


licenseutils.0.0.7-6.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: licenseutils
Source-Version: 0.0.7-7

We believe that the bug you reported is fixed in the latest version of
licenseutils, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated licenseutils 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: Fri, 15 Jul 2016 17:09:34 +
Source: licenseutils
Binary: licenseutils
Architecture: source
Version: 0.0.7-7
Distribution: unstable
Urgency: medium
Maintainer: Mattia Rizzolo 
Changed-By: Mattia Rizzolo 
Description:
 licenseutils - Put copyright and license notices at the head of source code 
file
Closes: 830218
Changes:
 licenseutils (0.0.7-7) unstable; urgency=medium
 .
   * Add patch to totally skip tests with network access.  Closes: #830218
   * Forward the patches.
Checksums-Sha1:
 40b1d1efdc99ab00dced0165ce9520e982914f0c 1965 licenseutils_0.0.7-7.dsc
 4774bb5402f0a2cc4ea7565c7444532cd9fbe2b2 8392 
licenseutils_0.0.7-7.debian.tar.xz
Checksums-Sha256:
 fcbf9606bcc390d7c04c9514106220687af91ff89ed275a2f80debb73e823102 1965 
licenseutils_0.0.7-7.dsc
 f9086b8501830dada4447ac338a550e93d38e50195f662ce9438256abb3dd856 8392 
licenseutils_0.0.7-7.debian.tar.xz
Files:
 b398ccd9eb667de1232992e99c459777 1965 devel optional licenseutils_0.0.7-7.dsc
 2470f0d284628e9357e30bd97201e414 8392 devel optional 
licenseutils_0.0.7-7.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXiRo4AAoJEEsEP825REVAOH4QAKKgNUJsbbAisdcrQAZjDAzs
4QekpjdOM3vzIabLoBzEspUWgfAKp/33EIgYVJcY2dqhXu5tJ4LyYkcJp1L15wv/
fXiHo/HmPgNQ1VCjVsSDZrCUFb02QHPx0KepbYfoAOI0JBiM/KTiZPPgzNIUqKM/
b1R29gy80YiJ5rX+3UG5Ob0Pm4LGZrX4EHVYLdKCe29ynTkP1lTJ+HdfR3keum3D
wylcdtBLHl/VYARqd/q/UwXVdpY4ulXpFaClZRVzhLPXCfTMk1EtxBDO8zG9oEk7
M2rKqF2bWpXdk5SmbMU8mOUaEYUZdlSpZFSPu+vwz4L2cU/ambQ3N3HHZl80yASs
3Rjps3yddM2zHu+4/YaBaO2d4T77sqjqPZoFs7ezirrCphlvZPXUi0icCZmcJh1e
yYiMeK2pKcexREPiEzkOrH1PcmsL238L7R+BCqoeTk1BD0lnJUdriiT1WJAJ/6Nx
HGOHCqrS1wP4UJRPhopqb4BV6fIjfipY/SenEGhR2/63cC22j5THNKaerbnwS86b
JHe8LtHNcNJfKvfe3sWq8MAPuwucO2Inmpvz3ODGeupjOjWQ3glh7J1v+kVTW1B2
XZPMLQjZPUV302XXp4Tho3iS7eEw5xL8fHpbtKYWJsndyqHdPHi/uc04Zr5KkHIg
w3YFmkF7kKtsdB7ES/bK
=vhAn
-END PGP SIGNATURE End Message ---

Bug#831403: xmlgraphics-commons: FTBFS: Could not initialize class org.mockito.Mockito

[Emmanuel Bourg]

Control: reassign -1 mockito 1.10.19-1
Control: affects -1 xmlgraphics-commons

On 07/15/2016 06:24 PM, Chris Lamb wrote:

>   [junit] Caused by: java.lang.ClassNotFoundException: 
> net.sf.cglib.proxy.Callback
>   [junit] at 
> java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   [junit] at 
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

Thank you for the report Chris. This issue was caused by the latest
mockito update, the mockito jar no longer has a Class-Path attribute and
this package relied on it. I'll fix mockito.

Bug#831109: mathic: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Doug Torrance]

Control: tags -1 pending

On 07/14/2016 04:06 AM, Lucas Nussbaum wrote:

Source: mathic
Version: 1.0~git20160320-3
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[1]: Entering directory '/«PKGBUILDDIR»'
dh_strip --dbgsym-migration='libmathic-dbg (<< 1.0~git20160320-1~)'
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_makeshlibs -a
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libmathic0v5/DEBIAN/symbols doesn't match 
completely debian/libmathic0v5.symbols
--- debian/libmathic0v5.symbols (libmathic0v5_1.0~git20160320-3_amd64)
+++ dpkg-gensymbols3hUTVg   2016-07-13 19:29:21.32400 +
@@ -102,7 +102,7 @@
   _ZNK6mathic10HelpAction5topicB5cxx11Ev@Base 1.0~git20160320
   _ZNK6mathic11BitTriangle12getMemoryUseEv@Base 1.0~git20130827
   
_ZNK6mathic11NameFactoryINS_6ActionEE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
- 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-3# 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
   _ZNK6mathic13BoolParameter12argumentTypeB5cxx11Ev@Base 1.0~git20160320
   _ZNK6mathic13BoolParameter13valueAsStringB5cxx11Ev@Base 1.0~git20160320
   _ZNK6mathic13ColumnPrinter14getColumnCountEv@Base 1.0~git20130827
@@ -118,15 +118,15 @@
   
_ZNK6mathic9CliParser29pushBackRegisteredActionNamesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base
 1.0~git20160320
   
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED1Ev@Base 
1.0~git20160320
   
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED2Ev@Base 
1.0~git20160320
- 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-3# 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
   
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
 1.0~git20160320
   
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
 1.0~git20160320
   
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
 1.0~git20160320
- 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
+#MISSING: 1.0~git20160320-3# 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
   
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
 1.0~git20130827
   
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED1Ev@Base
 1.0~git20130827
   
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED2Ev@Base
 1.0~git20130827
- 
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-3# 
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base
 1.0~git20160320
   
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIJSE_EEEvDpOT_@Base
 1.0~git20160320
   _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 
1.0~git20160320
   _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 
1.0~git20160320
dh_makeshlibs: failing due to earlier errors
make: *** [binary-arch] Error 255


The full build log is available from:

http://people.debian.org/~lucas/logs/2016/07/13/mathic_1.0~git20160320-3_unstable_gcc6.log


Thanks for the report!

I have pushed a fix to git marking the offending tags as optional [1] 
and have requested sponsorship for an upload of the new version.


Doug

[1] 

Processed: Re: Bug#831109: mathic: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #831109 [src:mathic] mathic: FTBFS with GCC 6: dh_makeshlibs: failing due 
to earlier errors
Added tag(s) pending.

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

Bug#831392: marked as done (rant: cannot load such file -- rant/rantlib (LoadError))

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 17:23:24 +
with message-id 
and subject line Bug#831393: Removed package(s) from unstable
has caused the Debian Bug report #831392,
regarding rant: cannot load such file -- rant/rantlib (LoadError)
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.)


-- 
831392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rant
Version: 0.5.8-8
Severity: grave
Tags: sid stretch jessie

Dear Maintainer,

when running "rant" from a shell, it fails to start:

% rant
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot 
load such file -- rant/rantlib (LoadError)
  from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from /usr/bin/rant:11:in `'

This also happens in jessie.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Version: 0.5.8-8+rm

Dear submitter,

as the package rant has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/831393

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: Bug#831403: xmlgraphics-commons: FTBFS: Could not initialize class org.mockito.Mockito

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 mockito 1.10.19-1
Bug #831403 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS: Could not 
initialize class org.mockito.Mockito
Bug reassigned from package 'src:xmlgraphics-commons' to 'mockito'.
No longer marked as found in versions xmlgraphics-commons/2.1-1.
Ignoring request to alter fixed versions of bug #831403 to the same values 
previously set
Bug #831403 [mockito] xmlgraphics-commons: FTBFS: Could not initialize class 
org.mockito.Mockito
There is no source info for the package 'mockito' at version '1.10.19-1' with 
architecture ''
Unable to make a source version for version '1.10.19-1'
Marked as found in versions 1.10.19-1.
> affects -1 xmlgraphics-commons
Bug #831403 [mockito] xmlgraphics-commons: FTBFS: Could not initialize class 
org.mockito.Mockito
Added indication that 831403 affects xmlgraphics-commons

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

Processed: Bug#830218 in licenseutils marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 830218 pending
Bug #830218 [src:licenseutils] licenseutils: accesses the internet during build
Added tag(s) pending.

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

Bug#830218: in licenseutils marked as pending

[Mattia Rizzolo]

Control: tag 830218 pending

Hello,

Bug #830218 in licenseutils reported by you has been fixed in the Git 
repository. You can
see the commit message below, and you can check the diff of the fix at:


https://anonscm.debian.org/git/collab-maint/licenseutils.git/commit/?id=4e1e958

(this message was generated automatically based on the debian/changelog diff)
---
commit 4e1e9582f1ce13a769370510ab3510d166ee236d
Author: Mattia Rizzolo 
Date:   Fri Jul 15 17:19:02 2016 +

changelog for 0.0.7-7

Bug#830409: marked as done (ahven: FTBFS: build-dependency not installable: gnat-4.9)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 17:00:11 +
with message-id 
and subject line Bug#830409: fixed in ahven 2.6-1
has caused the Debian Bug report #830409,
regarding ahven: FTBFS: build-dependency not installable: gnat-4.9
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.)


-- 
830409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ahven
Version: 2.4+repack-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 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):
> ┌──┐
> │ Install ahven build dependencies (apt-based resolver)   
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-ahven-dummy : Depends: gnat-4.9 but it is not going to 
> be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/ahven_2.4+repack-1_unstable_reb.normal.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: ahven
Source-Version: 2.6-1

We believe that the bug you reported is fixed in the latest version of
ahven, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reto Buerki  (supplier of updated ahven 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: SHA1

Format: 1.8
Date: Mon, 11 Jul 2016 09:23:47 +0200
Source: ahven
Binary: libahven26 libahven-dev
Architecture: source amd64
Version: 2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Reto Buerki 
Changed-By: Reto Buerki 
Description:
 libahven-dev - Unit test library for Ada (development)
 libahven26 - Unit test library for Ada
Closes: 830409
Changes:
 ahven (2.6-1) unstable; urgency=medium
 .
   * Adjust URL in watch file
   * Imported Upstream version 2.6
   * Transition to gnat-6 compiler (Closes: #830409)
   * Drop obsolete Conflicts/Replaces
   * Update binary package names
   * Switch Vcs-* URLs to HTTPS
   * Update to debhelper 9
   * Update to Standards-Version 3.9.8
   * Switch to comfignat build functionality
   * Rediff patches
   * Add link-with-shared autopkgtest
   * Drop explicit ahven-dbg package
Checksums-Sha1:
 f9fd317960f03951cca0374f9c8118d6293378c9 1941 ahven_2.6-1.dsc
 dc65e48200019a1e821ad8b894ef540ba96ef148 91792 ahven_2.6.orig.tar.xz
 d378af2c07586bb26fea343ac7a1df998a70a2cd 12312 ahven_2.6-1.debian.tar.xz
 81e8934c4b9e8cbe268dd1955a7aa36fa6f7c8f1 125058 libahven-dev_2.6-1_amd64.deb
 a9cdc153fc5cd2a7d619478644019acaf89d62b9 123922 
libahven26-dbgsym_2.6-1_amd64.deb
 f41cfdfb1af97f3659a84e8d65ac3e6804e75e49 74580 libahven26_2.6-1_amd64.deb
Checksums-Sha256:
 388fcf2c0d14eff905ff47515568bb24effd775066734e117ac94f9c1de8ee7f 1941 
ahven_2.6-1.dsc
 b779dff7589e7b7c0da72fd659f788bd0f76fea96a23ae5e018c25b39b9a5210 91792 
ahven_2.6.orig.tar.xz
 be891a533a070e29a01986d5f81db8e508355ab89712e488e12ccd1387cdf2f7 12312 

Bug#830355: marked as done (libanyevent-http-perl: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 16:32:37 +
with message-id 
and subject line Bug#830355: fixed in libanyevent-http-perl 2.22-2
has caused the Debian Bug report #830355,
regarding libanyevent-http-perl: accesses the internet during build
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.)


-- 
830355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libanyevent-http-perl
Version: 2.22-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst libanyevent-http-perl builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 7c34bbfc36ec.49868 > dnscache.uct.ac.za.domain: 8255+ A? 
nonexistant.invalid. (37)
  00:00:00.000161 IP 7c34bbfc36ec.49868 > dnscache.uct.ac.za.domain: 25298+ 
? nonexistant.invalid. (37)
  00:00:00.005790 IP dnscache.uct.ac.za.domain > 7c34bbfc36ec.49868: 8255 
NXDomain 0/1/0 (112)
  00:00:00.006054 IP dnscache.uct.ac.za.domain > 7c34bbfc36ec.49868: 25298 
NXDomain 0/1/0 (112)
  00:00:00.006220 IP 7c34bbfc36ec.49868 > dnscache.uct.ac.za.domain: 4263+ A? 
nonexistant.invalid.uct.ac.za. (47)
  00:00:00.006522 IP 7c34bbfc36ec.49868 > dnscache.uct.ac.za.domain: 42908+ 
? nonexistant.invalid.uct.ac.za. (47)

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


libanyevent-http-perl.2.22-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libanyevent-http-perl
Source-Version: 2.22-2

We believe that the bug you reported is fixed in the latest version of
libanyevent-http-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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libanyevent-http-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: SHA512

Format: 1.8
Date: Fri, 15 Jul 2016 16:31:22 +0200
Source: libanyevent-http-perl
Binary: libanyevent-http-perl
Architecture: source
Version: 2.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 830355
Description: 
 libanyevent-http-perl - simple non-blocking HTTP/HTTPS client
Changes:
 libanyevent-http-perl (2.22-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Don't run tests which try to connect to the internet.
 Thanks to Chris Lamb for the bug report. (Closes: #830355)
   * Drop unneeded version constraint from libanyevent-perl (build)
 dependency.
   * Bump debhelper compatibility level to 9.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 c73623aaa60bfe0d6d22fedd78ee94137f507aae 2316 libanyevent-http-perl_2.22-2.dsc
 c15933d315393c8f92a66ded1b51e28702a6ca06 3236 
libanyevent-http-perl_2.22-2.debian.tar.xz
Checksums-Sha256: 
 fe22dc4a9e99ea5b25dcae98774e5b1a41f8ecc39ffdd1d3f8d3860fd9513ebb 2316 
libanyevent-http-perl_2.22-2.dsc
 4d8cb4cc680209cbfe04e8c7a01c2d92693fad547eb0cf8b42898c1c2715d6b1 3236 
libanyevent-http-perl_2.22-2.debian.tar.xz
Files: 
 8e127d13e7c78782be2579bd61567ff4 2316 perl optional 
libanyevent-http-perl_2.22-2.dsc
 55d3ad800416b965914844e2a3094bc3 3236 perl optional 
libanyevent-http-perl_2.22-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXiPP5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG1/cQALtldGuNAI2CvfZVk0yZhjq5
RguGErsvKgp9adUK4YDqCy8ssBBdraw7m9EgCtQ5Cbhgi5pDaEuw346op3KwPt+Y
jf6dUreSXaPiUsrwAIlncZvKM+3DZQVEyuAE60GVTo0ohRekP6/8f8dI/9gYW0sL

Bug#831191: marked as done (libdap: FTBFS with GCC 6: dds.yy:265:15: error: reference to 'array' is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 16:33:17 +
with message-id 
and subject line Bug#831191: fixed in libdap 3.15.1-8
has caused the Debian Bug report #831191,
regarding libdap: FTBFS with GCC 6: dds.yy:265:15: error: reference to 'array' 
is ambiguous
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.)


-- 
831191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdap
Version: 3.15.1-7
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):
> /bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
> -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -Wcast-align  
> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> libparsers_la-dds.tab.lo `test -f 'dds.tab.cc' || echo './'`dds.tab.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -W -Wcast-align -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -c dds.tab.cc  -fPIC -DPIC -o 
> .libs/libparsers_la-dds.tab.o
> dds.yy: In function 'int ddsparse(libdap::parser_arg*)':
> dds.yy:265:15: error: reference to 'array' is ambiguous
> part = array;
>^
> In file included from BaseType.h:55:0,
>  from Byte.h:44,
>  from dds.yy:57:
> Type.h:50:5: note: candidates are: libdap::Part array
>  array,
>  ^
> In file included from /usr/include/c++/6/tuple:39:0,
>  from /usr/include/c++/6/bits/stl_map.h:63,
>  from /usr/include/c++/6/map:61,
>  from Keywords2.h:30,
>  from DDS.h:66,
>  from Vector.h:43,
>  from Array.h:48,
>  from dds.yy:66:
> /usr/include/c++/6/array:90:12: note: template long unsigned int _Nm> struct std::array
>  struct array
> ^
> make[4]: *** [libparsers_la-dds.tab.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/libdap_3.15.1-7_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: libdap
Source-Version: 3.15.1-8

We believe that the bug you reported is fixed in the latest version of
libdap, 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.
Alastair McKinstry  (supplier of updated libdap 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, 15 Jul 2016 10:25:23 +0100
Source: libdap
Binary: libdap17v5 libdapclient6v5 libdapserver7v5 libdap-bin libdap-dev 
libdap-doc
Architecture: source amd64 all
Version: 3.15.1-8
Distribution: sid
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libdap-bin - Binaries for the  libdap Data Access Protocol library
 libdap-dev - Development files (headers and static libraries) for libdap
 libdap-doc - Documentation for the libdap Data Access Protocol library
 libdap17v5 - Open-source Project for a Network Data Access Protocol library
 libdapclient6v5 - Client library for the Network Data Access Protocol
 libdapserver7v5 - Server library for the Network 

Bug#821412: marked as done (libnet-rblclient-perl: Net::DNS 1.01 breaks Net::RBLClient)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 16:35:32 +
with message-id 
and subject line Bug#821412: fixed in libnet-rblclient-perl 0.5-3
has caused the Debian Bug report #821412,
regarding libnet-rblclient-perl: Net::DNS 1.01 breaks Net::RBLClient
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.)


-- 
821412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-rblclient-perl
Version: 0.5-2
Severity: grave
Tags: upstream
Justification: renders package unusable

Net::DNS 1.01 requires setting RD (recursion desired) bit in DNS queries.

See the spamassassin bug below for more detailed description and fixes:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7223

Adding the two lines in mk_packet sub fixes the problem

$packet->header->rd(1);
...
$txt_packet->header->rd(1);



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

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

Versions of packages libnet-rblclient-perl depends on:
ii  libnet-dns-perl  1.05-1
ii  perl 5.22.1-9

libnet-rblclient-perl recommends no packages.

libnet-rblclient-perl suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: libnet-rblclient-perl
Source-Version: 0.5-3

We believe that the bug you reported is fixed in the latest version of
libnet-rblclient-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 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnet-rblclient-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: SHA512

Format: 1.8
Date: Fri, 15 Jul 2016 16:10:30 +0200
Source: libnet-rblclient-perl
Binary: libnet-rblclient-perl
Architecture: source
Version: 0.5-3
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 578878 821412
Description: 
 libnet-rblclient-perl - module to query multiple Realtime Blackhole Lists in 
parallel
Changes:
 libnet-rblclient-perl (0.5-3) unstable; urgency=low
 .
   [ gregor herrmann ]
   * debian/control: Changed: Switched Vcs-Browser field to ViewSVN
 (source stanza).
 .
   [ Rene Mayorga ]
   * Email change: Rene Mayorga -> rmayo...@debian.org
 .
   [ gregor herrmann ]
   * Email change: gregor herrmann -> gre...@debian.org
 .
   [ Fabrizio Regalli ]
   * Bump to 3.9.2 Standard-Version.
   * Switch to DEP5 license format.
   * Add myself to Uploaders.
   * Switch d/compat to 8.
   * Build-Depends: switch to debhelper (>= 8).
 .
   [ Ansgar Burchardt ]
   * debian/control: Convert Vcs-* fields to Git.
 .
   [ Salvatore Bonaccorso ]
   * debian/copyright: Replace DEP5 Format-Specification URL from
 svn.debian.org to anonscm.debian.org URL.
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
   * Change search.cpan.org based URIs to metacpan.org based URIs
 .
   [ Axel Beckert ]
   * debian/copyright: migrate pre-1.0 format to 1.0 using "cme fix dpkg-
 copyright"
   * Fix typo in Homepage header (Thanks DUCK!)
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Mark package as autopkgtest-able.
   * Declare compliance with Debian Policy 3.9.8.
   * Switch to source format "3.0 (quilt)".
   * Bump debhelper compatibility level to 9.
   * Add patch to set RD bit for Net::DNS 1.01 compatibility.
 Thanks to Andrzej A. Filip for the bug report and the patch sketch.
 (Closes: #821412)
   * Add runtime dependency on libnet-dns-perl.
   * Mention module name 

Bug#830275: marked as done (libgravatar-url-perl: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 16:34:22 +
with message-id 
and subject line Bug#830275: fixed in libgravatar-url-perl 1.06-3
has caused the Debian Bug report #830275,
regarding libgravatar-url-perl: accesses the internet during build
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.)


-- 
830275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgravatar-url-perl
Version: 1.06-2
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst libgravatar-url-perl builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 303fab90c7aa.44254 > dnscache.uct.ac.za.domain: 36711+ 
[1au] SRV? _avatars._tcp.wherever.whichever. (61)
  00:00:00.036493 IP dnscache.uct.ac.za.domain > 303fab90c7aa.44254: 36711 
NXDomain$ 0/6/1 (667)
  00:00:00.062950 IP 303fab90c7aa.58571 > dnscache.uct.ac.za.domain: 46657+ 
[1au] SRV? _avatars-sec._tcp.wherever.whichever. (65)
  00:00:00.136896 IP dnscache.uct.ac.za.domain > 303fab90c7aa.58571: 46657 
NXDomain$ 0/6/1 (671)
  00:00:00.138127 IP 303fab90c7aa.58785 > dnscache.uct.ac.za.domain: 52120+ 
[1au] SRV? _avatars._tcp.wherever.whichever. (61)
  00:00:00.166401 IP dnscache.uct.ac.za.domain > 303fab90c7aa.58785: 52120 
NXDomain$ 0/6/1 (667)

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


libgravatar-url-perl.1.06-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libgravatar-url-perl
Source-Version: 1.06-3

We believe that the bug you reported is fixed in the latest version of
libgravatar-url-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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libgravatar-url-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: SHA512

Format: 1.8
Date: Fri, 15 Jul 2016 17:24:36 +0200
Source: libgravatar-url-perl
Binary: libgravatar-url-perl
Architecture: source
Version: 1.06-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 830275
Description: 
 libgravatar-url-perl - Perl interface to make URLs for Gravatars from an email 
address
Changes:
 libgravatar-url-perl (1.06-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Skip test which tries to use the internet.
 Thanks to Chris Lamb for the bug report. (Closes: #830275)
   * Bump debhelper compatibility level to 9.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 e3388b6042a2687925c05b35ba1fed9fbe45c918 2368 libgravatar-url-perl_1.06-3.dsc
 ccbd05e14d26640b0e3f218a9a5039e98c09bc8b 2852 
libgravatar-url-perl_1.06-3.debian.tar.xz
Checksums-Sha256: 
 848a60229af87dd943e66a8d74416fc0c54ef0679bdfc149079f0511da78979e 2368 
libgravatar-url-perl_1.06-3.dsc
 15fd9b0d1d7b3b5ab1d4a190ba7dbad3bfafd99e13197c5688b5e48178ac8519 2852 
libgravatar-url-perl_1.06-3.debian.tar.xz
Files: 
 3b95d24ccc8bd077b98d2c3cd8ee7f94 2368 perl optional 
libgravatar-url-perl_1.06-3.dsc
 e7d07e385f4265594997db9f594d076d 2852 perl optional 
libgravatar-url-perl_1.06-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXiQB7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG0uwP/09cfyy97+GoRCLbebC9oWUj
+o7Ocnu4NU6I+MnYo8vURHQaIdVRJwIYsN2kP/zdC2biLCxu8cPZH5jN2I1kDZD1
+Zls+S1g7ZEHkqf0vYKfQbxQgs5xL/FTZsw3KzroOtLI6Om9qssuzCdtA7vi9Y6n
ce2Y7wZqL3XgXg5NhqFAawS8+7c4UXy6tQI0DXDvgO/DGzkhrgOYdm9zmNxIK8Ak

Bug#831406: yorick: FTBFS: dpkg-shlibdeps: error: no dependency information found for /usr/lib/libmpich.so.12 (used by debian/yorick-mpy-mpich2/usr/lib/yorick/bin/mpy.mpich2)

[Chris Lamb]

Source: yorick
Version: 2.2.04+dfsg1-5
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,

yorick fails to build from source in unstable/amd64:

  [..]

  "manual/yorick_prt.html"
  mkdir -p ../../build/doc/images
  cp -p images/*.* ../../build/doc//images/
  mkdir -p ../../build/doc/
  cp skull.css style.css ../../build/doc/
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160715182504.pdcokDfkyE.yorick/yorick-2.2.04+dfsg1/doc/html'
  cp doc/html/packinfo.txt build/00yorick.packinfo
  cp doc/html/keywords.txt build/00yorick.keywords
  cp doc/html/aliases.txt build/00yorick.aliases
  find build/doc/manual -name "*.html" -not -name yorick_prt.html | xargs sed 
-e 's|^http://dhmunro.github.io/yorick-doc/;>Web HomeGetting StartedManualPackagesQuick 
Reference|' -e 's||&|' -i
  sed 's|yorick_1.html|index.html|' -i build/doc/*.html build/doc/*/*.html
  touch build-indep-stamp
   fakeroot debian/rules binary
  dh_testdir
  xvfb-run relocate/bin/yorick -batch testfull.i
   Begin Yorick parser test...
   Test 17x10x10 binary operators...
   Test unary operators...
   Test array manipulation functions...
   Test struct instancing and indexing...
   Test range functions...
   Test math functions...
   Test informational functions...
   Test func declarations...
   Test binary I/O functions...
   Test binary I/O to netCDF...
   Test ASCII I/O functions...
   Test string manipulation functions...
   Test list functions...
   Test catch function...
  End of Yorick parser test, 0 goofs
   begin string manipulation test...
  end string manipulation test, 0 goofs
   PASSED oxy test1
   PASSED oxy test2
   PASSED oxy test3
   PASSED closure called with no arguments
   PASSED all closure tests
   PASSED alternate closure tests
   PASSED oxy friend test
   PASSED oxy sibling test
   
   Zeroth test is pdtest files:
   Testing sun_primitives db1 write...
   Testing dec_primitives db1 write...
   Testing cray_primitives db1 write...
   Testing mac_primitives db1 write...
   Testing macl_primitives db1 write...
   Testing pc_primitives db1 write...
   Testing sun3_primitives db1 write...
   Testing vax_primitives db1 write...
   Testing vaxg_primitives db1 write...
   Testing xdr_primitives db1 write...
   Testing sun_primitives db1 write w/PDB-style pointers...
   Testing dec_primitives db1 write w/PDB-style pointers...
   Testing cray_primitives db1 write w/PDB-style pointers...
   Testing native db1 write...
   
 First test is to write flat files:
   Write using native formats
   Write using DEC primitive formats
   Write using Sun primitive formats
   Write using Cray primitive formats
   
Second test is to write files with pointers:
   Write using native formats
   Write using DEC primitive formats
   Write using Sun primitive formats
   Write using Cray primitive formats
   
Third test is to update pointered files with flat data:
   Update using native formats
   Update using DEC primitive formats
   Update using Sun primitive formats
   Update using Cray primitive formats
   
Fourth test is exhaustive check of other primitive formats:
   Testing Sun format
   Testing i86 format
   Testing alpha format
   Testing sgi64 format
   Testing DEC format
   Testing Cray format
   Testing XDR format
   Testing Mac format
   Testing Mac long-double format
   Testing IBM PC format
   Testing VAX format
   Testing VAX G-double format
   Testing Sun-3/Sun-2 format
   Testing native format
 Timing Category CPU sec  System secWall sec
  Time to write/test all formats   0.004   0.000   0.007
   
Fifth test is check of Contents Log machinery:
   Contents Log -- testing Sun format
   Contents Log -- testing DEC format
   Contents Log -- testing Cray format
   Contents Log -- testing VAX format
   Contents Log -- testing native format
   Non-PDB Contents Log -- testing Sun format
   Non-PDB Contents Log -- testing DEC format
   Non-PDB Contents Log -- testing Cray format
   Non-PDB Contents Log -- testing VAX format
   Non-PDB Contents Log -- testing native format
   
Sixth test is flat history files (be patient):
   History -- testing Sun format
   History -- testing DEC format
   History -- testing Cray format
   History -- testing VAX format
   History -- testing native format
 Timing Category CPU sec  System secWall sec
 Time to write history files   0.060   0.000   0.063
   
Seventh test is a pointered history file:
   
Eighth test is vsave in-memory files:
   
Ninth test is vpack in-memory files:
   
  Shock tracker timing test:
 Timing Category CPU sec  System secWall sec
   Time per pass   0.002   0.000   0.002
  Total time   0.036   0.000   0.036
   
  Escape factor timing test:
  

Bug#830744: marked as done (flint: FTBFS on *-i386: testsuite timeout)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 16:23:08 +
with message-id 
and subject line Bug#830744: fixed in flint 2.5.2-8
has caused the Debian Bug report #830744,
regarding flint: FTBFS on *-i386: testsuite timeout
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.)


-- 
830744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flint
Version: 2.5.2-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

flint FTBFS on *-i386, the testsuite hangs and the build gets terminated
after it reaches the inactivity timeout.

https://buildd.debian.org/status/fetch.php?pkg=flint=i386=2.5.2-7=1467982677

make[3]: Entering directory '/«PKGBUILDDIR»/d_mat'
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-mul_classical.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-mul_classical 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-mul_classical.d -MT "../build/d_mat/test/t-mul_classical" 
-MT "../build/d_mat/test/t-mul_classical.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-qr.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-qr 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-qr.d -MT 
"../build/d_mat/test/t-qr" -MT "../build/d_mat/test/t-qr.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-is_empty.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-is_empty 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-is_empty.d 
-MT "../build/d_mat/test/t-is_empty" -MT "../build/d_mat/test/t-is_empty.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-is_square.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-is_square 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-is_square.d -MT "../build/d_mat/test/t-is_square" -MT 
"../build/d_mat/test/t-is_square.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-init_clear.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-init_clear 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-init_clear.d -MT "../build/d_mat/test/t-init_clear" -MT 
"../build/d_mat/test/t-init_clear.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-zero.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-zero 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-zero.d -MT 
"../build/d_mat/test/t-zero" -MT "../build/d_mat/test/t-zero.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-entry.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-entry 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-entry.d 
-MT "../build/d_mat/test/t-entry" -MT "../build/d_mat/test/t-entry.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-equal.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-equal 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-equal.d 
-MT "../build/d_mat/test/t-equal" -MT "../build/d_mat/test/t-equal.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-one.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-one 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib 

Bug#831403: xmlgraphics-commons: FTBFS: Could not initialize class org.mockito.Mockito

[Chris Lamb]

Source: xmlgraphics-commons
Version: 2.1-1
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,

xmlgraphics-commons fails to build from source in unstable/amd64:

  [..]

  [junit] 
  [junit] - Standard Output ---
  [junit] Skipping endianness test for ImageIO-based TIFF writer because 
JAI ImageIO Tools is not available!
  [junit] Skipping endianness test for ImageIO-based TIFF writer because 
JAI ImageIO Tools is not available!
  [junit] -  ---
  [junit] Testsuite: 
org.apache.xmlgraphics.io.TempResourceURIGeneratorTestCase
  [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.071 sec
  [junit] 
  [junit] Testsuite: org.apache.xmlgraphics.io.URIResolverAdapterTestCase
  [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 
0.087 sec
  [junit] 
  [junit] Testcase: 
testCatalogResolver(org.apache.xmlgraphics.io.URIResolverAdapterTestCase):SKIPPED:
 Literally no idea why this doesn't work... Gonna look at the catalog resolver 
source
  [junit] Testcase: 
testCatalogResolverInAdapter(org.apache.xmlgraphics.io.URIResolverAdapterTestCase):SKIPPED:
 Literally no idea why this doesn't work... Gonna look at the catalog resolver 
source
  [junit] Testsuite: org.apache.xmlgraphics.io.XmlSourceUtilTestCase
  [junit] Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed: 
0.113 sec
  [junit] 
  [junit] Testcase: 
testCloseQuietlyStreamSource(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):  
Caused an ERROR
  [junit] net/sf/cglib/proxy/Callback
  [junit] java.lang.NoClassDefFoundError: net/sf/cglib/proxy/Callback
  [junit]   at java.lang.Class.forName0(Native Method)
  [junit]   at java.lang.Class.forName(Class.java:264)
  [junit]   at 
org.mockito.internal.configuration.plugins.PluginLoader.loadPlugin(PluginLoader.java:33)
  [junit]   at 
org.mockito.internal.configuration.plugins.PluginRegistry.(PluginRegistry.java:13)
  [junit]   at 
org.mockito.internal.configuration.plugins.Plugins.(Plugins.java:11)
  [junit]   at org.mockito.internal.util.MockUtil.(MockUtil.java:24)
  [junit]   at org.mockito.internal.MockitoCore.(MockitoCore.java:44)
  [junit]   at org.mockito.Mockito.(Mockito.java:975)
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] Caused by: java.lang.ClassNotFoundException: 
net.sf.cglib.proxy.Callback
  [junit]   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
  [junit]   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
  [junit]   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
  [junit]   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
  [junit] 
  [junit] 
  [junit] Testcase: 
testNeedInputStreamFailureCaseStreamImage(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):
 Caused an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] 
  [junit] 
  [junit] Testcase: 
testHasInputStream(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):Caused 
an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] 
  [junit] 
  [junit] Testcase: 
testCloseQuietlyImageSource(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):   
Caused an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] 
  [junit] 
  [junit] Testcase: 
testCloseQuietlySaxSource(org.apache.xmlgraphics.io.XmlSourceUtilTestCase): 
Caused an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 
org.apache.xmlgraphics.io.XmlSourceUtilTestCase.setUp(XmlSourceUtilTestCase.java:71)
  [junit] 
  [junit] 
  [junit] Testcase: 
testNeedInputStreamFailureCaseSAXSource(org.apache.xmlgraphics.io.XmlSourceUtilTestCase):
   Caused an ERROR
  [junit] Could not initialize class org.mockito.Mockito
  [junit] java.lang.NoClassDefFoundError: Could not initialize class 
org.mockito.Mockito
  [junit]   at 

Bug#830360: marked as done (golang-github-kimor79-gollectd: FTBFS: build-dependency not installable: golang-github-stretchr-testify)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 16:24:21 +
with message-id 
and subject line Bug#830360: fixed in golang-github-kimor79-gollectd 1.0.0-2
has caused the Debian Bug report #830360,
regarding golang-github-kimor79-gollectd: FTBFS: build-dependency not 
installable: golang-github-stretchr-testify
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.)


-- 
830360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-kimor79-gollectd
Version: 1.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 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):
> ┌──┐
> │ Install golang-github-kimor79-gollectd build dependencies (apt-based 
> resolver) │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-golang-github-kimor79-gollectd-dummy : Depends: 
> golang-github-stretchr-testify but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/golang-github-kimor79-gollectd_1.0.0-1_unstable_reb.normal.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: golang-github-kimor79-gollectd
Source-Version: 1.0.0-2

We believe that the bug you reported is fixed in the latest version of
golang-github-kimor79-gollectd, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated 
golang-github-kimor79-gollectd 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: Fri, 15 Jul 2016 10:48:17 -0400
Source: golang-github-kimor79-gollectd
Binary: golang-github-kimor79-gollectd-dev
Architecture: source all
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 golang-github-kimor79-gollectd-dev - go parser for the collectd binary protocol
Closes: 830360
Changes:
 golang-github-kimor79-gollectd (1.0.0-2) unstable; urgency=medium
 .
   * Update golang-github-stretchr-testify-dev dependency. (Closes: #830360)
   * Bump Standards-Version to 3.9.8.
Checksums-Sha1:
 2a8df5c5d788d4d34fa92a3fea37fef78377f47b 2243 
golang-github-kimor79-gollectd_1.0.0-2.dsc
 bccc97bfced33f1e495a63470e0ebc373048adba 2196 
golang-github-kimor79-gollectd_1.0.0-2.debian.tar.xz
 09a70dbf80ebc4e381c3472a944c2d6f13cb8ef6 9918 
golang-github-kimor79-gollectd-dev_1.0.0-2_all.deb
Checksums-Sha256:
 7160bcb283f3003ba0109fc75fbbd57621aec24d1ef66e5906fff5eca647062c 2243 
golang-github-kimor79-gollectd_1.0.0-2.dsc
 7a6a57f77d71d914f40bb52b372c402efe3312b4a2909d2678ba66e127fabf15 2196 
golang-github-kimor79-gollectd_1.0.0-2.debian.tar.xz
 80d4a1fac98b906921a611e8236b41dee5daefa660bb4cc272e6863f881fdce6 9918 
golang-github-kimor79-gollectd-dev_1.0.0-2_all.deb
Files:
 58ddbf6c85fb0a2c52c05251d1835dbc 

Bug#828726: marked as done (cdbs: Please readd DEB_PYTHON(3)_MODULE_PACKAGES variable)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 18:06:26 +0200
with message-id <146859878680.9885.2620308283224677...@auryn.jones.dk>
and subject line Re: [Build-common-hackers] Bug#828726: cdbs: Please readd 
DEB_PYTHON(3)_MODULE_PACKAGES variable
has caused the Debian Bug report #828726,
regarding cdbs: Please readd DEB_PYTHON(3)_MODULE_PACKAGES variable
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.)


-- 
828726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdbs
Version: 0.4.142
Severity: serious

Hi,

Could you please readd DEB_PYTHON_MODULE_PACKAGES and
DEB_PYTHON3_MODULE_PACKAGES, this is definitely used in the archive,
see: https://codesearch.debian.net/results/DEB_PYTHON3%3F_MODULE_PACKAGES/page_0

It's used by packages that need dh_python2/3 to be called even if the
package name is not starting with python-

Regards,

Laurent Bigonville

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

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

cdbs depends on no packages.

Versions of packages cdbs recommends:
ii  autotools-dev  20160430.1

Versions of packages cdbs suggests:
ii  devscripts  2.16.5

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Lauent,

Quoting Laurent Bigonville (2016-06-27 11:20:06)
> Could you please readd DEB_PYTHON_MODULE_PACKAGES and
> DEB_PYTHON3_MODULE_PACKAGES, this is definitely used in the archive,
> see: 
> https://codesearch.debian.net/results/DEB_PYTHON3%3F_MODULE_PACKAGES/page_0
> 
> It's used by packages that need dh_python2/3 to be called even if the
> package name is not starting with python-

Thanks for reporting - I believe however that there is no bug here:

These variables was recently dropped:

  DEB_PYTHON_MODULE_PACKAGE
  DEB_PYTHON_MODULE_PACKAGES

These variables are still in use, however:

  DEB_PYTHON2_MODULE_PACKAGES
  DEB_PYTHON3_MODULE_PACKAGES

Current CDBS _is_ buggy, but this is not one of them.

Please include as a minimum the *symptoms* when reporting a bug. 
Suggestions for a fix (or workaround) is appreciated too, but don't 
forget to define the bug. :-)

(I could be wrong: If so then please reopen - and point me to some 
actual breakage)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


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

Bug#831402: gtk+2.0: FTBFS due to missing build-arch target

[Samuel Thibault]

Source: gtk+2.0
Version: 2.24.30-2
Severity: serious
Tags: patch
Justification: FTBFS

Hello,

gtk+2.0 currently FTBFS on buildds due to the missing build-arch target.
The attached patch fixes it.

Samuel

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- 
Samuel
>Ever heard of .cshrc?
That's a city in Bosnia.  Right?
(Discussion in comp.os.linux.misc on the intuitiveness of commands.)
--- debian/rules.orig   2016-07-15 17:41:35.317949840 +0200
+++ debian/rules2016-07-15 17:43:50.146555217 +0200
@@ -188,7 +188,9 @@
$(MAKE) $(PARALLEL_FLAGS) -C $(builddir)
touch $@
 
-build: $(addprefix $(STAMP_DIR)/build-stamp-, $(FLAVORS))
+build: build-arch
+build-arch: $(addprefix $(STAMP_DIR)/build-stamp-, $(FLAVORS))
+build-indep: $(addprefix $(STAMP_DIR)/build-stamp-, $(FLAVORS))
 
 $(STAMP_DIR)/check-stamp-%: $(STAMP_DIR)/build-stamp-%
dh_testdir

Processed: your mail

[Debian Bug Tracking System]

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

> found 831181 2.0.1-0.2
Bug #831181 [src:odin] odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: 
call of overloaded 'sqrt(funcMode&)' is ambiguous
Marked as found in versions odin/2.0.1-0.2.
> --
Stopping processing here.

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

Bug#830275: Pending fixes for bugs in the libgravatar-url-perl package

[pkg-perl-maintainers]

tag 830275 + pending
thanks

Some bugs in the libgravatar-url-perl package are closed in revision
3e496ad9fb2701ac28e76a06e4c835a481766a59 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libgravatar-url-perl.git/commit/?id=3e496ad

Commit message:

Skip test which tries to use the internet.

Thanks: Chris Lamb for the bug report.
Closes: #830275

Processed: Pending fixes for bugs in the libgravatar-url-perl package

[Debian Bug Tracking System]

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

> tag 830275 + pending
Bug #830275 [src:libgravatar-url-perl] libgravatar-url-perl: accesses the 
internet during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: bug 830468 is forwarded to https://github.com/thejerf/suture/issues/16

[Debian Bug Tracking System]

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

> forwarded 830468 https://github.com/thejerf/suture/issues/16
Bug #830468 [src:golang-github-thejerf-suture] golang-github-thejerf-suture: 
FTBFS: dh_auto_test: go test -v github.com/thejerf/suture returned exit code 1
Set Bug forwarded-to-address to 'https://github.com/thejerf/suture/issues/16'.
> thanks
Stopping processing here.

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

Bug#830355: Pending fixes for bugs in the libanyevent-http-perl package

[pkg-perl-maintainers]

tag 830355 + pending
thanks

Some bugs in the libanyevent-http-perl package are closed in revision
03145074017c57a2977b7e88e2d8fae2a2f4a5c6 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libanyevent-http-perl.git/commit/?id=0314507

Commit message:

Don't run tests which try to connect to the internet.

Thanks: Chris Lamb for the bug report.
Closes: #830355

Bug#827905: Character U+2028 can yield file corruption when edited in xterm

[Sven Joachim]

On 2016-07-15 05:02 -0400, Thomas Dickey wrote:

> On Thu, Jul 14, 2016 at 07:27:52PM +0200, Sven Joachim wrote:
>> On 2016-07-13 18:24 -0700, Vincent Lefevre wrote:
>> 
>> > On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote:
>> >> I don't see the behavior which is described, and haven't seen any
>> >> suitable justification for marking this as a "grave" issue, rather
>> >> than "normal".  Keep in mind that this is a rarely used line-break
>> >> character.
>> >
>> > This is not common, but this was sufficient to *silently* corrupt one
>> > of my files (what makes things really worse is that the corruption
>> > doesn't seem to appear immediately, and one notices it when it may be
>> > too late).
>> >
>> >> What I see on the screen is a box-outline for the nonprintable
>> >> character (no space).
>> >
>> > Could this depend on some library version or on the font?
>> 
>> On the latter.  With the default font I see no corruption, but with the
>> 9x15 font, for instance.  See the attached screenshot.
>
> 9x15 is an ISO-8859-1 font, and can't show U+2028

Surely it should just replace it with a space then, like for other
non-latin characters?  Besides, the problem also shows up with
terminus-18 which is an ISO-10646 font.

Cheers,
   Sven

Processed: Pending fixes for bugs in the libanyevent-http-perl package

[Debian Bug Tracking System]

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

> tag 830355 + pending
Bug #830355 [src:libanyevent-http-perl] libanyevent-http-perl: accesses the 
internet during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828926: [Freewx-maint] Bug#828926: wxwidgets3.0: FTBFS with gcc-6 and glibc 2.23

[Olly Betts]

On Wed, Jun 29, 2016 at 09:41:01AM -0400, Scott Talbert wrote:
> On Tue, 28 Jun 2016, Daniel Schepler wrote:
> 
> >../src/stc/scintilla/src/Editor.cxx: In function 'bool Close(Point, Point)':
> >../src/stc/scintilla/src/Editor.cxx:5844:23: error: call of overloaded
> >'abs(XYPOSITION)' is ambiguous
> > if (abs(pt1.x - pt2.x) > 3)
> >  ^
> 
> This upstream commit should fix it:
> https://github.com/wxWidgets/wxWidgets/commit/73e9e18ea09caac50237def0d9728a213c02

Looks good.

I'm currently travelling with a machine too slow to comfortably build wx
on, but if someone wants to NMU that's cool with me.  Otherwise I'll
likely sort it out in a couple of weeks time.

Cheers,
Olly

Bug#821412: Pending fixes for bugs in the libnet-rblclient-perl package

[pkg-perl-maintainers]

tag 821412 + pending
thanks

Some bugs in the libnet-rblclient-perl package are closed in revision
a6c967900ff883b087af65bbc984fedd76f8bcd6 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-rblclient-perl.git/commit/?id=a6c9679

Commit message:

Add patch to set RD bit for Net::DNS 1.01 compatibility.

Thanks: Andrzej A. Filip for the bug report and the patch sketch.
Closes: #821412

Processed: Pending fixes for bugs in the libnet-rblclient-perl package

[Debian Bug Tracking System]

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

> tag 821412 + pending
Bug #821412 [libnet-rblclient-perl] libnet-rblclient-perl: Net::DNS 1.01 breaks 
Net::RBLClient
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831392: rant: cannot load such file -- rant/rantlib (LoadError)

[Christian Hofstaedtler]

Package: rant
Version: 0.5.8-8
Severity: grave
Tags: sid stretch jessie

Dear Maintainer,

when running "rant" from a shell, it fails to start:

% rant
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot 
load such file -- rant/rantlib (LoadError)
  from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from /usr/bin/rant:11:in `'

This also happens in jessie.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#831180: marked as done (iperf: FTBFS with GCC 6: cpp_type_traits.h:205:12: error: redefinition of 'struct std::__is_integer')

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 12:51:03 +
with message-id 
and subject line Bug#831180: fixed in iperf 2.0.9+dfsg1-1
has caused the Debian Bug report #831180,
regarding iperf: FTBFS with GCC 6: cpp_type_traits.h:205:12: error: 
redefinition of 'struct std::__is_integer'
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.)


-- 
831180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iperf
Version: 2.0.5+dfsg1-2
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):
> g++ -DHAVE_CONFIG_H -I. -I. -I..  -I../include -I../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o delay.o delay.cpp
> In file included from /usr/include/c++/6/cmath:42:0,
>  from /usr/include/c++/6/math.h:36,
>  from ../include/headers.h:85,
>  from ../include/Timestamp.hpp:63,
>  from delay.cpp:53:
> /usr/include/c++/6/bits/cpp_type_traits.h:205:12: error: redefinition of 
> 'struct std::__is_integer'
>  struct __is_integer
> ^
> /usr/include/c++/6/bits/cpp_type_traits.h:138:12: error: previous definition 
> of 'struct std::__is_integer'
>  struct __is_integer
> ^~
> make[3]: *** [delay.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/iperf_2.0.5+dfsg1-2_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're 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: iperf
Source-Version: 2.0.9+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
iperf, 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.
Roberto Lumbreras  (supplier of updated iperf 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: SHA1

Format: 1.8
Date: Fri, 15 Jul 2016 13:05:06 +0200
Source: iperf
Binary: iperf
Architecture: source amd64
Version: 2.0.9+dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Roberto Lumbreras 
Changed-By: Roberto Lumbreras 
Description:
 iperf  - Internet Protocol bandwidth measuring tool
Closes: 831180
Changes:
 iperf (2.0.9+dfsg1-1) unstable; urgency=low
 .
   * New upstream version, including fix for FTBFS with gcc 6. (Closes: #831180)
   * Updated standards.
   * Updated homepage and watch file.
Checksums-Sha1:
 514a19f40331af86f9d50097aef68470481173d3 1749 iperf_2.0.9+dfsg1-1.dsc
 ae48e1277089289de56bbc234f32c37d3002cb64 272738 iperf_2.0.9+dfsg1.orig.tar.gz
 8c8cfdab1bcea72ba4c6bf9c6878464f6c1a5d14 47948 
iperf_2.0.9+dfsg1-1.debian.tar.xz
 b3a2325af2b50542ad452db3c134820f626bdce7 105496 
iperf-dbgsym_2.0.9+dfsg1-1_amd64.deb
 4c97c84cd9dbfb1477143fcd0b4868bf2981f3ad 57232 iperf_2.0.9+dfsg1-1_amd64.deb
Checksums-Sha256:
 d7a9e62e48dc4d62c3c718b794aa33f1726f0e6341d76ee5d411482a9de7ae72 1749 
iperf_2.0.9+dfsg1-1.dsc
 2a5a754c7cfd66610de1abfded77efae0abc73a085b3613ab2549a4fc4768ce9 272738 
iperf_2.0.9+dfsg1.orig.tar.gz
 4d8ca196db40a3aa564587cd1d25e6721f409d5dfa08e0e4828cb4fc881eec5f 47948 
iperf_2.0.9+dfsg1-1.debian.tar.xz
 52c55a7ac0b2c3cbe7f504f18329389b0b4dca5e5e5505d2c2bcc09a7053e26c 105496 

Bug#831150: marked as done (boinctui: FTBFS with GCC 6: src/infopanel.cpp:93:48: error: call of overloaded 'abs(double)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 12:33:34 +
with message-id 
and subject line Bug#831150: fixed in boinctui 2.4.1-1
has caused the Debian Bug report #831150,
regarding boinctui: FTBFS with GCC 6: src/infopanel.cpp:93:48: error: call of 
overloaded 'abs(double)' is ambiguous
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.)


-- 
831150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boinctui
Version: 2.4.0-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):
> g++ -c -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DENABLEMOUSE -DVERSION=2.4.0 
> -DPACKAGE_NAME=\"boinctui\" -DPACKAGE_TARNAME=\"boinctui\" 
> -DPACKAGE_VERSION=\"VERSION\" -DPACKAGE_STRING=\"boinctui\ VERSION\" 
> -DPACKAGE_BUGREPORT=\"BUG-REPORT-ADDRESS\" -DPACKAGE_URL=\"\" 
> -DHAVE_LIBNCURSESW=1 -DHAVE_LIBFORMW=1 -DHAVE_LIBPANELW=1 -DHAVE_LIBMENUW=1 
> -DHAVE_LIBEXPAT=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBGNUTLS_OPENSSL_=1 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_PTHREAD_H=1 -DHAVE_STRING_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STDIO_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_STDARG_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_ARPA_INET_H=1 -DHAVE_LOCALE_H=1 
> -DHAVE_MALLOC_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_NETDB_H=1 -DHAVE_SIGNAL_H=1 
> -DHAVE_CTYPE_H=1 -DHAVE_ALGORITHM=1 -DHAVE_STRING=1 -DHAVE_LIST=1 
> -DHAVE_VECTOR=1 -DHAVE_QUEUE=1 -DHAVE_STACK=1 -DHAVE_SSTREAM=1 
> -DHAVE_EXPAT_H=1 -DHAVE_GNUTLS_OPENSSL_H=1 -DHAVE_NCURSESW_CURSES_H=1 
> -DHAVE_NCURSESW_FORM_H=1 -DHAVE_NCURSESW_PANEL_H=1 -DHAVE__BOOL=1 
> -DHAVE_STDBOOL_H=1 -DLSTAT_FOLLOWS_SLASHED_SYMLINK=1 -DHAVE_STDLIB_H=1 
> -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DHAVE_MBLEN=1 
> -DHAVE_MEMSET=1 -DHAVE_SETLOCALE=1 -DHAVE_SOCKET=1 -DHAVE_STRDUP=1 
> -DHAVE_STRSTR=1 -o .obj/infopanel.o src/infopanel.cpp
> src/infopanel.cpp: In member function 'virtual void InfoPanel::refresh()':
> src/infopanel.cpp:93:48: error: call of overloaded 'abs(double)' is ambiguous
>  if ( (!compact)||(abs(usertotal - hosttotal) > 1) )
> ^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/bits/stl_algo.h:59,
>  from /usr/include/c++/6/algorithm:62,
>  from src/infopanel.cpp:19:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from src/infopanel.cpp:19:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int 
> std::abs(long long int)
>abs(long long __x) { return __builtin_llabs (__x); }
>^~~
> /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
>abs(long __i) { return __builtin_labs(__i); }
>^~~
> src/infopanel.cpp:100:44: error: call of overloaded 'abs(double)' is ambiguous
>  if ( (!compact)||(abs(useravg - hostavg) > 1) )
> ^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/bits/stl_algo.h:59,
>  from /usr/include/c++/6/algorithm:62,
>  from src/infopanel.cpp:19:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from src/infopanel.cpp:19:
> /usr/include/c++/6/cstdlib:185:3: note: 

Bug#830235: marked as done (Gem::LoadError: Could not find 'webrobots')

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 12:21:49 +
with message-id 
and subject line Bug#830235: fixed in ruby-webrobots 0.1.2-1
has caused the Debian Bug report #830235,
regarding Gem::LoadError: Could not find 'webrobots'
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.)


-- 
830235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-webrobots
Version: 0.1.1-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

% ruby -e 'gem "webrobots"'
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'webrobots' (>= 0) among 60 total gem(s) (Gem::LoadError)
[...]

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-webrobots
Source-Version: 0.1.2-1

We believe that the bug you reported is fixed in the latest version of
ruby-webrobots, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-webrobots 
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, 15 Jul 2016 08:56:31 -0300
Source: ruby-webrobots
Binary: ruby-webrobots
Architecture: source
Version: 0.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-webrobots - Library for creating robots.txt-aware web robots
Closes: 830235
Changes:
 ruby-webrobots (0.1.2-1) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Run wrap-and-sort on packaging files
 .
   [ Antonio Terceiro ]
   * New upstream release
 - Refresh patches
 - new build adds required Rubygems metadata (Closes: #830235)
   * Update packaging with a `dh-make-ruby -w` run
 - run test suite with debian/ruby-tests.rake; drop debian/ruby-tests.rb
Checksums-Sha1:
 ed7ea7003855cd1597a43349674a43e463e3f6c1 2105 ruby-webrobots_0.1.2-1.dsc
 a6465ed4398da1cb8656f450b45207f456f992fa 21231 ruby-webrobots_0.1.2.orig.tar.gz
 1393a206bfbde77adea69d7f42f312b6d15b4794 3244 
ruby-webrobots_0.1.2-1.debian.tar.xz
Checksums-Sha256:
 ec4375c5a1901ccabd5cc4b76ab331ecf1e954f34f38bc8bda412d6e5d57be8e 2105 
ruby-webrobots_0.1.2-1.dsc
 e967f8cf84c9a8c77e18e52c281cbacaab15263b7f561beaf29c65c6c84e9e62 21231 
ruby-webrobots_0.1.2.orig.tar.gz
 fab4ad9502abd99f6a318b06388a4072667e5fe927edaa39ad8ef6287c4b9cef 3244 
ruby-webrobots_0.1.2-1.debian.tar.xz
Files:
 d3fc67989200159714a15460c0766b85 2105 ruby optional ruby-webrobots_0.1.2-1.dsc
 b8c24315b061e42523991a337f7292e2 21231 ruby optional 
ruby-webrobots_0.1.2.orig.tar.gz
 c70c753435a449e4328f329e12774456 3244 ruby optional 
ruby-webrobots_0.1.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXiNEeAAoJEPwNsbvNRgveOd0P/jKE1u4GhhB4UQpJkV8yYsXG
aosNiUCVQDlWkF2g9ic6y8erSuCnmtZZ85WNy12/o0DvN+c4Ca4CgAwMETQBjMQX
qFuyEp45VWzhiVmoF2cXhMB3/g1TbMGIcQfBryJFVoMS+yHA1P6Q/Bt1SlSr8Fsr
NXAwC6CCyrnA3+uYQpOG5fob1kAE2oFJ02GFvqaEfXyIeBTqo8ZXMNyiMQU0k+LJ
QXfwprHm2PW08mErE4Fl02LK9jmjurdhMaFNOuKNDzFxc+bTMU4An0lEPj+qGSsJ
o+IGCFdJBUZZUT20xUu44ECSqQC4kIw7XCDkjKE5eIun14Ufz541IeSJkkM+qhut
KA+966TDskPrP5U6w6g02WW9rDmDGnprCZ8Pw4tP2vy8CC4ewNysedvjB4HS26Fs
CE+V3hYT47XHTV9dqRBfzMRjPBJ4gqHjUfUIk+aG+DpLCT4h8ynDMgOGtL4R5lMx
BPYDknb4xcG4we740sksZgWcMxQnb/o94XtJ3k6IrWQv1jjERHs7McgQ118aHf5e
n/o5Mik7ZMV+CWty4zWpAO2Ljp77TBQjJ5kJlwU4MViJKKaYMx7qJgI2pcw2oaYk
K/CcWQf9PrDRPYRz7+sfWGh/WqF1rtBgawBR4oFb3Ik1FtZZx0vp1haKLxEyQkW3
BfQfmxnf8bTsk9jAGcIx
=x+4e
-END PGP SIGNATURE End Message ---

Bug#831181: odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: call of overloaded 'sqrt(funcMode&)' is ambiguous

[Thies Jochimsen]

Hello,
the bug should be fixed in upstream now:
https://sourceforge.net/p/od1n/code/8688/tree//trunk/odin/odinseq/odinpulse.cpp?diff=8411

Best wishes, Thies (upstream maintainer of Odin)



On Thu, 14 Jul 2016 09:17:25 +0200 Lucas Nussbaum  wrote:
> Source: odin
> Version: 2.0.2-0.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):
> > /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H 
-I. -I../tjutils -I.. -I/«PKGBUILDDIR» -I/usr/include/qwt-qt4 
-I/usr/share/qt4/include/QtGui -I/usr/share/qt4/include/QtCore 
-I/usr/share/qt4/include -I. -I/usr/include/dcmtk 
-I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/ofstd 
-I/usr/include/vtk-6.3 -I/usr/include/nifti -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -fno-tree-vectorize -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
odinpulse.lo odinpulse.cpp
> > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../tjutils -I.. 
-I/«PKGBUILDDIR» -I/usr/include/qwt-qt4 -I/usr/share/qt4/include/QtGui 
-I/usr/share/qt4/include/QtCore -I/usr/share/qt4/include -I. 
-I/usr/include/dcmtk -I/usr/include/dcmtk/dcmdata 
-I/usr/include/dcmtk/ofstd -I/usr/include/vtk-6.3 -I/usr/include/nifti 
-Wdate-time -D_FORTIFY_SOURCE=2 -O3 -fno-tree-vectorize -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
odinpulse.cpp -fPIC -DPIC -o .libs/odinpulse.o

> > In file included from ../odinseq/seqplatform.h:24:0,
> > from ../odinseq/seqdriver.h:23,
> > from ../odinseq/seqphase.h:26,
> > from ../odinseq/seqfreq.h:25,
> > from ../odinseq/seqpuls.h:22,
> > from odinpulse.h:24,
> > from odinpulse.cpp:1:
> > ../odinseq/seqplot.h:39:87: warning: invalid suffix on literal; 
C++11 requires a space between literal and string macro [-Wliteral-suffix]
> > static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, 
ODIN_GRAD_UNIT, ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", "rad/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};

> > ^
> > ../odinseq/seqplot.h:39:106: warning: invalid suffix on literal; 
C++11 requires a space between literal and string macro [-Wliteral-suffix]
> > static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, 
ODIN_GRAD_UNIT, ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", "rad/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};

> > ^
> > ../odinseq/seqplot.h:39:128: warning: invalid suffix on literal; 
C++11 requires a space between literal and string macro [-Wliteral-suffix]
> > static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, 
ODIN_GRAD_UNIT, ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", "rad/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};

> > ^
> > ../odinseq/seqplot.h:39:148: warning: invalid suffix on literal; 
C++11 requires a space between literal and string macro [-Wliteral-suffix]
> > static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, 
ODIN_GRAD_UNIT, ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", "rad/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};

> > ^
> > ../odinseq/seqplot.h:39:167: warning: invalid suffix on literal; 
C++11 requires a space between literal and string macro [-Wliteral-suffix]
> > static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, 
ODIN_GRAD_UNIT, ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", "rad/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};

> > ^
> > ../odinseq/seqplot.h:39:187: warning: invalid suffix on literal; 
C++11 requires a space between literal and string macro [-Wliteral-suffix]
> > static const char* timecourseUnit[]= {ODIN_GRAD_UNIT, 
ODIN_GRAD_UNIT, ODIN_GRAD_UNIT"/"ODIN_TIME_UNIT, "rad/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT, 
"rad*"ODIN_TIME_UNIT"^2/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", "rad/"ODIN_SPAT_UNIT, 
ODIN_TIME_UNIT"/"ODIN_SPAT_UNIT"^2", ODIN_GRAD_UNIT};

> > ^
> > ../odinseq/seqplot.h:39:222: 

Bug#831227: mediawiki: fails to upgrade from 'jessie' - trying to overwrite /var/lib/mediawiki/extensions/Cite

[Kunal Mehta]

Hi,

On 07/14/2016 02:49 AM, Andreas Beckmann wrote:
>>From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package mediawiki.
>   Preparing to unpack .../mediawiki_1%3a1.25.5-1_all.deb ...
>   Unpacking mediawiki (1:1.25.5-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/mediawiki_1%3a1.25.5-1_all.deb (--unpack):
>trying to overwrite '/var/lib/mediawiki/extensions/Cite', which is also in 
> package mediawiki-extensions-base 3.7
>   Processing triggers for systemd (215-17+deb8u4) ...
>   Errors were encountered while processing:
>/var/cache/apt/archives/mediawiki_1%3a1.25.5-1_all.deb

Thanks for reporting! Since mediawiki-extensions-base is basically
folded into the mediawiki package now, I changed[1] it to conflict for
all versions of the package and be a replaces as well.

I couldn't really figure out how to reproduce the piuparts run locally
though - the invocation at the top of the log file wasn't very useful to
me as it referenced tmp directories mostly, soany help on how to do so
would be appreciated.

[1] https://gerrit.wikimedia.org/r/#/c/299101/

-- Kunal

Bug#822050: marked as done (liquidwar: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 11:24:40 +
with message-id 
and subject line Bug#822050: fixed in liquidwar 5.6.4-4
has caused the Debian Bug report #822050,
regarding liquidwar: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liquidwar
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package liquidwar builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that liquidwar builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to liquidwar at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, liquidwar will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: liquidwar
Source-Version: 5.6.4-4

We believe that the bug you reported is fixed in the latest version of
liquidwar, 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 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated liquidwar 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: SHA1

Format: 1.8
Date: Fri, 15 Jul 2016 18:55:52 +0800
Source: liquidwar
Binary: liquidwar liquidwar-data liquidwar-server
Architecture: source
Version: 5.6.4-4
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team 
Changed-By: Paul Wise 
Description:
 liquidwar  - truly original multiplayer wargame
 liquidwar-data - data files for Liquid War
 liquidwar-server - Liquid War server
Closes: 822050
Changes:
 liquidwar (5.6.4-4) unstable; urgency=low
 .
   * Team upload.
 .
   [ Evgeni Golov ]
   * Correct Vcs-* URLs to point to anonscm.debian.org
 .
   [ Paul Wise ]
   * Add build-arch/build-indep targets to fix FTBFS with unreleased dpkg 
(Closes: #822050)
Checksums-Sha1:
 456202895ce4886b390a45022b33cb0f1b643834 2098 liquidwar_5.6.4-4.dsc
 025c53959fba4a5adc19befdec6ce2423e4c9e5c 11151 liquidwar_5.6.4-4.diff.gz
Checksums-Sha256:
 fabdc9a4760a2122dcd518501d827eff1740ee384876c27e0c00ccfdde3b64ef 2098 
liquidwar_5.6.4-4.dsc
 be025f27c4805f86938e050a90f4396fdbdd50f6c980132ba1fb0b177c25c624 11151 
liquidwar_5.6.4-4.diff.gz
Files:
 5c3a54292a63252927e4456622496a5e 2098 games extra liquidwar_5.6.4-4.dsc
 88434fd3f4e6e1037c88568d5cab5e6a 11151 games extra liquidwar_5.6.4-4.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBAgAGBQJXiMGYAAoJEDEWul6f+mmjakwQAKS1BtHZgzi4bopa71/EOwUi
0esSGD3HieFm3/wVzoOQDbw+F03rtR7ME6j9jnRfNeiZLKiP46QQD1/7doeAgwFB
+GB3O8IA7ZNY9A9RQ2x08cGxvoHgPV4x3NlH6burFDYHLRrwIbOVykGm9sh+gkbw
2mnl7lmR68j0C5wbEap8o9xrPFnGH7pReOfqWMZ5TQcKbkFWoIWd11uWEIbbVgUH
wn7O4u0KVmgNbYs+tm3vDHUsxk4weVJlLnWWUv0ZWNDTSgQZbMxTb6ih6uu3p6++
hEDjP3RZCDsGu7RUtnV4yMesFiwm/s0OpSdLuYeUolcm3pRLhgOgZuYHOENtyNRk
51NyZO9pQApsUVMqjLLEu/CIKLI1jgwyfK6QF/3txg/PmYzIuXheDAYgDFktUiUu
4WzgLaTso93wrraLD0oJ+NvAFRgRStpcdjOyvp5bYjganV6G62MosjGF196tceEe
snLojAA5YZZjdgtGa033/phEUXz4StzokzAN2GGJRvV2T4ucnpV8OILlAnbqK2e6
SAWLRTP2bYURHopMy5JaEPXQbXEoyZf/BXMnER5Xdch3XaH2CiYz1fqV8wC1L7D5
/atHkCqFPpIxmWeN7LXj79dIPXEpjzIwBP8aNxLFI0I8CZkFWhDPfgFIZ7KS6hSw
tTaSd+CCX92hSPRMT7BP
=7S/L
-END PGP SIGNATURE End Message ---

Bug#830633: marked as done (djangorestframework: FTBFS: AttributeError: type object 'BaseFilterableItem' has no attribute '_default_manager')

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 11:20:47 +
with message-id 
and subject line Bug#830633: fixed in djangorestframework 3.4.0-1
has caused the Debian Bug report #830633,
regarding djangorestframework: FTBFS: AttributeError: type object 
'BaseFilterableItem' has no attribute '_default_manager'
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.)


-- 
830633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djangorestframework
Version: 3.3.2-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,

djangorestframework fails to build from source in unstable/amd64:

  [..]

  copying rest_framework/locale/ko_KR/LC_MESSAGES/django.po -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/ko_KR/LC_MESSAGES
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/cs
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/cs/LC_MESSAGES
  copying rest_framework/locale/cs/LC_MESSAGES/django.mo -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/cs/LC_MESSAGES
  copying rest_framework/locale/cs/LC_MESSAGES/django.po -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/cs/LC_MESSAGES
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/he_IL
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/he_IL/LC_MESSAGES
  copying rest_framework/locale/he_IL/LC_MESSAGES/django.mo -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/he_IL/LC_MESSAGES
  copying rest_framework/locale/he_IL/LC_MESSAGES/django.po -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/he_IL/LC_MESSAGES
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/it
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/it/LC_MESSAGES
  copying rest_framework/locale/it/LC_MESSAGES/django.mo -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/it/LC_MESSAGES
  copying rest_framework/locale/it/LC_MESSAGES/django.po -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/it/LC_MESSAGES
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/ja
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/ja/LC_MESSAGES
  copying rest_framework/locale/ja/LC_MESSAGES/django.mo -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/ja/LC_MESSAGES
  copying rest_framework/locale/ja/LC_MESSAGES/django.po -> 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/ja/LC_MESSAGES
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/id
  creating 
/home/lamby/temp/cdt.20160709223545.xtvmaxJ7Ml.djangorestframework/djangorestframework-3.3.2/.pybuild/pythonX.Y_3.5/build/rest_framework/locale/id/LC_MESSAGES
  copying rest_framework/locale/id/LC_MESSAGES/django.mo -> 

Bug#826887: marked as done (ggcov: FTBFS: Total: 2/20 tests passed)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 11:52:26 +0100
with message-id <1464232e-293a-ba68-6a04-5d1cf9797...@sceal.ie>
and subject line fixed in 0.9-11
has caused the Debian Bug report #826887,
regarding ggcov: FTBFS: Total: 2/20 tests passed
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.)


-- 
826887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ggcov
Version: 0.9-10
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,

ggcov fails to build from source in unstable/amd64:

  [..]

  g++ -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -DORBIT2=1 -pthread 
-I/usr/include/libglade-2.0 -I/usr/include/libgnomeui-2.0 
-I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 
-I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 
-I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 
-I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include 
-I/usr/include/gconf/2 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DPKGDATADIR="\"/usr/share/ggcov\"" -DPREFIX="\"/usr\"" 
-DDATADIR="\"/usr/share\"" -DLIBDIR="\"/usr/lib/x86_64-linux-gnu\"" 
-DSYSCONFDIR="\"/etc\"" -DDEBUG=0 -DUI_DEBUG=0 -DCOV_AMD64 -DCOV_I386   
-Wdate-time -D_FORTIFY_SOURCE=2  -I/usr/include/libiberty  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall 
-Wchar-subscripts -Wsign-compare -pedantic -Wno-long-long  -fno-rtti 
-fno-exceptions -fno-implement-inlines -c -o testrunner.o testrunner.c
  g++ -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -DORBIT2=1 -pthread 
-I/usr/include/libglade-2.0 -I/usr/include/libgnomeui-2.0 
-I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 
-I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 
-I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 
-I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include 
-I/usr/include/gconf/2 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DPKGDATADIR="\"/usr/share/ggcov\"" -DPREFIX="\"/usr\"" 
-DDATADIR="\"/usr/share\"" -DLIBDIR="\"/usr/lib/x86_64-linux-gnu\"" 
-DSYSCONFDIR="\"/etc\"" -DDEBUG=0 -DUI_DEBUG=0 -DCOV_AMD64 -DCOV_I386   
-Wdate-time -D_FORTIFY_SOURCE=2  -I/usr/include/libiberty  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall 
-Wchar-subscripts -Wsign-compare -pedantic -Wno-long-long  -fno-rtti 
-fno-exceptions -fno-implement-inlines -c -o testfw.o testfw.c
  g++ -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -DORBIT2=1 -pthread 
-I/usr/include/libglade-2.0 -I/usr/include/libgnomeui-2.0 
-I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 
-I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 
-I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 
-I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 

Bug#830439: marked as done (emoslib: FTBFS: ld: cannot find -lpython3.5m)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 11:51:03 +0100
with message-id <10bab582-f20e-2a2f-547a-6be4b86ec...@sceal.ie>
and subject line fixed in 4.4.2-1
has caused the Debian Bug report #830439,
regarding emoslib: FTBFS: ld: cannot find -lpython3.5m
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.)


-- 
830439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emoslib
Version: 2:4.4.1-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 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):
> /usr/bin/cc  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2  -pipe -O3 -DNDEBUG   -Wl,-z,defs 
> -Wl,--as-needed -Wl,-z,relro-Wl,--disable-new-dtags 
> CMakeFiles/libemos_version.dir/version.c.o  -o usr/bin/libemos_version 
> -rdynamic usr/lib/x86_64-linux-gnu/libemosR64.a /usr/lib/libgrib_api_f77.so.0 
> /usr/lib/libgrib_api_f90.so.0 /usr/lib/libgrib_api.so.0 -lpthread -lpng -lz 
> -lnetcdf /usr/lib/x86_64-linux-gnu/hdf5/serial/lib/libhdf5.so -lpthread -lsz 
> -ldl -lm -laec -L/usr/lib/python3.5/config-3.5m-x86_64-linux-gnu -L/usr/lib 
> -lpython3.5m -lpthread -ldl  -lutil -lm  -Xlinker -export-dynamic -Wl,-O1 
> -Wl,-Bsymbolic-functions -lfftw3 -lgfortran -lm -lquadmath -lm 
> -Wl,-rpath,"\$ORIGIN/../lib:/usr/lib/x86_64-linux-gnu/hdf5/serial/lib" 
> /usr/bin/ld: cannot find -lpython3.5m
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/emoslib_4.4.1-5_unstable_reb.normal.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 ---
close 830439-1

thanks

This bug was fixed in version 4.4.2-1, with changes in emoslib and
grib-api to avoid direct references to python and linking it.




-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. --- End Message ---

Bug#826811: marked as done (emoslib: OpenJPEG removal)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 11:48:48 +0100
with message-id <501c6d27-4d1f-b500-748f-048c61f03...@sceal.ie>
and subject line fixed in latest release
has caused the Debian Bug report #826811,
regarding emoslib: OpenJPEG removal
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.)


-- 
826811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emoslib
Severity: important
User: ma...@debian.org
Usertags: stretch2000

This is a continued operation since src:jasper removal for stretch
release.

src:openjpeg will be removed from Debian for the stretch release (and
following that, the archive in general). For more information see:
http://bugs.debian.org/826805

It has been superseeded by src:openjpeg2

Your package uses src:openjpeg, so please either remove the JPEG2000
functionality or move to the new API.

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Mathieu 
--- End Message ---
--- Begin Message ---
close 826811

thanks


emoslib is now at 4.4.2-1. Recent releases no longer depend (directly)
on openjpeg.



-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. --- End Message ---

Bug#831107: stimfit: FTBFS with GCC 6: ./gui/doc.cpp:1269:27: error: no matching function for call to 'transform(std::vector::const_iterator, std::vector::const_iterator, std::vector

[Christoph Schmidt-Hieber]

Thanks for the bug report.

0.15.3-1 closes this bug, but I accidentally referenced the wrong bug
number in the changelog:

http://metadata.ftp-master.debian.org/changelogs//main/s/stimfit/stimfit_0.15.3-1_changelog

On Thu, Jul 14, 2016 at 09:27:04AM +0200, Lucas Nussbaum wrote:
> Source: stimfit
> Version: 0.15.2-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[4]: Entering directory '/«PKGBUILDDIR»/src/stimfit'
> >   CXX  libstimfit_la-stf.lo
> >   CXX  libstimfit_la-app.lo
> > ./gui/app.cpp:1419:30: warning: macro "__DATE__" might prevent reproducible 
> > builds [-Wdate-time]
> >  verString << wxT(__DATE__) << wxT(", ") << wxT(__TIME__);
> >   ^
> > ./gui/app.cpp:1419:60: warning: macro "__TIME__" might prevent reproducible 
> > builds [-Wdate-time]
> >  verString << wxT(__DATE__) << wxT(", ") << wxT(__TIME__);
> > ^
> >   CXX  libstimfit_la-unopt.lo
> >   CXX  libstimfit_la-doc.lo
> > In file included from ./gui/././../../libstfio/stfio.h:66:0,
> >  from ./gui/././../stf.h:71,
> >  from ./gui/./app.h:176,
> >  from ./gui/doc.cpp:35:
> > ./gui/././../../libstfio/./recording.h: In copy constructor 
> > 'Recording::Recording(const Recording&)':
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' 
> > is deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:17: note: declared here
> >  std::string time0, date; 
> >  ^
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' 
> > is deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:17: note: declared here
> >  std::string time0, date; 
> >  ^
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' 
> > is deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:17: note: declared here
> >  std::string time0, date; 
> >  ^
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::time0' 
> > is deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:17: note: declared here
> >  std::string time0, date; 
> >  ^
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> > deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:24: note: declared here
> >  std::string time0, date; 
> > ^~~~
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> > deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:24: note: declared here
> >  std::string time0, date; 
> > ^~~~
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> > deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:24: note: declared here
> >  std::string time0, date; 
> > ^~~~
> > ./gui/././../../libstfio/./recording.h:41:16: warning: 'Recording::date' is 
> > deprecated [-Wdeprecated-declarations]
> >  class StfioDll Recording {
> > ^
> > ./gui/././../../libstfio/./recording.h:378:24: note: declared here
> >  std::string time0, date; 
> > ^~~~
> > ./gui/doc.cpp: In member function 'virtual bool wxStfDoc::SaveAs()':
> > ./gui/doc.cpp:711:45: note: synthesized method 'Recording::Recording(const 
> > Recording&)' first required here 
> >  Recording writeRec(ReorderChannels());
> >  ^
> > ./gui/doc.cpp: In member function 'void 
> > wxStfDoc::LnTransform(wxCommandEvent&)':
> > ./gui/doc.cpp:1269:27: error: no matching function for call to 
> > 'transform(std::vector::const_iterator, 
> > std::vector::const_iterator, std::vector::iterator, 
> > )'
> > 

Bug#811670: FTBFS with GCC 6: cannot convert x to y

[Jonas Smedegaard]

Hi Konclude Developer Team,

I maintail the packaging of Konclude for Debian.

My fellow developer, Martin, have discovered that Konclude fails to 
compile succesfully with the most recent GNU compiler, GCC 6.

Any help resolving this is quite appreciated.

Quoting Martin Michlmayr (2016-01-20 01:48:28)
> 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.
> 
> > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> ...
> > g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall -w 
> > -D_REENTRANT -DQT_XML_LIB -DQT_NETWORK_LIB 
> > -DKONCLUDE_FORCE_ALL_DEBUG_DEACTIVATED -DQT_NO_DEBUG -DQT_GUI_LIB 
> > -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
> > -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
> > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 
> > -I./generatedfiles -I./GeneratedFiles/Release -ISource -I. 
> > -IGeneratedFiles/release -o release/CQueryError.o 
> > Source/Reasoner/Query/CQueryError.cpp
> > g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall -w 
> > -D_REENTRANT -DQT_XML_LIB -DQT_NETWORK_LIB 
> > -DKONCLUDE_FORCE_ALL_DEBUG_DEACTIVATED -DQT_NO_DEBUG -DQT_GUI_LIB 
> > -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
> > -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
> > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 
> > -I./generatedfiles -I./GeneratedFiles/Release -ISource -I. 
> > -IGeneratedFiles/release -o release/CQueryInconsitentOntologyError.o 
> > Source/Reasoner/Query/CQueryInconsitentOntologyError.cpp
> > Source/Reasoner/Query/CQueryInconsitentOntologyError.cpp: In static member 
> > function 'static Konclude::Reasoner::Query::CQueryInconsitentOntologyError* 
> > Konclude::Reasoner::Query::CQueryInconsitentOntologyError::getInconsistentOntologyError(Konclude::Reasoner::Query::CQueryError*)':
> > Source/Reasoner/Query/CQueryInconsitentOntologyError.cpp:57:12: error: 
> > cannot convert 'bool' to 
> > 'Konclude::Reasoner::Query::CQueryInconsitentOntologyError*' in return
> >  return false;
> > ^
> > 
> > Makefile:10326: recipe for target 
> > 'release/CQueryInconsitentOntologyError.o' failed


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: tagging 811670

[Debian Bug Tracking System]

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

> tags 811670 + upstream help
Bug #811670 [konclude] FTBFS with GCC 6: cannot convert x to y
Added tag(s) help and upstream.
> thanks
Stopping processing here.

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

Processed: tagging 831036

[Debian Bug Tracking System]

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

> tags 831036 + pending
Bug #831036 [src:nomad] nomad: FTBFS: client/fingerprint/cpu.go:25: undefined: 
cpu.CPUInfo
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831099: marked as done (rosegarden: FTBFS with GCC 6: PitchBendSequenceDialog.cpp:922:73: error: call of overloaded 'abs(double)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:27:16 +
with message-id 
and subject line Bug#831099: fixed in rosegarden 1:16.02-2
has caused the Debian Bug report #831099,
regarding rosegarden: FTBFS with GCC 6: PitchBendSequenceDialog.cpp:922:73: 
error: call of overloaded 'abs(double)' is ambiguous
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.)


-- 
831099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rosegarden
Version: 1:16.02-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»/obj-x86_64-linux-gnu'
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/GzipFile.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -fvisibility=hidden   -o 
> CMakeFiles/rosegardenprivate.dir/document/GzipFile.cpp.o -c 
> /«PKGBUILDDIR»/src/document/GzipFile.cpp
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/LinkedSegmentsCommand.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -fvisibility=hidden   -o 
> CMakeFiles/rosegardenprivate.dir/document/LinkedSegmentsCommand.cpp.o -c 
> /«PKGBUILDDIR»/src/document/LinkedSegmentsCommand.cpp
> [  5%] Building CXX object 
> src/CMakeFiles/rosegardenprivate.dir/document/Command.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DBUILD_RELEASE 
> -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DNDEBUG -DNO_TIMING 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_TEST_LIB -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtTest -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore -isystem 
> /usr/share/qt4/mkspecs/default  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -fvisibility=hidden   

Bug#830497: marked as done (openjpa: FTBFS: the artifact javax.servlet:servlet-api:jar:debian has not been downloaded)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:24:42 +
with message-id 
and subject line Bug#830497: fixed in openjpa 2.4.0-3
has caused the Debian Bug report #830497,
regarding openjpa: FTBFS: the artifact javax.servlet:servlet-api:jar:debian has 
not been downloaded
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.)


-- 
830497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjpa
Version: 2.4.0-2
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Building OpenJPA JEST 2.4.0
[INFO] 
[WARNING] The POM for javax.servlet:servlet-api:jar:debian is missing,
no dependency information available
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] OpenJPA Utilities Library .. SUCCESS [  4.177 s]
[INFO] OpenJPA Kernel . SUCCESS [  4.931 s]
[INFO] OpenJPA JDBC ... SUCCESS [  2.821 s]
[INFO] OpenJPA Persistence  SUCCESS [  1.789 s]
[INFO] OpenJPA Persistence JDBC ... SUCCESS [  0.506 s]
[INFO] OpenJPA XML Store .. SUCCESS [  0.106 s]
[INFO] OpenJPA Slice .. SUCCESS [  0.379 s]
[INFO] OpenJPA JEST ... FAILURE [  0.019 s]
[INFO] OpenJPA Aggregate Jar .. SKIPPED
[INFO] OpenJPA Parent POM . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 15.301 s
[INFO] Finished at: 2016-07-04T07:27:51+00:00
[INFO] Final Memory: 39M/641M
[INFO] 
[ERROR] Failed to execute goal on project openjpa-jest: Could not
resolve dependencies for project
org.apache.openjpa:openjpa-jest:jar:2.4.0: Cannot access central
(https://repo.maven.apache.org/maven2) in offline mode and the
artifact javax.servlet:servlet-api:jar:debian has not been downloaded
from it before. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal on project openjpa-jest: Could not resolve dependencies
for project org.apache.openjpa:openjpa-jest:jar:2.4.0: Cannot access
central (https://repo.maven.apache.org/maven2) in offline mode and the
artifact javax.servlet:servlet-api:jar:debian has not been downloaded
from it before.
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:128)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:188)
at org.debian.maven.Wrapper.main(Wrapper.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 

Bug#829656: marked as done (mkdocs: Missing dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:26:17 +
with message-id 
and subject line Bug#829656: fixed in python-mkdocs 0.15.3-4
has caused the Debian Bug report #829656,
regarding mkdocs: Missing dependencies
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.)


-- 
829656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mkdocs
Version: 0.15.3-3
Severity: serious
Justification: not binNMU safe

When python-mkdocs is built in a clean chroot (like on Ubuntu or in
Debian's reproducible builds), it is missing some dependencies
(mkdocs-bootstrap and mkdocs-bootswatch) that were somehow present in
the package that was uploaded to Debian.

https://launchpad.net/ubuntu/+source/python-mkdocs/0.15.3-3/+build/9729927

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-mkdocs_0.15.3-3.rbuild.log

https://packages.debian.org/unstable/mkdocs

The logs have these warnings:
I: dh_python3 pydist:184: Cannot find package that provides
mkdocs_bootstrap. Please add package that provides it to Build-Depends
or add "mkdocs_bootstrap python3-mkdocs-bootstrap" line to
debian/py3dist-overrides or add proper  dependency to Depends by hand
and ignore this info.
I: dh_python3 pydist:184: Cannot find package that provides
mkdocs_bootswatch. Please add package that provides it to
Build-Depends or add "mkdocs_bootswatch python3-mkdocs-bootswatch"
line to debian/py3dist-overrides or add proper  dependency to Depends
by hand and ignore this info.

Please add the appropriate lines to debian/py3dist-overrides.

And please consider switching to source-only uploads:

https://wiki.debian.org/SourceOnlyUpload

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: python-mkdocs
Source-Version: 0.15.3-4

We believe that the bug you reported is fixed in the latest version of
python-mkdocs, 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 829...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Brian May  (supplier of updated python-mkdocs 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, 15 Jul 2016 18:25:17 +1000
Source: python-mkdocs
Binary: mkdocs mkdocs-doc
Architecture: source all
Version: 0.15.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 mkdocs - Static site generator geared towards building project documentati
 mkdocs-doc - Static site generator (documentation)
Closes: 829656
Changes:
 python-mkdocs (0.15.3-4) unstable; urgency=medium
 .
   * Ensure build depends get generated correctly. Closes: #829656.
Checksums-Sha1:
 c2c5f9c51895ee61d568a1c7651c1dc5844ddf6b 2287 python-mkdocs_0.15.3-4.dsc
 544760693a444da8f7b005ddc69b30e8ad69f3df 1805972 
python-mkdocs_0.15.3.orig.tar.gz
 e628c8dc7d9ba2732f2730f9627b8045a70d0e5a 148616 
python-mkdocs_0.15.3-4.debian.tar.xz
 2ea83c8d3aef903be44de30cf0b427b31bc4f1fe 1106944 mkdocs-doc_0.15.3-4_all.deb
 ea883c08b4356d02767e8dbb273e6b6a1ba95cc6 248260 mkdocs_0.15.3-4_all.deb
Checksums-Sha256:
 77c6b3430baf8107739001475d77444ec09c3f82660d3fefe3dafa4a77397fcf 2287 
python-mkdocs_0.15.3-4.dsc
 a5442ae24fd9e6f9daeefaf354c960e5dac27ff388f63e1bb324ed8a1b7edaa9 1805972 
python-mkdocs_0.15.3.orig.tar.gz
 519376bbde54de4265e464e21b2935ee2cb9d4c8249033c03ef79d9991c226e0 148616 
python-mkdocs_0.15.3-4.debian.tar.xz
 783585df05e4fe932df4ad9fc5f445a95853c64de62a8c15eadda08c57fb05af 1106944 
mkdocs-doc_0.15.3-4_all.deb
 15967dd4c0f0bd435e056185cd6353a46f8bb40d4e94d70c939c2f69b2c45e1e 248260 
mkdocs_0.15.3-4_all.deb
Files:
 6e59a9dd421c1b9620f6f70804cae619 2287 text optional python-mkdocs_0.15.3-4.dsc
 8d7ef937983bd7b7757d696aeaa5866a 1805972 text optional 
python-mkdocs_0.15.3.orig.tar.gz
 40e07b5b7758a4e9666241ecff3d185f 148616 text optional 
python-mkdocs_0.15.3-4.debian.tar.xz
 afdb1e419aaea34d7343747b1a6d4df0 1106944 doc optional 
mkdocs-doc_0.15.3-4_all.deb
 655af3f99c8e118ebe953db1a1357e55 248260 text optional 

Bug#829152: marked as done (liblapack3: misses Breaks: liblapack3gf)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:11:47 +
with message-id 
and subject line Bug#829152: fixed in lapack 3.6.1-2
has caused the Debian Bug report #829152,
regarding liblapack3: misses Breaks: liblapack3gf
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.)


-- 
829152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblapack3
Version: 3.5.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed again some error:

  octave3.0: error while loading shared libraries: liblapack.so.3gf: cannot 
open shared object file: No such file or directory

With the removal of the liblapack.so.3gf slave symlink the transitional
package liblapack3gf became unusable, therefore please add an unversioned
Breaks against it. Otherwise old stuff needing liblapack.so.3gf may stay
installed (because the dependencies are still satisfied), but will be no
longer usable.
(In my case, after a long upgrade path from lenny I ended up with both
liblapack3gf (3.5.0-4) and liblapack3 (3.6.0-2) installed as well as
octave3.0 and something using octave3.0 in its maintainer scripts.)


Andreas
--- End Message ---
--- Begin Message ---
Source: lapack
Source-Version: 3.6.1-2

We believe that the bug you reported is fixed in the latest version of
lapack, 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 829...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated lapack 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, 15 Jul 2016 11:31:26 +0200
Source: lapack
Binary: liblapack3 liblapacke liblapacke-dev libtmglib3 libtmglib-dev 
liblapack-dev liblapack-pic liblapack-test liblapack-doc liblapack-doc-man 
libblas3 libblas-common libblas-dev libblas-test libblas-doc
Architecture: source
Version: 3.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Description:
 libblas-common - Dependency package for all BLAS implementations
 libblas-dev - Basic Linear Algebra Subroutines 3, static library
 libblas-doc - Transitional package for BLAS manpages
 libblas-test - Basic Linear Algebra Subroutines 3, testing programs
 libblas3   - Basic Linear Algebra Reference implementations, shared library
 liblapack-dev - Library of linear algebra routines 3 - static version
 liblapack-doc - Library of linear algebra routines 3 - documentation (HTML)
 liblapack-doc-man - Library of linear algebra routines 3 - documentation 
(manual page
 liblapack-pic - Library of linear algebra routines 3 - static PIC version
 liblapack-test - Library of linear algebra routines 3 - testing programs
 liblapack3 - Library of linear algebra routines 3 - shared version
 liblapacke - Library of linear algebra routines 3 - C lib shared version
 liblapacke-dev - Library of linear algebra routines 3 - Headers
 libtmglib-dev - test matrix generators of LAPACK - development files
 libtmglib3 - test matrix generators of LAPACK - shared version
Closes: 829152
Changes:
 lapack (3.6.1-2) unstable; urgency=medium
 .
   * d/control: add Breaks of liblapack3 against liblapack3gf. (Closes: #829152)
Checksums-Sha1:
 5ee0f3b0a77afab922e36c999d040017b0b81e57 2841 lapack_3.6.1-2.dsc
 9fda14a53143f6d54535b283ad1d9d62fa2f5b23 21788 lapack_3.6.1-2.debian.tar.xz
Checksums-Sha256:
 5aca1bc28b75f64b0734af5bf2a7487d9e9ceb4ae994a3c7af7b2bc1316fca02 2841 
lapack_3.6.1-2.dsc
 5dfa2e137af79cda04a15b5d2415d8683042f326ffddbdc83be146d802dcb323 21788 
lapack_3.6.1-2.debian.tar.xz
Files:
 ba09f5868dd5d3c990cc2d7ae4370200 2841 libs optional lapack_3.6.1-2.dsc
 884a50d068f84382f9c033ee33b2f55e 21788 libs optional 
lapack_3.6.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXiK2kAAoJECzs6TUOzr5K5lkP/jNANLYqgvOFVrREwtf7rj8G
etAoyx9rg/7O4RM/4RjOU2UDtAUTmUVClc/eIuDErV+P56ZtTVrlnQuqIhqK+QRa

Bug#830244: marked as done (auditd: Crash at startup)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:05:24 +
with message-id 
and subject line Bug#830244: fixed in audit 1:2.6.5-1
has caused the Debian Bug report #830244,
regarding auditd: Crash at startup
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.)


-- 
830244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: auditd
Version: 1:2.6.3-1
Severity: grave
Tags: fixed-upstream upstream
Justification: renders package unusable

Hi,

So apparently with 2.6.3 the daemon can crash at startup in some
situation.

Let's prevent the migration until it's fixed (again...)

Cheers,

Laurent Bigonville

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: audit
Source-Version: 1:2.6.5-1

We believe that the bug you reported is fixed in the latest version of
audit, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated audit 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, 15 Jul 2016 11:25:41 +0200
Source: audit
Binary: auditd libauparse0 libauparse-dev libaudit1 libaudit-common 
libaudit-dev python-audit python3-audit golang-redhat-audit-dev audispd-plugins
Architecture: source amd64 all
Version: 1:2.6.5-1
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Laurent Bigonville 
Description:
 audispd-plugins - Plugins for the audit event dispatcher
 auditd - User space tools for security auditing
 golang-redhat-audit-dev - Go client bindings for the libaudit library
 libaudit-common - Dynamic library for security auditing - common files
 libaudit-dev - Header files and static library for security auditing
 libaudit1  - Dynamic library for security auditing
 libauparse-dev - Header files and static library for the libauparse0 library
 libauparse0 - Dynamic library for parsing security auditing
 python-audit - Python bindings for security auditing
 python3-audit - Python3 bindings for security auditing
Closes: 829500 830244
Changes:
 audit (1:2.6.5-1) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * New upstream release
 - Fix crash when starting the daemon (Closes: #830244)
 - Fix linking order between libaudit and libcap-ng (Closes: #829500)
   * debian/copyright: Add myself to the copyright file
 .
   [ Nicolas Braud-Santoni ]
   * debian/copyright: Make a DEP5-compliant, parseable file
Checksums-Sha1:
 5b5ea82f05a1b2b55c3553eac41fc820c1f7a1dc 2289 audit_2.6.5-1.dsc
 5b14b50733d6d9d11467d88933f2d2ef10f7b19e 1078910 audit_2.6.5.orig.tar.gz
 9779d7ddaa9e4e4171f3d10130ebb4b487996bb7 17944 audit_2.6.5-1.debian.tar.xz
 314bdd854d171da3bd4e5885036acf2ef568a95d 111672 
audispd-plugins-dbgsym_2.6.5-1_amd64.deb
 9002696af3cc43e3a8369cccec941a27f2a5425e 67018 
audispd-plugins_2.6.5-1_amd64.deb
 1a564ff2ab36b7915b4f26c1b26bb649b5156524 448858 auditd-dbgsym_2.6.5-1_amd64.deb
 03c6a61cff6f64acc0213145448cb6bd2d13a5c3 203800 auditd_2.6.5-1_amd64.deb
 2a4ec6ead554952f20eb4ed03daf4ea5bccd88cd 17440 
golang-redhat-audit-dev_2.6.5-1_all.deb
 e20ae5fc413d3738959068285289f3f227fde59c 17508 libaudit-common_2.6.5-1_all.deb
 d53a74012bdf4c93f741ca0677a31d826ae0c020 79594 libaudit-dev_2.6.5-1_amd64.deb
 112afcaedd50c151d1d6ff55f996f2fafedec4a3 53638 
libaudit1-dbgsym_2.6.5-1_amd64.deb
 e37e303ca7f856e80d54fbaac69777b289bf318c 50390 libaudit1_2.6.5-1_amd64.deb
 2362f403c8292e3cc72d18f6e5873e073d3e29f3 82976 libauparse-dev_2.6.5-1_amd64.deb
 a51046ae928e0d8d9836757b70e533e2170f11ed 104268 
libauparse0-dbgsym_2.6.5-1_amd64.deb
 

Processed: Bug#831099 marked as pending

[Debian Bug Tracking System]

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

> tag 831099 pending
Bug #831099 [src:rosegarden] rosegarden: FTBFS with GCC 6: 
PitchBendSequenceDialog.cpp:922:73: error: call of overloaded 'abs(double)' is 
ambiguous
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831099: marked as pending

[Stuart Prescott]

tag 831099 pending
thanks

Hello,

Bug #831099 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=pkg-multimedia/rosegarden.git;a=commitdiff;h=3972c1d

---
commit 3972c1d45cadda6b9416fb7df51517e031dcb325
Author: Stuart Prescott 
Date:   Fri Jul 15 19:00:05 2016 +1000

Add changelog for upload

diff --git a/debian/changelog b/debian/changelog
index ed62b7a..48efc09 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+rosegarden (1:16.02-2) unstable; urgency=medium
+
+  [ Stuart Prescott ]
+  * Cherry pick upstream patch to fix compilation with GCC 6 (Closes: #831099).
+
+  [ IOhannes m zmölnig ]
+  * Update mimetypes in package, with thanks to Petter Reinholdtsen
+(Closes: #825993).
+
+ -- Stuart Prescott   Fri, 15 Jul 2016 18:59:48 +1000
+
 rosegarden (1:16.02-1) unstable; urgency=medium
 
   * New upstream release.

Bug#827905: Character U+2028 can yield file corruption when edited in xterm

[Thomas Dickey]

On Thu, Jul 14, 2016 at 07:27:52PM +0200, Sven Joachim wrote:
> On 2016-07-13 18:24 -0700, Vincent Lefevre wrote:
> 
> > On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote:
> >> I don't see the behavior which is described, and haven't seen any
> >> suitable justification for marking this as a "grave" issue, rather
> >> than "normal".  Keep in mind that this is a rarely used line-break
> >> character.
> >
> > This is not common, but this was sufficient to *silently* corrupt one
> > of my files (what makes things really worse is that the corruption
> > doesn't seem to appear immediately, and one notices it when it may be
> > too late).
> >
> >> What I see on the screen is a box-outline for the nonprintable
> >> character (no space).
> >
> > Could this depend on some library version or on the font?
> 
> On the latter.  With the default font I see no corruption, but with the
> 9x15 font, for instance.  See the attached screenshot.

9x15 is an ISO-8859-1 font, and can't show U+2028

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature

Bug#830763: marked as done (akonadiconsole: crashes hard)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:48:18 +0200 (CEST)
with message-id 
and subject line Re: Bug#830763: akonadiconsole: crashes hard
has caused the Debian Bug report #830763,
regarding akonadiconsole: crashes hard
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.)


-- 
830763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: akonadiconsole
Version: 4:4.14.10-2
Severity: serious
Justification: makes the package unusable

While trying to debug #830762 (to see if the new messages are in fact
downloaded) I tried to start akonadiconsole, with, well, limited success:

-BEGIN cutting here may damage your screen surface-
tglase@tglase:~ $ akonadiconsole
   
QLayout: Attempting to add QLayout "" to QueryDebugger "", which already has a 
layout
QLayout: Attempting to add QLayout "" to JobTrackerWidget "", which already has 
a layout
QLayout: Attempting to add QLayout "" to JobTrackerWidget "", which already has 
a layout
QLayout: Attempting to add QLayout "" to NotificationMonitor "", which already 
has a layout
KCrash: Application 'akonadiconsole' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect 
sock_file=/home/tglase/.kde/socket-tglase.lan.tarent.de/kdeinit4__0
Unable to start Dr. Konqi
Not forwarding the crash to Apport.
255|tglase@tglase:~ $ akonadiconsole
   
QLayout: Attempting to add QLayout "" to QueryDebugger "", which already has a 
layout
QLayout: Attempting to add QLayout "" to JobTrackerWidget "", which already has 
a layout
QLayout: Attempting to add QLayout "" to JobTrackerWidget "", which already has 
a layout
QLayout: Attempting to add QLayout "" to NotificationMonitor "", which already 
has a layout
KCrash: Application 'akonadiconsole' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect 
sock_file=/home/tglase/.kde/socket-tglase.lan.tarent.de/kdeinit4__0
[1] + Stopped (signal) akonadiconsole 
tglase@tglase:~ $ Unable to start Dr. Konqi
Not forwarding the crash to Apport.
-END cutting here may damage your screen surface-

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages akonadiconsole depends on:
ii  kde-runtime   4:16.04.2-2
ii  kdepim-runtime4:16.04.2-2
ii  libakonadi-contact4   4:4.14.10-4
ii  libakonadi-kde4   4:4.14.10-4
ii  libakonadiprotocolinternals1  1.13.0-8
ii  libc6 2.23-1
ii  libcalendarsupport4   4:4.14.10-2
ii  libgcc1   1:6.1.1-9
ii  libkabc4  4:4.14.10-4
ii  libkcalcore4  4:4.14.10-4
ii  libkcmutils4  4:4.14.21-1
ii  libkdecore5   4:4.14.21-1
ii  libkdepim44:4.14.10-2
ii  libkdeui5 4:4.14.21-1
ii  libkio5   4:4.14.21-1
ii  libkmime4 4:4.14.10-4
ii  libmessageviewer4 4:4.14.10-2
ii  libqt4-dbus   4:4.8.7+dfsg-8
ii  libqt4-network4:4.8.7+dfsg-8
ii  libqt4-sql4:4.8.7+dfsg-8
ii  libqtcore44:4.8.7+dfsg-8
ii  libqtgui4 4:4.8.7+dfsg-8
ii  libstdc++66.1.1-9

akonadiconsole recommends no packages.

akonadiconsole suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:16.04.2-2

On Mon, 11 Jul 2016, Thorsten Glaser wrote:

> downloaded) I tried to start akonadiconsole, with, well, limited success:

With the new version, it… at least starts again, though
clicking on the Browse tab still crashes it.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg--- End Message ---

Bug#830762: marked as done (kmail: empty folders list)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jul 2016 10:46:24 +0200 (CEST)
with message-id 
and subject line Re: Bug#830762: kmail: empty folders list
has caused the Debian Bug report #830762,
regarding kmail: empty folders list
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.)


-- 
830762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 4:4.14.10-2
Severity: serious
Justification: makes the package unusable

After the recent KDEPIM-related updates (including involving a wallet
migration, which seems to have worked, and a reboot, so the last traces
of old Akonadi/KDEPIM are gone from the process table), parts of Kontact
stop working altogether.

First exhibit is KMail – the message folder pane is just completely
empty, although (see attached screenshot) the accounts are there and
synchronising. This happens both if I start KMail separately (see the
screenshot) or as component of Kontact (which is how I normally use it).

The same happens for the Calendar component – the bottom-left part which
normally holds the various calendars and their colours is empty.

Interestingly enough, the Feeds component not only works but shows very
up-to-date content (as of this morning), so it’s not a general Kontact
problem.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages kmail depends on:
ii  kde-runtime   4:16.04.2-2
ii  kdepim-runtime4:16.04.2-2
ii  kdepimlibs-kio-plugins4:4.14.10-4
ii  libakonadi-calendar4  4:4.14.10-4
ii  libakonadi-contact4   4:4.14.10-4
ii  libakonadi-kde4   4:4.14.10-4
ii  libakonadi-kmime4 4:4.14.10-4
ii  libakonadiprotocolinternals1  1.13.0-8
ii  libc6 2.23-1
ii  libcalendarsupport4   4:4.14.10-2
ii  libfollowupreminder4  4:4.14.10-2
ii  libgcc1   1:6.1.1-9
ii  libgpgme++2v5 4:4.14.10-4
ii  libgrantlee-core0 0.4.0-3
ii  libincidenceeditorsng44:4.14.10-2
ii  libkabc4  4:4.14.10-4
ii  libkalarmcal2 4:4.14.10-4
ii  libkcalcore4  4:4.14.10-4
ii  libkcalutils4 4:4.14.10-4
ii  libkcmutils4  4:4.14.21-1
ii  libkdecore5   4:4.14.21-1
ii  libkdepim44:4.14.10-2
ii  libkdeui5 4:4.14.21-1
ii  libkio5   4:4.14.21-1
ii  libkleo4  4:4.14.10-2
ii  libkmanagesieve4  4:4.14.10-2
ii  libkmime4 4:4.14.10-4
ii  libknotifyconfig4 4:4.14.21-1
ii  libkontactinterface4a 4:4.14.10-4
ii  libkparts44:4.14.21-1
ii  libkpimidentities44:4.14.10-4
ii  libkpimtextedit4  4:4.14.10-4
ii  libkpimutils4 4:4.14.10-4
ii  libkprintutils4   4:4.14.21-1
ii  libksieveui4  4:4.14.10-2
ii  libmailcommon44:4.14.10-2
ii  libmailimporter4  4:4.14.10-2
ii  libmailtransport4 4:4.14.10-4
ii  libmessagecomposer4   4:4.14.10-2
ii  libmessagecore4   4:4.14.10-2
ii  libmessagelist4   4:4.14.10-2
ii  libmessageviewer4 4:4.14.10-2
ii  libpimcommon4 4:4.14.10-2
ii  libqt4-dbus   4:4.8.7+dfsg-8
ii  libqt4-network4:4.8.7+dfsg-8
ii  libqt4-xml4:4.8.7+dfsg-8
ii  libqtcore44:4.8.7+dfsg-8
ii  libqtgui4 4:4.8.7+dfsg-8
ii  libqtwebkit4  2.3.4.dfsg-8
ii  libsendlater4 4:4.14.10-2
ii  libsolid4 4:4.14.21-1
ii  libstdc++66.1.1-9
ii  libtemplateparser44:4.14.10-2
ii  perl  5.22.2-2

Versions of packages kmail recommends:
ii  gnupg-agent 2.1.11-7
ii  gnupg2  2.1.11-7
ii  kdepim-doc  4:16.04.2-2
pn  kdepim-themeditors  
pn  ktnef   
ii  pinentry-qt [pinentry-x11]  0.9.7-5

Versions of packages kmail suggests:
pn  clamav

Bug#829656: marked as pending

[Brian May]

tag 829656 pending
thanks

Hello,

Bug #829656 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/python-mkdocs.git;a=commitdiff;h=51f5e2e

---
commit 51f5e2ed0d86b9b647e2f6f773baf286a872290e
Author: Brian May 
Date:   Fri Jul 15 18:26:05 2016 +1000

Fix dependencies

diff --git a/debian/changelog b/debian/changelog
index 020fc7f..da426ed 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-mkdocs (0.15.3-4) unstable; urgency=medium
+
+  * Ensure build depends get generated correctly. Closes: #829656.
+
+ -- Brian May   Fri, 15 Jul 2016 18:25:17 +1000
+
 python-mkdocs (0.15.3-3) unstable; urgency=medium
 
   * Look for theme files under /usr/share. Closes: #820783.

Processed: Bug#829656 marked as pending

[Debian Bug Tracking System]

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

> tag 829656 pending
Bug #829656 [mkdocs] mkdocs: Missing dependencies
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831374: ugene: please rebuild against libprocps6

[Emilio Pozuelo Monfort]

Source: ugene
Version: 1.21.0+dfsg-1
Severity: serious

Your package needs to be rebuilt against libprocps6. Since it
is not auto-built, you need to do a sourceful upload.

Emilio

Bug#829656: [Python-modules-team] Bug#829656: mkdocs: Missing dependencies

[Brian May]

Brian May  writes:

> I think you might be confused; these a warnings only. The build-depends
> installs the required packages.

Oh, I guess you were talking about depends on the binary packages, not
the build-depends.

Will upload after I finish doing some tests.

PS. All my uploads are done using a clean schroot.
-- 
Brian May