Bug#871325: marked as done (shiro: FTBFS: [ERROR] Failed to execute goal on project shiro-core: Could not resolve dependencies for project org.apache.shiro:shiro-core:jar:1.3.

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 05:34:36 +
with message-id 
and subject line Bug#871325: fixed in shiro 1.3.2-2
has caused the Debian Bug report #871325,
regarding shiro: FTBFS: [ERROR] Failed to execute goal on project 
shiro-core: Could not resolve dependencies for project 
org.apache.shiro:shiro-core:jar:1.3.2: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
junit:junit:jar:4.x has not been downloaded from it before. -> [Help 
1]
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.)


-- 
871325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shiro
Version: 1.3.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibshiro-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Shiro
> [INFO] Apache Shiro :: Core
> [INFO] Apache Shiro :: Web
> [INFO] Apache Shiro :: Support :: AspectJ
> [INFO] Apache Shiro :: Support :: EHCache
> [INFO] Apache Shiro :: Support :: Quartz
> [INFO] Apache Shiro :: Support :: Spring
> [INFO] Apache Shiro :: Support :: Guice
> [INFO] Apache Shiro :: Support :: Karaf Features
> [INFO] Apache Shiro :: Support
> [INFO] Apache Shiro :: Tools
> [INFO] Apache Shiro :: Tools :: Hasher
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache Shiro 1.3.2
> [INFO] 
> 
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache Shiro :: Core 1.3.2
> [INFO] 
> 
> [WARNING] The POM for junit:junit:jar:4.x is missing, no dependency 
> information available
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Shiro ... 
> SUCCESS [  0.001 s]
> [INFO] Apache Shiro :: Core ... 
> FAILURE [  0.045 s]
> [INFO] Apache Shiro :: Web  
> SKIPPED
> [INFO] Apache Shiro :: Support :: AspectJ . 
> SKIPPED
> [INFO] Apache Shiro :: Support :: EHCache . 
> SKIPPED
> [INFO] Apache Shiro :: Support :: Quartz .. 
> SKIPPED
> [INFO] Apache Shiro :: Support :: Spring .. 
> SKIPPED
> [INFO] Apache Shiro :: Support :: Guice ... 
> SKIPPED
> [INFO] Apache Shiro :: Support :: Karaf Features .. 
> SKIPPED
> [INFO] Apache Shiro :: Support  
> SKIPPED
> [INFO] Apache Shiro :: Tools .. 
> SKIPPED
> [INFO] Apache Shiro :: Tools :: Hasher  
> SKIPPED
> [INFO] 
> 

Bug#871325: Pending fixes for bugs in the shiro package

[pkg-java-maintainers]

tag 871325 + pending
thanks

Some bugs in the shiro package are closed in revision
ea98dfd94df20016a7f48c498f79a5578eae6751 in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/shiro.git/commit/?id=ea98dfd

Commit message:

Add missing build-dep on junit4 (Closes: #871325)

Processed: Pending fixes for bugs in the shiro package

[Debian Bug Tracking System]

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

> tag 871325 + pending
Bug #871325 [src:shiro] shiro: FTBFS: [ERROR] Failed to execute goal 
on project shiro-core: Could not resolve dependencies for 
project org.apache.shiro:shiro-core:jar:1.3.2: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
junit:junit:jar:4.x has not been downloaded from it before. -> [Help 
1]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#853688: tulip: ftbfs with GCC-7

[Aaron M. Ucko]

Source: tulip
Version: 4.8.0dfsg-2
Followup-For: Bug #853688

This bug broke the recent attempt to perform a binNMU against binutils
2.29, blocking a number of upgrades on systems with tulip installed.
AFAICT, you can address the immediate problem by having
thirdparty/OGDF/include/ogdf/basic/DisjointSets.h #include 
for memcpy().  I haven't checked whether there are other compatibility
issues, but suspect they should be similarly trivial to address.  (If
not, you can temporarily build-depend on, and build with, g++-6.)
Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#871352: marked as done (jdeb: FTBFS: [ERROR] /<>/src/test/java/org/vafer/jdeb/mapping/LsMapperTestCase.java:[25,45] cannot find symbol)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 04:34:14 +
with message-id 
and subject line Bug#871352: fixed in jdeb 1.5-6
has caused the Debian Bug report #871352,
regarding jdeb: FTBFS: [ERROR] 
/<>/src/test/java/org/vafer/jdeb/mapping/LsMapperTestCase.java:[25,45]
 cannot find symbol
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.)


-- 
871352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jdeb
Version: 1.5-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibjdeb-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] 
> 
> [INFO] Building jdeb 1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.2:resources 
> (default-resources) @ jdeb ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:compile 
> (default-compile) @ jdeb ---
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 49 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/org/vafer/jdeb/ControlBuilder.java: 
> /<>/src/main/java/org/vafer/jdeb/ControlBuilder.java uses or 
> overrides a deprecated API.
> [INFO] 
> /<>/src/main/java/org/vafer/jdeb/ControlBuilder.java: Recompile 
> with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-plugin-plugin:3.5:descriptor 
> (default-descriptor) @ jdeb ---
> [INFO] Using 'UTF-8' encoding to read mojo source files.
> [INFO] java-annotations mojo extractor found 1 mojo descriptor.
> line 8 column 4 - Error:  is not recognized!
> line 9 column 6 - Error:  is not recognized!
> line 10 column 8 - Error:  is not recognized!
> line 11 column 8 - Error:  is not recognized!
> line 12 column 8 - Error:  is not recognized!
> line 14 column 8 - Error:  is not recognized!
> [INFO] 
> [INFO] --- maven-plugin-plugin:3.5:descriptor 
> (mojo-descriptor) @ jdeb ---
> [INFO] Using 'UTF-8' encoding to read mojo source files.
> [INFO] java-annotations mojo extractor found 1 mojo descriptor.
> line 8 column 4 - Error:  is not recognized!
> line 9 column 6 - Error:  is not recognized!
> line 10 column 8 - Error:  is not recognized!
> line 11 column 8 - Error:  is not recognized!
> line 12 column 8 - Error:  is not recognized!
> line 14 column 8 - Error:  is not recognized!
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.2:testResources 
> (default-testResources) @ jdeb ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 22 resources
> [INFO] 
> [INFO] --- 

Processed: severity of 872517 is grave

[Debian Bug Tracking System]

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

> severity 872517 grave
Bug #872517 [ffmpeg] ffmpeg: CVE-2017-7206: heap-based buffer over-read in 
embed libav
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#871352: Pending fixes for bugs in the jdeb package

[pkg-java-maintainers]

tag 871352 + pending
thanks

Some bugs in the jdeb package are closed in revision
401873652282632a48e34fd76381089a37a71949 in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jdeb.git/commit/?id=4018736

Commit message:

Add build-dep on junit (Closes: #871352)

Processed: Pending fixes for bugs in the jdeb package

[Debian Bug Tracking System]

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

> tag 871352 + pending
Bug #871352 [src:jdeb] jdeb: FTBFS: [ERROR] 
/<>/src/test/java/org/vafer/jdeb/mapping/LsMapperTestCase.java:[25,45]
 cannot find symbol
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871609: marked as done (python3-gpg package should ship tofu module)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 03:07:13 +
with message-id 
and subject line Bug#871465: fixed in gpgme1.0 1.9.0-3
has caused the Debian Bug report #871465,
regarding python3-gpg package should ship tofu module
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.)


-- 
871465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dput
Version: 1.0.0
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading to 1.0.0 form experimental, dput fails to start with the
following stack trace:

Traceback (most recent call last):
  File "/usr/bin/dput", line 11, in 
load_entry_point('dput==1.0.0', 'console_scripts', 'execute-dput')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 561, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2649,
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2303,
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2309,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/dput/dput/dput.py", line 28, in 
from . import crypto
  File "/usr/share/dput/dput/crypto.py", line 14, in 
import gpg
  File "/usr/lib/python3/dist-packages/gpg/__init__.py", line 101, in 
from . import core
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 36, in 
from . import constants
  File "/usr/lib/python3/dist-packages/gpg/constants/__init__.py", line 28, in

from . import data, keylist, sig, tofu # The subdirs.
ImportError: cannot import name 'tofu'



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

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

Versions of packages dput depends on:
ii  python33.5.3-3
ii  python3-debian 0.1.30
ii  python3-gpg1.9.0-2
ii  python3-pkg-resources  36.0.1-1

dput recommends no packages.

Versions of packages dput suggests:
ii  lintian 2.5.52
pn  mini-dinstall   
ii  openssh-client  1:7.5p1-5
ii  rsync   3.1.2-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.9.0-3

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gpgme1.0 
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, 17 Aug 2017 22:16:47 -0400
Source: gpgme1.0
Binary: libgpgme-dev libgpgme11 python3-gpg python-gpg libqgpgme7 libgpgmepp6 
libgpgmepp-dev libgpgmepp-doc
Architecture: source
Version: 1.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 libgpgme-dev - GPGME - GnuPG Made Easy (development files)
 libgpgme11 - GPGME - GnuPG Made Easy (library)
 libgpgmepp-dev - C++ and Qt bindings for GPGME (development files)
 libgpgmepp-doc - C++ and Qt bindings for GPGME (documentation for developers)
 libgpgmepp6 - C++ wrapper library for GPGME
 libqgpgme7 - library for GPGME integration with Qt
 python-gpg - Python interface to the GPGME GnuPG encryption library (Python 2)
 python3-gpg - Python interface to the GPGME GnuPG encryption library (Python 3)
Closes: 871465
Changes:
 gpgme1.0 (1.9.0-3) unstable; urgency=medium
 .
   * imported cleanup+bugfixes from upstream
   * removed unnecessary 

Bug#871465: marked as done (python3-gpg package should ship tofu module)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 03:07:13 +
with message-id 
and subject line Bug#871465: fixed in gpgme1.0 1.9.0-3
has caused the Debian Bug report #871465,
regarding python3-gpg package should ship tofu module
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.)


-- 
871465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dput
Version: 1.0.0
Severity: serious
Justification: Policy 7.2

Dear Maintainer,

When running version 1.0.0 of dput, I receive the following error:

"""
Traceback (most recent call last):
  File "/usr/bin/dput", line 11, in 
load_entry_point('dput==1.0.0', 'console_scripts', 'execute-dput')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
564, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2662, in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2316, in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2322, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/dput/dput/dput.py", line 28, in 
from . import crypto
  File "/usr/share/dput/dput/crypto.py", line 14, in 
import gpg
  File "/usr/lib/python3/dist-packages/gpg/__init__.py", line 101, in

from . import core
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 36, in 
from . import constants
  File "/usr/lib/python3/dist-packages/gpg/constants/__init__.py", line
28, in 
from . import data, keylist, sig, tofu # The subdirs.
ImportError: cannot import name 'tofu'
"""

The package seems to require python3-tofu, which doesn't seem to be packaged in 
Debian currently.

Thanks for taking care of this package,

-Jonathan


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

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

Versions of packages dput depends on:
ii  python33.5.3-3
ii  python3-debian 0.1.30
ii  python3-gpg1.9.0-2
ii  python3-pkg-resources  36.2.7-1

dput recommends no packages.

Versions of packages dput suggests:
ii  lintian 2.5.52
pn  mini-dinstall   
ii  openssh-client  1:7.5p1-5
ii  rsync   3.1.2-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gpgme1.0
Source-Version: 1.9.0-3

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gpgme1.0 
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, 17 Aug 2017 22:16:47 -0400
Source: gpgme1.0
Binary: libgpgme-dev libgpgme11 python3-gpg python-gpg libqgpgme7 libgpgmepp6 
libgpgmepp-dev libgpgmepp-doc
Architecture: source
Version: 1.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 libgpgme-dev - GPGME - GnuPG Made Easy (development files)
 libgpgme11 - GPGME - GnuPG Made Easy (library)
 libgpgmepp-dev - C++ and Qt bindings for GPGME (development files)
 libgpgmepp-doc - C++ and Qt bindings for GPGME (documentation for developers)
 libgpgmepp6 - C++ wrapper library for GPGME
 libqgpgme7 - library for GPGME integration with Qt
 python-gpg - Python interface to the GPGME GnuPG encryption library (Python 2)
 python3-gpg - Python interface to the GPGME GnuPG encryption library 

Bug#871904: closing 871904

[Daniel Kahn Gillmor]

close 871904 2.1.23-2
thanks

Processed: closing 871904

[Debian Bug Tracking System]

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

> close 871904 2.1.23-2
Bug #871904 [src:gnupg2] gnupg2 FTBFS: 171 tests run, 168 succeeded, 2 failed, 
0 failed expectedly, 0 succeeded unexpectedly, 1 skipped.
Marked as fixed in versions gnupg2/2.1.23-2.
Bug #871904 [src:gnupg2] gnupg2 FTBFS: 171 tests run, 168 succeeded, 2 failed, 
0 failed expectedly, 0 succeeded unexpectedly, 1 skipped.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#871199: pysodium: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Christopher Hoskin]

Package: src:pysodium
Version: 0.6.14-1
Followup-For: Bug #871199

Dear Lucas,

Thanks for the bug report. This was a bug in 0.6.11-1, I beleive it is fixed in 
0.6.14-1.

Unfortunately I didn't spot this bug report before I uploaded 0.6.14-1, so it 
isn't referenced in the changelog.

Christopher

Bug#871199: marked as done (pysodium: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 03:40:05 +0100
with message-id <150302400507.4170.12872109720554233368.report...@tx100-s3p.lan>
and subject line Re: pysodium: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
has caused the Debian Bug report #871199,
regarding pysodium: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 
2.7 returned exit code 13
to be marked as done.

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

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


