Bug#829161: gplots: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

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

Dear Maintainer,

gplots fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../libtcl8.6_8.6.5+dfsg-2_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../libtk8.6_8.6.5-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.5-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package r-base-core.
  Preparing to unpack .../r-base-core_3.3.1-1_amd64.deb ...
  Unpacking r-base-core (3.3.1-1) ...
  Selecting previously unselected package libgfortran-5-dev:amd64.
  Preparing to unpack .../libgfortran-5-dev_5.4.0-4_amd64.deb ...
  Unpacking libgfortran-5-dev:amd64 (5.4.0-4) ...
  Selecting previously unselected package gfortran-5.
  Preparing to unpack .../gfortran-5_5.4.0-4_amd64.deb ...
  Unpacking gfortran-5 (5.4.0-4) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../gfortran_4%3a5.3.1-3_amd64.deb ...
  Unpacking gfortran (4:5.3.1-3) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../libblas-dev_3.6.1-1_amd64.deb ...
  Unpacking libblas-dev (3.6.1-1) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../liblapack-dev_3.6.1-1_amd64.deb ...
  Unpacking liblapack-dev (3.6.1-1) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../libtinfo-dev_6.0+20160319-2+b1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160319-2+b1) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack .../libncurses5-dev_6.0+20160319-2+b1_amd64.deb ...
  Unpacking libncurses5-dev:amd64 (6.0+20160319-2+b1) ...
  Selecting previously unselected package libreadline6-dev:amd64.
  Preparing to unpack .../libreadline6-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline6-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libreadline-dev:amd64.
  Preparing to unpack .../libreadline-dev_6.3-8+b4_amd64.deb ...
  Unpacking libreadline-dev:amd64 (6.3-8+b4) ...
  Selecting previously unselected package libjpeg62-turbo-dev:amd64.
  Preparing to unpack .../libjpeg62-turbo-dev_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo-dev:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package libjpeg-dev.
  Preparing to unpack .../libjpeg-dev_1%3a1.5.0-1_all.deb ...
  Unpacking libjpeg-dev (1:1.5.0-1) ...
  Selecting previously unselected package libpcre16-3:amd64.
  Preparing to unpack .../libpcre16-3_2%3a8.38-3.1_amd64.deb ...
  Unpacking libpcre16-3:amd64 (2:8.38-3.1) ...
  Selecting previously unselected package libpcre32-3:amd64.
  Preparing 

Bug#825704: swift-im: should it be removed from Debian?

[Mattia Rizzolo]

On Thu, Jun 16, 2016 at 09:17:32PM +0100, Kevin Smith wrote:
> Thanks very much - I’ve had something I think’s ready to go for a
> couple of days (I realised the license wasn’t a blocker), I’d been
> trying to hunt Olly out on IRC, now I know why I was failing.

Today should have been the day where I get libssl1.0.0 removed, thus
making your package even uninstallable.

This is a kind of last call to fix it, I'm not going to hold on much
more.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#827927: marked as done (hime: postinst fails due to "set -e" and "dpkg --compare-versions")

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2016 04:46:01 +
with message-id 
and subject line Bug#827927: fixed in hime 0.9.10+git20150916+dfsg1-7
has caused the Debian Bug report #827927,
regarding hime: postinst fails due to "set -e" and "dpkg --compare-versions"
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.)


-- 
827927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hime
Version: 0.9.10+git20150916+dfsg1-4
Severity: serious
Tags: patch
Justification: Policy 6.4

"hime.postinst configure" fails because it performs "set -e" at the top
then tests "dpkg --compare-versions".  The lines

dpkg --compare-versions $2 lt 0.9.10+git20150916+dfsg1-3~
if [ $? ]; then

should instead read

if dpkg --compare-versions $2 lt 0.9.10+git20150916+dfsg1-3~; then

Thanks!

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

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

Versions of packages hime depends on:
ii  hime-data0.9.10+git20150916+dfsg1-4
ii  hime-tables  0.9.10+git20150916+dfsg1-4
ii  libappindicator1 0.4.92-4
ii  libc62.22-12
ii  libcairo21.14.6-1+b1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-1
ii  libgtk2.0-0  2.24.30-2
ii  libhime  0.9.10+git20150916+dfsg1-4
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libx11-6 2:1.6.3-1
ii  libxtst6 2:1.2.2-1+b1

Versions of packages hime recommends:
ii  hime-gtk2-immodule  0.9.10+git20150916+dfsg1-4
ii  hime-gtk3-immodule  0.9.10+git20150916+dfsg1-4
ii  im-config   0.29-1.4

Versions of packages hime suggests:
pn  gcin-voice 
ii  hime-anthy 0.9.10+git20150916+dfsg1-4
ii  hime-chewing   0.9.10+git20150916+dfsg1-4
ii  hime-qt4-immodule  0.9.10+git20150916+dfsg1-4
pn  hime-qt5-immodule  

-- no debconf information

-- 
Edit this signature at http://conway.bostoncoop.net/~ccshan/cgi-bin/sig
Greens for Europe https://www.greenparty.org.uk/europe
Feel the Bern https://berniesanders.com/


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: hime
Source-Version: 0.9.10+git20150916+dfsg1-7

