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

[Debian Bug Tracking System]

Your message dated Wed, 03 Aug 2016 04:34:49 +
with message-id 
and subject line Bug#822039: fixed in xmldiff 0.6.10-2.2
has caused the Debian Bug report #822039,
regarding xmldiff: 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.)


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

Hi,

The package xmldiff 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 xmldiff builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to xmldiff 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, xmldiff 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: xmldiff
Source-Version: 0.6.10-2.2

We believe that the bug you reported is fixed in the latest version of
xmldiff, 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.
John Paul Adrian Glaubitz  (supplier of updated 
xmldiff 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: Wed, 03 Aug 2016 05:59:29 +0200
Source: xmldiff
Binary: xmldiff xmldiff-xmlrev
Architecture: source amd64 all
Version: 0.6.10-2.2
Distribution: sid
Urgency: medium
Maintainer: Alexandre Fayolle 
Changed-By: John Paul Adrian Glaubitz 
Description:
 xmldiff- tree to tree correction between xml documents
 xmldiff-xmlrev - xmldiff output formatter
Closes: 822039
Changes:
 xmldiff (0.6.10-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build-arch and build-indep targets to debian/rules to fix
 FTBFS with newer versions of dpkg (Closes: #822039)
Checksums-Sha1:
 2f0f87aa9d1ad8190ea6073dc564e5ec718242b7 1981 xmldiff_0.6.10-2.2.dsc
 c939c67aa97b2fd1d087308e6183674ac5fb5071 4404 xmldiff_0.6.10-2.2.diff.gz
 562b85a2a148ea226f1a0b99a425cf76f274c8e1 11038 
xmldiff-dbgsym_0.6.10-2.2_amd64.deb
 d069ddb7d738dd9c14e14b882eb7b52ab2787b95 8646 xmldiff-xmlrev_0.6.10-2.2_all.deb
 39246abfce47bec773312a488692ea6ce0e96968 43726 xmldiff_0.6.10-2.2_amd64.deb
Checksums-Sha256:
 04f1dba94436a7cd282acca063e697680d2c103633fea4f348183e2a481409dd 1981 
xmldiff_0.6.10-2.2.dsc
 5e404657e73eae4e67cfcfff23433a4d73f77034cf4c1461e0276e3193ab4b1f 4404 
xmldiff_0.6.10-2.2.diff.gz
 4675477b1a512f31e84880534c384bb5a794d7a0a10323d4b775d0b28bb351cf 11038 
xmldiff-dbgsym_0.6.10-2.2_amd64.deb
 6302573638935240ed56a8bf6d398331cfa57529a014432fa116d31ec4a00fe5 8646 
xmldiff-xmlrev_0.6.10-2.2_all.deb
 1e27b93b3ce05763dbe8e48eb3181436031d15cc22dab739164688d8a9b0a876 43726 
xmldiff_0.6.10-2.2_amd64.deb
Files:
 5b2d7bb27c8910d25fafa327e9bbd9e2 1981 misc optional xmldiff_0.6.10-2.2.dsc
 5356d53d2116dc3b7341c08510787368 4404 misc optional xmldiff_0.6.10-2.2.diff.gz
 6394766b9020e8039387fd8c3d140d2a 11038 debug extra 
xmldiff-dbgsym_0.6.10-2.2_amd64.deb
 851e76ecc29b2e570f3609b0de9e1234 8646 misc optional 
xmldiff-xmlrev_0.6.10-2.2_all.deb
 1b74a41206b3165d40cfab6df1b79a4d 43726 misc optional 
xmldiff_0.6.10-2.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXoWzmAAoJEHQmOzf1tfkTy38P/RfC7u3vf3KJx9T473UOVgeK
LThaN+EHjLhAhAQs9fvr/H4k79aALwmDl8nwVD6b3O2GhHhinoSfpd4psnaDvB+F
YCSHSmeY07gLtF27cU1dbL79NrT3lGU7W3U4Qzg2NktfXrHpfxtHAZkBNVvqPPqs
ms4lSivaQVVIQUgD3hFQCxAibCjdsXAHGlXU/3J30DPhccz5tUq8VNyaAkDR7Dfb
ks+537nkSzygDJikc080CdbvTs5gCAr01z9mfXmNpFxtH9Ey364N05BkMOECv7eH

Bug#832844: marked as done (qtwebkit: FTBFS: /bin/sh: 1: python: not found)

[Debian Bug Tracking System]

Your message dated Wed, 03 Aug 2016 04:34:02 +
with message-id 
and subject line Bug#832844: fixed in qtwebkit 2.3.4.dfsg-8.1
has caused the Debian Bug report #832844,
regarding qtwebkit: FTBFS: /bin/sh: 1: python: not found
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.)


-- 
832844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtwebkit
Version: 2.3.4.dfsg-8
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory 
> '/«PKGBUILDDIR»/WebKitBuild/Release/Source/JavaScriptCore'
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ArrayConstructor.cpp -i > 
> generated/ArrayConstructor.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ArrayConstructor.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ArrayPrototype.cpp -i > 
> generated/ArrayPrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ArrayPrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/BooleanPrototype.cpp -i > 
> generated/BooleanPrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/BooleanPrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/DateConstructor.cpp -i > 
> generated/DateConstructor.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/DateConstructor.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/DatePrototype.cpp -i > 
> generated/DatePrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/DatePrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ErrorPrototype.cpp -i > 
> generated/ErrorPrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ErrorPrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/JSGlobalObject.cpp -i > 
> generated/JSGlobalObject.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/JSGlobalObject.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/JSONObject.cpp -i > 
> generated/JSONObject.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/JSONObject.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/MathObject.cpp -i > 
> generated/MathObject.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/MathObject.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/NamePrototype.cpp -i > 
> generated/NamePrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/NamePrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/NumberConstructor.cpp -i > 
> generated/NumberConstructor.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/NumberConstructor.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/NumberPrototype.cpp -i > 
> generated/NumberPrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/NumberPrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ObjectConstructor.cpp -i > 
> generated/ObjectConstructor.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ObjectConstructor.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ObjectPrototype.cpp -i > 
> generated/ObjectPrototype.lut.h
> Creating hashtable for 
> /«PKGBUILDDIR»/Source/JavaScriptCore/runtime/ObjectPrototype.cpp
> perl /«PKGBUILDDIR»/Source/JavaScriptCore/create_hash_table 
> 

Bug#833304: closed by se...@debian.org (Steinar H. Gunderson) (Bug#833304: fixed in nageru 1.3.4-1)

[Chris Lamb]

> it's a simple sub-point of “new upstream release”; if something
> changed in the Debian packaging, I do of course document it.

Ah, I think I misunderstood your previous comment about running IWYU
and thus it being "part" of the packaging rather than upstream, especially
when you were asking questions regarding my build environment :)

Agree with the above ^  :)


Best regards,

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

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Peter Colberg]

Dear Debian Release Team,

twinkle has been marked for autoremoval from testing on 2016-08-27 due
to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields
slight differences in the list of visible symbols.

How should this bug be dealt with? Is it not simply a matter of
waiting for GCC 6 to become default, uploading ucommon with an
updated symbols file and an ABI bump (if needed), and submitting
binNMUs for dependent packages?

If so, can this bug be downgraded to severity important until then?

Regards,
Peter

Processed: tagging 822030

[Debian Bug Tracking System]

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

> tags 822030 + pending
Bug #822030 [src:timidity] timidity: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#833304: closed by se...@debian.org (Steinar H. Gunderson) (Bug#833304: fixed in nageru 1.3.4-1)

[Steinar H. Gunderson]