-- 
871199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysodium
Version: 0.6.11-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.6 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_pysodium.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> creating /<>/.pybuild/pythonX.Y_2.7/build/pysodium
> copying pysodium/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysodium
> I: pybuild base:184: /usr/bin/python3.6 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.6/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_3.6/build/test
> copying test/test_pysodium.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/test
> creating /<>/.pybuild/pythonX.Y_3.6/build/pysodium
> copying pysodium/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pysodium
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/test
> copying test/test_pysodium.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/test
> creating /<>/.pybuild/pythonX.Y_3.5/build/pysodium
> copying pysodium/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/pysodium
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m unittest discover -v 
> test_AsymCrypto_With_Seeded_Keypair (test.test_pysodium.TestPySodium) ... ok
> test_aead_chacha20poly1305 (test.test_pysodium.TestPySodium) ... ok
> test_aead_chacha20poly1305_detached (test.test_pysodium.TestPySodium) ... ok
> test_aead_chacha20poly1305_ietf (test.test_pysodium.TestPySodium) ... ok
> test_crypto_auth (test.test_pysodium.TestPySodium) ... ok
> test_crypto_blake2b (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_open (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_open_afternm (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_open_detached (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_pk_from_sk (test.test_pysodium.TestPySodium) ... ok
> test_crypto_box_seal (test.test_pysodium.TestPySodium) ... ok
> test_crypto_generichash (test.test_pysodium.TestPySodium) ... *** Error in 
> `python2.7': double free or corruption (!prev): 0x561176470750 ***
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f688c0c1bfb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f688c0c7fc6]
> /lib/x86_64-linux-gnu/libc.so.6(+0x7780e)[0x7f688c0c880e]
> /usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(+0x11a03)[0x7f688bb7ea03]
> python2.7(+0x138243)[0x5611757bc243]
> python2.7(PyEval_EvalFrameEx+0x60c1)[0x561175789671]
> python2.7(PyEval_EvalFrameEx+0x5e5f)[0x56117578940f]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a5c8)[0x56117579e5c8]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(PyEval_EvalFrameEx+0x2eeb)[0x56117578649b]
> python2.7(PyEval_EvalCodeEx+0x255)[0x561175781da5]
> python2.7(+0x11a40e)[0x56117579e40e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x12fd7e)[0x5611757b3d7e]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> python2.7(+0x19071b)[0x56117581471b]
> python2.7(PyObject_Call+0x43)[0x561175770163]
> 

Processed: Bug#871465 marked as pending

[Debian Bug Tracking System]

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

> tag 871465 pending
Bug #871465 [python3-gpg] python3-gpg package should ship tofu module
Bug #871609 [python3-gpg] python3-gpg package should ship tofu module
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871465: marked as pending

[Daniel Kahn Gillmor]

tag 871465 pending
thanks

Hello,

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

https://anonscm.debian.org/cgit/pkg-gnupg/gpgme.git/commit/?id=b5f7cb1

---
commit b5f7cb174d80d3e252f947d6790f3e01f91ffa9e
Author: Daniel Kahn Gillmor 
Date:   Thu Aug 17 22:17:18 2017 -0400

prepare debian release

diff --git a/debian/changelog b/debian/changelog
index 3958fa8..4bc0875 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+gpgme1.0 (1.9.0-3) unstable; urgency=medium
+
+  * imported cleanup+bugfixes from upstream
+  * removed unnecessary b-d on autoreconf
+  * drop unneeded DEBIAN_VERSION from debian/rules
+  * ship constants.tofu (Closes: #871465)
+  * Standards-Version: bump to 4.0.1 (extra -> optional)
+  * try to force python 3.6
+  * strip debian revision from new 1.9.0 symbols
+  * add the simplest possible python burn-in autopkgtest
+  * release to unstable
+
+ -- Daniel Kahn Gillmor   Thu, 17 Aug 2017 22:16:47 
-0400
+
 gpgme1.0 (1.9.0-2) experimental; urgency=medium
 
   * Remove Jose Carlos Garcia Sogo from Uploaders (Closes: #862622)

Processed: Re: [pkg-gnupg-maint] Bug#871465: dput seems to miss a dependency on python3-tofu

[Debian Bug Tracking System]

Processing control commands:

> retitle 871465 python3-gpg package should ship tofu module
Bug #871465 [python3-gpg] python3-gpg: depends on, but does not install, ‘tofu’ 
module
Bug #871609 [python3-gpg] python3-gpg: depends on, but does not install, ‘tofu’ 
module
Changed Bug title to 'python3-gpg package should ship tofu module' from 
'python3-gpg: depends on, but does not install, ‘tofu’ module'.
Changed Bug title to 'python3-gpg package should ship tofu module' from 
'python3-gpg: depends on, but does not install, ‘tofu’ module'.

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

Bug#871465: [pkg-gnupg-maint] Bug#871465: dput seems to miss a dependency on python3-tofu

[Daniel Kahn Gillmor]

Control: retitle 871465 python3-gpg package should ship tofu module

On Tue 2017-08-08 12:51:59 +0300, Adrian Bunk wrote:
> On Tue, Aug 08, 2017 at 03:11:40AM -0400, Jonathan Carter wrote:
>>...
>>   File "/usr/lib/python3/dist-packages/gpg/constants/__init__.py", line
>> 28, in 
>> from . import data, keylist, sig, tofu # The subdirs.
>> ImportError: cannot import name 'tofu'
>> """
>>...
>> Versions of packages dput depends on:
>>...
>> ii  python3-gpg1.9.0-2
>>...
>
> This is a bug in the python3-gpg package in experimental.
>
> tofu is part of gpgme and should be shipped in python3-gpg.

  --dkg

Bug#790222: [boinc_dev] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[Olly Betts]

On Thu, Aug 17, 2017 at 05:34:02PM -0400, Jeremy Bicha wrote:
> > But as I've said already, I don't have a problem with just disabling
> > webview before buster if it comes to it.  It just seems unhelpful to
> > boinc users running testing to do that right now, unless you're actually
> > at the point of removing the old webkitgtk from testing.
> 
> Removal of webkitgtk from testing is still a few weeks away.

There's been a bit of progress on the wx+GTK3 front - most notably wx
upstream have now fixed all the bugs I spotted in my initial testing
with a couple of applications.

However, I don't think we're very close to starting a transition to
wx+GTK3 at this point, so probably we need to decide what to do with
boinc.  The options for the short term seem to be:

* Remove boinc from testing and break it in unstable (which is clearly
  not helpful for anyone wanting to use it and running either).

* Drop the use of wx webview in boinc, which doesn't render it entirely
  unusable, but isn't great.

* Patch boinc to use wxHtmlWindow instead, which has more simplistic
  rendering, but is probably OK if there's not Javascript or CSS
  involved.  I've no idea how much work that would be, or if boinc
  upstream has done any work towards this.

* Upload parallel packages of wx+GTK3 for boinc to use.  I have started
  work on packaging, but it needs more work so that parallel installs
  work properly.  I'm also hesitant to take this approach without a firm
  plan to actually do the transition, as I don't think we have the
  resources to adequately maintain two sets of wx packages (historically
  we've tried this, and one set just ended up neglected).

> But in my opinion, this is the last package blocking removal of
> webkitgtk from Ubuntu 17.10. Removal there is also probably a few
> weeks away since many Ubuntu removals happen late in Ubuntu's release
> cycle.)

I'm sure Ubuntu can make that decision for themselves.

Cheers,
Olly

Bug#847642: marked as done (node-uglify: neither manpage nor --help output useful)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 23:20:31 +
with message-id 
and subject line Bug#847642: fixed in uglifyjs 2.8.29-2
has caused the Debian Bug report #847642,
regarding node-uglify: neither manpage nor --help output useful
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.)


-- 
847642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-uglify
Version: 2.7.4-1
Severity: normal

The command ‘uglifyjs’ has a manual page ‘uglifyjs(1)’ that does not
helpfully describe the command:

NAME
   uglify-js - manual page for uglify-js 2.7.5

DESCRIPTION
   [object Object]

The manual page should have the sections described ‘man-pages(7)’ §
“Sections within a manual page”, with the content as described in that
document.

-- 
 \   “Following fashion and the status quo is easy. Thinking about |
  `\your users' lives and creating something practical is much |
_o__)harder.” —Ryan Singer, 2008-07-09 |
Ben Finney 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: uglifyjs
Source-Version: 2.8.29-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uglifyjs 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, 18 Aug 2017 01:00:38 +0200
Source: uglifyjs
Binary: node-uglify libjs-uglify
Architecture: source
Version: 2.8.29-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 libjs-uglify - UglifyJS in library form
 node-uglify - JavaScript parser, mangler/compressor and beautifier toolkit
Closes: 847642
Changes:
 uglifyjs (2.8.29-2) unstable; urgency=medium
 .
   [ Bastien Roucariès ]
   * Fix render help output.
 Closes: #847642). Thanks to Ben Finney.
 .
   [ Jonas Smedegaard ]
   * Declare compliance with Debian Policy 4.0.1.
   * Rename patch to follow naming micro policy.
   * Add DEP-3 patch header.
   * Advertise DEP3 format in patch headers.
Checksums-Sha1:
 3198d58efa6bbd168a92c46fafaf1d28afb389aa 2173 uglifyjs_2.8.29-2.dsc
 c9a19bbd0bd9b4692cbc0563e6bbed5e1c99cc16 10384 uglifyjs_2.8.29-2.debian.tar.xz
 19a77ee7db1a044187cb53cb373e3dc8dad8a3b1 9081 uglifyjs_2.8.29-2_amd64.buildinfo
Checksums-Sha256:
 4e9a849a0c02bd6fa052032d30cbfbaed2d44b4ee7a5a60f6babfa8e1c60715a 2173 
uglifyjs_2.8.29-2.dsc
 e4c6ed6e5ca6403d1bbb9bbeb2242977116a72687c829f623117db4236db7d15 10384 
uglifyjs_2.8.29-2.debian.tar.xz
 e697f3033a8f6b44d095c8c07bd79c9f4007d13b868c7be2ed70f62e36d524b5 9081 
uglifyjs_2.8.29-2_amd64.buildinfo
Files:
 9e59e887c9bef7d0e134ec388cef4484 2173 web optional uglifyjs_2.8.29-2.dsc
 b31ca5982523a5bf6ee637cdb03bb024 10384 web optional 
uglifyjs_2.8.29-2.debian.tar.xz
 8d02fda74e9f899d038ba5c55358106c 9081 web optional 
uglifyjs_2.8.29-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmWIV4ACgkQLHwxRsGg
ASF9hQ//chwRjDPkbgWLh9hlRziCQydDNjevn8fop9Bm9l27PA3N6lzc99PLrDRD
UHQSD99XhMhhU2jKydaBF3mMoySHUkMEd8IWkGz7OpnOlkah7QtRq7AiZ1Val1w9
KDuK024ROvUqh2dH2XNyJP8Eb/pY9p1C7AUQpqOwr2gWcjRY5cwcbj8bCqA4O3eP
IqxKG+oR1Z+XkrYkP4M4cmPnRQcm+sgVUzjQzVbX7tH0GPg/s/f3HPITPlsbH9t1
GGOvqErmQJtX08p0xwKugJiCOqzI5z042DF0ocXB8LfLZEUiGQGZY0laFS/W5HOd
UdP70oeJh1iQEBr62Twx0pMXhNZkySToEoj10j5UEhN+Got/uGrQd8BvrJBW84Yj
aDfKlZeeRBplpmgXu/I9d6F8Pa/Fmya+u+5fV0mjgnx7azWbDbPp+7u2xD0+cwmS
rfQSSB7MZ+Beu+X8uPD/pq14uwi67X2+l3HFRshbd5koHXR5esHIfgc9w/uH41No
xZ3otrWY+sygM5YxSM+mC4+IKyFgJjI7+jl6ST78nQEoSdsGhKyfxNH7AdjSHrsv
sEVTXWdG3psLwFHB/XLUPddTwyuPrEeRrzHsf6P1ugWbEM7suEtdUpUZNbEdie6B
fQjuD8Vbgqyl1o+q/X1mE00DEJh9VJS+CUwToAZbavLUjXcVD7Y=
=v3/O
-END PGP SIGNATURE End Message ---

Bug#853408: marked as done (funguloids: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 23:19:28 +
with message-id 
and subject line Bug#853408: fixed in funguloids 1.06-13
has caused the Debian Bug report #853408,
regarding funguloids: ftbfs with GCC-7
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.)


-- 
853408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:funguloids
Version: 1.06-12
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/funguloids_1.06-12_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
   ~^~~~
mpak.cpp:308:9: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
fread(files[f], 1, len, fpointer);

~^~~~
mpak.cpp:310:9: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
fread([f], sizeof(offsets[f]), 1, fpointer);

~^~
mpak.cpp: In member function 'int MPAK_FILE::extract_file(const char*, const 
char*)':
mpak.cpp:540:8: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
   fread(buffer, 1, bytes_left, fin);

   ~^~~~
game.cpp: In member function 'void GameApplication::endGame()':
game.cpp:255:61: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   int place = hiscoreList.addName("zzz", mPlayer->getScore());

 ^
mp3stream.cpp: In member function 'int MP3Stream::load(const string&)':
mp3stream.cpp:191:10: warning: ignoring return value of 'size_t fread(void*, 
size_t, size_t, FILE*)', declared with attribute warn_unused_result 
[-Wunused-result]
 fread( mMemoryFile.dataPtr, 1, size, fh);
 ~^~~
oggstream.cpp: In member function 'int OggStream::load(const string&)':
oggstream.cpp:129:10: warning: ignoring return value of 'size_t fread(void*, 
size_t, size_t, FILE*)', declared with attribute warn_unused_result 
[-Wunused-result]
 fread( mOggMemoryFile.dataPtr, 1, size, fh);
 ~^~
hiscore.cpp: In member function 'void HiscoreList::load(const String&)':
hiscore.cpp:163:8: warning: ignoring return value of 'size_t fread(void*, 
size_t, size_t, FILE*)', declared with attribute warn_unused_result 
[-Wunused-result]
   fread([f].score, sizeof(long), 1, fin);

   ~^~~
hiscore.cpp:167:8: warning: ignoring return value of 'size_t fread(void*, 
size_t, size_t, FILE*)', declared with attribute warn_unused_result 
[-Wunused-result]
   fread(mList[f].name, NAME_LEN, 1, fin);

   ~^
g++ -I/usr/include/ois -pthread -I/usr/include/OGRE/Overlay -I/usr/include/OGRE 
 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -L/lib -Wl,-z,relro -Wl,-z,defs -Wl,-O1 
-Wl,--as-needed  -L/lib -L/lib -o funguloids funguloids-asteroid.o 
funguloids-ballworm.o funguloids-base.o funguloids-bground.o 
funguloids-blackhole.o funguloids-effects.o funguloids-fmodexsoundsystem.o 
funguloids-gamecamera.o 

Bug#847643: marked as done (node-uglify: neither manpage nor --help output useful)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 23:20:31 +
with message-id 
and subject line Bug#847642: fixed in uglifyjs 2.8.29-2
has caused the Debian Bug report #847642,
regarding node-uglify: neither manpage nor --help output useful
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.)


-- 
847642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-uglify
Version: 2.7.4-1
Severity: normal

The ‘uglifyjs --help’ output is not helpful for learning to use the command:

$ uglifyjs --help
[object Object]

Conventionally that should produce a usage message that tells the
reader what the command does, and all the ways to invoke the program,
with descriptions of all possible arbuments and options.

$ uglifyjs --help
Usage: uglifyjs --foo --bar COLOR --baz INFILE OUTFILE
Obfuscate the infile to the outfile with a snargle snorgle.

INFILE
The input file to obfuscate.

OUTFILE
The obfuscated output.

Options:
--foo
Obfuscate upside down.
--bar COLOR
Turn the output to COLOR.
(default: green)
--baz
Hum gently while working.


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

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

Versions of packages node-uglify depends on:
ii  node-async  0.8.0-1
ii  node-yargs  6.4.0-2
ii  nodejs  4.6.1~dfsg-1

Versions of packages node-uglify recommends:
ii  node-source-map  0.5.6+dfsg-1

Versions of packages node-uglify suggests:
pn  node-uglify-to-browserify  

-- no debconf information