We believe that the bug you reported is fixed in the latest version of
hime, 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.
ChangZhuo Chen (陳昌倬)  (supplier of updated hime 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, 01 Jul 2016 11:08:50 +0800
Source: hime
Binary: hime hime-data hime-tables libhime hime-gtk2-immodule 
hime-gtk3-immodule hime-qt4-immodule hime-qt5-immodule hime-anthy hime-chewing
Architecture: source amd64 all
Version: 0.9.10+git20150916+dfsg1-7
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 hime   - GTK+ based input method for Chinese users
 hime-anthy - support library to use Anthy in HIME
 hime-chewing - support library to use Chewing in HIME
 hime-data  - icons, locales and scripts for HIME
 hime-gtk2-immodule - GTK2 input method module with HIME as backend
 hime-gtk3-immodule - GTK3 input method module with HIME as backend
 hime-qt4-immodule - Qt4 input method module with HIME as backend
 hime-qt5-immodule - Qt5 input method module with HIME as backend
 hime-tables - input method tables for HIME
 libhime- library for HIME
Closes: 827927
Changes:
 hime (0.9.10+git20150916+dfsg1-7) unstable; urgency=medium
 .
   * Fix buggy version comparison in hime.postinst.
 Thanks to Chung-chieh Shan, Andreas Beckmann (Closes: #827927)
Checksums-Sha1:
 0e37d071df62913402be1efad1da63f6849b97a7 2776 

Bug#812041: thrift-compiler: diff for NMU version 0.9.1-2.1

[tony mancill]

Control: tags 812041 + patch
Control: tags 812041 + pending

Dear maintainer,

I've prepared an NMU for thrift-compiler (versioned as 0.9.1-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer or if you would like me to dcut the upload.

Also, I would be interested in collaborating on an update to a newer
version of the thrift compiler.  Please let me know if you are amenable
to that.

Cheers,
tony
diff -Nru thrift-compiler-0.9.1/debian/changelog thrift-compiler-0.9.1/debian/changelog
--- thrift-compiler-0.9.1/debian/changelog	2014-10-12 00:21:34.0 -0700
+++ thrift-compiler-0.9.1/debian/changelog	2016-06-30 21:33:13.0 -0700
@@ -1,3 +1,10 @@
+thrift-compiler (0.9.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add gcc6.patch to address FTBFS with GCC 6. (Closes: #812041)
+
+ -- tony mancill   Thu, 30 Jun 2016 21:32:33 -0700
+
 thrift-compiler (0.9.1-2) unstable; urgency=low
 
   * Output modernized Go (closes: #729430).
diff -Nru thrift-compiler-0.9.1/debian/patches/gcc6.patch thrift-compiler-0.9.1/debian/patches/gcc6.patch
--- thrift-compiler-0.9.1/debian/patches/gcc6.patch	1969-12-31 16:00:00.0 -0800
+++ thrift-compiler-0.9.1/debian/patches/gcc6.patch	2016-06-30 21:33:13.0 -0700
@@ -0,0 +1,31 @@
+--- a/cpp/src/generate/t_java_generator.cc
 b/cpp/src/generate/t_java_generator.cc
+@@ -2827,7 +2827,7 @@
+  bool first = true;
+  if (xceptions.size() > 0) {
+ 	 for (x_iter = xceptions.begin(); x_iter != xceptions.end(); ++x_iter) {
+-		 first ? first = false : indent(f_service_) << "else ";
++		 if (first) { first = false; } else { indent(f_service_) << "else "; }
+ 		 indent(f_service_) << "if (e instanceof " << type_name((*x_iter)->get_type(), false, false)<<") {" << endl;
+ 		 indent(f_service_) << indent() << "result." << (*x_iter)->get_name() << " = (" << type_name((*x_iter)->get_type(), false, false) << ") e;" << endl;
+ 	  	 indent(f_service_) << indent() << "result.set" << get_cap_name((*x_iter)->get_name()) << get_cap_name("isSet") << "(true);" << endl;
+--- a/cpp/src/generate/t_rb_generator.cc
 b/cpp/src/generate/t_rb_generator.cc
+@@ -363,7 +363,7 @@
+   for(c_iter = constants.begin(); c_iter != constants.end(); ++c_iter) {
+ // Populate the hash
+ int value = (*c_iter)->get_value();
+-first ? first = false : f_types_ << ", ";
++if (first) { first = false; } else { f_types_ << ", "; }
+ f_types_ << value << " => \"" << capitalize((*c_iter)->get_name()) << "\"";
+   }
+   f_types_ << "}" << endl;
+@@ -373,7 +373,7 @@
+   first = true;
+   for (c_iter = constants.begin(); c_iter != constants.end(); ++c_iter) {
+ // Populate the set
+-first ? first = false : f_types_ << ", ";
++if (first) { first = false; } else { f_types_ << ", "; }
+ f_types_ << capitalize((*c_iter)->get_name());
+   }
+   f_types_ << "]).freeze" << endl;
diff -Nru thrift-compiler-0.9.1/debian/patches/series thrift-compiler-0.9.1/debian/patches/series
--- thrift-compiler-0.9.1/debian/patches/series	2014-10-12 00:21:20.0 -0700
+++ thrift-compiler-0.9.1/debian/patches/series	2016-06-30 21:33:13.0 -0700
@@ -1 +1,2 @@
 thrift-2247-binary-as-string-keys.patch
+gcc6.patch

Processed: thrift-compiler: diff for NMU version 0.9.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 812041 + patch
Bug #812041 [thrift-compiler] thrift-compiler: FTBFS with GCC 6: operands to ?: 
have different
Added tag(s) patch.
> tags 812041 + pending
Bug #812041 [thrift-compiler] thrift-compiler: FTBFS with GCC 6: operands to ?: 
have different
Added tag(s) pending.

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

Bug#826022: marked as done (Does not work with Django 1.8)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2016 04:35:42 +
with message-id 
and subject line Bug#826022: fixed in django-tastypie 0.13.3-1
has caused the Debian Bug report #826022,
regarding Does not work with Django 1.8
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.)


-- 
826022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django-tastypie
Version: 0.12.0-1
Severity: serious

Hello,

thank you for maintaining tastypie.

An attempt to use it with Django 1.8 gives this:

[...]
  File "/usr/lib/python2.7/dist-packages/tastypie/resources.py", line 1740, in 

class BaseModelResource(Resource):
  File "/usr/lib/python2.7/dist-packages/tastypie/resources.py", line 2210, in 
BaseModelResource
@transaction.commit_on_success()
AttributeError: 'module' object has no attribute 'commit_on_success'

Upstream has several bugs about it, this seems a good start:
https://github.com/django-tastypie/django-tastypie/issues/1288

Enrico

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

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

Versions of packages python-django-tastypie depends on:
ii  python-dateutil   2.4.2-1
ii  python-django 1.9.6-1
ii  python-mimeparse  0.1.4-1
pn  python:any

python-django-tastypie recommends no packages.

Versions of packages python-django-tastypie suggests:
pn  python-defusedxml  
ii  python-lxml3.6.0-1
ii  python-yaml3.11-3+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: django-tastypie
Source-Version: 0.13.3-1

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

Debian distribution maintenance software
pp.
Dominique Belhachemi  (supplier of updated django-tastypie 
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: Thu, 30 Jun 2016 23:07:53 -0400
Source: django-tastypie
Binary: python-django-tastypie python3-django-tastypie
Architecture: source all
Version: 0.13.3-1
Distribution: unstable
Urgency: medium
Maintainer: Dominique Belhachemi 
Changed-By: Dominique Belhachemi 
Description:
 python-django-tastypie - webservice API framework for Django (Python 2)
 python3-django-tastypie - webservice API framework for Django (Python 3)
Closes: 826022
Changes:
 django-tastypie (0.13.3-1) unstable; urgency=medium
 .
   * new upstream release with support for Django 1.8/1.9 (Closes: #826022)
   * Bump Standards-Version to 3.9.8
   * supports python 2.7 and 3.4
Checksums-Sha1:
 0bf02909e8fc04188407ea3e11067c0a1a56d2f4 2073 django-tastypie_0.13.3-1.dsc
 d3c5cd0fe095ba0dbe24e55289b3f4bdc9ce1b2b 231373 
django-tastypie_0.13.3.orig.tar.gz
 0eba1c456745320b30bf911409d1ab62e135e4ee 3000 
django-tastypie_0.13.3-1.debian.tar.xz
 c50c877e673d4dfde5c9e6477001c166021b832e 53762 
python-django-tastypie_0.13.3-1_all.deb
 5cadfaf380636f32e461cefb8a69f29f3330c803 53828 
python3-django-tastypie_0.13.3-1_all.deb
Checksums-Sha256:
 6e458172807b095f72f93cafd1c9d4cc92c2e1ef6e19cc90b6f011859d3f2452 2073 
django-tastypie_0.13.3-1.dsc
 7a6aac94911a09823e9f9f865d11845bbc9d7627eb44fa010650595c54c4596b 231373 
django-tastypie_0.13.3.orig.tar.gz
 88bfd6156c9dfdcd6934c72b44c655a21607181e35a7650e0fd654c06b3baef6 3000 
django-tastypie_0.13.3-1.debian.tar.xz
 80b80262a241d9bd531134802d464ffba68437c16f2100540560a68ae15357d5 53762 
python-django-tastypie_0.13.3-1_all.deb
 372972138aba4a25b794ea149f2d8d2d6f114b38718c4b77a2409501a5f34f30 53828 
python3-django-tastypie_0.13.3-1_all.deb
Files:
 06349f350f4b793ddaf378b53d9a6a9a 2073 python optional 
django-tastypie_0.13.3-1.dsc
 460117c5bda80ebab3cb658d061b3ee1 231373 python optional 
django-tastypie_0.13.3.orig.tar.gz
 

Bug#822718: marked as done (flrig: FTBFS with GCC 6: reference to 'ignore' is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2016 04:36:04 +
with message-id 
and subject line Bug#822718: fixed in flrig 1.3.26-1
has caused the Debian Bug report #822718,
regarding flrig: FTBFS with GCC 6: reference to 'ignore' 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.)


-- 
822718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flrig
Version: 1.3.24-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-reference-ambiguous

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but will probably come out this week.

You can find GCC 6 in unstable (gcc-6).  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.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I.  -I. -I./include -I./xmlrpcpp -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I./xmlrpcpp  -I/usr/include/cairo 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/freetype2 -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -fvisibility-inlines-hidden  
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT -I. 
> -I./include   -pipe -Wall -fexceptions -O2 -ffast-math -finline-functions 
> -fomit-frame-pointer   -DNDEBUG -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o support/flrig-xml_io.o `test -f 
> 'support/xml_io.cxx' || echo './'`support/xml_io.cxx
> support/xml_io.cxx: In function 'void send_modes()':
> support/xml_io.cxx:158:3: error: reference to 'ignore' is ambiguous
>ignore = 2;
>^~
> support/xml_io.cxx:88:5: note: candidates are: int ignore
>  int ignore = 0; // skip next "ignore" read loops
>  ^~
> In file included from /usr/include/c++/6/bits/stl_map.h:63:0,
>  from /usr/include/c++/6/map:61,
>  from ./xmlrpcpp/XmlRpcServer.h:25,
>  from ./xmlrpcpp/XmlRpc.h:30,
>  from support/xml_io.cxx:34:
> /usr/include/c++/6/tuple:1541:25: note: const 
> std::_Swallow_assign std::ignore
>const _Swallow_assign ignore{};
>  ^~
> support/xml_io.cxx: In function 'void send_bandwidths()':
> support/xml_io.cxx:179:3: error: reference to 'ignore' is ambiguous
>ignore = 2;
>^~
> support/xml_io.cxx:88:5: note: candidates are: int ignore
>  int ignore = 0; // skip next "ignore" read loops
>  ^~
> In file included from /usr/include/c++/6/bits/stl_map.h:63:0,
>  from /usr/include/c++/6/map:61,
>  from ./xmlrpcpp/XmlRpcServer.h:25,
>  from ./xmlrpcpp/XmlRpc.h:30,
>  from support/xml_io.cxx:34:
> /usr/include/c++/6/tuple:1541:25: note: const 
> std::_Swallow_assign std::ignore
>const _Swallow_assign ignore{};
>  ^~
> support/xml_io.cxx: In function 'void send_name()':
> support/xml_io.cxx:193:3: error: reference to 'ignore' is ambiguous
>ignore = 2;
>^~
> support/xml_io.cxx:88:5: note: candidates are: int ignore
>  int ignore = 0; // skip next "ignore" read loops
>  ^~
> In file included from /usr/include/c++/6/bits/stl_map.h:63:0,
>  from /usr/include/c++/6/map:61,
>  from ./xmlrpcpp/XmlRpcServer.h:25,
>  from ./xmlrpcpp/XmlRpc.h:30,
>  from support/xml_io.cxx:34:
> /usr/include/c++/6/tuple:1541:25: note: const 
> std::_Swallow_assign std::ignore
>const _Swallow_assign ignore{};
>  ^~
> support/xml_io.cxx: In function 'void send_ptt_changed(bool)':
> support/xml_io.cxx:207:3: error: reference to 'ignore' is ambiguous
>ignore = 2;
>^~
> support/xml_io.cxx:88:5: note: candidates are: int ignore
>  int ignore = 0; // skip next "ignore" read loops
>  ^~
> In file included from /usr/include/c++/6/bits/stl_map.h:63:0,
>  from /usr/include/c++/6/map:61,
>  from ./xmlrpcpp/XmlRpcServer.h:25,
>  from ./xmlrpcpp/XmlRpc.h:30,
>  from support/xml_io.cxx:34:
> /usr/include/c++/6/tuple:1541:25: note: const 
> 

Processed: user debian...@lists.debian.org, usertagging 827927, found 827927 in 0.9.10+git20150916+dfsg1-6 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 827927 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 827927 0.9.10+git20150916+dfsg1-6
Bug #827927 [hime] hime: postinst fails due to "set -e" and "dpkg 
--compare-versions"
Ignoring request to alter found versions of bug #827927 to the same values 
previously set
> found 821831 4.2.1.102+dfsg2-8
Bug #821831 [ca-certificates-mono] ca-certificates-mono: unowned files after 
purge (policy 6.8, 10.8): /etc/mono/certstore/certs/Trust/*.cer and the 
/etc/mono/certstore/ tree
Marked as found in versions mono/4.2.1.102+dfsg2-8.
> found 744165 1.21-1
Bug #744165 [libfakeroot] '/usr/lib/i386-linux-gnu/libfakeroot' not empty so 
not removed
Bug #786386 [libfakeroot] dpkg: warning: while removing libfakeroot:i386, 
directory '/usr/lib/i386-linux-gnu/libfakeroot' not empty so not removed
Marked as found in versions fakeroot/1.21-1.
Marked as found in versions fakeroot/1.21-1.
> usertags 744165 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 788253 gfarm/2.6.11+dfsg-2
Bug #788253 [dh-systemd] gfsd: unowned files after purge (policy 6.8, 10.8): 
/var/lib/systemd/deb-systemd-helper-masked/gfsd.service
Marked as found in versions gfarm/2.6.11+dfsg-2.
> found 825121 asterisk-modules/1:13.9.1~dfsg-1
Bug #825121 [libradcli4] libradcli4: prompting due to modified conffiles which 
were not modified by the user: /etc/radcli/dictionary
The source asterisk-modules and version 1:13.9.1~dfsg-1 do not appear to match 
any binary packages
Marked as found in versions asterisk-modules/1:13.9.1~dfsg-1.
> thanks
Stopping processing here.

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

Bug#829152: liblapack3: misses Breaks: liblapack3gf

[Andreas Beckmann]

Package: liblapack3
Version: 3.5.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed again some error:

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

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


Andreas

Processed: bug 812264 is forwarded to https://bugzilla.samba.org/show_bug.cgi?id=11750

[Debian Bug Tracking System]

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

> forwarded 812264 https://bugzilla.samba.org/show_bug.cgi?id=11750
Bug #812264 [samba] samba: FTBFS with GCC 6: ctype.h:216: first defined here
Set Bug forwarded-to-address to 
'https://bugzilla.samba.org/show_bug.cgi?id=11750'.
> thanks
Stopping processing here.

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

Processed: tagging 812264

[Debian Bug Tracking System]

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

> tags 812264 + confirmed upstream fixed-upstream
Bug #812264 [samba] samba: FTBFS with GCC 6: ctype.h:216: first defined here
Added tag(s) fixed-upstream, confirmed, and upstream.
> thanks
Stopping processing here.

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

Processed: minetest-data: fails to upgrade from 'jessie' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + minetest-dbg
Bug #829150 [minetest-data] minetest-data: fails to upgrade from 'jessie' - 
trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg
Added indication that 829150 affects minetest-dbg

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

Bug#829150: minetest-data: fails to upgrade from 'jessie' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg

[Andreas Beckmann]

Package: minetest-data
Version: 0.4.14+repack-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + minetest-dbg

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' 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 .../minetest-data_0.4.14+repack-4_all.deb ...
  Unpacking minetest-data (0.4.14+repack-4) over (0.4.10+repack-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/minetest-data_0.4.14+repack-4_all.deb (--unpack):
   trying to overwrite '/usr/share/icons/hicolor/scalable/apps/minetest.svg', 
which is also in package minetest 0.4.10+repack-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


minetest-dbg_None.log.gz
Description: application/gzip

Bug#829149: gcin: fails to upgrade from testing: subprocess installed post-installation script returned error exit status 1

[Andreas Beckmann]

Package: gcin
Version: 2.8.4+dfsg1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'stretch', then the upgrade to 'sid' fails.

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

  Setting up gcin (2.8.4+dfsg1-7) ...
  dpkg: error processing package gcin (--configure):
   subprocess installed post-installation script returned error exit status 1

  Processing triggers for libc-bin (2.22-13) ...
  Errors were encountered while processing:
   gcin


I havent checked the maintainer scripts, but this could be a problem
similar to the one in hime.


cheers,

Andreas


gcin_2.8.4+dfsg1-7.log.gz
Description: application/gzip

Bug#829148: alljoyn-gateway-1504: repeated postinst execution creates wrong symlink

[Andreas Beckmann]

Package: alljoyn-gateway-1504
Version: 15.04~git20160606-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

Just reinstall the package twice to create a failure:

apt-get install alljoyn-gateway-1504
# creates /opt/alljoyn -> /usr/lib/alljoyn/opt/alljoyn

apt-get install --reinstall alljoyn-gateway-1504
# creates /usr/lib/alljoyn/opt/alljoyn/alljoyn -> /usr/lib/alljoyn/opt/alljoyn

apt-get install --reinstall alljoyn-gateway-1504
# fails:

Preparing to unpack .../alljoyn-gateway-1504_15.04~git20160606-1_amd64.deb ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of stop.
Unpacking alljoyn-gateway-1504 (15.04~git20160606-1) over (15.04~git20160606-1) 
...
Setting up alljoyn-gateway-1504 (15.04~git20160606-1) ...
ln: failed to create symbolic link '/opt/alljoyn/alljoyn': File exists
dpkg: error processing package alljoyn-gateway-1504 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 alljoyn-gateway-1504


Please take care to remove the incorrect /usr/lib/alljoyn/opt/alljoyn/alljoyn
symlink on upgrades.


cheers,

Andreas

Processed: Re: hime: postinst fails due to "set -e" and "dpkg --compare-versions"

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.9.10+git20150916+dfsg1-5
Bug #827927 {Done: ChangZhuo Chen (陳昌倬) } [hime] hime: 
postinst fails due to "set -e" and "dpkg --compare-versions"
Marked as found in versions hime/0.9.10+git20150916+dfsg1-5 and reopened.

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

Bug#827927: hime: postinst fails due to "set -e" and "dpkg --compare-versions"

[Chung-chieh Shan]

Package: hime
Version: 0.9.10+git20150916+dfsg1-6
Followup-For: Bug #827927

Unfortunately, the bug still exists.  Please see my original bug
report for the change that needs to be made.  I am encountering
this bug upgrading from hime:amd64 0.9.10+git20150916+dfsg1-5 to
0.9.10+git20150916+dfsg1-6.  Thanks.

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

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

Versions of packages hime depends on:
ii  hime-data0.9.10+git20150916+dfsg1-6
ii  hime-tables  0.9.10+git20150916+dfsg1-6
ii  libappindicator1 0.4.92-4
ii  libc62.22-13
ii  libcairo21.14.6-1+b1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-1
ii  libgtk2.0-0  2.24.30-2
ii  libhime  0.9.10+git20150916+dfsg1-6
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libx11-6 2:1.6.3-1
ii  libxtst6 2:1.2.2-1+b1

Versions of packages hime recommends:
iu  hime-gtk2-immodule  0.9.10+git20150916+dfsg1-6
iu  hime-gtk3-immodule  0.9.10+git20150916+dfsg1-6
ii  im-config   0.29-1.4

Versions of packages hime suggests:
pn  gcin-voice 
iu  hime-anthy 0.9.10+git20150916+dfsg1-6
iu  hime-chewing   0.9.10+git20150916+dfsg1-6
iu  hime-qt4-immodule  0.9.10+git20150916+dfsg1-6
iu  hime-qt5-immodule  0.9.10+git20150916+dfsg1-6

-- no debconf information

-- 
Edit this signature at http://conway.bostoncoop.net/~ccshan/cgi-bin/sig
Keep Scotland in Europe https://greens.scot/eu
Feel the Bern https://berniesanders.com/


signature.asc
Description: PGP signature

Bug#827927: hime: postinst fails due to "set -e" and "dpkg --compare-versions"

[Andreas Beckmann]

Followup-For: Bug #827927
Control: found -1 0.9.10+git20150916+dfsg1-5

Hi,

that postinst script is still broken. You could just try to

  apt-get install hime
  apt-get install --reinstall hime

in a minimal chroot.

You probably wanted to do something like this (untested!):


#!/bin/sh
set -e

ua_remove () {
update-alternatives --remove xinput-$1 /etc/X11/xinit/xinput.d/$2
}

if [ "$1" = "configure" ]
then
if dpkg --compare-versions "$2" lt-nl 0.9.10+git20150916+dfsg1-3~
then
ua_remove all_ALL hime
ua_remove zh_CN   hime
ua_remove zh_TW   hime
fi
fi



Andreas

Processed: tagging 812303, tagging 812289, tagging 812280, tagging 812274, tagging 812272, tagging 812270 ...

[Debian Bug Tracking System]

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

> tags 812303 + sid stretch
Bug #812303 [synergy] synergy: FTBFS with GCC 6: test suite segfaults
Added tag(s) stretch and sid.
> tags 812289 + sid stretch
Bug #812289 {Done: Fredrik Hallenberg } [google-mock] 
google-mock: FTBFS with GCC 6: test suite segfault
Added tag(s) sid and stretch.
> tags 812280 + sid stretch
Bug #812280 [newmat] newmat: FTBFS with GCC 6: terminate called
Added tag(s) stretch and sid.
> tags 812274 + sid stretch
Bug #812274 [dataquay] dataquay: FTBFS with GCC 6: terminate called
Added tag(s) sid and stretch.
> tags 812272 + sid stretch
Bug #812272 [laserboy] laserboy: FTBFS with GCC 6: error: switch quantity not 
an integer
Added tag(s) stretch and sid.
> tags 812270 + sid stretch
Bug #812270 [unittest++] unittest++: FTBFS with GCC 6: terminate called after 
throwing an instance
Added tag(s) stretch and sid.
> tags 812138 + sid stretch
Bug #812138 [pyqwt3d] pyqwt3d: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> tags 812054 + sid stretch
Bug #812054 [lzop] lzop: FTBFS with GCC 6: failed the ACC conformance test
Added tag(s) stretch and sid.
> tags 812048 + sid stretch
Bug #812048 [aqemu] aqemu: FTBFS with GCC 6: invalid initialization
Added tag(s) stretch and sid.
> tags 812041 + sid stretch
Bug #812041 [thrift-compiler] thrift-compiler: FTBFS with GCC 6: operands to ?: 
have different
Added tag(s) stretch and sid.
> tags 812040 + sid stretch
Bug #812040 [gelemental] gelemental: FTBFS with GCC 6: operands to ?: have 
different
Added tag(s) stretch and sid.
> tags 812034 + sid stretch
Bug #812034 [klick] klick: FTBFS with GCC 6: needed for in-class initialization
Added tag(s) stretch and sid.
> tags 812032 + sid stretch
Bug #812032 [mldemos] mldemos: FTBFS with GCC 6: needed for in-class 
initialization
Added tag(s) sid and stretch.
> tags 812031 + sid stretch
Bug #812031 [prime-phylo] prime-phylo: FTBFS with GCC 6: needed for in-class 
initialization
Added tag(s) stretch and sid.
> tags 812028 + sid stretch
Bug #812028 [sigviewer] sigviewer: FTBFS with GCC 6: needed for in-class 
initialization
Added tag(s) stretch and sid.
> tags 812027 + sid stretch
Bug #812027 [zthreads] zthreads: FTBFS with GCC 6: return-statement with a value
Added tag(s) sid and stretch.
> tags 812022 + sid stretch
Bug #812022 [traverso] traverso: FTBFS with GCC 6: flexible array member...
Added tag(s) stretch and sid.
> tags 811993 + sid stretch
Bug #811993 [terminatorx] terminatorx: FTBFS with GCC 6: call overloaded is 
ambiguous
Added tag(s) stretch and sid.
> tags 811991 + sid stretch
Bug #811991 [hyperrogue] hyperrogue: FTBFS with GCC 6: call overloaded is 
ambiguous
Added tag(s) sid and stretch.
> tags 811990 + sid
Bug #811990 [linbox] linbox: FTBFS with GCC 6: call overloaded is ambiguous
Added tag(s) sid.
> tags 811988 + sid stretch
Bug #811988 [libcgicc] libcgicc: FTBFS with GCC 6: call overloaded is ambiguous
Added tag(s) stretch and sid.
> tags 811959 + sid stretch
Bug #811959 [curlpp] curlpp: FTBFS with GCC 6: is deprecated
Added tag(s) sid and stretch.
> tags 811954 + sid stretch
Bug #811954 [binutils-msp430] binutils-msp430: FTBFS with GCC 6: left shift of 
negative value
Added tag(s) stretch and sid.
> tags 811950 + sid stretch
Bug #811950 [openhpi] openhpi: FTBFS with GCC 6: unable to find string literal 
operator
Added tag(s) stretch and sid.
> tags 811945 + sid stretch
Bug #811945 [ucimf-openvanilla] ucimf-openvanilla: FTBFS with GCC 6: unable to 
find string literal operator
Added tag(s) stretch and sid.
> tags 811919 + sid stretch
Bug #811919 [objcryst-fox] objcryst-fox: FTBFS with GCC 6: use of deleted 
function
Added tag(s) sid and stretch.
> tags 811912 + sid stretch
Bug #811912 [tandem-mass] tandem-mass: FTBFS with GCC 6: declared in this scope
Added tag(s) stretch and sid.
> tags 811908 + sid stretch
Bug #811908 [kvirc] kvirc: FTBFS with GCC 6: invalid conversion
Added tag(s) sid and stretch.
> tags 811907 + sid stretch
Bug #811907 [music] music: FTBFS with GCC 6: invalid conversion
Added tag(s) sid and stretch.
> tags 811896 + sid stretch
Bug #811896 [percona-xtrabackup] percona-xtrabackup: FTBFS with GCC 6: 
inconsistent user-defined literal suffixes
Added tag(s) stretch and sid.
> tags 811888 + sid stretch
Bug #811888 [aegis] aegis: FTBFS with GCC 6: declaration of ... has a different 
exception specifier
Added tag(s) stretch and sid.
> tags 811887 + sid stretch
Bug #811887 [duma] duma: FTBFS with GCC 6: declaration of ... has a different 
exception specifier
Added tag(s) sid and stretch.
> tags 811882 + sid stretch
Bug #811882 [knutclient] knutclient: FTBFS with GCC 6: no matching function for 
call to
Added tag(s) stretch and sid.
> tags 811877 + sid stretch
Bug #811877 [zinnia] zinnia: FTBFS with GCC 6: no matching function for call to
Added tag(s) stretch and sid.
> tags 811874 + sid stretch
Bug #811874 [kftpgrabber] kftpgrabber: FTBFS with GCC 6: no matching function 
for call to

Processed: tagging 811723, tagging 811719, tagging 811717, found 811707 in 1.03+repack-3, tagging 811702 ...

[Debian Bug Tracking System]

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

> tags 811723 + sid stretch
Bug #811723 [fcitx-unikey] fcitx-unikey: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> tags 811719 + sid stretch
Bug #811719 [fbterm] fbterm: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> tags 811717 + sid stretch
Bug #811717 [ivtools] ivtools: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> found 811707 1.03+repack-3
Bug #811707 [src:ucl] gcc-6 fails to compile a valid code
Marked as found in versions ucl/1.03+repack-3.
> tags 811702 + sid stretch
Bug #811702 [librg-blast-parser-perl] FTBFS with GCC 6: macro passed X 
arguments, takes Y
Added tag(s) sid and stretch.
> tags 811699 + sid stretch
Bug #811699 [mswatch] FTBFS with GCC 6: macro passed X arguments, takes Y
Added tag(s) sid and stretch.
> tags 811673 + sid stretch
Bug #811673 [pyodbc] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811672 + sid stretch
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811671 + sid stretch
Bug #811671 [audacity] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811663 + sid stretch
Bug #811663 [tora] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811657 + sid stretch
Bug #811657 [libbpp-core] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811656 + sid stretch
Bug #811656 [starvoyager] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811655 + sid stretch
Bug #811655 [starplot] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811654 + sid stretch
Bug #811654 [open-invaders] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811653 + sid stretch
Bug #811653 [libaria] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811647 + sid stretch
Bug #811647 [scorched3d] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811645 + sid stretch
Bug #811645 [ams] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811644 + sid stretch
Bug #811644 [idba] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811643 + sid stretch
Bug #811643 [bloboats] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811640 + sid stretch
Bug #811640 [dasher] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811635 + sid stretch
Bug #811635 [libfolia] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811634 + sid stretch
Bug #811634 [meshlab] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811632 + sid stretch
Bug #811632 [hupnp] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811629 + sid stretch
Bug #811629 [tagua] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811628 + sid stretch
Bug #811628 [kyototycoon] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811621 + sid stretch
Bug #811621 [critterding] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811619 + sid stretch
Bug #811619 [gbgoffice] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811616 + sid stretch
Bug #811616 [warmux] FTBFS with GCC 6: cannot convert x to y
Added tag(s) sid and stretch.
> tags 811595 + sid stretch
Bug #811595 [upx-ucl] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) sid and stretch.
> tags 811594 + sid stretch
Bug #811594 [chordii] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) sid and stretch.
> tags 811591 + sid stretch
Bug #811591 [ifhp] FTBFS with GCC 6: statement indented as if it were guarded by
Ignoring request to alter tags of bug #811591 to the same tags previously set
> tags 811588 + sid stretch
Bug #811588 [grail] FTBFS with GCC 6: statement indented as if it were guarded 
by
Added tag(s) sid and stretch.
> tags 811585 + sid stretch
Bug #811585 [clutter-gesture] FTBFS with GCC 6: statement indented as if it 
were guarded by
Added tag(s) stretch and sid.
> tags 811584 + sid stretch
Bug #811584 [phalanx] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) stretch and sid.
> tags 811582 + sid stretch
Bug #811582 [ion] FTBFS with GCC 6: statement indented as if it were guarded by
Added tag(s) stretch and sid.
> tags 811578 + sid stretch
Bug #811578 [confetti] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) sid and stretch.
> tags 829109 + sid stretch
Bug #829109 [src:acepack] acepack: FTBFS: dh_clean: Compatibility levels before 
5 are no longer supported (level 4 requested)
Added tag(s) sid and stretch.
> tags 822711 + sid stretch
Bug #822711 {Done: Paul Wise } [chromium-bsu] chromium-bsu: 
FTBFS 

Bug#811886: marked as done (grass: FTBFS with GCC 6: declaration of ... has a different exception specifier)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 23:30:51 +
with message-id 
and subject line Bug#811886: fixed in grass 7.0.4-3
has caused the Debian Bug report #811886,
regarding grass: FTBFS with GCC 6: declaration of ... has a different exception 
specifier
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.)


-- 
811886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Version: 7.0.2-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-exception-specifier

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
...
> c++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC  
> -I/<>/dist.x86_64-pc-linux-gnu/include 
> -I/<>/dist.x86_64-pc-linux-gnu/include
> -DPACKAGE=\""grasslibs"\"   
> -I/<>/dist.x86_64-pc-linux-gnu/include 
> -I/<>/dist.x86_64-pc-linux-gnu/include -DRELDIR=\"lib/iostream\" 
> -o OBJ.x86_64-pc-linux-gnu/rtimer.o -c rtimer.cpp
> mm.cpp: In function 'void* operator new [](size_t)':
> mm.cpp:279:7: error: declaration of 'void* operator new [](size_t) throw 
> (std::bad_alloc)' has a different exception specifier
>  void* operator new[] (size_t sz) throw(std::bad_alloc) {
>^~~~
> 
> In file included from mm.cpp:49:0:
> /<>/dist.x86_64-pc-linux-gnu/include/grass/iostream/mm.h:132:17: 
> note: from previous declaration 'void* operator new [](std::size_t)'
>friend void * operator new[](size_t) throw(std::bad_alloc);
>  ^~~~
> 
> mm.cpp: In function 'void* operator new(size_t)':
> mm.cpp:330:7: error: declaration of 'void* operator new(size_t) throw 
> (std::bad_alloc)' has a different exception specifier
>  void* operator new (size_t sz) throw(std::bad_alloc) {
>^~~~
> 
> In file included from mm.cpp:49:0:
> /<>/dist.x86_64-pc-linux-gnu/include/grass/iostream/mm.h:131:17: 
> note: from previous declaration 'void* operator new(std::size_t)'
>friend void * operator new(size_t) throw(std::bad_alloc);
>  ^~~~
> 
> ../../include/Make/Compile.make:35: recipe for target 
> 'OBJ.x86_64-pc-linux-gnu/mm.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: grass
Source-Version: 7.0.4-3

We believe that the bug you reported is fixed in the latest version of
grass, 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.
Bas Couwenberg  (supplier of updated grass 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: Thu, 30 Jun 2016 23:21:27 +0200
Source: grass
Binary: grass grass-core grass-gui grass-doc grass-dev-doc grass-dev
Architecture: source amd64 all
Version: 7.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 grass  - Geographic Resources Analysis Support System (GRASS GIS)
 grass-core - GRASS GIS core components
 grass-dev  - GRASS GIS development files
 grass-dev-doc - GRASS GIS Programmers' Manual
 grass-doc  - GRASS GIS user documentation
 grass-gui  - GRASS GIS graphical user interfaces
Closes: 811886
Changes:
 grass (7.0.4-3) unstable; urgency=medium
 .
   * Add upstream patch to fix FTBFS with GCC 6.
 (closes: #811886)
   * Add patch to fix spelling errors.
Checksums-Sha1:
 85863e201b96ea4fb83aa6da69f27c189355229a 2749 grass_7.0.4-3.dsc
 e1eac7fda2c24dc7cc29e3f491a0ad1914764697 29104 grass_7.0.4-3.debian.tar.xz
 

Bug#795081: marked as done (Incompatible with subversion 1.9)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 22:37:44 +
with message-id 
and subject line Bug#795081: fixed in svn-all-fast-export 1.0.10+git4158cb06-1
has caused the Debian Bug report #795081,
regarding Incompatible with subversion 1.9
to be marked as done.

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

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


-- 
795081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: svn-all-fast-export
Version: 1.0.10-3
Severity: serious
Tags: stretch sid

Since I upgraded subversion to 1.9 today, svn-all-fast-export can no
longer perform an svn-to-git conversion with a previously working set
of rules.  It stops with an error message like:

svn: E160013: File not found: revision 3034, path 
'/branches/kernel-image-2.6.11/arch/i386/config.common'

I can provide more details (like the complete rules) if you like.

Ben.

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

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

Versions of packages svn-all-fast-export depends on:
ii  git 1:2.5.0-1
ii  libapr1 1.5.1-3
ii  libc6   2.19-19
ii  libgcc1 1:5.1.1-14
ii  libqtcore4  4:4.8.7+dfsg-1
ii  libstdc++6  5.1.1-14
ii  libsvn1 1.9.0-1

svn-all-fast-export recommends no packages.

svn-all-fast-export suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: svn-all-fast-export
Source-Version: 1.0.10+git4158cb06-1

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated svn-all-fast-export 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Jul 2016 06:48:01 +1000
Source: svn-all-fast-export
Binary: svn-all-fast-export
Architecture: source
Version: 1.0.10+git4158cb06-1
Distribution: unstable
Urgency: medium
Maintainer: Stuart Prescott 
Changed-By: Stuart Prescott 
Closes: 795081
Description: 
 svn-all-fast-export - fast-import based converter to convert repos from 
Subversion to g
Changes:
 svn-all-fast-export (1.0.10+git4158cb06-1) unstable; urgency=medium
 .
   * New upstream version from git (commit 4158cb06)
 - fixes incompatiblity with subversion 1.9 (Closes: #795081); thanks
   to Ben Hutchings for the heads-up.
   * Update Standards-Version to 3.9.8 (no changes required).
   * Change Vcs-* fields to use https URLs.
   * Enable additional hardening options.
Checksums-Sha1: 
 47849a1c8362c1e0b1954333f75ce427d616c079 2130 
svn-all-fast-export_1.0.10+git4158cb06-1.dsc
 4a8e4a9fee928665c0952a4f14ceea2af046e428 29916 
svn-all-fast-export_1.0.10+git4158cb06.orig.tar.gz
 400d51a55e9d69422d3e3157e3056a1c1ee9f30c 28600 
svn-all-fast-export_1.0.10+git4158cb06-1.debian.tar.xz
Checksums-Sha256: 
 2b0318365ef9b511246a636188e56379dcd096f553d4b107cc3a1ebd58148d8b 2130 
svn-all-fast-export_1.0.10+git4158cb06-1.dsc
 4e5c1249bb121748fadc60324734efa87695959b57268a4bbe2f225d6fae953a 29916 
svn-all-fast-export_1.0.10+git4158cb06.orig.tar.gz
 8105185ace54ede68b1806d9c441a407b4edb56d2574f0a72f1fd84570e7398c 28600 
svn-all-fast-export_1.0.10+git4158cb06-1.debian.tar.xz
Files: 
 1e5666d309bbde5e93f026990333e18d 2130 devel extra 
svn-all-fast-export_1.0.10+git4158cb06-1.dsc
 3329fe29d057dd47f49973c71e18db4e 29916 devel extra 
svn-all-fast-export_1.0.10+git4158cb06.orig.tar.gz
 cd6929fd4e71c6465a66eee98d6f2b46 28600 devel extra 
svn-all-fast-export_1.0.10+git4158cb06-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdY5qAAoJELvBfrsTlvL3534P/1J0LaQNNn1B6BrW7DiIU0VC
OZmJZIfGl+GWJ36LRKLahPQKYBgx1yqoZqV2vK7XXL92wh8WP9DqjPEtGmNQqX2u

Bug#811744: marked as done (libraw: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 22:35:53 +
with message-id 
and subject line Bug#811744: fixed in libraw 0.17.2-3
has caused the Debian Bug report #811744,
regarding libraw: 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.)


-- 
811744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libraw
Version: 0.17.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
...
> make[1]: Entering directory '/<>'
> /bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DPACKAGE_NAME=\"LibRaw\" 
> -DPACKAGE_TARNAME=\"libraw\" -DPACKAGE_VERSION=\"0.17.1\" 
> -DPACKAGE_STRING=\"LibRaw\ 0.17.1\" -DPACKAGE_BUGREPORT=\"i...@libraw.org\" 
> -DPACKAGE_URL=\"http://www.libraw.org\; -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_JPEGLIB_H=1 -DHAVE_JPEGLIB_H=1 
> -DHAVE_JASPER_JASPER_H=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/local/include -DUSE_JPEG -DUSE_JPEG8 -DUSE_JASPER  -DUSE_LCMS2  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c -o 
> internal/dcraw_common.lo internal/dcraw_common.cpp
> libtool: compile:  g++ -DPACKAGE_NAME=\"LibRaw\" -DPACKAGE_TARNAME=\"libraw\" 
> -DPACKAGE_VERSION=\"0.17.1\" "-DPACKAGE_STRING=\"LibRaw 0.17.1\"" 
> -DPACKAGE_BUGREPORT=\"i...@libraw.org\" 
> -DPACKAGE_URL=\"http://www.libraw.org\; -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_JPEGLIB_H=1 -DHAVE_JPEGLIB_H=1 
> -DHAVE_JASPER_JASPER_H=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/local/include -DUSE_JPEG -DUSE_JPEG8 -DUSE_JASPER -DUSE_LCMS2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c 
> internal/dcraw_common.cpp  -fPIC -DPIC -o internal/.libs/dcraw_common.o
> In file included from ./libraw/libraw.h:40:0,
>  from internal/dcraw_common.cpp:29:
> ./libraw/libraw_datastream.h:96:10: warning: 'template class 
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>  std::auto_ptr f; /* will close() automatically through 
> dtor */
>   ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from ./libraw/libraw_datastream.h:38,
>  from ./libraw/libraw.h:40,
>  from internal/dcraw_common.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In file included from ./libraw/libraw.h:40:0,
>  from internal/dcraw_common.cpp:29:
> ./libraw/libraw_datastream.h:97:10: warning: 'template class 
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>  std::auto_ptr saved_f; /* when *f is a subfile, *saved_f 
> is the master file */
>   ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from ./libraw/libraw_datastream.h:38,
>  from ./libraw/libraw.h:40,
>  from internal/dcraw_common.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> internal/dcraw_common.cpp: In member function 'void 
> LibRaw::vng_interpolate()':
> internal/dcraw_common.cpp:4539:3: error: narrowing conversion of '128' from 
> 'int' to 'signed char' inside { } [-Wnarrowing]
>}, chood[] = { -1,-1, -1,0, -1,+1, 0,+1, +1,+1, +1,0, +1,-1, 0,-1 };
>^
> 
> internal/dcraw_common.cpp:4539:3: error: narrowing conversion of '136' from 
> 'int' to 'signed char' inside { } [-Wnarrowing]
> internal/dcraw_common.cpp:4539:3: error: narrowing conversion of '128' from 
> 'int' 

Bug#811811: marked as done (mriconvert: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 22:36:08 +
with message-id 
and subject line Bug#811811: fixed in mriconvert 1:2.0.8-4
has caused the Debian Bug report #811811,
regarding mriconvert: 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.)


-- 
811811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mriconvert
Version: 1:2.0.8-3
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
...
> /usr/bin/c++   -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -isystem 
> /usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -isystem 
> /usr/include/wx-3.0  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -pthread   -o 
> CMakeFiles/MRIConvert.dir/AnalyzeVolume.cpp.o -c 
> /<>/AnalyzeVolume.cpp
> /<>/DicomFile.cpp: In member function 'bool 
> jcs::DicomFile::mFindElement(const jcs::DicomTag&, jcs::DicomElement&, 
> std::istream&)':
> /<>/DicomFile.cpp:1049:17: error: no match for 'operator==' 
> (operand types are 'std::istream {aka std::basic_istream}' and 
> 'std::ifstream {aka std::basic_ifstream}')
>if (input == mInputFile) {
>~~^
> 
> /<>/DicomFile.cpp:1049:17: note: candidate: operator==(int, int) 
> 
> /<>/DicomFile.cpp:1049:17: note:   no known conversion for 
> argument 2 from 'std::ifstream {aka std::basic_ifstream}' to 'int'
--- End Message ---
--- Begin Message ---
Source: mriconvert
Source-Version: 1:2.0.8-4

We believe that the bug you reported is fixed in the latest version of
mriconvert, 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.
Gert Wollny  (supplier of updated mriconvert 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: Thu, 30 Jun 2016 19:43:45 +
Source: mriconvert
Binary: mriconvert
Architecture: source
Version: 1:2.0.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 mriconvert - medical image file conversion utility
Closes: 811811
Changes:
 mriconvert (1:2.0.8-4) unstable; urgency=medium
 .
   [ Gert Wollny ]
   * Team upload.
   * d/p/gcc-6: Fix compilation with Gcc-6, Closes: #811811
   * cme fix dpkg-control
 .
   [ Andreas Tille ]
   * Secure Vcs-Browser
   * hardening=+bindnow
   * d/control: remove duplicated section field
Checksums-Sha1:
 a15e335df85fd82d6bf0cd933be5b133fb4a6130 2042 mriconvert_2.0.8-4.dsc
 656f1851b56dcc70994aeef47fa26381fa1dd715 7696 mriconvert_2.0.8-4.debian.tar.xz
Checksums-Sha256:
 9663cc565571ef75b461dd09a11d8c9ac75fb1422849feae4a8519809cd7bb12 2042 
mriconvert_2.0.8-4.dsc
 e0c03945ebc514d8ba1756aeb95e6486c1530d82754c786e4b9d0e3ba1ad2c8b 7696 
mriconvert_2.0.8-4.debian.tar.xz
Files:
 8ae13236300a66e9a807193a1d88b074 2042 science optional mriconvert_2.0.8-4.dsc
 0278548f5ff6fb03b2a51d1f68bf60aa 7696 science optional 
mriconvert_2.0.8-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdY4DAAoJEFeKBJTRxkbRNjYQAIDVB4CRHQCWEjlO6zBDcQrC
dF2PmXgrztMpPJQz4yNGHdUHhvIwC+LYBGjz9RqYTkXyZMVSG3OUssJghupwkh5g
/85LK1k1fJyR3XY1+w0b7osYay1ZxuZvwun2s5jNL2uM+rmnBNoi9doJSr5SMFat
SstgpVFwjv3TZU0l0gjniHwrhsNx/Gd1+6GsCIoNrmYi6ZvzCbxMuUTGampiqNI9
RcfO8bxQW8v6whs1XXg4qv+XTjajRsInB4+rglyuBUyr4033qtFbNe+1GXHpMmLF
t8R1MgKAhLDjDCFIcp86ia+mVCO7x6ndEAkmqwgaWjHu2Q1hIofvdpulE0EuxebG

Bug#812284: Workaround for googletest

[Christian Hofstaedtler]

Dear Maintainer,

while the issue in googletest is still open, please consider
applying a workaround for this bug.

Attached you'll find a proposed patch.

I'll upload this soon to a short DELAYED queue, please let me know
if you want me to delay this further or cancel the upload.

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

>From ab83c842b00a6c3d31939fb4722daf0c7a22c440 Mon Sep 17 00:00:00 2001
From: Christian Hofstaedtler 
Date: Thu, 30 Jun 2016 22:06:17 +
Subject: [PATCH] Apply temporary workaround for segfault in googletest

Closes: #812284

Similar to:
https://github.com/shogun-toolbox/shogun/pull/2989/commits/17d452f67f5bc2b0914c013ede3d2a61c0584fd9
---
 ...round-bug-in-googletest-fixing-bug-812284.patch | 32 ++
 debian/patches/series  |  1 +
 2 files changed, 33 insertions(+)
 create mode 100644 
debian/patches/0003-Workaround-bug-in-googletest-fixing-bug-812284.patch

diff --git 
a/debian/patches/0003-Workaround-bug-in-googletest-fixing-bug-812284.patch 
b/debian/patches/0003-Workaround-bug-in-googletest-fixing-bug-812284.patch
new file mode 100644
index 000..8eacf0d
--- /dev/null
+++ b/debian/patches/0003-Workaround-bug-in-googletest-fixing-bug-812284.patch
@@ -0,0 +1,32 @@
+From: Christian Hofstaedtler 
+Date: Thu, 30 Jun 2016 22:05:02 +
+Subject: Workaround bug in googletest, fixing bug #812284
+
+---
+ test/CMakeLists.txt | 13 +
+ 1 file changed, 13 insertions(+)
+
+diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt
+index 61f1f7f..2083d5e 100644
+--- a/test/CMakeLists.txt
 b/test/CMakeLists.txt
+@@ -13,6 +13,19 @@ if("${CMAKE_CXX_COMPILER_ID}" MATCHES "GNU" OR
+   set(yaml_test_flags "-Wno-c99-extensions -Wno-variadic-macros 
-Wno-sign-compare")
+ endif()
+ 
++# In some cases gTest segfaults with GCC >= 6.0.0.  This is a dirty fix.
++# TODO: Update to gTest-release with proper support for GCC >= 6.0.0.
++# See:  https://github.com/google/googletest/issues/705
++IF(CMAKE_COMPILER_IS_GNUCXX)
++  # in order to support cmake 2.8.7 and older
++  IF(NOT CMAKE_CXX_COMPILER_VERSION)
++  include(CheckCompiler)
++  ENDIF(NOT CMAKE_CXX_COMPILER_VERSION)
++  IF(NOT "${CMAKE_CXX_COMPILER_VERSION}" VERSION_LESS "6.0.0")
++  set(yaml_test_flags "${yaml_test_flags} 
-fno-delete-null-pointer-checks")
++  ENDIF(NOT "${CMAKE_CXX_COMPILER_VERSION}" VERSION_LESS "6.0.0")
++ENDIF(CMAKE_COMPILER_IS_GNUCXX)
++
+ file(GLOB test_headers [a-z_]*.h)
+ file(GLOB test_sources [a-z_]*.cpp integration/[a-z_]*.cpp node/[a-z_]*.cpp)
+ file(GLOB test_new_api_sources new-api/[a-z]*.cpp)
diff --git a/debian/patches/series b/debian/patches/series
index 099bc08..925ec14 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 pkgconfig.patch
 install-cmake-dev-files.patch
+0003-Workaround-bug-in-googletest-fixing-bug-812284.patch
-- 
2.8.1

Bug#829140: mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}'

[Simon McVittie]

Control: tags 829140 - patch

On Thu, 30 Jun 2016 at 22:55:12 +0100, Simon McVittie wrote:
> Since converting to dh, mutter fails to build on what appear to be all
> 32-bit architectures. I believe the patch attached to upstream bug
> https://bugzilla.gnome.org/show_bug.cgi?id=762407 is the correct solution.

That patch is not a full solution: there are other compiler warnings
on i386, which are made fatal by the default configure options.

I think the real root cause is a missing backslash in debian/rules,
which led to some of the intended configure options being ignored.
I've fixed that in svn, but not fully tested the result, so I haven't
released it so far.

S

Processed: Re: Bug#829140: mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}'

[Debian Bug Tracking System]

Processing control commands:

> tags 829140 - patch
Bug #829140 [src:mutter] mutter: FTBFS on ILP32 architectures: format '%ld' 
expects 'long int', but argument 3 has type 'gint64 {aka long long int}'
Removed tag(s) patch.

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

Processed: tagging 817430, found 817430 in 0.99.36+nmu2

[Debian Bug Tracking System]

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

> tags 817430 =
Bug #817430 [src:dh-kpatches] dh-kpatches: Removal of debhelper compat 4
Removed tag(s) stretch and sid.
> found 817430 0.99.36+nmu2
Bug #817430 [src:dh-kpatches] dh-kpatches: Removal of debhelper compat 4
Marked as found in versions dh-kpatches/0.99.36+nmu2.
> thanks
Stopping processing here.

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

Bug#812016: marked as done (soundmodem: FTBFS with GCC 6: return-statement with a value)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 15:15:03 -0700
with message-id 

Bug#829142: debhelper: dh_strip triggers fatal lintian error for packages with multiple hardlinks

[Sven Joachim]

Package: debhelper
Version: 9.20160618.1
Severity: serious

For packages which ship files with multiple hardlinks, dh_strip produces
broken -dbgsym packages that trigger the
library-in-debug-or-profile-should-not-be-stripped lintian error, which
unfortunately leads to auto-rejection by the FTP masters and cannot be
overridden.  To reproduce the problem:

- Find a suitable source package, say "apt-get source ed".

- Edit debian/rules and add this override to it to produce a file with
  two hardlinks:

override_dh_strip:
ln debian/ed/bin/ed debian/ed/bin/ed2
dh_strip

- Build the package, this already produces a warning from objcopy:

,
| make[1]: Verzeichnis „/tmp/ed-1.10“ wird betreten
| ln debian/ed/bin/ed debian/ed/bin/ed2
| dh_strip
|   install -d debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8
|   objcopy --only-keep-debug --compress-debug-sections debian/ed/bin/ed2 
debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
|   chmod 0644 
debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
|   strip --remove-section=.comment --remove-section=.note debian/ed/bin/ed2
|   objcopy --add-gnu-debuglink 
debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
 debian/ed/bin/ed2
|   objcopy --only-keep-debug --compress-debug-sections debian/ed/bin/ed 
debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
|   chmod 0644 
debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
|   strip --remove-section=.comment --remove-section=.note debian/ed/bin/ed
|   objcopy --add-gnu-debuglink 
debian/.debhelper/ed/dbgsym-root/usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
 debian/ed/bin/ed
| objcopy: debian/ed/bin/stNvhs2Q: debuglink section already exists
`

- Run lintian on the -dbgsym package, this gives an error and a warning:

,
| E: ed-dbgsym: library-in-debug-or-profile-should-not-be-stripped 
usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
| W: ed-dbgsym: debug-file-with-no-debug-symbols 
usr/lib/debug/.build-id/d8/571320f0b57dd55598aaff154e79dfca08cae2.debug
`

Today, the mesa 12.0.0~rc4-1 upload has been auto-rejected because of
this problem: https://lists.debian.org/debian-x/2016/06/msg00204.html.


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20160430.1
ii  binutils 2.26.1-1
ii  dh-autoreconf12
ii  dh-strip-nondeterminism  0.019-1
ii  dpkg 1.18.8
ii  dpkg-dev 1.18.7
ii  file 1:5.28-2
ii  libdpkg-perl 1.18.7
ii  man-db   2.7.5-1
ii  perl 5.22.2-1
ii  po-debconf   1.0.19

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201606

-- no debconf information

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Michael Biebl]

Am 30.06.2016 um 21:37 schrieb Eric Valette:
> On 30/06/2016 21:32, Felipe Sateler wrote:
>> On 30 June 2016 at 15:20, Eric Valette  wrote:
>>> On 30/06/2016 21:18, Martin Pitt wrote:

 Control: reassing -1 libaudit1
 Control: forcemerge 828991 -1

 Hello Eric,
>>>
>>>
 This has never been a supported configuration, and just because it
 happend to mostly work once it doesn't mean that it can be guaranteed
 forever, sorry.
>>>
>>>
>>> I have an initrd on this machine so this is something else
>>
>> Your initrd needs to mount /usr. Which one are you using?
>>
> 
> initramfs-tools

Which version? Can you attach your initrd please.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#829140: mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}'

[Simon McVittie]

Source: mutter
Version: 3.20.3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: upstream patch
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=762407

Since converting to dh, mutter fails to build on what appear to be all
32-bit architectures. I believe the patch attached to upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=762407 is the correct solution.

S
--- a/src/core/startup-notification.c	2016-06-06 12:13:27.100251933 +0200
+++ a/src/core/startup-notification.c	2016-06-06 12:13:42.554956773 +0200
@@ -418,7 +418,7 @@ 
   elapsed = ctod->now - timestamp;
 
   meta_topic (META_DEBUG_STARTUP,
-  "Sequence used %ld ms vs. %d max: %s\n",
+  "Sequence used %" G_GINT64_FORMAT " ms vs. %d max: %s\n",
   elapsed, STARTUP_TIMEOUT,
   meta_startup_notification_sequence_get_id (sequence));
 

Processed: Re: Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Debian Bug Tracking System]

Processing control commands:

> unmerge -1
Bug #829127 [libaudit1] systemd: Please make sure /lib/systemd/systemd is not 
linked with something in /usr
Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 
which is installed in /usr
Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
Disconnected #829127 from all other report(s).
> retitle -1 initrd does not mount /usr
Bug #829127 [libaudit1] systemd: Please make sure /lib/systemd/systemd is not 
linked with something in /usr
Changed Bug title to 'initrd does not mount /usr' from 'systemd: Please make 
sure /lib/systemd/systemd is not linked with something in /usr'.
> reassign -1 initramfs-tools
Bug #829127 [libaudit1] initrd does not mount /usr
Bug reassigned from package 'libaudit1' to 'initramfs-tools'.
No longer marked as found in versions audit/1:2.6.1-1.
Ignoring request to alter fixed versions of bug #829127 to the same values 
previously set
> tags -1 moreinfo
Bug #829127 [initramfs-tools] initrd does not mount /usr
Added tag(s) moreinfo.

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

Bug#829088: ccache may silently miscompile symlinked source files

[Joel Rosdahl]

Thanks for the bug report. I have reproduced the issue, see the attached
script. Yes, to trigger the bug, the source file path must be absolute and
CCACHE_BASEDIR must be enabled.

The behavior change in question comes from this commit: <
https://github.com/ccache/ccache/commit/2df269a3121889ebcdfa5d98dfb4d675f690e039>.
It's included in ccache 3.1.8 and newer.

Not sure what to do, though. Have to think about it some more.

-- Joel

On 30 June 2016 at 14:15, Stefan Fritsch  wrote:

> found 829088 3.2.5-1
> thanks
>
> Version 3.2.5-1 is also affected by this issue.
>
> Attached is a log file from that version.
>
> Since the path names are rather complicated in the examples: The dir with
> the symlinked source files is (note the obj in the 3rd component):
>
>
> /changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc-minimal/libc/src/libc/stdlib/malloc-standard/free.c
>
> The path to the source file with all symlinks resolved is (there is no
> obj/ and no amd64/ in this path):
>
>
> /changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/contrib/uclibc/libc/stdlib/malloc-standard/free.c


debian-bug-829088
Description: Binary data

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Felipe Sateler]

Control: unmerge -1
Control: retitle -1 initrd does not mount /usr
Control: reassign -1 initramfs-tools
Control: tags -1 moreinfo

On 30 June 2016 at 16:24, Eric Valette  wrote:
> On 30/06/2016 22:17, Eric Valette wrote:
>>
>> On 30/06/2016 22:06, Felipe Sateler wrote:
>>
 initramfs-tools
>>>
>>>
>>> If you add debug to your kernel command line, you should get a
>>> (possibly very verbose) log at /run/initramfs/initramfs.debug. Does it
>>> say anything about mounting /usr?
>>
>>
>> Same answer : I cannot right now. But I expect the mount to be automatic
>> or I should have the classical message at boot saying /usr not mounted
>> and this will break...
>
>
> I indeed have the message, so initrd is not mounting /usr for some reason..
>
> : systemd 230 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR
> +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SEC
> Jun 30 20:42:48 htpc1 systemd[1]: Detected architecture x86-64.
> Jun 30 20:42:48 htpc1 systemd[1]: Set hostname to .
> Jun 30 20:42:48 htpc1 systemd[1]: /usr appears to be on its own filesystem
> and is not already mounted. This is not a supported setup. Some things will
> probably break (sometimes ev

So it looks like the initrd did not mount your /usr. Reassigning to
initramfs-tools

Please post the log of the initramfs, and any relevant details (fstab,
initramfs-tools.conf) so that the problem may be diagnosed.


-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#829003: wine: FTBFS since unicode 9 update

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #829003 [wine] wine: FTBFS since unicode 9 update
Added tag(s) pending.

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

Bug#829003: wine: FTBFS since unicode 9 update

[Jens Reyer]

control: tags -1 + pending

Fix committed, based on the previously mentioned 2 commits. Some
files/contents were moved between Wine 1.8 and 1.9.13 (which carries the
Unicode 9.0 changes), which made spotting changes to autogenerated files
a bit harder.
In the resulting patch there are still some data tables and listings -
but these aren't generated automatically, so are indeed needed.

Greets
jre

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Eric Valette]

On 30/06/2016 22:17, Eric Valette wrote:

On 30/06/2016 22:06, Felipe Sateler wrote:


initramfs-tools


If you add debug to your kernel command line, you should get a
(possibly very verbose) log at /run/initramfs/initramfs.debug. Does it
say anything about mounting /usr?


Same answer : I cannot right now. But I expect the mount to be automatic
or I should have the classical message at boot saying /usr not mounted
and this will break...


I indeed have the message, so initrd is not mounting /usr for some reason..

: systemd 230 running in system mode. (+PAM +AUDIT +SELINUX +IMA 
+APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ 
-LZ4 +SEC

Jun 30 20:42:48 htpc1 systemd[1]: Detected architecture x86-64.
Jun 30 20:42:48 htpc1 systemd[1]: Set hostname to .
Jun 30 20:42:48 htpc1 systemd[1]: /usr appears to be on its own 
filesystem and is not already mounted. This is not a supported setup. 
Some things will probably break (sometimes ev


--eric

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Felipe Sateler]

On 30 June 2016 at 15:37, Eric Valette  wrote:
> On 30/06/2016 21:32, Felipe Sateler wrote:
>>
>> On 30 June 2016 at 15:20, Eric Valette  wrote:
>>>
>>> On 30/06/2016 21:18, Martin Pitt wrote:


 Control: reassing -1 libaudit1
 Control: forcemerge 828991 -1

 Hello Eric,
>>>
>>>
>>>
 This has never been a supported configuration, and just because it
 happend to mostly work once it doesn't mean that it can be guaranteed
 forever, sorry.
>>>
>>>
>>>
>>> I have an initrd on this machine so this is something else
>>
>>
>> Your initrd needs to mount /usr. Which one are you using?
>>
>
> initramfs-tools

If you add debug to your kernel command line, you should get a
(possibly very verbose) log at /run/initramfs/initramfs.debug. Does it
say anything about mounting /usr?

-- 

Saludos,
Felipe Sateler

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Laurent Bigonville]

On Thu, 30 Jun 2016 21:52:09 +0200 Eric Valette  
wrote:

> On 30/06/2016 21:50, Laurent Bigonville wrote:
> > On Thu, 30 Jun 2016 21:37:24 +0200 Eric Valette 
> > wrote:
> >> On 30/06/2016 21:32, Felipe Sateler wrote:
> >> > On 30 June 2016 at 15:20, Eric Valette  wrote:
> >> >> On 30/06/2016 21:18, Martin Pitt wrote:
> >> >>>
> >> >>> Control: reassing -1 libaudit1
> >> >>> Control: forcemerge 828991 -1
> >> >>>
> >> >>> Hello Eric,
> >> >>
> >> >>
> >> >>> This has never been a supported configuration, and just because it
> >> >>> happend to mostly work once it doesn't mean that it can be 
guaranteed

> >> >>> forever, sorry.
> >> >>
> >> >>
> >> >> I have an initrd on this machine so this is something else
> >> >
> >> > Your initrd needs to mount /usr. Which one are you using?
> >> >
> >>
> >> initramfs-tools
> >
> > Is /usr present in the fstab?
>
> Yes attached:
>
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name 
devices

> # that works even if disks are added and removed. See fstab(5).
> #
> #  
> # / was on /dev/sda1 during installation
> /dev/sda1 / ext4
> defaults,noatime,nodiratime,discard,errors=remount-ro 0 1
> # /home was on /dev/sda9 during installation
> LABEL=HOME /home ext4
> defaults,noatime,nodiratime,discard 0 2
> # /tmp was on /dev/sda8 during installation
> LABEL=TMP /tmp ext4
> defaults,noatime,nodiratime,discard 0 2
> # /usr was on /dev/sda3 during installation
> LABEL=USR /usr ext4
> defaults,noatime,nodiratime,discard 0 2

Could you try to replace the label with /dev/sda3?

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Eric Valette]

On 30/06/2016 21:46, Martin Pitt wrote:

Hello Eric,

Eric Valette [2016-06-30 21:33 +0200]:

I have an initrd on this machine so this is something else


OK, I owe you an apology then, sorry. In #771652 you didn't yet, so I
just assumed that was still the case.


I was lucky to see at the top of the screen something about shared object,
booted with sysvinit and found it. I suspect the bug is true even with an
initrd this time. Maybe analysing the initrd could tell us.


That's strange indeed. Mind booting with "debug" and attaching
/run/initramfs/initramfs.debug?




Cannot right now as it is my htpc and tv recorder. Sorry. Will do later. 
In the meantime:


lsinitramfs /boot/initrd.img-4.4.14
/boot/initrd.img-4.4.14
.
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/AuthenticAMD.bin
.
init
scripts
scripts/local
scripts/nfs
scripts/init-bottom
scripts/init-bottom/udev
scripts/init-bottom/ORDER
scripts/init-top
scripts/init-top/udev
scripts/init-top/all_generic_ide
scripts/init-top/ORDER
scripts/init-top/blacklist
scripts/init-top/keymap
scripts/functions
scripts/local-bottom
scripts/local-bottom/ORDER
scripts/local-bottom/ntfs_3g
scripts/local-premount
scripts/local-premount/ORDER
scripts/local-premount/resume
scripts/local-premount/ntfs_3g
run
lib64
lib64/ld-linux-x86-64.so.2
lib
lib/udev
lib/udev/rules.d
lib/udev/rules.d/60-persistent-storage.rules
lib/udev/rules.d/73-special-net-names.rules
lib/udev/rules.d/80-drivers.rules
lib/udev/rules.d/73-usb-net-by-mac.rules
lib/udev/rules.d/60-persistent-storage-dm.rules
lib/udev/rules.d/70-persistent-net.rules
lib/udev/rules.d/50-firmware.rules
lib/udev/rules.d/50-udev-default.rules
lib/udev/rules.d/75-net-description.rules
lib/udev/rules.d/80-net-setup-link.rules
lib/udev/rules.d/55-dm.rules
lib/udev/scsi_id
lib/udev/ata_id
lib/modules
lib/modules/4.4.14
lib/modules/4.4.14/modules.symbols.bin
lib/modules/4.4.14/modules.symbols
lib/modules/4.4.14/modules.builtin.bin
lib/modules/4.4.14/modules.alias.bin
lib/modules/4.4.14/modules.devname
lib/modules/4.4.14/modules.softdep
lib/modules/4.4.14/modules.dep
lib/modules/4.4.14/modules.alias
lib/modules/4.4.14/modules.dep.bin
lib/modprobe.d
lib/modprobe.d/fbdev-blacklist.conf
lib/modprobe.d/aliases.conf
lib/x86_64-linux-gnu
lib/x86_64-linux-gnu/libm-2.23.so
lib/x86_64-linux-gnu/libuuid.so.1
lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
lib/x86_64-linux-gnu/libpcre.so.3
lib/x86_64-linux-gnu/libattr.so.1
lib/x86_64-linux-gnu/libc.so.6
lib/x86_64-linux-gnu/libblkid.so.1
lib/x86_64-linux-gnu/libpcre.so.3.13.2
lib/x86_64-linux-gnu/libpthread-2.23.so
lib/x86_64-linux-gnu/libcom_err.so.2.1
lib/x86_64-linux-gnu/libacl.so.1
lib/x86_64-linux-gnu/libmount.so.1.1.0
lib/x86_64-linux-gnu/libext2fs.so.2
lib/x86_64-linux-gnu/libe2p.so.2
lib/x86_64-linux-gnu/librt-2.23.so
lib/x86_64-linux-gnu/libudev.so.1.6.4
lib/x86_64-linux-gnu/libdl-2.23.so
lib/x86_64-linux-gnu/libmount.so.1
lib/x86_64-linux-gnu/libpthread.so.0
lib/x86_64-linux-gnu/libntfs-3g.so.871.0.0
lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
lib/x86_64-linux-gnu/libdl.so.2
lib/x86_64-linux-gnu/libkmod.so.2
lib/x86_64-linux-gnu/libext2fs.so.2.4
lib/x86_64-linux-gnu/libcom_err.so.2
lib/x86_64-linux-gnu/ld-2.23.so
lib/x86_64-linux-gnu/libkmod.so.2.3.0
lib/x86_64-linux-gnu/libudev.so.1
lib/x86_64-linux-gnu/libacl.so.1.1.0
lib/x86_64-linux-gnu/libuuid.so.1.3.0
lib/x86_64-linux-gnu/libm.so.6
lib/x86_64-linux-gnu/libc-2.23.so
lib/x86_64-linux-gnu/librt.so.1
lib/x86_64-linux-gnu/libselinux.so.1
lib/x86_64-linux-gnu/libattr.so.1.1.0
lib/x86_64-linux-gnu/libe2p.so.2.3
lib/x86_64-linux-gnu/libblkid.so.1.1.0
lib/x86_64-linux-gnu/libntfs-3g.so.871
lib/systemd
lib/systemd/systemd-udevd
lib/systemd/network
lib/systemd/network/99-default.link
lib/klibc-k3La8MUnuzHQ0_kG8hokcGAC0PA.so
bin
bin/dmesg
bin/ln
bin/cat
bin/resume
bin/readlink
bin/run-init
bin/poweroff
bin/nfsmount
bin/halt
bin/mount
bin/losetup
bin/chroot
bin/nuke
bin/pivot_root
bin/sync
bin/sleep
bin/ntfs-3g
bin/mv
bin/minips
bin/fstype
bin/sh
bin/reboot
bin/mkdir
bin/ipconfig
bin/true
bin/gzip
bin/gunzip
bin/ls
bin/dd
bin/umount
bin/cpio
bin/kill
bin/mknod
bin/mkfifo
bin/udevadm
bin/kmod
bin/false
bin/uname
sbin
sbin/fsck.ext4
sbin/logsave
sbin/dmsetup
sbin/mount.fuse
sbin/blkid
sbin/fsck
sbin/modprobe
sbin/rmmod
sbin/e2fsck
sbin/udevadm
sbin/mount.ntfs
sbin/mount.ntfs-3g
conf
conf/initramfs.conf
conf/arch.conf
conf/conf.d
conf/conf.d/resume
etc
etc/udev
etc/udev/udev.conf
etc/ld.so.conf
etc/modprobe.d
etc/modprobe.d/amd64-microcode-blacklist.conf
etc/modprobe.d/etc-modules-parameters.conf
etc/mtab
etc/fstab
etc/ld.so.conf.d
etc/ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf
etc/ld.so.conf.d/libc.conf
etc/ld.so.conf.d/x86_64-linux-gnu.conf
etc/ld.so.cache

-- eric

Bug#829131: avro-java: FTBFS: Could not resolve dependencies for project org.apache.avro:avro-compiler:bundle:1.7.7

[Chris Lamb]

Source: avro-java
Version: 1.7.7-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,

avro-java fails to build from source in unstable/amd64:

  [..]

  Setting up openjdk-8-jre-headless:amd64 (8u91-b14-3) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to 
provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool 
to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 
to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide 
/usr/bin/unpack200 (unpack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/orbd to 
provide /usr/bin/orbd (orbd) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/servertool to provide 
/usr/bin/servertool (servertool) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/tnameserv to provide 
/usr/bin/tnameserv (tnameserv) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec to 
provide /usr/bin/jexec (jexec) in auto mode
  update-binfmts: warning: Couldn't load the binfmt_misc module.
  Setting up default-jre-headless (2:1.8-57) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-3) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up openjdk-8-jdk-headless:amd64 (8u91-b14-3) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to 
provide /usr/bin/jsadebugd (jsadebugd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii 
to provide /usr/bin/native2ascii (native2ascii) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript (jrunscript) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to 
provide /usr/bin/jhat (jhat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to 
provide /usr/bin/jar (jar) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to 
provide /usr/bin/xjc (xjc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to 
provide /usr/bin/jps (jps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to 
provide /usr/bin/extcheck (extcheck) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to 
provide /usr/bin/jmap (jmap) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to 
provide /usr/bin/jstatd (jstatd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to 

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Eric Valette]

On 30/06/2016 21:50, Laurent Bigonville wrote:

On Thu, 30 Jun 2016 21:37:24 +0200 Eric Valette 
wrote:

On 30/06/2016 21:32, Felipe Sateler wrote:
> On 30 June 2016 at 15:20, Eric Valette  wrote:
>> On 30/06/2016 21:18, Martin Pitt wrote:
>>>
>>> Control: reassing -1 libaudit1
>>> Control: forcemerge 828991 -1
>>>
>>> Hello Eric,
>>
>>
>>> This has never been a supported configuration, and just because it
>>> happend to mostly work once it doesn't mean that it can be guaranteed
>>> forever, sorry.
>>
>>
>> I have an initrd on this machine so this is something else
>
> Your initrd needs to mount /usr. Which one are you using?
>

initramfs-tools


Is /usr present in the fstab?


Yes attached:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
/dev/sda1/   ext4 
defaults,noatime,nodiratime,discard,errors=remount-ro 0   1

# /home was on /dev/sda9 during installation
LABEL=HOME   /home   ext4 
defaults,noatime,nodiratime,discard 0   2

# /tmp was on /dev/sda8 during installation
LABEL=TMP/tmpext4 
defaults,noatime,nodiratime,discard 0   2

# /usr was on /dev/sda3 during installation
LABEL=USR/usrext4 
defaults,noatime,nodiratime,discard 0   2

# /usr/local was on /dev/sda6 during installation
LABEL=USR_LOCAL  /usr/local  ext4 
defaults,noatime,nodiratime,discard 0   2

# /var was on /dev/sda5 during installation
LABEL=VAR/varext4 
defaults,noatime,nodiratime,discard 0   2

# /var/cache was on /dev/sda7 during installation
LABEL=VAR_CACHE  /var/cache  ext4 
defaults,noatime,nodiratime,discard 0   2

# swap was on /dev/sda2 during installation
UUID=8fa6a1ce-a10a-4f8d-af01-c10af388a142 noneswapsw 
 0   0
LABEL=EXT4_TVRECORDS /pvrRecordsext4 
defaults,nofail,x-systemd.device-timeout=1 0   2



--eric

Bug#805547: marked as done (libhtml-calendarmonth-perl: FTBFS: Failed test '(2010/03 i8n) Spanish Mexico (wb:1) using auto-detect')

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 19:49:41 +
with message-id 
and subject line Bug#805547: fixed in libhtml-calendarmonth-perl 2.04-1
has caused the Debian Bug report #805547,
regarding libhtml-calendarmonth-perl: FTBFS: Failed test '(2010/03 i8n) Spanish 
Mexico (wb:1) using auto-detect'
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.)


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

libhtml-calendarmonth-perl fails to build from source in unstable/amd64:

  [..]

  t/04_datemanip.t .. ok
  t/05_datecalc.t ... ok
  t/06_cal.t  ok
  t/07_ncal.t ... ok
  
  #   Failed test '(2010/03 i8n) Spanish Mexico (wb:1) using
  auto-detect'
  #   at /build/libhtml-calendarmonth-perl-1.26/t/testload.pm line 233.
  #  got: 'marzo2010dom.lun.mar.mi.jue.vie.sb.12345678910111213141516171819202122232425262728293031'
  # expected: 'marzo2010lunmarmijueviesbdom12345678910111213141516171819202122232425262728293031'
  
  #   Failed test '(2010/03 i8n) German Germany (wb:2) using
  auto-detect'
  #   at /build/libhtml-calendarmonth-perl-1.26/t/testload.pm line 233.
  #  got: 'Mrz2010MoDiMiDoFrSaSo12345678910111213141516171819202122232425262728293031'
  # expected: 'Mrz2010Mo.Di.Mi.Do.Fr.Sa.So.12345678910111213141516171819202122232425262728293031'
  
  #   Failed test '(2010/03 i8n) Russian Russia (wb:2) using
  auto-detect'
  #   at /build/libhtml-calendarmonth-perl-1.26/t/testload.pm line 233.
  #  got: '201012345678910111213141516171819202122232425262728293031'
  # expected: '201012345678910111213141516171819202122232425262728293031'
  
  #   Failed test '(2010/03 i8n) Zulu South Africa (wb:1) using
  auto-detect'
  #   at /build/libhtml-calendarmonth-perl-1.26/t/testload.pm line 233.
  #  got: 'Mashi2010SonMsoBilThaSinHlaMgq12345678910111213141516171819202122232425262728293031'
  # expected: 'uMashi2010MsoBilThaSinHlaMgqSon12345678910111213141516171819202122232425262728293031'
  # Looks like you failed 4 tests of 8.
  t/20_i8n.t  
  Dubious, test returned 4 (wstat 1024, 0x400)
  Failed 4/8 subtests 
  t/21_narrow.t . ok
  t/author-critic.t . skipped: these tests are for testing by
  the author
  t/release-pod-coverage.t .. skipped: these tests are for release
  candidate testing
  t/release-pod-syntax.t  skipped: these tests are for release
  candidate testing
  
  Test Summary Report
  ---
  t/20_i8n.t  (Wstat: 1024 Tests: 8 Failed: 4)
Failed tests:  3, 5-6, 8
Non-zero exit status: 4
  Files=13, Tests=1096, 19 wallclock secs ( 0.36 usr  0.05 sys + 18.61
  cusr  0.25 csys = 19.27 CPU)
  Result: FAIL
  Failed 1/13 test programs. 4/1096 subtests failed.
  Makefile:876: recipe for target 'test_dynamic' failed
  make[1]: *** [test_dynamic] Error 255
  make[1]: Leaving directory '/build/libhtml-calendarmonth-perl-1.26'
  debian/rules:22: recipe for target 'test-stamp' failed
  make: *** [test-stamp] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/libhtml-calendarmonth-perl_1.26-1.build1.log.gz


Regards,

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


libhtml-calendarmonth-perl.1.26-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libhtml-calendarmonth-perl
Source-Version: 2.04-1

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

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

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

Debian distribution maintenance software
pp.
Don Armstrong  (supplier of updated libhtml-calendarmonth-perl 
package)

(This message was generated automatically at their request; if you

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Laurent Bigonville]

On Thu, 30 Jun 2016 21:37:24 +0200 Eric Valette  
wrote:

> On 30/06/2016 21:32, Felipe Sateler wrote:
> > On 30 June 2016 at 15:20, Eric Valette  wrote:
> >> On 30/06/2016 21:18, Martin Pitt wrote:
> >>>
> >>> Control: reassing -1 libaudit1
> >>> Control: forcemerge 828991 -1
> >>>
> >>> Hello Eric,
> >>
> >>
> >>> This has never been a supported configuration, and just because it
> >>> happend to mostly work once it doesn't mean that it can be guaranteed
> >>> forever, sorry.
> >>
> >>
> >> I have an initrd on this machine so this is something else
> >
> > Your initrd needs to mount /usr. Which one are you using?
> >
>
> initramfs-tools

Is /usr present in the fstab?

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Martin Pitt]

Hello Eric,

Eric Valette [2016-06-30 21:33 +0200]:
> > I have an initrd on this machine so this is something else

OK, I owe you an apology then, sorry. In #771652 you didn't yet, so I
just assumed that was still the case.

> I was lucky to see at the top of the screen something about shared object,
> booted with sysvinit and found it. I suspect the bug is true even with an
> initrd this time. Maybe analysing the initrd could tell us.

That's strange indeed. Mind booting with "debug" and attaching
/run/initramfs/initramfs.debug?

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Processed: reassign 829127 to libaudit1, forcibly merging 828991 829127

[Debian Bug Tracking System]

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

> reassign 829127 libaudit1
Bug #829127 [systemd] systemd: Please make sure /lib/systemd/systemd is not 
linked with something in /usr
Bug reassigned from package 'systemd' to 'libaudit1'.
No longer marked as found in versions systemd/230-3.
Ignoring request to alter fixed versions of bug #829127 to the same values 
previously set
> forcemerge 828991 829127
Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 
which is installed in /usr
Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
Bug #829127 [libaudit1] systemd: Please make sure /lib/systemd/systemd is not 
linked with something in /usr
Severity set to 'serious' from 'critical'
829127 was not blocked by any bugs.
829127 was not blocking any bugs.
Added blocking bug(s) of 829127: 828992
Added indication that 829127 affects systemd
Marked as found in versions audit/1:2.6.1-1.
Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
Merged 828991 829110 829127
> thanks
Stopping processing here.

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

Processed: affects 828991

[Debian Bug Tracking System]

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

> affects 828991 + systemd
Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 
which is installed in /usr
Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
Added indication that 828991 affects systemd
Added indication that 829110 affects systemd
> thanks
Stopping processing here.

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

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Felipe Sateler]

On 30 June 2016 at 15:20, Eric Valette  wrote:
> On 30/06/2016 21:18, Martin Pitt wrote:
>>
>> Control: reassing -1 libaudit1
>> Control: forcemerge 828991 -1
>>
>> Hello Eric,
>
>
>> This has never been a supported configuration, and just because it
>> happend to mostly work once it doesn't mean that it can be guaranteed
>> forever, sorry.
>
>
> I have an initrd on this machine so this is something else

Your initrd needs to mount /usr. Which one are you using?

-- 

Saludos,
Felipe Sateler

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Eric Valette]

On 30/06/2016 21:20, Eric Valette wrote:

On 30/06/2016 21:18, Martin Pitt wrote:

Control: reassing -1 libaudit1
Control: forcemerge 828991 -1


I martin


I have an initrd on this machine so this is something else


I was lucky to see at the top of the screen something about shared 
object, booted with sysvinit and found it. I suspect the bug is true 
even with an initrd this time. Maybe analysing the initrd could tell us.


menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class 
gnu --class os $menuentry_id_option 
'gnulinux-simple-a1adf4c4-77e8-494b-8ae4-42b695014c2b' {

load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 
--hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 
a1adf4c4-77e8-494b-8ae4-42b695014

c2b
else
  search --no-floppy --fs-uuid --set=root 
a1adf4c4-77e8-494b-8ae4-42b695014c2b

fi
echo'Loading Linux 4.4.14 ...'
linux   /boot/vmlinuz-4.4.14 root=/dev/sda1 ro rootfstype=ext4 
radeon.audio=1 quiet

echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-4.4.14

-- eric

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Eric Valette]

On 30/06/2016 21:18, Martin Pitt wrote:

Control: reassing -1 libaudit1
Control: forcemerge 828991 -1

Hello Eric,



This has never been a supported configuration, and just because it
happend to mostly work once it doesn't mean that it can be guaranteed
forever, sorry.


I have an initrd on this machine so this is something else

-- eric

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Martin Pitt]

Control: reassing -1 libaudit1
Control: forcemerge 828991 -1

Hello Eric,

Eric Valette [2016-06-30 21:05 +0200]:
> Package: systemd
> Version: 230-3
> Severity: critical
> Justification: breaks the whole system
> 
> Today a system using initrd was unbootable after upgrade because of the very
> same problem of /usr/lib library dependency.
> 
> Please make a check afetr building the binary so this is automagically 
> detected!

systemd already grew a check in debian/rules [1], after you previously
filed [2]. But this doesn't help, because this time this:

> valette@tri-yann4:~$ ldd /lib/systemd/systemd
> libcap-ng.so.0 => /usr/lib/x86_64-linux-gnu/libcap-ng.so.0 
> (0x7f962afa4000)

... was not caused by a systemd upload, but by a new audit package.

But really, this is a whack-a-mole game. You keep running an
unsupported configuration, you get to keep both halves. You *must* run
an initrd if you have a separate /usr. At some point we'll get the
/usr merge and this will be the latest point where separate /usr
without initrd will break for good, and even now it can't work
reliably (not just because of linking to pid 1, but also because of
udev rules or early boot scripts calling programs from /usr, etc.).

This has never been a supported configuration, and just because it
happend to mostly work once it doesn't mean that it can be guaranteed
forever, sorry.

Martin


[1] http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=24b267b53
[2] https://bugs.debian.org/771652
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: PGP signature

Processed (with 2 errors): Re: Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Debian Bug Tracking System]

Processing control commands:

> reassing -1 libaudit1
Unknown command or malformed arguments to command.

> forcemerge 828991 -1
Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 
which is installed in /usr
Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
Unable to merge bugs because:
package of #829127 is 'systemd' not 'libaudit1'
Failed to forcibly merge 828991: Did not alter merged bugs.


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

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

[Eric Valette]

Package: systemd
Version: 230-3
Severity: critical
Justification: breaks the whole system

Today a system using initrd was unbootable after upgrade because of the very
same problem of /usr/lib library dependency.

Please make a check afetr building the binary so this is automagically detected!

valette@tri-yann4:~$ ldd /lib/systemd/systemd   

   
linux-vdso.so.1 (0x7ffc639f4000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7f962ccdc000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f962cad6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f962c8cd000)
libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2 
(0x7f962c688000)
libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x7f962c479000)
libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 
(0x7f962c25)
libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x7f962c039000)
libapparmor.so.1 => /lib/x86_64-linux-gnu/libapparmor.so.1 
(0x7f962be28000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7f962bbdd000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f962b9c)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f962b61f000)
/lib64/ld-linux-x86-64.so.2 (0x5612a1c74000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f962b3ae000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f962b1aa000)
libcap-ng.so.0 => /usr/lib/x86_64-linux-gnu/libcap-ng.so.0 
(0x7f962afa4000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7f962ad6)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f962ab5b000)