On Wed, Aug 03, 2016 at 12:16:10AM +0200, Chris Lamb wrote:
>> Fixes FTBFS. (Closes: #833304)
> This seems a little terse. Could you elaborate..?

I guess I could have pasted in the relevant commit from upstream:

  commit 156470e2dca8813f8eb736f52363e94501ab36f5
  Author: Steinar H. Gunderson 
  Date:   Tue Aug 2 22:46:01 2016 +0200

  Run IWYU on quicksync_encoder.{cpp,h}.

One of the effects of this was that #include  now was properly
#included. You can see the commit at

  
https://git.sesse.net/?p=nageru;a=commitdiff;h=156470e2dca8813f8eb736f52363e94501ab36f5

I normally don't put detailed upstream information in Debian changelogs,
though. In this case, it really is the new upstream version that fixes the
issue, so it's a simple sub-point of “new upstream release”; if something
changed in the Debian packaging, I do of course document it.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#822030: proposed NMU

[Adam Borowski]

Hi!
I've prepared, and uploaded to DELAYED/7, a NMU with Santiago's patch for
this bug.  If there's anything amiss, please holler!

Debdiff attached.

-- 
An imaginary friend squared is a real enemy.
diff -Nru timidity-2.13.2/debian/changelog timidity-2.13.2/debian/changelog
--- timidity-2.13.2/debian/changelog2016-04-07 16:04:35.0 +0200
+++ timidity-2.13.2/debian/changelog2016-08-03 00:54:56.0 +0200
@@ -1,3 +1,10 @@
+timidity (2.13.2-40.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due to missing build-{arch,indep}.  Closes: #822030
+
+ -- Adam Borowski   Wed, 03 Aug 2016 00:54:56 +0200
+
 timidity (2.13.2-40.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru timidity-2.13.2/debian/rules timidity-2.13.2/debian/rules
--- timidity-2.13.2/debian/rules2015-12-23 20:12:46.0 +0100
+++ timidity-2.13.2/debian/rules2016-08-03 00:52:15.0 +0200
@@ -53,6 +53,8 @@
 ##  The rules
 ##
 
+build-arch: build
+build-indep: build
 build: doconfigure build-stamp
 build-stamp:
dh_testdir
@@ -196,4 +198,4 @@
dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install

Bug#772576: taskcoach: Start failed

[Nicolas Boulenguez]

Package: taskcoach
Followup-For: Bug #772576

Hello.
In order to find whether the bug originates in the Debian packaging,
could you please install the debian package available at
http://www.taskcoach.org/download_for_linux.html
then attempt to reproduce the bug?
Thanks.

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

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:54:07 +
with message-id 
and subject line Bug#828656: fixed in django-sekizai 0.9.0-4
has caused the Debian Bug report #828656,
regarding FTBFS under Django 1.10
to be marked as done.

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

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


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

Hi,

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

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

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

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

The full build log is attached.


Regards,

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


django-sekizai_0.9.0-3.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-sekizai
Source-Version: 0.9.0-4

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated django-sekizai 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: Tue, 02 Aug 2016 08:41:21 +
Source: django-sekizai
Binary: python-django-sekizai python3-django-sekizai python-django-sekizai-doc
Architecture: source all
Version: 0.9.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python-django-sekizai - template blocks for Django projects
 python-django-sekizai-doc - template blocks for Django projects (Documentation)
 python3-django-sekizai - template blocks for Django projects (Python3 version)
Closes: 828656
Changes:
 django-sekizai (0.9.0-4) unstable; urgency=medium
 .
   * Add myself as uploader.
   * Add patch to runtests.py to define TEMPLATES, which is required with Django
 1.10. This fixes FTBFS (Closes: #828656).
   * Remove useless X-Python{3,}-Version: (all satisfied in Stable).
   * Move some Build-Depends into Build-Depends-Indep, and remove version of
 python-django, as 1.5 is even already in oldstable.
Checksums-Sha1:
 137cccdde9e0630108de8738cbedaba1ad2f9ef5 2507 django-sekizai_0.9.0-4.dsc
 f7fb30a89e2d88bfec24a1523730816b225ce965 5232 
django-sekizai_0.9.0-4.debian.tar.xz
 475f6c008f011d78dd9e37448f7ad76749fe3973 24252 
python-django-sekizai-doc_0.9.0-4_all.deb
 588bfc880dee8aeb6e514381960286413e71ada7 13730 
python-django-sekizai_0.9.0-4_all.deb
 1e0e2e0a339a3731c872f52328c9864fd9f255f0 13236 
python3-django-sekizai_0.9.0-4_all.deb
Checksums-Sha256:
 a3e4923388be4544cfa859bac09664fef13607df9f1d2bbd424f375a07ff335a 2507 
django-sekizai_0.9.0-4.dsc
 4306e298ef26f652fa5ccd2381e354b868fc2baba3591b26b3acce35f86889ae 5232 
django-sekizai_0.9.0-4.debian.tar.xz
 5a4166fec036c5d1295fd6955f4e5fc24281e7f3b47a9724526cb43e8c2c890b 24252 
python-django-sekizai-doc_0.9.0-4_all.deb
 6aaf535984dcdf4ae09267635f2b0936898790bbff6a9140e10c0989bcd378ce 13730 
python-django-sekizai_0.9.0-4_all.deb
 75ab3d100d4a02572bd1ed8a9353b294a369aa3904aac24a879c25bbe2e07da7 13236 
python3-django-sekizai_0.9.0-4_all.deb
Files:
 7946a7d01a3f8f478d9b4d099a61ea85 2507 python optional 
django-sekizai_0.9.0-4.dsc
 be063b03dd1802b11fdae67993fc579c 5232 python optional 
django-sekizai_0.9.0-4.debian.tar.xz
 00a11ec5c4ca10116701c59b1043fe8f 24252 doc optional 
python-django-sekizai-doc_0.9.0-4_all.deb
 c53df3dcd457950a0b8a7cefe0f10143 13730 python optional 
python-django-sekizai_0.9.0-4_all.deb
 73abe24d1da005cdc371cd36e622cd10 13236 python optional 

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

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:53:58 +
with message-id 
and subject line Bug#828644: fixed in django-classy-tags 0.7.2-3
has caused the Debian Bug report #828644,
regarding FTBFS under Django 1.10
to be marked as done.

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

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


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

Hi,

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

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

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

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

The full build log is attached.


Regards,

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


django-classy-tags_0.7.2-2.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-classy-tags
Source-Version: 0.7.2-3

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated django-classy-tags 
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: Tue, 02 Aug 2016 10:08:09 +
Source: django-classy-tags
Binary: python-django-classy-tags python3-django-classy-tags 
python-django-classy-tags-doc
Architecture: source all
Version: 0.7.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python-django-classy-tags - Class based template tags for Django projects
 python-django-classy-tags-doc - Class based template tags for Django projects 
(Documentation)
 python3-django-classy-tags - Class based template tags for Django projects 
(Python3 version)
Closes: 828644
Changes:
 django-classy-tags (0.7.2-3) unstable; urgency=medium
 .
   * Added myself as uploader.
   * Removed obsolete python version restriction X-Python{3,}-Version:.
   * Added patch to fix Django 1.10 FTBFS (Closes: #828644):
 - 0002-django-1.10-define_TEMPLATES.patch
Checksums-Sha1:
 0fa808ccb99d1fb74890d9eced9b53c1f52cb65e 2444 django-classy-tags_0.7.2-3.dsc
 eb084c814c04c910624054b688823b8c93c3713f 5212 
django-classy-tags_0.7.2-3.debian.tar.xz
 96031607658a0a9549ee16bf34873baf2589989c 45084 
python-django-classy-tags-doc_0.7.2-3_all.deb
 342f0868f92125cea8756fdca7bcbb3e51c9a12d 20804 
python-django-classy-tags_0.7.2-3_all.deb
 d177bbd1c84048e65180ebf2305c18e05c450881 20902 
python3-django-classy-tags_0.7.2-3_all.deb
Checksums-Sha256:
 a636dbed0dfc867e8bd39bef0447b30f9abe5e42b7799cd8d1eb4d0cd3dc9ad6 2444 
django-classy-tags_0.7.2-3.dsc
 7d9d9cb087910e509e524aeefe238d7543796f6332cad53305ee0af1dcafe269 5212 
django-classy-tags_0.7.2-3.debian.tar.xz
 55b60fa1fc611860a4548c90cedd6e411e567a91948160c08926c2158a3eb084 45084 
python-django-classy-tags-doc_0.7.2-3_all.deb
 08c909e9f02908b990abb36a6d1c28dfda1deeba4c8a881370e2572e5afcd121 20804 
python-django-classy-tags_0.7.2-3_all.deb
 565ae4fc21a9740ff2d3fd91424c34be48c830594d05d8ab0fae347f53b3ca7f 20902 
python3-django-classy-tags_0.7.2-3_all.deb
Files:
 3de4fbb8fd0d7569293d3c7d9e844c18 2444 python optional 
django-classy-tags_0.7.2-3.dsc
 19a588aba1b28695dd5a8f161fd8732a 5212 python optional 
django-classy-tags_0.7.2-3.debian.tar.xz
 0782215c9649c2d1c5e65a0e5436853c 45084 doc optional 
python-django-classy-tags-doc_0.7.2-3_all.deb
 96a0bd6261ea87ba47463e7288d92a0b 20804 python optional 
python-django-classy-tags_0.7.2-3_all.deb
 ce58fa5adac9e578971020cc702b49f3 20902 python optional 

Bug#828642: Committed a patch

[Thomas Goirand]

Hi,

I committed a patch to the DPMT git fixing most of the issues, which
were related to the removal of django.conf.urls.patterns. Remaining is
the fix for the removal of _default_manager from Django 1.10, which is
still accessible via  Meta.default_manager_name (see Django 1.10 release
notes).

I hope this helps,
Cheers,

Thomas Goirand (zigo)

Bug#811841: marked as done (seqan: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:17:13 +
with message-id 
and subject line Bug#811841: fixed in seqan 1.4.2+dfsg-1
has caused the Debian Bug report #811841,
regarding seqan: FTBFS with GCC 6: no match for
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.)


-- 
811841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seqan
Version: 1.4.1+dfsg-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

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
...
> /<>/seqan-1.4.1+dfsg/core/include/seqan/basic/debug_test_system.h: 
> In instantiation of 'bool seqan::ClassTest::testTrue(const char*, int, const 
> T&, const char*, const char*, ...) [with T = std::basic_ifstream]':
> /<>/seqan-1.4.1+dfsg/core/include/seqan/basic/debug_test_system.h:1410:20:
>required from 'bool seqan::ClassTest::testTrue(const char*, int, const T&, 
> const char*) [with T = std::basic_ifstream]'
> /<>/seqan-1.4.1+dfsg/core/tests/store/test_store_io.h:435:9:   
> required from 'void SEQAN_TEST_test_store_io_sam() [with bool 
> speed_up_dummy_to_prevent_compilation_of_unused_tests_ = true]'
> /<>/seqan-1.4.1+dfsg/core/tests/store/test_store.cpp:60:5:   
> required from here
> /<>/seqan-1.4.1+dfsg/core/include/seqan/basic/debug_test_system.h:1362:64:
>  error: no match for 'operator<<' (operand types are 
> 'std::basic_ostream' and 'const std::basic_ifstream')
>  std::cerr << file << ":" << line << " Assertion failed : "
>  ~~
><< expression_ << " should be true but was " << (value_);
>~^~~
> 
--- End Message ---
--- Begin Message ---
Source: seqan
Source-Version: 1.4.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
seqan, 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.
Andreas Tille  (supplier of updated seqan 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: Tue, 02 Aug 2016 15:58:06 +0200
Source: seqan
Binary: seqan-dev
Architecture: source all
Version: 1.4.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 seqan-dev  - C++ library for the analysis of biological sequences (development
Closes: 766741 809058 811841 816988 818088
Changes:
 seqan (1.4.2+dfsg-1) unstable; urgency=medium
 .
   [Andreas Tille]
   * New upstream version
 Closes: #766741
   * Moved packaging to Git
   * Adapt watch file to fetch only seqan 1.x series
   * Update list of uploaders
   * Add compression option to watch file
   * Remove extras and core/apps from upstream source since these will be taken
 from seqan2 series (when doing so remove other unneeded stuff and binary
 files)
   * Add README.source to explain removals
   * Moved debian/upstream to debian/upstream/metadata
   * Drop documentation since developers should rather use seqan2
 Closes: #816988, #809058
   * Install cmake files
 Closes: #818088
 .
   [Gert Wollny]
   * d/rules: Add -DNDEBUG to CXXFLAGS, Closes: #811841
   * d/rules: enable parallel build
Checksums-Sha1:
 cf0f703821f42a32a85aebb93744cd71d7d57e90 2059 seqan_1.4.2+dfsg-1.dsc
 15b1150582ecbba675dec35793986a15d2c5c32b 9175900 seqan_1.4.2+dfsg.orig.tar.xz
 d9048975034c2c60a88b7898787b24b114e0deae 7148 

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

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:17:13 +
with message-id 
and subject line Bug#816988: fixed in seqan 1.4.2+dfsg-1
has caused the Debian Bug report #816988,
regarding seqan: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
to be marked as done.

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

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


-- 
816988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seqan
Version: 1.4.1+dfsg-2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
mkdir -p obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 5.3.1
-- The CXX compiler identification is GNU 5.3.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works

[... snipped ...]

cp --reflink=auto -a ./docs/main.py 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/main_tex.py 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/make.bat 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/make.sh 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/make2.bat 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/old_pages 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/pages 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/seqan_logo.gif 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
cp --reflink=auto -a ./docs/test_dddoc.py 
debian/seqan-dev/usr/share/doc/seqan-dev/html/
install -d debian/seqan-dev/usr/include
cp --reflink=auto -a ./core/include/seqan debian/seqan-dev/usr/include/
# /usr/bin/join is part of coreutils package: Avoid name conflict by renaming 
it to seqan-join
# This solution is withdrawn in favour of just providing a set of binaries 
according to upstream
# in /usr/bin (via symlink) while others go to /usr/lib/seqan/bin (see 
README.Debian)
# mv /<>/seqan-1.4.1+dfsg/debian/seqan-apps/usr/bin/join 
/<>/seqan-1.4.1+dfsg/debian/seqan-apps/usr/bin/seqan-join
#
# Formerly binaries were installed into usr/lib/seqan/bin/
# and only some of them were made available in /usr/bin via dh_link
# Since there is no obvious reason for this neither is there any
# documentation that explains the motivation this is commented here.
#for APP in `find /<>/seqan-1.4.1+dfsg/obj*/apps -mindepth 1 
-maxdepth 1 -executable -type f` ; do \
#  cp -a $APP 
/<>/seqan-1.4.1+dfsg/debian/seqan-apps/usr/lib/seqan/bin/ ; done
# --
# Formerly readmes were named README.app.  It seems more consistent
# to keep upstream documentation layout which in addition contains
# some example files.  So the old code is commented here.
#for APP in `find apps -name README` ; do \
#  app=`echo $APP | sed 's?.*apps/\(.\+\)/README?\1?'` ; \
#  echo $app ; \
#  cp -a $APP 
/<>/seqan-1.4.1+dfsg/debian/seqan-apps/usr/share/doc/seqan-apps/README.$app
 ; \
#done
# --
# Delete additional LICENSE files
find /<>/seqan-1.4.1+dfsg/debian/seqan-apps -type f -name LICENSE 
-delete
find: '/<>/seqan-1.4.1+dfsg/debian/seqan-apps': No such file or 
directory
debian/rules:26: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>/seqan-1.4.1+dfsg'
debian/rules:19: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


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

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

* 

Bug#833304: closed by se...@debian.org (Steinar H. Gunderson) (Bug#833304: fixed in nageru 1.3.4-1)

[Chris Lamb]

> Fixes FTBFS. (Closes: #833304)

This seems a little terse. Could you elaborate..?


Regards,

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

Bug#833304: marked as done (nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:13:04 +
with message-id 
and subject line Bug#833304: fixed in nageru 1.3.4-1
has caused the Debian Bug report #833304,
regarding nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not 
declared in this scope
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.)


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

nageru fails to build from source in unstable/amd64:

  [..]

  Setting up libinput-bin (1.4.0-1) ...
  Setting up libbmusb-dev (0.5.1-1) ...
  Setting up ucf (3.0036) ...
  Setting up libzita-resampler1:amd64 (1.3.0-2) ...
  Setting up libopus0:amd64 (1.1.2-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libva1:amd64 (1.7.1-2) ...
  Setting up libasound2:amd64 (1.1.1-2) ...
  Setting up libdrm2:amd64 (2.4.70-1) ...
  Setting up libx265-79:amd64 (1.9-3) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libogg0:amd64 (1.3.2-1) ...
  Setting up libfftw3-quad3:amd64 (3.3.4-2+b1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up libmp3lame0:amd64 (3.99.5+repack1-9+b1) ...
  Setting up libgnutlsxx28:amd64 (3.5.2-2) ...
  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3) ...
  Setting up libusb-1.0-0:amd64 (2:1.0.20-1) ...
  Setting up libcrystalhd3:amd64 (1:0.0~git20110715.fdd2f19-11+b1) ...
  Setting up libgcrypt20-dev (1.7.2-2) ...
  Setting up libepoxy0:amd64 (1.3.1-1) ...
  Setting up libsnappy1v5:amd64 (1.1.3-3) ...
  Setting up libgnutls-openssl27:amd64 (3.5.2-2) ...
  Setting up libusb-1.0-0-dev:amd64 (2:1.0.20-1) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up libreadline-dev:amd64 (6.3-8+b4) ...
  Setting up libzvbi-common (0.2.35-10) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Setting up libfftw3-single3:amd64 (3.3.4-2+b1) ...
  Setting up libxkbcommon0:amd64 (0.5.0-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libva-drm1:amd64 (1.7.1-2) ...
  Setting up liblua5.2-0:amd64 (5.2.4-1) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libmicrohttpd12 (0.9.50-2) ...
  Setting up liborc-0.4-0:amd64 (1:0.4.25-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-1) ...
  Setting up libgme0:amd64 (0.6.0-3) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libzvbi0:amd64 (0.2.35-10+b1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libschroedinger-1.0-0:amd64 (1.0.11-2.1) ...
  Setting up libwebp5:amd64 (0.4.4-1.1) ...
  Setting up libfftw3-long3:amd64 (3.3.4-2+b1) ...
  Setting up libwayland-cursor0:amd64 (1.11.0-2) ...
  Setting up libgsm1:amd64 (1.0.13-4) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libepoxy-dev:amd64 (1.3.1-1) ...
  Setting up libidn11-dev (1.33-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libgmp-dev:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-3) ...
  Setting up libx264-dev:amd64 (2:0.148.2699+gita5e06b9-1) ...
  Setting up libzita-resampler-dev:amd64 (1.3.0-2) ...
  Setting up libasound2-dev:amd64 (1.1.1-2) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-3) ...
  Setting up libfftw3-bin (3.3.4-2+b1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-3) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libwacom2:amd64 (0.19-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.70-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up libva-wayland1:amd64 (1.7.1-2) ...
  Setting up libeigen3-dev (3.3~beta2-1) ...
  Setting up libgbm1:amd64 (11.2.2-1) ...
  Setting up libva-tpi1:amd64 

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

[Ola Lundqvist]

Hi Chris

I had this
// Make sure this file is not readable by others

But maybe it was not clear enough. :-)

// Ola

On Wed, Aug 3, 2016 at 12:00 AM, Chris Lamb  wrote:

> > This is why I just override the "world readable" part and
> > let the rest be controlled by the user.
>
> Ah, didn't quite spot you are overriding just this bit. Worth a comment
> I think.
>
> > In the working patch you can see that I also set back the umask (just a
> > little further down in the file) as it was to just change this specific
> > case of logging.
>
> Well, sure, of course. :)
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#832413: marked as done (google-android-m2repository-installer: fails to install, remove, and install again)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:09:41 +
with message-id 
and subject line Bug#832413: fixed in google-android-m2repository-installer 35
has caused the Debian Bug report #832413,
regarding google-android-m2repository-installer: fails to install, remove, and 
install again
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.)


-- 
832413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-android-m2repository-installer
Version: 33
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install,
remove (but not purge), and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is the same version that is going to be
installed again.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

>From the attached log (scroll to the bottom...):

[...]
  install -d -m0755 /usr/share/doc/google-android-m2repository
  gzip -9 --stdout 
/var/cache/google-android-m2repository-installer/m2repository/NOTICE.txt > 
/usr/share/doc/google-android-m2repository/copyright.gz
  install -m0644 
/var/cache/google-android-m2repository-installer/m2repository/source.properties 
/usr/share/doc/google-android-m2repository/
  install -d -m0755 /usr/lib/android-sdk/extras/android
  mv /var/cache/google-android-m2repository-installer/m2repository 
/usr/lib/android-sdk/extras/android/
  mv: cannot move 
'/var/cache/google-android-m2repository-installer/m2repository' to 
'/usr/lib/android-sdk/extras/android/m2repository': Directory not empty
  Makefile:15: recipe for target 'install' failed
  make: *** [install] Error 1
  make: Leaving directory '/var/cache/google-android-m2repository-installer'
  dpkg: error processing package google-android-m2repository-installer 
(--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   google-android-m2repository-installer


Probably the maintainer scripts don't clean up properly on removal
but just on purge.


cheers,

Andreas


google-android-m2repository-installer_33.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: google-android-m2repository-installer
Source-Version: 35

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

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

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

Debian distribution maintenance software
pp.
Mouaad Aallam  (supplier of updated 
google-android-m2repository-installer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2016 20:40:07 +
Source: google-android-m2repository-installer
Binary: google-android-m2repository-installer
Architecture: source all
Version: 35
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Mouaad Aallam 
Description:
 google-android-m2repository-installer - Google Android support m2 repository
Closes: 832413
Changes:
 google-android-m2repository-installer (35) unstable; urgency=medium
 .
   * Create download folder and download archive as nobody:nogroup
   * Add mirror choosing feature with debconf shared template
   * Minor Makefile update (Closes: #832413)
   * Update to revision 35
Checksums-Sha1:
 f2fa4941e2b965b6a651513f35ea1ccc64ea212e 1637 
google-android-m2repository-installer_35.dsc
 0b075a9c26877759641a6cbbb1acab5d765d28ff 4100 
google-android-m2repository-installer_35.tar.xz
 853b753c3fc974ae35c13a4242027229dedb2ba4 3618 
google-android-m2repository-installer_35_all.deb
Checksums-Sha256:
 4e329de9e00a711d07c32e01aba2d89418913460eba66ab7cc7718b2ec7869af 1637 
google-android-m2repository-installer_35.dsc
 

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

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 22:08:19 +
with message-id 
and subject line Bug#806018: fixed in docbook-xsl-saxon 1.00.dfsg.1-6
has caused the Debian Bug report #806018,
regarding docbook-xsl-saxon: FTBFS when built with dpkg-buildpackage -A (No 
such file or directory)
to be marked as done.

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

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


-- 
806018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:docbook-xsl-saxon
Version: 1.00.dfsg.1-5
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

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


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ant --with=javahelper --parallel
   dh_testroot -i -O--buildsystem=ant -O--parallel
   dh_prep -i -O--buildsystem=ant -O--parallel
   dh_auto_install -i -O--buildsystem=ant -O--parallel
   jh_installjavadoc -i -O--buildsystem=ant -O--parallel
   dh_installdocs -i -O--buildsystem=ant -O--parallel
   dh_installchangelogs -i -O--buildsystem=ant -O--parallel
   dh_installexamples -i -O--buildsystem=ant -O--parallel
   dh_perl -i -O--buildsystem=ant -O--parallel
   dh_link -i -O--buildsystem=ant -O--parallel
   debian/rules override_jh_installlibs
make[1]: Entering directory '/<>'
jh_installlibs -pdocbook-xsl-saxon --upstream-version=1.00
dh_nativejava -pdocbook-xsl-saxon-gcj
dh_nativejava: No packages to build.
Couldn't unlink  : No such file or directory at /usr/bin/dh_nativejava line 92.
END failed--call queue aborted at /usr/bin/dh_nativejava line 272.
debian/rules:35: recipe for target 'override_jh_installlibs' failed
make[1]: *** [override_jh_installlibs] Error 2
make[1]: Leaving directory '/<>'
debian/rules:25: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: docbook-xsl-saxon
Source-Version: 1.00.dfsg.1-6

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated docbook-xsl-saxon 
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: Tue, 02 Aug 2016 21:21:18 +0100
Source: docbook-xsl-saxon
Binary: docbook-xsl-saxon docbook-xsl-saxon-gcj
Architecture: source
Version: 1.00.dfsg.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 docbook-xsl-saxon - Java extensions for use with DocBook XML stylesheets 
(Saxon)
 docbook-xsl-saxon-gcj - Java extensions for use with DocBook XML stylesheets 
(native code

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

[Chris Lamb]

> This is why I just override the "world readable" part and
> let the rest be controlled by the user.

Ah, didn't quite spot you are overriding just this bit. Worth a comment
I think.

> In the working patch you can see that I also set back the umask (just a
> little further down in the file) as it was to just change this specific
> case of logging.

Well, sure, of course. :)


Regards,

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

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

[Ola Lundqvist]

Hi Chris

The reason I do not simply set the umask to a fixed value is to use the
same principle as upstream. That is honor the umask set bu the user. There
may be reasons why group read and/or write should be set for example.

I agree with upstream that the umask should be honored, but not as strictly
as upstream do. This is why I just override the "world readable" part and
let the rest be controlled by the user.

In the working patch you can see that I also set back the umask (just a
little further down in the file) as it was to just change this specific
case of logging.

More clear now?

Best regards

// Ola

On Tue, Aug 2, 2016 at 7:14 PM, Chris Lamb  wrote:

> > Here is the working patch (attached).
>
> Out of interest, why:
>
> +mode_t prev_mask = umask(0022);
> +// Make sure this file is not readable by others
> +umask(prev_mask | S_IROTH | S_IWOTH | S_IXOTH);
>  FILE *fp = fopen(filename,"w");
>
> .. over, say:
>
> +// Make sure this file is not readable by others
> +mode_t prev_mask = umask(S_IXUSR|S_IRWXG|S_IRWXO);
>  FILE *fp = fopen(filename,"w");
> +umask(prev_mask);
>
> We don't really want to change the umask for the entire process.
> Or at least, we don't know the ramifications of that so better to
> keep it isolated to just this bit?
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#778747: openssl: RFC 7465 says RC4 is broken, never to be used

[Sebastian Andrzej Siewior]

On 2015-02-22 11:44:37 [+0100], Kurt Roeckx wrote:
> Even with RC4 enabled on both sides, it does provide something
> secure that doesn't use RC4 as long as you don't don't touch the
> defaults.  And I've seen many applications that screw up the
> defaults.

As of openssl in experimental we don't have RC4 in list of default
ciphers. The bug reported wants RC4 removed from openssl so my
understanding is that adding RC4 to the cipher's list should not result
in RC4 being available. Is that so?

If so lets continue…
We can't remove RC4 completly from openssl. From codesearch.d.n I see
that hydra and kismet are using it. I am not sure how much good we do if
they stop building.

Someone said that here that major browser vendors offer RC4. So I
checked them and can say that this is no longer an argument:

Chrome 50 (sid)
  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  TLS_RSA_WITH_AES_128_GCM_SHA256
  TLS_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_AES_128_CBC_SHA
  TLS_RSA_WITH_3DES_EDE_CBC_SHA

Firefox 45.1.1 (sid):
  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  TLS_DHE_RSA_WITH_AES_128_CBC_SHA
  TLS_DHE_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_AES_128_CBC_SHA
  TLS_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_3DES_EDE_CBC_SHA

Win XP, IE 8 (fully patched):
  TLS_RSA_WITH_RC4_128_MD5
  TLS_RSA_WITH_RC4_128_SHA
  TLS_RSA_WITH_3DES_EDE_CBC_SHA
  TLS_RSA_WITH_DES_CBC_SHA
  TLS_RSA_EXPORT1024_WITH_RC4_56_SHA
  TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA
  TLS_RSA_EXPORT_WITH_RC4_40_MD5
  TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5
  TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
  TLS_DHE_DSS_WITH_DES_CBC_SHA
  TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA

Win XP, Firefox 45.1.1 (ESR)
  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  TLS_DHE_RSA_WITH_AES_128_CBC_SHA
  TLS_DHE_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_AES_128_CBC_SHA
  TLS_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_3DES_EDE_CBC_SHA

Win XP, Firefox 38.8 (ESR, lowest major supported)
  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  TLS_DHE_RSA_WITH_AES_128_CBC_SHA
  TLS_DHE_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_AES_128_CBC_SHA
  TLS_RSA_WITH_AES_256_CBC_SHA
  TLS_RSA_WITH_3DES_EDE_CBC_SHA

Win XP, Opera 36.0
 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 TLS_RSA_WITH_AES_128_GCM_SHA256
 TLS_RSA_WITH_AES_256_CBC_SHA
 TLS_RSA_WITH_AES_128_CBC_SHA
 TLS_RSA_WITH_3DES_EDE_CBC_SHA

So. As of today RC4 isn't offerred by browsers except for IE4 on WinXP.
Firefox gone, Chromium gone. It remains only on XP with IE8 which has
_no_ support from its vendor so…

Kurt mentioned some broken exchange servers which do only RC4. Is this
still an issue? But this is SMTP only, right? So if the sender drops SSL
then everything works in plain text and there is no problem?

> Kurt

Sebastian

Bug#833304: nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope

[Chris Lamb]

> That's odd; I built it in a pbuilder, and several buildds have built it in
> the past few days. Is there anything special about your setup?

Not that I am aware of, sorry. Up-to-date pretty minimal-ish chroot, etc., the
usual. :)


Regards,

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

Bug#833304: nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope

[Steinar H. Gunderson]

On Tue, Aug 02, 2016 at 10:41:02PM +0200, Chris Lamb wrote:
>> That's odd; I built it in a pbuilder, and several buildds have built it in
>> the past few days. Is there anything special about your setup?
> Not that I am aware of, sorry. Up-to-date pretty minimal-ish chroot, etc., the
> usual. :)

Well, I'll put on my upstream hat and apt install iwyu, then... Thanks for
the bug report.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#833304: nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope

[Steinar H. Gunderson]

On Tue, Aug 02, 2016 at 07:59:28PM +0200, Chris Lamb wrote:
> nageru fails to build from source in unstable/amd64:

That's odd; I built it in a pbuilder, and several buildds have built it in
the past few days. Is there anything special about your setup?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Processed: Re: Bug#811684: FTBFS with GCC 6: enumerator value for... is not

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #811684 [mssh] FTBFS with GCC 6: enumerator value for... is not
Added tag(s) patch.

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

Bug#811684: FTBFS with GCC 6: enumerator value for... is not

[Axel Beckert]

Control: tag -1 + patch

Dear Hector,

Martin Michlmayr wrote:
> > gcc -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I..  -pthread 
> > -I/usr/include/vte-2.91 -I/usr/include/gtk-3.0 
> > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> > -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
> > -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 
> > -I/usr/include/libpng12 -I/usr/include/gio-unix-2.0/ 
> > -I/usr/include/p11-kit-1 -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 -Wdate-time 
> > -D_FORTIFY_SOURCE=2 -pedantic-errors -Werror -Wall -Wfatal-errors 
> > -Wwrite-strings -g -O2 -fstack-protector-strong -Wformat 
> > -Werror=format-security -c -o mssh.o mssh.c
> > In file included from /usr/include/glib-2.0/gobject/gobject.h:26:0,
> >  from /usr/include/glib-2.0/gobject/gbinding.h:29,
> >  from /usr/include/glib-2.0/glib-object.h:23,
> >  from /usr/include/glib-2.0/gio/gioenums.h:28,
> >  from /usr/include/glib-2.0/gio/giotypes.h:28,
> >  from /usr/include/glib-2.0/gio/gio.h:26,
> >  from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:28,
> >  from /usr/include/gtk-3.0/gdk/gdk.h:32,
> >  from /usr/include/gtk-3.0/gtk/gtk.h:30,
> >  from mssh.c:10:
> > /usr/include/glib-2.0/gobject/gparam.h:166:33: error: enumerator value for 
> > 'G_PARAM_DEPRECATED' is not an integer constant expression [-Wpedantic]
> >G_PARAM_DEPRECATED  = 1 << 31
> >  ^
> > 
> > compilation terminated due to -Wfatal-errors.
> > Makefile:379: recipe for target 'mssh.o' failed

This can be workarounded by removing the pedantic errors flags from CFLAGS:

--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -1,4 +1,4 @@
-AM_CFLAGS = -pedantic-errors -Werror -Wall -Wfatal-errors -Wwrite-strings
+AM_CFLAGS = -Wall -Wfatal-errors -Wwrite-strings
 
 AM_CPPFLAGS = $(MSSH_CFLAGS)
 
With this patch, mssh builds fine for me. (Patch inspired by the one
for 1.2.4 QA upload and hence removes "-Werror", too.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#831039: totem crash on startup, can't start it

[Andrea Zagli]

yes it works!!! thanks a lot!!!

also rhythmbox and epiphany-browser work

but it doesn't work for steam client; but i don't know if it is the  
same problem; it doesn't crash but it doesn't show "web pages"  
(everything except list of buyed games), and it is started to not work  
in the same moment of totem/rhythmbox/epipany-browser

Bug#831039: Processed: moreinfo

[Victor Nazarov]

I've found a fix...

You need to delete gstreamer registry file to fix this:

rm $HOME/.cache/gstreamer-1.0/registry.x86_64.bin

($HOME/.cache should probably be replaced with
${XDG_CACHE_HOME:-$HOME/.cache} to be freedesktop friendly)

Works for me at least.

I think this should be incorporated into package install script somewhere...

---
Victor Nazarov

On Tue, Aug 2, 2016 at 2:48 AM, Victor Nazarov 
wrote:

> It seems that it's a libav bug. If started like
>
> $ totem --gst-debug=6
>
> the following output is produced:
>
> 0:00:05.212869886 17220 0x7fd284013b70 ERROR  libav :0::
> Invalid chars '.0' at the end of expression '1.0'
> 0:00:05.212878563 17220 0x7fd284013b70 ERROR  libav :0::
> Unable to parse option value "1.0"
> 0:00:05.212884114 17220 0x7fd284013b70 INFO   libav :0::
> Assertion ret >= 0 failed at src/libavcodec/options.c:142
>
> The problem seems to be with libav trying to parse "1.0" string as a
> floating-point number, but current locale
>  is set up to treat comma "," as a decimal-point instead of plain point
> ".".
> I don't know where "1.0" string comes from.
>
>
> Victor Nazarov
>
> On Mon, Aug 1, 2016 at 2:51 PM, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Processing commands for cont...@bugs.debian.org:
>>
>> > tags 831039 + moreinfo
>> Bug #831039 [totem] totem crash on startup, can't start it
>> Added tag(s) moreinfo.
>> > thanks
>> Stopping processing here.
>>
>> Please contact me if you need assistance.
>> --
>> 831039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831039
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>> --
>> To unsubscribe, send mail to 831039-unsubscr...@bugs.debian.org.
>>
>
>

Bug#806221: marked as done (fakechroot: FTBFS when built with dpkg-buildpackage -A (Directory nonexistent))

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 19:35:06 +
with message-id 
and subject line Bug#806221: fixed in fakechroot 2.18-1.1
has caused the Debian Bug report #806221,
regarding fakechroot: FTBFS when built with dpkg-buildpackage -A (Directory 
nonexistent)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --with autoreconf
   dh_testdir -i -O--parallel
   dh_autoreconf -i -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'

[... snipped ...]

make[3]: Leaving directory '/<>/src'
Making install in scripts
make[3]: Entering directory '/<>/scripts'
make[4]: Entering directory '/<>/scripts'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c env.fakechroot fakechroot ldd.fakechroot 
'/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/usr/sbin'
 /usr/bin/install -c chroot.fakechroot '/<>/debian/tmp/usr/sbin'
 /bin/mkdir -p '/<>/debian/tmp/etc/fakechroot'
 /usr/bin/install -c -m 644 chroot.env debootstrap.env rinse.env 
'/<>/debian/tmp/etc/fakechroot'
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/scripts'
make[3]: Leaving directory '/<>/scripts'
Making install in test
make[3]: Entering directory '/<>/test'
Making install in src
make[4]: Entering directory '/<>/test/src'
make[5]: Entering directory '/<>/test/src'
make[5]: Nothing to be done for 'install-exec-am'.
make[5]: Nothing to be done for 'install-data-am'.
make[5]: Leaving directory '/<>/test/src'
make[4]: Leaving directory '/<>/test/src'
make[4]: Entering directory '/<>/test'
make[5]: Entering directory '/<>/test'
make[5]: Nothing to be done for 'install-exec-am'.
make[5]: Nothing to be done for 'install-data-am'.
make[5]: Leaving directory '/<>/test'
make[4]: Leaving directory '/<>/test'
make[3]: Leaving directory '/<>/test'
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
echo /usr/lib/x86_64-linux-gnu/fakechroot > 
debian/libfakechroot/etc/ld.so.conf.d/fakechroot-x86_64-linux-gnu.conf
/bin/sh: 1: cannot create 
debian/libfakechroot/etc/ld.so.conf.d/fakechroot-x86_64-linux-gnu.conf: 
Directory nonexistent
debian/rules:17: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 2
make[1]: Leaving directory '/<>'
debian/rules:11: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one.

In this case, I see that you are using "dh", which allow
(independently) optional targets override_dh_foo-arch and
override_dh_foo-indep (for several values of "foo").

Maybe using them this problem could be fixed.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: fakechroot
Source-Version: 2.18-1.1

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

Debian distribution maintenance software
pp.

Bug#742881: marked as done (missing license in debian/copyright)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 19:00:09 +
with message-id 
and subject line Bug#742881: fixed in camlpdf 2.1.1-1
has caused the Debian Bug report #742881,
regarding missing license in debian/copyright
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.)


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

Package: camlpdf
Version: 1.7.2+1-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing license of miniz.c to debian/copyright.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: camlpdf
Source-Version: 2.1.1-1

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

Debian distribution maintenance software
pp.
Nicolas Braud-Santoni  (supplier of updated camlpdf 
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, 23 Jul 2016 17:21:36 -0400
Source: camlpdf
Binary: libcamlpdf-ocaml-dev libcamlpdf-ocaml
Architecture: source amd64
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Nicolas Braud-Santoni 
Description:
 libcamlpdf-ocaml - library for reading, writing and manipulating PDF files and 
data
 libcamlpdf-ocaml-dev - library for reading, writing and manipulating PDF files 
and data
Closes: 742881
Changes:
 camlpdf (2.1.1-1) unstable; urgency=medium
 .
   * Team upload
   * Imported Upstream version 2.1.1
   * copyright: Add license of miniz.c (Closes: #742881)
   * debian/watch: Use filenamemangle
   * Remove obsolete patches
   * Use HTTPS for Vcs-* URLs
   * Bump Standards-Version to 3.9.8.
 No change required.
Checksums-Sha1:
 210e3c6ed9b177eb5f07207114a7ac9068323f25 2146 camlpdf_2.1.1-1.dsc
 049db26f3874fb3e577715a8c649fca46b40765a 563633 camlpdf_2.1.1.orig.tar.gz
 1b24c0f2bc0d5649dda084ebcd0bf077b1a52d0a 5232 camlpdf_2.1.1-1.debian.tar.xz
 fb8a74f78fe2a82ffb644d763f03f58b24ef0cf6 51396 
libcamlpdf-ocaml-dbgsym_2.1.1-1_amd64.deb
 101872aa95e06a23e7ab419b6f217301b42fba5c 1607548 
libcamlpdf-ocaml-dev_2.1.1-1_amd64.deb
 375e9f0eeba843973043d641edf474505b9fa9a6 35418 
libcamlpdf-ocaml_2.1.1-1_amd64.deb
Checksums-Sha256:
 17d1b650b49352981dcf282cfdd285bfcef8befa5f9f5c2e6f556a7af635ff72 2146 
camlpdf_2.1.1-1.dsc
 970b63bbe0d78c415813f48b103066286e95fe04ad5fb30cc968472b3c3b00b1 563633 
camlpdf_2.1.1.orig.tar.gz
 240ad50d6018758ef0e9972c017c055720edd8e7d57dd3f805db70119a6aecfe 5232 
camlpdf_2.1.1-1.debian.tar.xz
 bf6610e39c6953a99d69fe0add721fdf928a2261f52c352e8ac494f57a76eff5 51396 
libcamlpdf-ocaml-dbgsym_2.1.1-1_amd64.deb
 c4265cddc75a47636695da0037cb38e6424ac35dabaf3ec3cc7cdd3922aa89d0 1607548 
libcamlpdf-ocaml-dev_2.1.1-1_amd64.deb
 968dae578fcd8b2742c300d7f70d5da073551ee85fe578e609b70f233b140a4b 35418 
libcamlpdf-ocaml_2.1.1-1_amd64.deb
Files:
 3fd45ddebb902e5ff898c89a41ab287b 2146 ocaml optional camlpdf_2.1.1-1.dsc
 a3df80d071cc8d13ed119f9826941361 563633 ocaml optional 
camlpdf_2.1.1.orig.tar.gz
 0fa541fc65580416d5c6273722dab49e 5232 ocaml optional 
camlpdf_2.1.1-1.debian.tar.xz
 6872374da79f275e77cbf0c6b923a9cf 51396 debug extra 
libcamlpdf-ocaml-dbgsym_2.1.1-1_amd64.deb
 9de75da8059d4cadc37123ae04d72f7d 1607548 ocaml optional 
libcamlpdf-ocaml-dev_2.1.1-1_amd64.deb
 6020c9acb9df40385e06a6b9f6a27d9d 35418 ocaml optional 
libcamlpdf-ocaml_2.1.1-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXnyPyAAoJEHhT2k1JiBrTqS0P/RjQIRwijghCstOrdsc/xTj4
/oidzmUc1YsLwOsI6m9jsrMZqPzzohrxkNWW1rpZalsgwrxh5zizncTWfHXy9mje
xve0QLdmwd2l6hxQmCkVQB+BT+o3zVX1rmh3rSOq+pkYzalG826LUg7dCzEVslW1
vnaw7qYW062y6LCykQmdwjYROL6qtfeBIICLUowEP2Vt9TTvF7rcId3YI6q3Kr+g
PqVCcMSW/VESZSkbVI3tdfjAOT769wAKt7SEKR+GYnYj9ueCXtat8YYHq1RC2j7k
2CtXD7vYUF8+IaX+e/XRNSfxxj8jGqAd1uEhkONG0LZVoBzZ4y9wpe4C5MXO8wbn

Bug#832125: chromium crashing at startup

[Eric Delcamp]

hi, seems bug hasn't been corrected. i just update the package via apt
ii  chromium
52.0.2743.82-2  amd64web browser

previous release (49) worked like a charm

best,

Bug#833265: refcard: depends on unexistent package

[Holger Wansing]

Hi,

victory  wrote:
> On Tue, 2 Aug 2016 10:25:13 + (UTC)
> Gianfranco Costamagna wrote:
> 
> > As said, "ttf-kochi-gothic" is not available in Debian, so, the package
> > seems to be not buildable from source, at least with Debian repositories.
> 
> as long as stable has it, "not available in Debian" is not true;
> anyway you can apply this:
> 
> Index: refcard/dblatex.xsl
> ===
> --- refcard/dblatex.xsl   (r42)
> +++ refcard/dblatex.xsl   (wc)
> @@ -10,7 +10,7 @@
>   \setCJKmainfont{IPAPGothic}
>   \setCJKsansfont{IPAPMincho}
>   \setCJKmonofont{IPAexGothic}
> - \setmainfont{Kochi Gothic}
> + \setmainfont{IPAPGothic}
>   \setsansfont{IPAPMincho}
>   \setmonofont{IPAexGothic}
>  

I assume you have checked the displaying of the IPAPGothic font, right?
So that I can blindly commit the above?


Holger



-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Processed: tagging 831857

[Debian Bug Tracking System]

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

> tags 831857 + wheezy jessie stretch sid
Bug #831857 [src:libupnp] libupnp: CVE-2016-6255: write files via POST
Added tag(s) wheezy, stretch, sid, and jessie.
> thanks
Stopping processing here.

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

Bug#832357: marked as done (bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 18:00:13 +
with message-id 
and subject line Bug#832357: fixed in bacula 7.4.3+dfsg-3
has caused the Debian Bug report #832357,
regarding bacula-director-*: fails to upgrade from 'sid' - trying to overwrite 
/etc/init.d/bacula-director
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.)


-- 
832357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director-sqlite3,bacula-director-mysql,bacula-director-pgsql
Version: 7.4.3+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../bacula-director-sqlite3_7.4.3+dfsg-2_amd64.deb ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of stop.
  Unpacking bacula-director-sqlite3 (7.4.3+dfsg-2) over (7.4.3+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/bacula-director-sqlite3_7.4.3+dfsg-2_amd64.deb 
(--unpack):
   trying to overwrite '/etc/init.d/bacula-director', which is also in package 
bacula-director-common 7.4.3+dfsg-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Preparing to unpack .../bacula-director-common_7.4.3+dfsg-2_amd64.deb ...
  Unpacking bacula-director-common (7.4.3+dfsg-2) over (7.4.3+dfsg-1) ...
  Preparing to unpack .../bacula-common_7.4.3+dfsg-2_amd64.deb ...
  Unpacking bacula-common (7.4.3+dfsg-2) over (7.4.3+dfsg-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/bacula-director-sqlite3_7.4.3+dfsg-2_amd64.deb

Same problem in the other bacula-director-* backends.

Does switching between e.g. bacula-director-sqlite3 and bacula-director-mysql
work without problems if both packages ship /etc/init.d/bacula-director?


cheers,

Andreas


bacula-director-sqlite3_7.4.3+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bacula
Source-Version: 7.4.3+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Carsten Leonhardt  (supplier of updated bacula package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Aug 2016 02:41:20 +0200
Source: bacula
Binary: bacula bacula-common bacula-common-sqlite3 bacula-common-pgsql 
bacula-common-mysql bacula-director bacula-director-sqlite3 
bacula-director-mysql bacula-director-pgsql bacula-client bacula-fd 
bacula-server bacula-sd bacula-bscan bacula-console bacula-console-qt
Architecture: source kfreebsd-amd64 all
Version: 7.4.3+dfsg-3
Distribution: experimental
Urgency: medium
Maintainer: Debian Bacula Team 
Changed-By: Carsten Leonhardt 
Description:
 bacula - network backup service - metapackage
 bacula-bscan - network backup service - bscan tool
 bacula-client - network backup service - client metapackage
 bacula-common - network backup service - common support files
 bacula-common-mysql - network backup service - MySQL common files
 bacula-common-pgsql - network backup service - PostgreSQL common files
 bacula-common-sqlite3 - network backup service - SQLite v3 common files
 bacula-console - network backup service - text console
 bacula-console-qt - network backup service - Bacula Administration Tool
 bacula-director - network backup service - Director common files
 bacula-director-mysql - network backup service - MySQL storage 

Bug#830365: marked as done (sympy: FTBFS: Please install the mpmath package with a version >= 0.19)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 18:00:45 +
with message-id 
and subject line Bug#830365: fixed in sympy 1.0-2
has caused the Debian Bug report #830365,
regarding sympy: FTBFS: Please install the mpmath package with a version >= 0.19
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.)


-- 
830365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sympy
Version: 1.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):
>  fakeroot debian/rules clean
> dh  clean --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_auto_clean
> I: pybuild base:184: python2.7 setup.py clean 
> /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running clean
> I: pybuild base:184: python3.5 setup.py clean 
> Please install the mpmath package with a version >= 0.19
> E: pybuild pybuild:274: clean: plugin distutils failed with: exit code=255: 
> python3.5 setup.py clean 
> dh_auto_clean: pybuild --clean -i python{version} -p 3.5 returned exit code 13
> make[1]: *** [override_dh_auto_clean] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/sympy_1.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: sympy
Source-Version: 1.0-2

We believe that the bug you reported is fixed in the latest version of
sympy, 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.
Drew Parsons  (supplier of updated sympy 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, 29 Jul 2016 01:10:39 +0800
Source: sympy
Binary: isympy isympy3 isympy-common python-sympy python3-sympy python-sympy-doc
Architecture: source all
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Drew Parsons 
Changed-By: Drew Parsons 
Description:
 isympy - Python shell for SymPy
 isympy-common - Python shell for SymPy
 isympy3- Python3 shell for SymPy
 python-sympy - Computer Algebra System (CAS) in Python
 python-sympy-doc - Computer Algebra System (CAS) in Python - Documentation
 python3-sympy - Computer Algebra System (CAS) in Python (Python3)
Closes: 827740 829158 830365
Changes:
 sympy (1.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Georges Khaznadar ]
   * added a build-dependency on python3-mpmath. Closes: #830365.
   * Updated Standards-Version to 3.9.8
 .
   [ Drew Parsons ]
   * Build a isympy3 package to handle python3 dependencies.
 The common isympy script is placed in the isympy-common package.
 Uses a /usr/bin/isympy3 wrapper script. Closes: #827740.
   * python-sympy no longer conflicts: python-gmpy2. Closes: #829158.
Checksums-Sha1:
 9c9321e236c5fe9bd3dd4b17a9e20840f2ba84ed 2388 sympy_1.0-2.dsc
 4dc1ab3c4fd82f2da6d05322f2afea4ca7bd4bb3 9272 sympy_1.0-2.debian.tar.xz
 e0d3bea5fed9230803dc0e91ee898b5830d05a15 189056 isympy-common_1.0-2_all.deb
 8391b59cf5f7cbd9c43a3c284331e1ab8d25e514 6658 isympy3_1.0-2_all.deb
 e49dfb3b7de1aa81c47331002c13b643c14a393c 6726 isympy_1.0-2_all.deb
 f214fdc1313d042c4136d9970d3491da01c208cc 4895292 python-sympy-doc_1.0-2_all.deb
 f0eb88133d5a2544a46e21583bcd2ea9824d1838 2366716 python-sympy_1.0-2_all.deb
 dc1e4df4e3a68fa4317654999d75e1cb7c8960cf 2367502 

Bug#827740: marked as done (isympy start fails: No module named sympy.interactive)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 18:00:45 +
with message-id 
and subject line Bug#827740: fixed in sympy 1.0-2
has caused the Debian Bug report #827740,
regarding isympy start fails: No module named sympy.interactive
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.)


-- 
827740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: isympy
Version: 1.0-1
Severity: important

Dear Maintainer,

trying to start isympy fails with the error in the subject line.
  
I have tried to uninstall ipython in case it was a python 2/3
issue, but the result is the same.

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

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

Versions of packages isympy depends on:
ii  python3-sympy1.0-1
pn  python:any | python:any  

Versions of packages isympy recommends:
ii  ipython   2.4.1-1
ii  ipython3  2.4.1-1

isympy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sympy
Source-Version: 1.0-2

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated sympy 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, 29 Jul 2016 01:10:39 +0800
Source: sympy
Binary: isympy isympy3 isympy-common python-sympy python3-sympy python-sympy-doc
Architecture: source all
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Drew Parsons 
Changed-By: Drew Parsons 
Description:
 isympy - Python shell for SymPy
 isympy-common - Python shell for SymPy
 isympy3- Python3 shell for SymPy
 python-sympy - Computer Algebra System (CAS) in Python
 python-sympy-doc - Computer Algebra System (CAS) in Python - Documentation
 python3-sympy - Computer Algebra System (CAS) in Python (Python3)
Closes: 827740 829158 830365
Changes:
 sympy (1.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Georges Khaznadar ]
   * added a build-dependency on python3-mpmath. Closes: #830365.
   * Updated Standards-Version to 3.9.8
 .
   [ Drew Parsons ]
   * Build a isympy3 package to handle python3 dependencies.
 The common isympy script is placed in the isympy-common package.
 Uses a /usr/bin/isympy3 wrapper script. Closes: #827740.
   * python-sympy no longer conflicts: python-gmpy2. Closes: #829158.
Checksums-Sha1:
 9c9321e236c5fe9bd3dd4b17a9e20840f2ba84ed 2388 sympy_1.0-2.dsc
 4dc1ab3c4fd82f2da6d05322f2afea4ca7bd4bb3 9272 sympy_1.0-2.debian.tar.xz
 e0d3bea5fed9230803dc0e91ee898b5830d05a15 189056 isympy-common_1.0-2_all.deb
 8391b59cf5f7cbd9c43a3c284331e1ab8d25e514 6658 isympy3_1.0-2_all.deb
 e49dfb3b7de1aa81c47331002c13b643c14a393c 6726 isympy_1.0-2_all.deb
 f214fdc1313d042c4136d9970d3491da01c208cc 4895292 python-sympy-doc_1.0-2_all.deb
 f0eb88133d5a2544a46e21583bcd2ea9824d1838 2366716 python-sympy_1.0-2_all.deb
 dc1e4df4e3a68fa4317654999d75e1cb7c8960cf 2367502 python3-sympy_1.0-2_all.deb
Checksums-Sha256:
 9430893fee9968dac66c68effb58f6dc13f8bc5f9e4f3e53b3fd0ba4c6757b12 2388 
sympy_1.0-2.dsc
 669aafc08c3f81b305a48199131c331d6bb5a98b0067e1d7b5fb4f69380dafb2 9272 
sympy_1.0-2.debian.tar.xz
 457110fab26310f42ed71d9c6fd95d2fa2b39e73c98375d2bc5d1a5346693a1e 189056 
isympy-common_1.0-2_all.deb
 912f8442dce302e9d2036ef12b2e87d197deae3b2d1d833d0bf3824cc4b124f2 6658 
isympy3_1.0-2_all.deb
 293e939218e86f230eaecc279d15daa3f49a527f5a181b5064bfc25caf9e09d8 6726 
isympy_1.0-2_all.deb
 6f5050f6d7b8a5e26c3c4745c44fb48c4da62800f622b13899a24a0a49081095 4895292 
python-sympy-doc_1.0-2_all.deb
 3bcee4bd1e71ef1c06350017ddb3f4e207b8bf8f0c5e2ca5621f60b6960ac60f 2366716 

Bug#833304: nageru: FTBFS: quicksync_encoder.cpp:996:15: error: 'close' was not declared in this scope

[Chris Lamb]

Source: nageru
Version: 1.3.3-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,

nageru fails to build from source in unstable/amd64:

  [..]

  Setting up libinput-bin (1.4.0-1) ...
  Setting up libbmusb-dev (0.5.1-1) ...
  Setting up ucf (3.0036) ...
  Setting up libzita-resampler1:amd64 (1.3.0-2) ...
  Setting up libopus0:amd64 (1.1.2-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libva1:amd64 (1.7.1-2) ...
  Setting up libasound2:amd64 (1.1.1-2) ...
  Setting up libdrm2:amd64 (2.4.70-1) ...
  Setting up libx265-79:amd64 (1.9-3) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libogg0:amd64 (1.3.2-1) ...
  Setting up libfftw3-quad3:amd64 (3.3.4-2+b1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up libmp3lame0:amd64 (3.99.5+repack1-9+b1) ...
  Setting up libgnutlsxx28:amd64 (3.5.2-2) ...
  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3) ...
  Setting up libusb-1.0-0:amd64 (2:1.0.20-1) ...
  Setting up libcrystalhd3:amd64 (1:0.0~git20110715.fdd2f19-11+b1) ...
  Setting up libgcrypt20-dev (1.7.2-2) ...
  Setting up libepoxy0:amd64 (1.3.1-1) ...
  Setting up libsnappy1v5:amd64 (1.1.3-3) ...
  Setting up libgnutls-openssl27:amd64 (3.5.2-2) ...
  Setting up libusb-1.0-0-dev:amd64 (2:1.0.20-1) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up libreadline-dev:amd64 (6.3-8+b4) ...
  Setting up libzvbi-common (0.2.35-10) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Setting up libfftw3-single3:amd64 (3.3.4-2+b1) ...
  Setting up libxkbcommon0:amd64 (0.5.0-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libva-drm1:amd64 (1.7.1-2) ...
  Setting up liblua5.2-0:amd64 (5.2.4-1) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libmicrohttpd12 (0.9.50-2) ...
  Setting up liborc-0.4-0:amd64 (1:0.4.25-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-1) ...
  Setting up libgme0:amd64 (0.6.0-3) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libzvbi0:amd64 (0.2.35-10+b1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libschroedinger-1.0-0:amd64 (1.0.11-2.1) ...
  Setting up libwebp5:amd64 (0.4.4-1.1) ...
  Setting up libfftw3-long3:amd64 (3.3.4-2+b1) ...
  Setting up libwayland-cursor0:amd64 (1.11.0-2) ...
  Setting up libgsm1:amd64 (1.0.13-4) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libepoxy-dev:amd64 (1.3.1-1) ...
  Setting up libidn11-dev (1.33-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libgmp-dev:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-3) ...
  Setting up libx264-dev:amd64 (2:0.148.2699+gita5e06b9-1) ...
  Setting up libzita-resampler-dev:amd64 (1.3.0-2) ...
  Setting up libasound2-dev:amd64 (1.1.1-2) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-3) ...
  Setting up libfftw3-bin (3.3.4-2+b1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-3) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libwacom2:amd64 (0.19-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.70-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up libva-wayland1:amd64 (1.7.1-2) ...
  Setting up libeigen3-dev (3.3~beta2-1) ...
  Setting up libgbm1:amd64 (11.2.2-1) ...
  Setting up libva-tpi1:amd64 (1.7.1-2) ...
  Setting up libqt5test5:amd64 (5.6.1+dfsg-3) ...
  Setting up libinput10:amd64 (1.4.0-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libmovit4:amd64 (1.3.2-1) ...
  Setting up libdrm-intel1:amd64 (2.4.70-1) ...
  Setting up liblua5.2-dev:amd64 (5.2.4-1) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up libqt5xml5:amd64 (5.6.1+dfsg-3) ...
  Setting up libfftw3-dev:amd64 (3.3.4-2+b1) ...
  Setting up libqt5sql5:amd64 (5.6.1+dfsg-3) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up nettle-dev (3.2-1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libvorbisenc2:amd64 (1.3.5-3) ...
  Setting up libwayland-dev:amd64 (1.11.0-2) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up libqt5concurrent5:amd64 

Bug#833305: jacktrip: FTBFS: RtAudioInterface.h:41:21: fatal error: RtAudio.h: No such file or directory

[Chris Lamb]

Source: jacktrip
Version: 1.1~repack-4
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,

This might be the same as #828951, but jacktrip fails to build from
source in unstable/amd64:

  [..]

  Selecting previously unselected package libpulse0:amd64.
  Preparing to unpack .../libpulse0_9.0-1.1_amd64.deb ...
  Unpacking libpulse0:amd64 (9.0-1.1) ...
  Selecting previously unselected package librtaudio5a:amd64.
  Preparing to unpack .../librtaudio5a_4.1.2~ds0-3_amd64.deb ...
  Unpacking librtaudio5a:amd64 (4.1.2~ds0-3) ...
  Selecting previously unselected package librtaudio-dev:amd64.
  Preparing to unpack .../librtaudio-dev_4.1.2~ds0-3_amd64.deb ...
  Unpacking librtaudio-dev:amd64 (4.1.2~ds0-3) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-4) ...
  Processing triggers for systemd (231-1) ...
  Processing triggers for udev (231-1) ...
  Setting up cdbs (0.4.142) ...
  Setting up libedit2:amd64 (3.1-20150325-1+b1) ...
  Setting up x11proto-dri2-dev (2.8-2) ...
  Setting up libgts-0.7-5:amd64 (0.7.6+darcs121130-1.2) ...
  Setting up libpathplan4 (2.38.0-14) ...
  Setting up libobjc4:amd64 (6.1.1-10) ...
  Setting up libxdot4 (2.38.0-14) ...
  Setting up libasyncns0:amd64 (0.8-6) ...
  Setting up libjack0:amd64 (1:0.124.1+20140122git5013bed0-3) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libwacom-common (0.19-1) ...
  Setting up libevdev2:amd64 (1.5.2+dfsg-1) ...
  Setting up libpng16-16:amd64 (1.6.23-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
  Setting up fonts-dejavu-core (2.36-1) ...
  Setting up libjson-c3:amd64 (0.12-3) ...
  Setting up libasound2-data (1.1.1-2) ...
  Setting up libxshmfence1:amd64 (1.2-1) ...
  Setting up xorg-sgml-doctools (1:1.11-1) ...
  Setting up libwayland-client0:amd64 (1.11.0-2) ...
  Setting up xkb-data (2.17-1) ...
  Setting up qtchooser (58-gfab25f1-1) ...
  Setting up libproxy1v5:amd64 (0.4.11-5) ...
  Setting up uuid-dev:amd64 (2.28-6) ...
  Setting up libdatrie1:amd64 (0.2.10-2) ...
  Setting up libtiff5:amd64 (4.0.6-2) ...
  Setting up x11proto-xf86vidmode-dev (2.3.1-2) ...
  Setting up x11proto-kb-dev (1.0.7-1) ...
  Setting up libglapi-mesa:amd64 (11.2.2-1) ...
  Setting up libinput-bin (1.4.0-1) ...
  Setting up ucf (3.0036) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libasound2:amd64 (1.1.1-2) ...
  Setting up libdrm2:amd64 (2.4.70-1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libogg0:amd64 (1.3.2-1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Setting up libltdl7:amd64 (2.4.6-1) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up help2man (1.47.4) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Setting up libxkbcommon0:amd64 (0.5.0-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-1) ...
  Setting up libthai-data (0.1.25-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libwebp5:amd64 (0.4.4-1.1) ...
  Setting up dh-buildinfo (0.11+nmu1) ...
  Setting up libcdt5 (2.38.0-14) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libllvm3.6v5:amd64 (1:3.6.2-3) ...
  Setting up libwrap0:amd64 (7.6.q-25) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libcgraph6 (2.38.0-14) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up libobjc-5-dev:amd64 (5.4.0-6) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-3) ...
  Setting up libasound2-dev:amd64 (1.1.1-2) ...
  Setting up libjack-dev (1:0.124.1+20140122git5013bed0-3) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-3) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-3) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libwacom2:amd64 (0.19-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.70-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up libgvpr2 (2.38.0-14) ...
  Setting up libgbm1:amd64 (11.2.2-1) ...
  Setting up libqt5test5:amd64 (5.6.1+dfsg-3) ...
  Setting up libflac8:amd64 (1.3.1-4) ...
  Setting up libinput10:amd64 (1.4.0-1) ...
  Setting up libharfbuzz0b:amd64 

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

[Chris Lamb]

> Here is the working patch (attached).

Out of interest, why:

+mode_t prev_mask = umask(0022);
+// Make sure this file is not readable by others
+umask(prev_mask | S_IROTH | S_IWOTH | S_IXOTH);
 FILE *fp = fopen(filename,"w");

.. over, say:

+// Make sure this file is not readable by others
+mode_t prev_mask = umask(S_IXUSR|S_IRWXG|S_IRWXO);
 FILE *fp = fopen(filename,"w");
+umask(prev_mask);

We don't really want to change the umask for the entire process.
Or at least, we don't know the ramifications of that so better to
keep it isolated to just this bit?


Regards,

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

Bug#832843: marked as done (berkshelf-api: FTBFS: ERROR: Test "ruby2.3" failed: /usr/lib/ruby/vendor_ruby/grape/msgpack.rb:39:in `': uninitialized constant Grape::Formatter::Base (Name

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:57:25 +
with message-id 
and subject line Bug#830820: fixed in ruby-grape-msgpack 0.2.0-1
has caused the Debian Bug report #830820,
regarding berkshelf-api: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/vendor_ruby/grape/msgpack.rb:39:in `': 
uninitialized constant Grape::Formatter::Base (NameError)
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.)


-- 
830820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: berkshelf-api
Version: 2.1.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/grape/msgpack.rb:39:in `': 
> uninitialized constant Grape::Formatter::Base (NameError)
> Did you mean?  Base64
>   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 /usr/lib/ruby/vendor_ruby/grape-msgpack.rb:1: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 /«PKGBUILDDIR»/lib/berkshelf/api/endpoint.rb:2:in ` (required)>'
>   from /«PKGBUILDDIR»/lib/berkshelf/api.rb:23:in `require_relative'
>   from /«PKGBUILDDIR»/lib/berkshelf/api.rb:23:in `'
>   from /«PKGBUILDDIR»/lib/berkshelf/api.rb:10:in `'
>   from /«PKGBUILDDIR»/lib/berkshelf/api.rb:9: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 /«PKGBUILDDIR»/spec/spec_helper.rb:3: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 /«PKGBUILDDIR»/spec/unit/berkshelf/api/application_spec.rb:1:in 
> `'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1361:in 
> `load'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1361:in 
> `block in load_spec_files'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1359:in 
> `each'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1359:in 
> `load_spec_files'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:106:in `setup'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:92:in `run'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:78:in `run'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
>   from /usr/bin/rspec:4:in `'
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/28/berkshelf-api_2.1.3-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
ruby-grape-msgpack, 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 Kanashiro  (supplier of updated ruby-grape-msgpack 
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: Tue, 02 Aug 2016 13:04:44 -0300
Source: ruby-grape-msgpack
Binary: ruby-grape-msgpack
Architecture: source all
Version: 0.2.0-1

Bug#831173: marked as done (surf-alggeo: FTBFS with GCC 6: stl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:57:53 +
with message-id 
and subject line Bug#831173: fixed in surf-alggeo 1.0.6+ds-3
has caused the Debian Bug report #831173,
regarding surf-alggeo: FTBFS with GCC 6: stl_algobase.h:243:56: error: macro 
"min" passed 3 arguments, but takes just 2
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.)


-- 
831173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: surf-alggeo
Version: 1.0.6+ds-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++ -DPACKAGE_NAME=\"surf\" -DPACKAGE_TARNAME=\"surf\" 
> -DPACKAGE_VERSION=\"1.0.6\" -DPACKAGE_STRING=\"surf\ 1.0.6\" 
> -DPACKAGE_BUGREPORT=\"endr...@mathematik.uni-mainz.de\" -DPACKAGE_URL=\"\" 
> -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 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 
> -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 
> -DPACKAGE=\"surf\" -DVERSION=\"1.0.6\" -DYYTEXT_POINTER=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 -DHAVE_INSTANTIATIONS=/\*\*/ 
> -DHAVE_FUNCTION_NONTYPE_PARAMETERS=/\*\*/ -DHAVE_PTHREAD_PRIO_INHERIT=1 
> -D_REENTRANT=1 -DNO_GUI=1 -DHAVE_PROGRAM_INVOCATION_SHORT_NAME=1 -I. 
> -I../../../yaccsrc  -I../../../src -I../../../curve -I../../../drawfunc 
> -I../../../draw -I../../../dither -I../../../image-formats -I../../../yaccsrc 
> -I../../../mt -I../../../misc -I../../../debug -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-rtti -fno-exceptions -Wall -W -Wwrite-strings 
> -Wpointer-arith -Wconversion -Wno-unused -Woverloaded-virtual -Wno-deprecated 
> -c -o libsurf_parser_a-ExecuteScriptStruct.o `test -f 
> 'ExecuteScriptStruct.cc' || echo '../../../yaccsrc/'`ExecuteScriptStruct.cc
> In file included from /usr/include/c++/6/bits/char_traits.h:39:0,
>  from /usr/include/c++/6/ios:40,
>  from /usr/include/c++/6/ostream:38,
>  from /usr/include/c++/6/iostream:39,
>  from ../../../yaccsrc/polyx.h:29,
>  from ../../../yaccsrc/hornerarith.h:38,
>  from ../../../src/gui_config.h:47,
>  from ../../../mt/TSDrawingArea.h:32,
>  from ../../../yaccsrc/ExecuteScriptStruct.cc:29:
> /usr/include/c++/6/bits/stl_algobase.h:243:56: error: macro "min" passed 3 
> arguments, but takes just 2
>  min(const _Tp& __a, const _Tp& __b, _Compare __comp)
> ^
> /usr/include/c++/6/bits/stl_algobase.h:265:56: error: macro "max" passed 3 
> arguments, but takes just 2
>  max(const _Tp& __a, const _Tp& __b, _Compare __comp)
> ^
> In file included from ../../../src/RgbBuffer.h:65:0,
>  from ../../../mt/TSDrawingArea.h:31,
>  from ../../../yaccsrc/ExecuteScriptStruct.cc:29:
> ../../../src/color.h: In member function 'unsigned char 
> colorrgb::getRedByte() const':
> ../../../src/color.h:47:22: warning: conversion to 'unsigned char' from 'int' 
> may alter its value [-Wconversion]
> return red >= 1.0 ? 255: (int) (red*255);
>~~~^~
> ../../../src/color.h: In member function 'unsigned char 
> colorrgb::getGreenByte() const':
> ../../../src/color.h:52:24: warning: conversion to 'unsigned char' from 'int' 
> may alter its value [-Wconversion]
> return green >= 1.0 ? 255: (int) (green*255);
>~^~~~
> ../../../src/color.h: In member function 'unsigned char 
> colorrgb::getBlueByte() const':
> ../../../src/color.h:57:23: warning: conversion to 'unsigned char' from 'int' 
> may alter its value [-Wconversion]
> return blue >= 1.0 ? 255: (int) (blue*255);
>^~~
> In file included from ../../../src/gui_config.h:42:0,
>  from 

Bug#831539: marked as done (ruby-berkshelf-api-client: FTBFS: grape/msgpack.rb:39:in `': uninitialized constant Grape::Formatter::Base (NameError))

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:57:25 +
with message-id 
and subject line Bug#830820: fixed in ruby-grape-msgpack 0.2.0-1
has caused the Debian Bug report #830820,
regarding ruby-berkshelf-api-client: FTBFS: grape/msgpack.rb:39:in `': uninitialized constant Grape::Formatter::Base (NameError)
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.)


-- 
830820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-berkshelf-api-client
Version: 2.0.2-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,

ruby-berkshelf-api-client fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../ruby-buff-ruby-engine_0.1.0-2_all.deb ...
  Unpacking ruby-buff-ruby-engine (0.1.0-2) ...
  Selecting previously unselected package ruby-buff-shell-out.
  Preparing to unpack .../ruby-buff-shell-out_0.2.0-1_all.deb ...
  Unpacking ruby-buff-shell-out (0.2.0-1) ...
  Selecting previously unselected package ruby-mixlib-shellout.
  Preparing to unpack .../ruby-mixlib-shellout_2.2.6-1_all.deb ...
  Unpacking ruby-mixlib-shellout (2.2.6-1) ...
  Selecting previously unselected package ruby-mixlib-config.
  Preparing to unpack .../ruby-mixlib-config_2.2.1-1_all.deb ...
  Unpacking ruby-mixlib-config (2.2.1-1) ...
  Selecting previously unselected package ruby-fuzzyurl.
  Preparing to unpack .../ruby-fuzzyurl_0.8.0-1_all.deb ...
  Unpacking ruby-fuzzyurl (0.8.0-1) ...
  Selecting previously unselected package ruby-chef-config.
  Preparing to unpack .../ruby-chef-config_12.10.24-1_all.deb ...
  Unpacking ruby-chef-config (12.10.24-1) ...
  Selecting previously unselected package ruby-erubis.
  Preparing to unpack .../ruby-erubis_2.7.0-3_all.deb ...
  Unpacking ruby-erubis (2.7.0-3) ...
  Selecting previously unselected package ruby-httpclient.
  Preparing to unpack .../ruby-httpclient_2.7.1-1_all.deb ...
  Unpacking ruby-httpclient (2.7.1-1) ...
  Selecting previously unselected package ruby-mixlib-log.
  Preparing to unpack .../ruby-mixlib-log_1.6.0-1_all.deb ...
  Unpacking ruby-mixlib-log (1.6.0-1) ...
  Selecting previously unselected package ruby-mixlib-authentication.
  Preparing to unpack .../ruby-mixlib-authentication_1.4.1-1_all.deb ...
  Unpacking ruby-mixlib-authentication (1.4.1-1) ...
  Selecting previously unselected package ruby-retryable.
  Preparing to unpack .../ruby-retryable_2.0.1-1_all.deb ...
  Unpacking ruby-retryable (2.0.1-1) ...
  Selecting previously unselected package ruby-semverse.
  Preparing to unpack .../ruby-semverse_1.2.1-2_all.deb ...
  Unpacking ruby-semverse (1.2.1-2) ...
  Selecting previously unselected package ruby-ridley.
  Preparing to unpack .../ruby-ridley_4.4.3-2_all.deb ...
  Unpacking ruby-ridley (4.4.3-2) ...
  Selecting previously unselected package berkshelf-api.
  Preparing to unpack .../berkshelf-api_2.1.3-1_all.deb ...
  Unpacking berkshelf-api (2.1.3-1) ...
  Selecting previously unselected package ruby-diff-lcs.
  Preparing to unpack .../ruby-diff-lcs_1.2.5-2_all.deb ...
  Unpacking ruby-diff-lcs (1.2.5-2) ...
  Selecting previously unselected package ruby-rspec-support.
  Preparing to unpack .../ruby-rspec-support_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-support (3.4.0c3e0m1s1-1) ...
  Selecting previously unselected package ruby-rspec-expectations.
  Preparing to unpack .../ruby-rspec-expectations_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-expectations (3.4.0c3e0m1s1-1) ...
  Selecting previously unselected package ruby-rspec-mocks.
  Preparing to unpack .../ruby-rspec-mocks_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-mocks (3.4.0c3e0m1s1-1) ...
  Selecting previously unselected package ruby-thread-order.
  Preparing to unpack .../ruby-thread-order_1.1.0-1_all.deb ...
  Unpacking ruby-thread-order (1.1.0-1) ...
  Selecting previously unselected package ruby-rspec-core.
  Preparing to unpack .../ruby-rspec-core_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-core (3.4.0c3e0m1s1-1) ...
  Selecting previously unselected package ruby-rspec.
  Preparing to unpack .../ruby-rspec_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec (3.4.0c3e0m1s1-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-1) ...
  Setting up ruby-did-you-mean (1.0.0-2) ...
  Setting up libyaml-0-2:amd64 (0.1.6-3) ...
  Setting up libhttp-parser2.1:amd64 

Bug#830820: marked as done (ruby-grape-msgpack: FTBFS: grape/msgpack.rb:39:in `': uninitialized constant Grape::Formatter::Base (NameError))

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:57:25 +
with message-id 
and subject line Bug#830820: fixed in ruby-grape-msgpack 0.2.0-1
has caused the Debian Bug report #830820,
regarding ruby-grape-msgpack: FTBFS: grape/msgpack.rb:39:in `': 
uninitialized constant Grape::Formatter::Base (NameError)
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.)


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

ruby-grape-msgpack fails to build from source in unstable/amd64:

  [..]

  Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
  Selecting previously unselected package libruby2.3:amd64.
  Preparing to unpack .../libruby2.3_2.3.1-5_amd64.deb ...
  Unpacking libruby2.3:amd64 (2.3.1-5) ...
  Selecting previously unselected package ruby2.3.
  Preparing to unpack .../ruby2.3_2.3.1-5_amd64.deb ...
  Unpacking ruby2.3 (2.3.1-5) ...
  Selecting previously unselected package ruby.
  Preparing to unpack .../ruby_1%3a2.3.0+4_amd64.deb ...
  Unpacking ruby (1:2.3.0+4) ...
  Selecting previously unselected package rake.
  Preparing to unpack .../archives/rake_10.5.0-2_all.deb ...
  Unpacking rake (10.5.0-2) ...
  Selecting previously unselected package gem2deb-test-runner.
  Preparing to unpack .../gem2deb-test-runner_0.31_amd64.deb ...
  Unpacking gem2deb-test-runner (0.31) ...
  Selecting previously unselected package libgmpxx4ldbl:amd64.
  Preparing to unpack .../libgmpxx4ldbl_2%3a6.1.1+dfsg-1_amd64.deb ...
  Unpacking libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ...
  Selecting previously unselected package libgmp-dev:amd64.
  Preparing to unpack .../libgmp-dev_2%3a6.1.1+dfsg-1_amd64.deb ...
  Unpacking libgmp-dev:amd64 (2:6.1.1+dfsg-1) ...
  Selecting previously unselected package ruby2.3-dev:amd64.
  Preparing to unpack .../ruby2.3-dev_2.3.1-5_amd64.deb ...
  Unpacking ruby2.3-dev:amd64 (2.3.1-5) ...
  Selecting previously unselected package ruby-all-dev:amd64.
  Preparing to unpack .../ruby-all-dev_1%3a2.3.0+4_amd64.deb ...
  Unpacking ruby-all-dev:amd64 (1:2.3.0+4) ...
  Selecting previously unselected package ruby-setup.
  Preparing to unpack .../ruby-setup_3.4.1-9_all.deb ...
  Unpacking ruby-setup (3.4.1-9) ...
  Selecting previously unselected package gem2deb.
  Preparing to unpack .../gem2deb_0.31_amd64.deb ...
  Unpacking gem2deb (0.31) ...
  Selecting previously unselected package ruby-i18n.
  Preparing to unpack .../ruby-i18n_0.7.0-2_all.deb ...
  Unpacking ruby-i18n (0.7.0-2) ...
  Selecting previously unselected package ruby-json.
  Preparing to unpack .../ruby-json_1.8.3-1+b3_amd64.deb ...
  Unpacking ruby-json (1.8.3-1+b3) ...
  Selecting previously unselected package ruby-atomic.
  Preparing to unpack .../ruby-atomic_1.1.16-2+b6_amd64.deb ...
  Unpacking ruby-atomic (1.1.16-2+b6) ...
  Selecting previously unselected package ruby-thread-safe.
  Preparing to unpack .../ruby-thread-safe_0.3.5-3_all.deb ...
  Unpacking ruby-thread-safe (0.3.5-3) ...
  Selecting previously unselected package ruby-tzinfo.
  Preparing to unpack .../ruby-tzinfo_1.2.2-1_all.deb ...
  Unpacking ruby-tzinfo (1.2.2-1) ...
  Selecting previously unselected package ruby-activesupport.
  Preparing to unpack .../ruby-activesupport_2%3a4.2.6-1_all.deb ...
  Unpacking ruby-activesupport (2:4.2.6-1) ...
  Selecting previously unselected package ruby-blankslate.
  Preparing to unpack .../ruby-blankslate_3.1.3-1_all.deb ...
  Unpacking ruby-blankslate (3.1.3-1) ...
  Selecting previously unselected package ruby-builder.
  Preparing to unpack .../ruby-builder_3.2.2-4_all.deb ...
  Unpacking ruby-builder (3.2.2-4) ...
  Selecting previously unselected package ruby-hashie.
  Preparing to unpack .../ruby-hashie_3.4.4-1_all.deb ...
  Unpacking ruby-hashie (3.4.4-1) ...
  Selecting previously unselected package ruby-multi-json.
  Preparing to unpack .../ruby-multi-json_1.11.2-3_all.deb ...
  Unpacking ruby-multi-json (1.11.2-3) ...
  Selecting previously unselected package ruby-multi-xml.
  Preparing to unpack .../ruby-multi-xml_0.5.5-2_all.deb ...
  Unpacking ruby-multi-xml (0.5.5-2) ...
  Selecting previously unselected package ruby-mustermann19.
  Preparing to unpack .../ruby-mustermann19_0.4.3+git20160621-1_all.deb ...
  Unpacking ruby-mustermann19 (0.4.3+git20160621-1) ...
  Selecting previously 

Bug#831075: marked as done (imview: FTBFS with GCC 6: interpreter.cxx:1454:27: error: reference to 'move' is ambiguous)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:55:20 +
with message-id 
and subject line Bug#831075: fixed in imview 1.1.9c-17
has caused the Debian Bug report #831075,
regarding imview: FTBFS with GCC 6: interpreter.cxx:1454:27: error: reference 
to 'move' 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.)


-- 
831075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imview
Version: 1.1.9c-16
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++  -D_REENTRANT -DLinux -Wdate-time -D_FORTIFY_SOURCE=2 -I.   
> -I/usr/include -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 
> -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/x86_64-linux-gnu//ImageMagick-6 
> -I/usr/include/ImageMagick-6 -O2 -Wall -Wno-return-type -Wno-unknown-pragmas 
> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I.. -I.. -c 
> interpreter.cxx
> interpreter.cxx: In member function 'int 
> linkmanager::getresponse(TCPClientStream*)':
> interpreter.cxx:1345:49: warning: suggest parentheses around assignment used 
> as truth value [-Wparentheses]
>  while (run = getline(*stream, message).good())  {
>  ^
> interpreter.cxx: In constructor 'interpreter::interpreter()':
> interpreter.cxx:1454:27: error: reference to 'move' is ambiguous
>  tokens["move"]  = new move;
>^~~~
> In file included from interpreter.cxx:78:0:
> interpreter.hxx:141:7: note: candidates are: class move
>  class move:public action {
>^~~~
> In file included from /usr/include/c++/6/deque:64:0,
>  from /usr/include/c++/6/queue:60,
>  from asynchat.hxx:66,
>  from imserver.hxx:50,
>  from interpreter.hxx:66,
>  from interpreter.cxx:78:
> /usr/include/c++/6/bits/stl_deque.h:422:5: note: 
> template std::_Deque_iterator<_Tp, _Tp&, _Tp*> 
> std::move(std::_Deque_iterator<_Tp, _Tp&, _Tp*>, std::_Deque_iterator<_Tp, 
> _Tp&, _Tp*>, std::_Deque_iterator<_Tp, _Tp&, _Tp*>)
>  move(_Deque_iterator<_Tp, _Tp&, _Tp*> __first,
>  ^~~~
> In file included from /usr/include/c++/6/deque:66:0,
>  from /usr/include/c++/6/queue:60,
>  from asynchat.hxx:66,
>  from imserver.hxx:50,
>  from interpreter.hxx:66,
>  from interpreter.cxx:78:
> /usr/include/c++/6/bits/deque.tcc:1032:5: note: 
> template std::_Deque_iterator<_Tp, _Tp&, _Tp*> 
> std::move(std::_Deque_iterator<_Tp, const _Tp&, const _Tp*>, 
> std::_Deque_iterator<_Tp, const _Tp&, const _Tp*>, std::_Deque_iterator<_Tp, 
> _Tp&, _Tp*>)
>  move(_Deque_iterator<_Tp, const _Tp&, const _Tp*> __first,
>  ^~~~
> In file included from /usr/include/c++/6/bits/char_traits.h:39:0,
>  from /usr/include/c++/6/string:40,
>  from ../imview.hxx:53,
>  from interpreter.cxx:52:
> /usr/include/c++/6/bits/stl_algobase.h:479:5: note: 
> template _OI std::move(_II, _II, _OI)
>  move(_II __first, _II __last, _OI __result)
>  ^~~~
> In file included from /usr/include/c++/6/bits/stl_pair.h:59:0,
>  from /usr/include/c++/6/bits/stl_algobase.h:64,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from ../imview.hxx:53,
>  from interpreter.cxx:52:
> /usr/include/c++/6/bits/move.h:101:5: note: template _Tp> constexpr typename std::remove_reference<  
> >::type&& std::move(_Tp&&)
>  move(_Tp&& __t) noexcept
>  ^~~~
> make[2]: *** [interpreter.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/imview_1.1.9c-16_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 

Processed: Re: libavcodec57: broken option parsing with LANGs with decimal mark different from .

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #831529 [libavcodec57] libavcodec57: broken option parsing with LANGs with 
decimal mark different from .
Bug #831909 [libavcodec57] libavcodec57: broken option parsing with LANGs with 
decimal mark different from .
Bug #832964 [libavcodec57] libavcodec57: Error in libavcodec.so.57 crashes 
radiotray
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.

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

Bug#831529: libavcodec57: broken option parsing with LANGs with decimal mark different from .

[Sebastian Ramacher]

Control: tags -1 + patch

Hi Carl

On 2016-08-02 17:51:47, Carl Eugen Hoyos wrote:
> Please someone test attached patch, I cannot reproduce on any of my systems.

The patch fixes the issue here.

Cheers

> diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
> index 979cf37..5bed4e4 100644
> --- a/libavcodec/vaapi_encode_h264.c
> +++ b/libavcodec/vaapi_encode_h264.c
> @@ -1323,10 +1323,10 @@ static const AVCodecDefault 
> vaapi_encode_h264_defaults[] = {
>  { "b",  "0"   },
>  { "bf", "2"   },
>  { "g",  "120" },
> -{ "i_qfactor",  "1.0" },
> -{ "i_qoffset",  "0.0" },
> -{ "b_qfactor",  "1.2" },
> -{ "b_qoffset",  "0.0" },
> +{ "i_qfactor",  "1"   },
> +{ "i_qoffset",  "0"   },
> +{ "b_qfactor",  "6/5" },
> +{ "b_qoffset",  "0"   },
>  { NULL },
>  };
>  
> diff --git a/libavcodec/vaapi_encode_h265.c b/libavcodec/vaapi_encode_h265.c
> index 1ef968c..45f6f6d 100644
> --- a/libavcodec/vaapi_encode_h265.c
> +++ b/libavcodec/vaapi_encode_h265.c
> @@ -1341,10 +1341,10 @@ static const AVCodecDefault 
> vaapi_encode_h265_defaults[] = {
>  { "b",  "0"   },
>  { "bf", "2"   },
>  { "g",  "120" },
> -{ "i_qfactor",  "1.0" },
> -{ "i_qoffset",  "0.0" },
> -{ "b_qfactor",  "1.2" },
> -{ "b_qoffset",  "0.0" },
> +{ "i_qfactor",  "1"   },
> +{ "i_qoffset",  "0"   },
> +{ "b_qfactor",  "6/5" },
> +{ "b_qoffset",  "0"   },
>  { NULL },
>  };
>  


-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#817884: marked as done (mpi4py: FTBFS: AssertionError: False is not true)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:21:39 +
with message-id 
and subject line Bug#817884: fixed in mpi4py 2.0.0-2
has caused the Debian Bug report #817884,
regarding mpi4py: FTBFS: AssertionError: False is not true
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.)


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

mpi4py fails to build from source in unstable/amd64:

  [..]

  testGetGroup (test_win.TestWinCreateWorld) ... ok
  testGetSetErrhandler (test_win.TestWinCreateWorld) ... ok
  testGetSetInfo (test_win.TestWinCreateWorld) ... ok
  testGetSetName (test_win.TestWinCreateWorld) ... ok
  testMemory (test_win.TestWinCreateWorld) ... ok
  testMemoryModel (test_win.TestWinCreateWorld) ... ok
  
  ==
  FAIL: testDL1 (test_dl.TestDL)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160311084051.TDWc8pX5SV/mpi4py-2.0.0/test/test_dl.py", 
line 18, in testDL1
  self.assertTrue(handle != 0)
  AssertionError: False is not true
  
  --
  Ran 1007 tests in 7.521s
  
  FAILED (failures=1)
  debian/rules:89: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160311084051.TDWc8pX5SV/mpi4py-2.0.0'
  debian/rules:22: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


mpi4py.2.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 2.0.0-2

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated mpi4py 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: Tue, 02 Aug 2016 10:42:00 -0400
Source: mpi4py
Binary: python-mpi4py python-mpi4py-dbg python3-mpi4py python3-mpi4py-dbg 
python-mpi4py-doc
Architecture: source amd64 all
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-mpi4py - bindings of the Message Passing Interface (MPI) standard
 python-mpi4py-dbg - bindings of the MPI standard -- debug symbols
 python-mpi4py-doc - bindings of the MPI standard -- documentation
 python3-mpi4py - bindings of the Message Passing Interface (MPI) standard
 python3-mpi4py-dbg - bindings of the MPI standard -- debug symbols
Closes: 805301 817884
Changes:
 mpi4py (2.0.0-2) unstable; urgency=medium
 .
   * Point to libm.so.6 in the test, not libm.so (Closes: #817884)
 (Thanks Alastair McKinstry)
   * Removed dangling symlink /usr/include/mpi4py.  include/ is symlinked
 for each python version under /usr/include/python*.*/mpi4py/
 (Closes: #805301)
Checksums-Sha1:
 83bbcdec6d2b0af22bb7c28eda4d6b180fc78aef 2384 mpi4py_2.0.0-2.dsc
 e2f540f9ce799c1592498f4b1176f42a9d752c43 7712 mpi4py_2.0.0-2.debian.tar.xz
 2707fb716ef84e83598c6dc212a15a9eaba71ef2 955722 
python-mpi4py-dbg_2.0.0-2_amd64.deb
 457892d3c7a2f8ab0560fc49c9df9f3a44e8b89d 55362 
python-mpi4py-doc_2.0.0-2_all.deb
 d37a73c265a072ea05c6df35306168c8f729bb1b 416334 python-mpi4py_2.0.0-2_amd64.deb
 269a60ae8fca1bfa36ecab0d7f4ceaf9f638 1101880 
python3-mpi4py-dbg_2.0.0-2_amd64.deb
 a22156e5a52d430997bfd7be1688f933262f32f5 412650 

Processed: tagging 832656, tagging 816988, tagging 806879, tagging 806658, tagging 806657, tagging 806654 ...

[Debian Bug Tracking System]

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

> tags 832656 + sid stretch
Bug #832656 [bcron] runit: breaks users of runit: ln: failed to create symbolic 
link '/etc/service/bcron-sched': No such file or directory
Added tag(s) sid and stretch.
> tags 816988 + sid
Bug #816988 [src:seqan] seqan: FTBFS when built with dpkg-buildpackage -A (No 
such file or directory)
Added tag(s) sid.
> tags 806879 + sid stretch
Bug #806879 [src:xsp] xsp: FTBFS when built with dpkg-buildpackage -A 
(dh_clideps fails)
Added tag(s) stretch and sid.
> tags 806658 + sid stretch
Bug #806658 [src:sofia-sip] sofia-sip: FTBFS when built with dpkg-buildpackage 
-A (No such file or directory)
Added tag(s) sid and stretch.
> tags 806657 + sid stretch
Bug #806657 [src:love] love: FTBFS when built with dpkg-buildpackage -A 
(dh_install: love-doc missing files)
Added tag(s) stretch and sid.
> tags 806654 + sid stretch
Bug #806654 [src:libtool] libtool: FTBFS in stretch when built with 
"dpkg-buildpackage -A"
Added tag(s) sid and stretch.
> tags 806629 + sid stretch
Bug #806629 [src:libkarma] libkarma: FTBFS when built with dpkg-buildpackage -A 
(dh_clideps fails)
Added tag(s) sid and stretch.
> tags 806616 + sid stretch
Bug #806616 [src:fftw3] fftw3: FTBFS when built with dpkg-buildpackage -A 
(build-indep fails)
Added tag(s) stretch and sid.
> tags 806127 + sid stretch
Bug #806127 [src:zope2.13] zope2.13: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) stretch and sid.
> tags 806604 + sid stretch
Bug #806604 [src:aubio] aubio: FTBFS when built with dpkg-buildpackage -A (No 
such file or directory)
Added tag(s) sid and stretch.
> tags 806117 + sid stretch
Bug #806117 [src:the] the: FTBFS when built with dpkg-buildpackage -A (No such 
file or directory)
Added tag(s) stretch and sid.
> tags 806114 + sid stretch
Bug #806114 [src:tacacs+] tacacs+: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) sid and stretch.
> tags 806100 + sid stretch
Bug #806100 [src:pyviennacl] pyviennacl: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Added tag(s) stretch and sid.
> tags 806092 + sid stretch
Bug #806092 [src:pcb] pcb: FTBFS when built with dpkg-buildpackage -A (No such 
file or directory)
Added tag(s) sid and stretch.
> tags 806055 + sid
Bug #806055 [src:libaria] libaria: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) sid.
> tags 806049 + sid stretch
Bug #806049 [src:indigo] indigo: FTBFS when built with dpkg-buildpackage -A (No 
such file or directory)
Added tag(s) sid and stretch.
> tags 806046 + sid stretch
Bug #806046 [src:horgand] horgand: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) sid and stretch.
> tags 806040 + sid stretch
Bug #806040 [src:gtkglext] gtkglext: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) sid and stretch.
> tags 806034 + sid stretch
Bug #806034 [src:gmpc] gmpc: FTBFS when built with dpkg-buildpackage -A (No 
such file or directory)
Added tag(s) sid and stretch.
> tags 806019 + sid stretch
Bug #806019 [src:e17] e17: FTBFS when built with dpkg-buildpackage -A (No such 
file or directory)
Added tag(s) sid and stretch.
> tags 806018 + sid stretch
Bug #806018 [src:docbook-xsl-saxon] docbook-xsl-saxon: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Added tag(s) stretch and sid.
> tags 806005 + sid stretch
Bug #806005 [src:charmap.app] charmap.app: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Added tag(s) sid and stretch.
> tags 805988 + sid stretch
Bug #805988 [src:aboot] aboot: FTBFS on amd64 when built with dpkg-buildpackage 
-A
Added tag(s) sid and stretch.
> tags 805961 + sid stretch
Bug #805961 [src:toilet] toilet: FTBFS when built with dpkg-buildpackage -A (no 
binary artifacts)
Added tag(s) stretch and sid.
> tags 805957 + sid
Bug #805957 [src:pidgin-hotkeys] pidgin-hotkeys: FTBFS when built with 
dpkg-buildpackage -A (no binary artifacts)
Added tag(s) sid.
> tags 805953 + sid
Bug #805953 [src:noiz2sa] noiz2sa: FTBFS when built with dpkg-buildpackage -A 
(no binary artifacts)
Added tag(s) sid.
> tags 805952 + sid
Bug #805952 [src:mysqmail] mysqmail: FTBFS when built with dpkg-buildpackage -A 
(no binary artifacts)
Added tag(s) sid.
> tags 805951 + sid
Bug #805951 [src:music] music: FTBFS when built with dpkg-buildpackage -A (no 
binary artifacts)
Added tag(s) sid.
> tags 805947 + sid stretch
Bug #805947 [src:libforms] libforms: FTBFS when built with dpkg-buildpackage -A 
(no binary artifacts)
Added tag(s) stretch and sid.
> tags 805943 + sid stretch
Bug #805943 [src:hocr] hocr: FTBFS when built with dpkg-buildpackage -A (no 
binary artifacts)
Added tag(s) sid and stretch.
> tags 833258 + sid stretch
Bug #833258 [gufw] [gufw] Application Segfaults on Newer KDE/QT
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

Please contact me if you need 

Bug#826197: marked as done (discount: FTBFS on many architectures: 1 test failed)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 16:19:41 +
with message-id 
and subject line Bug#826197: fixed in discount 2.2.0+git20160802-1
has caused the Debian Bug report #826197,
regarding discount: FTBFS on many architectures: 1 test failed
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.)


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

Hi,

discount FTBFS on arm* ppc* s390x:
https://buildd.debian.org/status/package.php?p=discount=unstable

   dh_auto_test -a
make -j1 test
make[1]: Entering directory '/«PKGBUILDDIR»'
headers ... GOOD
Reddit-style automatic links . OK
automatic links .. OK
backslash escapes  OK
callbacks  OK
code blocks .. OK
markdown 1.0 compatibility ... OK
crashes .. OK
reported defects . OK
%div% blocks . OK
definition lists . OK
emphasis . OK
markdown extra-style footnotes ... OK
paragraph flow ... OK
footnotes  OK
github tags .. OK
headers .. OK
html blocks .. OK
html5 blocks (mkd_with_html5_tags) ... OK
html comments  OK
embedded links ... OK
embedded images .. OK
lists  OK
deeply nested lists .. OK
misc . OK
data corruption cases from Fernando Muñoz 
id_000108_06
source:
 

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 830820 ruby-grape-msgpack
Bug #830820 [src:ruby-grape-msgpack] ruby-grape-msgpack: FTBFS: 
grape/msgpack.rb:39:in `': uninitialized constant 
Grape::Formatter::Base (NameError)
Bug reassigned from package 'src:ruby-grape-msgpack' to 'ruby-grape-msgpack'.
No longer marked as found in versions ruby-grape-msgpack/0.1.2-2.
Ignoring request to alter fixed versions of bug #830820 to the same values 
previously set
> merge 830820 831539 832843
Bug #830820 [ruby-grape-msgpack] ruby-grape-msgpack: FTBFS: 
grape/msgpack.rb:39:in `': uninitialized constant 
Grape::Formatter::Base (NameError)
Bug #830820 [ruby-grape-msgpack] ruby-grape-msgpack: FTBFS: 
grape/msgpack.rb:39:in `': uninitialized constant 
Grape::Formatter::Base (NameError)
Added tag(s) sid and stretch.
Bug #831539 [ruby-grape-msgpack] ruby-berkshelf-api-client: FTBFS: 
grape/msgpack.rb:39:in `': uninitialized constant 
Grape::Formatter::Base (NameError)
Added tag(s) stretch and sid.
Bug #832843 [ruby-grape-msgpack] berkshelf-api: FTBFS: ERROR: Test "ruby2.3" 
failed: /usr/lib/ruby/vendor_ruby/grape/msgpack.rb:39:in `': 
uninitialized constant Grape::Formatter::Base (NameError)
Merged 830820 831539 832843
> thanks
Stopping processing here.

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

Bug#831529: libavcodec57: broken option parsing with LANGs with decimal mark different from .

[Carl Eugen Hoyos]

Hi!

Please someone test attached patch, I cannot reproduce on any of my systems.

Thank you, Carl Eugen
diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
index 979cf37..5bed4e4 100644
--- a/libavcodec/vaapi_encode_h264.c
+++ b/libavcodec/vaapi_encode_h264.c
@@ -1323,10 +1323,10 @@ static const AVCodecDefault 
vaapi_encode_h264_defaults[] = {
 { "b",  "0"   },
 { "bf", "2"   },
 { "g",  "120" },
-{ "i_qfactor",  "1.0" },
-{ "i_qoffset",  "0.0" },
-{ "b_qfactor",  "1.2" },
-{ "b_qoffset",  "0.0" },
+{ "i_qfactor",  "1"   },
+{ "i_qoffset",  "0"   },
+{ "b_qfactor",  "6/5" },
+{ "b_qoffset",  "0"   },
 { NULL },
 };
 
diff --git a/libavcodec/vaapi_encode_h265.c b/libavcodec/vaapi_encode_h265.c
index 1ef968c..45f6f6d 100644
--- a/libavcodec/vaapi_encode_h265.c
+++ b/libavcodec/vaapi_encode_h265.c
@@ -1341,10 +1341,10 @@ static const AVCodecDefault 
vaapi_encode_h265_defaults[] = {
 { "b",  "0"   },
 { "bf", "2"   },
 { "g",  "120" },
-{ "i_qfactor",  "1.0" },
-{ "i_qoffset",  "0.0" },
-{ "b_qfactor",  "1.2" },
-{ "b_qoffset",  "0.0" },
+{ "i_qfactor",  "1"   },
+{ "i_qoffset",  "0"   },
+{ "b_qfactor",  "6/5" },
+{ "b_qoffset",  "0"   },
 { NULL },
 };
 

Processed (with 1 error): reassign

[Debian Bug Tracking System]

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

> reassign 831539 ruby-grape-msgpack
Bug #831539 [src:ruby-berkshelf-api-client] ruby-berkshelf-api-client: FTBFS: 
grape/msgpack.rb:39:in `': uninitialized constant 
Grape::Formatter::Base (NameError)
Bug reassigned from package 'src:ruby-berkshelf-api-client' to 
'ruby-grape-msgpack'.
No longer marked as found in versions ruby-berkshelf-api-client/2.0.2-1.
Ignoring request to alter fixed versions of bug #831539 to the same values 
previously set
> reassign 832843 ruby-grape-msgpack
Bug #832843 [src:berkshelf-api] berkshelf-api: FTBFS: ERROR: Test "ruby2.3" 
failed: /usr/lib/ruby/vendor_ruby/grape/msgpack.rb:39:in `': 
uninitialized constant Grape::Formatter::Base (NameError)
Bug reassigned from package 'src:berkshelf-api' to 'ruby-grape-msgpack'.
No longer marked as found in versions berkshelf-api/2.1.3-1.
Ignoring request to alter fixed versions of bug #832843 to the same values 
previously set
> merge 830820 831539 832843
Bug #830820 [src:ruby-grape-msgpack] ruby-grape-msgpack: FTBFS: 
grape/msgpack.rb:39:in `': uninitialized constant 
Grape::Formatter::Base (NameError)
Unable to merge bugs because:
package of #831539 is 'ruby-grape-msgpack' not 'src:ruby-grape-msgpack'
package of #832843 is 'ruby-grape-msgpack' not 'src:ruby-grape-msgpack'
Failed to merge 830820: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Re: Bug#819835: [src:dico] dico: FTBFS in testing (test suite fails)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +help
Bug #819835 [src:dico] dico: FTBFS in testing (test suite fails)
Added tag(s) help.

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

Bug#819835: [src:dico] dico: FTBFS in testing (test suite fails)

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tag -1 +help

On Tue, 2016-08-02 at 15:22 +0200, Santiago Vila wrote:
> Before disabling all the tests, I would try to find the way to disable
> the tests that fail, and only those. That's usually considered better
> than disabling all the tests.
> 

My initial attempt to disable the specific test didn't work. But I'll admit I'm
not much versed with guile and haven't spent much time to figure that out. I
hope the upstream folks respond, because the same guile patch is there in the
upstream repository too.

> Also, if the maintainer is MIA, try contacting the MIA team.

I really don't know. His last uploads were from around Aug/Sep, 2015. So he
isn't like that long inactive.

But I haven't heard from him for my emails. My most recent attempt to reach him
out (last week) resulted in bounced emails. I hope he's fine.

Let's ensure we don't get this kicked out of Debian testing. If nothing works,
disabling the tests may be the last available option.

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXoLghAAoJEKY6WKPy4XVpiKAQAJLIZ8qSKdPZh3gn1MiuXner
+mr/Vpz2G/wcHcr3/XCmsXXEvs7VA/baICJ8k5qNxu9g8iypVjd8dgHKcJ9hJCcu
3Oo3+HKXvL0ipoAMCw62v9ydMCwROMNz4/SB0pU9u6Hu8Eoegda+cC47jfSzla+S
vQW3BCL038gpN6zUpQbmqmehk0tPS6+DagcWRh/TADmVLBubGCXPop88D1Qrraqw
NMQEfNAiXpa5T6HWYqAewjSiSy5/ouKtF9lIOzhDwu9cSZgH2Lt4SzO4BFJ6rfwu
LrtRgFjE8aXkTq4U1TZBWmX+RKrZKBfiH7Drt/8q0hN2+1nu8bQPFZl6M8xU9/et
PJlGvjsYlJvjA3+3pCdHfv8y/Z5YYEjXGIgnaJhMUqFLx1myvWL8hFsg5P29VxKj
2340j6S3woKZAM6YBqcrwHzMhHwUDhQmfL7NDHCDnkRYdJHzPYXo5JmZH30oB4Qu
sM3kC5DxvnSKDPDPaQ64CnyuXbdTdYFiTb+cTGy5zvFDug4aaqnEpgv3xyiQrHko
hkThENoi9xvDB4ZSsar/2eIdM773v8UKUnER5cMrRHKFSGks8noncca+Zu5b26S7
NA6awUuF+BUJUQYZ3cCZjC2KnTCcTOEldZ9U+Nw+uasj/q9GTEnynndiexpUD9aY
OoIfsH6AfF0cTUi0YB/5
=agcB
-END PGP SIGNATURE-

Bug#833288: would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'

[Yaroslav Halchenko]

Package: macs
Version: 2.1.1.20160309-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

I have just uploaded cython 0.24.1 into sid and while testing reverse build
depends found that macs fails to build.  Here is the log extract:

building 'MACS2.Signal' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c MACS2/Signal.c -o build/temp.linux-x86_64-2.7/MACS2/Signal.o -w -O3 
-ffast-math
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-2.7/MACS2/Signal.o -o 
/build/macs-2.1.1.20160309/.pybuild/pythonX.Y_2.7/build/MACS2/Signal.so
cythoning MACS2/IO/PeakIO.pyx to MACS2/IO/PeakIO.c

Error compiling Cython file:

...
pileup = float(fields[5])
pscore = float(fields[6])
fc = float(fields[7])
qscore = float(fields[8])
peakname = rstrip(fields[9])
add(chrom, start, end, summit, qscore, pileup, pscore, fc, qscore,
^


MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
building 'MACS2.IO.PeakIO' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python2.7 -c MACS2/IO/PeakIO.c -o 
build/temp.linux-x86_64-2.7/MACS2/IO/PeakIO.o -w -O3 -ffast-math
MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result of 
a failed Cython compilation.
 #error Do not use this file, it is the result of a failed Cython compilation.
  ^
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:274: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:16: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/macs-2.1.1.20160309'
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2


cheers!

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 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)

Processed: affects

[Debian Bug Tracking System]

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

> affects 829020 src:sqlalchemy
Bug #829020 {Done: Piotr Ożarowski } [zzzeeksphinx] 
sqlalchemy: FTBFS in testing (too many values to unpack)
Bug #830178 {Done: Piotr Ożarowski } [zzzeeksphinx] mako: 
FTBFS: ValueError: too many values to unpack
Added indication that 829020 affects src:sqlalchemy
Added indication that 830178 affects src:sqlalchemy
> affects 830178 src:mako
Bug #830178 {Done: Piotr Ożarowski } [zzzeeksphinx] mako: 
FTBFS: ValueError: too many values to unpack
Bug #829020 {Done: Piotr Ożarowski } [zzzeeksphinx] 
sqlalchemy: FTBFS in testing (too many values to unpack)
Added indication that 830178 affects src:mako
Added indication that 829020 affects src:mako
> thanks
Stopping processing here.

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

Processed: .

[Debian Bug Tracking System]

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

> forwarded 831857 https://sourceforge.net/p/pupnp/bugs/132/
Bug #831857 [src:libupnp] libupnp: CVE-2016-6255: write files via POST
Set Bug forwarded-to-address to 'https://sourceforge.net/p/pupnp/bugs/132/'.
> thanks
Stopping processing here.

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

Bug#754755: [rt.cpan.org #98683] libinline-java-perl: FTBFS on mips: test suite issues

[Daniel Knezevic]

Hi,

Tests are still failing in version 0.58 during build.

I have found out that the tests are failing when Inline::Java uses JNI 
extensions
(PERL_INLINE_JAVA_JNI is set to 1), but the tests pass when Inline::Java run 
JVM in
the default client/server mode (PERL_INLINE_JAVA_JNI is unset).

--- debian/rules_orig   2016-08-02 12:16:34.206089692 +
+++ debian/rules2016-08-02 12:16:46.476196564 +
@@ -49,9 +49,6 @@

 export JAVA_HOME=/usr/lib/jvm/default-java

-# Have testsuite use JNI
-export PERL_INLINE_JAVA_JNI=1
-
 # Put aside upstream cruft during build
 DEB_UPSTREAM_CRUFT_MOVE = t/t13.txt

It may be some mips/mipsel specific issue, because the build succeeds on 
mips64el.
We are still investigating, any tip will be useful.

Can we use Inline::Java without JNI extension for mips/mipsel?

Regards,
Daniel

Bug#819835: [src:dico] dico: FTBFS in testing (test suite fails)

[Santiago Vila]

On Tue, 2 Aug 2016, Ritesh Raj Sarraf wrote:

> As a result of this bug, dico will be out of testing. I've tried reaching to
> Ahmed but haven't had any reply.
> 
> As is mentioned in the bug, the build failure has to do with test suite. The
> packaging already carries a patch that fixed similar build failure in the 
> past.
> I have zero knowledge about these guile testcases, so have reached out to
> upstream (email/logs attached) folks hoping they may have some input.
> 
> Worst case, is it okay to prepare an (NMU) upload with the test suite 
> disabled ?
> I'd not want to see this package out of testing.

Hi.

Before disabling all the tests, I would try to find the way to disable
the tests that fail, and only those. That's usually considered better
than disabling all the tests.

Also, if the maintainer is MIA, try contacting the MIA team.

Thanks.

Bug#819835: [src:dico] dico: FTBFS in testing (test suite fails)

[Ritesh Raj Sarraf]

Hi,

As a result of this bug, dico will be out of testing. I've tried reaching to
Ahmed but haven't had any reply.

As is mentioned in the bug, the build failure has to do with test suite. The
packaging already carries a patch that fixed similar build failure in the past.
I have zero knowledge about these guile testcases, so have reached out to
upstream (email/logs attached) folks hoping they may have some input.

Worst case, is it okay to prepare an (NMU) upload with the test suite disabled ?
I'd not want to see this package out of testing.


Ritesh

On Sat, 2016-07-30 at 10:51 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > 
> > #I'm trying to reach out to upstream for help. Worst case, I'll upload a
> > build with testcases disabled
> > tags 819835 + confirmed
> Bug #819835 [src:dico] dico: FTBFS in testing (test suite fails)
> Added tag(s) confirmed.
> > 
> > thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System--- Begin Message ---
Hello Sergey and others,

Could you please help me with dico testcase failures which have begun recently?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819835

This bug has ended making dico unfit for release and I'd like to see this fixed.
My fallback option is to disable tests, but I'd rather prefer if you could help
with the test failure.

Note: The same build used to build fine earlier. But I see a guilde-2.x patch to
make it build earlier too. So my guess is something further broke in the
testcases.


Attached is the failing test log.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

testsuite.log.gz
Description: application/gzip


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


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

Bug#833265: refcard: depends on unexistent package

[victory]

On Tue, 2 Aug 2016 10:25:13 + (UTC)
Gianfranco Costamagna wrote:

> As said, "ttf-kochi-gothic" is not available in Debian, so, the package
> seems to be not buildable from source, at least with Debian repositories.

as long as stable has it, "not available in Debian" is not true;
anyway you can apply this:

Index: refcard/dblatex.xsl
===
--- refcard/dblatex.xsl (r42)
+++ refcard/dblatex.xsl (wc)
@@ -10,7 +10,7 @@
\setCJKmainfont{IPAPGothic}
\setCJKsansfont{IPAPMincho}
\setCJKmonofont{IPAexGothic}
-   \setmainfont{Kochi Gothic}
+   \setmainfont{IPAPGothic}
\setsansfont{IPAPMincho}
\setmonofont{IPAexGothic}
 


-- 
victory
no need to CC me :-)

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

[Sebastiaan Couwenberg]

Control: tags -1 patch

Hi Sandro,

Because this RC bug is threatening the removal of several reverse
dependencies I had a look at fixing it. The attached patch adds the
build-arch target to the build-indep target dependencies to have the
missing files built.

Kind Regards,

Bas

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


0001-Add-dependency-on-build-arch-target-to-build-indep-target.patch
Description: inode/symlink

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #806606 [src:basemap] basemap: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) patch.

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

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

[Ola Lundqvist]

Hi again

Here is the working patch (attached).

Hope it helps for later versions too.

// Ola

On Tue, Aug 2, 2016 at 12:15 AM, Ola Lundqvist  wrote:

> Hi again
>
> I just realize that we need to change back the umask after the file is
> created. I'll update the patch tomorrow and send one that I know works.
>
> // Ola
>
> On Tue, Aug 2, 2016 at 12:13 AM, Ola Lundqvist  wrote:
>
>> Hi all
>>
>> I have prepared a preliminary patch for wheezy. I have not yet been able
>> to test it fully (it is building right now). It looks like attached. You
>> may need to modify it for later versions.
>>
>> Please comment. The principles should be ok even if I may have made some
>> stupid copy+paste mistake. It worked fine in a little test program I made.
>>
>> Hope this helps
>>
>> // Ola
>>
>> On Mon, Aug 1, 2016 at 5:53 AM, Chris Lamb  wrote:
>>
>>> > 2) How do you plan to handle the "upgrade case" that is will you try to
>>> > change the permission on already created history file or will you just
>>> > handle the creation case?
>>>
>>> For redis, what I did was set and then unset the umask (for creation) and
>>> chmod(2) the file afterwards to "upgrade" existing ones.
>>>
>>> I don't recommend a postinst approach (ie. chmod 0600 /home/*/.filename)
>>> for
>>> various reasons.
>>>
>>>
>>> Regards,
>>>
>>> --
>>>   ,''`.
>>>  : :'  : Chris Lamb
>>>  `. `'`  la...@debian.org / chris-lamb.co.uk
>>>`-
>>>
>>
>>
>>
>> --
>>  --- Inguza Technology AB --- MSc in Information Technology 
>> /  o...@inguza.comFolkebogatan 26\
>> |  o...@debian.org   654 68 KARLSTAD|
>> |  http://inguza.com/Mobile: +46 (0)70-332 1551 |
>> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
>>  ---
>>
>>
>
>
> --
>  --- Inguza Technology AB --- MSc in Information Technology 
> /  o...@inguza.comFolkebogatan 26\
> |  o...@debian.org   654 68 KARLSTAD|
> |  http://inguza.com/Mobile: +46 (0)70-332 1551 |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
>  ---
>
>


-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---
Description: World readable dbshell log file
 This correction make sure the ~/.dbshell log file is not world readable.
 .
 mongodb (1:2.0.6-1+deb7u1) wheezy-security; urgency=high
 .
   * Non-maintainer upload by the Long Term Security Team.
   * Make sure dbshell log file is not readable by others
 CVE-2016-6494 (Closes: #832908).
Author: Ola Lundqvist 
Origin: other
Bug: https://jira.mongodb.org/browse/SERVER-25335
Bug-Debian: https://bugs.debian.org/832908
Forwarded: no
Reviewed-By: Ola Lundqvist 
Last-Update: 2016-08-01

Index: mongodb-2.0.6/third_party/linenoise/linenoise.cpp
===
--- mongodb-2.0.6.orig/third_party/linenoise/linenoise.cpp	2016-08-01 22:10:07.318825853 +
+++ mongodb-2.0.6/third_party/linenoise/linenoise.cpp	2016-08-01 22:19:52.706824724 +
@@ -104,11 +104,13 @@
 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -799,6 +801,9 @@
 /* Save the history in the specified file. On success 0 is returned
  * otherwise -1 is returned. */
 int linenoiseHistorySave(const char *filename) {
+mode_t prev_mask = umask(0022);
+// Make sure this file is not readable by others
+umask(prev_mask | S_IROTH | S_IWOTH | S_IXOTH);
 FILE *fp = fopen(filename,"w");
 int j;
 
@@ -808,6 +813,7 @@
 fprintf(fp,"%s\n",history[j]);
 }
 fclose(fp);
+umask(prev_mask);
 return 0;
 }
 
@@ -817,6 +823,16 @@
  * If the file exists and the operation succeeded 0 is returned, otherwise
  * on error -1 is returned. */
 int linenoiseHistoryLoad(const char *filename) {
+struct stat fileStat;
+if (stat(filename,) < 0) return -1;
+if (fileStat.st_mode & S_IROTH ||
+	fileStat.st_mode & S_IWOTH ||
+	fileStat.st_mode & S_IXOTH) {
+  // If the file is world readable, writeable or executable
+  // make sure it is not but keep all other permissions.
+  chmod(filename, fileStat.st_mode & 070);
+}
+
 FILE *fp = fopen(filename,"r");
 char buf[LINENOISE_MAX_LINE];
 

Bug#832355: ktap: module FTBFS for Linux 4.6: error: '__GFP_WAIT' undeclared

[Azat Khuzhin]

On Sun, Jul 24, 2016 at 04:20:38PM +0200, Andreas Beckmann wrote:
> Package: ktap
> Version: 0.4+git20160427-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,

Hi Andreas,

Thanks for detailed report, actually I already had a patch to fix this
[1], but didn't though ktap must be build under 4.6 in debian, since
none of releases has 4.6 kernel [2]

But anyway I'm going to fix this and separate dkms.

Thanks,
Azat.

[1]: https://github.com/ktap/ktap/pull/97
[2]: https://packages.debian.org/search?keywords=linux-image

Processed (with 1 error): merge 828901 829726

[Debian Bug Tracking System]

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

> merge 828901 829726
Bug #828901 [src:python-websockets] python-websockets: FTBFS: AssertionError: 
Expected 'get_extra_info' to be called once. Called 2 times.
Unable to merge bugs because:
forwarded of #829726 is 'https://github.com/aaugustin/websockets/issues/123' 
not ''
Failed to merge 828901: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#831093: marked as done (qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing conversion of ''\37777777600'' from 'char' to 'uchar {aka unsigned char}' inside { } [-Wnarrowing])

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:50:19 +
with message-id 
and subject line Bug#831093: fixed in libterralib 4.3.0+dfsg.2-9
has caused the Debian Bug report #831093,
regarding qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing 
conversion of ''\3777600'' from 'char' to 'uchar {aka unsigned char}' 
inside { } [-Wnarrowing]
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.)


-- 
831093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qterm
Version: 1:0.5.12-1.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'
> [ 51%] Building CXX object src/CMakeFiles/qterm.dir/aboutdialog.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/aboutdialog.cpp.o -c 
> /«PKGBUILDDIR»/src/aboutdialog.cpp
> [ 52%] Building CXX object src/CMakeFiles/qterm.dir/addrdialog.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/addrdialog.cpp.o -c 
> /«PKGBUILDDIR»/src/addrdialog.cpp
> [ 53%] Building CXX object src/CMakeFiles/qterm.dir/articledialog.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/articledialog.cpp.o -c 
> /«PKGBUILDDIR»/src/articledialog.cpp
> [ 54%] Building CXX object src/CMakeFiles/qterm.dir/assistantclient.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/assistantclient.cpp.o -c 
> /«PKGBUILDDIR»/src/assistantclient.cpp
> [ 54%] Building CXX object src/CMakeFiles/qterm.dir/imageviewer.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/g++   -DDBUS_ENABLED 
> -DHAVE_CONFIG_H -DSCRIPT_ENABLED -DSSH_ENABLED -I/usr/include/qt4/QtDBus 
> -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -o CMakeFiles/qterm.dir/imageviewer.cpp.o -c 
> /«PKGBUILDDIR»/src/imageviewer.cpp
> [ 55%] Building CXX object 

Bug#812259: marked as done (openbabel: FTBFS with GCC 6: cmake errors)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:38:53 +
with message-id 
and subject line Bug#812259: fixed in openbabel 2.3.2+dfsg-2.3
has caused the Debian Bug report #812259,
regarding openbabel: FTBFS with GCC 6: cmake 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.)


-- 
812259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openbabel
Version: 2.3.2+dfsg-2.2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

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
...
> -- Check size of clock_t
> -- Check size of clock_t - done
> CMake Error at cmake/modules/MacroEnsureVersion.cmake:76 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   cmake/modules/MacroEnsureVersion.cmake:95 (NORMALIZE_VERSION)
>   CMakeLists.txt:231 (macro_ensure_version)
> 
> 
> CMake Error at cmake/modules/MacroEnsureVersion.cmake:76 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   cmake/modules/MacroEnsureVersion.cmake:95 (NORMALIZE_VERSION)
>   CMakeLists.txt:232 (macro_ensure_version)
> 
> 
> CMake Error at cmake/modules/MacroEnsureVersion.cmake:76 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   cmake/modules/MacroEnsureVersion.cmake:95 (NORMALIZE_VERSION)
>   CMakeLists.txt:233 (macro_ensure_version)
> 
> 
> -- Performing Test SCANDIR_NEEDS_CONST
> -- Performing Test SCANDIR_NEEDS_CONST - Failed
> -- Performing Test HAVE_GCC_VISIBILITY
> -- Performing Test HAVE_GCC_VISIBILITY - Success
> -- Could NOT find Boost
> CMake Error at CMakeLists.txt:303 (message):
>   Boost is required to compile OpenBabel with GCC 3.x
> 
> 
> -- Configuring incomplete, errors occurred!

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: openbabel
Source-Version: 2.3.2+dfsg-2.3

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openbabel 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: Tue, 02 Aug 2016 11:44:00 +0200
Source: openbabel
Binary: openbabel openbabel-gui libopenbabel-dev libopenbabel4v5 
libopenbabel-doc python-openbabel libchemistry-openbabel-perl openbabel-dbg
Architecture: source amd64 all
Version: 2.3.2+dfsg-2.3
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Matthias Klose 
Description:
 libchemistry-openbabel-perl - Chemical toolbox library (perl bindings)
 libopenbabel-dev - Chemical toolbox library (development files)
 libopenbabel-doc - Chemical toolbox library (documentation)
 libopenbabel4v5 - Chemical toolbox library
 openbabel  - Chemical toolbox utilities (cli)
 openbabel-dbg - Chemical toolbox library (debugging symbols)
 openbabel-gui - Chemical toolbox utilities (graphical user interface)
 

Bug#814435: marked as done (log4shib: FTBFS when built with dpkg-buildpackage -A (liblog4shib.la is not installed to anywhere))

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:36:52 +
with message-id 
and subject line Bug#814435: fixed in log4shib 1.0.9-3
has caused the Debian Bug report #814435,
regarding log4shib: FTBFS when built with dpkg-buildpackage -A (liblog4shib.la 
is not installed to anywhere)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf
   dh_testdir -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: copying file `config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'

[... snipped ...]

/usr/bin/install -c -m 644 ./man/man3/log4shib_StringUtil.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::StringUtil.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_SyslogAppender.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::SyslogAppender.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_ThreadNameComponent.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::ThreadNameComponent.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_TimeStamp.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::TimeStamp.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_TimeStampComponent.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::TimeStampComponent.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_Win32DebugAppender.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::Win32DebugAppender.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_threading.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::threading.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_threading_MSMutex.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::threading::MSMutex.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_threading_MSScopedLock.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::threading::MSScopedLock.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_threading_Mutex.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::threading::Mutex.3
/usr/bin/install -c -m 644 ./man/man3/log4shib_threading_ScopedLock.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::threading::ScopedLock.3
/usr/bin/install -c -m 644 
./man/man3/log4shib_threading_ThreadLocalDataHolder.3 
/<>/debian/tmp/usr/share/man/man3/log4shib::threading::ThreadLocalDataHolder.3
/bin/bash /<>/config/install-sh -d 
/<>/debian/tmp/usr/share/doc/log4shib-1.0.9/api
cp -r html /<>/debian/tmp/usr/share/doc/log4shib-1.0.9/api
rm -f -r -f 
/<>/debian/tmp/usr/share/doc/log4shib-1.0.9/api/html/.svn 
/<>/debian/tmp/usr/share/doc/log4shib-1.0.9/api/html/Makefile*
make[4]: Leaving directory '/<>/doc'
make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>/doc'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c log4shib-config '/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/aclocal'
 /usr/bin/install -c -m 644 log4shib.m4 
'/<>/debian/tmp/usr/share/aclocal'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 log4shib.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>'
find debian/tmp/usr/share/doc/log4shib-*/api/html -name "*.md5" -delete
dh_install -Xman3 --fail-missing
dh_install: usr/lib/x86_64-linux-gnu/liblog4shib.la exists in debian/tmp but is 
not installed to anywhere
dh_install: missing files, aborting
debian/rules:31: recipe for target 'override_dh_install-indep' failed
make[1]: *** [override_dh_install-indep] Error 2
make[1]: Leaving directory '/<>'
debian/rules:38: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not 

Bug#833265: refcard: depends on unexistent package

[Gianfranco Costamagna]

source: refcard
version: 9.0
severity: serious
justification: depends on unexistent package.

As said, "ttf-kochi-gothic" is not available in Debian, so, the package
seems to be not buildable from source, at least with Debian repositories.

thanks,

G.

Bug#812271: marked as done (strigi: FTBFS with GCC 6: cmake error)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:06:17 +
with message-id 
and subject line Bug#812271: fixed in strigi 0.7.8-2.2
has caused the Debian Bug report #812271,
regarding strigi: FTBFS with GCC 6: cmake error
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.)


-- 
812271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: strigi
Version: 0.7.8-2
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

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.

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
...
> -- Checking: /<>/strigiclient/CMakeLists.txt
> -- Performing Test __STRIGI_HAVE_GCC_VISIBILITY
> -- Performing Test __STRIGI_HAVE_GCC_VISIBILITY - Success
> CMake Error at libstreams/cmake/MacroEnsureVersion.cmake:27 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   libstreams/cmake/MacroCheckGccVisibility.cmake:24 (macro_ensure_version)
>   libstreams/CMakeLists.txt:47 (macro_check_gcc_visibility)
> 
> 
> CMake Error at libstreams/cmake/MacroEnsureVersion.cmake:27 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   libstreams/cmake/MacroCheckGccVisibility.cmake:25 (macro_ensure_version)
>   libstreams/CMakeLists.txt:47 (macro_check_gcc_visibility)
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: strigi
Source-Version: 0.7.8-2.2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated strigi 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: Tue, 02 Aug 2016 11:36:26 +0200
Source: strigi
Binary: strigi-daemon strigi-client strigi-utils libstreams0v5 libstreams-dev 
libstreamanalyzer0v5 libstreamanalyzer-dev libsearchclient0v5 
libsearchclient-dev libstrigihtmlgui0v5 libstrigihtmlgui-dev 
libstrigiqtdbusclient0 libstrigiqtdbusclient-dev strigi-dbg
Architecture: source amd64
Version: 0.7.8-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Matthias Klose 
Description:
 libsearchclient-dev - development files for libsearchclient
 libsearchclient0v5 - searchclient library for Strigi Desktop Search
 libstreamanalyzer-dev - development files for libstreamanalyzer
 libstreamanalyzer0v5 - streamanalyzer library for Strigi Desktop Search
 libstreams-dev - development files for libstreams
 libstreams0v5 - streams library for Strigi Desktop Search
 libstrigihtmlgui-dev - development files for libstrigihtmlgui
 libstrigihtmlgui0v5 - library for writing html clients for Strigi Desktop 
Search
 libstrigiqtdbusclient-dev - development files for libstrigiqtdbusclient
 libstrigiqtdbusclient0 - library for writing D-Bus clients for Strigi Desktop 
Search
 strigi-client - Qt4 client for Strigi Desktop Search
 strigi-daemon - fast indexing and searching tool for your personal data 
(daemon)
 strigi-dbg - debugging symbols for strigi
 strigi-utils - command-line tools for Strigi Desktop Search
Closes: 812271
Changes:
 strigi (0.7.8-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * "Fix" GCC 

Bug#812265: marked as done (avogadro: FTBFS with GCC 6: cmake failure)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:04:16 +
with message-id 
and subject line Bug#812265: fixed in avogadro 1.0.3-13.1
has caused the Debian Bug report #812265,
regarding avogadro: FTBFS with GCC 6: cmake failure
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.)


-- 
812265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: avogadro
Version: 1.0.3-13
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

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

Note: openbabel has the same issue

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> -- Performing Test HAVE_GCC_VISIBILITY - Success
> CMake Error at cmake/modules/MacroEnsureVersion.cmake:76 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   cmake/modules/MacroEnsureVersion.cmake:95 (NORMALIZE_VERSION)
>   CMakeLists.txt:82 (macro_ensure_version)
> 
> 
> CMake Error at cmake/modules/MacroEnsureVersion.cmake:76 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   cmake/modules/MacroEnsureVersion.cmake:95 (NORMALIZE_VERSION)
>   CMakeLists.txt:83 (macro_ensure_version)
> 
> 
> -- Performing Test COMPILES_WITHOUT_FPERMISSIVE
> -- Performing Test COMPILES_WITHOUT_FPERMISSIVE - Failed
...
> -- Configuring incomplete, errors occurred!

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: avogadro
Source-Version: 1.0.3-13.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated avogadro 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: Tue, 02 Aug 2016 11:46:17 +0200
Source: avogadro
Binary: avogadro avogadro-data libavogadro1 libavogadro-dev python-avogadro
Architecture: source all amd64
Version: 1.0.3-13.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Matthias Klose 
Description:
 avogadro   - Molecular Graphics and Modelling System
 avogadro-data - Molecular Graphics and Modelling System (Data Files)
 libavogadro-dev - Molecular Graphics and Modelling System (development files)
 libavogadro1 - Molecular Graphics and Modelling System (library)
 python-avogadro - Molecular Graphics and Modelling System (Python module)
Closes: 812265
Changes:
 avogadro (1.0.3-13.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * "Fix" GCC version check up to GCC 9. Closes: #812265.
Checksums-Sha1:
 2f8da78de41402702e956f902da5575ab85e6078 2467 avogadro_1.0.3-13.1.dsc
 78fed89f2c9691224055d3d69972dc46dc6744b3 22844 
avogadro_1.0.3-13.1.debian.tar.xz
 7f6b7e31805e788a6e66091ca2271b8fdc5d11ff 293446 
avogadro-data_1.0.3-13.1_all.deb
 13b9e8a7c093c39055a7662cbb38d456b2ae2b0f 3556494 
avogadro-dbgsym_1.0.3-13.1_amd64.deb
 4873f7f3c644efbdc3b0c1956484e6290f27e546 3454342 avogadro_1.0.3-13.1_amd64.deb
 02b3883a253e03c29b0825b1bc86f8349753ad79 249104 
libavogadro-dev_1.0.3-13.1_amd64.deb
 9d2beeb2e2f09b607fb1eeeb5af20c8897ee6063 29706460 
libavogadro1-dbgsym_1.0.3-13.1_amd64.deb
 

Bug#812292: marked as done (clucene-core: FTBFS with GCC 6: cmake error)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:04:35 +
with message-id 
and subject line Bug#812292: fixed in clucene-core 2.3.3.4-4.2
has caused the Debian Bug report #812292,
regarding clucene-core: FTBFS with GCC 6: cmake error
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.)


-- 
812292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clucene-core
Version: 2.3.3.4-4.1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

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.

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
...
> -- Performing Test _CL_HAVE_GCCVISIBILITYPATCH - Success
> CMake Error at src/shared/cmake/MacroEnsureVersion.cmake:27 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   src/shared/cmake/MacroCheckGccVisibility.cmake:35 (macro_ensure_version)
>   src/shared/CMakeLists.txt:230 (MACRO_CHECK_GCC_VISIBILITY)
> 
> 
> CMake Error at src/shared/cmake/MacroEnsureVersion.cmake:27 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   src/shared/cmake/MacroCheckGccVisibility.cmake:36 (macro_ensure_version)
>   src/shared/CMakeLists.txt:230 (MACRO_CHECK_GCC_VISIBILITY)
> 
> 
> -- Performing Test _CL_HAVE_TRY_BLOCKS
> -- Performing Test _CL_HAVE_TRY_BLOCKS - Success
> -- Checking support new float byte<->float conversions
> -- Checking support new float byte<->float conversions - yes
> -- Choosing namespace for hashmaps
> -- Performing Test _CL_HAVE_STD__TR1_HASHMAP
> -- Performing Test _CL_HAVE_STD__TR1_HASHMAP - Success
> -- Choosing namespace for hashmaps - std::tr1::func
> -- Performing Test _CL_HAVE_NAMESPACES
> -- Performing Test _CL_HAVE_NAMESPACES - Success
> -- Performing Test _CL_HAVE_NO_SNPRINTF_BUG
> -- Performing Test _CL_HAVE_NO_SNPRINTF_BUG - Success
> -- Performing Test _CL_ILONGLONG_LL
> -- Performing Test _CL_ILONGLONG_LL - Success
> -- Performing Test LUCENE_STATIC_CONSTANT_SYNTAX
> -- Performing Test LUCENE_STATIC_CONSTANT_SYNTAX - Success
> -- Check for ANSI scope
> -- Check for ANSI scope - found
> CMake Error at src/shared/cmake/MacroEnsureVersion.cmake:27 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   src/shared/cmake/MacroCheckGccVisibility.cmake:35 (macro_ensure_version)
>   src/core/CMakeLists.txt:10 (MACRO_CHECK_GCC_VISIBILITY)
> 
> 
> CMake Error at src/shared/cmake/MacroEnsureVersion.cmake:27 (MATH):
>   math cannot parse the expression: "cc (Debian 6-20160117-16*1 + cc
>   (Debian 6-20160117-10*100 + cc (Debian 6-20160117-10": syntax error,
>   unexpected $end, expecting exp_CLOSEPARENT or exp_OR (88)
> Call Stack (most recent call first):
>   src/shared/cmake/MacroCheckGccVisibility.cmake:36 (macro_ensure_version)
>   src/core/CMakeLists.txt:10 (MACRO_CHECK_GCC_VISIBILITY)
> 
> 
> -- Checking to see if CXX compiler accepts flag -fprofile-arcs -ftest-coverage
> -- Checking to see if CXX compiler accepts flag -fprofile-arcs 
> -ftest-coverage - yes
> -- Performing Test ICONV_SECOND_ARGUMENT_IS_CONST
> -- Performing Test ICONV_SECOND_ARGUMENT_IS_CONST - Failed
> -- Found Iconv: /usr/lib/x86_64-linux-gnu/libc.so
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
>   "tail -v -n +0 CMakeCache.txt"

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: clucene-core
Source-Version: 2.3.3.4-4.2

We believe that the bug you reported is fixed in the latest version of
clucene-core, which is 

Bug#811754: marked as done (ibus-unikey: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 10:05:09 +
with message-id 
and subject line Bug#811754: fixed in ibus-unikey 0.6.1-1.1
has caused the Debian Bug report #811754,
regarding ibus-unikey: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibus-unikey
Version: 0.6.1-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

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
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
> -Wall-g -O2 -c -o data.lo data.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -c data.cpp  
> -fPIC -DPIC -o .libs/data.o
> data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
>  };
>  ^
> 
> data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777642'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777651'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\310'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
...

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: ibus-unikey
Source-Version: 0.6.1-1.1

We believe that the bug you reported is fixed in the latest version of
ibus-unikey, 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.
Matthias Klose  (supplier of updated ibus-unikey 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: Tue, 02 Aug 2016 10:22:17 +0200
Source: ibus-unikey
Binary: ibus-unikey
Architecture: source amd64
Version: 0.6.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Lê 

Bug#833258: [gufw] Application Segfaults on Newer KDE/QT

[David Baron]

Package: gufw
Version: 12.10.0-1
Severity: grave

--- Please enter the report below this line. ---
Note: The ufw CLI application works correctly.

~$ sudo gufw
No protocol specified
Unable to init server: Could not connect: Connection refused

(gufw.py:10441): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
No protocol specified
Unable to init server: Could not connect: Connection refused
/usr/share/gufw/gufw/view/guiGufw.py:23: PyGIWarning: Gtk was imported without 
specifying a version first. Use gi.require_version('Gtk', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GLib
/usr/share/gufw/gufw/view/guiGufw.py:25: PyGIWarning: Polkit was imported 
without specifying a version first. Use gi.require_version('Polkit', '1.0') 
before import to ensure that the right version gets loaded.
  from gi.repository import Polkit

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:10441): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 
'GDK_IS_DISPLAY (display)' failed

(gufw.py:10441): Gdk-CRITICAL **: 

Bug#831244: [DRE-maint] Bug#831244: ruby-eventmachine: FTBFS: Build hangs minutes of inactivity

[Lucas Nussbaum]

On 02/08/16 at 01:05 +0200, Christian Hofstaedtler wrote:
> * Antonio Terceiro  [160801 15:21]:
> > On Sun, Jul 31, 2016 at 10:21:39PM +0200, Christian Hofstaedtler wrote:
> > > * Lucas Nussbaum  [160731 20:17]:
> > > > During a rebuild of all packages in sid, your package failed to build on
> > > > amd64.
> > > 
> > > So I tried debugging this a bit; for me the 'TestFileWatch' test
> > > hangs, both with our 1.0.7-3 and also if I update that to 1.2.0.1.
> > > 
> > > Now from what I see the test uses inotify; if our test builds use
> > > overlayfs, maybe that just does not support inotify (properly).
> > 
> > if it's a single test that hangs we can probably report the bug upstream
> > and skip it for now?
> 
> If my analysis is correct, then yes, that'd be my preferred option.
> But I'd like somebody else to have a look at it too - after all I've
> done mostly guesswork.

Hi,

For my archive rebuilds, I use sbuild+schroot in tarball mode, on an
ext4 filesystem. So unfortunately I don't see anything strange on that
side that would cause problems with inotify. :(

Lucas

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Lucas Nussbaum]

Hi Peter,

On 01/08/16 at 22:33 -0400, Peter Colberg wrote:
> Hi Lucas, Jonas,
> 
> twinkle has been marked for autoremoval from testing on 2016-08-27 due
> to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields
> slight differences in the list of visible symbols.
> 
> How should this bug be dealt with? Is it not simply a matter of
> waiting for GCC 6 to become default, uploading ucommon with an
> updated symbols file and an ABI bump (if needed), and submitting
> binNMUs for dependent packages?
> 
> If so, can this bug be downgraded to severity important until then?

Please ask the release team (debian-release@l.d.o) how they want to deal
with that.

Lucas

Bug#832531: marked as done (namazu2: FTBFS (No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 02 Aug 2016 07:18:35 +
with message-id 
and subject line Bug#832531: fixed in namazu2 2.0.21-15
has caused the Debian Bug report #832531,
regarding namazu2: FTBFS (No such file or directory)
to be marked as done.

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

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


-- 
832531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:namazu2
Version: 2.0.21-14
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'

[... snipped ...]

dh_installchangelogs -plibnmz7 -plibnmz7-dev ChangeLog
dh_installchangelogs: No packages to build.
cp /<>/debian/copyright 
/<>/debian/libnmz7-dev/usr/share/doc/libnmz7-dev/
cp: cannot create regular file 
'/<>/debian/libnmz7-dev/usr/share/doc/libnmz7-dev/': No such file 
or directory
debian/rules:70: recipe for target 'override_dh_installchangelogs' failed
make[1]: *** [override_dh_installchangelogs] Error 1
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The package also fails on every official autobuilder:

https://buildd.debian.org/status/package.php?p=namazu2

(they do "dpkg-buildpackage -B").

So, to summarize: Please ensure that both "dpkg-buildpackage -A" and
"dpkg-buildpackage -B" work properly, not just "dpkg-buildpackage".

After that, the package will be suitable to be uploaded in source-only
form if you wish.

Thanks.
--- End Message ---
--- Begin Message ---
Source: namazu2
Source-Version: 2.0.21-15

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Aug 2016 07:04:38 +
Source: namazu2
Binary: namazu2 namazu2-index-tools namazu2-common libnmz7 libnmz7-dev
Architecture: source i386 all
Version: 2.0.21-15
Distribution: unstable
Urgency: medium
Maintainer: NOKUBI Takatsugu 
Changed-By: NOKUBI Takatsugu 
Description:
 libnmz7- full text search engine - shared library
 libnmz7-dev - full text search engine - header files and static libraries
 namazu2- full text search engine - binary and CGI script
 namazu2-common - full text search engine - documentation
 namazu2-index-tools - full text search engine - index handling tools
Closes: 832531
Changes:
 namazu2 (2.0.21-15) unstable; urgency=medium
 .
   * Remove some $(CURDIR), closes: #832531.
Checksums-Sha1:
 d72d267f50db4fcd272a0f5845d961f90ba3f6e0 1996 namazu2_2.0.21-15.dsc
 35690391ec5df83187def465b3c2250ea8d4880e 337764 namazu2_2.0.21-15.debian.tar.xz
 2846083cc6243e2724f596e2d34a688948958eb5 148762 libnmz7-dev_2.0.21-15_i386.deb
 2abdab3a0bdf5675232379bd68ce4450682834c7 138524 libnmz7_2.0.21-15_i386.deb
 7bb1460b3953468ad4e128cb24fa2039232e6ba9 16 
namazu2-common_2.0.21-15_all.deb
 e82a356fdf62928c00777930efaf7677f453cdf0 91260 
namazu2-index-tools_2.0.21-15_all.deb
 8d9d51debe0dead01c7cdc04b3f8f06169abf96c 101426 namazu2_2.0.21-15_i386.deb
Checksums-Sha256:
 bd38d9af182da06180b9328d29e442f382614b5ee1d67fc7162c666cf70cb794 1996 
namazu2_2.0.21-15.dsc
 de2fee8604c4f5e29b89f1ecae8e009f4dbe4c002ce138e46df57d25925ffd66 337764 
namazu2_2.0.21-15.debian.tar.xz
 bf8db8e8d931044e61e45e55e79d3d28ca77e4c9492d96f8a98b9b53a8400465 148762 
libnmz7-dev_2.0.21-15_i386.deb
 

Bug#832908:

[Sébastien Delafond]

FWIW, the vendor has closed https://jira.mongodb.org/browse/SERVER-25335
with "Works as Designed".

If someone wants to follow up on explaining to mongodb upstream why
umask shouldn't prevent them from applying proper permissions where
needed, they're welcome to do so. ssh-keygen(1) would be a good example
to point to.

Cheers,

--Seb