-- 
 \   “It's easy to play any musical instrument: all you have to do |
  `\   is touch the right key at the right time and the instrument |
_o__)will play itself.” —Johann Sebastian Bach |
Ben Finney 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: uglifyjs
Source-Version: 2.8.29-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uglifyjs 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, 18 Aug 2017 01:00:38 +0200
Source: uglifyjs
Binary: node-uglify libjs-uglify
Architecture: source
Version: 2.8.29-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 libjs-uglify - UglifyJS in library form
 node-uglify - JavaScript parser, mangler/compressor and beautifier toolkit
Closes: 847642
Changes:
 uglifyjs (2.8.29-2) unstable; urgency=medium
 .
   [ Bastien Roucariès ]
   * Fix render help output.
 Closes: #847642). Thanks to Ben Finney.
 .
   [ Jonas Smedegaard ]
   * Declare compliance with Debian Policy 4.0.1.
   * Rename patch to follow naming micro policy.
   * Add DEP-3 patch header.
   * Advertise DEP3 format in patch headers.
Checksums-Sha1:
 3198d58efa6bbd168a92c46fafaf1d28afb389aa 2173 uglifyjs_2.8.29-2.dsc
 c9a19bbd0bd9b4692cbc0563e6bbed5e1c99cc16 10384 uglifyjs_2.8.29-2.debian.tar.xz
 19a77ee7db1a044187cb53cb373e3dc8dad8a3b1 9081 uglifyjs_2.8.29-2_amd64.buildinfo
Checksums-Sha256:
 4e9a849a0c02bd6fa052032d30cbfbaed2d44b4ee7a5a60f6babfa8e1c60715a 2173 
uglifyjs_2.8.29-2.dsc
 e4c6ed6e5ca6403d1bbb9bbeb2242977116a72687c829f623117db4236db7d15 10384 
uglifyjs_2.8.29-2.debian.tar.xz
 e697f3033a8f6b44d095c8c07bd79c9f4007d13b868c7be2ed70f62e36d524b5 9081 
uglifyjs_2.8.29-2_amd64.buildinfo
Files:
 9e59e887c9bef7d0e134ec388cef4484 2173 web optional uglifyjs_2.8.29-2.dsc
 

Bug#872485: marked as done (vdr-plugin-epgsearch FTBFS with vdr 2.3.8)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 22:49:36 +
with message-id 
and subject line Bug#872485: fixed in vdr-plugin-epgsearch 2.2.0+git20170817-1
has caused the Debian Bug report #872485,
regarding vdr-plugin-epgsearch FTBFS with vdr 2.3.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.)


-- 
872485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-epgsearch
Version: 1.0.1~beta6+git20150211-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-epgsearch.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c  -DSENDMAIL='"/usr/sbin/sendmail"' -DPLUGIN_NAME_I18N='"epgsearch"'  -o 
blacklist.o blacklist.c
blacklist.c: In constructor 'cBlacklist::cBlacklist()':
blacklist.c:50:18: error: 'Channels' was not declared in this scope
 channelMin = Channels.GetByNumber(cDevice::CurrentChannel());
  ^~~~
blacklist.c:50:18: note: suggested alternative: 'kChannels'
 channelMin = Channels.GetByNumber(cDevice::CurrentChannel());
  ^~~~
  kChannels
blacklist.c: In member function 'bool cBlacklist::Parse(const char*)':
blacklist.c:334:17: error: 'Channels' was not declared in this scope
channelMin = 
Channels.GetByChannelID(tChannelID::FromString(channelMinbuffer), true, true);
 ^~~~
blacklist.c:334:17: note: suggested alternative: 'kChannels'
channelMin = 
Channels.GetByChannelID(tChannelID::FromString(channelMinbuffer), true, true);
 ^~~~
 kChannels
blacklist.c: In member function 'cEvent* cBlacklist::GetEventByBlacklist(const 
cSchedule*, const cEvent*, int)':
blacklist.c:521:37: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   p1 = schedules->Events()->Next(Start);
~^~~
blacklist.c:523:38: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   p1 = schedules->Events()->First();
~~^~
blacklist.c:548:56: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   for (cEvent *p = p1; p; p = schedules->Events()->Next(p))
   ~^~~
blacklist.c: In member function 'cSearchResults* 
cBlacklist::Run(cSearchResults*, int)':
blacklist.c:636:5: error: 'cSchedulesLock' was not declared in this scope
 cSchedulesLock schedulesLock;
 ^~
blacklist.c:636:5: note: suggested alternative: 'cSchedules_Lock'
 cSchedulesLock schedulesLock;
 ^~
 cSchedules_Lock
blacklist.c:638:29: error: 'Schedules' is not a member of 'cSchedules'
 schedules = cSchedules::Schedules(schedulesLock);
 ^
blacklist.c:638:39: error: 'schedulesLock' was not declared in this scope
 schedules = cSchedules::Schedules(schedulesLock);
   ^
blacklist.c:638:39: note: suggested alternative: 'cSchedules_Lock'
 schedules = cSchedules::Schedules(schedulesLock);
   ^
   cSchedules_Lock
blacklist.c:647:22: error: 'Channels' was not declared in this scope
  cChannel* channel = Channels.GetByChannelID(Schedule->ChannelID(),true,true);
  ^~~~
blacklist.c:647:22: note: suggested alternative: 'kChannels'
  cChannel* channel = Channels.GetByChannelID(Schedule->ChannelID(),true,true);
  ^~~~
  kChannels
blacklist.c: In member function 'int cBlacklists::GetNewID()':
blacklist.c:740:10: error: 'max' was not declared in this scope
  newID = max(newID, l->ID);
  ^~~
blacklist.c:740:10: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from blacklist.c:24:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
Makefile:193: recipe for target 'blacklist.o' failed
make[1]: *** [blacklist.o] Error 1
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-epgsearch
Source-Version: 2.2.0+git20170817-1

We believe that the bug you reported is fixed in the latest version of

Bug#853488: marked as done (libclaw: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 23:37:08 +0200
with message-id <996b9f3e-1669-f69e-2eb8-12cc72334...@debian.org>
and subject line Re: libclaw: ftbfs with GCC-7
has caused the Debian Bug report #853488,
regarding libclaw: ftbfs with GCC-7
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.)


-- 
853488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libclaw
Version: 1.7.4-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libclaw_1.7.4-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
/usr/bin/ar qc libclaw_configuration_file.a  
CMakeFiles/claw_configuration_file-static.dir/claw/code/configuration_file.cpp.o
/usr/bin/ar qc libclaw_tween.a  
CMakeFiles/claw_tween-static.dir/claw/code/tween/base_tweener.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/single_tweener.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/tweener.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/tweener_group.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/tweener_sequence.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_circ.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_none.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_linear.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_elastic.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_quint.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_cubic.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_back.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_quad.cpp.o 
CMakeFiles/claw_tween-sta
 tic.dir/claw/code/tween/easing/easing_sine.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_quart.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_bounce.cpp.o 
CMakeFiles/claw_tween-static.dir/claw/code/tween/easing/easing_expo.cpp.o
/usr/bin/ranlib libclaw_configuration_file.a
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/ranlib libclaw_tween.a
[ 85%] Built target claw_configuration_file-static
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_symlink_library libclaw_configuration_file.so.1.7.4 
libclaw_configuration_file.so.1 libclaw_configuration_file.so
[ 85%] Built target claw_tween-static
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 85%] Built target claw_configuration_file
/<>/claw/claw.hpp:99: warning: unable to resolve reference to 
`tweeners' for \ref command
/<>/claw/tween/base_tweener.hpp:41: warning: unable to resolve 
reference to `tweeners' for \ref command
/<>/claw/tween/single_tweener.hpp:44: warning: unable to resolve 
reference to `tweeners' for \ref command
/<>/claw/tween/tweener.hpp:44: warning: unable to resolve 
reference to `tweeners' for \ref command
/<>/claw/tween/tweener_group.hpp:44: warning: unable to resolve 
reference to `tweeners' for \ref command
/<>/claw/tween/tweener_sequence.hpp:46: warning: unable to resolve 
reference to `tweeners' for \ref command
sh: 1: latex: not found
error: Problems running latex. Check your installation or look for typos in 
_formulas.tex and check _formulas.log!
sh: 1: dvips: not found
error: Problems running dvips. Check your installation!
[ 86%] Linking CXX static library libclaw_application.a
/usr/bin/cmake -P 

Bug#790222: [boinc_dev] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

> But as I've said already, I don't have a problem with just disabling
> webview before buster if it comes to it.  It just seems unhelpful to
> boinc users running testing to do that right now, unless you're actually
> at the point of removing the old webkitgtk from testing.

Removal of webkitgtk from testing is still a few weeks away.

But in my opinion, this is the last package blocking removal of
webkitgtk from Ubuntu 17.10. Removal there is also probably a few
weeks away since many Ubuntu removals happen late in Ubuntu's release
cycle.)

Thanks,
Jeremy Bicha

Bug#872506: profitbricks-sdk-python FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 11333: ordinal not in range(128)

[Adrian Bunk]

Source: profitbricks-sdk-python
Version: 4.1.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/profitbricks-sdk-python.html

...
I: pybuild base:184: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 48, in 
long_desc = read('README.md')
  File "setup.py", line 35, in read
return codecs.open(os.path.join(here, *parts), 'r').read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 11333: 
ordinal not in range(128)
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p "3.6 3.5" returned exit 
code 13
debian/rules:6: recipe for target 'clean' failed
make: *** [clean] Error 25

Bug#853546: marked as done (mgba: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 21:08:05 +
with message-id 
and subject line Bug#853546: fixed in mgba 0.5.2+dfsg1-3
has caused the Debian Bug report #853546,
regarding mgba: ftbfs with GCC-7
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.)


-- 
853546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mgba
Version: 0.5.2+dfsg1-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mgba_0.5.2+dfsg1-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 is_function
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.h:202:13: error: 
'function' is not a member of 'std'
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.h:202:13: note: 
suggested alternative: 'is_function'
  QList m_resetActions;
 ^~~~
 is_function
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.h:202:28: error: 
template argument 1 is invalid
  QList m_resetActions;
^
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.h:202:29: error: 
expected unqualified-id before '>' token
  QList m_resetActions;
 ^~
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.cpp: In lambda 
function:
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.cpp:152:34: 
error: 'class QGBA::GameController' has no member named 'm_resetActions'; did 
you mean 'm_useBios'?
   for (auto action : controller->m_resetActions) {
  ^~
  m_useBios
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.cpp:155:15: 
error: 'class QGBA::GameController' has no member named 'm_resetActions'; did 
you mean 'm_useBios'?
   controller->m_resetActions.clear();
   ^~
   m_useBios
qt/CMakeFiles/mgba-qt.dir/build.make:524: recipe for target 
'qt/CMakeFiles/mgba-qt.dir/IOViewer.cpp.o' failed
make[3]: *** [qt/CMakeFiles/mgba-qt.dir/IOViewer.cpp.o] Error 1
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.cpp: In member 
function 'void QGBA::GameController::loadSave(const QString&, bool)':
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.cpp:473:2: error: 
'm_resetActions' was not declared in this scope
  m_resetActions.append([this, path, temporary]() {
  ^~
qt/CMakeFiles/mgba-qt.dir/build.make:740: recipe for target 
'qt/CMakeFiles/mgba-qt.dir/MemoryView.cpp.o' failed
make[3]: *** [qt/CMakeFiles/mgba-qt.dir/MemoryView.cpp.o] Error 1
/<>/mgba-0.5.2+dfsg1/src/platform/qt/GameController.cpp:473:2: note: 
suggested alternative: 'm_useBios'
  m_resetActions.append([this, path, temporary]() {
  ^~
  m_useBios
qt/CMakeFiles/mgba-qt.dir/build.make:452: recipe for target 
'qt/CMakeFiles/mgba-qt.dir/GameController.cpp.o' failed
make[3]: *** [qt/CMakeFiles/mgba-qt.dir/GameController.cpp.o] Error 1
qt/CMakeFiles/mgba-qt.dir/build.make:644: recipe for target 
'qt/CMakeFiles/mgba-qt.dir/LoadSaveState.cpp.o' failed
make[3]: *** [qt/CMakeFiles/mgba-qt.dir/LoadSaveState.cpp.o] Error 1
qt/CMakeFiles/mgba-qt.dir/build.make:836: recipe for target 
'qt/CMakeFiles/mgba-qt.dir/PaletteView.cpp.o' failed
make[3]: *** [qt/CMakeFiles/mgba-qt.dir/PaletteView.cpp.o] Error 1
make[3]: Leaving directory '/<>/mgba-0.5.2+dfsg1/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:256: recipe for target 

Processed: affects

[Debian Bug Tracking System]

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

> affects 872201 piuparts.debian.org
Bug #872201 [libc-bin] libc-bin: sometimes throws std::logic_error while 
processing triggers
Added indication that 872201 affects piuparts.debian.org
> thanks
Stopping processing here.

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

Bug#872497: vdr-plugin-games FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-games
Version: 0.6.3-46
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-games.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -DVERSION=\"0.6.3\" -D_GNU_SOURCE -DVDRVERSNUM=20308 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  
-I/usr/include/vdr/include  -I/usr/include/vdr/include -c screen.cpp -o screen.o
screen.cpp: In function 'int Scr::palette(int)':
screen.cpp:90:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
screen->GetBitmap(0)->SetColor(i, PALETTE(i));
   ^
In file included from screen.cpp:8:0:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
Makefile:95: recipe for target 'screen.o' failed
make[3]: *** [screen.o] Error 1

Bug#872496: vdr-plugin-xineliboutput FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-xineliboutput
Version: 1.1.0+cvs20150907-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-xineliboutput.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DVIDEODIR='"/var/lib/video"' 
-DXINELIBOUTPUT_VERSION='"2.0.0-cvs"' -Wall  -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -o 
xineliboutput.o xineliboutput.c
xineliboutput.c:112:1: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 "   (default "LISTEN_PORT_S")\n"
 ^
In file included from xineliboutput.c:35:0:
device.h:126:13: error: 'eVideoSystem' does not name a type
 virtual eVideoSystem GetVideoSystem(void);
 ^~~~
Makefile:241: recipe for target 'xineliboutput.o' failed
make[2]: *** [xineliboutput.o] Error 1

Bug#872495: vdr-plugin-remoteosd FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-remoteosd
Version: 1.0.0-5
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-remoteosd.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"remoteosd"'  -o menu.o menu.c
menu.c: In member function 'bool cRemoteOsdMenu::Open(const char*, short 
unsigned int, const char*)':
menu.c:72:23: error: 'Channels' was not declared in this scope
   cChannel *channel = Channels.GetByNumber(cDevice::CurrentChannel());
   ^~~~
menu.c:72:23: note: suggested alternative: 'cChannels'
   cChannel *channel = Channels.GetByNumber(cDevice::CurrentChannel());
   ^~~~
   cChannels
Makefile:65: recipe for target 'menu.o' failed
make[1]: *** [menu.o] Error 1

Bug#872494: vdr-plugin-skinenigmang FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-skinenigmang
Version: 0.1.2+git20150212-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-skinenigmang.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='"skinenigmang"' -DUSE_PLUGIN_EPGSEARCH 
-DUSE_PLUGIN_MAILBOX -DUSE_PLUGIN_AVARDS -DHAVE_IMAGEMAGICK 
-DRECORDING_COVER='"Cover-Enigma"' -I/usr/include/vdr/include -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/freetype2 enigma.c
In file included from enigma.c:36:0:
services/epgsearch.h:164:12: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
   std::auto_ptr handler;
^~~~
In file included from /usr/include/c++/7/bits/locale_conv.h:41:0,
 from /usr/include/c++/7/locale:43,
 from /usr/include/c++/7/iomanip:43,
 from enigma.c:18:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
enigma.c: In member function 'void cSkinEnigmaDisplayChannel::DrawSymbols(const 
cChannel*)':
enigma.c:566:5: error: 'cSchedulesLock' was not declared in this scope
 cSchedulesLock SchedulesLock;
 ^~
enigma.c:566:5: note: suggested alternative: 'cSchedules_Lock'
 cSchedulesLock SchedulesLock;
 ^~
 cSchedules_Lock
enigma.c:567:47: error: 'Schedules' is not a member of 'cSchedules'
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
   ^
enigma.c:567:57: error: 'SchedulesLock' was not declared in this scope
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
 ^
enigma.c:567:57: note: suggested alternative: 'cSchedules_Lock'
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
 ^
 cSchedules_Lock
enigma.c: In constructor 'cSkinEnigmaDisplayMenu::cSkinEnigmaDisplayMenu()':
enigma.c:1379:16: error: 'min' was not declared in this scope
   nMarkerGap = min(MarkerGap, lineHeight / 2 - 1); //lineHeight - 2 * MarkerGap
^~~
enigma.c:1379:16: note: suggested alternative:
In file included from /usr/include/c++/7/bits/char_traits.h:39:0,
 from /usr/include/c++/7/string:40,
 from common.h:11,
 from enigma.c:8:
/usr/include/c++/7/bits/stl_algobase.h:243:5: note:   'std::min'
 min(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
enigma.c: In member function 'void cSkinEnigmaDisplayMenu::SetColors()':
enigma.c:1417:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   if (osd->GetBitmap(1) == NULL) { //single area
   ^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1421:37: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   cBitmap *bitmap = osd->GetBitmap(0);
 ^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1428:28: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   bitmap = osd->GetBitmap(1);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1437:28: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   bitmap = osd->GetBitmap(2);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);

Bug#872493: vdr-plugin-sudoku FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-sudoku
Version: 0.3.5-20
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-sudoku.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-z,relro 
-I/usr/include/vdr/include -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"sudoku"' 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o bitmap.o bitmap.cpp
bitmap.cpp: In member function 'void SudokuPlugin::Bitmap::text(const char*, 
bool)':
bitmap.cpp:54:11: error: 'max' was not declared in this scope
   int y = max((Height() - wrapper.Lines() * font->Height()) / 2, 0);
   ^~~
bitmap.cpp:54:11: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from sudoku.h:29,
 from bitmap.h:24,
 from bitmap.cpp:21:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
: recipe for target 'bitmap.o' failed
make[2]: *** [bitmap.o] Error 1

Bug#872490: vdr-plugin-osdteletext FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-osdteletext
Version: 0.9.5-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-osdteletext.html

...
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-DPLUGIN_NAME_I18N='"osdteletext"'  -o menu.o menu.c
In file included from display.h:19:0,
 from menu.c:18:
displaybase.h: In member function 'int 
cDisplay::GetColorIndex(enumTeletextColor, int)':
displaybase.h:145:40: error: 'cBitmap* cOsd::GetBitmap(int)' is protected 
within this context
 cBitmap *bm=osd->GetBitmap(Area);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from /usr/include/vdr/interface.h:15,
 from menu.c:14:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
In file included from display.h:19:0,
 from menu.c:18:
displaybase.h: In member function 'int 
cDisplay::GetColorIndexAlternate(enumTeletextColor, int)':
displaybase.h:153:40: error: 'cBitmap* cOsd::GetBitmap(int)' is protected 
within this context
 cBitmap *bm=osd->GetBitmap(Area);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from /usr/include/vdr/interface.h:15,
 from menu.c:14:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
menu.c: In member function 'bool TeletextBrowser::CheckIsValidChannel(int)':
menu.c:76:12: error: 'Channels' was not declared in this scope
return (Channels.GetByNumber(number) != 0);
^~~~
menu.c:76:12: note: suggested alternative: 'cChannels'
return (Channels.GetByNumber(number) != 0);
^~~~
cChannels
menu.c: In static member function 'static void 
TeletextBrowser::ChannelSwitched(int)':
menu.c:80:19: error: 'Channels' was not declared in this scope
cChannel *chan=Channels.GetByNumber(ChannelNumber);
   ^~~~
menu.c:80:19: note: suggested alternative: 'cChannels'
cChannel *chan=Channels.GetByNumber(ChannelNumber);
   ^~~~
   cChannels
Makefile:64: recipe for target 'menu.o' failed
make[1]: *** [menu.o] Error 1

Bug#872492: vdr-plugin-spider FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-spider
Version: 0.2.2-21
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-spider.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-z,relro 
-I/usr/include/vdr/include -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"spider"' 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o bitmap.o bitmap.cpp
bitmap.cpp: In member function 'void SpiderPlugin::Bitmap::text(const char*, 
bool)':
bitmap.cpp:77:11: error: 'max' was not declared in this scope
   int y = max((Height() - wrapper.Lines() * font->Height()) / 2, 0);
   ^~~
bitmap.cpp:77:11: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from spider.h:30,
 from bitmap.h:26,
 from bitmap.cpp:23:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
bitmap.cpp: In constructor 'SpiderPlugin::Bitmap::Bitmap(int, int, const char*, 
const char*)':
bitmap.cpp:54:11: warning: ignoring return value of 'int asprintf(char**, const 
char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
   asprintf(, "%s/%s.xpm", dir, name);
   ^~~
bitmap.cpp: In constructor 'SpiderPlugin::Bitmap::Bitmap(int, int, const char*, 
const char*, const char*)':
bitmap.cpp:65:11: warning: ignoring return value of 'int asprintf(char**, const 
char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
   asprintf(, "%s/%s_%s.xpm", dir, suit, rank);
   ^~~~
: recipe for target 'bitmap.o' failed
make[2]: *** [bitmap.o] Error 1

Bug#872491: vdr-plugin-streamdev FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-streamdev
Version: 0.6.1+git20150213-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-streamdev.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"streamdev-client"' -I/include -I.. -o 
filter.o filter.c
filter.c: In member function 'int cStreamdevFilters::OpenFilter(u_short, 
u_char, u_char)':
filter.c:222:2: error: reference to 'Lock' is ambiguous
  Lock();
  ^~~~
In file included from /usr/include/vdr/tools.h:29:0,
 from /usr/include/vdr/i18n.h:14,
 from /usr/include/vdr/config.h:19,
 from ../client/filter.h:8,
 from filter.c:5:
/usr/include/vdr/thread.h:94:8: note: candidates are: void cThread::Lock()
   void Lock(void) { mutex.Lock(); }
^~~~
In file included from /usr/include/vdr/i18n.h:14:0,
 from /usr/include/vdr/config.h:19,
 from ../client/filter.h:8,
 from filter.c:5:
/usr/include/vdr/tools.h:531:8: note: bool 
cListBase::Lock(cStateKey&, bool, int) const
   bool Lock(cStateKey , bool Write = false, int TimeoutMs = 0) const;
^~~~
Makefile:34: recipe for target 'filter.o' failed
make[2]: *** [filter.o] Error 1

Bug#872489: vdr-plugin-femon FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-femon
Version: 2.2.1-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-femon.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"femon"'  -o femon.o femon.c
femon.c: In member function 'virtual cOsdObject* 
cPluginFemon::MainMenuAction()':
femon.c:123:31: error: 'Channels' was not declared in this scope
   if (cControl::Control() || (Channels.Count() <= 0))
   ^~~~
femon.c:123:31: note: suggested alternative: 'kChannels'
   if (cControl::Control() || (Channels.Count() <= 0))
   ^~~~
   kChannels
Makefile:73: recipe for target 'femon.o' failed
make[1]: *** [femon.o] Error 1

Bug#872486: vdr-plugin-epgsync FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-epgsync
Version: 1.0.1-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-epgsync.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"epgsync"'  -o thread.o thread.c
thread.c: In function 'cChannel* GetChannelByName(const char*, const cChannel*, 
eChannelTypes)':
thread.c:47:27: error: 'Channels' was not declared in this scope
  for (cChannel *channel = Channels.First(); channel; channel = 
Channels.Next(channel)) {
   ^~~~
thread.c:47:27: note: suggested alternative: 'kChannels'
  for (cChannel *channel = Channels.First(); channel; channel = 
Channels.Next(channel)) {
   ^~~~
   kChannels
thread.c: In member function 'virtual void cEpgSyncThread::Action()':
thread.c:98:4: error: 'cSchedulesLock' was not declared in this scope
cSchedulesLock *lock = NULL;
^~
thread.c:98:4: note: suggested alternative: 'cSchedules_Lock'
cSchedulesLock *lock = NULL;
^~
cSchedules_Lock
thread.c:98:20: error: 'lock' was not declared in this scope
cSchedulesLock *lock = NULL;
^~~~
thread.c:98:20: note: suggested alternative: 'Lock'
cSchedulesLock *lock = NULL;
^~~~
Lock
thread.c:99:29: error: 'Channels' was not declared in this scope
for (cChannel *channel = Channels.First(); channel && Running();
 ^~~~
thread.c:99:29: note: suggested alternative: 'kChannels'
for (cChannel *channel = Channels.First(); channel && Running();
 ^~~~
 kChannels
thread.c:102:17: error: expected type-specifier before 'cSchedulesLock'
  lock = new cSchedulesLock();
 ^~
thread.c:103:21: error: 'Schedules' is not a member of 'cSchedules'
 if (cSchedules::Schedules(*lock)->GetSchedule(channel)) {
 ^
thread.c: In member function 'bool cEpgSyncThread::CmdLSTE(FILE*, const char*)':
thread.c:185:18: error: 'Channels' was not declared in this scope
cChannel *c = Channels.GetByChannelID(tChannelID::FromString(p));
  ^~~~
thread.c:185:18: note: suggested alternative: 'kChannels'
cChannel *c = Channels.GetByChannelID(tChannelID::FromString(p));
  ^~~~
  kChannels
Makefile:65: recipe for target 'thread.o' failed
make[1]: *** [thread.o] Error 1

Processed: Re: severity of 776567 is serious

[Debian Bug Tracking System]

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

> severity 776567 important
Bug #776567 [src:mclibs] mclibs: FTBFS - segfault in testsuite
Severity set to 'important' from 'serious'
> Thanks
Stopping processing here.

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

Bug#872487: vdr-plugin-infosatepg FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-infosatepg
Version: 0.0.12-6
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-infosatepg.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='"infosatepg"' -I/usr/include/vdr/include 
infosatepg.cpp
infosatepg.cpp: In member function 'virtual bool 
cPluginInfosatepg::Initialize()':
infosatepg.cpp:97:14: error: 'Channels' was not declared in this scope
 if (!Channels.GetByChannelID(ChannelID))
  ^~~~
infosatepg.cpp:97:14: note: suggested alternative: 'kChannels'
 if (!Channels.GetByChannelID(ChannelID))
  ^~~~
  kChannels
infosatepg.cpp: In member function 'virtual void 
cPluginInfosatepg::MainThreadHook()':
infosatepg.cpp:167:20: error: 'Channels' was not declared in this scope
 cChannel *chan=Channels.GetByNumber(global->Channel());
^~~~
infosatepg.cpp:167:20: note: suggested alternative: 'kChannels'
 cChannel *chan=Channels.GetByNumber(global->Channel());
^~~~
kChannels
infosatepg.cpp: In member function 'virtual cString 
cPluginInfosatepg::Active()':
infosatepg.cpp:238:28: error: 'Channels' was not declared in this scope
 cChannel *chan=Channels.GetByNumber(global->LastCurrentChannel);
^~~~
infosatepg.cpp:238:28: note: suggested alternative: 'kChannels'
 cChannel *chan=Channels.GetByNumber(global->LastCurrentChannel);
^~~~
kChannels
Makefile:59: recipe for target 'infosatepg.o' failed
make[2]: *** [infosatepg.o] Error 1

Bug#872485: vdr-plugin-epgsearch FTBFS with vdr 2.3.8

[Adrian Bunk]

Source: vdr-plugin-epgsearch
Version: 1.0.1~beta6+git20150211-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-epgsearch.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c  -DSENDMAIL='"/usr/sbin/sendmail"' -DPLUGIN_NAME_I18N='"epgsearch"'  -o 
blacklist.o blacklist.c
blacklist.c: In constructor 'cBlacklist::cBlacklist()':
blacklist.c:50:18: error: 'Channels' was not declared in this scope
 channelMin = Channels.GetByNumber(cDevice::CurrentChannel());
  ^~~~
blacklist.c:50:18: note: suggested alternative: 'kChannels'
 channelMin = Channels.GetByNumber(cDevice::CurrentChannel());
  ^~~~
  kChannels
blacklist.c: In member function 'bool cBlacklist::Parse(const char*)':
blacklist.c:334:17: error: 'Channels' was not declared in this scope
channelMin = 
Channels.GetByChannelID(tChannelID::FromString(channelMinbuffer), true, true);
 ^~~~
blacklist.c:334:17: note: suggested alternative: 'kChannels'
channelMin = 
Channels.GetByChannelID(tChannelID::FromString(channelMinbuffer), true, true);
 ^~~~
 kChannels
blacklist.c: In member function 'cEvent* cBlacklist::GetEventByBlacklist(const 
cSchedule*, const cEvent*, int)':
blacklist.c:521:37: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   p1 = schedules->Events()->Next(Start);
~^~~
blacklist.c:523:38: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   p1 = schedules->Events()->First();
~~^~
blacklist.c:548:56: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   for (cEvent *p = p1; p; p = schedules->Events()->Next(p))
   ~^~~
blacklist.c: In member function 'cSearchResults* 
cBlacklist::Run(cSearchResults*, int)':
blacklist.c:636:5: error: 'cSchedulesLock' was not declared in this scope
 cSchedulesLock schedulesLock;
 ^~
blacklist.c:636:5: note: suggested alternative: 'cSchedules_Lock'
 cSchedulesLock schedulesLock;
 ^~
 cSchedules_Lock
blacklist.c:638:29: error: 'Schedules' is not a member of 'cSchedules'
 schedules = cSchedules::Schedules(schedulesLock);
 ^
blacklist.c:638:39: error: 'schedulesLock' was not declared in this scope
 schedules = cSchedules::Schedules(schedulesLock);
   ^
blacklist.c:638:39: note: suggested alternative: 'cSchedules_Lock'
 schedules = cSchedules::Schedules(schedulesLock);
   ^
   cSchedules_Lock
blacklist.c:647:22: error: 'Channels' was not declared in this scope
  cChannel* channel = Channels.GetByChannelID(Schedule->ChannelID(),true,true);
  ^~~~
blacklist.c:647:22: note: suggested alternative: 'kChannels'
  cChannel* channel = Channels.GetByChannelID(Schedule->ChannelID(),true,true);
  ^~~~
  kChannels
blacklist.c: In member function 'int cBlacklists::GetNewID()':
blacklist.c:740:10: error: 'max' was not declared in this scope
  newID = max(newID, l->ID);
  ^~~
blacklist.c:740:10: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from blacklist.c:24:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
Makefile:193: recipe for target 'blacklist.o' failed
make[1]: *** [blacklist.o] Error 1

Bug#872438: [Pkg-javascript-devel] Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Bastien ROUCARIES]

On Thu, Aug 17, 2017 at 3:54 PM, Felipe Sateler  wrote:
> Package: src:nodejs
> Version: 6.11.2~dfsg-2
> Severity: serious
>
> nodejs failed to build with this error:
>
> make[1]: Entering directory '/<>'
> # Clean up any leftover processes but don't error if found.
> ps awwx | grep Release/node | grep -v grep | cat
> /usr/bin/python tools/test.py  -p tap \
> --mode=release --flaky-tests=dontcare \
> --arch=mips64el --timeout=3000 message parallel sequential
> Can't determine the arch of: './node'
>
> Can't determine the arch of: './node'
>
> Can't determine the arch of: './node'

The line are :

vm = context.GetVm(arch, mode)
if not exists(vm):
  print "Can't find shell executable: '%s'" % vm
  continue
archEngineContext = Execute([vm, "-p", "process.arch"], context)
vmArch = archEngineContext.stdout.rstrip()
if archEngineContext.exit_code is not 0 or vmArch == "undefined":
  print "Can't determine the arch of: '%s'" % vm
  print archEngineContext.stderr.rstrip()
  continue
env = {
  'mode': mode,
  'system': utils.GuessOS(),
  'arch': vmArch,
}


>
> No tests to run.
> Makefile:220: recipe for target 'test-ci-js' failed
> make[1]: *** [test-ci-js] Error 1
> make[1]: Leaving directory '/<>'
>
>
> Full log at 
> https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=6.11.2~dfsg-2=1502862893=0
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Processed: 5.9.0+dfsg-3 never existed

[Debian Bug Tracking System]

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

> notfixed 869008 5.9.0+dfsg-3
Bug #869008 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
Bug #869016 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871380 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] algobox: FTBFS: build-dependency not 
installable: qtwebengine5-dev
Bug #871387 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qupzilla: FTBFS: build-dependency not 
installable: qtwebengine5-dev
The source 'qtwebengine-opensource-src' and version '5.9.0+dfsg-3' do not 
appear to match any binary packages
Ignoring request to alter fixed versions of bug #869008 to the same values 
previously set
Ignoring request to alter fixed versions of bug #869016 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871064 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871380 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871387 to the same values 
previously set
> fixed 869008 5.9.1+dfsg-3
Bug #869008 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
Bug #869016 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871380 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] algobox: FTBFS: build-dependency not 
installable: qtwebengine5-dev
Bug #871387 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qupzilla: FTBFS: build-dependency not 
installable: qtwebengine5-dev
Ignoring request to alter fixed versions of bug #869008 to the same values 
previously set
Ignoring request to alter fixed versions of bug #869016 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871064 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871380 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871387 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
869016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869016
871064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871064
871380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871380
871387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: 5.9.0+dfsg-3 never existed

[Debian Bug Tracking System]

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

> notfixed 869008 5.9.0+dfsg-3
Bug #869008 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
Bug #869016 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871380 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] algobox: FTBFS: build-dependency not 
installable: qtwebengine5-dev
Bug #871387 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qupzilla: FTBFS: build-dependency not 
installable: qtwebengine5-dev
The source 'qtwebengine-opensource-src' and version '5.9.0+dfsg-3' do not 
appear to match any binary packages
No longer marked as fixed in versions 5.9.0+dfsg-3.
No longer marked as fixed in versions 5.9.0+dfsg-3.
No longer marked as fixed in versions 5.9.0+dfsg-3.
No longer marked as fixed in versions 5.9.0+dfsg-3.
No longer marked as fixed in versions 5.9.0+dfsg-3.
> fixed 869008 5.9.1+dfsg-3
Bug #869008 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
Bug #869016 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871380 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] algobox: FTBFS: build-dependency not 
installable: qtwebengine5-dev
Bug #871387 {Done: Sandro Knauß } 
[src:qtwebengine-opensource-src] qupzilla: FTBFS: build-dependency not 
installable: qtwebengine5-dev
Marked as fixed in versions qtwebengine-opensource-src/5.9.1+dfsg-3.
Marked as fixed in versions qtwebengine-opensource-src/5.9.1+dfsg-3.
Marked as fixed in versions qtwebengine-opensource-src/5.9.1+dfsg-3.
Marked as fixed in versions qtwebengine-opensource-src/5.9.1+dfsg-3.
Marked as fixed in versions qtwebengine-opensource-src/5.9.1+dfsg-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
869016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869016
871064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871064
871380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871380
871387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872481: imagemagick: CVE-2017-12433

[Salvatore Bonaccorso]

Control: severity -1 important
Control: tags -1 upstream fixed-upstream

On Thu, Aug 17, 2017 at 09:33:18PM +0200, Salvatore Bonaccorso wrote:
> Source: imagemagick
> Version: 8:6.9.7.4+dfsg-16
> Severity: grave
> Tags: security

Something went wrong when submitting the report.

Regards,
Salvatore

Processed: Re: Bug#872481: imagemagick: CVE-2017-12433

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #872481 [src:imagemagick] imagemagick: CVE-2017-12433
Severity set to 'important' from 'grave'
> tags -1 upstream fixed-upstream
Bug #872481 [src:imagemagick] imagemagick: CVE-2017-12433
Added tag(s) fixed-upstream and upstream.

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

Bug#872481: imagemagick: CVE-2017-12433

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-16
Severity: grave
Tags: security
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/548

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-12433[0]:
| In ImageMagick 7.0.6-1, a memory leak vulnerability was found in the
| function ReadPESImage in coders/pes.c, which allows attackers to cause
| a denial of service, related to ResizeMagickMemory in memory.c.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12433
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12433
[1] https://github.com/ImageMagick/ImageMagick/issues/548

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



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

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

Bug#853649: gnulib intprops.h build error with gcc 7

[Adrian Bunk]

On Thu, Aug 17, 2017 at 08:40:28PM +0200, Bruno Haible wrote:
>...
> Now about your test case: It is not valid C to try to compile just an
> expression.
>...

I was about to say that this was directly copied from intprops.h

And when double-checking that, I finally realized that this is
what is in intprops.h in rush - but intprops.h in current gnulib
git is fine.

When looking at them I missed that they are different at this relevant 
macro, and that the problem is only in the older intprops.h shipped in 
rush.

Sorry for the confusion
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#872480: [node-acorn] Need depends on nodejs > 6

[Bastien ROUCARIÈS]

Package: node-acorn
Version: 5.0.3-1
Severity: grave

This version use a lot of depends of nodejs > 6

YOu could drop the second patch serie and use an hard depends

acorn fail on testing

Bastien

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

Bug#854272: Zoneminder issues fixed? (was: Re: Bug#854733 tagged as pending)

[Chris Lamb]

Hi Salvatore,

> Will try to schedule a bit of time to check this, or if any other can
> as well would be appreciated. The CSRF vulnerabilities from that list
> probably yes, but not sure about all of the reported CVEs.

Any update on this? :)


Regards,

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

Bug#853649: gnulib intprops.h build error with gcc 7

[Bruno Haible]

Adrian Bunk wrote:
> For reproducing and my tiny testcase I was using
>   gcc (Debian 7.1.0-13) 7.1.0
> from Debian unstable - that is GCC 7.2 release candidate 2
> with minimal Debian patching.

OK thanks.

Now about your test case: It is not valid C to try to compile just an
expression.

   a + b

is not a valid C compilation unit either. Can you submit a small test case
that
1) makes use of the intprops.h file from gnulib as a whole,
2) compiles with gcc 6 or earlier?

Bruno

Bug#864327: marked as done (shiboken: extend test skipping hack to python 3.6)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 18:37:32 +
with message-id 
and subject line Bug#864327: fixed in shiboken 1.2.2-4
has caused the Debian Bug report #864327,
regarding shiboken: extend test skipping hack to python 3.6
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.)


-- 
864327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shiboken
Severity: normal
Tags: patch
User: debian-pyt...@lists.debian.org

Dear Maintainer,

The tests that fail with Python 3.4 and 3.5 also fail with 3.6. I've uploaded
the attached patch to Ubuntu, but perhaps given the overall status of the
package it would be best to just make the hack apply to all Python 3 versions...

Cheers,
mwh

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

Kernel: Linux 4.4.0-78-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru shiboken-1.2.2/debian/changelog shiboken-1.2.2/debian/changelog
--- shiboken-1.2.2/debian/changelog	2017-05-16 03:59:33.0 +
+++ shiboken-1.2.2/debian/changelog	2017-06-07 00:19:48.0 +
@@ -1,3 +1,9 @@
+shiboken (1.2.2-3.1ubuntu1) artful; urgency=medium
+
+  * Extend hack to skip tests which still fail for py3.6. 
+
+ -- Michael Hudson-Doyle   Tue, 06 Jun 2017 17:19:07 -0700
+
 shiboken (1.2.2-3.1build1) artful; urgency=medium
 
   * No change rebuild to add Python 3.6 support.
diff -Nru shiboken-1.2.2/debian/control shiboken-1.2.2/debian/control
--- shiboken-1.2.2/debian/control	2017-04-13 15:22:45.0 +
+++ shiboken-1.2.2/debian/control	2017-06-07 00:20:02.0 +
@@ -1,7 +1,8 @@
 Source: shiboken
 Section: devel
 Priority: optional
-Maintainer: Debian Python Modules Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Python Modules Team 
 Uploaders: Didier Raboud 
 Build-Depends: dpkg-dev (>= 1.15.7), debhelper (>= 9), cmake (>= 2.8.4+dfsg.1-3~),
  libqt4-dev (>= 4:4.7.0),
diff -Nru shiboken-1.2.2/debian/rules shiboken-1.2.2/debian/rules
--- shiboken-1.2.2/debian/rules	2017-04-13 15:22:45.0 +
+++ shiboken-1.2.2/debian/rules	2017-06-07 00:18:52.0 +
@@ -131,6 +131,10 @@
 	# The tests for the other and sample libraries segfault. The same goes for the shiboken_module.
 	dh_auto_test -a --builddirectory=build-3.5-dbg -- ARGS="-E '^(other|sample|shiboken_module)'"
 
+override_dh_auto_test_dbg-3.6:
+	# The tests for the other and sample libraries segfault. The same goes for the shiboken_module.
+	dh_auto_test -a --builddirectory=build-3.5-dbg -- ARGS="-E '^(other|sample|shiboken_module)'"
+
 override_dh_auto_test-%:
 	dh_auto_test -a --builddirectory=build-$*
 
--- End Message ---
--- Begin Message ---
Source: shiboken
Source-Version: 1.2.2-4

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated shiboken 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, 17 Aug 2017 14:59:50 +0200
Source: shiboken
Binary: shiboken shiboken-doc libshiboken1.2v5 libshiboken-py3-1.2v5 
libshiboken-dev shiboken-dbg
Architecture: source
Version: 1.2.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Raphaël Hertzog 
Description:
 libshiboken-dev - development files for the shiboken bindings generator library
 libshiboken-py3-1.2v5 - CPython3 bindings 

Bug#853501: marked as done (libosmocore: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 18:23:02 +
with message-id 
and subject line Bug#853501: fixed in libosmocore 0.9.0-7
has caused the Debian Bug report #853501,
regarding libosmocore: ftbfs with GCC-7
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.)


-- 
853501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libosmocore
Version: 0.9.0-6
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libosmocore_0.9.0-6_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
gb/gprs_ns_test.c:224:28: warning: 'gprs_ns_unblock' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_unblock[1] = {
^~~
gb/gprs_ns_test.c:219:28: warning: 'gprs_ns_alive_ack' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_alive_ack[1] = {
^
gb/gprs_ns_test.c:206:28: warning: 'gprs_ns_alive' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_alive[1] = {
^
gb/gprs_ns_test.c:200:28: warning: 'gprs_ns_reset_nsei2' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_reset_nsei2[12] = {
^~~
gb/gprs_ns_test.c:192:28: warning: 'gprs_ns_reset_vci2' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_reset_vci2[12] = {
^~
gb/gprs_ns_test.c:184:28: warning: 'gprs_ns_reset' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_reset[12] = {
^
/bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
gb/gprs_ns_test gb/gprs_ns_test.o ../src/libosmocore.la ../src/gb/libosmogb.la 
../src/vty/libosmovty.la -ldl  
libtool: link: gcc -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -Wl,--as-needed -o gb/.libs/gprs_ns_test gb/gprs_ns_test.o  
../src/.libs/libosmocore.so ../src/gb/.libs/libosmogb.so 
../src/vty/.libs/libosmovty.so -ldl
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
kasumi/kasumi_test.o kasumi/kasumi_test.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
kasumi/kasumi_test kasumi/kasumi_test.o ../src/libosmocore.la 
../src/gsm/libgsmint.la 
libtool: link: gcc -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -Wl,--as-needed -o kasumi/.libs/kasumi_test kasumi/kasumi_test.o 
 ../src/.libs/libosmocore.so ../src/gsm/.libs/libgsmint.a 
/<>/src/.libs/libosmocore.so -ldl
kasumi/kasumi_test.o: In function `test_expansion':
./tests/kasumi/kasumi_test.c:27: undefined reference to `_compare_mem'
./tests/kasumi/kasumi_test.c:28: undefined reference to `_compare_mem'
./tests/kasumi/kasumi_test.c:29: 