-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.10.95-3
ii  libaudit1   1:2.6.1-1
ii  libblkid1   2.28-5
ii  libc6   2.23-0experimental4
ii  libcap2 1:2.25-1
ii  libcap2-bin 1:2.25-1
ii  libcryptsetup4  2:1.7.0-2
ii  libgcrypt20 1.7.1-2
ii  libgpg-error0   1.23-1
ii  libkmod222-1.1
ii  liblzma55.1.1alpha+20120614-2.1
ii  libmount1   2.28-5
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.5-3
ii  libsystemd0 230-3
ii  mount   2.28-5
ii  util-linux  2.28-5

Versions of packages systemd recommends:
ii  dbus1.11.2-1
ii  libpam-systemd  230-3

Versions of packages systemd suggests:
ii  policykit-10.113-4
pn  systemd-container  
pn  systemd-ui 

Versions of packages systemd is related to:
ii  udev  230-3

-- no debconf information

Bug#829126: libcap-ng0: /sbin/init now depend on libcap-ng.so.0 which is in /usr

[Eric Valette]

Package: libcap-ng0
Version: 0.7.7-2
Severity: critical
Justification: breaks the whole system

I have a system with /usr and / on dfferent filesystem. Yet as I use an
initrd it should be transparent but is not. Today upgrade ended up
with a crash in /sbin/init as /sbin/init depends on libcap-ng0