Bug#853308: marked as done (alljoyn-services-1604: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 18:04:24 +
with message-id 
and subject line Bug#853308: fixed in alljoyn-services-1604 16.04-4
has caused the Debian Bug report #853308,
regarding alljoyn-services-1604: ftbfs with GCC-7
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.)


-- 
853308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:alljoyn-services-1604
Version: 16.04-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/alljoyn-services-1604_16.04-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
g++ -o 
build/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ServerSample/generated/MyDeviceStatusStringProperty.o
 -c -std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -Wno-long-long -Wno-deprecated -Wno-unknown-pragmas 
-Wunused-parameter -Os -m64 -fPIC -Wno-deprecated-declarations -fPIE -fPIC 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DNEED_DATA_STORE -D_NOTIFICATION_ 
-D_CONTROLPANEL_ -I/<>/build/linux/x86_64/release/dist/cpp/inc 
-I/<>/build/linux/x86_64/release/dist/cpp/inc/alljoyn 
-Ibuild/linux/x86_64/release/dist/services_common/inc 
-Ibuild/linux/x86_64/release/dist/notification/inc 
-Ibuild/linux/x86_64/release/dist/controlpanel/inc 
-Ibuild/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ServerSample/generated
 -Icpp/samples/ServerSample/generated -Icpp/samples_com
 mon -Icpp/samples/ServerSample/generated -Icpp/samples/ServerSample/provided 
cpp/samples/ServerSample/generated/MyDeviceStatusStringProperty.cc
g++ -o 
build/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ServerSample/generated/MyDeviceTurnFanOff.o
 -c -std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -Wno-long-long -Wno-deprecated -Wno-unknown-pragmas 
-Wunused-parameter -Os -m64 -fPIC -Wno-deprecated-declarations -fPIE -fPIC 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DNEED_DATA_STORE -D_NOTIFICATION_ 
-D_CONTROLPANEL_ -I/<>/build/linux/x86_64/release/dist/cpp/inc 
-I/<>/build/linux/x86_64/release/dist/cpp/inc/alljoyn 
-Ibuild/linux/x86_64/release/dist/services_common/inc 
-Ibuild/linux/x86_64/release/dist/notification/inc 
-Ibuild/linux/x86_64/release/dist/controlpanel/inc 
-Ibuild/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ServerSample/generated
 -Icpp/samples/ServerSample/generated -Icpp/samples_common -Icpp/
 samples/ServerSample/generated -Icpp/samples/ServerSample/provided 
cpp/samples/ServerSample/generated/MyDeviceTurnFanOff.cc
g++ -o 
build/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ServerSample/generated/MyDeviceTurnFanOn.o
 -c -std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -Wno-long-long -Wno-deprecated -Wno-unknown-pragmas 
-Wunused-parameter -Os -m64 -fPIC -Wno-deprecated-declarations -fPIE -fPIC 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DNEED_DATA_STORE -D_NOTIFICATION_ 
-D_CONTROLPANEL_ 

Bug#853307: marked as done (alljoyn-services-1504: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 18:04:06 +
with message-id 
and subject line Bug#853307: fixed in alljoyn-services-1504 15.04-7
has caused the Debian Bug report #853307,
regarding alljoyn-services-1504: ftbfs with GCC-7
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.)


-- 
853307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:alljoyn-services-1504
Version: 15.04-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/alljoyn-services-1504_15.04-5_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
g++ -o 
build/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ACServerSample/generated/MyDeviceStatusStringProperty.o
 -c -Wall -Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -fPIE -fPIC 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-DNEED_DATA_STORE -D_CONFIG_ -DNEED_DATA_STORE -D_NOTIFICATION_ 
-D_CONTROLPANEL_ -Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/services_common/inc 
-Ibuild/linux/x86_64/release/dist/config/inc 
-Ibuild/linux/x86_64/release/dist/notification/inc 
-Ibuild/linux/x86_64/release/dist/controlpanel/inc 
-Ibuild/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ACSer
 verSample/generated -Icpp/samples/ACServerSample/generated 
-Icpp/samples_common -Icpp/samples/ACServerSample/generated 
-Icpp/samples/ACServerSample/provided 
cpp/samples/ACServerSample/generated/MyDeviceStatusStringProperty.cc
g++ -o 
build/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ACServerSample/generated/MyDeviceTurnFanOff.o
 -c -Wall -Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -fPIE -fPIC 
-D_FORTIFY_SOURCE=2 -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-DNEED_DATA_STORE -D_CONFIG_ -DNEED_DATA_STORE -D_NOTIFICATION_ 
-D_CONTROLPANEL_ -Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/services_common/inc 
-Ibuild/linux/x86_64/release/dist/config/inc 
-Ibuild/linux/x86_64/release/dist/notification/inc 
-Ibuild/linux/x86_64/release/dist/controlpanel/inc 
-Ibuild/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ACServerSample/
 generated -Icpp/samples/ACServerSample/generated -Icpp/samples_common 
-Icpp/samples/ACServerSample/generated -Icpp/samples/ACServerSample/provided 
cpp/samples/ACServerSample/generated/MyDeviceTurnFanOff.cc
g++ -o 
build/linux/x86_64/release/obj/services/sample_apps/cpp/samples/ACServerSample/generated/MyDeviceTurnFanOn.o
 -c -Wall -Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas 

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:glm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #870217 (http://bugs.debian.org/870217)
> # Bug title: glm: FTBFS with gcc-7: Test failures
> #  * https://github.com/g-truc/glm/issues/666
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 870217 + fixed-upstream
Bug #870217 [src:glm] glm: FTBFS with gcc-7: Test failures
Added tag(s) fixed-upstream.
> usertags 870217 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 870217 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:nss
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #871691 (http://bugs.debian.org/871691)
> # Bug title: nss FTBFS on big endian: cpputil/databuffer.h:96:14: error: 
> 'curve' may be used uninitialized in this function
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1389263
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 871691 + fixed-upstream
Bug #871691 [src:nss] nss FTBFS on big endian: cpputil/databuffer.h:96:14: 
error: 'curve' may be used uninitialized in this function
Added tag(s) fixed-upstream.
> usertags 871691 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #871700 (http://bugs.debian.org/871700)
> # Bug title: nss 2:3.32-1 on i386 requires SSE2, regression from 2:3.31-1
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1389432
> #  * remote status changed: (?) -> NEW
> usertags 871700 + status-NEW
There were no usertags set.
Usertags are now: status-NEW.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package mate-power-manager

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package mate-power-manager
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #870121 (http://bugs.debian.org/870121)
> # Bug title: mate-power-manager: crashes with upower 0.99.5 on any device 
> with a backlit keyboard
> #  * https://github.com/mate-desktop/mate-power-manager/issues/226
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 870121 + fixed-upstream
Bug #870121 [mate-power-manager] mate-power-manager: crashes with upower 0.99.5 
on any device with a backlit keyboard
Added tag(s) fixed-upstream.
> usertags 870121 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 870121 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#871275: marked as done (libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 17:49:06 +
with message-id 
and subject line Bug#871275: fixed in apt 1.5~beta2
has caused the Debian Bug report #871275,
regarding libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapt-pkg5.0
Version: 1.5~beta1
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: apt
Source-Version: 1.5~beta2

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated apt 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, 17 Aug 2017 19:28:00 +0200
Source: apt
Binary: apt libapt-pkg5.0 libapt-inst2.0 apt-doc libapt-pkg-dev libapt-pkg-doc 
apt-utils apt-transport-https
Architecture: source
Version: 1.5~beta2
Distribution: unstable
Urgency: medium
Maintainer: APT Development Team 
Changed-By: Julian Andres Klode 
Description:
 apt- commandline package manager
 apt-doc- documentation for APT
 apt-transport-https - Transitional package: curl-https download transport for 