Booting with sysvinit option did no gave me a fully aoperationnal system but
enough to fix my system by copying manully to /lib

ldd /sbin/init 
linux-vdso.so.1 (0x7ffe2ffbd000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fa3f846d000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fa3f8267000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fa3f805e000)
libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2 
(0x7fa3f7e19000)
libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x7fa3f7c0a000)
libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 
(0x7fa3f79e1000)
libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x7fa3f77ca000)
libapparmor.so.1 => /lib/x86_64-linux-gnu/libapparmor.so.1 
(0x7fa3f75b9000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7fa3f736e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa3f7151000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3f6db)
/lib64/ld-linux-x86-64.so.2 (0x55bf8ba48000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fa3f6b3f000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa3f693b000)
libcap-ng.so.0 => /usr/lib/x86_64-linux-gnu/libcap-ng.so.0 
(0x7fa3f6735000) <===
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7fa3f64f1000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fa3f62ec000)


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

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

Versions of packages libcap-ng0 depends on:
ii  libc6  2.23-0experimental3

libcap-ng0 recommends no packages.

libcap-ng0 suggests no packages.

-- no debconf information

Processed: reassign 811920 to src:ompl, fixed 811920 in 1.1.0+ds1-1

[Debian Bug Tracking System]

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

> # get rid of some weird fixed versions
> reassign 811920 src:ompl 1.0.0+ds2-1
Bug #811920 {Done: Leopold Palomo-Avellaneda } [ompl] ompl: 
FTBFS with GCC 6: use of deleted function
Bug reassigned from package 'ompl' to 'src:ompl'.
No longer marked as found in versions 1.0.0+ds2-1.
No longer marked as fixed in versions new, package', 1.0.0+ds2-1, 1.1.0+ds1-1, 
'#, of, the, version, in, and Fixed.
Bug #811920 {Done: Leopold Palomo-Avellaneda } [src:ompl] 
ompl: FTBFS with GCC 6: use of deleted function
Marked as found in versions ompl/1.0.0+ds2-1.
> fixed 811920 1.1.0+ds1-1
Bug #811920 {Done: Leopold Palomo-Avellaneda } [src:ompl] 
ompl: FTBFS with GCC 6: use of deleted function
Marked as fixed in versions ompl/1.1.0+ds1-1.
> thanks
Stopping processing here.

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