APT
 apt-utils  - package management related utility programs
 libapt-inst2.0 - deb package format runtime library
 libapt-pkg-dev - development files for APT's libapt-pkg and libapt-inst
 libapt-pkg-doc - documentation for APT development
 libapt-pkg5.0 - package management runtime library
Closes: 811181 858877 868127 869425 869557 870675 871275
Changes:
 apt (1.5~beta2) unstable; urgency=medium
 .
   [ M. Willis Monroe ]
   * Minor grammar fix
 .
   [ Zhou Mo ]
   * zh_CN.po: update Simplified Chinese programs translation
 .
 

Bug#853441: hexcurse: diff for NMU version 1.58-1.1

[Adrian Bunk]

Control: tags 853441 + patch
Control: tags 853441 + pending

Dear maintainer,

I've prepared an NMU for hexcurse (versioned as 1.58-1.1) and uploaded 
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru hexcurse-1.58/debian/changelog hexcurse-1.58/debian/changelog
--- hexcurse-1.58/debian/changelog	2014-04-01 15:53:00.0 +0300
+++ hexcurse-1.58/debian/changelog	2017-08-17 20:32:55.0 +0300
@@ -1,3 +1,11 @@
+hexcurse (1.58-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patches from Felix Gruber to fix FTBFS with gcc 7.
+(Closes: #853441)
+
+ -- Adrian Bunk   Thu, 17 Aug 2017 20:32:55 +0300
+
 hexcurse (1.58-1) unstable; urgency=low
 
   * New upstream vesion 1.58-1 from https://github.com/LonnyGomes/hexcurse
diff -Nru hexcurse-1.58/debian/patches/0001-explicitly-mark-fallthrough-case.patch hexcurse-1.58/debian/patches/0001-explicitly-mark-fallthrough-case.patch
--- hexcurse-1.58/debian/patches/0001-explicitly-mark-fallthrough-case.patch	1970-01-01 02:00:00.0 +0200
+++ hexcurse-1.58/debian/patches/0001-explicitly-mark-fallthrough-case.patch	2017-08-17 20:32:14.0 +0300
@@ -0,0 +1,26 @@
+From d808cb7067d1df067f8b707fabbfaf9f8931484c Mon Sep 17 00:00:00 2001
+From: Felix Gruber 
+Date: Fri, 5 May 2017 22:40:07 +0200
+Subject: explicitly mark fallthrough case
+
+This prevents another error that got introduced with the more thorough
+diagnostics in GCC-7.
+---
+ src/acceptch.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/acceptch.c b/src/acceptch.c
+index 1580645..d57207b 100644
+--- a/src/acceptch.c
 b/src/acceptch.c
+@@ -297,6 +297,7 @@ int wacceptch(WINS *win, off_t len)
+ 		}
+ 		else
+ 		currentLine -= (2*MAXY);
++/* fall through */
+ 
+ 	case CTRL_AND('d'):
+ 	case KEY_PGDN:	/* if KEY_PGDN... */
+-- 
+2.11.0
+
diff -Nru hexcurse-1.58/debian/patches/0001-fix-format-truncation-error-with-GCC-7.patch hexcurse-1.58/debian/patches/0001-fix-format-truncation-error-with-GCC-7.patch
--- hexcurse-1.58/debian/patches/0001-fix-format-truncation-error-with-GCC-7.patch	1970-01-01 02:00:00.0 +0200
+++ hexcurse-1.58/debian/patches/0001-fix-format-truncation-error-with-GCC-7.patch	2017-08-17 20:32:55.0 +0300
@@ -0,0 +1,37 @@
+From 716b5d58ac859cc240b8ccb9cbd79ace3e0593c1 Mon Sep 17 00:00:00 2001
+From: Felix Gruber 
+Date: Fri, 5 May 2017 22:20:00 +0200
+Subject: fix format truncation error with GCC-7
+
+GCC-7 introduced new warnings and errors. Among them is a new warning
+for possible truncations in the output of snprintf. Since we are only
+interested in the return value of snprintf and do not use the string
+written by it we can also replace the buffer with a NULL pointer.
+This makes it explicit that we do not want to write a string and
+silences the GCC-7 error.
+
+See also the examples in
+http://en.cppreference.com/w/c/io/fprintf
+---
+ src/hexcurse.c | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/src/hexcurse.c b/src/hexcurse.c
+index 9342eb5..e723ddc 100644
+--- a/src/hexcurse.c
 b/src/hexcurse.c
+@@ -235,10 +235,9 @@ off_t parseArgs(int argc, char *argv[])
+ \/
+ int getMinimumAddressLength(off_t len)
+ {
+-char buffer[1];
+ int min_address_length;
+ 
+-min_address_length = snprintf(buffer, 1, "%jd", (intmax_t)len);
++min_address_length = snprintf(NULL, 0, "%jd", (intmax_t)len);
+ 
+ /* At least 8 characters wide */
+ return min_address_length > 8 ? min_address_length : 8;
+-- 
+2.11.0
+
diff -Nru hexcurse-1.58/debian/patches/series hexcurse-1.58/debian/patches/series
--- hexcurse-1.58/debian/patches/series	2014-04-01 15:52:40.0 +0300
+++ hexcurse-1.58/debian/patches/series	2017-08-17 20:32:55.0 +0300
@@ -1,2 +1,4 @@
 0001-Dont-ignore-singals.patch
 0002-Manpage-fix.patch
+0001-explicitly-mark-fallthrough-case.patch
+0001-fix-format-truncation-error-with-GCC-7.patch

Processed: hexcurse: diff for NMU version 1.58-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853441 + patch
Bug #853441 [src:hexcurse] hexcurse: ftbfs with GCC-7
Added tag(s) patch.
> tags 853441 + pending
Bug #853441 [src:hexcurse] hexcurse: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#853368: Fix for the dbf2mysql FTBFS with gcc 7

[Adrian Bunk]

Control: tags -1 patch

A fix for the dbf2mysql FTBFS with gcc 7 is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Description: Make strtoupper/strtolower static inline
 This seems to have been intended,
 and the static makes gcc 7 happy.
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/853368

--- dbf2mysql-1.14a.orig/dbf2mysql.c
+++ dbf2mysql-1.14a/dbf2mysql.c
@@ -41,21 +41,19 @@ char	*convert = NULL;
 
 void do_onlyfields (char *flist, dbhead *dbh);
 void do_substitute(char *subarg, dbhead *dbh);
-inline void strtoupper(char *string);
-inline void strtolower(char *string);
 void do_create(MYSQL *, char*, dbhead*);
 void do_inserts(MYSQL *, char*, dbhead*);
 int check_table(MYSQL *, char*);
 void usage(void);
 
-inline void strtoupper(char *string) {
+static inline void strtoupper(char *string) {
 	while(*string != '\0') {
 		*string = toupper(*string);
 		string++;
 	}
 }
 
-inline void strtolower(char *string) {
+static inline void strtolower(char *string) {
 	while(*string != '\0') {
 		*string = tolower(*string);
 		string++;
--- dbf2mysql-1.14a.orig/mysql2dbf.c
+++ dbf2mysql-1.14a/mysql2dbf.c
@@ -21,18 +21,16 @@ char	*table = NULL;
 char*pass = NULL;
 char*user = NULL;
 
-inline void strtoupper(char *string);
-inline void strtolower(char *string);
 void usage(void);
 
-inline void strtoupper(char *string) {
+static inline void strtoupper(char *string) {
 while(*string != '\0') {
 *string = toupper(*string);
 		string++;
 }
 }
 
-inline void strtolower(char *string) {
+static inline void strtolower(char *string) {
 while(*string != '\0') {
 *string = tolower(*string);
 		string++;

Processed: Fix for the dbf2mysql FTBFS with gcc 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #853368 [src:dbf2mysql] dbf2mysql: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#872464: zimlib: FTBFS all over the place due to symbols diff

[Vasudev Kamath]

Hi James,

On 17-Aug-2017 22:45, "James Clarke"  wrote:

Source: zimlib
Version: 2.0.0-1
Severity: serious

Hi,
Once again zimlib FTBFS due to symbols file diffs. Please at least *try*
to get a working symbols file; you can at least build amd64 locally, and
we have porterboxen for a reason...


I know it is failing, please have some patience :). It's failing because
soname bumped and a new symbol file was created.

I use i386 box hence it's breaking on amd64, also I will update symbols
file once it has built on all architecture on builds, so  I get all diff
for symbol files. This is my workflow for most of my library packages as I
don't have time to build it on all architecture using porter boxes.

Thanks for the report, it will be a reminder for me so I'll deal with
failure as quickly as possible.

Cheers,
Vasudev

Bug#853645: rocksdb: ftbfs with GCC-7

[Adrian Bunk]

Control: tags -1 fixed-upstream

On Tue, Jan 31, 2017 at 09:35:40AM +, Matthias Klose wrote:
>...
>   CC   db/auto_roll_logger.o
> In file included from ./util/posix_logger.h:28:0,
>  from ./port/util_logger.h:18,
>  from ./db/auto_roll_logger.h:15,
>  from db/auto_roll_logger.cc:6:
> ./util/sync_point.h:75:25: error: 'std::function' has not been declared
> std::function callback);
>  ^~~~
>...

This has been fixed upstream in
https://github.com/facebook/rocksdb/commit/816c1e30ca73615c75fc208ddcc4b05012b30951

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#872190: gitlab: CVE-2017-12426: Remote Command Execution in git client

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #872190 [src:gitlab] gitlab: CVE-2017-12426: Remote Command Execution in 
git client
Severity set to 'minor' from 'grave'

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

Bug#872190: gitlab: CVE-2017-12426: Remote Command Execution in git client

[Salvatore Bonaccorso]

Control: severity -1 minor

On Thu, Aug 17, 2017 at 06:24:43PM +0530, Pirate Praveen wrote:
> On Tue, 15 Aug 2017 07:40:59 +0200 Salvatore Bonaccorso
>  wrote:> If you fix the vulnerability please also
> make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> This is already fixed in git 1:2.11.0-3+deb9u1. The patch in gitlab is
> extra step to prevent in case of a vulnerable git. Since debian already
> has the fixed version of git, I don't think we need to do anything to
> gitlab.

Agree, we can at least lower the severity and thanks a lot for the
followup. The CVE seem to be specific assigned for the "via a crafted
SSH URL in a project import". Can you close this bug once the gitlab
version contains as well this extra safety measure if still running
with older git?

For the security tracker I have already downgraded the severity to
unimportant.

Regards,
Salvatore

Processed: Re: Bug#853645: rocksdb: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #853645 [src:rocksdb] rocksdb: ftbfs with GCC-7
Added tag(s) fixed-upstream.

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

Bug#872464: zimlib: FTBFS all over the place due to symbols diff

[James Clarke]

Source: zimlib
Version: 2.0.0-1
Severity: serious

Hi,
Once again zimlib FTBFS due to symbols file diffs. Please at least *try*
to get a working symbols file; you can at least build amd64 locally, and
we have porterboxen for a reason...

James

Bug#853649: gnulib intprops.h build error with gcc 7

[Adrian Bunk]

On Thu, Aug 17, 2017 at 07:02:47PM +0200, Bruno Haible wrote:
> Hi Adrian,
> 
> Could you please give the complete output of "gcc --version"?
> 
> Given that [1] references an URL that contains the string
> 'gcc7-20170126' whereas gcc 7 was released on 2017-05-02 [2],
> it could be that the report is about a gcc prerelease that
> came 3 months before the gcc 7 release.

For reproducing and my tiny testcase I was using
  gcc (Debian 7.1.0-13) 7.1.0
from Debian unstable - that is GCC 7.2 release candidate 2
with minimal Debian patching.

> Bruno
>...

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#853649: gnulib intprops.h build error with gcc 7

[Bruno Haible]

Hi Adrian,

Could you please give the complete output of "gcc --version"?

Given that [1] references an URL that contains the string
'gcc7-20170126' whereas gcc 7 was released on 2017-05-02 [2],
it could be that the report is about a gcc prerelease that
came 3 months before the gcc 7 release.

Bruno

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853649
[2] https://gcc.gnu.org/

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 853351 src:libmstoolkit
Bug #853351 [src:comet-ms] comet-ms: ftbfs with GCC-7
Bug reassigned from package 'src:comet-ms' to 'src:libmstoolkit'.
No longer marked as found in versions comet-ms/2014022-3.
Ignoring request to alter fixed versions of bug #853351 to the same values 
previously set
> forcemerge 853498 853351
Bug #853498 [src:libmstoolkit] libmstoolkit: ftbfs with GCC-7
Bug #853351 [src:libmstoolkit] comet-ms: ftbfs with GCC-7
Marked as found in versions libmstoolkit/77.0.0-1.
Merged 853351 853498
> affects 853498 src:comet-ms
Bug #853498 [src:libmstoolkit] libmstoolkit: ftbfs with GCC-7
Bug #853351 [src:libmstoolkit] comet-ms: ftbfs with GCC-7
Added indication that 853498 affects src:comet-ms
Added indication that 853351 affects src:comet-ms
> thanks
Stopping processing here.

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

Processed: found 871514 in gcc-7/7.1.0-10

[Debian Bug Tracking System]

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

> found 871514 gcc-7/7.1.0-10
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Marked as found in versions gcc-7/7.1.0-10.
Marked as found in versions gcc-7/7.1.0-10.
> thanks
Stopping processing here.

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

Processed: Fix for the bind-dyndb-ldap FTBFS with gcc 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #853326 [src:bind-dyndb-ldap] bind-dyndb-ldap: ftbfs with GCC-7
Added tag(s) patch and fixed-upstream.

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

Bug#853326: Fix for the bind-dyndb-ldap FTBFS with gcc 7

[Adrian Bunk]

Control: tags -1 patch fixed-upstream

The upstream fix for the bind-dyndb-ldap FTBFS with gcc 7
is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

>From f76ca3b3a4c2c030071dd23c706d8cc06e1fa2a9 Mon Sep 17 00:00:00 2001
From: Tomas Krizek 
Date: Thu, 9 Feb 2017 17:52:59 +0100
Subject: Remove duplicate const declaration specifier
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reviewed-By: Petr Menšík 
---
 src/ldap_helper.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: bind-dyndb-ldap-10.1/src/ldap_helper.c
===
--- bind-dyndb-ldap-10.1.orig/src/ldap_helper.c
+++ bind-dyndb-ldap-10.1/src/ldap_helper.c
@@ -2297,7 +2297,7 @@ free_rdatalist(isc_mem_t *mctx, dns_rdat
  * @retval  others Unexpected errors.
  */
 static isc_result_t ATTR_NONNULLS ATTR_CHECKRESULT
-ldap_substitute_rr_template(isc_mem_t *mctx, const settings_set_t const * set,
+ldap_substitute_rr_template(isc_mem_t *mctx, const settings_set_t * set,
 			ld_string_t *orig_val, ld_string_t **output) {
 	isc_result_t result;
 	regex_t regex;

Bug#853649: gnulib intprops.h build error with gcc 7

[Adrian Bunk]

> Package: src:rush
> Version: 1.8+dfsg-1
>...
> In file included from inttostr.h:25:0,
>  from anytostr.c:31,
>  from imaxtostr.c:5:
> intprops.h:236:34: error: expected ')' before '(' token
> __builtin_add_overflow (a, b, (__typeof__ ((a) + (b)) *) 0)
>   ^
> Makefile:1284: recipe for target 'imaxtostr.o' failed
>...

This can be reproduced with

$ cat test.c
# define _GL_ADD_OVERFLOW(a, b, min, max)
   __builtin_add_overflow (a, b, (__typeof__ ((a) + (b)) *) 0)
$ gcc -c test.c
test.c:2:34: error: expected ‘)’ before ‘(’ token
__builtin_add_overflow (a, b, (__typeof__ ((a) + (b)) *) 0)
  ^
$ 


This is a problem in gnulib, introduced by

commit d22721e2efd88f26588c971eb1eeb3ec40de
Author: Paul Eggert 
Date:   Mon Aug 29 10:08:32 2016 -0700

intprops.h: use __typeof__ with GCC 7

* lib/intprops.h (_GL_ADD_OVERFLOW, _GL_SUBTRACT_OVERFLOW)
(_GL_MULTIPLY_OVERFLOW): Use __typeof__ as in the GCC manual.
This avoids computing the expression's value (which might overflow!).


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#853672: Fix for svxlink FTBFS with gcc 7

[Adrian Bunk]

Control: tags -1 patch fixed-upstream

The upstream fix for the svxlink FTBFS with gcc 7 is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

>From 611cc5cc134f710f94fc8987375259bd8af34604 Mon Sep 17 00:00:00 2001
From: Tobias Blomberg 
Date: Mon, 19 Jun 2017 22:04:20 +0200
Subject: Fix compilation problem in Async::AudioDeviceAlsa

- On newer compilers the compilation would fail on ambiguous call to abs
---
 src/async/audio/AsyncAudioDeviceAlsa.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/async/audio/AsyncAudioDeviceAlsa.cpp b/src/async/audio/AsyncAudioDeviceAlsa.cpp
index 17d255e8..15d760d5 100644
--- a/src/async/audio/AsyncAudioDeviceAlsa.cpp
+++ b/src/async/audio/AsyncAudioDeviceAlsa.cpp
@@ -548,7 +548,7 @@ bool AudioDeviceAlsa::initParams(snd_pcm_t *pcm_handle)
 return false;
   }
 
-  if (::abs(real_rate - sample_rate) > 100)
+  if (::abs(static_cast(real_rate) - sample_rate) > 100)
   {
 cerr << "*** ERROR: The sample rate could not be set to "
  << sample_rate << "Hz for ALSA device \"" << dev_name << "\". "
-- 
2.11.0

Processed: Fix for svxlink FTBFS with gcc 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #853672 [src:svxlink] svxlink: ftbfs with GCC-7
Added tag(s) patch and fixed-upstream.

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

Processed: Re: libsnappy-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libsnappy-shared.a -> /build/snappy-1.1.6/debian/libsnappy-dev/usr/lib/x86_64-linux-gnu/libsnappy.a

[Debian Bug Tracking System]

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

> tags 872226 + patch
Bug #872226 [libsnappy-dev] libsnappy-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/libsnappy-shared.a -> 
/build/snappy-1.1.6/debian/libsnappy-dev/usr/lib/x86_64-linux-gnu/libsnappy.a
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#872226: libsnappy-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libsnappy-shared.a -> /build/snappy-1.1.6/debian/libsnappy-dev/usr/lib/x86_64-linux-gnu/libsnappy.a

[Chris Lamb]

tags 872226 + patch
thanks

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/rules b/debian/rules
index e9f099e..e41c98a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,7 +13,7 @@ override_dh_auto_configure:
 
 override_dh_install:
dh_install
-   ln -s $(DEVPKGDIR)/usr/lib/${DEB_HOST_MULTIARCH}/libsnappy.a \
+   ln -s /usr/lib/${DEB_HOST_MULTIARCH}/libsnappy.a \
$(DEVPKGDIR)/usr/lib/${DEB_HOST_MULTIARCH}/libsnappy-shared.a
 
 %:

Bug#872226: libsnappy-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libsnappy-shared.a -> /build/snappy-1.1.6/debian/libsnappy-dev/usr/lib/x86_64-linux-gnu/libsnappy.a

[Chris Lamb]

Hi,

> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.

This was also flagged by the reproducible builds effort; the symlink includes
the build path so it was different between the two builds :)


Regards,

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

Bug#871685: marked as done (courier FTBFS: configure: error: /usr/bin/gpg not found)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 16:51:47 +0100
with message-id <0e45b088-3200-312a-9a26-0cfb69bbc...@p10link.net>
and subject line courier FTBFS: configure: error: /usr/bin/gpg not found
has caused the Debian Bug report #871685,
regarding courier FTBFS: configure: error: /usr/bin/gpg not found
to be marked as done.

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

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


-- 
871685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: courier
Version: 0.77.0-1
Severity: serious

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

...
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether ln -s works... yes
checking for gpg... no
checking for gpg2... no
configure: error: /usr/bin/gpg not found
configure: error: ./configure failed for libs/gpglib
--- End Message ---
--- Begin Message ---

Version: 0.77.0-2

According to the changelog this was fixed in -2, however it seems -2 was never 
actually uploaded (-3 was) and so the changelog entries for -2 were never 
passed to the automatic bug closer.

-3 built successfully on all release architectures, so i'm closing this bug.--- End Message ---

Bug#869016: marked as done (pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~))

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 17:35:38 +0200
with message-id <6164580.9KX5ojMMXr@tuxin>
and subject line Re: Bug#869008: qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
has caused the Debian Bug report #869008,
regarding pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 
5.7.1+dfsg-3~)
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.)


-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyqt5
Version: 5.7+dfsg-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> dpkg-deb: building package 'sbuild-build-depends-pyqt5-dummy' in 
> '/<>/resolver-Yj9i1S/apt_archive/sbuild-build-depends-pyqt5-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pyqt5-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Yj9i1S/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Yj9i1S/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Yj9i1S/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Yj9i1S/apt_archive ./ Sources [815 B]
> Get:5 copy:/<>/resolver-Yj9i1S/apt_archive ./ Packages [864 B]
> Fetched 2642 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pyqt5 build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution 

Bug#871064: marked as done (pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~))

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 17:35:38 +0200
with message-id <6164580.9KX5ojMMXr@tuxin>
and subject line Re: Bug#869008: qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
has caused the Debian Bug report #869008,
regarding pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 
5.7.1+dfsg-3~)
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.)


-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyqt5
Version: 5.7+dfsg-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> dpkg-deb: building package 'sbuild-build-depends-pyqt5-dummy' in 
> '/<>/resolver-01Uh6s/apt_archive/sbuild-build-depends-pyqt5-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pyqt5-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-01Uh6s/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-01Uh6s/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-01Uh6s/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-01Uh6s/apt_archive ./ Sources [815 B]
> Get:5 copy:/<>/resolver-01Uh6s/apt_archive ./ Packages [866 B]
> Fetched 2644 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pyqt5 build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution 

Bug#871387: marked as done (qupzilla: FTBFS: build-dependency not installable: qtwebengine5-dev)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 17:35:38 +0200
with message-id <6164580.9KX5ojMMXr@tuxin>
and subject line Re: Bug#869008: qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
has caused the Debian Bug report #869008,
regarding qupzilla: FTBFS: build-dependency not installable: qtwebengine5-dev
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.)


-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qupzilla
Version: 2.1.2~dfsg1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), qtbase5-dev, qtchooser, qt5-qmake, 
> libqt5webkit5-dev, qtwebengine5-dev, qttools5-dev-tools, libxcb-util0-dev, 
> qtbase5-private-dev, qtscript5-dev, libqt5x11extras5-dev, libx11-dev, 
> libssl1.0-dev, kdelibs5-dev, libgnome-keyring-dev, libjs-jquery, 
> libjs-jquery-ui
> Filtered Build-Depends: debhelper (>= 9), qtbase5-dev, qtchooser, qt5-qmake, 
> libqt5webkit5-dev, qtwebengine5-dev, qttools5-dev-tools, libxcb-util0-dev, 
> qtbase5-private-dev, qtscript5-dev, libqt5x11extras5-dev, libx11-dev, 
> libssl1.0-dev, kdelibs5-dev, libgnome-keyring-dev, libjs-jquery, 
> libjs-jquery-ui
> dpkg-deb: building package 'sbuild-build-depends-qupzilla-dummy' in 
> '/<>/resolver-dAb3BH/apt_archive/sbuild-build-depends-qupzilla-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-qupzilla-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-dAb3BH/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-dAb3BH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-dAb3BH/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-dAb3BH/apt_archive ./ Sources [611 B]
> Get:5 copy:/<>/resolver-dAb3BH/apt_archive ./ Packages [692 B]
> Fetched 2266 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install qupzilla build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-qupzilla-dummy : Depends: qtwebengine5-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/qupzilla_2.1.2~dfsg1-2_unstable.log

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

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

Hey,

the 5.9.0+dfsg-1 shouldn't never enter sid, this version was proposed to go to 
experimental, but sbuild worked against me :( I think I now fixed my 
scripting... Together with the Qt 5.9 transition the needed packages now 
enters sid and this issue is solved.

Best Regards,

sandro


On Donnerstag, 20. Juli 2017 07:44:30 CEST Lucas Nussbaum wrote:
> Source: qtwebengine-opensource-src
> Version: 5.9.0+dfsg-1
> Severity: serious
> 

Bug#871380: marked as done (algobox: FTBFS: build-dependency not installable: qtwebengine5-dev)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 17:35:38 +0200
with message-id <6164580.9KX5ojMMXr@tuxin>
and subject line Re: Bug#869008: qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
has caused the Debian Bug report #869008,
regarding algobox: FTBFS: build-dependency not installable: qtwebengine5-dev
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.)


-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: algobox
Version: 1.0.1+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), qtbase5-dev, qtwebengine5-dev
> Filtered Build-Depends: debhelper (>= 9), qtbase5-dev, qtwebengine5-dev
> dpkg-deb: building package 'sbuild-build-depends-algobox-dummy' in 
> '/<>/resolver-MDbFki/apt_archive/sbuild-build-depends-algobox-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-algobox-dummy 
> sbuild-build-depends-core-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MDbFki/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MDbFki/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-MDbFki/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MDbFki/apt_archive ./ Sources [506 B]
> Get:5 copy:/<>/resolver-MDbFki/apt_archive ./ Packages [587 B]
> Fetched 2056 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install algobox build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-algobox-dummy : Depends: qtwebengine5-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/algobox_1.0.1+dfsg-1_unstable.log

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

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

Hey,

the 5.9.0+dfsg-1 shouldn't never enter sid, this version was proposed to go to 
experimental, but sbuild worked against me :( I think I now fixed my 
scripting... Together with the Qt 5.9 transition the needed packages now 
enters sid and this issue is solved.

Best Regards,

sandro


On Donnerstag, 20. Juli 2017 07:44:30 CEST Lucas Nussbaum wrote:
> Source: qtwebengine-opensource-src
> Version: 5.9.0+dfsg-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170719 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.


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

Bug#869008: marked as done (qtwebengine-opensource-src: FTBFS: unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), q

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 17:35:38 +0200
with message-id <6164580.9KX5ojMMXr@tuxin>
and subject line Re: Bug#869008: qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
has caused the Debian Bug report #869008,
regarding qtwebengine-opensource-src: FTBFS: unsatisfiable build-dependencies: 
libqt5opengl5-dev (>= 5.9.0~), libqt5webchannel5-dev (>= 5.9.0~), 
libqt5xmlpatterns5-dev (>= 5.9.0~), qtbase5-private-dev (>= 5.9.0~), 
qtdeclarative5-private-dev (>= 5.9.0~), qtscript5-private-dev (>= 5.9.0~), 
libqt5sql5-sqlite (>= 5.9.0~), qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools 
(>= 5.9.0~)
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.)


-- 
869008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtwebengine-opensource-src
Version: 5.9.0+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: autotools-dev, bison, chrpath, closure-compiler, 
> debhelper (>= 10), dh-autoreconf, flex, gperf, yasm, ninja-build, 
> khronos-api, libasound2-dev, libavcodec-dev, libavformat-dev, libavutil-dev, 
> libcap-dev, libdbus-1-dev, libegl1-mesa-dev, libgl1-mesa-dri, libevent-dev, 
> libflac-dev, libfontconfig1-dev, libgl1-mesa-dev | libgl-dev, libglib2.0-dev, 
> libglu1-mesa-dev | libglu-dev, libgstreamer-plugins-base1.0-dev, 
> libgstreamer1.0-dev, libharfbuzz-dev, libicu-dev, libjpeg-dev, 
> libjsoncpp-dev, libminizip-dev, libnss3-dev, libopus-dev, liblcms2-dev, 
> libpci-dev, libpng-dev, libprotobuf-dev, libpulse-dev, libqt5opengl5-dev (>= 
> 5.9.0~), libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 
> 5.9.0~), libre2-dev (>= 20161101+dfsg-2), libsnappy-dev, libsqlite3-dev, 
> libsrtp-dev, libusb-1.0-0-dev, libvpx-dev, libwebp-dev, libxcomposite-dev, 
> libxcursor-dev, libxml2-dev, libxnvctrl-dev, libxrandr-dev, libxrender-dev, 
> libxslt1-dev, libxss-dev, libxtst-dev, mesa-common-dev, pkg-config, 
> pkg-kde-tools, protobuf-compiler, python, qtbase5-private-dev (>= 5.9.0~), 
> qtdeclarative5-private-dev (>= 5.9.0~), qtlocation5-dev, 
> qtscript5-private-dev (>= 5.9.0~), re2c, ruby, xauth, xvfb, yui-compressor, 
> libqt5sql5-sqlite (>= 5.9.0~), qtbase5-doc-html (>= 5.9.0~), 
> qttools5-dev-tools (>= 5.9.0~)
> Filtered Build-Depends: autotools-dev, bison, chrpath, closure-compiler, 
> debhelper (>= 10), dh-autoreconf, flex, gperf, yasm, ninja-build, 
> khronos-api, libasound2-dev, libavcodec-dev, libavformat-dev, libavutil-dev, 
> libcap-dev, libdbus-1-dev, libegl1-mesa-dev, libgl1-mesa-dri, libevent-dev, 
> libflac-dev, libfontconfig1-dev, libgl1-mesa-dev, libglib2.0-dev, 
> libglu1-mesa-dev, libgstreamer-plugins-base1.0-dev, libgstreamer1.0-dev, 
> libharfbuzz-dev, libicu-dev, libjpeg-dev, libjsoncpp-dev, libminizip-dev, 
> libnss3-dev, libopus-dev, liblcms2-dev, libpci-dev, libpng-dev, 
> libprotobuf-dev, libpulse-dev, libqt5opengl5-dev (>= 5.9.0~), 
> libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
> libre2-dev (>= 20161101+dfsg-2), libsnappy-dev, libsqlite3-dev, libsrtp-dev, 
> libusb-1.0-0-dev, libvpx-dev, libwebp-dev, libxcomposite-dev, libxcursor-dev, 
> libxml2-dev, libxnvctrl-dev, libxrandr-dev, libxrender-dev, libxslt1-dev, 
> libxss-dev, libxtst-dev, mesa-common-dev, pkg-config, pkg-kde-tools, 
> protobuf-compiler, python, qtbase5-private-dev (>= 5.9.0~), 
> qtdeclarative5-private-dev (>= 5.9.0~), qtlocation5-dev, 
> qtscript5-private-dev (>= 5.9.0~), re2c, ruby, xauth, xvfb, yui-compressor, 
> libqt5sql5-sqlite (>= 5.9.0~), qtbase5-doc-html (>= 5.9.0~), 
> qttools5-dev-tools (>= 5.9.0~)
> dpkg-deb: building package 
> 'sbuild-build-depends-qtwebengine-opensource-src-dummy' in 
> 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 853610 src:gcc-7
Bug #853610 [src:pesign] pesign: ftbfs with GCC-7
Bug reassigned from package 'src:pesign' to 'src:gcc-7'.
No longer marked as found in versions pesign/0.112-3.
Ignoring request to alter fixed versions of bug #853610 to the same values 
previously set
> forcemerge 853537 853610
Bug #853537 [src:gcc-7] binutils: /usr/bin/gcc-ar segfaults
Bug #853610 [src:gcc-7] pesign: ftbfs with GCC-7
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR81829'.
Added indication that 853610 affects src:mariadb-10.1
Added tag(s) upstream.
Merged 853537 853610
> affects 853537 src:pesign
Bug #853537 [src:gcc-7] binutils: /usr/bin/gcc-ar segfaults
Bug #853610 [src:gcc-7] pesign: ftbfs with GCC-7
Added indication that 853537 affects src:pesign
Added indication that 853610 affects src:pesign
> thanks
Stopping processing here.

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

Bug#831238: marked as done (plasma-widget-adjustableclock: FTBFS: build-dependency not installable: kde-workspace-dev (>= 4:4.8))

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 15:05:01 +
with message-id 
and subject line Bug#872279: Removed package(s) from unstable
has caused the Debian Bug report #831238,
regarding plasma-widget-adjustableclock: FTBFS: build-dependency not 
installable: kde-workspace-dev (>= 4:4.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.)


-- 
831238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-widget-adjustableclock
Version: 4.1.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ┌──┐
> │ Install plasma-widget-adjustableclock build dependencies (apt-based 
> resolver) │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-plasma-widget-adjustableclock-dummy : Depends: 
> kde-workspace-dev (>= 4:4.8) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/plasma-widget-adjustableclock_4.1.4-1_unstable_gcc5.log

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

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

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#868741: marked as done (lcmaps-plugins-voms: build-dependency globus-core has been removed from unstable)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 15:05:39 +
with message-id 
and subject line Bug#868741: fixed in lcmaps-plugins-voms 1.7.1-1
has caused the Debian Bug report #868741,
regarding lcmaps-plugins-voms: build-dependency globus-core has been removed 
from unstable
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.)


-- 
868741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lcmaps-plugins-voms
Version: 1.6.1-2.1
Severity: serious

The transitional globus-core package has been removed
from unstable (see #868335).
--- End Message ---
--- Begin Message ---
Source: lcmaps-plugins-voms
Source-Version: 1.7.1-1

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

Debian distribution maintenance software
pp.
Dennis van Dok  (supplier of updated lcmaps-plugins-voms 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 16 Aug 2017 14:08:35 +0200
Source: lcmaps-plugins-voms
Binary: lcmaps-plugins-voms
Architecture: source amd64
Version: 1.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Dennis van Dok 
Changed-By: Dennis van Dok 
Description:
 lcmaps-plugins-voms - VOMS plugins for the LCMAPS authorization framework
Closes: 868741
Changes:
 lcmaps-plugins-voms (1.7.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Remove build dependency on globus-core. Closes: #868741
Checksums-Sha1:
 280d30372c0eeeb2302437f8ca378dabbda5acfa 2180 lcmaps-plugins-voms_1.7.1-1.dsc
 7d43e2e0922fa3634f599dcd145d44db2726123a 392550 
lcmaps-plugins-voms_1.7.1.orig.tar.gz
 9a8d56fa314417466a57edf54b7f5391db7087ef 3200 
lcmaps-plugins-voms_1.7.1-1.debian.tar.xz
 1b06d963b9a9e69d9eed92ac25106057d2c32b1b 93816 
lcmaps-plugins-voms-dbgsym_1.7.1-1_amd64.deb
 d77caf938807b852356733886a48f99eb880b5be 6698 
lcmaps-plugins-voms_1.7.1-1_amd64.buildinfo
 bdf5558fdb74b25c095e91e2963e426a1acbaeff 66152 
lcmaps-plugins-voms_1.7.1-1_amd64.deb
Checksums-Sha256:
 6ebf6797c6ca8db821ba7482ce15334a9e63a95bd7b96394b30f829420454b17 2180 
lcmaps-plugins-voms_1.7.1-1.dsc
 fe2fd0d2abaed91f078b51933668b418f394bbbcba102276944261f1340f0ee9 392550 
lcmaps-plugins-voms_1.7.1.orig.tar.gz
 1615efa47fc16291764d739dd19e59e42b91192c156e112e09ebe0336a89f389 3200 
lcmaps-plugins-voms_1.7.1-1.debian.tar.xz
 1a3635e126875aea582b63d4a866b4fe557a31569405698e0fc3cc0fab5b498a 93816 
lcmaps-plugins-voms-dbgsym_1.7.1-1_amd64.deb
 57d00b12e236e4d8a6f6f648266103f73f8e22d653f4f46356b1ed34ef5eeca3 6698 
lcmaps-plugins-voms_1.7.1-1_amd64.buildinfo
 2dfcb764ca3bbe6addea81638dfd71efbb25209859d14462acf6e30413d65963 66152 
lcmaps-plugins-voms_1.7.1-1_amd64.deb
Files:
 b056a38adbbd43407cabb591ac1b6dad 2180 libs extra 
lcmaps-plugins-voms_1.7.1-1.dsc
 0f6937dbd51d3c01382ddc5f75c364b4 392550 libs extra 
lcmaps-plugins-voms_1.7.1.orig.tar.gz
 cc3fd33698bfa383f886825977eb09b1 3200 libs extra 
lcmaps-plugins-voms_1.7.1-1.debian.tar.xz
 e62efb75285d8f294401dc56cb83d7d8 93816 debug extra 
lcmaps-plugins-voms-dbgsym_1.7.1-1_amd64.deb
 700fea69b2e67c5873b6e012bcb382b1 6698 libs extra 
lcmaps-plugins-voms_1.7.1-1_amd64.buildinfo
 e6f898038a98021a531d72ba50e49eeb 66152 libs extra 
lcmaps-plugins-voms_1.7.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE6hgwr99NQxrZ4RRS6K7C/zvhqUsFAlmVmuwACgkQ6K7C/zvh
qUtSGw//d8JaXMR4BDztGqybLsftbKXj471ubchApOoqggkKVxhGO7URgB+0qgZd
0ywPVxXBXlhYxRq686mlw8O0Q88seBv6dxjhG7etwlHQivVLuwUz1ESwZJGO1ry5
RBFAI6MxasLWfJ1bbR9dP+ZWWoBdapF/eL4PWtEoCzbfv872YaY/JLczK4K6OHyP
NP0x2FUZ3f631xxt5XG9v0dCDj9t7t3opZTAydy0jO62oIW7yDEOmorRP5j3U5ov
xlUhefNX/vIAfWcbXkp6u/VZ5LHTQW2zfB6CAHQc1LonBlE28BefD7tXOAO5lO9c
dSJnyPaEOX96F1kMHJULX7MzzvwRjJ5OT4uhNxiUiVp70ksXVmngg/E6zGHm97K5
1fWibCynLyIzVUcdCWvcJDn7sBlIkmWXB10xuVtcRdSDaZGsN+MOEMFAiEz6WVDj
VKlkKMe0RKtdIatFd2LpIem2QUqBBgw0tiHj7tD/NR2Z5z/Y8iQDgEBuKNRvrwK+
TERXRcq/y8U9SMKu48/NwUs0Ocu3O5mWwQ6jW3y9MfUjfT2FDEyYWBolraWI9mNH

Bug#795109: marked as done (plasma-widget-adjustableclock: Not usable anymore in Plasma5)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 15:05:01 +
with message-id 
and subject line Bug#872279: Removed package(s) from unstable
has caused the Debian Bug report #795109,
regarding plasma-widget-adjustableclock: Not usable anymore in Plasma5
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.)


-- 
795109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-widget-adjustableclock
Version: 4.1.4-1
Severity: serious
Justification: Not usable anymore

Hi! Plasma 5 has arrived to testing a few weeks ago and so all Plasma 4
widgets have become unusable.

Please consider either porting this widget to Plasma5 or asking it's removal
from the archive.

Thanks!

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 4.1.4-1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: Bug#853674: synfig: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 etl-dev
Bug #853674 [src:synfig] synfig: ftbfs with GCC-7
Bug reassigned from package 'src:synfig' to 'etl-dev'.
No longer marked as found in versions synfig/1.0.2-1.
Ignoring request to alter fixed versions of bug #853674 to the same values 
previously set
> reassign 853675 etl-dev
Bug #853675 [src:synfigstudio] synfigstudio: ftbfs with GCC-7
Bug reassigned from package 'src:synfigstudio' to 'etl-dev'.
No longer marked as found in versions synfigstudio/1.0.2-1.
Ignoring request to alter fixed versions of bug #853675 to the same values 
previously set
> forcemerge -1 853675
Bug #853674 [etl-dev] synfig: ftbfs with GCC-7
Bug #853675 [etl-dev] synfigstudio: ftbfs with GCC-7
Merged 853674 853675
> retitle -1 etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Bug #853674 [etl-dev] synfig: ftbfs with GCC-7
Bug #853675 [etl-dev] synfigstudio: ftbfs with GCC-7
Changed Bug title to 'etl-dev: /usr/include/ETL/_surface.h error with gcc 7' 
from 'synfig: ftbfs with GCC-7'.
Changed Bug title to 'etl-dev: /usr/include/ETL/_surface.h error with gcc 7' 
from 'synfigstudio: ftbfs with GCC-7'.
> affects -1 src:synfig src:synfigstudio
Bug #853674 [etl-dev] etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Bug #853675 [etl-dev] etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Added indication that 853674 affects src:synfig and src:synfigstudio
Added indication that 853675 affects src:synfig and src:synfigstudio

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

Bug#853674: synfig: ftbfs with GCC-7

[Adrian Bunk]

Control: reassign -1 etl-dev
Control: reassign 853675 etl-dev
Control: forcemerge -1 853675
Control: retitle -1 etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Control: affects -1 src:synfig src:synfigstudio

The actual error message is:

...
In file included from /usr/include/ETL/surface:32:0,
 from surface.h:34,
 from context.h:34,
 from target_cairo_tile.cpp:37:
/usr/include/ETL/_surface.h: In member function 'void etl::surface::swap(const etl::surface&)':
/usr/include/ETL/_surface.h:95:20: error: no matching function for call to 
'swap(int&, const int&)'
   std::swap(w_,x.w_);
^
...


This is a bug in etl-dev that is also visible during src:etl build [1].

cu
Adrian

[1] 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/etl_0.04.19-1.rbuild.log

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#871275: in apt marked as pending

[Julian Andres Klode]

Control: tag 871275 pending

Hello,

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

https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=f63b3e0

(this message was generated automatically based on the git commit message)
---
commit f63b3e01e436a8c0b4711b69a1a8794161e4c5a7
Author: Julian Andres Klode 
Date:   Thu Aug 17 15:37:49 2017 +0200

Handle GCC 7 std::string operator ABI break

We now require gcc 7 on the packaging side, and add an appropriate
symbol to our symbols file.

Also adjust prepare-release to ignore g++ version requirements
when setting up build dependencies on CI.

Closes: #871275

Processed: Bug#871275 in apt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 871275 pending
Bug #871275 [libapt-pkg5.0] libapt-pkg5.0: requires rebuild against GCC 7 and 
symbols/shlibs bump
Added tag(s) pending.

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

Bug#853573: marked as done (nodejs: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 17 Aug 2017 11:17:26 -0300
with message-id 

and subject line 6.11 built with gcc-7
has caused the Debian Bug report #853573,
regarding nodejs: ftbfs with GCC-7
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.)


-- 
853573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nodejs
Version: 4.7.2~dfsg-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/nodejs_4.7.2~dfsg-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
  g++  -I../deps/gtest -I../deps/gtest/include  -pthread -Wall -Wextra 
-Wno-unused-parameter -m64 -Wno-missing-field-initializers -O3 
-ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti 
-fno-exceptions -std=gnu++0x -MMD -MF 
/<>/out/Release/.deps//<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-filepath.o.d.raw
 -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
/<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-filepath.o 
../deps/gtest/src/gtest-filepath.cc
  g++  -I../deps/gtest -I../deps/gtest/include  -pthread -Wall -Wextra 
-Wno-unused-parameter -m64 -Wno-missing-field-initializers -O3 
-ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti 
-fno-exceptions -std=gnu++0x -MMD -MF 
/<>/out/Release/.deps//<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-port.o.d.raw
 -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
/<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-port.o 
../deps/gtest/src/gtest-port.cc
  g++  -I../deps/gtest -I../deps/gtest/include  -pthread -Wall -Wextra 
-Wno-unused-parameter -m64 -Wno-missing-field-initializers -O3 
-ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti 
-fno-exceptions -std=gnu++0x -MMD -MF 
/<>/out/Release/.deps//<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-printers.o.d.raw
 -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
/<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-printers.o 
../deps/gtest/src/gtest-printers.cc
  g++  -I../deps/gtest -I../deps/gtest/include  -pthread -Wall -Wextra 
-Wno-unused-parameter -m64 -Wno-missing-field-initializers -O3 
-ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti 
-fno-exceptions -std=gnu++0x -MMD -MF 
/<>/out/Release/.deps//<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-test-part.o.d.raw
 -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
/<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-test-part.o 
../deps/gtest/src/gtest-test-part.cc
  g++  -I../deps/gtest -I../deps/gtest/include  -pthread -Wall -Wextra 
-Wno-unused-parameter -m64 -Wno-missing-field-initializers -O3 
-ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti 
-fno-exceptions -std=gnu++0x -MMD -MF 
/<>/out/Release/.deps//<>/out/Release/obj.target/gtest/deps/gtest/src/gtest-typed-test.o.d.raw
 -g -O2 -fdebug-prefix-map=/<>=. 

Bug#870121: mate-power-manager: sometimes hits not-reached assertion on startup

[Vlad Orlov]

Hi,

Here's a quick patch from upstream commit, it should fix the crash:

https://github.com/mate-desktop/mate-power-manager/commit/7facec455d825d317caffb8cafc4e4fec60065d9.patch

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

reassign 872402 golang-golang-x-sys
thanks

> Since 0.0~git20170629.0.1b3bb8de-1 a patch has made the source files shipped
> fail to build in mips* architectures. It does not FTBFS just because tests 
> have
> been disabled in a previous version, but it is making other packages FTBFS.
> 

I am being stupid and mixing x/tools with x/sys. Sorry about the noise.

-- 
Martín Ferrari (Tincho)

Processed: Re: Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Debian Bug Tracking System]

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

> reassign 872402 golang-golang-x-sys
Bug #872402 [golang-golang-x-tools-dev] golang-golang-x-tools-dev: Does not 
work on mips*
Bug reassigned from package 'golang-golang-x-tools-dev' to 
'golang-golang-x-sys'.
No longer marked as found in versions 0.0~git20170629.0.1b3bb8de-1.
Ignoring request to alter fixed versions of bug #872402 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Felipe Sateler]

Package: src:nodejs
Version: 6.11.2~dfsg-2
Severity: serious

nodejs failed to build with this error:

make[1]: Entering directory '/<>'
# Clean up any leftover processes but don't error if found.
ps awwx | grep Release/node | grep -v grep | cat
/usr/bin/python tools/test.py  -p tap \
--mode=release --flaky-tests=dontcare \
--arch=mips64el --timeout=3000 message parallel sequential
Can't determine the arch of: './node'

Can't determine the arch of: './node'

Can't determine the arch of: './node'

No tests to run.
Makefile:220: recipe for target 'test-ci-js' failed
make[1]: *** [test-ci-js] Error 1
make[1]: Leaving directory '/<>'


Full log at 
https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=6.11.2~dfsg-2=1502862893=0


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

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