Processed: reassign 811920 to ompl, fixed 811920 in 1.1.0+ds1-1

[Debian Bug Tracking System]

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

> reassign 811920 ompl 1.0.0+ds2-1
Bug #811920 {Done: Leopold Palomo-Avellaneda } [ompl] ompl: 
FTBFS with GCC 6: use of deleted function
Ignoring request to reassign bug #811920 to the same package
Bug #811920 {Done: Leopold Palomo-Avellaneda } [ompl] ompl: 
FTBFS with GCC 6: use of deleted function
There is no source info for the package 'ompl' at version '1.0.0+ds2-1' with 
architecture ''
Unable to make a source version for version '1.0.0+ds2-1'
Ignoring request to alter found versions of bug #811920 to the same values 
previously set
> fixed 811920 1.1.0+ds1-1
Bug #811920 {Done: Leopold Palomo-Avellaneda } [ompl] ompl: 
FTBFS with GCC 6: use of deleted function
There is no source info for the package 'ompl' at version '1.1.0+ds1-1' with 
architecture ''
Unable to make a source version for version '1.1.0+ds1-1'
Marked as fixed in versions 1.1.0+ds1-1.
> thanks
Stopping processing here.

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

Processed: tagging 811591, tagging 811642, tagging 811659, tagging 811733, tagging 811863, tagging 811868 ...

[Debian Bug Tracking System]

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

> tags 811591 + sid stretch
Bug #811591 [ifhp] FTBFS with GCC 6: statement indented as if it were guarded by
Added tag(s) sid and stretch.
> tags 811642 + sid stretch
Bug #811642 [fracplanet] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811659 + sid stretch
Bug #811659 [wvstreams] FTBFS with GCC 6: cannot convert x to y
Added tag(s) stretch and sid.
> tags 811733 + sid stretch
Bug #811733 [cdrdao] cdrdao: FTBFS with GCC 6: narrowing conversion
Added tag(s) sid and stretch.
> tags 811863 + sid stretch
Bug #811863 [tagcoll2] tagcoll2: FTBFS with GCC 6: no matching function for 
call to
Added tag(s) sid and stretch.
> tags 811868 + sid stretch
Bug #811868 [linuxdcpp] linuxdcpp: FTBFS with GCC 6: no matching function for 
call to
Added tag(s) stretch and sid.
> tags 811894 + sid stretch
Bug #811894 [tvtime] tvtime: FTBFS with GCC 6: inconsistent user-defined 
literal suffixes
Added tag(s) sid and stretch.
> tags 811899 + sid stretch
Bug #811899 [gnuift] gnuift: FTBFS with GCC 6: declared in this scope
Added tag(s) stretch and sid.
> tags 812053 + sid stretch
Bug #812053 [galib] galib: FTBFS with GCC 6
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811591
811642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811642
811659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811659
811733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811733
811863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811863
811868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811868
811894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811894
811899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811899
812053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#811750: marked as done (FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 18:27:37 +
with message-id 
and subject line Bug#811750: fixed in rsbackup 3.1-2
has caused the Debian Bug report #811750,
regarding 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.)


-- 
811750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: re
Version: 0.1-6
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
...
> make[1]: Entering directory '/<>'
> g++ -fsigned-char -Wno-write-strings -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wl,-z,relro src/re_cmd.c src/ru32call.c src/ru32cp.c 
> src/ru32var.c src/ru32lat.c  src/ru32fi.c src/ru32au.c src/ru32mau.c 
> src/ru32un.c -ore
> src/ru32cp.c:92:1: error: narrowing conversion of '136' from 'int' to 'char' 
> inside { } [-Wnarrowing]
>  };
>  ^
> 
> src/ru32cp.c:92:1: error: narrowing conversion of '152' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '160' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '164' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '144' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '166' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '167' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '169' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '171' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '172' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '173' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '174' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '176' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '177' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '145' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '181' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '182' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '183' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '187' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> debian/rules:5: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: rsbackup
Source-Version: 3.1-2

We believe that the bug you reported is fixed in the latest version of
rsbackup, 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.
Matthew Vernon  (supplier of updated rsbackup 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: Thu, 30 Jun 2016 16:37:44 +0100
Source: rsbackup
Binary: rsbackup
Architecture: i386 source
Version: 3.1-2
Distribution: unstable

Bug#829124: viva build-depends on libpajeutils-dev which is no longer built

[peter green]

Package: viva
Version: 1.1+git20150820.1a3d1f680f-1
Severity: serious

Viva build-depends on libpajeutils-dev which is no longer built by 
source package pajeng.

Bug#817778: info-beamer: nmu 1.0~pre3+dfsg-0.1

[Noël Köthe]

Hello James,

Am Mittwoch, den 29.06.2016, 02:14 +0100 schrieb James Cowgill:

> I have uploaded an NMU to DELAYED/10 to fix the following bugs.
> Please tell me if I should cancel / delay it.
>  #817778 silkscreen font is not DFSG compliant
>  #826288 info-beamer: please use glfw3

Thanks for your work! You can upload it again without delay if you
like.

Regards

Noel

Bug#817372: bandwidthcalc: Removal of debhelper compat 4

[Christoph Goehre]

Hi Niels,

On Wed, Mar 09, 2016 at 08:46:10PM +0100, ni...@thykier.net wrote:
> The package bandwidthcalc uses debhelper with a compat level of 4,
> which is deprecated and scheduled for removal.

autoremove of bandwidthcalc is fine. Since I ask for remove before the
jessie release (#781926), I forgot to remove bandwidthcalc finally from
testing and unstable.

Cheers,
Christoph

Processed: Fix blocked by sphinx bug

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 829118
Bug #828980 [src:pyx3] pyx3: FTBFS in testing (LaTeX Error: File `iftex.sty' 
not found)
828980 was not blocked by any bugs.
828980 was not blocking any bugs.
Added blocking bug(s) of 828980: 829118

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

Processed: Fix blocked by sphinx bug

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 829118
Bug #828981 [src:pyx] pyx: FTBFS in testing (LaTeX Error: File `iftex.sty' not 
found)
828981 was not blocked by any bugs.
828981 was not blocking any bugs.
Added blocking bug(s) of 828981: 829118

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

Bug#829052: libneo4j-client8-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/neo4j-client.h

[Andreas Beckmann]

On 2016-06-30 08:09, Chris Leishman wrote:
> Hi Andreas,
> 
> If you don't mind, I was hoping for a little direction in resolving this.

Let's discuss this within the bug report ... even if it does not fit
perfectly.

> It seems I've got a mistake in the packaging, whereby the -dev package for
> the library contains the soname - i.e. libneo4j-client8-dev. I did this
> because it contains the symlink
> ./usr/lib/x86_64-linux-gnu/libneo4j-client.so -> libneo4j-client.so.8.0.0.
> 
> But I believe that was a mistake, and the package should simply be
> libneo4j-client-dev.

That's the reasonable approach (unless you have good reasons to need two
versions of the -dev package, but then you usually need two source
packages, too).

> What's the best way to remove both libneo4j-client7-dev and
> libneo4j-client8-dev, and replace with a package libneo4j-client-dev? I can

Are there any packages with Build-Depends: libneo4j-client[78]-dev?
Do they have versioned dependencies?
Or do all use the virtual package libneo4j-client-dev?

> upload a new package with the new name, but I'm unclear how to force
> removal of the others from the distribution. Will using 'Provides' +
> 'Conflicts' + 'Replaces', as per policy 7.6.2, achieve this? Do I make it
> '(Provides|Conflicts|Replaces): libneo4j-client7-dev libneo4j-client8-dev`?

We currently have:

Package: libneo4j-client7-dev
Source: libneo4j-client
Version: 0.9.2-1
Provides: libneo4j-client-dev
Depends: libneo4j-client7 (= 0.9.2-1)

Package: libneo4j-client8-dev
Source: libneo4j-client
Version: 1.0.0-1
Provides: libneo4j-client-dev
Depends: libneo4j-client8 (= 1.0.0-1)

If you introduce

Package: libneo4j-client-dev
Depends: libneo4j-client8 (= ${binary:Version})
Breaks: libneo4j-client7-dev, libneo4j-client8-dev
Replaces: libneo4j-client7-dev, libneo4j-client8-dev
Provides: libneo4j-client7-dev, libneo4j-client8-dev

that should work quite well. You only need the Provides if there are any
reverse depends/build-depends on the versioned package name.
Breaks+Replaces can be unversioned in this case. Or use a version
constraint of (<< 1.0.0-2~) (assuming the new package will be uploaded
in rev -2).

The old -dev packages will be no longer installable since they have a
strict dependency on the library package, so they will get removed
automatically on upgrades. There won't be an automatic upgrade path that
installs the unversioned -dev package if the versioned -dev package was
installed, but that is probably no needed (v7 was never in stable, only
in testing, v8 won't go to testing).


Andreas

Bug#812281: marked as done (oce: FTBFS with GCC 6: test suite failures)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 19:05:48 +0200
with message-id 

Processed: Not relevant in a newer oce-version

[Debian Bug Tracking System]

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

> fixed 812281 0.17.2-1
Bug #812281 [oce] oce: FTBFS with GCC 6: test suite failures
There is no source info for the package 'oce' at version '0.17.2-1' with 
architecture ''
Unable to make a source version for version '0.17.2-1'
Marked as fixed in versions 0.17.2-1.
> thanks
Stopping processing here.

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

Bug#828963: marked as done (squirrel3: FTBFS: Makefile:66: recipe for target 'stdlib.pdf' failed)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:48:28 +
with message-id 
and subject line Bug#828963: fixed in squirrel3 3.1-3
has caused the Debian Bug report #828963,
regarding squirrel3: FTBFS: Makefile:66: recipe for target 'stdlib.pdf' 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.)


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

squirrel3 fails to build from source in unstable/amd64:

  [..]

  dh clean
 dh_testdir
 dh_auto_clean
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_update_autotools_config
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1'
  dh_auto_configure --buildsystem=cmake -- \
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu \
-DINSTALL_INC_DIR=include/squirrel3 \
-DDISABLE_STATIC="" -DLONG_OUTPUT_NAMES=""
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DINSTALL_LIB_DIR=lib/x86_64-linux-gnu 
-DINSTALL_INC_DIR=include/squirrel3 -DDISABLE_STATIC= -DLONG_OUTPUT_NAMES=
  -- The C compiler identification is GNU 5.4.0
  -- The CXX compiler identification is GNU 5.4.0
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Configuring done
  -- Generating done
  CMake Warning:
Manually-specified variables were not used by the project:
  
  CMAKE_INSTALL_LOCALSTATEDIR
  CMAKE_INSTALL_SYSCONFDIR
  DISABLE_STATIC
  LONG_OUTPUT_NAMES
  
  
  -- Build files have been written to: 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1'
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  /usr/bin/cmake 
-H/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1 
-B/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
 --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/CMakeFiles
 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
  make -f CMakeFiles/Makefile2 all
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  make -f squirrel/CMakeFiles/squirrel.dir/build.make 
squirrel/CMakeFiles/squirrel.dir/depend
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/squirrel 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/squirrel
 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/squirrel/CMakeFiles/squirrel.dir/DependInfo.cmake
 --color=
  Scanning dependencies of target squirrel
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  make -f squirrel/CMakeFiles/squirrel.dir/build.make 
squirrel/CMakeFiles/squirrel.dir/build
  make[3]: 

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

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:48:22 +
with message-id 
and subject line Bug#829106: fixed in sisu-inject 0.3.2-2
has caused the Debian Bug report #829106,
regarding sisu-inject: FTBFS: the artifact javax.servlet:servlet-api:jar:debian 
has not been downloaded
to be marked as done.

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

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


-- 
829106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sisu-inject
Version: 0.3.2-1
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Sisu Inject  SUCCESS [  0.002 s]
[INFO] org.eclipse.sisu.inject  FAILURE [  0.149 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.274 s
[INFO] Finished at: 2016-06-28T00:11:06+00:00
[INFO] Final Memory: 7M/150M
[INFO] 
[ERROR] Failed to execute goal on project org.eclipse.sisu.inject:
Could not resolve dependencies for project
org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.3.2: Cannot access
central (https://repo.maven.apache.org/maven2) in offline mode and the
artifact javax.servlet:servlet-api:jar:debian has not been downloaded
from it before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :org.eclipse.sisu.inject
/usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: sisu-inject
Source-Version: 0.3.2-2

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated sisu-inject 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: Thu, 30 Jun 2016 17:59:37 +0200
Source: sisu-inject
Binary: libsisu-inject-java
Architecture: source all
Version: 0.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libsisu-inject-java - Dependency Injection container for Java
Closes: 829106
Changes:
 sisu-inject (0.3.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Completed the transition to the Servlet API 3.1 (Closes: #829106)
   * Build with the DH sequencer instead of CDBS
   * Tightened the dependency on libosgi-core-java
   * Standards-Version updated to 3.9.8 (no changes)
   * Use a secure Vcs-Git URL
Checksums-Sha1:
 cfe68361127bdbfec0cf23bf020b493771dd912c 2170 sisu-inject_0.3.2-2.dsc
 2aff42af8abc3972fb136b31e9b801bd473a147a 8676 sisu-inject_0.3.2-2.debian.tar.xz
 2cff07e1093c263d19b57c85ffe10cd5b3a08214 345972 
libsisu-inject-java_0.3.2-2_all.deb
Checksums-Sha256:
 f746aa9053ebe28fe4045bb21f755d29a7295d7ed25e5d480b978ed5704570e2 2170 
sisu-inject_0.3.2-2.dsc
 4f900db58b0759efe5b2c4afc31ddb452857df39c6c369cf987a896ab53cc3f1 8676 
sisu-inject_0.3.2-2.debian.tar.xz
 0a06ce6c6ca72031a451522d7f231c9794734367607a677f86f7c396fb7bf058 345972 
libsisu-inject-java_0.3.2-2_all.deb
Files:
 24aea596e3428c587bc1729d6663734d 2170 java optional sisu-inject_0.3.2-2.dsc
 c5b7fe266d5b13390c7b9fad75a501dc 8676 java optional 

Bug#811873: marked as done (scidavis: FTBFS with GCC 6: no matching function for call to)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:48:10 +
with message-id 
and subject line Bug#811873: fixed in scidavis 1.D9-2
has caused the Debian Bug report #811873,
regarding scidavis: FTBFS with GCC 6: no matching function for call to
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.)


-- 
811873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scidavis
Version: 1.D9-1
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
...
> g++ -c -m64 -pipe -O2 -D_REENTRANT -Wall -W -fPIC -DSCRIPTING_CONSOLE 
> -DSCRIPTING_DIALOG -DQT_PLUGIN -DTS_PATH=\"/usr/share/scidavis/translations\" 
> -DDOC_PATH=\"/usr/share/doc/scidavis\" 
> -DPLUGIN_PATH=\"/usr/lib/scidavis/plugins\" -DLEGACY_CODE_0_2_x 
> -DSCRIPTING_MUPARSER -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_QT3SUPPORT_LIB 
> -DQT3_SUPPORT -DQT_XML_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml 
> -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtSvg -I/usr/include/qt4 
> -I/sbuild-nonexistent/usr/include -I/usr/include/qwt-qt4 
> -I/usr/include/qwtplot3d -I/usr/include/muParser -I../scidavis -Isrc 
> -Isrc/future -I/usr/X11R6/include -I../tmp/scidavis -I. -o 
> ../tmp/scidavis/FitDialog.o src/FitDialog.cpp
> In file included from src/Graph.h:47:0,
>  from src/FitDialog.h:32,
>  from src/FitDialog.cpp:29:
> src/future/core/column/Column.h:87:36: warning: 'template class 
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>Column(const QString& name, std::auto_ptr data,
> ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from src/future/core/column/Column.h:38,
>  from src/Graph.h:47,
>  from src/FitDialog.h:32,
>  from src/FitDialog.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In file included from src/Graph.h:47:0,
>  from src/FitDialog.h:32,
>  from src/FitDialog.cpp:29:
> src/future/core/column/Column.h:324:25: warning: 'template class 
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>void initPrivate(std::auto_ptr, IntervalAttribute);
>  ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from src/future/core/column/Column.h:38,
>  from src/Graph.h:47,
>  from src/FitDialog.h:32,
>  from src/FitDialog.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In file included from src/Graph.h:47:0,
>  from src/FitDialog.h:32,
>  from src/FitDialog.cpp:29:
> src/future/core/column/Column.h: In constructor 'Column::Column(const 
> QString&, const D&, IntervalAttribute)':
> src/future/core/column/Column.h:82:22: warning: 'template class 
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>  initPrivate(std::auto_ptr(new D(data)), validity);
>   ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from src/future/core/column/Column.h:38,
>  from src/Graph.h:47,
>  from src/FitDialog.h:32,
>  from src/FitDialog.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> src/FitDialog.cpp: In member function 'void FitDialog::showFitPage()':
> src/FitDialog.cpp:658:41: error: no matching function for call to 
> 'QTableWidgetItem::setFlags(bool)'
>  it->setFlags(!Qt::ItemIsEditable);
> 

Bug#829102: marked as done (modello: FTBFS: the artifact org.jdom:jdom:jar:debian has not been downloaded)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:45:47 +
with message-id 
and subject line Bug#829102: fixed in modello 1.8.3-3
has caused the Debian Bug report #829102,
regarding modello: FTBFS: the artifact org.jdom:jdom:jar:debian has not been 
downloaded
to be marked as done.

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

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


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

>From my pbuilder build log:

...
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Modello  SUCCESS [  0.535 s]
[INFO] Modello Core ... SUCCESS [  3.681 s]
[INFO] Modello Plugins  SUCCESS [  0.027 s]
[INFO] Modello Java Plugin  SUCCESS [  2.905 s]
[INFO] Modello XML Plugin . SUCCESS [  1.352 s]
[INFO] Modello StAX Plugin  SUCCESS [  1.497 s]
[INFO] Modello Model Version Converter Plugin . SUCCESS [  1.080 s]
[INFO] Modello XSD Plugin . SUCCESS [  1.288 s]
[INFO] Modello XDOC Plugin  SUCCESS [  1.118 s]
[INFO] Modello XPP3 Plugin  SUCCESS [  1.151 s]
[INFO] Modello Dom4J Plugin ... SUCCESS [  1.120 s]
[INFO] Modello JDOM Plugin  FAILURE [  0.011 s]
[INFO] Modello SAX Plugin . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 16.149 s
[INFO] Finished at: 2016-06-28T19:13:19+00:00
[INFO] Final Memory: 23M/278M
[INFO] 
[ERROR] Failed to execute goal on project modello-plugin-jdom: Could
not resolve dependencies for project
org.codehaus.modello:modello-plugin-jdom:jar:1.8.3: Cannot access
central (https://repo.maven.apache.org/maven2) in offline mode and the
artifact org.jdom:jdom:jar:debian has not been downloaded from it
before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :modello-plugin-jdom
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/build/modello-1.8.3
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/modello-1.8.3/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml
-Ddebian.dir=/build/modello-1.8.3/debian
-Dmaven.repo.local=/build/modello-1.8.3/debian/maven-repo package
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true
-Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: modello
Source-Version: 1.8.3-3

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated modello 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: Thu, 30 

Bug#811870: marked as done (libmems: FTBFS with GCC 6: no matching function for call to)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:44:34 +
with message-id 
and subject line Bug#811870: fixed in libmems 1.6.0+4725-3
has caused the Debian Bug report #811870,
regarding libmems: FTBFS with GCC 6: no matching function for call to
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.)


-- 
811870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmems
Version: 1.6.0+4725-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
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
>   -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -funroll-loops -fomit-frame-pointer 
> -ftree-vectorize  -I/usr/include/libGenome-1.3 -I/usr/include/libMUSCLE-3.7   
>-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> ProgressiveAligner.lo ProgressiveAligner.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O2 -funroll-loops -fomit-frame-pointer -ftree-vectorize 
> -I/usr/include/libGenome-1.3 -I/usr/include/libMUSCLE-3.7 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> ProgressiveAligner.cpp  -fPIC -DPIC -o .libs/ProgressiveAligner.o
> In file included from /usr/include/c++/6/ext/hash_map:60:0,
>  from ../libMems/HomologyHMM/dptables.h:43,
>  from ../libMems/HomologyHMM/homology.h:27,
>  from ../libMems/Islands.h:25,
>  from ../libMems/ProgressiveAligner.h:21,
>  from ProgressiveAligner.cpp:14:
> /usr/include/c++/6/backward/backward_warning.h:32:2: warning: #warning This 
> file includes at least one deprecated or antiquated header which may be 
> removed without further notice at a future date. Please use a non-deprecated 
> interface with equivalent functionality instead. For a listing of replacement 
> headers and interfaces, consult the file backward_warning.h. To disable this 
> warning use -Wno-deprecated. [-Wcpp]
>  #warning \
>   ^~~
> 
> ProgressiveAligner.cpp: In member function 'void 
> mems::ProgressiveAligner::constructLcbTrackingMatches(node_id_t, 
> std::vector&, 
> std::vector >&)':
> ProgressiveAligner.cpp:1602:74: error: no matching function for call to 
> 'std::vector*, 
> std::vector >*, mems::AbstractMatch*> 
> >::push_back(std::tuple  std::allocator, std::allocator > > >*, 
> std::vector >, std::allocator > >*, mems::AbstractMatch*>)'
>cga_list.push_back(make_tuple(c.Copy(), [mI], ancestral_matches[mI]));
>   ^
> 
> In file included from /usr/include/c++/6/vector:64:0,
>  from ../libMems/AbstractMatch.h:17,
>  from ../libMems/SparseAbstractMatch.h:18,
>  from ../libMems/Interval.h:18,
>  from ../libMems/SuperInterval.h:8,
>  from ../libMems/ProgressiveAligner.h:16,
>  from ProgressiveAligner.cpp:14:
> /usr/include/c++/6/bits/stl_vector.h:914:7: note: candidate: void 
> std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = 
> boost::tuples::tuple*, 
> std::vector >*, mems::AbstractMatch*>; _Alloc = 
> std::allocator*, 
> std::vector >*, mems::AbstractMatch*> >; 
> std::vector<_Tp, _Alloc>::value_type = 
> boost::tuples::tuple*, 
> std::vector >*, mems::AbstractMatch*>]
>push_back(const value_type& __x)
>^
> 
> /usr/include/c++/6/bits/stl_vector.h:914:7: note:   no known conversion for 

Bug#816571: marked as done (libwx-scintilla-perl: FTBFS with GCC 6: call overloaded is ambiguous)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:44:56 +
with message-id 
and subject line Bug#816571: fixed in libwx-scintilla-perl 0.39-3
has caused the Debian Bug report #816571,
regarding libwx-scintilla-perl: FTBFS with GCC 6: call overloaded 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.)


-- 
816571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwx-scintilla-perl
Version: 0.39-2
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

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

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.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -c -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 
> -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ 
> -pthread -pthread  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__  -DWXBUILDING -DSCI_LEXER 
> -DLINK_LEXERS -DWXUSINGDLL -DWXMAKINGDLL_STC -D__WX__ -c -fPIC -o 
> wx-scintilla/src/scintilla/src/scintilladll_Editor.o -O2 -Wall 
> -Wno-missing-braces -Wno-char-subscripts 
> -MTwx-scintilla/src/scintilla/src/scintilladll_Editor.o 
> -MFwx-scintilla/src/scintilla/src/scintilladll_Editor.o.d -MD -MP 
> -Iwx-scintilla/include -Iwx-scintilla/src/scintilla/include 
> -Iwx-scintilla/src/scintilla/src -Iwx-scintilla/src 
> -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
>  wx-scintilla/src/scintilla/src/Editor.cxx
> wx-scintilla/src/scintilla/src/Editor.cxx: In member function 'long int 
> Editor::FindText(uptr_t, sptr_t)':
> wx-scintilla/src/scintilla/src/Editor.cxx:5748:7: warning: 'template 
> class std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>   std::auto_ptr pcf(CaseFolderForEncoding());
>^~~~
> In file included from /usr/include/c++/6/memory:81:0,
>  from wx-scintilla/src/scintilla/src/Editor.cxx:18:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> wx-scintilla/src/scintilla/src/Editor.cxx: In member function 'long int 
> Editor::SearchText(unsigned int, uptr_t, sptr_t)':
> wx-scintilla/src/scintilla/src/Editor.cxx:5793:7: warning: 'template 
> class std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>   std::auto_ptr pcf(CaseFolderForEncoding());
>^~~~
> In file included from /usr/include/c++/6/memory:81:0,
>  from wx-scintilla/src/scintilla/src/Editor.cxx:18:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> wx-scintilla/src/scintilla/src/Editor.cxx: In member function 'long int 
> Editor::SearchInTarget(const char*, int)':
> wx-scintilla/src/scintilla/src/Editor.cxx:5844:7: warning: 'template 
> class std::auto_ptr' is deprecated [-Wdeprecated-declarations]
>   std::auto_ptr pcf(CaseFolderForEncoding());
>^~~~
> In file included from /usr/include/c++/6/memory:81:0,
>  from wx-scintilla/src/scintilla/src/Editor.cxx:18:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> wx-scintilla/src/scintilla/src/Editor.cxx: In function 'bool Close(Point, 
> Point)':
> wx-scintilla/src/scintilla/src/Editor.cxx:5871:23: error: call of overloaded 
> 'abs(XYPOSITION)' is ambiguous
>   if (abs(pt1.x - pt2.x) > 3)
>^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/stdlib.h:36,
>  from wx-scintilla/src/scintilla/src/Editor.cxx:8:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/stdlib.h:36:0,
>  from wx-scintilla/src/scintilla/src/Editor.cxx:8:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> 

Bug#828107: marked as done (FTBFS on armel (egr_bound isn't zero))

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:36:06 +
with message-id 
and subject line Bug#828107: fixed in eclib 20160206-2
has caused the Debian Bug report #828107,
regarding FTBFS on armel (egr_bound isn't zero)
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.)


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

Package: eclib
Version: 20160206-1
Severity: serious

One of the checks breaks on armel :

https://buildd.debian.org/status/fetch.php?pkg=eclib=armel=20160206-1=1460835373

I have been unable to reproduce it on the armhf box I have though.

Snark on #debian-science
--- End Message ---
--- Begin Message ---
Source: eclib
Source-Version: 20160206-2

We believe that the bug you reported is fixed in the latest version of
eclib, 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.
Julien Puydt  (supplier of updated eclib 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: Thu, 30 Jun 2016 15:25:35 +0100
Source: eclib
Binary: libec2 libec-dev eclib-tools
Architecture: source amd64
Version: 20160206-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Julien Puydt 
Description:
 eclib-tools - Programs for modular symbols and elliptic curves over Q
 libec-dev  - Library for modular symbols and elliptic curves over Q (developme
 libec2 - Library for modular symbols and elliptic curves over Q
Closes: 828107
Changes:
 eclib (20160206-2) unstable; urgency=medium
 .
   * Added the egr_bound_small_to_zero patch so tests don't
 fail on numerical noise. (Closes: #828107)
   * Bumped standards version to 3.9.8.
Checksums-Sha1:
 be44775695be44a46f0fe0fa5b587b346c9c95dc 2095 eclib_20160206-2.dsc
 b6575ad72609f05420de3aa788c87ec8d5549116 3984 eclib_20160206-2.debian.tar.xz
 a730f4d8d46f9d7c987e5f747fa5be5eb6cd954b 66476 
eclib-tools-dbgsym_20160206-2_amd64.deb
 635cf5180c003bcba9391e3bda24c5a60750b836 18472 eclib-tools_20160206-2_amd64.deb
 4dcda9c8f7e54d1c4cacc8e962a0ae47c80d20eb 72712 libec-dev_20160206-2_amd64.deb
 5b9a3f5a3c44df0981c512598589ca8b58c568a0 7709074 
libec2-dbgsym_20160206-2_amd64.deb
 0c440b8af72cf5de80e7f5875a1fedcc7410beb1 1023212 libec2_20160206-2_amd64.deb
Checksums-Sha256:
 8146ab8dd9bfecad0e8cb0d48c1f0f367f8b75559ea382f0ad34df36d6236209 2095 
eclib_20160206-2.dsc
 16f47f90be25bcf5b8262f427d8dc34d7306deecfc9ea6063177bab79ceb6301 3984 
eclib_20160206-2.debian.tar.xz
 893d7ef045b3d38ce8e72ef7a51faee3ce7a37e45681fc63b4175334ba8cbde1 66476 
eclib-tools-dbgsym_20160206-2_amd64.deb
 c1b06b02cb7c17482c00dcb7f9b91659e27612005632646713ce8331ef2a36f9 18472 
eclib-tools_20160206-2_amd64.deb
 64f91d97789906aecd70ee7d353eee42be491b002628444f1e679e5661dee024 72712 
libec-dev_20160206-2_amd64.deb
 22bface53d1f678e4595b21dad673db141db795df8563ddeae54acbe4f24e8da 7709074 
libec2-dbgsym_20160206-2_amd64.deb
 cef5cb8732174b94807aed8dd13b0705c9f417b792082b8051a48467491b0474 1023212 
libec2_20160206-2_amd64.deb
Files:
 9f9b00448fb62b927a23f4e88b5b9d76 2095 math optional eclib_20160206-2.dsc
 3e6ea16c99c9ce7ab792bc1205b446a2 3984 math optional 
eclib_20160206-2.debian.tar.xz
 fe1b811c883056e213288a02ca3c3be5 66476 debug extra 
eclib-tools-dbgsym_20160206-2_amd64.deb
 e717a3e6b8e5958359fa319e1ec89de5 18472 math optional 
eclib-tools_20160206-2_amd64.deb
 3ba57b2a93061ac46dc0f7d5f08cc74b 72712 libdevel optional 
libec-dev_20160206-2_amd64.deb
 2ee4274333bcfb8077d5ab886b716069 7709074 debug extra 
libec2-dbgsym_20160206-2_amd64.deb
 de943f4d9849fb435b429679992ff32a 1023212 libs optional 
libec2_20160206-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdS3vAAoJEIyCFp2Ozs0qg2oP/jhUqjUj5cHIoRn8iPNTBIEL
CUQScO4vFNsLorqQidsJJ+8QJ1gTR4UtVaI1Il3sUC87PLaryhLIJfoC5Ic6blv7
a0Frl/Hvco8IeNwwsWojcLuM3xIwP9Cx1rpvXP40/cZ68ag4snXrKt3gTaQURu1l

Bug#822711: marked as done (chromium-bsu: FTBFS with GCC 6: call of overloaded 'abs(float&)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 16:35:50 +
with message-id 
and subject line Bug#822711: fixed in chromium-bsu 0.9.16-1
has caused the Debian Bug report #822711,
regarding chromium-bsu: FTBFS with GCC 6: call of overloaded 'abs(float&)' 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.)


-- 
822711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium-bsu
Version: 0.9.15.1-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but will probably come out this week.

You can find GCC 6 in unstable (gcc-6).  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.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
>   
> MainSDL_Event.cpp: In member function 'void MainSDL::keyMove()':
> MainSDL_Event.cpp:420:88: error: call of overloaded 'abs(float&)' is ambiguous

^^

>if( keystate[SDLK_LEFT]  || keystate[SDLK_KP4] ) key_speed_x -= 2.0 + 
> abs(key_speed_x)*0.4;
>   
>   ^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/stdlib.h:36,
>  from /usr/include/SDL/SDL_stdinc.h:40,
>  from /usr/include/SDL/SDL_main.h:26,
>  from /usr/include/SDL/SDL.h:30,
>  from MainSDL.h:12,
>  from MainSDL_Event.cpp:15:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/stdlib.h:36:0,
>  from /usr/include/SDL/SDL_stdinc.h:40,
>  from /usr/include/SDL/SDL_main.h:26,
>  from /usr/include/SDL/SDL.h:30,
>  from MainSDL.h:12,
>  from MainSDL_Event.cpp:15:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int 
> std::abs(long long int)
>abs(long long __x) { return __builtin_llabs (__x); }
>^~~
> /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
>abs(long __i) { return __builtin_labs(__i); }
>^~~
> MainSDL_Event.cpp:421:88: error: call of overloaded 'abs(float&)' is ambiguous
>if( keystate[SDLK_RIGHT] || keystate[SDLK_KP6] ) key_speed_x += 2.0 + 
> abs(key_speed_x)*0.4;
>   
>   ^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/stdlib.h:36,
>  from /usr/include/SDL/SDL_stdinc.h:40,
>  from /usr/include/SDL/SDL_main.h:26,
>  from /usr/include/SDL/SDL.h:30,
>  from MainSDL.h:12,
>  from MainSDL_Event.cpp:15:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/stdlib.h:36:0,
>  from /usr/include/SDL/SDL_stdinc.h:40,
>  from /usr/include/SDL/SDL_main.h:26,
>  from /usr/include/SDL/SDL.h:30,
>  from MainSDL.h:12,
>  from MainSDL_Event.cpp:15:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int 
> std::abs(long long int)
>abs(long long __x) { return __builtin_llabs (__x); }
>^~~
> /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
>abs(long __i) { return __builtin_labs(__i); }
>^~~
> MainSDL_Event.cpp:422:88: error: call of overloaded 'abs(float&)' is ambiguous
>if( keystate[SDLK_UP]|| keystate[SDLK_KP8] ) key_speed_y -= 2.0 + 
> abs(key_speed_y)*0.4;
>   
>   ^
> In file included 

Bug#829110: systemd: FTBFS: FAIL: test-process-util [..] test-calendarspec

[Martin Pitt]

Control: reassign -1 libaudit1
Control: forcemerge 828991 -1

Hello Chris,

Chris Lamb [2016-06-30 16:53 +0100]:
> systemd fails to build from source in unstable/amd64:

This is known, due to yesterday's libaudit. Merging/linking bugs.

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: PGP signature

Processed: Re: Bug#829110: systemd: FTBFS: FAIL: test-process-util [..] test-calendarspec

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libaudit1
Bug #829110 [src:systemd] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
Bug reassigned from package 'src:systemd' to 'libaudit1'.
No longer marked as found in versions systemd/230-4.
Ignoring request to alter fixed versions of bug #829110 to the same values 
previously set
> forcemerge 828991 -1
Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 
which is installed in /usr
Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] 
test-calendarspec
829110 was not blocked by any bugs.
829110 was not blocking any bugs.
Added blocking bug(s) of 829110: 828992
Marked as found in versions audit/1:2.6.1-1.
Merged 828991 829110

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

Bug#811606: FTBFS with GCC 6: multiple errors

[Apollon Oikonomopoulos]

Hi zigo,

On 14:13 Thu 30 Jun , Thomas Goirand wrote:
> Hi,
> 
> I've been looking into this problem, and the following has to bee added
> to the SConstruct file (around line 720) to allow mongodb to build:
> 
> -Wdeprecated-declarations
> -Wno-error=misleading-indentation
> -Wno-error=nonnull-compare
> -Wno-error=literal-suffix
> 
> But that's unfortunately not enough. At some point, -fpermissive has to
> be added, but that also is turned into errors. Adding -fpermissive and
> removing -Wall made the bad source code build, but I stopped my
> investigations there.

I think MongoDB 2.4 in unstable is already dead enough[1] that we should 
drop it before it gets a chance to build against GCC 6 in a couple of 
months. The attached patch fixes the FTBFS for the 2.6 package in 
experimental by disabling the newly-introduced warnings and patching 
(some) C++11 compatibility, but then again 2.6 will also be EOL by 
October[1].

Note that most (if not all) of these warnings seem to be fixed in the 
3.2 branch which IMHO should be the target version for Stretch.

[1] https://www.mongodb.com/support-policy
> 
> Laszlo, since you're coming to Debconf, maybe we can discuss this when
> you arrive tomorrow?

I started a discussion with Làszlo quite a while ago regarding an 
updated MongoDB package, but didn't have the time to finish it, so I'd 
be happy to join you as well :)

Regards,
Apollon
Index: mongodb-2.6.11/SConstruct
===
--- mongodb-2.6.11.orig/SConstruct
+++ mongodb-2.6.11/SConstruct
@@ -842,6 +842,10 @@ if nix:
  "-Wno-unused-variable",
  "-Wno-maybe-uninitialized",
  "-Wno-unknown-pragmas",
+			 "-Wno-misleading-indentation",
+			 "-Wno-deprecated-declarations",
+			 "-Wno-nonnull-compare",
+			 "-Wno-error=overflow",
  "-Winvalid-pch"] )
 # env.Append( " -Wconversion" ) TODO: this doesn't really work yet
 if linux or darwin:
Index: mongodb-2.6.11/src/mongo/db/exec/working_set.cpp
===
--- mongodb-2.6.11.orig/src/mongo/db/exec/working_set.cpp
+++ mongodb-2.6.11/src/mongo/db/exec/working_set.cpp
@@ -119,7 +119,7 @@ namespace mongo {
 }
 
 bool WorkingSetMember::hasComputed(const WorkingSetComputedDataType type) const {
-return _computed[type];
+return _computed[type].get();
 }
 
 const WorkingSetComputedData* WorkingSetMember::getComputed(const WorkingSetComputedDataType type) const {
Index: mongodb-2.6.11/src/mongo/db/pipeline/document_source_sort.cpp
===
--- mongodb-2.6.11.orig/src/mongo/db/pipeline/document_source_sort.cpp
+++ mongodb-2.6.11/src/mongo/db/pipeline/document_source_sort.cpp
@@ -99,7 +99,7 @@ namespace mongo {
 bool DocumentSourceSort::coalesce(const intrusive_ptr ) {
 if (!limitSrc) {
 limitSrc = dynamic_cast(pNextSource.get());
-return limitSrc; // false if next is not a $limit
+return limitSrc.get(); // false if next is not a $limit
 }
 else {
 return limitSrc->coalesce(pNextSource);
Index: mongodb-2.6.11/src/mongo/db/pipeline/document_source_cursor.cpp
===
--- mongodb-2.6.11.orig/src/mongo/db/pipeline/document_source_cursor.cpp
+++ mongodb-2.6.11/src/mongo/db/pipeline/document_source_cursor.cpp
@@ -141,7 +141,7 @@ namespace mongo {
 
 if (!_limit) {
 _limit = dynamic_cast(nextSource.get());
-return _limit; // false if next is not a $limit
+return _limit.get(); // false if next is not a $limit
 }
 else {
 return _limit->coalesce(nextSource);
Index: mongodb-2.6.11/src/mongo/s/chunk_manager_targeter.cpp
===
--- mongodb-2.6.11.orig/src/mongo/s/chunk_manager_targeter.cpp
+++ mongodb-2.6.11/src/mongo/s/chunk_manager_targeter.cpp
@@ -48,7 +48,7 @@ namespace mongo {
 *errMsg = ex.toString();
 }
 
-return config;
+return config.get();
 }
 
 ChunkManagerTargeter::ChunkManagerTargeter() :


signature.asc
Description: PGP signature

Bug#827716: Non-maintainer upload to fix RC bugs

[Daniel James]

Hi Ondřej,

>> I'd be happy to merge other fixes I have made since version 1:5.2.0-1
>> into http://anonscm.debian.org/cgit/collab-maint/tidy-html5.git/ if
>> that's OK with you.

I've merged a few of my improvements into collab-maint/tidy-html5.git
today, and merged back most of your improvements to the original repo,
thanks!

The solution for bug #827716 of using Breaks: for the overwritten
symlink is not ideal, because on a system which has the older version of
libtidy installed, the upgrade of libtidy-dev results in the error:

 libtidy-dev (1:5.2.0-1.1) breaks libtidy-0.99-0 and is installed.

...followed by a dpkg error.

The solution I have in the other repo is to use Replaces: for the
library package and Conflicts: for the libtidy-dev package, which means
that the user is warned to remove libtidy-0.99-0 first, but does not
actually result in an error:

https://anonscm.debian.org/cgit/collab-maint/tidy.git/tree/debian/control

I feel this is more accurate because libtidy-dev does not generally fit
the definition 'Replaces: libtidy-0.99-0'

Would you be willing to give this alternative solution for #827716 a try?

Cheers!

Daniel

Bug#829111: spock: FTBFS: exception IOException is never thrown in body of corresponding try statement

[Daniel Schepler]

Source: spock
Version: 0.7-groovy-2.0-2
Severity: serious

>From my pbuilder build log:

...
   dh_auto_build -O--buildsystem=ant
ant -Duser.name debian
Buildfile: /build/spock-0.7-groovy-2.0/debian/build.xml

init:
[mkdir] Created dir: /build/spock-0.7-groovy-2.0/dist

build.core:
[mkdir] Created dir: /build/spock-0.7-groovy-2.0/spock-core/build
  [groovyc] Compiling 350 source files to
/build/spock-0.7-groovy-2.0/spock-core/build
  [groovyc] org.codehaus.groovy.control.MultipleCompilationErrorsException:
startup failed:
  [groovyc] Compile error during compilation with javac.
  [groovyc] warning: [options] bootstrap class path not set in
conjunction with -source 1.5
  [groovyc] warning: [options] source value 1.5 is obsolete and will
be removed in a future release
  [groovyc] warning: [options] target value 1.5 is obsolete and will
be removed in a future release
  [groovyc] warning: [options] To suppress warnings about obsolete
options, use -Xlint:-options.
  [groovyc] 
/build/spock-0.7-groovy-2.0/spock-core/src/main/java/spock/lang/Specification.java:46:
warning: '_' used as an identifier
  [groovyc]   public static final Object _ = Wildcard.INSTANCE;
  [groovyc]  ^
  [groovyc]   (use of '_' as an identifier might not be supported in
releases after Java SE 8)
  [groovyc] 
/build/spock-0.7-groovy-2.0/spock-core/src/main/java/org/spockframework/runtime/ConfigurationScriptLoader.java:129:
error: exception IOException is never thrown in body of corresponding
try statement
  [groovyc] } catch (IOException e) {
  [groovyc]   ^
  [groovyc] Note: Some input files use or override a deprecated API.
  [groovyc] Note: Recompile with -Xlint:deprecation for details.
  [groovyc] 1 error
  [groovyc] 5 warnings
  [groovyc]
  [groovyc]
  [groovyc] 1 error

BUILD FAILED
/build/spock-0.7-groovy-2.0/debian/build.xml:82: The following error
occurred while executing this line:
/build/spock-0.7-groovy-2.0/debian/build.xml:122: Compilation Failed

Total time: 3 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#829103: plexus-compiler: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

[Daniel Schepler]

On Thu, Jun 30, 2016 at 8:40 AM, Emmanuel Bourg  wrote:
> I'm unable to reproduce this error with pbuilder. Are you using locally
> rebuilt packages?

Yes, this was with locally rebuilt packages - sorry I neglected to
check against a vanilla pbuilder chroot, I was assuming all these
would be reproducible now since the new upload of velocity with
reduced dependencies.  But in this case, it looks like the difference
is that my locally rebuilt version of libsisu-plexus-java depends on
libplexus-component-annotations-java instead of
libplexus-containers1.5-java.

So, feel free to downgrade the severity.
-- 
Daniel Schepler

Bug#829103: plexus-compiler: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

[Emmanuel Bourg]

Le 30/06/2016 à 17:32, Daniel Schepler a écrit :

> [ERROR] Plugin org.codehaus.plexus:plexus-component-metadata:1.5.5 or
> one of its dependencies could not be resolved: Cannot access central
> (https://repo.maven.apache.org/maven2) in offline mode and the
> artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has
> not been downloaded from it before. -> [Help 1]

Hi Daniel,

I'm unable to reproduce this error with pbuilder. Are you using locally
rebuilt packages?

Emmanuel bourg

Bug#829106: sisu-inject: FTBFS: the artifact javax.servlet:servlet-api:jar:debian has not been downloaded

[Daniel Schepler]

Source: sisu-inject
Version: 0.3.2-1
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Sisu Inject  SUCCESS [  0.002 s]
[INFO] org.eclipse.sisu.inject  FAILURE [  0.149 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.274 s
[INFO] Finished at: 2016-06-28T00:11:06+00:00
[INFO] Final Memory: 7M/150M
[INFO] 
[ERROR] Failed to execute goal on project org.eclipse.sisu.inject:
Could not resolve dependencies for project
org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.3.2: Cannot access
central (https://repo.maven.apache.org/maven2) in offline mode and the
artifact javax.servlet:servlet-api:jar:debian has not been downloaded
from it before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :org.eclipse.sisu.inject
/usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#829105: sisu-guice: FTBFS: the artifact org.apache.ant:ant:jar:debian has not been downloaded

[Daniel Schepler]

Source: sisu-guice
Version: 3.2.6-2
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Sisu Guice . SUCCESS [  0.003 s]
[INFO] Sisu Guice - Bill of Materials . SUCCESS [  0.001 s]
[INFO] Sisu Guice - Core Library .. FAILURE [  0.158 s]
[INFO] Sisu Guice - Extensions  SKIPPED
[INFO] Sisu Guice - Extensions - AssistedInject ... SKIPPED
[INFO] Sisu Guice - Extensions - TestLib .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.338 s
[INFO] Finished at: 2016-06-27T08:12:06+00:00
[INFO] Final Memory: 7M/150M
[INFO] 
[ERROR] Failed to execute goal on project sisu-guice: Could not
resolve dependencies for project
org.sonatype.sisu:sisu-guice:jar:3.2.6: Cannot access central
(https://repo.maven.apache.org/maven2) in offline mode and the
artifact org.apache.ant:ant:jar:debian has not been downloaded from it
before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :sisu-guice
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/build/sisu-guice-3.2.6
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/sisu-guice-3.2.6/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml
-Ddebian.dir=/build/sisu-guice-3.2.6/debian
-Dmaven.repo.local=/build/sisu-guice-3.2.6/debian/maven-repo package
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#829103: plexus-compiler: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

[Daniel Schepler]

Source: plexus-compiler
Version: 2.4-3
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Plexus Compiler  FAILURE [  0.002 s]
[INFO] Plexus Compiler Api  SKIPPED
[INFO] Plexus Compiler Manager  SKIPPED
[INFO] Plexus Compiler Test Harness ... SKIPPED
[INFO] Plexus Compilers ... SKIPPED
[INFO] Plexus C# Compiler . SKIPPED
[INFO] Plexus Eclipse Compiler  SKIPPED
[INFO] Plexus Jikes Compiler .. SKIPPED
[INFO] Plexus Javac Component . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.300 s
[INFO] Finished at: 2016-06-25T20:58:01+00:00
[INFO] Final Memory: 9M/212M
[INFO] 
[ERROR] Plugin org.codehaus.plexus:plexus-component-metadata:1.5.5 or
one of its dependencies could not be resolved: Cannot access central
(https://repo.maven.apache.org/maven2) in offline mode and the
artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has
not been downloaded from it before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/build/plexus-compiler-2.4
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/plexus-compiler-2.4/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml
-Ddebian.dir=/build/plexus-compiler-2.4/debian
-Dmaven.repo.local=/build/plexus-compiler-2.4/debian/maven-repo
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true
-Dlocale=en_US returned exit code 1
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#829101: maven-shade-plugin: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

[Daniel Schepler]

Source: maven-shade-plugin
Version: 2.4.3-1
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Building Apache Maven Shade Plugin 2.4.3
[INFO] 
[WARNING] The POM for
org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 is missing, no
dependency information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.091 s
[INFO] Finished at: 2016-06-28T19:49:07+00:00
[INFO] Final Memory: 6M/150M
[INFO] 
[ERROR] Plugin org.codehaus.plexus:plexus-component-metadata:1.5.5 or
one of its dependencies could not be resolved: Cannot access central
(https://repo.maven.apache.org/maven2) in offline mode and the
artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has
not been downloaded from it before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/build/maven-shade-plugin-2.4.3
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/maven-shade-plugin-2.4.3/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml
-Ddebian.dir=/build/maven-shade-plugin-2.4.3/debian
-Dmaven.repo.local=/build/maven-shade-plugin-2.4.3/debian/maven-repo
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit
code 1
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Processed: Pending fixes for bugs in the libwx-scintilla-perl package

[Debian Bug Tracking System]

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

> tag 816571 + pending
Bug #816571 [libwx-scintilla-perl] libwx-scintilla-perl: FTBFS with GCC 6: call 
overloaded is ambiguous
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to sgt-puzzles, tagging 684193, tagging 811577, tagging 767531, tagging 791982

[Debian Bug Tracking System]

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

> limit source sgt-puzzles
Limiting to bugs with field 'source' containing at least one of 'sgt-puzzles'
Limit currently set to 'source':'sgt-puzzles'

> tags 684193 + pending
Bug #684193 [sgt-puzzles] guess command conflicts with nvram-wakeup; many 
others have generic names
Added tag(s) pending.
> tags 811577 + pending
Bug #811577 [sgt-puzzles] FTBFS with GCC 6: statement indented as if it were 
guarded by
Added tag(s) pending.
> tags 767531 + pending
Bug #767531 [sgt-puzzles] sgt-puzzles: Patch for Lintian warning 
'hardening-no-relro'
Added tag(s) pending.
> tags 791982 + pending
Bug #791982 [sgt-puzzles] New upstream games
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#817531: marked as done (libimage-info-perl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 13:53:51 +
with message-id 
and subject line Bug#817531: fixed in libimage-info-perl 1.28-1.2
has caused the Debian Bug report #817531,
regarding libimage-info-perl: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libimage-info-perl
Severity: important
Usertags: compat-4-removal

Hi,

The package libimage-info-perl uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: libimage-info-perl
Source-Version: 1.28-1.2

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libimage-info-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Jun 2016 15:32:30 +0200
Source: libimage-info-perl
Binary: libimage-info-perl
Architecture: source all
Version: 1.28-1.2
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: gregor herrmann 
Description:
 libimage-info-perl - allows extraction of meta information from image files
Closes: 817531
Changes:
 libimage-info-perl (1.28-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "Removal of debhelper compat 4": use debhelper compat level 9.
 (Closes: #817531)
Checksums-Sha1:
 866b79f6a5f16396a6738dca6d901a1553c9dbaf 2012 libimage-info-perl_1.28-1.2.dsc
 d2f2c8fd624c618e5e2b1bc6c68556b3ab718a8d 4025 
libimage-info-perl_1.28-1.2.diff.gz
 2fc31f150fe4d4962942d0c4af95e6f134b2 52384 
libimage-info-perl_1.28-1.2_all.deb
Checksums-Sha256:
 78d6060432eb56791407d562a4777212be7b325659a49d45828cca7fd6e6df55 2012 
libimage-info-perl_1.28-1.2.dsc
 2c9c6dc5d110315e63df1b05e480a6ec5a79a29d73faeb7d3c89f8d639fea9b0 4025 
libimage-info-perl_1.28-1.2.diff.gz
 f18f15a191d992f6d8336951219d19774abf3487e2cfd27c17114b6c97c4150d 52384 
libimage-info-perl_1.28-1.2_all.deb
Files:
 a52ec68fd1e6b3551345ffe1e5f4adbe 2012 perl optional 
libimage-info-perl_1.28-1.2.dsc
 6c9dce67a1facd4741e65b3396285529 4025 perl optional 
libimage-info-perl_1.28-1.2.diff.gz
 fdfcac0e17b2eebecd19b287475f6f8f 52384 perl optional 
libimage-info-perl_1.28-1.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXcnyDXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGsaMQALIuyiay1ZOVvMThpbDQDiVe
dqJKI1zQoa78ddXI0tr+3UxTbviTHYz9+m/J9EQ0O4ygxkSOynEuBKBidpNZ1bYY
7h+y3MCbqH82PjZMhnC1gL3IMc74jVoBE89FTLH50oXI4q9oZCbY+sSGpu1YIEQP
7xG/E0+EfqwtKqjuv1o9Zs3WXI3H3sRVebH+BrTszLcPd6lZwpUvT5NqJAGrhNBt
xzn60f1+LY6q6pfkwzsLwb85AwcEvZ3Y3tqDDr+wntzRNpxOXf6rEGWZpmCEz6Td
SVXsGTqT43ic6uRFZZVFb4wxur4DPIV4DEc3sCufG4nJaEGp2X0Rds3IrQUBFyFM
Is6+/ldbuqmyZwYS7f/iUMMgCwM6bsbqih8D7ePc90byfuiBDOEWEDdm77G8Ir5f
5RdsTxLAuP7IebDFVkWvJH5hDt3XLaNnxqP0Zw0Am839TMKiGY12wQwawvYI5Wfd
aw43FzlG6DrX/sF1bXSCWnZDsXyoq1DGvBdM4HbLrLzNR4XDtmUZg7At7ezJ9MXF
LkwpeNqbEcXhXw2+/aFHYgV466IYhlYI9D7Abvv3MX+V3qDBAkYOk99VaOxZKktH
KHJVy/XhKPPYwi/ZdzZfLQOPVFIPfAqUQn12O3ZH8Kpuu1vtcQ0qBSVtG11PmVcA
+NIWVAGQ9+byuN+TqPzn
=Yn02
-END PGP SIGNATURE End Message ---

Bug#812030: marked as done (previsat: FTBFS with GCC 6: needed for in-class initialization)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 13:59:45 +
with message-id 
and subject line Bug#812030: fixed in previsat 3.5.1.7+dfsg1-2
has caused the Debian Bug report #812030,
regarding previsat: FTBFS with GCC 6: needed for in-class initialization
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.)


-- 
812030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: previsat
Version: 3.5.0.8+dfsg1-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
...
> g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT 
> -fPIC -DAPPVERSION="\"3.5.0.8\"" -DAPPVER_MAJ="\"3.5\"" 
> -DAPP_ANNEES_DEV="\"2005-2015\"" -DQT_NO_DEBUG -DQT_WEBKITWIDGETS_LIB 
> -DQT_WEBKIT_LIB -DQT_MULTIMEDIA_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o previsat.o 
> previsat.cpp
> In file included from librairies/corps/satellite/satellite.h:44:0,
>  from previsat.cpp:79:
> librairies/corps/satellite/sgp4.h:91:31: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZEL' of 
> non-integral type [-fpermissive]
>  static const double ZEL = 0.0549;
>^~
> 
> librairies/corps/satellite/sgp4.h:92:31: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZES' of 
> non-integral type [-fpermissive]
>  static const double ZES = 0.01675;
>^~~
> 
> librairies/corps/satellite/sgp4.h:93:31: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZNL' of 
> non-integral type [-fpermissive]
>  static const double ZNL = 1.5835218e-4;
>^~~~
> 
> librairies/corps/satellite/sgp4.h:94:31: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZNS' of 
> non-integral type [-fpermissive]
>  static const double ZNS = 1.19459e-5;
>^~
> 
> librairies/corps/satellite/sgp4.h:95:32: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::C1SS' of 
> non-integral type [-fpermissive]
>  static const double C1SS = 2.9864797e-6;
> ^~~~
> 
> librairies/corps/satellite/sgp4.h:96:31: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::C1L' of 
> non-integral type [-fpermissive]
>  static const double C1L = 4.7968065e-7;
>^~~~
> 
> librairies/corps/satellite/sgp4.h:97:34: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZSINIS' of 
> non-integral type [-fpermissive]
>  static const double ZSINIS = 0.39785416;
>   ^~
> 
> librairies/corps/satellite/sgp4.h:98:34: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZCOSIS' of 
> non-integral type [-fpermissive]
>  static const double ZCOSIS = 0.91744867;
>   ^~
> 
> librairies/corps/satellite/sgp4.h:99:34: error: 'constexpr' needed for 
> in-class initialization of static data member 'const double SGP4::ZCOSGS' of 
> 

Bug#817529: marked as done (libimage-base-bundle-perl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 13:53:37 +
with message-id 
and subject line Bug#817529: fixed in libimage-base-bundle-perl 1.0.7-3.2
has caused the Debian Bug report #817529,
regarding libimage-base-bundle-perl: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libimage-base-bundle-perl
Severity: important
Usertags: compat-4-removal

Hi,

The package libimage-base-bundle-perl uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: libimage-base-bundle-perl
Source-Version: 1.0.7-3.2

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libimage-base-bundle-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Jun 2016 15:28:29 +0200
Source: libimage-base-bundle-perl
Binary: libimage-base-bundle-perl
Architecture: source all
Version: 1.0.7-3.2
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: gregor herrmann 
Description:
 libimage-base-bundle-perl - set of modules for loading, saving and creating 
xpm and xbm image
Closes: 817529
Changes:
 libimage-base-bundle-perl (1.0.7-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "Removal of debhelper compat 4": use debhelper compat level 9.
 (Closes: #817529)
Checksums-Sha1:
 05f5e4d9fc425f25b4b409b6e241ea91955cfc0f 1946 
libimage-base-bundle-perl_1.0.7-3.2.dsc
 1bd46af8fc4e435b3a0e088cd49f7fc0328b187e 2366 
libimage-base-bundle-perl_1.0.7-3.2.diff.gz
 83ccfc71ae45d8e7a713e1c7b1e0bc8f0a726971 26768 
libimage-base-bundle-perl_1.0.7-3.2_all.deb
Checksums-Sha256:
 489324591c8a02ef494b47eb8699030fa9eb1660cbd8272284ed2865780cb8c2 1946 
libimage-base-bundle-perl_1.0.7-3.2.dsc
 29e9060f490e4d6000dd10160b96fa705900fc901e54fce03a7973f2a15c61f8 2366 
libimage-base-bundle-perl_1.0.7-3.2.diff.gz
 012486c6032c302a248ac87e94565dbc4e2f87a011eac6d3b8b92e6643f95cbd 26768 
libimage-base-bundle-perl_1.0.7-3.2_all.deb
Files:
 3cd51f29861b79001b96021b5e65f474 1946 perl optional 
libimage-base-bundle-perl_1.0.7-3.2.dsc
 1008680cf604f6a95c58b9b266a23480 2366 perl optional 
libimage-base-bundle-perl_1.0.7-3.2.diff.gz
 997c3605b7d91d825cd5a4039bd8d13e 26768 perl optional 
libimage-base-bundle-perl_1.0.7-3.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXcnuWXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGSQ4QAIB83ATcMS3VjSgrhRm+z6t/
b5J1rl0Bzb105uIWSk2FAOnBFRuVwQNcv0eftpaoEofuizV5g7dwSzry5K7Ft+3A
WsVZz0VSRKRv05c16dK8faW1mVKKDXOdyKyusKHOJqrsosvWUn44NEk6/EZbNJLt
2+G5Tffdr8PvpXbvdhkR06e+I+vFVlIjis3xGdD/N3SVjnTFkUDuA5OUaSIQVY6a
PzrBhRhl0KaUN7D9SkiyYQA5I+7zQG8dGIBe/EHeLPRdVY+7yc5F7BVj+fYvHsL0
RfIb21onCJsIMg2ZFacvOgrPFXQ/mTztxhesB+poVS+CoRYVNPrfbHxp4K0NDNxR
IJfR2f/4I/rM/0aSn8s3Oo1DTOqDQxPksjjBNsRAqs81iBNdFSyYT3lPw5hf0amZ
o5dCMQ2Z2rLyIrJKbmJ4uObVFg7xfBxkjzi48YN4G+zdzdXhgCLPXMjTCC1wfF1Y
amn5Z8atfoqAWnoWnmWEJMX+QsagbtQ0NyfR6R2Im10rfVLCGvsBZ9XDxL0v3JoB
+481kDJIltvuvopdmZefKJRDWoHSb5fgFhF31nd7BdmpumLFu0v49DRjbxKS85v7
uP5iLe4lZ2y8ZQgYaVii8dAVU0FR+TMb6LT3rFxF7l/FVIMU6ee2/jrCsHOEu2uY
lZuPgsCUtjHGqx57SyrI
=7Dop
-END PGP 

Bug#811667: Fix in upstream

[Matthias Klose]

could you pick the relevant SVN changes?

Bug#811739: marked as done (adplay: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 13:18:50 +
with message-id 
and subject line Bug#811739: fixed in adplay 1.7-2
has caused the Debian Bug report #811739,
regarding adplay: 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.)


-- 
811739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adplay
Version: 1.7-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
...
> g++ -DHAVE_CONFIG_H -I.  -I/usr/include/libbinio  -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -DADPLUG_DATA_DIR=\"/usr/com/adplug\" 
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o alsa.o alsa.cc
> esound.cc: In member function 'virtual void EsoundPlayer::output(const void*, 
> long unsigned int)':
> esound.cc:46:27: warning: ignoring return value of 'ssize_t write(int, const 
> void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
>write(socket, buf, size);
>^
> 
> oss.cc: In member function 'virtual void OSSPlayer::output(const void*, long 
> unsigned int)':
> oss.cc:59:29: warning: ignoring return value of 'ssize_t write(int, const 
> void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
>write(audio_fd, buf, size);
>  ^
> 
> adplay.cc:98:1: error: narrowing conversion of '-1' from 'int' to 'unsigned 
> int' inside { } [-Wnarrowing]
>  };
>  ^
> 
> Makefile:497: recipe for target 'adplay.o' failed
> make[3]: *** [adplay.o] Error 1
> make[3]: *** Waiting for unfinished jobs

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: adplay
Source-Version: 1.7-2

We believe that the bug you reported is fixed in the latest version of
adplay, 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 adplay 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: Thu, 30 Jun 2016 14:55:20 +0200
Source: adplay
Binary: adplay
Architecture: source
Version: 1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Matthias Klose 
Description:
 adplay - console-based OPL2 audio player
Closes: 811739
Changes:
 adplay (1.7-2) unstable; urgency=medium
 .
   * QA upload.
   * Fix build failure using GCC 6. Closes: #811739.
Checksums-Sha1:
 c0457dbb7a0db65ef1ef2547b3cd1d086bd503cd 1770 adplay_1.7-2.dsc
 b7121425193ea55eab343dd62d9d8638707ab107 6296 adplay_1.7-2.debian.tar.xz
Checksums-Sha256:
 1a1d7036cbe599d6bf50ba5622165730eb1fe4f7c1552145b07868d2b0b4ff18 1770 
adplay_1.7-2.dsc
 4c234fb94101233f368ed30fe08317c1c4b20f6e17a1ea0f5959f7ddea525075 6296 
adplay_1.7-2.debian.tar.xz
Files:
 d70a06168ee08c3573adfd60387ed051 1770 sound optional adplay_1.7-2.dsc
 83da053f92206bbd2f2fd527abaee066 6296 sound optional adplay_1.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXdRplAAoJEL1+qmB3j6b1XPEQAMjkPLyV24wSfmhiYWYY3rjX
SwhzHv9mJY4Apwh9Jd+pwdunQ+Q8QJZt1cuI12VQ7ysuMwy9zi4kjlT8HTYbJ50t
oQo9P9xQ8o0/WM272b65pkTZaqOBNcYm2N+h9intLN7F6MV6xrbF9t/0wlt4HtIQ
hN/ZlpZ+GdWgSEyOXDkHxfxEArQJDXHbjVH8I2mAYZVyLxUy/FCbgi7aaRWzI24/
MsGDV2RTsyfo8zIbjcvZ2dTzvvZs/DemyMXD9qO8qpRsXkjdb55SVUQqWkfMg2YH
tNq4lYE5uHOAR1wfCnsKG5bX3EJT8IkZAkCe8riQGCbccTsx48yOkGU2gZlazWhk

Processed: libqtpas: FTBFS with GCC 6: symbol changes

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #811965 [libqt4pas] libqt4pas: FTBFS with GCC 6: symbol changes
Severity set to 'important' from 'serious'

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

Bug#811965: libqtpas: FTBFS with GCC 6: symbol changes

[Matthias Klumpp]

Control: severity -1 important

Hi!
I can only adapt the symbols file correctly if GCC 6 is default,
because otherwise this package would likely FTBFS with the current GCC
5 compiler.
Therefore adjusting severity to important, and this will get fixed as
soon as GCC 6 is the default compiler in Debian.

Thanks for reporting the issue!
Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

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

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 12:50:12 +
with message-id 
and subject line Bug#811675: fixed in xdrawchem 2.0-5
has caused the Debian Bug report #811675,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.

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

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


-- 
811675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xdrawchem
Version: 2.0-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -c -m64 -pipe -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -g -O0 -g3 
> -D_REENTRANT -Wall -W -DUNIX -DRINGHOME="/usr/share/xdrawchem2" 
> -DQT_NO_CAST_TO_ASCII -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. 
> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 
> -I/usr/include/openbabel-2.0 -I.moc -o .obj/molecule_obmol.o 
> xdrawchem/molecule_obmol.cpp
> In file included from /usr/include/openbabel-2.0/openbabel/atom.h:33:0,
>  from /usr/include/openbabel-2.0/openbabel/mol.h:42,
>  from xdrawchem/molecule.h:6,
>  from xdrawchem/molecule_obmol.cpp:9:
> /usr/include/openbabel-2.0/openbabel/base.h: In member function 'virtual 
> const char* OpenBabel::OBBase::GetTitle(bool) const':
> /usr/include/openbabel-2.0/openbabel/base.h:287:68: warning: unused parameter 
> 'replaceNewlines' [-Wunused-parameter]
>virtual const char  *GetTitle(bool UNUSED(replaceNewlines) = true) 
> const { return "";}
> ^~~~
> 
> xdrawchem/molecule_obmol.cpp: In member function 'OpenBabel::OBMol* 
> Molecule::convertToOBMol()':
> xdrawchem/molecule_obmol.cpp:222:28: error: cannot convert 'bool' to 
> 'OpenBabel::OBMol*' in return
>  return ( false );
> ^
> 
> xdrawchem/molecule_obmol.cpp:239:28: error: cannot convert 'bool' to 
> 'OpenBabel::OBMol*' in return
>  return ( false );
> ^
> 
> Makefile:1293: recipe for target '.obj/molecule_obmol.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: xdrawchem
Source-Version: 2.0-5

We believe that the bug you reported is fixed in the latest version of
xdrawchem, 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.
Georges Khaznadar  (supplier of updated xdrawchem 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: Thu, 30 Jun 2016 12:26:08 +0200
Source: xdrawchem
Binary: xdrawchem
Architecture: source amd64
Version: 2.0-5
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 xdrawchem  - Chemical structures and reactions editor
Closes: 811675
Changes:
 xdrawchem (2.0-5) unstable; urgency=medium
 .
   * prepared for GCC6: patched xdrawchem/molecule_obmol.cpp,
 checked the compilation with QT_CXX = g++-6. Closes: #811675
   * upgraded Standards-Version to 3.9.8
Checksums-Sha1:
 ebe0c29adc3bcfea2d85441bc1fe2ffb020a5571 1780 xdrawchem_2.0-5.dsc
 6f3f5e1f9967d34d0d0cd1cd8b2edb81d4e064bd 23236 xdrawchem_2.0-5.debian.tar.xz
 bd1124af88717776856ec288be84f455d1a75cc9 6674508 
xdrawchem-dbgsym_2.0-5_amd64.deb
 00a90555a151edc7f3549e90e8d1a603aa3a3afd 554078 xdrawchem_2.0-5_amd64.deb
Checksums-Sha256:

Bug#828767: marked as done (toxiproxy: FTBFS: B-D favors old mux, logrus packages)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 12:38:30 +
with message-id 
and subject line Bug#828767: fixed in toxiproxy 2.0.0+dfsg1-3
has caused the Debian Bug report #828767,
regarding toxiproxy: FTBFS: B-D favors old mux, logrus packages
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.)


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

Automated builds of toxiproxy have been failing to start because its
build dependencies include

golang-mux-dev | golang-github-gorilla-mux-dev

golang-github-gorilla-mux-dev has replaced golang-mux-dev in the
archive, but the autobuilders don't care because they ignore
alternative dependencies for the sake of determinism (unless
architecture qualifiers explicitly eliminate earlier options).
Please either flip this dependency or specify just
golang-github-gorilla-mux-dev.

Likewise for golang-logrus-dev | golang-github-sirupsen-logrus-dev;
although there's still a transitional golang-logrus-dev package in the
archive, you shouldn't count on its long-term availability.

Thanks!

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

Kernel: Linux 4.5.0-2-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)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: toxiproxy
Source-Version: 2.0.0+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
toxiproxy, 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.
Alexandre Viau  (supplier of updated toxiproxy 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: Thu, 30 Jun 2016 14:12:28 +0200
Source: toxiproxy
Binary: toxiproxy-dev toxiproxy toxiproxy-cli
Architecture: source amd64 all
Version: 2.0.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 toxiproxy  - proxy to simulate network and system conditions
 toxiproxy-cli - proxy to simulate network and system conditions - CLI
 toxiproxy-dev - proxy to simulate network and system conditions - dev package
Closes: 828767
Changes:
 toxiproxy (2.0.0+dfsg1-3) unstable; urgency=medium
 .
   * Depend on new packages (Closes: #828767)
Checksums-Sha1:
 5fcd0424ebf3b916b0a81110aa6d41a14aba327f 2282 toxiproxy_2.0.0+dfsg1-3.dsc
 0665a125dac2a7b5468886b875cf1e8aaddcfab9 5136 
toxiproxy_2.0.0+dfsg1-3.debian.tar.xz
 4ae35641aee05b10e22ac805e841200fc34bed5b 1492182 
toxiproxy-cli_2.0.0+dfsg1-3_amd64.deb
 b7627f39cde597792ab3a2a4a787a07d49573b61 26746 
toxiproxy-dev_2.0.0+dfsg1-3_all.deb
 9f600f3a1778f96bac254b664184226e73a02830 1449410 
toxiproxy_2.0.0+dfsg1-3_amd64.deb
Checksums-Sha256:
 b5db1f8e2d15aff96c9bf9baf9cf0460b34f509a8bf45694aa3910ea8971884e 2282 
toxiproxy_2.0.0+dfsg1-3.dsc
 47ac52dd1f6effa0f379d510d2a6e25c50dfeacf9deac94e5a657bc6e0c4f3dd 5136 
toxiproxy_2.0.0+dfsg1-3.debian.tar.xz
 7a68b8a3b9e242323d54b10c344fdc19a6c303ecf1395f23f7b2beaa2ba4b002 1492182 
toxiproxy-cli_2.0.0+dfsg1-3_amd64.deb
 140771645facf51d4e3b4a72d1cf876ec25b9f022ad7b9de92299ed77cda9ba4 26746 
toxiproxy-dev_2.0.0+dfsg1-3_all.deb
 524c93294257fbb021c88ad0f9143707866c8579beddeaaeefcf43da06f5b333 1449410 
toxiproxy_2.0.0+dfsg1-3_amd64.deb
Files:
 e0f4aa722ddbbd9ad474f082a9556156 2282 net optional toxiproxy_2.0.0+dfsg1-3.dsc
 a16365b3ea18fb9ad251730f96073cfa 5136 net optional 
toxiproxy_2.0.0+dfsg1-3.debian.tar.xz
 7d2470642dcae21d4ee170b1d43d839c 1492182 net optional 
toxiproxy-cli_2.0.0+dfsg1-3_amd64.deb
 2891211c56268ba6b99fd1a1f3d1e573 26746 devel optional 

Bug#811997: marked as done (aria2: FTBFS with GCC 6: call overloaded is ambiguous)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 12:33:56 +
with message-id 
and subject line Bug#811997: fixed in aria2 1.24.0-1
has caused the Debian Bug report #811997,
regarding aria2: FTBFS with GCC 6: call overloaded 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.)


-- 
811997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aria2
Version: 1.19.0-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

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

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>   CXX  Context.lo
> AuthConfig.cc: In static member function 'static 
> std::unique_ptr 
> aria2::AuthConfig::create(std::__cxx11::string, std::__cxx11::string)':
> AuthConfig.cc:66:72: error: call of overloaded 
> 'make_unique(std::remove_reference::type, 
> std::remove_reference::type)' is ambiguous
>  return make_unique(std::move(user), std::move(password));
> ^
> 
> In file included from AuthConfig.cc:39:0:
> a2functional.h:178:1: note: candidate: typename std::enable_if<(! 
> std::is_array<  >::value), std::unique_ptr<_Tp> 
> >::type aria2::make_unique(U&& ...) [with T = aria2::AuthConfig; U = 
> {std::__cxx11::basic_string std::allocator >, std::__cxx11::basic_string std::char_traits, std::allocator >}; typename std::enable_if<(! 
> std::is_array<  >::value), std::unique_ptr<_Tp> 
> >::type = std::unique_ptr]
>  make_unique(U&&... u)
>  ^~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from AuthConfig.h:42,
>  from AuthConfig.cc:35:
> /usr/include/c++/6/bits/unique_ptr.h:786:5: note: candidate: typename 
> std::_MakeUniq<_Tp>::__single_object std::make_unique(_Args&& ...) [with _Tp 
> = aria2::AuthConfig; _Args = {std::__cxx11::basic_string std::char_traits, std::allocator >, 
> std::__cxx11::basic_string >}; typename std::_MakeUniq<_Tp>::__single_object = 
> std::unique_ptr]
>  make_unique(_Args&&... __args)
>  ^~~
> 
>   CXX  ContextAttribute.lo
>   CXX  Cookie.lo
> Makefile:2299: recipe for target 'AuthConfig.lo' failed
> make[4]: *** [AuthConfig.lo] Error 1
> make[4]: *** Waiting for unfinished jobs
> AuthConfigFactory.cc: In member function 'std::unique_ptr 
> aria2::AuthConfigFactory::createAuthConfig(const 
> std::shared_ptr&, const aria2::Option*)':
> AuthConfigFactory.cc:70:71: error: call of overloaded 'make_unique(const 
> string&, const string&, const string&, uint16_t, const string&, bool)' is 
> ambiguous
> request->getDir(), true));
>^
> 
> In file included from AuthConfigFactory.h:45:0,
>  from AuthConfigFactory.cc:35:
> a2functional.h:178:1: note: candidate: typename std::enable_if<(! 
> std::is_array<  >::value), std::unique_ptr<_Tp> 
> >::type aria2::make_unique(U&& ...) [with T = aria2::BasicCred; U = {const 
> std::__cxx11::basic_string >&, const std::__cxx11::basic_string std::allocator >&, const std::__cxx11::basic_string std::char_traits, std::allocator >&, short unsigned int, const 
> std::__cxx11::basic_string >&, bool}; typename std::enable_if<(! std::is_array<  
> >::value), std::unique_ptr<_Tp> >::type = std::unique_ptr]
>  make_unique(U&&... u)
>  ^~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from AuthConfigFactory.h:42,
>  from AuthConfigFactory.cc:35:
> /usr/include/c++/6/bits/unique_ptr.h:786:5: note: candidate: typename 
> std::_MakeUniq<_Tp>::__single_object std::make_unique(_Args&& ...) [with _Tp 
> = aria2::BasicCred; _Args = {const std::__cxx11::basic_string std::char_traits, 

Processed: bug 828985 is forwarded to https://github.com/gosimple/slug/issues/8

[Debian Bug Tracking System]

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

> forwarded 828985 https://github.com/gosimple/slug/issues/8
Bug #828985 [src:golang-github-gosimple-slug] golang-github-gosimple-slug: 
FTBFS: FAIL: TestSubstituteLang (0.00s)slug_test.go:155: 1. Substitute("o a 
o", map[string]string{"o":"no", "a":"or"}) = "no nor no"; want "no or no"
Set Bug forwarded-to-address to 'https://github.com/gosimple/slug/issues/8'.
> thanks
Stopping processing here.

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

Bug#829088: ccache may silently miscompile symlinked source files

[Stefan Fritsch]

found 829088 3.2.5-1
thanks

Version 3.2.5-1 is also affected by this issue.

Attached is a log file from that version.

Since the path names are rather complicated in the examples: The dir with 
the symlinked source files is (note the obj in the 3rd component):

/changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc-minimal/libc/src/libc/stdlib/malloc-standard/free.c

The path to the source file with all symlinks resolved is (there is no 
obj/ and no amd64/ in this path):

/changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/contrib/uclibc/libc/stdlib/malloc-standard/free.c

ccache-log.3.2.5-1.fail
Description: Binary data