Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

[Drew Parsons]

On Thu, 2017-08-24 at 03:22 +0200, Cyril Brulebois wrote:
> 
> Drew, such conversion from xsfbs to dh should really be accompanied
> by
> a thorough debdiff check:
> 
>   $ debdiff --controlfiles=ALL ../libxcursor*changes
> 
> which makes the breakage obvious:
> > Shlibs files of package libxcursor1: lines which differ (wdiff
> > format)
> > -
> > -
> > udeb: libXcursor 1 [--udeb-] {+libxcursor1-udeb+} (>> 1.1.2)
> 
> (This one is between the version in unstable and a build with the
> trivial, attached patch. You would have had the opposite between the
> -1 and -2 uploads.)
> 
> Also: DEBDIFF_CONTROLFILES=ALL in ~/.devscripts works fine.

Thanks KiBi.  I'll use that to check on libxres and libxdamage.

Drew

Bug#853494: marked as done (libindi: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 05:34:21 +
with message-id 
and subject line Bug#853494: fixed in libindi 1.2.0-4
has caused the Debian Bug report #853494,
regarding libindi: 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.)


-- 
853494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libindi
Version: 1.2.0-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/libindi_1.2.0-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

[...]
+#MISSING: 1.2.0-3# 
(optional=gccinternal)_ZN4INDI18AlignmentSubsystem40TelescopeDirectionVectorSupportFunctionsD0Ev@Base
 1.0.0
+#MISSING: 1.2.0-3# 
(optional=gccinternal)_ZN4INDI18AlignmentSubsystem40TelescopeDirectionVectorSupportFunctionsD1Ev@Base
 1.0.0
+#MISSING: 1.2.0-3# 
(optional=gccinternal)_ZN4INDI18AlignmentSubsystem40TelescopeDirectionVectorSupportFunctionsD2Ev@Base
 1.0.0
  
_ZNK4INDI18AlignmentSubsystem16InMemoryDatabase26CheckForDuplicateSyncPointERKNS0_22AlignmentDatabaseEntryEd@Base
 1.0.0
- 
(optional=gccinternal)_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
- 
_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE13_M_insert_auxIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
- 
(optional=gccinternal)_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.0
- 
_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 1.0.0
- 
(optional=gccinternal)_ZNSt6vectorIN4INDI18AlignmentSubsystem24TelescopeDirectionVectorESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.0
- 
_ZNSt6vectorIN4INDI18AlignmentSubsystem24TelescopeDirectionVectorESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 1.0.0
- 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0.0
+#MISSING: 1.2.0-3# 
(optional=gccinternal)_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
+#MISSING: 1.2.0-3# 
_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE13_M_insert_auxIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
+ 
_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.2.0-3
+#MISSING: 1.2.0-3# 
(optional=gccinternal)_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.0
+#MISSING: 1.2.0-3# 
_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 1.0.0
+ 
_ZNSt6vectorIN4INDI18AlignmentSubsystem22AlignmentDatabaseEntryESaIS2_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS2_S4_EERS7_@Base
 1.2.0-3
+ 
_ZNSt6vectorIN4INDI18AlignmentSubsystem24TelescopeDirectionVectorESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.2.0-3
+#MISSING: 1.2.0-3# 
(optional=gccinternal)_ZNSt6vectorIN4INDI18AlignmentSubsystem24TelescopeDirectionVectorESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.0

Bug#873052: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

[Adrian Bunk]

Source: gcl
Version: 2.6.12-53
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=gcl=arm64

...
/<>/unixport/raw_pcl_gcl /<>/unixport/ -libdir 
/<>/ < foo
GCL (GNU Common Lisp)  April 1994  67111603 pages
Building symbol table for /<>/unixport/raw_pcl_gcl ..
loading /<>/unixport/../lsp/gcl_export.lsp
Initializing gcl_defmacro.o
Initializing gcl_evalmacros.o
Initializing gcl_top.o
Initializing gcl_module.o
loading /<>/unixport/../lsp/gcl_autoload.lsp

>
#<"COMPILER" package>

>
#<"SLOOP" package>

>
#<"ANSI-LOOP" package>

>
#<"DEFPACKAGE" package>

>
#<"TK" package>

>
#<"FPE" package>

>
#<"CLTL1-COMPAT" package>

>
#<"SYSTEM" package>

SYSTEM>
T

SYSTEM>Initializing gcl_predlib.o
Initializing gcl_setf.o
Initializing gcl_arraylib.o
Initializing gcl_assert.o
Initializing gcl_defstruct.o
Initializing gcl_restart.o
Initializing gcl_describe.o
Initializing gcl_listlib.o
Initializing gcl_mislib.o
Initializing gcl_numlib.o
Initializing gcl_packlib.o
Initializing gcl_seq.o
Initializing gcl_seqlib.o
Initializing gcl_trace.o
Initializing gcl_sloop.o
Initializing gcl_serror.o
Initializing gcl_destructuring_bind.o
Initializing gcl_loop.o
Initializing gcl_defpackage.o
Initializing gcl_make_defpackage.o
Initializing gcl_sharp.o
Initializing gcl_sharp_uv.o
Initializing gcl_namestring.o
Initializing gcl_logical_pathname_translations.o
Initializing gcl_make_pathname.o
Initializing gcl_parse_namestring.o
Initializing gcl_translate_pathname.o
Initializing gcl_directory.o
Initializing gcl_merge_pathnames.o
Initializing gcl_truename.o
Initializing gcl_rename_file.o
Initializing gcl_wild_pathname_p.o
Initializing gcl_pathname_match_p.o
Initializing gcl_iolib.o
Initializing gcl_fpe.o
Initializing gcl_cmpinline.o
Initializing gcl_cmputil.o
Initializing gcl_debug.o

Unrecoverable error: Segmentation violation..
Aborted
makefile:93: recipe for target 'saved_pcl_gcl' failed
make[2]: *** [saved_pcl_gcl] Error 134
rm raw_pcl_gcl
make[2]: Leaving directory '/<>/unixport'
makefile:90: recipe for target 'unixport/saved_pcl_gcl' failed
make[1]: *** [unixport/saved_pcl_gcl] Error 2
rm h/mcompdefs.h
make[1]: Leaving directory '/<>'
debian/rules:109: recipe for target 'build-ansi-gprof-stamp' failed
make: *** [build-ansi-gprof-stamp] Error 2

Processed: tagging 853494

[Debian Bug Tracking System]

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

> tags 853494 + pending
Bug #853494 [src:libindi] libindi: ftbfs with GCC-7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#846314: marked as done (alot: please use python-gpg instead of python-gpgme)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 03:34:11 +
with message-id 
and subject line Bug#866027: fixed in alot 0.6-1
has caused the Debian Bug report #866027,
regarding alot: please use python-gpg instead of python-gpgme
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.)


-- 
866027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alot
Version: 0.3.6-1
Severity: normal
Tags: patch upstream
Control: affects -1 python-gpg python-gpgme

Please use the python-gpg package, which is supplied by GnuPG and
GPGME upstream, rather than the python-gpgme package, which is not
being actively maintained.

This will require some minor changes in the source, which i've already
made patches for upstream:

https://github.com/pazz/alot/pull/906

they don't apply cleanly to 0.3.6, though; they should be easier to
apply if debian updates to a more recent version of alot.

  --dkg

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

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

Versions of packages alot depends on:
ii  python-configobj  5.0.6-2
ii  python-gpgme  0.3-1.2
ii  python-magic  1:5.29-1
ii  python-notmuch0.23.3+16~g5ff385c+1
ii  python-twisted16.5.0-1
ii  python-urwid  1.3.1-2+b1
pn  python:any

Versions of packages alot recommends:
ii  links2.13-1
ii  notmuch  0.23.3+16~g5ff385c+1
ii  w3m  0.5.3-33

Versions of packages alot suggests:
pn  alot-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.6-1

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated alot 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: Sun, 20 Aug 2017 15:40:54 -0700
Source: alot
Binary: alot alot-doc
Architecture: source
Version: 0.6-1
Distribution: unstable
Urgency: low
Maintainer: Python Applications Packaging Team 

Changed-By: Jordan Justen 
Description:
 alot   - Text mode MUA using notmuch mail
 alot-doc   - Text mode MUA using notmuch mail - documentation
Closes: 846314 866027
Changes:
 alot (0.6-1) unstable; urgency=low
 .
   * New upstream release
   * Add PGP signature validation to watch file with pazz's signature
 with fingerprint B7838D65FEE80DED1DCA494D94340367D7D6C5AA.
   * Depend on python-gpg rather than pygpgme (Closes: #846314, #866027)
   * Update debian patches for 0.6 release
   * Add procps build-dependency since ps is used by tests
   * Set LC_ALL=C.UTF-8 in rules to fix two failing tests that make use of
 unicode characters.
Checksums-Sha1:
 e9dbda7b40a4ddca84899012a1127b2437fe0ac3 2519 alot_0.6-1.dsc
 2233b73c0277173c440284cbd16eb37df0fb9b8a 1526781 alot_0.6.orig.tar.gz
 84a478604f7ea0c0175423dfbdfb3cfc60507c20 195 alot_0.6.orig.tar.gz.asc
 69c859c2e7b01e821526e9e81813a762bcd36c51 6720 alot_0.6-1.debian.tar.xz
 630a8d41ebfad71c4eb4822b55fa1fdc23013add 8641 alot_0.6-1_amd64.buildinfo
Checksums-Sha256:
 b067f3fc71c9824406fe379f283eeaba8062c7b422ae8e562854d050f69c60ea 2519 
alot_0.6-1.dsc
 36b4b3471e2815b3fac320d3b82be5c4252dce119d3d3112dcbf69dd67f0acb2 1526781 
alot_0.6.orig.tar.gz
 98af49e6aad0a02f41f9070b774820468913687426a1090011aaadd14c567bb0 195 
alot_0.6.orig.tar.gz.asc
 be9b0dfe60faf8687ba8349f8aa3d63e80c35ab1292161082382603cd68e6632 6720 
alot_0.6-1.debian.tar.xz
 2c745c319af6b686bd8ee670776056073c861d599af0e0b2a9d2ee9bb047500a 8641 
alot_0.6-1_amd64.buildinfo
Files:
 

Bug#866027: marked as done (alot: Migrate from pygpgme to python-gpg)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 03:34:11 +
with message-id 
and subject line Bug#846314: fixed in alot 0.6-1
has caused the Debian Bug report #846314,
regarding alot: Migrate from pygpgme to python-gpg
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.)


-- 
846314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alot
Version: 0.3.6-1
Severity: important

Hi,

your package depends on the obsolete and abandoned python library
pygpgme. I've just filed an RC bug against that package, so that we
don't release buster with an essentially unmaintained package:



The packages python-gpg and python3-gpg (built from source package
gpgme1.0) provide python bindings for interactions with the gpgme
library. Both packages are already available in stretch.

Upstream of alot is already working on migrating away from the obsolete
pypgpme package:



Regards,
Tobias



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.6-1

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated alot 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: Sun, 20 Aug 2017 15:40:54 -0700
Source: alot
Binary: alot alot-doc
Architecture: source
Version: 0.6-1
Distribution: unstable
Urgency: low
Maintainer: Python Applications Packaging Team 

Changed-By: Jordan Justen 
Description:
 alot   - Text mode MUA using notmuch mail
 alot-doc   - Text mode MUA using notmuch mail - documentation
Closes: 846314 866027
Changes:
 alot (0.6-1) unstable; urgency=low
 .
   * New upstream release
   * Add PGP signature validation to watch file with pazz's signature
 with fingerprint B7838D65FEE80DED1DCA494D94340367D7D6C5AA.
   * Depend on python-gpg rather than pygpgme (Closes: #846314, #866027)
   * Update debian patches for 0.6 release
   * Add procps build-dependency since ps is used by tests
   * Set LC_ALL=C.UTF-8 in rules to fix two failing tests that make use of
 unicode characters.
Checksums-Sha1:
 e9dbda7b40a4ddca84899012a1127b2437fe0ac3 2519 alot_0.6-1.dsc
 2233b73c0277173c440284cbd16eb37df0fb9b8a 1526781 alot_0.6.orig.tar.gz
 84a478604f7ea0c0175423dfbdfb3cfc60507c20 195 alot_0.6.orig.tar.gz.asc
 69c859c2e7b01e821526e9e81813a762bcd36c51 6720 alot_0.6-1.debian.tar.xz
 630a8d41ebfad71c4eb4822b55fa1fdc23013add 8641 alot_0.6-1_amd64.buildinfo
Checksums-Sha256:
 b067f3fc71c9824406fe379f283eeaba8062c7b422ae8e562854d050f69c60ea 2519 
alot_0.6-1.dsc
 36b4b3471e2815b3fac320d3b82be5c4252dce119d3d3112dcbf69dd67f0acb2 1526781 
alot_0.6.orig.tar.gz
 98af49e6aad0a02f41f9070b774820468913687426a1090011aaadd14c567bb0 195 
alot_0.6.orig.tar.gz.asc
 be9b0dfe60faf8687ba8349f8aa3d63e80c35ab1292161082382603cd68e6632 6720 
alot_0.6-1.debian.tar.xz
 2c745c319af6b686bd8ee670776056073c861d599af0e0b2a9d2ee9bb047500a 8641 
alot_0.6-1_amd64.buildinfo
Files:
 834a8d3ba20938c76d68db2682aab666 2519 mail optional alot_0.6-1.dsc
 db355cfb3e905aede50e757cb723ad4d 1526781 mail optional alot_0.6.orig.tar.gz
 a4690fc6a7855e80988fc047c777c085 195 mail optional alot_0.6.orig.tar.gz.asc
 110d2aeaccba135eb79f9e8a7a912fec 6720 mail optional alot_0.6-1.debian.tar.xz
 cbe9acc2c714179eb6f69ba4e7283ca9 8641 mail optional alot_0.6-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCAA1FiEElFhU6KL81LF4wVq58sulx4+9g+EFAlmeROcXHGpvc2NoQG1p
c3Rlci1tdWZmaW4uZGUACgkQ8sulx4+9g+HUzxAAprLuGXH3y2bTP9lPVMMtT4Hq
/BK+uG9V3YYjd1URBDzAXX/LO3em0+cy311P3JFyRbXRmicz8K16vUDbE8eMXAMf
oMfRVMAE4OXpei4HHkldueDyPMKGyk3QnYacjd/jpavLsGHwD9t1fImZuXM7gFM2
/qBunwuYTknmipQ4fRD6C1/Ng0AuJUIY4q7Q8LXiNMZzKqXNxCYxT+kKsYhMvsNO
d3ko6h2e66IUUNN8Blzcq98Yy1wlcgOQYUHvuOa7jLKMcGl38CakHAC2IuuiKQjg

Bug#846314: marked as done (alot: please use python-gpg instead of python-gpgme)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 03:34:11 +
with message-id 
and subject line Bug#846314: fixed in alot 0.6-1
has caused the Debian Bug report #846314,
regarding alot: please use python-gpg instead of python-gpgme
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.)


-- 
846314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alot
Version: 0.3.6-1
Severity: normal
Tags: patch upstream
Control: affects -1 python-gpg python-gpgme

Please use the python-gpg package, which is supplied by GnuPG and
GPGME upstream, rather than the python-gpgme package, which is not
being actively maintained.

This will require some minor changes in the source, which i've already
made patches for upstream:

https://github.com/pazz/alot/pull/906

they don't apply cleanly to 0.3.6, though; they should be easier to
apply if debian updates to a more recent version of alot.

  --dkg

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

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

Versions of packages alot depends on:
ii  python-configobj  5.0.6-2
ii  python-gpgme  0.3-1.2
ii  python-magic  1:5.29-1
ii  python-notmuch0.23.3+16~g5ff385c+1
ii  python-twisted16.5.0-1
ii  python-urwid  1.3.1-2+b1
pn  python:any

Versions of packages alot recommends:
ii  links2.13-1
ii  notmuch  0.23.3+16~g5ff385c+1
ii  w3m  0.5.3-33

Versions of packages alot suggests:
pn  alot-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.6-1

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated alot 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: Sun, 20 Aug 2017 15:40:54 -0700
Source: alot
Binary: alot alot-doc
Architecture: source
Version: 0.6-1
Distribution: unstable
Urgency: low
Maintainer: Python Applications Packaging Team 

Changed-By: Jordan Justen 
Description:
 alot   - Text mode MUA using notmuch mail
 alot-doc   - Text mode MUA using notmuch mail - documentation
Closes: 846314 866027
Changes:
 alot (0.6-1) unstable; urgency=low
 .
   * New upstream release
   * Add PGP signature validation to watch file with pazz's signature
 with fingerprint B7838D65FEE80DED1DCA494D94340367D7D6C5AA.
   * Depend on python-gpg rather than pygpgme (Closes: #846314, #866027)
   * Update debian patches for 0.6 release
   * Add procps build-dependency since ps is used by tests
   * Set LC_ALL=C.UTF-8 in rules to fix two failing tests that make use of
 unicode characters.
Checksums-Sha1:
 e9dbda7b40a4ddca84899012a1127b2437fe0ac3 2519 alot_0.6-1.dsc
 2233b73c0277173c440284cbd16eb37df0fb9b8a 1526781 alot_0.6.orig.tar.gz
 84a478604f7ea0c0175423dfbdfb3cfc60507c20 195 alot_0.6.orig.tar.gz.asc
 69c859c2e7b01e821526e9e81813a762bcd36c51 6720 alot_0.6-1.debian.tar.xz
 630a8d41ebfad71c4eb4822b55fa1fdc23013add 8641 alot_0.6-1_amd64.buildinfo
Checksums-Sha256:
 b067f3fc71c9824406fe379f283eeaba8062c7b422ae8e562854d050f69c60ea 2519 
alot_0.6-1.dsc
 36b4b3471e2815b3fac320d3b82be5c4252dce119d3d3112dcbf69dd67f0acb2 1526781 
alot_0.6.orig.tar.gz
 98af49e6aad0a02f41f9070b774820468913687426a1090011aaadd14c567bb0 195 
alot_0.6.orig.tar.gz.asc
 be9b0dfe60faf8687ba8349f8aa3d63e80c35ab1292161082382603cd68e6632 6720 
alot_0.6-1.debian.tar.xz
 2c745c319af6b686bd8ee670776056073c861d599af0e0b2a9d2ee9bb047500a 8641 
alot_0.6-1_amd64.buildinfo
Files:
 

Bug#866027: marked as done (alot: Migrate from pygpgme to python-gpg)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 03:34:11 +
with message-id 
and subject line Bug#866027: fixed in alot 0.6-1
has caused the Debian Bug report #866027,
regarding alot: Migrate from pygpgme to python-gpg
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.)


-- 
866027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alot
Version: 0.3.6-1
Severity: important

Hi,

your package depends on the obsolete and abandoned python library
pygpgme. I've just filed an RC bug against that package, so that we
don't release buster with an essentially unmaintained package:



The packages python-gpg and python3-gpg (built from source package
gpgme1.0) provide python bindings for interactions with the gpgme
library. Both packages are already available in stretch.

Upstream of alot is already working on migrating away from the obsolete
pypgpme package:



Regards,
Tobias



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.6-1

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated alot 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: Sun, 20 Aug 2017 15:40:54 -0700
Source: alot
Binary: alot alot-doc
Architecture: source
Version: 0.6-1
Distribution: unstable
Urgency: low
Maintainer: Python Applications Packaging Team 

Changed-By: Jordan Justen 
Description:
 alot   - Text mode MUA using notmuch mail
 alot-doc   - Text mode MUA using notmuch mail - documentation
Closes: 846314 866027
Changes:
 alot (0.6-1) unstable; urgency=low
 .
   * New upstream release
   * Add PGP signature validation to watch file with pazz's signature
 with fingerprint B7838D65FEE80DED1DCA494D94340367D7D6C5AA.
   * Depend on python-gpg rather than pygpgme (Closes: #846314, #866027)
   * Update debian patches for 0.6 release
   * Add procps build-dependency since ps is used by tests
   * Set LC_ALL=C.UTF-8 in rules to fix two failing tests that make use of
 unicode characters.
Checksums-Sha1:
 e9dbda7b40a4ddca84899012a1127b2437fe0ac3 2519 alot_0.6-1.dsc
 2233b73c0277173c440284cbd16eb37df0fb9b8a 1526781 alot_0.6.orig.tar.gz
 84a478604f7ea0c0175423dfbdfb3cfc60507c20 195 alot_0.6.orig.tar.gz.asc
 69c859c2e7b01e821526e9e81813a762bcd36c51 6720 alot_0.6-1.debian.tar.xz
 630a8d41ebfad71c4eb4822b55fa1fdc23013add 8641 alot_0.6-1_amd64.buildinfo
Checksums-Sha256:
 b067f3fc71c9824406fe379f283eeaba8062c7b422ae8e562854d050f69c60ea 2519 
alot_0.6-1.dsc
 36b4b3471e2815b3fac320d3b82be5c4252dce119d3d3112dcbf69dd67f0acb2 1526781 
alot_0.6.orig.tar.gz
 98af49e6aad0a02f41f9070b774820468913687426a1090011aaadd14c567bb0 195 
alot_0.6.orig.tar.gz.asc
 be9b0dfe60faf8687ba8349f8aa3d63e80c35ab1292161082382603cd68e6632 6720 
alot_0.6-1.debian.tar.xz
 2c745c319af6b686bd8ee670776056073c861d599af0e0b2a9d2ee9bb047500a 8641 
alot_0.6-1_amd64.buildinfo
Files:
 834a8d3ba20938c76d68db2682aab666 2519 mail optional alot_0.6-1.dsc
 db355cfb3e905aede50e757cb723ad4d 1526781 mail optional alot_0.6.orig.tar.gz
 a4690fc6a7855e80988fc047c777c085 195 mail optional alot_0.6.orig.tar.gz.asc
 110d2aeaccba135eb79f9e8a7a912fec 6720 mail optional alot_0.6-1.debian.tar.xz
 cbe9acc2c714179eb6f69ba4e7283ca9 8641 mail optional alot_0.6-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCAA1FiEElFhU6KL81LF4wVq58sulx4+9g+EFAlmeROcXHGpvc2NoQG1p
c3Rlci1tdWZmaW4uZGUACgkQ8sulx4+9g+HUzxAAprLuGXH3y2bTP9lPVMMtT4Hq
/BK+uG9V3YYjd1URBDzAXX/LO3em0+cy311P3JFyRbXRmicz8K16vUDbE8eMXAMf
oMfRVMAE4OXpei4HHkldueDyPMKGyk3QnYacjd/jpavLsGHwD9t1fImZuXM7gFM2
/qBunwuYTknmipQ4fRD6C1/Ng0AuJUIY4q7Q8LXiNMZzKqXNxCYxT+kKsYhMvsNO
d3ko6h2e66IUUNN8Blzcq98Yy1wlcgOQYUHvuOa7jLKMcGl38CakHAC2IuuiKQjg

Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

[Cyril Brulebois]

Control: reassign -1 libxcursor1 1:1.1.14-2
Control: retitle -1 libxcursor1: broken shlibs for the udeb
Control: tag -1 patch

(Minor nitpick.)

Jeremy Bicha  (2017-08-23):
> When libxcursor was converted to dh's rules, the line defining PACKAGE
> was accidentally removed.
> 
> So this line:
> dh_makeshlibs -V "libxcursor1 (>> 1.1.2)" --add-udeb=$(PACKAGE)-udeb
> 
> gets interpreted as:
> dh_makeshlibs -V "libxcursor1 (>> 1.1.2)" --add-udeb=-udeb
> 
> Which leads to packages like gtk+3.0 failing to build from source:
> 
> =
> dpkg-shlibdeps: warning: can't parse dependency -udeb (>> 1.1.2)
> dpkg-shlibdeps: error: invalid dependency got generated:
> libepoxy0-udeb (>= 1.3), libx11-6-udeb (>= 2:1.6.0), -udeb (>> 1.1.2),
> libgtk-3-0-udeb (>= 3.22.19), libxinerama1-udeb,
> libgdk-pixbuf2.0-0-udeb (>= 2.36.5), libxi6-udeb (>= 2:1.6.99.1),
> libatk-bridge-2.0-0-udeb, libglib2.0-udeb (>= 2.53.4), fontconfig-udeb
> (>= 2.11.94), libxext6-udeb (>= 2:1.3.0), libc6-udeb (>= 2.24),
> libatk1.0-udeb (>= 2.24.0), libcairo2-udeb (>= 1.14.0),
> libpango1.0-udeb (>= 1.40.11), libcairo2-udeb (>= 1.10.0)
> dh_shlibdeps: dpkg-shlibdeps -Tdebian/libgtk-3-0-udeb.substvars -tudeb
> debian/libgtk-3-0-udeb/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.19
> debian/libgtk-3-0-udeb/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.19
> returned exit code 255
> dh_shlibdeps: Aborting due to earlier error
> =

Thanks for filing this bug report, Jeremy.

Drew, such conversion from xsfbs to dh should really be accompanied by
a thorough debdiff check:

  $ debdiff --controlfiles=ALL ../libxcursor*changes

which makes the breakage obvious:
| Shlibs files of package libxcursor1: lines which differ (wdiff format)
| --
| udeb: libXcursor 1 [--udeb-] {+libxcursor1-udeb+} (>> 1.1.2)

(This one is between the version in unstable and a build with the
trivial, attached patch. You would have had the opposite between the
-1 and -2 uploads.)

Also: DEBDIFF_CONTROLFILES=ALL in ~/.devscripts works fine.


KiBi.
From 3e91691c6274547e1aa8a033447f993ff617d80c Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Thu, 24 Aug 2017 01:20:00 +
Subject: [PATCH] debian/rules: Set PACKAGE to libxcursor1 (Closes: #873041).

Otherwise dh_makeshlibs is called with an incomplete package name for
the udeb, which breaks reverse dependencies.
---
 debian/changelog | 6 ++
 debian/rules | 3 +++
 2 files changed, 9 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 9ccc9f8..b1402c0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,14 @@
 libxcursor (1:1.1.14-3) UNRELEASED; urgency=medium
 
+  [ Drew Parsons ]
   * Team upload.
   * debian/control Homepage: https://www.x.org
 
+  [ Cyril Brulebois ]
+  * debian/rules: Set PACKAGE to libxcursor1. Otherwise dh_makeshlibs is
+called with an incomplete package name for the udeb, which breaks
+reverse dependencies (Closes: #873041).
+
  -- Drew Parsons   Sun, 20 Aug 2017 13:54:29 +0800
 
 libxcursor (1:1.1.14-2) unstable; urgency=medium
diff --git a/debian/rules b/debian/rules
index 61ad145..3619536 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,4 +1,7 @@
 #!/usr/bin/make -f
+
+PACKAGE = libxcursor1
+
 %:
 	dh $@
 
-- 
2.14.0



signature.asc
Description: Digital signature

Processed: Re: Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libxcursor1 1:1.1.14-2
Bug #873041 [libxcursor1-udeb] libxcursor1-udeb: Broken dpkg-shlibdeps rule
Bug reassigned from package 'libxcursor1-udeb' to 'libxcursor1'.
No longer marked as found in versions libxcursor/1:1.1.14-2.
Ignoring request to alter fixed versions of bug #873041 to the same values 
previously set
Bug #873041 [libxcursor1] libxcursor1-udeb: Broken dpkg-shlibdeps rule
Marked as found in versions libxcursor/1:1.1.14-2.
> retitle -1 libxcursor1: broken shlibs for the udeb
Bug #873041 [libxcursor1] libxcursor1-udeb: Broken dpkg-shlibdeps rule
Changed Bug title to 'libxcursor1: broken shlibs for the udeb' from 
'libxcursor1-udeb: Broken dpkg-shlibdeps rule'.
> tag -1 patch
Bug #873041 [libxcursor1] libxcursor1: broken shlibs for the udeb
Added tag(s) patch.

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

Bug#872598: udev-udeb: no input in graphical installer

[Cyril Brulebois]

.oO( Third time is the charm? )

Cyril Brulebois  (2017-08-24):
> Michael Biebl  (2017-08-24):
> > Am 23.08.2017 um 23:57 schrieb Cyril Brulebois:
> > 
> > > My NMU FTBFSes on mips64el:
> > >   
> > > https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0
> > > 
> > > James Cowgill mentioned this gcc bug report:
> > >   https://bugs.debian.org/871514
> > > 
> > > so I think I might duplicate the rules file in src:debian-installer and
> > > work around the missing file by putting it into place manually, which is
> > > somewhat ugly but means we're no longer blocking on the systemd update.
> > 
> > I wouldn't mind if you forced the compiler to be GCC 6 in src:systemd
> > until this bug is fixed.
> 
> The attached patch seems to do the trick, will upload after a full build
> inside sbuild, then open a bug report as you suggested on IRC, so that
> you think about reverting this when the gcc-7 bug is fixed.

I initially meant to add g++ and CXX and should have, but it seemed
not to be needed… until it failed on buildds since there are checks
building in c++ mode; which I didn't catch locally because the wrong
chroot has been used while build testing… Sorry for that.

Hopefully attaching the last debdiff…


KiBi.
diff -Nru systemd-234/debian/changelog systemd-234/debian/changelog
--- systemd-234/debian/changelog	2017-08-24 00:53:09.0 +0200
+++ systemd-234/debian/changelog	2017-08-24 02:45:13.0 +0200
@@ -1,3 +1,12 @@
+systemd (234-2.3) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Also switch to g++-6 temporarily (needed for some tests):
+- Add g++-6 to Build-Depends
+- Export CXX = g++-6
+
+ -- Cyril Brulebois   Thu, 24 Aug 2017 02:40:53 +0200
+
 systemd (234-2.2) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru systemd-234/debian/control systemd-234/debian/control
--- systemd-234/debian/control	2017-08-24 00:45:38.0 +0200
+++ systemd-234/debian/control	2017-08-24 02:27:16.0 +0200
@@ -54,6 +54,7 @@
libcap2-bin ,
iproute2 ,
gcc-6,
+   g++-6,
 
 Package: systemd
 Architecture: linux-any
diff -Nru systemd-234/debian/rules systemd-234/debian/rules
--- systemd-234/debian/rules	2017-08-24 00:45:44.0 +0200
+++ systemd-234/debian/rules	2017-08-24 02:28:10.0 +0200
@@ -5,6 +5,7 @@
 
 export LC_ALL = C.UTF-8
 export CC = gcc-6
+export CXX = g++-6
 
 include /usr/share/dpkg/default.mk
 


signature.asc
Description: Digital signature

Bug#873041: libxcursor1-udeb: Broken dpkg-shlibdeps rule

[Jeremy Bicha]

Package: libxcursor1-udeb
Version: 1:1.1.14-2
Severity: serious
X-Debbugs-CC: debian-b...@lists.debian.org

When libxcursor was converted to dh's rules, the line defining PACKAGE
was accidentally removed.

So this line:
dh_makeshlibs -V "libxcursor1 (>> 1.1.2)" --add-udeb=$(PACKAGE)-udeb

gets interpreted as:
dh_makeshlibs -V "libxcursor1 (>> 1.1.2)" --add-udeb=-udeb

Which leads to packages like gtk+3.0 failing to build from source:

=
dpkg-shlibdeps: warning: can't parse dependency -udeb (>> 1.1.2)
dpkg-shlibdeps: error: invalid dependency got generated:
libepoxy0-udeb (>= 1.3), libx11-6-udeb (>= 2:1.6.0), -udeb (>> 1.1.2),
libgtk-3-0-udeb (>= 3.22.19), libxinerama1-udeb,
libgdk-pixbuf2.0-0-udeb (>= 2.36.5), libxi6-udeb (>= 2:1.6.99.1),
libatk-bridge-2.0-0-udeb, libglib2.0-udeb (>= 2.53.4), fontconfig-udeb
(>= 2.11.94), libxext6-udeb (>= 2:1.3.0), libc6-udeb (>= 2.24),
libatk1.0-udeb (>= 2.24.0), libcairo2-udeb (>= 1.14.0),
libpango1.0-udeb (>= 1.40.11), libcairo2-udeb (>= 1.10.0)
dh_shlibdeps: dpkg-shlibdeps -Tdebian/libgtk-3-0-udeb.substvars -tudeb
debian/libgtk-3-0-udeb/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.19
debian/libgtk-3-0-udeb/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.19
returned exit code 255
dh_shlibdeps: Aborting due to earlier error
=

Thanks,
Jeremy Bicha

Bug#853534: marked as done (mahimahi: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 00:50:36 +
with message-id 
and subject line Bug#853534: fixed in mahimahi 0.97-1
has caused the Debian Bug report #853534,
regarding mahimahi: 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.)


-- 
853534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mahimahi
Version: 0.96-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/mahimahi_0.96-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

[...]
[libprotobuf WARNING google/protobuf/compiler/parser.cc:547] No syntax 
specified for the proto file: http_record.proto. Please use 'syntax = 
"proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to 
proto2 syntax.)
make  all-am
make[5]: Entering directory '/<>/src/protobufs'
g++ -DHAVE_CONFIG_H -I. -I../..  -pthread -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o http_record.pb.o http_record.pb.cc
rm -f libhttprecordprotos.a
ar cru libhttprecordprotos.a  http_record.pb.o  
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib libhttprecordprotos.a
make[5]: Leaving directory '/<>/src/protobufs'
make[4]: Leaving directory '/<>/src/protobufs'
Making all in util
make[4]: Entering directory '/<>/src/util'
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o ezio.o ezio.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o file_descriptor.o file_descriptor.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o netdevice.o netdevice.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o timestamp.o timestamp.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o child_process.o child_process.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o signalfd.o signalfd.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o socket.o socket.cc
g++ -DHAVE_CONFIG_H -I. -I../..  -std=c++11 -pthread -Wdate-time 
-D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra -Weffc++ -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o address.o address.cc
address.cc: In constructor 'Address::Address(const 

Bug#871815: marked as done (asn1c FTBFS on ppc64el: FAIL: check-REAL)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 23:19:15 +
with message-id 
and subject line Bug#871815: fixed in asn1c 0.9.28+dfsg-2
has caused the Debian Bug report #871815,
regarding asn1c FTBFS on ppc64el: FAIL: check-REAL
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.)


-- 
871815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asn1c
Version: 0.9.28+dfsg-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=asn1c=ppc64el=0.9.28%2Bdfsg-1=1502306601=0

...
check-REAL: check-REAL.c:58: check_str_representation: Assertion `!strcmp(s0, 
sample)' failed.
361: Checking 0->["0"] against ["0"] (canonical follows...)
361: Checking 0->["0"] against ["0"] (canonical)
365: Checking -0->["-0"] against ["-0"] (canonical follows...)
365: Checking -0->["-0"] against ["-0"] (canonical)
373: Checking -0->["-0"] against ["-0"] (canonical follows...)
373: Checking -0->["-0"] against ["-0"] (canonical)
374: Checking -0->["-0"] against ["-0"] (canonical follows...)
374: Checking -0->["-0"] against ["-0"] (canonical)
375: Checking -0->["-0"] against ["-0"] (canonical follows...)
375: Checking -0->["-0"] against ["-0"] (canonical)
376: Checking -0->["-0"] against ["-0"] (canonical follows...)
376: Checking -0->["-0"] against ["-0"] (canonical)
382: Checking inf->[""] against [""] (canonical 
follows...)
382: Checking inf->[""] against [""] (canonical)
383: Checking -inf->[""] against [""] 
(canonical follows...)
383: Checking -inf->[""] against [""] 
(canonical)
384: Checking nan->[""] against [""] (canonical 
follows...)
384: Checking nan->[""] against [""] (canonical)
389: Checking 0->["0"] against ["0"] (canonical follows...)
389: Checking 0->["0"] against ["0"] (canonical)
392: Checking 0->["0"] against ["0"] (canonical follows...)
392: Checking 0->["0"] against ["0"] (canonical)
395: Checking 0->["0"] against ["0"] (canonical follows...)
395: Checking 0->["0"] against ["0"] (canonical)
398: Checking 0->["0"] against ["0"] (canonical follows...)
398: Checking 0->["0"] against ["0"] (canonical)
401: Checking 0->["0"] against ["0"] (canonical follows...)
401: Checking 0->["0"] against ["0"] (canonical)
404: Checking -0->["-0"] against ["-0"] (canonical follows...)
404: Checking -0->["-0"] against ["-0"] (canonical)
407: Checking -0->["-0"] against ["-0"] (canonical follows...)
407: Checking -0->["-0"] against ["-0"] (canonical)
411: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
411: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
414: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
414: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
417: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
417: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
420: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
420: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
423: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
423: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
426: Checking -1->["-1.0"] against ["-1.0"] (canonical follows...)
426: Checking -1->["-1.0E0"] against ["-1.0E0"] (canonical)
429: Checking -1->["-1.0"] against ["-1.0"] (canonical follows...)
429: Checking -1->["-1.0E0"] against ["-1.0E0"] (canonical)
440: Checking 0->["0"] against ["0"] (canonical follows...)
440: Checking 0->["0"] against ["0"] (canonical)
443: Checking 0->["0"] against ["0"] (canonical follows...)
443: Checking 0->["0"] against ["0"] (canonical)
446: Checking 0->["0"] against ["0"] (canonical follows...)
446: Checking 0->["0"] against ["0"] (canonical)
449: Checking 0->["0"] against ["0"] (canonical follows...)
449: Checking 0->["0"] against ["0"] (canonical)
452: Checking 0->["0"] against ["0"] (canonical follows...)
452: Checking 0->["0"] against ["0"] (canonical)
455: Checking -0->["-0"] against ["-0"] (canonical follows...)
455: Checking -0->["-0"] against ["-0"] (canonical)
458: Checking -0->["-0"] against ["-0"] (canonical follows...)
458: Checking -0->["-0"] against ["-0"] (canonical)
463: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
463: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
466: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
466: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
469: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
469: Checking 1->["1.0E0"] against ["1.0E0"] (canonical)
472: Checking 1->["1.0"] against ["1.0"] (canonical follows...)
472: Checking 1->["1.0E0"] against ["1.0E0"] 

Bug#872598: udev-udeb: no input in graphical installer

[Cyril Brulebois]

Michael Biebl  (2017-08-24):
> Am 23.08.2017 um 23:57 schrieb Cyril Brulebois:
> 
> > My NMU FTBFSes on mips64el:
> >   
> > https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0
> > 
> > James Cowgill mentioned this gcc bug report:
> >   https://bugs.debian.org/871514
> > 
> > so I think I might duplicate the rules file in src:debian-installer and
> > work around the missing file by putting it into place manually, which is
> > somewhat ugly but means we're no longer blocking on the systemd update.
> 
> I wouldn't mind if you forced the compiler to be GCC 6 in src:systemd
> until this bug is fixed.

The attached patch seems to do the trick, will upload after a full build
inside sbuild, then open a bug report as you suggested on IRC, so that
you think about reverting this when the gcc-7 bug is fixed.


KiBi.
diff -Nru systemd-234/debian/changelog systemd-234/debian/changelog
--- systemd-234/debian/changelog	2017-08-23 18:41:34.0 +
+++ systemd-234/debian/changelog	2017-08-23 22:53:09.0 +
@@ -1,3 +1,13 @@
+systemd (234-2.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Switch to gcc-6 on all architectures, working around an FTBFS on mips64el,
+apparently due to a gcc-7 bug (See: #871514):
+- Add gcc-6 to Build-Depends in debian/control
+- Export CC = gcc-6 in debian/rules
+
+ -- Cyril Brulebois   Wed, 23 Aug 2017 22:53:09 +
+
 systemd (234-2.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru systemd-234/debian/control systemd-234/debian/control
--- systemd-234/debian/control	2017-07-20 13:13:42.0 +
+++ systemd-234/debian/control	2017-08-23 22:45:38.0 +
@@ -53,6 +53,7 @@
tzdata ,
libcap2-bin ,
iproute2 ,
+   gcc-6,
 
 Package: systemd
 Architecture: linux-any
diff -Nru systemd-234/debian/rules systemd-234/debian/rules
--- systemd-234/debian/rules	2017-07-20 13:13:42.0 +
+++ systemd-234/debian/rules	2017-08-23 22:45:44.0 +
@@ -4,6 +4,7 @@
 #export DEB_BUILD_OPTIONS = nostrip
 
 export LC_ALL = C.UTF-8
+export CC = gcc-6
 
 include /usr/share/dpkg/default.mk
 


signature.asc
Description: Digital signature

Bug#867464: marked as done (python3-radicale: missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 22:50:05 +
with message-id 
and subject line Bug#867464: fixed in radicale 2.1.4-2
has caused the Debian Bug report #867464,
regarding python3-radicale: missing dependencies
to be marked as done.

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

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


-- 
867464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-radicale
Version: 1.1.1+20160115-4
Severity: serious
Tags: patch

Due to a cut'n'paste error there are no package dependencies.

Fix (also removes the deprecated XB-Python3-Version):

--- debian/control.old  2017-07-06 17:49:43.0 +
+++ debian/control  2017-07-06 17:50:24.0 +
@@ -73,9 +73,8 @@
 Package: python3-radicale
 Section: python
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-XB-Python3-Version: ${python:Versions}
+Depends: ${misc:Depends}, ${python3:Depends}
+Provides: ${python3:Provides}
 Description: simple calendar and addressbook server - python3 module
  Radicale is a CalDAV (calendar) and CardDAV (contact) server.
  .
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 2.1.4-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated radicale 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, 24 Aug 2017 00:29:32 +0200
Source: radicale
Binary: radicale python3-radicale
Architecture: source
Version: 2.1.4-2
Distribution: experimental
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 python3-radicale - simple calendar and addressbook server - python3 module
 radicale   - simple calendar and addressbook server - daemon
Closes: 867464
Changes:
 radicale (2.1.4-2) experimental; urgency=medium
 .
   * Fix resolve python-related dependencies and provisions, and drop
 deprecated (and bogus, for python3 package) XB-Python-Version field.
 Closes: Bug#867464. Thanks to Adrian Bunk.
   * Declare compliance with Debian Policy 4.1.0.
Checksums-Sha1:
 a953fceb89370cdc72ba3921dfe3cfeceab9320e 2198 radicale_2.1.4-2.dsc
 f161db645f8c7fa42620a31a721f06e7167a5874 28580 radicale_2.1.4-2.debian.tar.xz
 2190db7c12c697353055195a4ad36f472501435c 6310 radicale_2.1.4-2_amd64.buildinfo
Checksums-Sha256:
 413495af4db6cc3995960e6e68fe21bed340aabe07283ee4a6e300fb78266c26 2198 
radicale_2.1.4-2.dsc
 382f1886ce27aa11a304cccfb82443557827adabe8d5af63f71e8bc43c0c86e3 28580 
radicale_2.1.4-2.debian.tar.xz
 0556ea5e0df12a1f0eda8ac371fe8fabdc61c61e47e0eaf85cbc3b2a904762a1 6310 
radicale_2.1.4-2_amd64.buildinfo
Files:
 18cc77fc5eaf61116e34345e22b8e8de 2198 web optional radicale_2.1.4-2.dsc
 bb1c57650a2b1d01d9fe1cf33fa6d657 28580 web optional 
radicale_2.1.4-2.debian.tar.xz
 9e43d8d4ae6d134c35edf8d72f31908c 6310 web optional 
radicale_2.1.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmeA0kACgkQLHwxRsGg
ASE6Bg/9HuGzcIjYfza9uovnZ6ESJk7cxMz9DzgbbyqDmnTfph1dV5laJz2tjyWZ
voxwtl4t11b+UGY4rlN14v+ZDe+zTHKocCxyclMp+g52YTrsxsd2fAf1rB0kvcv3
1wf8Y1PJSMtmyCRviAs5p1bjPM6GOUcUIqIWAlq7BYjnEpAkX5DoZeNaWxzkbHwB
SLSua586BjrWRljNCLQ36zNaAkr6aT1FHw5Sog0TwgxZktPIwz5M4BgZn9R/wfTG
vdK8gjmgcRRp3YusMmkpzax8IFcZ+rnyOZrJmZMb0Pfi9J0+GQPmWeQi+OhzgLDr
51QA83QdgOd5TIIEz+bxyXlE4OihhTkSL6QyzTmm484ODGzX7fTceDAVqfaB1o3l
CEcbEmmmx7+LIScc411T3e+IkSEysQbMiU4+/5RAC7JdjwsIwMjvX7s7r2TlWNzb
DbdvwsdJiIa/tssOhJUNjQPYNoEM0XHhHGOk7nYZn91Z4YmGFAWp5Pzq1mExbtUX
gNvsJS6MjUa616hY63XRyIU6ChmPdI8gOqcSMtXRGelhQan4ZUUyhva/bNAjLY6m
avlge+p1zMhTejOd9fzBMEeKPGda2Vl4CBrJI1MC/I197qyOekRj8lVenHoKuWIT
pQy+oG3cps14h7AfzIac/iQa+WAtQAeXe6XNGhxd9ll+2j9n4w8=
=FjLE
-END PGP SIGNATURE End Message ---

Bug#871114: marked as done (widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized])

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 22:39:13 +
with message-id 
and subject line Bug#871114: fixed in widelands 1:19+repack-4
has caused the Debian Bug report #871114,
regarding widelands: FTBFS: game_settings.h:52:8: error: 
'newuser.UserSettings::position' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
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.)


-- 
871114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: widelands
Version: 1:19+repack-3
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):
> cd /<>/widelands-19+repack/obj-x86_64-linux-gnu/src/network && 
> /usr/bin/c++   -I/<>/widelands-19+repack/src 
> -I/<>/widelands-19+repack/obj-x86_64-linux-gnu/src -isystem 
> /usr/include/SDL2 -isystem /usr/include/minizip -isystem /usr/include/GL  -g 
> -O2 -fdebug-prefix-map=/<>/widelands-19+repack=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG
> -std=c++11 -fext-numeric-literals -g -O3 -DNDEBUG -DNOPARACHUTE -Wall 
> -Wpedantic -Wdeprecated-declarations -Wextra -Wformat -Wformat-nonliteral 
> -Wformat-security -Wformat-y2k -Winit-self -Winvalid-pch -Wlogical-op 
> -Wmissing-include-dirs -Wno-undef -Wold-style-cast -Woverlength-strings 
> -Wpacked -Wpointer-arith -Wredundant-decls -Wsign-promo -Wsync-nand 
> -Wtrampolines -Wundef -Wunused -Wunused-macros -Werror=format-security 
> -Werror=return-type -Werror=shadow -Werror=uninitialized -o 
> CMakeFiles/network.dir/network_player_settings_backend.cc.o -c 
> /<>/widelands-19+repack/src/network/network_player_settings_backend.cc
> In file included from 
> /<>/widelands-19+repack/src/network/network.h:29:0,
>  from 
> /<>/widelands-19+repack/src/network/network.cc:20:
> /<>/widelands-19+repack/src/network/network.h: In member function 
> 'virtual const char* ProtocolException::what() const':
> /<>/widelands-19+repack/src/base/wexception.h:63:90: warning: throw 
> will always call terminate() [-Wterminate]
>  #define NEVER_HERE() throw WException(__FILE__, __LINE__, "Unreachable code 
> was reached.")
>   
> ^
> /<>/widelands-19+repack/src/network/network.h:184:3: note: in 
> expansion of macro 'NEVER_HERE'
>NEVER_HERE();
>^~
> In file included from 
> /<>/widelands-19+repack/src/network/network.h:29:0,
>  from 
> /<>/widelands-19+repack/src/network/internet_gaming.h:34,
>  from 
> /<>/widelands-19+repack/src/network/internet_gaming.cc:20:
> /<>/widelands-19+repack/src/network/network.h: In member function 
> 'virtual const char* ProtocolException::what() const':
> /<>/widelands-19+repack/src/base/wexception.h:63:90: warning: throw 
> will always call terminate() [-Wterminate]
>  #define NEVER_HERE() throw WException(__FILE__, __LINE__, "Unreachable code 
> was reached.")
>   
> ^
> /<>/widelands-19+repack/src/network/network.h:184:3: note: in 
> expansion of macro 'NEVER_HERE'
>NEVER_HERE();
>^~
> In file included from 
> /<>/widelands-19+repack/src/scripting/lua_errors.h:25:0,
>  from 
> /<>/widelands-19+repack/src/scripting/lua_table.h:32,
>  from 
> /<>/widelands-19+repack/src/logic/map_objects/tribes/tribe_basic_info.h:29,
>  from 
> /<>/widelands-19+repack/src/logic/game_settings.h:28,
>  from 
> /<>/widelands-19+repack/src/network/nethost.h:24,
>  from 
> /<>/widelands-19+repack/src/network/nethost.cc:20:
> /<>/widelands-19+repack/src/network/network.h: In member function 
> 'virtual const char* ProtocolException::what() const':
> /<>/widelands-19+repack/src/base/wexception.h:63:90: warning: throw 
> will always call terminate() [-Wterminate]
>  #define NEVER_HERE() throw WException(__FILE__, __LINE__, "Unreachable code 
> was reached.")
>   
> ^
> /<>/widelands-19+repack/src/network/network.h:184:3: note: in 
> expansion of macro 'NEVER_HERE'
>NEVER_HERE();
>^~
> In file included from 

Bug#872598: udev-udeb: no input in graphical installer

[Michael Biebl]

Am 23.08.2017 um 23:57 schrieb Cyril Brulebois:

> My NMU FTBFSes on mips64el:
>   
> https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0
> 
> James Cowgill mentioned this gcc bug report:
>   https://bugs.debian.org/871514
> 
> so I think I might duplicate the rules file in src:debian-installer and
> work around the missing file by putting it into place manually, which is
> somewhat ugly but means we're no longer blocking on the systemd update.

I wouldn't mind if you forced the compiler to be GCC 6 in src:systemd
until this bug is fixed.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

[Debian Bug Tracking System]

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

> severity #822601 serious
Bug #822601 [src:xnetcardconfig] xnetcardconfig: depends on gksu which is 
deprecated
Severity set to 'serious' from 'important'
> severity #822603 serious
Bug #822603 [src:network-config] network-config: depends on gksu which is 
deprecated
Severity set to 'serious' from 'important'
> severity #822600 serious
Bug #822600 [src:sbackup] sbackup: depends on gksu which is deprecated
Severity set to 'serious' from 'important'
> kthxbye
Stopping processing here.

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

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Markus Koschany]

Control: tags -1 pending

Am 23.08.2017 um 21:56 schrieb Hans Joachim Desserud:
> Control: tags -1 confirmed
> Control: forwarded -1 https://bugs.launchpad.net/widelands/+bug/1695879
> 
> Hello
> 
> We ran into the same issue upstream a while back when attempting to
> build with GCC7,
> see [1] for details. The issue was fixed, and since we expected distros
> would switch to GCC7
> as the default compiler at some point the changes was also backported to
> our build19 branch.
> You can find the specific patch at [2] or [3] for the whole branch.
> (Note that the branch
> also includes a fix for the wrong en_GB translations [4], so you might
> want to include that at
> the same time)
> 
> Hope this helps. Let us know if you have any comments or questions. :)
> 
> [1] https://bugs.launchpad.net/widelands/+bug/1695879
> [2] http://bazaar.launchpad.net/~widelands-dev/widelands/b19/revision/8149
> [3] https://code.launchpad.net/~widelands-dev/widelands/b19
> [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853052

Funny. It seems we worked on this bug at the same time. I can confirm
that [2] resolved the FTBFS with GCC 7. However it was not clear to me
how [3] could fix [4]. I suggest to add a simple patch to bug reports
next time which tremendously simplifies things for non-regular uploaders
of Widelands.

Anyway I believe this bug should be fixed in a couple of minutes. Thank
you for your assistance.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #871114 [src:widelands] widelands: FTBFS: game_settings.h:52:8: error: 
'newuser.UserSettings::position' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
Added tag(s) pending.

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

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

[Reinhard Tartler]

On 08/23/2017 12:07 PM, Olaf Spinczyk wrote:
> Hi!
> 
> You can generate the config file easily with ag++ --gen_config. Sorry
> for the inconvenience. The background is that when I wrote the first
> ac++ tests, I did not want the makefile to depend on ag++.
> 
> We should change that sooner or later, because it is obviously confusing.

Not a problem.

Progress! With a "correct" PUMA CONFIG, I now get further, but there seem to be
genuine test failures. Are they concerning or shall I ignore them for the debian
package?

They look like this:

/usr/bin/make -C tests -s  all
make[2]: Entering directory
'/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests'
...[C:ExecAdviceNewDelete].[D:Bug574]...[C:Bug598]


+-+
|ERRORS:  |
+-+

-
TEST: ExecAdviceNewDelete
-
STDOUT:

make[3]: Entering directory
'/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/ExecAdviceNewDelete'
Weaving main.cc
* Running ac++ 2.2
* Handling Translation Unit `main.cc'.
  - Path "main.cc"
  - Parsing ...
  - Weaving Aspects Forward Declarations ...
  - Inserting namespace AC
  - Committing
  - Preparing introductions ...
  - Parsing again ...
  - Weaving access control bypass classes ...
  - Weaving Join Points ...
Advicecode manipulation
Collecting Advice
  Setting up thisJoinPoint for aspectof
Create pointcut expression tree
Matching joinpoints
Aspect ordering ...
Creating project repository 'repo.acp'
Type Check Functions
Access Join Points
Execution Join Points
  void *operator new(unsigned long int)
  void *operator new[](unsigned long int)
  void operator delete(void *)
  void operator delete[](void *)
  void A::operator delete(void *)
  void *C::operator new(unsigned long int)
  void C::operator delete(void *)
Construction Join Points
Destruction Join Points
  - Aspect Includes ...
  - Final cleanup
  - Committing
* Inserting unit pro- and epilogues
  - Manipulating translation unit file main.cc
* Updating #line directives of generated code fragments
* Saving
  - Expanding project includes
  - Fixing #line directives
  - Path "main.acc"
* Done
Compiling main.acc
../Makefile.generic:80: recipe for target 'Junk/main.o' failed
make[3]: Leaving directory
'/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/ExecAdviceNewDelete'

STDERR:

main.cc:5:30: warning: dynamic exception specifications are deprecated in C++11
[-Wdeprecated]
 void *operator new (size_t ) throw(std::bad_alloc);
  ^
main.cc:7:31: warning: dynamic exception specifications are deprecated in C++11
[-Wdeprecated]
 void *operator new (size_t s) throw(std::bad_alloc) {
   ^
main.cc: In function 'void* operator new(size_t)':
main.cc:7:7: error: declaration of 'void* operator new(size_t) throw
(std::bad_alloc)' has a different exception specifier
 void *operator new (size_t s) throw(std::bad_alloc) {
   ^~~~
main.cc:5:7: note: from previous declaration 'void* operator new(std::size_t)'
 void *operator new (size_t ) throw(std::bad_alloc);
   ^~~~
main.acc: In function 'void* operator new(std::size_t)':
main.acc:147:61: warning: dynamic exception specifications are deprecated in
C++11 [-Wdeprecated]
   typedef TJP__Znwm_0< void *, void, void, void *(::size_t)
throw(std::bad_alloc),  AC::TL< ::size_t, AC::TLE > > __TJP;
 ^
main.cc: At global scope:
main.cc:11:33: warning: dynamic exception specifications are deprecated in C++11
[-Wdeprecated]
 void *operator new[] (size_t s) throw(std::bad_alloc) {
 ^
main.acc: In function 'void* operator new [](std::size_t)':
main.acc:198:61: warning: dynamic exception specifications are deprecated in
C++11 [-Wdeprecated]
   typedef TJP__Znam_0< void *, void, void, void *(::size_t)
throw(std::bad_alloc),  AC::TL< ::size_t, AC::TLE > > __TJP;
 ^
make[3]: *** [Junk/main.o] Error 1


-
TEST: Bug574
-
STDOUT:

make[3]: Entering directory
'/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/Bug574'
Weaving main.cc
* Running ac++ 2.2
* Handling Translation Unit `main.cc'.
  - Path "main.cc"
  - Parsing ...
  - Weaving Aspects Forward Declarations ...
  - Inserting namespace AC
  - Committing
  - Preparing introductions ...
  - Parsing again ...
  - Weaving access control bypass classes ...
  - Weaving Join 

Processed: update #871514 v2

[Debian Bug Tracking System]

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

> # Not checked, but it seems very likely this is "the" mips64el bug
> forcemerge 871514 872987
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Removed indication that 871538 affects src:aptitude, clamav, apparmor, pspp, 
postgresql-10, postgresql-9.6, src:subversion, givaro, and ngircd
Added indication that 871538 affects 
apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10
Removed indication that 871514 affects apparmor, clamav, src:aptitude, givaro, 
src:subversion, ngircd, pspp, postgresql-9.6, and postgresql-10
Added indication that 871514 affects 
apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10
Removed indication that 872438 affects src:subversion, givaro, ngircd, pspp, 
postgresql-10, postgresql-9.6, apparmor, src:aptitude, and clamav
Added indication that 872438 affects 
apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10
Bug #872987 [gcc-7] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803'.
Added indication that 872987 affects 
apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10
Marked as found in versions gcc-7/7.1.0-13, gcc-7/7.2.0-1, gcc-7/7.1.0-10, and 
gcc-7/7.1.0-12.
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Merged 871514 871538 872438 872987
> affects 871514 src:nodejs
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Bug #872987 [gcc-7] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Added indication that 871514 affects src:nodejs
Added indication that 871538 affects src:nodejs
Added indication that 872438 affects src:nodejs
Added indication that 872987 affects src:nodejs
> retitle 871514 gcc-7: miscompiles stack spills on mips64el
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Bug #872987 [gcc-7] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Changed Bug title to 'gcc-7: miscompiles stack spills on mips64el' from 
'clamav: FTBFS on mips64el'.
Changed Bug title to 'gcc-7: miscompiles stack spills on mips64el' from 'Makes 
apparmor FTBFS on mips64el (generated code thinks that 1 > 1)'.
Changed Bug title to 'gcc-7: miscompiles stack spills on mips64el' from 
'src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node'.
Changed Bug title to 'gcc-7: miscompiles stack spills on mips64el' from 'pspp 
1.0.0-1 FTBFS on mips64el architecture on debian'.
> 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
872438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872438
872987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 3 errors): update #871514

[Debian Bug Tracking System]

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

> # Not checked, but it seems very likely this is "the" mips64el bug
> merge 871514 872987
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Unable to merge bugs because:
affects of #871538 is 
'apparmor,ngircd,src:aptitude,givaro,postgresql-9.6,pspp,src:subversion,clamav,postgresql-10'
 not 
'apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10'
forwarded of #872987 is '' not 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803'
affects of #872987 is '' not 
'apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10'
affects of #872438 is 
'pspp,src:subversion,clamav,postgresql-10,src:aptitude,ngircd,apparmor,givaro,postgresql-9.6'
 not 
'apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10'
Failed to merge 871514: Did not alter merged bugs.

> affects 871514 src:nodejs
Failed to mark 871514 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/merge -- Unable to lock 
/org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

> retitle 871514 gcc-7: miscompiles stack spills on mips64el
Failed to set the title of 871514: failed to get lock on 
/org/bugs.debian.org/spool/lock/merge -- Unable to lock 
/org/bugs.debian.org/spool/lock/merge Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

> 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
872438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872438
872987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872598: udev-udeb: no input in graphical installer

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2017-08-23):
> Michael Biebl  (2017-08-23):
> > Am 23.08.2017 um 10:08 schrieb Cyril Brulebois:
> > > Would you be OK with a minimal NMU to fix the missing file? This issue has
> > > been blocking the D-I Buster Alpha 1 release for weeks already (even if it
> > > hadn't been diagnosed and reported against udev-udeb until recently), and
> > > I'd be happy to get a release out the door ASAP, since I won't have much
> > > time in the following weeks.
> > 
> > Felipe has already looked into this issue a bit and discovered more
> > inconsistencies between the deb and udeb build for udev. This will
> > probably need some more time to review/investigate properly, so feel
> > free to go ahead with the NMU!
> 
> Thanks!
> 
> Attached is the NMU diff.

My NMU FTBFSes on mips64el:
  
https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=234-2.1=1503523165=0

James Cowgill mentioned this gcc bug report:
  https://bugs.debian.org/871514

so I think I might duplicate the rules file in src:debian-installer and
work around the missing file by putting it into place manually, which is
somewhat ugly but means we're no longer blocking on the systemd update.


KiBi.


signature.asc
Description: Digital signature

Processed: Add patch tag

[Debian Bug Tracking System]

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

> tags 853470 patch
Bug #853470 [src:kadu] kadu: ftbfs with GCC-7
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#869608: marked as done (bareos-filedaemon: corrupts backups when signature=SHA1 in fileset)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 21:17:43 +
with message-id 
and subject line Bug#869608: fixed in bareos 14.2.1+20141017gitc6c5b56-3+deb8u3
has caused the Debian Bug report #869608,
regarding bareos-filedaemon: corrupts backups when signature=SHA1 in fileset
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.)


-- 
869608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bareos-filedaemon
Version: 16.2.4-3
Severity: critical
Justification: causes serious data loss

to reproduce:
1) install bareos 16.2.4 client and server packages - all with
defaults.
2) run a SelfTest backup of the client/server.
3) Restore a file from this backup - everything should be fine.

4) now change
Signature = SHA1
in /etc/bareos/bareos-dir.d/fileset/SelfTest.conf

5) run another SelfTest Full backup
6) restore a file from this new backup

The restored file is corrupted.

I marked this critical because I upgraded a debian 8 client to debian 9
without any problems. Backups (bareos 15.2.2 Server) appeared to be
running fine until I had to do a restore and ended up with broken
files.

Regards,
  Tom

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

Kernel: Linux 4.10.17-1-pve (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bareos-filedaemon depends on:
ii  adduser3.115
ii  bareos-common  16.2.4-3
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  libacl12.2.52-3+b1
ii  libc6  2.24-11+deb9u1
ii  libcap21:2.25-1
ii  libgcc11:6.3.0-18
ii  libgnutls303.5.8-5+deb9u2
ii  libjansson42.9-1
ii  liblzo2-2  2.08-1.2+b2
ii  libstdc++6 6.3.0-18
ii  libwrap0   7.6.q-26
ii  lsb-base   9.20161125
ii  lsof   4.89+dfsg-0.1
ii  zlib1g 1:1.2.8.dfsg-5

bareos-filedaemon recommends no packages.

bareos-filedaemon suggests no packages.
--- End Message ---
--- Begin Message ---
Source: bareos
Source-Version: 14.2.1+20141017gitc6c5b56-3+deb8u3

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated bareos 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, 27 Jul 2017 21:02:50 +0200
Source: bareos
Binary: bareos bareos-bconsole bareos-client bareos-common 
bareos-database-common bareos-database-postgresql bareos-database-mysql 
bareos-database-sqlite3 bareos-database-tools bareos-dbg bareos-devel 
bareos-director bareos-filedaemon bareos-storage bareos-storage-fifo 
bareos-storage-tape bareos-tools bareos-bat bareos-director-python-plugin 
bareos-filedaemon-python-plugin bareos-storage-python-plugin bareos-traymonitor
Architecture: source amd64
Version: 14.2.1+20141017gitc6c5b56-3+deb8u3
Distribution: jessie
Urgency: medium
Maintainer: Bareos Packaging Team 
Changed-By: Felix Geyer 
Description:
 bareos - Backup Archiving Recovery Open Sourced - metapackage
 bareos-bat - Backup Archiving Recovery Open Sourced - Bareos Admin Tool (BAT)
 bareos-bconsole - Backup Archiving Recovery Open Sourced - text console
 bareos-client - Backup Archiving Recovery Open Sourced - client metapackage
 bareos-common - Backup Archiving Recovery Open Sourced - common files
 bareos-database-common - Backup Archiving Recovery Open Sourced - common 
catalog files
 bareos-database-mysql - Backup Archiving Recovery Open Sourced - MySQL backend
 bareos-database-postgresql - Backup Archiving Recovery Open Sourced - 
PostgreSQL backend
 bareos-database-sqlite3 - Backup Archiving 

Processed: Re: [Debian-med-packaging] Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #873024 [src:orthanc-wsi] orthanc-wsi FTBFS with dcmtk 3.6.2
Added tag(s) pending.

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

Bug#853515: marked as done (libwebsockets: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 20:57:55 +
with message-id 
and subject line Bug#853515: fixed in libwebsockets 2.0.3-2.1
has caused the Debian Bug report #853515,
regarding libwebsockets: 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.)


-- 
853515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libwebsockets
Version: 2.0.3-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/libwebsockets_2.0.3-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

[...]
[ 91%] Linking C executable bin/libwebsockets-test-fraggle
/usr/bin/cmake -E cmake_link_script CMakeFiles/test-fraggle.dir/link.txt 
--verbose=1
/usr/bin/cc  -Wall -Werror -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 
-pthread  -Wl,-z,relro -Wl,-z,now 
CMakeFiles/test-echo.dir/test-server/test-echo.c.o  -o 
bin/libwebsockets-test-echo -rdynamic lib/libwebsockets.a -lz -lssl -lcrypto 
-lev -luv -lm 
/usr/bin/cc  -Wall -Werror -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 
-pthread  -Wl,-z,relro -Wl,-z,now 
CMakeFiles/test-fraggle.dir/test-server/test-fraggle.c.o  -o 
bin/libwebsockets-test-fraggle -rdynamic lib/libwebsockets.a -lz -lssl -lcrypto 
-lev -luv -lm 
cc1: all warnings being treated as errors
[ 92%] Linking C executable bin/libwebsockets-test-ping
CMakeFiles/test-server-extpoll.dir/build.make:89: recipe for target 
'CMakeFiles/test-server-extpoll.dir/test-server/test-server-http.c.o' failed
make[3]: *** 
[CMakeFiles/test-server-extpoll.dir/test-server/test-server-http.c.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:366: recipe for target 
'CMakeFiles/test-server-extpoll.dir/all' failed
make[2]: *** [CMakeFiles/test-server-extpoll.dir/all] Error 2
/usr/bin/cmake -E cmake_link_script CMakeFiles/test-ping.dir/link.txt 
--verbose=1
/usr/bin/cc  -Wall -Werror -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 
-pthread  -Wl,-z,relro -Wl,-z,now 
CMakeFiles/test-ping.dir/test-server/test-ping.c.o  -o 
bin/libwebsockets-test-ping -rdynamic lib/libwebsockets.a -lz -lssl -lcrypto 
-lev -luv -lm 
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/test-server.dir/build.make:89: recipe for target 
'CMakeFiles/test-server.dir/test-server/test-server-http.c.o' failed
make[3]: *** [CMakeFiles/test-server.dir/test-server/test-server-http.c.o] 
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:107: recipe for target 
'CMakeFiles/test-server-libuv.dir/all' failed
make[2]: *** [CMakeFiles/test-server-libuv.dir/all] Error 2
CMakeFiles/Makefile2:144: recipe for target 'CMakeFiles/test-server.dir/all' 
failed
make[2]: *** [CMakeFiles/test-server.dir/all] Error 2
CMakeFiles/test-server-pthreads.dir/build.make:89: recipe for target 
'CMakeFiles/test-server-pthreads.dir/test-server/test-server-http.c.o' failed
make[3]: *** 
[CMakeFiles/test-server-pthreads.dir/test-server/test-server-http.c.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:70: recipe 

Bug#853579: marked as done (nut: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 20:59:16 +
with message-id 
and subject line Bug#853579: fixed in nut 2.7.4-5.1
has caused the Debian Bug report #853579,
regarding nut: 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.)


-- 
853579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nut
Version: 2.7.4-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/nut_2.7.4-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

[...]
dh_compress -pnut-xml 
dh_fixperms -pnut-xml 
dh_makeshlibs -pnut-xml  
dh_strip -pnut-powerman-pdu  
dh_strip_nondeterminism -pnut-powerman-pdu 
dh_compress -pnut-powerman-pdu 
dh_fixperms -pnut-powerman-pdu 
dh_makeshlibs -pnut-powerman-pdu  
dh_strip -plibupsclient4  
dh_strip_nondeterminism -plibupsclient4 
dh_compress -plibupsclient4 
dh_fixperms -plibupsclient4 
dh_makeshlibs -plibupsclient4  
dh_strip -plibupsclient-dev  
dh_strip_nondeterminism -plibupsclient-dev 
dh_compress -plibupsclient-dev 
dh_fixperms -plibupsclient-dev 
dh_makeshlibs -plibupsclient-dev  
dh_strip -plibnutclient0  
dh_strip_nondeterminism -plibnutclient0 
dh_compress -plibnutclient0 
dh_fixperms -plibnutclient0 
dh_makeshlibs -plibnutclient0  
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libnutclient0/DEBIAN/symbols doesn't match 
completely debian/libnutclient0.symbols
--- debian/libnutclient0.symbols (libnutclient0_2.7.4-5_amd64)
+++ dpkg-gensymbolsYGrFp1   2017-01-27 13:31:28.13600 +
@@ -1,4 +1,6 @@
 libnutclient.so.0 libnutclient0 #MINVER#
+ 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 2.7.4-5
+ 
_ZNSt6vectorIS_INSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base
 2.7.4-5
  (c++)"nut::Client::Client()@Base" 2.7.3
  (c++)"nut::Client::getDevice(std::__cxx11::basic_string const&)@Base" 2.7.3
  (c++)"nut::Client::getDeviceVariableValues(std::__cxx11::basic_string const&)@Base" 2.7.3
@@ -185,8 +187,8 @@
  (c++)"typeinfo name for nut::TcpClient@Base" 2.7.3
  (c++)"typeinfo name for nut::TimeoutException@Base" 2.7.3
  (c++)"typeinfo name for nut::UnknownHostException@Base" 2.7.3
- (c++)"void std::vector, 
std::allocator > 
>::_M_emplace_back_aux const&>(std::__cxx11::basic_string const&)@Base" 2.7.3
- (c++)"void std::vector, 
std::allocator > >, 
std::allocator, 
std::allocator > > > 

Bug#873024: [Debian-med-packaging] Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

[Gert Wollny]

Control: tags -1 pending 

I've pushed the needed changes to the packaging git. Will check and
upload tomorrow. 

Best, 
Gert 

Bug#869633: marked as done (CVE-2015-5191)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 20:47:28 +
with message-id 
and subject line Bug#869633: fixed in open-vm-tools 2:10.1.5-5055683-4+deb9u1
has caused the Debian Bug report #869633,
regarding CVE-2015-5191
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.)


-- 
869633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: open-vm-tools
Severity: grave
Tags: security

Please see:
http://www.openwall.com/lists/oss-security/2017/07/24/3

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: open-vm-tools
Source-Version: 2:10.1.5-5055683-4+deb9u1

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated open-vm-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Jul 2017 11:40:02 +0200
Source: open-vm-tools
Binary: open-vm-tools open-vm-tools-desktop open-vm-tools-dev open-vm-tools-dkms
Architecture: source amd64 all
Version: 2:10.1.5-5055683-4+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Description:
 open-vm-tools - Open VMware Tools for virtual machines hosted on VMware (CLI)
 open-vm-tools-desktop - Open VMware Tools for virtual machines hosted on 
VMware (GUI)
 open-vm-tools-dev - Open VMware Tools for virtual machines hosted on VMware 
(developm
 open-vm-tools-dkms - Open VMware Tools vmxnet kernel module (deprecated)
Closes: 869633
Changes:
 open-vm-tools (2:10.1.5-5055683-4+deb9u1) stretch; urgency=medium
 .
   * [dec8df6] Upstream fix for CVE-2015-5191 (Closes: #869633)
   * [ff10dcb] Update gbp.conf for stretch.
Checksums-Sha1:
 12812c4a87cec78edca51c1c6062e9b4bce416f8 2530 
open-vm-tools_10.1.5-5055683-4+deb9u1.dsc
 5374dd0dd7b5190449c99e2ee0071b98d230416c 29128 
open-vm-tools_10.1.5-5055683-4+deb9u1.debian.tar.xz
 b8278a9594e16559cea45a72954dfd80dc239c98 2000734 
open-vm-tools-dbgsym_10.1.5-5055683-4+deb9u1_amd64.deb
 beb5dfa9a91c9b381b3fe072c173ba6869ed531c 197262 
open-vm-tools-desktop-dbgsym_10.1.5-5055683-4+deb9u1_amd64.deb
 faeeffad7a55ffd220659a98dd9a034fcd598305 166788 
open-vm-tools-desktop_10.1.5-5055683-4+deb9u1_amd64.deb
 c1b7ce373aa7d24a61f6c0ecd033c5c10300d510 499558 
open-vm-tools-dev_10.1.5-5055683-4+deb9u1_amd64.deb
 2a3ea7ba442e9afce5b774aed8a20757c75b7f44 418366 
open-vm-tools-dkms_10.1.5-5055683-4+deb9u1_all.deb
 afac67016c1b98e9da861d63834ee44d3ed31d2f 13673 
open-vm-tools_10.1.5-5055683-4+deb9u1_amd64.buildinfo
 f8493fade20417da30c6c66a16a63ca6a37e6459 561360 
open-vm-tools_10.1.5-5055683-4+deb9u1_amd64.deb
Checksums-Sha256:
 e21809aa160b14a0d4da41d083dc9fa749adc2f397b3227d3657fed4b67a20d8 2530 
open-vm-tools_10.1.5-5055683-4+deb9u1.dsc
 5c7896486b0cfa5c64fc388015b265f824d6d9c62eec3dcd90bf860e6ac69b84 29128 
open-vm-tools_10.1.5-5055683-4+deb9u1.debian.tar.xz
 79a3d15efc23f6ddc5a778af73704ae88403a6bc3dbcb02f302a4888d7be16de 2000734 
open-vm-tools-dbgsym_10.1.5-5055683-4+deb9u1_amd64.deb
 18312a33688a6cd4c9384ebcd4f6da010aa80e8e46e6e4d18ab96d7de5c7fd79 197262 
open-vm-tools-desktop-dbgsym_10.1.5-5055683-4+deb9u1_amd64.deb
 7bb49cb50ba8512631f64a4c288a3b40f81a21a203fe84ad51297682474015f9 166788 
open-vm-tools-desktop_10.1.5-5055683-4+deb9u1_amd64.deb
 975f5abc441f0d2610b004a8e9db6aee9402d7f3a6c9052e893bd5d8e3ba84d4 499558 
open-vm-tools-dev_10.1.5-5055683-4+deb9u1_amd64.deb
 034229a0c1c6de0643d38327d7d0d360b76417b30106972d6ffa796ff7be61da 418366 
open-vm-tools-dkms_10.1.5-5055683-4+deb9u1_all.deb
 fadb25a5da5b403c60418d0f48398e22950da879428b598d3c98d346cf936744 13673 
open-vm-tools_10.1.5-5055683-4+deb9u1_amd64.buildinfo
 c80ca51d60828e056669e052546dd9907a3722e6594453969843deae977aaef4 561360 
open-vm-tools_10.1.5-5055683-4+deb9u1_amd64.deb
Files:
 b8e1a86b0c05d1d2c8f17ffdc2e01c78 2530 admin extra 
open-vm-tools_10.1.5-5055683-4+deb9u1.dsc
 fbd9293f4b12339d8bd6e738ee2b8bf8 

Bug#868150: marked as done (imapproxy: fails to start)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 20:47:32 +
with message-id 
and subject line Bug#868150: fixed in up-imapproxy 1.2.8~svn20161210-2+deb9u1
has caused the Debian Bug report #868150,
regarding imapproxy: fails to start
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.)


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

Package: imapproxy
Version: 1.2.8~svn20161210-2
Severity: grave


Quack,

The server does not start. Trying to restart it does not change 
anything. Here is the systemd status:


# systemctl status imapproxy
● imapproxy.service - IMAP proxy
   Loaded: loaded (/lib/systemd/system/imapproxy.service; static; vendor 
preset: enabled)

   Active: inactive (dead)
 Docs: man:imapproxyd(8)

Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: main(): Internal admin 
commands are disabled
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: main(): Allocating 3072 IMAP 
connection structures.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: main(): Enabling openssl 
library.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: Initialising 1 
pthread_mutexes
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ServerInit(): Using 
'/var/log/imapproxy_protocol.log' for global protocol logging file.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ServerInit(): proxying to 
IMAP server 'localhost'.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ServerInit(): Proxying to 
IMAP port 143
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ParseBannerAndCapability: 
Attempting to parse capability string: * OK [CAPABILITY IMAP4rev1 
LITERAL+ SA

Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: [238B blob data]
Jul 12 14:32:49 Orfeo systemd[1]: Started IMAP proxy.


The service is marked as "static", which is wrong in this case IIUC.

Interestingly:

# systemctl enable imapproxy
Synchronizing state of imapproxy.service with SysV service script with 
/lib/systemd/systemd-sysv-install.

Executing: /lib/systemd/systemd-sysv-install enable imapproxy
The unit files have no installation config (WantedBy, RequiredBy, Also, 
Alias
settings in the [Install] section, and DefaultInstance for template 
units).

This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another 
unit's

   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which 
has

   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, 
timer,

   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.


There is indeed not [Install] section. If I add one with 
"WantedBy=multi-user.target" I can enable the service but still it does 
not start properly.


But if I use the init script directly it starts fine (and the service 
works fine too, so the config is all right):


# /etc/init.d/imapproxy start
Starting imapproxy (via systemctl): imapproxy.service.
# /etc/init.d/imapproxy status
● imapproxy.service - IMAP proxy
   Loaded: loaded (/lib/systemd/system/imapproxy.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2017-07-12 14:40:25 CEST; 2min 37s 
ago

 Docs: man:imapproxyd(8)
  Process: 19772 ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf 
(code=exited, status=0/SUCCESS)
  Process: 19766 ExecStartPre=/usr/share/imapproxy/prepare-chroot 
(code=exited, status=0/SUCCESS)

 Main PID: 19776 (imapproxyd)
Tasks: 2 (limit: 4915)
   Memory: 1.6M
  CPU: 19ms
   CGroup: /system.slice/imapproxy.service
   └─19776 /usr/sbin/imapproxyd -f /etc/imapproxy.conf

Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: ServerInit(): proxying to 
IMAP server 'localhost'.
Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: ServerInit(): Proxying to 
IMAP port 143
Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: ParseBannerAndCapability: 
Attempting to parse capability string: * OK [CAPABILITY IMAP4rev1 …cot 
ready.

Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: [238B blob data]
Jul 12 14:40:25 Orfeo systemd[1]: 

Bug#869608: marked as done (bareos-filedaemon: corrupts backups when signature=SHA1 in fileset)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 20:47:12 +
with message-id 
and subject line Bug#869608: fixed in bareos 16.2.4-3+deb9u1
has caused the Debian Bug report #869608,
regarding bareos-filedaemon: corrupts backups when signature=SHA1 in fileset
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.)


-- 
869608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bareos-filedaemon
Version: 16.2.4-3
Severity: critical
Justification: causes serious data loss

to reproduce:
1) install bareos 16.2.4 client and server packages - all with
defaults.
2) run a SelfTest backup of the client/server.
3) Restore a file from this backup - everything should be fine.

4) now change
Signature = SHA1
in /etc/bareos/bareos-dir.d/fileset/SelfTest.conf

5) run another SelfTest Full backup
6) restore a file from this new backup

The restored file is corrupted.

I marked this critical because I upgraded a debian 8 client to debian 9
without any problems. Backups (bareos 15.2.2 Server) appeared to be
running fine until I had to do a restore and ended up with broken
files.

Regards,
  Tom

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

Kernel: Linux 4.10.17-1-pve (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bareos-filedaemon depends on:
ii  adduser3.115
ii  bareos-common  16.2.4-3
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  libacl12.2.52-3+b1
ii  libc6  2.24-11+deb9u1
ii  libcap21:2.25-1
ii  libgcc11:6.3.0-18
ii  libgnutls303.5.8-5+deb9u2
ii  libjansson42.9-1
ii  liblzo2-2  2.08-1.2+b2
ii  libstdc++6 6.3.0-18
ii  libwrap0   7.6.q-26
ii  lsb-base   9.20161125
ii  lsof   4.89+dfsg-0.1
ii  zlib1g 1:1.2.8.dfsg-5

bareos-filedaemon recommends no packages.

bareos-filedaemon suggests no packages.
--- End Message ---
--- Begin Message ---
Source: bareos
Source-Version: 16.2.4-3+deb9u1

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated bareos 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, 27 Jul 2017 20:58:49 +0200
Source: bareos
Binary: bareos bareos-bconsole bareos-client bareos-common 
bareos-database-common bareos-database-postgresql bareos-database-mysql 
bareos-database-sqlite3 bareos-database-tools bareos-dbg bareos-devel 
bareos-director bareos-filedaemon bareos-storage bareos-storage-fifo 
bareos-storage-tape bareos-tools bareos-director-python-plugin 
bareos-filedaemon-ceph-plugin bareos-filedaemon-glusterfs-plugin 
bareos-filedaemon-python-plugin bareos-filedaemon-ldap-python-plugin 
bareos-storage-ceph bareos-storage-glusterfs bareos-storage-python-plugin 
bareos-traymonitor bareos-bat
Architecture: source amd64
Version: 16.2.4-3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Bareos Packaging Team 
Changed-By: Felix Geyer 
Description:
 bareos - Backup Archiving Recovery Open Sourced - metapackage
 bareos-bat - Backup Archiving Recovery Open Sourced - Bareos Admin Tool (BAT)
 bareos-bconsole - Backup Archiving Recovery Open Sourced - text console
 bareos-client - Backup Archiving Recovery Open Sourced - client metapackage
 bareos-common - Backup Archiving Recovery Open Sourced - common files
 bareos-database-common - Backup Archiving Recovery Open Sourced - common 
catalog files
 bareos-database-mysql - Backup Archiving Recovery Open Sourced - MySQL backend
 bareos-database-postgresql - Backup 

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Markus Koschany]

Hi Hans Joachim,

it appears you are involved in upstream development for Widelands. The
game currently fails to build from source with GCC 7. I discovered this
[1] merge commit which shall resolve GCC 7 issues but unfortunately it
doesn't apply cleanly for the recent 1.19 release of Widelands.

Do you know if a targeted fix for 1.19 exists already or are there any
plans to release a new version of Widelands to resolve this issue?

Thanks,

Markus


[1] https://code.launchpad.net/~widelands-dev/widelands/gcc7/+merge/323576



signature.asc
Description: OpenPGP digital signature

Processed: Re: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #871114 [src:widelands] widelands: FTBFS: game_settings.h:52:8: error: 
'newuser.UserSettings::position' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
Added tag(s) confirmed.
> forwarded -1 https://bugs.launchpad.net/widelands/+bug/1695879
Bug #871114 [src:widelands] widelands: FTBFS: game_settings.h:52:8: error: 
'newuser.UserSettings::position' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/widelands/+bug/1695879'.

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

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Hans Joachim Desserud]

Control: tags -1 confirmed
Control: forwarded -1 https://bugs.launchpad.net/widelands/+bug/1695879

Hello

We ran into the same issue upstream a while back when attempting to 
build with GCC7,
see [1] for details. The issue was fixed, and since we expected distros 
would switch to GCC7
as the default compiler at some point the changes was also backported to 
our build19 branch.
You can find the specific patch at [2] or [3] for the whole branch. 
(Note that the branch
also includes a fix for the wrong en_GB translations [4], so you might 
want to include that at

the same time)

Hope this helps. Let us know if you have any comments or questions. :)

[1] https://bugs.launchpad.net/widelands/+bug/1695879
[2] 
http://bazaar.launchpad.net/~widelands-dev/widelands/b19/revision/8149

[3] https://code.launchpad.net/~widelands-dev/widelands/b19
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853052

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#873029: [unicode-data] Copyriht/Lack of get-orig-source where is the source

[Bastien ROUCARIÈS]

Package: unicode-data
Version: 10.0.0-1
Severity: serious

Without copyright information with exact location of souce, it is hard to get 
source

It is at least a violation of 12.5. Copyright information

I could help with this package if needed

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

Processed (with 1 error): merge

[Debian Bug Tracking System]

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

> merge 872987 871514
Bug #872987 [gcc-7] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Unable to merge bugs because:
forwarded of #871538 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' 
not ''
affects of #871538 is 
'apparmor,ngircd,src:aptitude,givaro,postgresql-9.6,pspp,src:subversion,clamav,postgresql-10'
 not ''
forwarded of #872438 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' 
not ''
affects of #872438 is 
'pspp,src:subversion,clamav,postgresql-10,src:aptitude,ngircd,apparmor,givaro,postgresql-9.6'
 not ''
forwarded of #871514 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' 
not ''
affects of #871514 is 
'apparmor,ngircd,src:aptitude,postgresql-9.6,givaro,src:subversion,clamav,pspp,postgresql-10'
 not ''
Failed to merge 872987: Did not alter merged bugs.

> 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
872438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872438
872987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

[Adrian Bunk]

Source: orthanc-wsi
Version: 0.4+dfsg-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orthanc-wsi.html

...
-- Trying to find DCMTK expecting DCMTKConfig.cmake
-- Trying to find DCMTK expecting DCMTKConfig.cmake - ok
DCMTK version: 362
CMake Error at 
/build/1st/orthanc-wsi-0.4+dfsg/Resources/Orthanc/Resources/CMake/DcmtkConfiguration.cmake:318
 (message):
  Cannot locate the DICOM dictionary on this system
Call Stack (most recent call first):
  CMakeLists.txt:67 (include)


-- Configuring incomplete, errors occurred!

Bug#873023: tupi FTBFS with qtmultimedia5-dev 5.9.1-2

[Adrian Bunk]

Source: tupi
Version: 0.2+git08-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tupi.html

...
 * Checking for Qt >= 5.4.0
 * Testing for qmake... [ OK ]
 * Adding libav support: true
 * Checking for Theora... [ OK ]
 * Priority: optional
 * Checking for Qt Multimedia... [ FAILED ]
 * Priority: required
 * Seems like you are running unix...
 * You MUST install these dependencies: 
 * URL: 
 * 
 * Configure failed. error was: Missing required dependency
...

Bug#873020: marked as done (phonon FTBFS qtbase5-dev 5.9.1+dfsg-9)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 22:04:35 +0300
with message-id <20170823190435.aprffxpezigzjh4u@localhost>
and subject line Already fixed in experimental
has caused the Debian Bug report #873020,
regarding phonon FTBFS qtbase5-dev 5.9.1+dfsg-9
to be marked as done.

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

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


-- 
873020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phonon
Version: 4:4.9.0-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phonon.html

...
In file included from /build/1st/phonon-4.9.0/phonon/audiooutput_p.h:28:0,
 from /build/1st/phonon-4.9.0/phonon/audiooutput.cpp:23:
/build/1st/phonon-4.9.0/build-qt5/phonon/phononconfig_p.h:6:10: fatal error: 
QtCore/qfeatures.h: No such file or directory
 #include 
  ^~~~
compilation terminated.
phonon/CMakeFiles/phonon4qt5.dir/build.make:209: recipe for target 
'phonon/CMakeFiles/phonon4qt5.dir/audiooutput.cpp.o' failed
make[5]: *** [phonon/CMakeFiles/phonon4qt5.dir/audiooutput.cpp.o] Error 1


qfeatures.h was removed from Qt.
--- End Message ---
--- Begin Message ---
Version: 4:4.9.1-1

The package in experimental no longer uses qfeatures.h

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--- End Message ---

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

[Jonas Smedegaard]

Quoting Pirate Praveen (2017-08-23 20:11:28)
> On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote:
> > Package: node-lodash-packages
> > Severity: serious
> > Justification: Policy 2.1
> 
> I do not think the root issue is serious, but only important.

Lack of source is serious.

Please elaborate why you think differently.


> > The source package node-lodash-packages does not contain the source 
> > form preferred for editing by upstream.  Instead, upstream documents 
> > how the contents of that code is generated from the sources included 
> > in Debian in the source package node-lodash.
> 
> Adding a build dependency on node-lodash would be enough for the 
> policy requirement.

If your reasoning is that the bug is easy to fix, then that does not 
change the severity (only - hopefully - the longevity of the bug staying 
open).


 - Jonas

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

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


signature.asc
Description: signature

Processed: severity of 873016 is serious

[Debian Bug Tracking System]

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

> severity 873016 serious
Bug #873016 [node-lodash-packages] node-lodash-packages: not preferred form for 
source: Should be built from node-lodash
Ignoring request to change severity of Bug 873016 to the same value.
> thanks
Stopping processing here.

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

Bug#872598: udev-udeb: no input in graphical installer

[Cyril Brulebois]

Control: tag -1 patch pending

Michael Biebl  (2017-08-23):
> Am 23.08.2017 um 10:08 schrieb Cyril Brulebois:
> > Would you be OK with a minimal NMU to fix the missing file? This issue has
> > been blocking the D-I Buster Alpha 1 release for weeks already (even if it
> > hadn't been diagnosed and reported against udev-udeb until recently), and
> > I'd be happy to get a release out the door ASAP, since I won't have much
> > time in the following weeks.
> 
> Felipe has already looked into this issue a bit and discovered more
> inconsistencies between the deb and udeb build for udev. This will
> probably need some more time to review/investigate properly, so feel
> free to go ahead with the NMU!

Thanks!

Attached is the NMU diff.


KiBi.
diff -Nru systemd-234/debian/changelog systemd-234/debian/changelog
--- systemd-234/debian/changelog	2017-07-20 15:13:42.0 +0200
+++ systemd-234/debian/changelog	2017-08-23 20:41:34.0 +0200
@@ -1,3 +1,12 @@
+systemd (234-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix missing 60-input-id.rules in udev-udeb, which breaks the graphical
+version of the Debian Installer, as no key presses or mouse events get
+processed (Closes: #872598).
+
+ -- Cyril Brulebois   Wed, 23 Aug 2017 20:41:33 +0200
+
 systemd (234-2) unstable; urgency=medium
 
   [ Martin Pitt ]
diff -Nru systemd-234/debian/udev-udeb.install systemd-234/debian/udev-udeb.install
--- systemd-234/debian/udev-udeb.install	2017-07-20 15:13:42.0 +0200
+++ systemd-234/debian/udev-udeb.install	2017-08-23 20:41:25.0 +0200
@@ -6,6 +6,7 @@
 lib/udev/cdrom_id
 lib/udev/rules.d/50-udev-default.rules
 lib/udev/rules.d/60-cdrom_id.rules
+lib/udev/rules.d/60-input-id.rules
 lib/udev/rules.d/60-persistent-input.rules
 lib/udev/rules.d/60-persistent-storage.rules
 lib/udev/rules.d/64-btrfs.rules


signature.asc
Description: Digital signature

Processed: Re: Bug#872598: udev-udeb: no input in graphical installer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #872598 [udev-udeb] udev-udeb: no input in graphical installer
Added tag(s) pending.

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

Bug#873020: phonon FTBFS qtbase5-dev 5.9.1+dfsg-9

[Adrian Bunk]

Source: phonon
Version: 4:4.9.0-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phonon.html

...
In file included from /build/1st/phonon-4.9.0/phonon/audiooutput_p.h:28:0,
 from /build/1st/phonon-4.9.0/phonon/audiooutput.cpp:23:
/build/1st/phonon-4.9.0/build-qt5/phonon/phononconfig_p.h:6:10: fatal error: 
QtCore/qfeatures.h: No such file or directory
 #include 
  ^~~~
compilation terminated.
phonon/CMakeFiles/phonon4qt5.dir/build.make:209: recipe for target 
'phonon/CMakeFiles/phonon4qt5.dir/audiooutput.cpp.o' failed
make[5]: *** [phonon/CMakeFiles/phonon4qt5.dir/audiooutput.cpp.o] Error 1


qfeatures.h was removed from Qt.

Bug#871333: marked as done (r-bioc-rtracklayer: FTBFS: Error: package or namespace load failed for 'rtracklayer' in dyn.load(file, DLLpath = DLLpath, ...):)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 18:53:01 +
with message-id 
and subject line Bug#871333: fixed in r-bioc-rtracklayer 1.36.4-1
has caused the Debian Bug report #871333,
regarding r-bioc-rtracklayer: FTBFS: Error: package or namespace load failed 
for 'rtracklayer' in dyn.load(file, DLLpath = DLLpath, ...):
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.)


-- 
871333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-rtracklayer
Version: 1.34.1-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):
> make[1]: Entering directory '/<>/src'
> make[1]: Leaving directory '/<>/src'
> installing to 
> /<>/debian/r-bioc-rtracklayer/usr/lib/R/site-library/rtracklayer/libs
> ** R
> ** data
> ** demo
> ** inst
> ** preparing package for lazy loading
> Warning: undefined slot classes in definition of "UCSCTableQuery": 
> track(class "characterORNULL"), table(class "characterORNULL"), 
> outputType(class "characterORNULL"), NAMES(class "characterORNULL"), 
> intersectTrack(class "characterORNULL")
> Warning: undefined slot classes in definition of "Bed15TrackLine": 
> expNames(class "characterORNULL")
> Creating a generic function for 'offset' from package 'stats' in package 
> 'rtracklayer'
> Creating a generic function from function 'uri' in package 'rtracklayer'
> ** help
> *** installing help indices
> ** building package indices
> ** installing vignettes
> ** testing if installed package can be loaded
> Error: package or namespace load failed for 'rtracklayer' in dyn.load(file, 
> DLLpath = DLLpath, ...):
>  unable to load shared object 
> '/<>/debian/r-bioc-rtracklayer/usr/lib/R/site-library/rtracklayer/libs/rtracklayer.so':
>   
> /<>/debian/r-bioc-rtracklayer/usr/lib/R/site-library/rtracklayer/libs/rtracklayer.so:
>  undefined symbol: append_string_to_CharAEAE
> Error: loading failed
> Execution halted
> ERROR: loading failed
> * removing 
> '/<>/debian/r-bioc-rtracklayer/usr/lib/R/site-library/rtracklayer'
> dh_auto_install: R CMD INSTALL -l 
> /<>/debian/r-bioc-rtracklayer/usr/lib/R/site-library --clean . 
> "--built-timestamp='Sun, 04 Dec 2016 21:53:17 +0100'" returned exit code 1
> debian/rules:4: recipe for target 'binary' failed
> make: *** [binary] Error 25

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/r-bioc-rtracklayer_1.34.1-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
r-bioc-rtracklayer, 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.
Andreas Tille  (supplier of updated r-bioc-rtracklayer 
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, 23 Aug 2017 19:43:41 +0200
Source: r-bioc-rtracklayer
Binary: r-bioc-rtracklayer
Architecture: source
Version: 1.36.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 r-bioc-rtracklayer - GNU R interface to genome browsers and their annotation 
tracks
Closes: 871333
Changes:
 r-bioc-rtracklayer (1.36.4-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #871333
   * Standards-Version: 4.0.1 (no changes needed)
   * Remove unused lintian override
Checksums-Sha1:
 673abe6aa0ad0603fac753b26fc42394328beb6f 2230 

Bug#873016: [Pkg-javascript-devel] Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

[Pirate Praveen]

On ബുധന്‍ 23 ആഗസ്റ്റ് 2017 11:33 വൈകു, Jonas Smedegaard wrote:
> Package: node-lodash-packages
> Severity: serious
> Justification: Policy 2.1

I do not think the root issue is serious, but only important.

> The source package node-lodash-packages does not contain the source form
> preferred for editing by upstream.  Instead, upstream documents how the
> contents of that code is generated from the sources included in Debian
> in the source package node-lodash.

Adding a build dependency on node-lodash would be enough for the policy
requirement.



signature.asc
Description: OpenPGP digital signature

Processed: Bug#872992 marked as pending

[Debian Bug Tracking System]

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

> tag 872992 pending
Bug #872992 [src:pytest-qt] pytest-qt: FTBFS: Tests failures because of logging 
changes in Qt
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#872992: marked as pending

[Ghislain Antony Vaillant]

tag 872992 pending
thanks

Hello,

Bug #872992 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/python-modules/packages/pytest-qt.git/commit/?id=a66fe10

---
commit a66fe10c3bc5930dcde4fcc813b9fcbde59bfdb3
Author: Ghislain Antony Vaillant 
Date:   Wed Aug 23 19:27:29 2017 +0100

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index 05d5fc6..3db4200 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+pytest-qt (2.1.2-3) unstable; urgency=medium
+
+  * Fix FTBFS due to logging changes in Qt.
+Thanks to Dmitry Shachnev for the patch (Closes: #872992)
+  * Use DEB_BUILD_OPTIONS for nocheck and nodoc guards
+  * Fixup the Vcs-Browser URI
+  * Bump standards version to 4.1.0
+
+ -- Ghislain Antony Vaillant   Wed, 23 Aug 2017 19:26:33 
+0100
+
 pytest-qt (2.1.2-2) unstable; urgency=medium
 
   * Drop autopkgtests for PySide.

Bug#872866: wily: Appears to contain non-free code

[Thorsten Alteholz]

control: severity -1 normal
thanks

Hi Jacob,

thanks a lot for your bug report. Please have a look at Doc/sam/README. In 
this file the license of libframe and libXg is clearly mentioned. This 
license is already added to the debian/copyright of the package.


As you are right that some copyright holders are missing and need to be 
added, I am not closing this bug. Unfortunately the package is orphaned, 
so maybe you want to take care of it?


  Thorsten

Processed: Re: wily: Appears to contain non-free code

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #872866 [wily] wily: Appears to contain non-free code
Severity set to 'normal' from 'serious'

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

Bug#873016: node-lodash-packages: not preferred form for source: Should be built from node-lodash

[Jonas Smedegaard]

Package: node-lodash-packages
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The source package node-lodash-packages does not contain the source form
preferred for editing by upstream.  Instead, upstream documents how the
contents of that code is generated from the sources included in Debian
in the source package node-lodash.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmdw4sACgkQLHwxRsGg
ASGTug/2Lp398huckuiUYZpi1L3JQ1gKA52++Vn/q57MoT1nRd/9FvY9dkRuNmCw
B1kD+wp/Fd/MkWxdP+b/ZaoizQbbpGLg6BT1AHqFht1iwLl1pNDYsJkHx3R9LqTW
JCOfaKsetIcW+DPzYV6sbaqaULWtxK1p1oN9xcYsFaeD+vBk8D1dIerT3E6wLbRJ
B6p/h7T6k1nHZdik1eTD7Hyereocu8QzicNhkY0lCOmqa//bWTrkrP4xPICM0JEw
g3U8VlUHkezb+XlP/IcRp7iK6Oz7L5c2ZBmzxxmku/tapGMbtqm7JI/lvjuNldyZ
TKepo6jywEjJAx6F3D35U5vEla22TRpWNm0UP4S9IzAxfl4nGofY2vOp1lR8cNbb
LMhXWIdIcAA5NKwMxnzSZv4zH1tEPB8GrPNPUM8FCuwQN2mNxlURhkb7S8TZX2di
QdmvR6lRuECrOUWS6VeRsPK1HeHqXkKDo52fSJK5yCfJChHxPHtNUv+mARs3BWdC
rZVQcVXm4BoQp2OdwsqIH5Wg/h89GApRVh16C/6bbjWe7tim7QCt0W6B67woHmU2
cK41cZVvcCawPFzC1N2ggk8SqI+3bxsokN/YvAUibZRpj+box92QlJNd9Yak9IlF
7BU/XDLRlrRegafJ1KRm8P66v14D+O3PfAso3nCQCAHFI2MtXA==
=Kn8q
-END PGP SIGNATURE-

Bug#853699: marked as done (vdr-plugin-live: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 17:54:27 +
with message-id 
and subject line Bug#853699: fixed in vdr-plugin-live 2.3.1-1
has caused the Debian Bug report #853699,
regarding vdr-plugin-live: 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.)


-- 
853699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vdr-plugin-live
Version: 0.3.0+git20160123-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/vdr-plugin-live_0.3.0+git20160123-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/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
In file included from ../setup.h:8:0,
 from multischedule.ecpp:10:
../live.h:36:7: warning: 'template class std::auto_ptr' is deprecated 
[-Wdeprecated-declarations]
  std::auto_ptr< ServerThread > m_thread;
   ^~~~
In file included from /usr/include/c++/7/bits/locale_conv.h:41:0,
 from /usr/include/c++/7/locale:43,
 from /usr/include/cxxtools/char.h:420,
 from /usr/include/cxxtools/string.h:34,
 from /usr/include/cxxtools/serializationinfo.h:33,
 from /usr/include/tnt/tntconfig.h:35,
 from /usr/include/tnt/sessionscope.h:34,
 from /usr/include/tnt/ecpp.h:35,
 from multischedule.cpp:6:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
multischedule.ecpp: In member function 'virtual unsigned int 
{anonymous}::_component_::operator()(tnt::HttpRequest&, tnt::HttpReply&, 
tnt::QueryParams&)':
multischedule.ecpp:302:50: error: ISO C++ forbids comparison between pointer 
and integer [-fpermissive]
   if ( Channel->GroupSep() || Channel->Name() == '\0' )
  ^~~~
Makefile:26: recipe for target 'multischedule.o' failed
make[2]: *** [multischedule.o] Error 1
make[2]: Leaving directory 
'/<>/vdr-plugin-live-0.3.0+git20160123/pages'
make[2]: Entering directory 
'/<>/vdr-plugin-live-0.3.0+git20160123/css'
ecppc   -b -m "text/css" styles.css
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include  
-Wno-overloaded-virtual -Wno-unused-function -c -D_GNU_SOURCE 
-DPLUGIN_NAME_I18N='"live"' -DTNTVERSION=22100 -DCXXTOOLVER=22100 
-DHAVE_LIBPCRECPP -I/include -I.. styles.cpp
ar r libcss.a styles.o
ar: creating libcss.a
rm styles.cpp
make[2]: Leaving directory '/<>/vdr-plugin-live-0.3.0+git20160123/css'
make[2]: Entering directory 
'/<>/vdr-plugin-live-0.3.0+git20160123/javascript'
ecppc   -b -m "text/javascript" treeview.js
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include  
-Wno-overloaded-virtual -Wno-unused-function -c -D_GNU_SOURCE 
-DPLUGIN_NAME_I18N='"live"' -DTNTVERSION=22100 -DCXXTOOLVER=22100 
-DHAVE_LIBPCRECPP -I/include -I.. treeview.cpp
ar r libjavascript.a treeview.o
ar: creating libjavascript.a
rm treeview.cpp
make[2]: Leaving directory 
'/<>/vdr-plugin-live-0.3.0+git20160123/javascript'
g++ -g -O2 

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #822603 [src:network-config] network-config: depends on gksu which is 
deprecated
Severity set to 'important' from 'serious'

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

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #822601 [src:xnetcardconfig] xnetcardconfig: depends on gksu which is 
deprecated
Severity set to 'important' from 'serious'

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

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is 
deprecated
Severity set to 'important' from 'serious'

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

Processed: Re: Bug#822595: Raising severity to serious for packages depending on gksu

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #822600 [src:sbackup] sbackup: depends on gksu which is deprecated
Severity set to 'important' from 'serious'

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

Bug#822595: Raising severity to serious for packages depending on gksu

[Mike Gabriel]

Control: severity -1 important

Hi Jeremy, hi all,

On  Mi 05 Jul 2017 02:21:07 CEST, Jeremy Bicha wrote:


Control: severity -1 serious
Control: tags -1 -stretch +buster

For the next major stable release of Debian (codenamed "buster"), the
Debian GNOME team plans to default to GNOME on Wayland where gksu does
not work. We do not intend to release "buster" with gksu. Therefore, I
am raising the severity of this issue to serious.

Please drop the dependency on gksu because the Debian GNOME team plans
to remove gksu from Debian soon.

On behalf of the Debian GNOME team,
Jeremy Bicha


I will drop severity temporarily for this bug, because we need  
caja-extensions 1.18 in testing (rather than some older 1.16 version).


Once caja-admin has landed in unstable, I will upload caja-extensions  
without caja-gksu being built to address this bug.


Hope dropping severity for now is ok. I fully get the need of  
caja-gksu removal and by bringing caja-admin to Debian, we have worked  
on that. However, the NEW queue processing currently take so long...


Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpJZgV6EcJgE.pgp
Description: Digitale PGP-Signatur

Bug#822595: Raising severity to serious for packages depending on gksu

[Jeremy Bicha]

On Wed, Aug 23, 2017 at 1:41 PM, Mike Gabriel
 wrote:
> I will drop severity temporarily for this bug, because we need
> caja-extensions 1.18 in testing (rather than some older 1.16 version).
>
> Once caja-admin has landed in unstable, I will upload caja-extensions
> without caja-gksu being built to address this bug.
>
> Hope dropping severity for now is ok.

That's fine.

Except you accidentally changed the status of some other bugs too!
(Check your CC line)

Thanks,
Jeremy Bicha

Bug#872598: udev-udeb: no input in graphical installer

[Michael Biebl]

Hi KiBi

Am 23.08.2017 um 10:08 schrieb Cyril Brulebois:
> Would you be OK with a minimal NMU to fix the missing file? This issue has
> been blocking the D-I Buster Alpha 1 release for weeks already (even if it
> hadn't been diagnosed and reported against udev-udeb until recently), and
> I'd be happy to get a release out the door ASAP, since I won't have much
> time in the following weeks.

Felipe has already looked into this issue a bit and discovered more
inconsistencies between the deb and udeb build for udev. This will
probably need some more time to review/investigate properly, so feel
free to go ahead with the NMU!

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



signature.asc
Description: OpenPGP digital signature

Bug#872860: marked as done (csound FTBFS with libgmm++-dev 5.2+dfsg1-5)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 17:34:38 +
with message-id 
and subject line Bug#872860: fixed in csound 1:6.09.1~dfsg-2
has caused the Debian Bug report #872860,
regarding csound FTBFS with libgmm++-dev 5.2+dfsg1-5
to be marked as done.

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

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


-- 
872860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: csound
Version: 1:6.09.1~dfsg-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/csound.html

...
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp: In member function 
'int la_i_print_vr_t::init(CSOUND*)':
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp:633:12: error: no 
match for 'operator<<' (operand types are 'std::ostringstream {aka 
std::__cxx11::basic_ostringstream}' and 'std::vector')
 stream << array->vr << std::endl;
 ~~~^~~~
In file included from /usr/include/c++/7/istream:39:0,
 from /usr/include/c++/7/sstream:38,
 from /usr/include/c++/7/complex:45,
 from 
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp:345:
/usr/include/c++/7/ostream:108:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, 
_Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ostream_type& 
(*)(std::basic_ostream<_CharT, _Traits>::__ostream_type&)) [with _CharT = char; 
_Traits = std::char_traits; std::basic_ostream<_CharT, 
_Traits>::__ostream_type = std::basic_ostream]
   operator<<(__ostream_type& (*__pf)(__ostream_type&))
   ^~~~
/usr/include/c++/7/ostream:108:7: note:   no known conversion for argument 1 
from 'std::vector' to 'std::basic_ostream::__ostream_type& 
(*)(std::basic_ostream::__ostream_type&) {aka std::basic_ostream& 
(*)(std::basic_ostream&)}'
/usr/include/c++/7/ostream:117:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, 
_Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ios_type& 
(*)(std::basic_ostream<_CharT, _Traits>::__ios_type&)) [with _CharT = char; 
_Traits = std::char_traits; std::basic_ostream<_CharT, 
_Traits>::__ostream_type = std::basic_ostream; std::basic_ostream<_CharT, 
_Traits>::__ios_type = std::basic_ios]
   operator<<(__ios_type& (*__pf)(__ios_type&))
   ^~~~
/usr/include/c++/7/ostream:117:7: note:   no known conversion for argument 1 
from 'std::vector' to 'std::basic_ostream::__ios_type& 
(*)(std::basic_ostream::__ios_type&) {aka std::basic_ios& 
(*)(std::basic_ios&)}'
/usr/include/c++/7/ostream:127:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, 
_Traits>::operator<<(std::ios_base& (*)(std::ios_base&)) [with _CharT = char; 
_Traits = std::char_traits; std::basic_ostream<_CharT, 
_Traits>::__ostream_type = std::basic_ostream]
   operator<<(ios_base& (*__pf) (ios_base&))
   ^~~~
/usr/include/c++/7/ostream:127:7: note:   no known conversion for argument 1 
from 'std::vector' to 'std::ios_base& (*)(std::ios_base&)'
/usr/include/c++/7/ostream:166:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(long 
int) [with _CharT = char; _Traits = std::char_traits; 
std::basic_ostream<_CharT, _Traits>::__ostream_type = std::basic_ostream]
   operator<<(long __n)
   ^~~~
/usr/include/c++/7/ostream:166:7: note:   no known conversion for argument 1 
from 'std::vector' to 'long int'
/usr/include/c++/7/ostream:170:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(long 
unsigned int) [with _CharT = char; _Traits = std::char_traits; 
std::basic_ostream<_CharT, _Traits>::__ostream_type = std::basic_ostream]
   operator<<(unsigned long __n)
   ^~~~
/usr/include/c++/7/ostream:170:7: note:   no known conversion for argument 1 
from 'std::vector' to 'long unsigned int'
/usr/include/c++/7/ostream:174:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(bool) 
[with _CharT = char; _Traits = std::char_traits; 
std::basic_ostream<_CharT, _Traits>::__ostream_type = std::basic_ostream]
   operator<<(bool __n)
   ^~~~
/usr/include/c++/7/ostream:174:7: note:   no known conversion for argument 1 
from 'std::vector' to 'bool'
In file included from /usr/include/c++/7/ostream:693:0,
 from 

Bug#871918: libssl1.1: tls_process_server_hello:unsupported protocol

[Sebastian Andrzej Siewior]

On 2017-08-23 09:32:12 [+0200], Michal Palenik wrote:
> it look like a something strange with libssl1.1 version 1.1.0f-4 and
> some of the certificates.
> 
> openssl s_client -connect mail7.hostmaster.sk:465 (and port 995)
> 
> gives some buggy output (including connections with postfix or
> fetchmail), (older versions on libssl1.1 were OK), however, others like

The server supports only TLS1.0, see also [0]. You could forward [0] to
the hoster and let him make the red go away.

[0] https://www.ssllabs.com/ssltest/analyze.html?d=mail7.hostmaster.sk

> michal

Sebastian

Bug#872275: slic3r-prusa: diff for NMU version 1.37.0+dfsg-1.1

[gregor herrmann]

Control: tags 872275 + pending

Dear maintainer,

I've prepared an NMU for slic3r-prusa (versioned as 1.37.0+dfsg-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Nick Drake: Ride
diff -Nru slic3r-prusa-1.37.0+dfsg/debian/changelog slic3r-prusa-1.37.0+dfsg/debian/changelog
--- slic3r-prusa-1.37.0+dfsg/debian/changelog	2017-08-05 19:04:13.0 +0200
+++ slic3r-prusa-1.37.0+dfsg/debian/changelog	2017-08-23 19:17:28.0 +0200
@@ -1,3 +1,13 @@
+slic3r-prusa (1.37.0+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Loadable library and perl binary mismatch":
+add override_dh_perl in debian/rules to make dh_perl search for perl
+modules in the private directory as well.
+(Closes: #872275)
+
+ -- gregor herrmann   Wed, 23 Aug 2017 19:17:28 +0200
+
 slic3r-prusa (1.37.0+dfsg-1) unstable; urgency=medium
 
   * [3561f7e] New upstream version 1.37.0+dfsg
diff -Nru slic3r-prusa-1.37.0+dfsg/debian/rules slic3r-prusa-1.37.0+dfsg/debian/rules
--- slic3r-prusa-1.37.0+dfsg/debian/rules	2017-08-05 19:04:13.0 +0200
+++ slic3r-prusa-1.37.0+dfsg/debian/rules	2017-08-16 23:35:03.0 +0200
@@ -45,3 +45,6 @@
 	# Install zsh completion
 	mkdir -p $(CURDIR)/debian/slic3r-prusa/usr/share/zsh/vendor-completions
 	cp utils/zsh/functions/_slic3r $(CURDIR)/debian/slic3r-prusa/usr/share/zsh/vendor-completions/_slic3r-prusa
+
+override_dh_perl:
+	dh_perl /usr/lib/slic3r-prusa


signature.asc
Description: Digital Signature

Processed: slic3r-prusa: diff for NMU version 1.37.0+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 872275 + pending
Bug #872275 [slic3r-prusa] slic3r-prusa: Loadable library and perl binary 
mismatch
Added tag(s) pending.

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

Processed: Reassign to gcc-7

[Debian Bug Tracking System]

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

> reassign 872987 gcc-7
Bug #872987 [pspp] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Bug reassigned from package 'pspp' to 'gcc-7'.
No longer marked as found in versions pspp/1.0.0-1.
Ignoring request to alter fixed versions of bug #872987 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Bug#872860 marked as pending

[Debian Bug Tracking System]

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

> tag 872860 pending
Bug #872860 [src:csound] csound FTBFS with libgmm++-dev 5.2+dfsg1-5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#872860: marked as pending

[Felipe Sateler]

tag 872860 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/csound.git/commit/?id=550dc39

---
commit 550dc39611a3ea1cf33ab8bdd73b103e0f3d5faf
Author: Felipe Sateler 
Date:   Wed Aug 23 13:12:54 2017 -0300

Release

diff --git a/debian/changelog b/debian/changelog
index 364c9b5..c6dd98f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+csound (1:6.09.1~dfsg-2) unstable; urgency=medium
+
+  * Fix build failure with GMM 5.2+ (Closes: #872860)
+
+ -- Felipe Sateler   Wed, 23 Aug 2017 13:12:48 -0300
+
 csound (1:6.09.1~dfsg-1) unstable; urgency=medium
 
   * New upstream version 6.09.1~dfsg

Processed: Affects

[Debian Bug Tracking System]

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

> affects 871514 pspp
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Added indication that 871514 affects pspp
Added indication that 871538 affects pspp
Added indication that 872438 affects pspp
> 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
872438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): Merge bugs

[Debian Bug Tracking System]

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

> severity 872987 serious
Bug #872987 [pspp] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Severity set to 'serious' from 'normal'
> merge 872987 871514
Bug #872987 [pspp] pspp 1.0.0-1 FTBFS on mips64el architecture on debian
Unable to merge bugs because:
forwarded of #872438 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' 
not ''
affects of #872438 is 
'postgresql-9.6,src:aptitude,clamav,apparmor,ngircd,src:subversion,postgresql-10,givaro'
 not ''
package of #872438 is 'gcc-7' not 'pspp'
forwarded of #871538 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' 
not ''
affects of #871538 is 
'postgresql-9.6,src:aptitude,clamav,apparmor,ngircd,src:subversion,postgresql-10,givaro'
 not ''
package of #871538 is 'gcc-7' not 'pspp'
forwarded of #871514 is 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803' 
not ''
affects of #871514 is 
'postgresql-9.6,src:aptitude,clamav,apparmor,ngircd,src:subversion,postgresql-10,givaro'
 not ''
package of #871514 is 'gcc-7' not 'pspp'
Failed to merge 872987: Did not alter merged bugs.

> affects 871514 pspp
Failed to mark 871514 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/871514 -- Unable to lock 
/org/bugs.debian.org/spool/lock/871514 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/871514 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

>
End of message, 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
872438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872438
872987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#871514: clamav: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 872438
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Bug #872438 [gcc-7] src:nodejs: FTBFS on mips64el: Can't determine the arch of 
./node
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803'.
Removed indication that 872438 affects nodejs
Added indication that 872438 affects 
postgresql-9.6,src:aptitude,clamav,apparmor,ngircd,src:subversion,postgresql-10,givaro
Marked as found in versions gcc-7/7.1.0-10, gcc-7/7.2.0-1, and gcc-7/7.1.0-13.
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Removed indication that 871538 affects src:aptitude, clamav, ngircd, 
postgresql-9.6, src:subversion, givaro, postgresql-10, and apparmor
Added indication that 871538 affects 
postgresql-9.6,src:aptitude,clamav,apparmor,ngircd,src:subversion,postgresql-10,givaro
Removed indication that 871514 affects apparmor, postgresql-10, src:subversion, 
givaro, ngircd, postgresql-9.6, clamav, and src:aptitude
Added indication that 871514 affects 
postgresql-9.6,src:aptitude,clamav,apparmor,ngircd,src:subversion,postgresql-10,givaro
Merged 871514 871538 872438

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

Bug#871514: clamav: FTBFS on mips64el

[James Cowgill]

Control: forcemerge -1 872438

Hi,

Just a brief update on this bug. Unfortunately there is still no "good" fix.

As I have written in a few places now, the bug occurs on mips64el where
a "small" variable gets spilled to the stack. It is possible that GCC
writes the variable to the stack using a small instruction (like sw for
a 32-bit store) and then reloads it as a 64-bit integer (using ld). This
means that the upper bits of the loaded value will contain garbage
causing chaos later when the value is used.

The bug is almost certainly in the LRA part of the compiler which
handles spilling values to the stack. One possible temporary workaround
(originally suggested by Adrian Bunk) would be to disable LRA on
mips64el. I have tested the attached patch which does seem to work. The
disadvantage of this is that non-LRA hasn't really been tested on MIPS
for ages so it might introduce some other bugs. Given the scale of this
issue it might be worth it?

This bug is very closely related to an earlier GCC bootstrap failure on
mips64el: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78660
In comment 17 Matthew sent a patch and applying it also fixes this bug.
However, he tells me it has some other issues and isn't suitable to be
applied (which is presumably why it was reverted).

James
commit 21398b7c319ed013741a9b249cb2315a098b6753
Author: James Cowgill 
Date:   Tue Aug 22 11:33:47 2017 +0100

Disable LRA on mips as a workaround

diff --git a/gcc/config/mips/mips.c b/gcc/config/mips/mips.c
index 563f74b74f0..c89067cf89c 100644
--- a/gcc/config/mips/mips.c
+++ b/gcc/config/mips/mips.c
@@ -19738,7 +19738,7 @@ mips_option_override (void)
   else if (ISA_MIPS1 && !TARGET_FLOAT32)
 error ("%<-march=%s%> requires %<-mfp32%>", mips_arch_info->name);
   else if (TARGET_FLOATXX && !mips_lra_flag)
-error ("%<-mfpxx%> requires %<-mlra%>");
+mips_lra_flag = 1;
 
   /* End of code shared with GAS.  */
 
diff --git a/gcc/config/mips/mips.opt b/gcc/config/mips/mips.opt
index ced243218e3..cf7795c63e4 100644
--- a/gcc/config/mips/mips.opt
+++ b/gcc/config/mips/mips.opt
@@ -385,7 +385,7 @@ Target Report Mask(SYNCI)
 Use synci instruction to invalidate i-cache.
 
 mlra
-Target Report Var(mips_lra_flag) Init(1) Save
+Target Report Var(mips_lra_flag) Init(0) Save
 Use LRA instead of reload.
 
 mlxc1-sxc1


signature.asc
Description: OpenPGP digital signature

Processed: fixed 869074 in 0.188+dfsg.1-1

[Debian Bug Tracking System]

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

> fixed 869074 0.188+dfsg.1-1
Bug #869074 [src:mame] mame FTBFS on i386: virtual memory exhausted
Marked as fixed in versions mame/0.188+dfsg.1-1.
> thanks
Stopping processing here.

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

Bug#873008: hfst FTBFS on big endian: FAIL: test

[Adrian Bunk]

Source: hfst
Version: 3.12.2~r3289-1
Severity: serious

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

...
Making check in tools
make[3]: Entering directory '/<>/tools'
Making check in src
make[4]: Entering directory '/<>/tools/src'
Making check in hfst-proc
make[5]: Entering directory '/<>/tools/src/hfst-proc'
make[5]: Nothing to be done for 'check'.
make[5]: Leaving directory '/<>/tools/src/hfst-proc'
Making check in hfst-twolc
make[5]: Entering directory '/<>/tools/src/hfst-twolc'
Making check in src
make[6]: Entering directory '/<>/tools/src/hfst-twolc/src'
make[6]: Nothing to be done for 'check'.
make[6]: Leaving directory '/<>/tools/src/hfst-twolc/src'
Making check in test
make[6]: Entering directory '/<>/tools/src/hfst-twolc/test'
/usr/bin/make  test1 test1.txt_fst test10 test10.txt_fst test11 test11.txt_fst 
test12 test12.txt_fst test13 test13.txt_fst test14 test14.txt_fst test15 
test15.txt_fst test16 test16.txt_fst test17 test17.txt_fst test18 
test18.txt_fst test19 test19.txt_fst test2 test2.txt_fst test20 test20.txt_fst 
test21 test21.txt_fst test22 test22.txt_fst test23 test23.txt_fst test24 
test24.txt_fst test25 test25.txt_fst test26 test26.txt_fst test27 
test27.txt_fst test28 test28.txt_fst test29 test29.txt_fst test3 test3.txt_fst 
test30 test30.txt_fst test31 test31.txt_fst test32 test32.txt_fst test33 
test33.txt_fst test34 test34.txt_fst test35 test35.txt_fst test36 
test36.txt_fst test37 test37.txt_fst test38 test38.txt_fst test39 
test39.txt_fst test4 test4.txt_fst test40 test40.txt_fst test41 test41.txt_fst 
test42 test42.txt_fst test43 test43.txt_fst test44 test44.txt_fst test45 
test45.txt_fst test46 test46.txt_fst test47 test47.txt_fst test48 
test48.txt_fst test49 test49.txt_fst test5 test5.txt_fst tes
 t51 test51.txt_fst test52 test52.txt_fst test53 test53.txt_fst test54 
test54.txt_fst test55 test55.txt_fst test56 test56.txt_fst test57 
test57.txt_fst test58 test58.txt_fst test59 test59.txt_fst test6 test6.txt_fst 
test60 test60.txt_fst test61 test61.txt_fst test62 test62.txt_fst test7 
test7.txt_fst test8 test8.txt_fst test9 test9.txt_fst
make[7]: Entering directory '/<>/tools/src/hfst-twolc/test'
make[7]: Nothing to be done for 'test1'.
make[7]: Nothing to be done for 'test1.txt_fst'.
make[7]: Nothing to be done for 'test10'.
make[7]: Nothing to be done for 'test10.txt_fst'.
make[7]: Nothing to be done for 'test11'.
make[7]: Nothing to be done for 'test11.txt_fst'.
make[7]: Nothing to be done for 'test12'.
make[7]: Nothing to be done for 'test12.txt_fst'.
make[7]: Nothing to be done for 'test13'.
make[7]: Nothing to be done for 'test13.txt_fst'.
make[7]: Nothing to be done for 'test14'.
make[7]: Nothing to be done for 'test14.txt_fst'.
make[7]: Nothing to be done for 'test15'.
make[7]: Nothing to be done for 'test15.txt_fst'.
make[7]: Nothing to be done for 'test16'.
make[7]: Nothing to be done for 'test16.txt_fst'.
make[7]: Nothing to be done for 'test17'.
make[7]: Nothing to be done for 'test17.txt_fst'.
make[7]: Nothing to be done for 'test18'.
make[7]: Nothing to be done for 'test18.txt_fst'.
make[7]: Nothing to be done for 'test19'.
make[7]: Nothing to be done for 'test19.txt_fst'.
make[7]: Nothing to be done for 'test2'.
make[7]: Nothing to be done for 'test2.txt_fst'.
make[7]: Nothing to be done for 'test20'.
make[7]: Nothing to be done for 'test20.txt_fst'.
make[7]: Nothing to be done for 'test21'.
make[7]: Nothing to be done for 'test21.txt_fst'.
make[7]: Nothing to be done for 'test22'.
make[7]: Nothing to be done for 'test22.txt_fst'.
make[7]: Nothing to be done for 'test23'.
make[7]: Nothing to be done for 'test23.txt_fst'.
make[7]: Nothing to be done for 'test24'.
make[7]: Nothing to be done for 'test24.txt_fst'.
make[7]: Nothing to be done for 'test25'.
make[7]: Nothing to be done for 'test25.txt_fst'.
make[7]: Nothing to be done for 'test26'.
make[7]: Nothing to be done for 'test26.txt_fst'.
make[7]: Nothing to be done for 'test27'.
make[7]: Nothing to be done for 'test27.txt_fst'.
make[7]: Nothing to be done for 'test28'.
make[7]: Nothing to be done for 'test28.txt_fst'.
make[7]: Nothing to be done for 'test29'.
make[7]: Nothing to be done for 'test29.txt_fst'.
make[7]: Nothing to be done for 'test3'.
make[7]: Nothing to be done for 'test3.txt_fst'.
make[7]: Nothing to be done for 'test30'.
make[7]: Nothing to be done for 'test30.txt_fst'.
make[7]: Nothing to be done for 'test31'.
make[7]: Nothing to be done for 'test31.txt_fst'.
make[7]: Nothing to be done for 'test32'.
make[7]: Nothing to be done for 'test32.txt_fst'.
make[7]: Nothing to be done for 'test33'.
make[7]: Nothing to be done for 'test33.txt_fst'.
make[7]: Nothing to be done for 'test34'.
make[7]: Nothing to be done for 'test34.txt_fst'.
make[7]: Nothing to be done for 'test35'.
make[7]: Nothing to be done for 'test35.txt_fst'.
make[7]: Nothing to be done for 'test36'.
make[7]: Nothing to be done for 'test36.txt_fst'.
make[7]: Nothing to be done for 'test37'.
make[7]: Nothing to be 

Bug#865633:

[Liang Guo]

Hi,

I test this problem on the latest Debian sid, and I cannot reproduce
this problem.

This is my software version:

spice client:
Debian sid
virt-manager  1:1.4.0-6
virt-viewer   5.0-1
gir1.2-spice-client-glib-2.0 0.33-3.3
gir1.2-spice-client-gtk-3.0 0.33-3.3
libspice-client-glib-2.0-8:amd64 0.33-3.3
libspice-client-gtk-3.0-5:amd64 0.33-3.3
libspice-server1:amd64 0.12.8-2.2
spice-client-glib-usb-acl-helper 0.33-3.3

vm server:
Debian sid
libspice-server1:amd64 0.12.8-2.2
qemu-system-x86 1:2.8+dfsg-7
libvirt0 3.6.0-1

vm:
Debian sid:
gnome 1:3.22+3
gdm3  3.24.2-3
libwayland-bin1.14.0-1

Would you like upgrade your system to sid, and check if this problem
still exist ?

BTW: do you have any other DE installed, does it works correctly ?

Thanks,
-- 
Liang Guo

Bug#869816: marked as done (openjdk-7: several vulnerabilities)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 16:26:18 +
with message-id 
and subject line Bug#869816: fixed in openjdk-7 7u151-2.6.11-1
has caused the Debian Bug report #869816,
regarding openjdk-7: several vulnerabilities
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.)


-- 
869816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-7
Version: 7u131-2.6.9-3
Severity: grave

Hi,

openjdk-7 needs fixing for the recent Oracle CPU.

Thanks,
Emilio

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

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: openjdk-7
Source-Version: 7u151-2.6.11-1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-7 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, 23 Aug 2017 16:02:57 +0200
Source: openjdk-7
Binary: openjdk-7-jdk openjdk-7-jre-headless openjdk-7-jre openjdk-7-jre-lib 
openjdk-7-demo openjdk-7-source openjdk-7-doc openjdk-7-dbg icedtea-7-jre-jamvm 
openjdk-7-jre-zero
Architecture: source
Version: 7u151-2.6.11-1
Distribution: experimental
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 icedtea-7-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
 openjdk-7-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-7-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-7-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-7-jdk - OpenJDK Development Kit (JDK)
 openjdk-7-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-7-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-7-jre-lib - OpenJDK Java runtime (architecture independent libraries)
 openjdk-7-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-7-source - OpenJDK Development Kit (JDK) source files
Closes: 766601 827741 863007 865533 865749 869816
Changes:
 openjdk-7 (7u151-2.6.11-1) experimental; urgency=medium
 .
   * IcedTea release 2.6.11 (based on 7u151). Closes: #869816.
   * Security fixes:
 - S8163958, CVE-2017-10102: Improved garbage collection.
 - S8167228: Update to libpng 1.6.28.
 - S8169209, CVE-2017-10053: Improved image post-processing steps.
 - S8169392, CVE-2017-10067: Additional jar validation steps.
 - S8170966, CVE-2017-10081: Right parenthesis issue.
 - S8172204, CVE-2017-10087: Better Thread Pool execution.
 - S8172461, CVE-2017-10089: Service Registration Lifecycle.
 - S8172465, CVE-2017-10090: Better handling of channel groups.
 - S8172469, CVE-2017-10096: Transform Transformer Exceptions.
 - S8173286, CVE-2017-10101: Better reading of text catalogs.
 - S8173697, CVE-2017-10107: Less Active Activations.
 - S8173770, CVE-2017-10074: Image conversion improvements.
 - S8174098, CVE-2017-10110: Better image fetching.
 - S8174105, CVE-2017-10108: Better naming attribution.
 - S8174113, CVE-2017-10109: Better sourcing of code.
 - S8174770: Check registry registration location.
 - S8174873: Improved certificate processing.
 - S8175106, CVE-2017-10115: Higher quality DSA operations.
 - S8175110, CVE-2017-10118: Higher quality ECDSA operations.
 - S8176055: JMX diagnostic improvements.
 - S8176067, CVE-2017-10116: Proper directory lookup processing.
 - S8176760, CVE-2017-10135: Better handling of PKCS8 material.
 - S8178135, 

Bug#871062: marked as done (collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated writing up to 1023 bytes into a region of size 1010 [-Werror=format-truncation=])

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 16:34:19 +
with message-id 
and subject line Bug#871062: fixed in collectd 5.7.2-1
has caused the Debian Bug report #871062,
regarding collectd: FTBFS: client.c:621:23: error: '%s' directive output may be 
truncated writing up to 1023 bytes into a region of size 1010 
[-Werror=format-truncation=]
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.)


-- 
871062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: collectd
Version: 5.7.1-1.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):
> /bin/bash ../../libtool  --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I../../src   -I../../src/libcollectdclient/collectd 
> -I../../src/libcollectdclient/collectd -I../../src/daemon  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/<>/debian/include -UCONFIGFILE 
> -DCONFIGFILE='"/etc/collectd/collectd.conf"' -Wall -Werror -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wno-error=deprecated-declarations -c -o 
> libcollectdclient_la-client.lo `test -f 'client.c' || echo './'`client.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../src 
> -I../../src/libcollectdclient/collectd -I../../src/libcollectdclient/collectd 
> -I../../src/daemon -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/<>/debian/include -UCONFIGFILE 
> -DCONFIGFILE=\"/etc/collectd/collectd.conf\" -Wall -Werror -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wno-error=deprecated-declarations -c client.c  
> -fPIC -DPIC -o .libs/libcollectdclient_la-client.o
> client.c: In function 'lcc_getval':
> client.c:621:23: error: '%s' directive output may be truncated writing up to 
> 1023 bytes into a region of size 1010 [-Werror=format-truncation=]
>  LCC_SET_ERRSTR(c, "Server error: %s", res.message);
>^   ~
> client.c:94:48: note: in definition of macro 'LCC_SET_ERRSTR'
>  snprintf((c)->errbuf, sizeof((c)->errbuf), __VA_ARGS__); 
>   \
> ^~~
> In file included from /usr/include/stdio.h:938:0,
>  from client.c:42:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
> '__builtin___snprintf_chk' output between 15 and 1038 bytes into a 
> destination of size 1024
>return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
>   ^~~~
> __bos (__s), __fmt, __va_arg_pack ());
> ~
> client.c: In function 'lcc_putval':
> client.c:754:23: error: '%s' directive output may be truncated writing up to 
> 1023 bytes into a region of size 1010 [-Werror=format-truncation=]
>  LCC_SET_ERRSTR(c, "Server error: %s", res.message);
>^   ~
> client.c:94:48: note: in definition of macro 'LCC_SET_ERRSTR'
>  snprintf((c)->errbuf, sizeof((c)->errbuf), __VA_ARGS__); 
>   \
> ^~~
> In file included from /usr/include/stdio.h:938:0,
>  from client.c:42:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
> '__builtin___snprintf_chk' output between 15 and 1038 bytes into a 
> destination of size 1024
>return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
>   ^~~~
> __bos (__s), __fmt, __va_arg_pack ());
> ~
> client.c: In function 'lcc_flush':
> client.c:802:23: error: '%s' directive output may be truncated writing up to 
> 1023 bytes into a region of size 1010 [-Werror=format-truncation=]
>  LCC_SET_ERRSTR(c, "Server error: %s", res.message);
>^   ~
> client.c:94:48: note: in definition of macro 'LCC_SET_ERRSTR'
>  snprintf((c)->errbuf, sizeof((c)->errbuf), __VA_ARGS__); 
>   \
> ^~~
> In file included from /usr/include/stdio.h:938:0,
>  from client.c:42:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
> '__builtin___snprintf_chk' 

Bug#872276: marked as done (collectd: FTBFS with linux-libc-dev >= 4.12: please bundle asm/msr-index.h)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 16:34:19 +
with message-id 
and subject line Bug#872276: fixed in collectd 5.7.2-1
has caused the Debian Bug report #872276,
regarding collectd: FTBFS with linux-libc-dev >= 4.12: please bundle 
asm/msr-index.h
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.)


-- 
872276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: collectd
Version: 5.7.1-1.1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

After patching bug #871062, I found that collectd still FTBFS on amd64 and
i386 in Ubuntu because the asm/msr-index.h header is no longer shipped by
linux-libc-dev >= 4.12.  This has been dropped by upstream for reasons
explained in
.

The correct solution for this is for collectd to bundle the register defines
itself rather than relying on the kernel header package to provide them, as
in the attached patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru collectd-5.7.1/debian/patches/local-msr-index-h.patch 
collectd-5.7.1/debian/patches/local-msr-index-h.patch
--- collectd-5.7.1/debian/patches/local-msr-index-h.patch   1969-12-31 
16:00:00.0 -0800
+++ collectd-5.7.1/debian/patches/local-msr-index-h.patch   2017-08-15 
09:08:03.0 -0700
@@ -0,0 +1,768 @@
+Description: Bundle our own copy of asm/msr-index.h
+ As of Linux 4.12, asm/msr-index.h is not a userspace-exported header, per
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b72e7464e4cf80117938e6adb8c22fdc1ca46d42
+ So to use this header (which only lists defines for register names rather
+ than exposing any kernel interfaces), we need to bundle our own - which also
+ obviates any need for a configure check.
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1710799
+Author: Steve Langasek 
+Last-Update: 2017-08-15
+
+--- collectd-5.7.1.orig/configure.ac
 collectd-5.7.1/configure.ac
+@@ -804,29 +804,6 @@ AC_CACHE_CHECK([whether clock_boottime a
+  [c_cv_have_clock_boottime_monotonic="no"]))
+ 
+ 
+-# For the turbostat plugin
+-have_asm_msrindex_h="no"
+-AC_CHECK_HEADERS(asm/msr-index.h, [have_asm_msrindex_h="yes"])
+-
+-if test "x$have_asm_msrindex_h" = "xyes"
+-then
+-  AC_CACHE_CHECK([whether asm/msr-index.h has MSR_PKG_C10_RESIDENCY],
+- [c_cv_have_usable_asm_msrindex_h],
+- AC_COMPILE_IFELSE([AC_LANG_PROGRAM(
+-[[[
+-#include
+-]]],
+-[[[
+-int y = MSR_PKG_C10_RESIDENCY;
+-return(y);
+-]]]
+-  )],
+- [c_cv_have_usable_asm_msrindex_h="yes"],
+- [c_cv_have_usable_asm_msrindex_h="no"],
+-  )
+- )
+-fi
+-
+ have_cpuid_h="no"
+ AC_CHECK_HEADERS(cpuid.h, [have_cpuid_h="yes"])
+ 
+@@ -6016,7 +5993,7 @@ then
+   then
+   plugin_ipvs="yes"
+   fi
+-  if test "x$c_cv_have_usable_asm_msrindex_h" = "xyes" && test 
"x$have_cpuid_h" = "xyes"
++  if test "x$have_cpuid_h" = "xyes"
+   then
+   plugin_turbostat="yes"
+   fi
+--- /dev/null
 collectd-5.7.1/src/asm/msr-index.h
+@@ -0,0 +1,714 @@
++#ifndef _ASM_X86_MSR_INDEX_H
++#define _ASM_X86_MSR_INDEX_H
++
++/*
++ * CPU model specific register (MSR) numbers.
++ *
++ * Do not add new entries to this file unless the definitions are shared
++ * between multiple compilation units.
++ */
++
++/* x86-64 specific MSRs */
++#define MSR_EFER  0xc080 /* extended feature register */
++#define MSR_STAR  0xc081 /* legacy mode SYSCALL target */
++#define MSR_LSTAR 0xc082 /* long mode SYSCALL target */
++#define MSR_CSTAR 0xc083 /* compat mode SYSCALL target */
++#define MSR_SYSCALL_MASK  0xc084 /* EFLAGS mask for syscall */
++#define MSR_FS_BASE   0xc100 /* 64bit FS base */
++#define MSR_GS_BASE   0xc101 /* 64bit GS base */
++#define MSR_KERNEL_GS_BASE0xc102 /* SwapGS GS shadow */
++#define MSR_TSC_AUX   0xc103 /* Auxiliary TSC */
++
++/* EFER bits: */
++#define _EFER_SCE 0  /* 

Bug#766601: marked as done (openjdk-7-jre-headless: still depending on libjpeg8?)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 16:26:18 +
with message-id 
and subject line Bug#766601: fixed in openjdk-7 7u151-2.6.11-1
has caused the Debian Bug report #766601,
regarding openjdk-7-jre-headless: still depending on libjpeg8?
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.)


-- 
766601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-7-jre-headless
Version: 7u71-2.5.3-1
Severity: minor

Dear OpenJDK Team,

this package depends on both libjpeg62-turbo and libjpeg8. Is the
dependency on libjpeg8 still necessary?
--
Regards,
jvp.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17.1 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openjdk-7-jre-headless depends on:
ii  ca-certificates-java  20140324
ii  java-common   0.52
ii  libc6 2.19-11
ii  libcups2  1.7.5-6
ii  libfontconfig12.11.0-6.1
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.1-17
ii  libglib2.0-0  2.42.0-2
ii  libjpeg62-turbo   1:1.3.1-8
ii  libjpeg8  8d1-2
ii  libkrb5-3 1.12.1+dfsg-10
ii  liblcms2-22.6-3+b2
ii  libnss3   2:3.17.2-1
ii  libpcsclite1  1.8.12-1
ii  libpulse0 5.0-13
ii  libstdc++64.9.1-17
ii  multiarch-support 2.19-11
ii  tzdata-java   2014i-1
ii  zlib1g1:1.2.8.dfsg-2

openjdk-7-jre-headless recommends no packages.

Versions of packages openjdk-7-jre-headless suggests:
ii  fonts-dejavu-extra 2.34-1
pn  fonts-indic
pn  fonts-ipafont-gothic   
pn  fonts-ipafont-mincho   
pn  icedtea-7-jre-jamvm
pn  libnss-mdns
pn  sun-java6-fonts
pn  ttf-wqy-microhei | ttf-wqy-zenhei  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openjdk-7
Source-Version: 7u151-2.6.11-1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-7 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, 23 Aug 2017 16:02:57 +0200
Source: openjdk-7
Binary: openjdk-7-jdk openjdk-7-jre-headless openjdk-7-jre openjdk-7-jre-lib 
openjdk-7-demo openjdk-7-source openjdk-7-doc openjdk-7-dbg icedtea-7-jre-jamvm 
openjdk-7-jre-zero
Architecture: source
Version: 7u151-2.6.11-1
Distribution: experimental
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 icedtea-7-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
 openjdk-7-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-7-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-7-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-7-jdk - OpenJDK Development Kit (JDK)
 openjdk-7-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-7-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-7-jre-lib - OpenJDK Java runtime (architecture independent libraries)
 openjdk-7-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-7-source - OpenJDK Development Kit (JDK) source files
Closes: 766601 827741 863007 865533 865749 869816
Changes:
 openjdk-7 (7u151-2.6.11-1) experimental; urgency=medium
 .
   * IcedTea release 2.6.11 (based on 7u151). Closes: #869816.
   * Security fixes:
 - S8163958, CVE-2017-10102: Improved garbage collection.
 - S8167228: Update to libpng 1.6.28.
 - S8169209, CVE-2017-10053: Improved image post-processing steps.
 - S8169392, CVE-2017-10067: Additional jar validation steps.
 - S8170966, 

Processed: tagging 868300

[Debian Bug Tracking System]

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

> tags 868300 + fixed-upstream
Bug #868300 [yadm] yadm: CVE-2017-11353: race condition allows access to SSH 
and PGP keys
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

[Olaf Spinczyk]

Hi!

You can generate the config file easily with ag++ --gen_config. Sorry
for the inconvenience. The background is that when I wrote the first
ac++ tests, I did not want the makefile to depend on ag++.

We should change that sooner or later, because it is obviously confusing.

Cheers,

Olaf


On 08/23/2017 17:57, Reinhard Tartler wrote:
> 
> 
> On 08/23/2017 04:29 AM, Olaf Spinczyk wrote:
>> Hi Reinhard,
>>
>> when trying to compile the tests, ac++ seems to have no (or an invalid)
>> puma.config file. It doesn't find the system header files, e.g. stdio.h
>> and iostream. For 'make test' to succeed PUMA_CONFIG must point to a
>> valid config file. Are you sure that there is one? Where do you set the
>> environment variable? I haven't seen it in the log.
> 
> 
> I think what confused me is that the build did succeed for release 2.2.
> Here is the old buildlog:
> https://buildd.debian.org/status/fetch.php?pkg=aspectc%2B%2B=amd64=1%3A2.2-1=1490665251=0
> 
> The difference is that in release 2.2, failures in the test suite were
> ignored. Now they are causing the build to fail.
> 
> I'm a bit surprised that invoking the testsuite doesn't handle
> puma.config generation by itself and requires the caller to take care of
> that. But I can certainly look into that.
> 
> I'll try that out and report back.
> 
> Thanks guys!
> -rt
> 

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

[Reinhard Tartler]

On 08/23/2017 04:29 AM, Olaf Spinczyk wrote:
> Hi Reinhard,
> 
> when trying to compile the tests, ac++ seems to have no (or an invalid)
> puma.config file. It doesn't find the system header files, e.g. stdio.h
> and iostream. For 'make test' to succeed PUMA_CONFIG must point to a
> valid config file. Are you sure that there is one? Where do you set the
> environment variable? I haven't seen it in the log.


I think what confused me is that the build did succeed for release 2.2.
Here is the old buildlog:
https://buildd.debian.org/status/fetch.php?pkg=aspectc%2B%2B=amd64=1%3A2.2-1=1490665251=0

The difference is that in release 2.2, failures in the test suite were
ignored. Now they are causing the build to fail.

I'm a bit surprised that invoking the testsuite doesn't handle
puma.config generation by itself and requires the caller to take care of
that. But I can certainly look into that.

I'll try that out and report back.

Thanks guys!
-rt

Bug#870121: marked as done (mate-power-manager: crashes with upower 0.99.5 on any device with a backlit keyboard)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 15:07:51 +
with message-id 
and subject line Bug#870121: fixed in mate-power-manager 1.18.0-2
has caused the Debian Bug report #870121,
regarding mate-power-manager: crashes with upower 0.99.5 on any device with a 
backlit keyboard
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.)


-- 
870121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mate-power-manager
Version: 1.16.2-1
Severity: important

mate-power-manager is not starting when I log in anymore.  It logs the
following to ~/.xsession-errors.

  **
  ERROR:gpm-kbd-backlight.c:342:gpm_kbd_backlight_on_dbus_signal: code should 
not be reached

Running it by hand the first time produced the same result.  Running a
second time caused it to start.

I believe this issue is preventing my screen from locking when I suspend
my laptop.  I've seen that issue on two separare Thinkpad X1 Carbon
laptops, both at home and at work.  On the work laptop, the machine does
not suspend at all.

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

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mate-power-manager depends on:
ii  dbus-user-session [default-dbus-session-bus]1.11.16+really1.10.22-1
ii  dbus-x11 [dbus-session-bus] 1.11.16+really1.10.22-1
ii  libatk1.0-0 2.24.0-1
ii  libc6   2.24-12
ii  libcairo-gobject2   1.14.10-1
ii  libcairo2   1.14.10-1
ii  libcanberra-gtk3-0  0.30-3
ii  libcanberra00.30-3
ii  libdbus-1-3 1.11.16+really1.10.22-1
ii  libdbus-glib-1-20.108-2
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.52.3-1
ii  libgnome-keyring0   3.12.0-1+b2
ii  libgtk-3-0  3.22.17-1
ii  libmate-panel-applet-4-11.16.2-1
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.6-1
ii  libpangocairo-1.0-0 1.40.6-1
ii  libupower-glib3 0.99.5-2
ii  libx11-62:1.6.4-3
ii  libxext62:1.3.3-1+b2
ii  libxrandr2  2:1.5.1-1
ii  libxrender1 1:0.9.10-1
ii  mate-notification-daemon [notification-daemon]  1.16.1-1
ii  mate-power-manager-common   1.16.2-1
ii  notification-daemon 3.20.0-1+b1
ii  policykit-1 0.105-18
ii  systemd 234-2
ii  upower  0.99.5-2

mate-power-manager recommends no packages.

Versions of packages mate-power-manager suggests:
ii  mate-polkit  1.16.0-2

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mate-power-manager
Source-Version: 1.18.0-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mate-power-manager 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the 

Bug#853452: marked as done (injeqt: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 15:06:29 +
with message-id 
and subject line Bug#853452: fixed in injeqt 1.1.0-1.1
has caused the Debian Bug report #853452,
regarding injeqt: 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.)


-- 
853452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:injeqt
Version: 1.1.0-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/injeqt_1.1.0-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/include/c++/7/bits/stl_algo.h:4318:5: note:   template argument 
deduction/substitution failed:
/<>/src/injector.cpp:51:92: note:   deduced conflicting types for 
parameter '_IIter1' ('std::vector' and 
'std::function')
  _pimpl.reset(new ::injeqt::internal::injector_impl{transform(super_injectors, 
extract_impl), std::move(modules)});

^
In file included from /usr/include/c++/7/algorithm:62:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:94,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtGlobal:1,
 from /<>/include/injeqt/injeqt.h:23,
 from /<>/include/injeqt/injector.h:23,
 from /<>/src/injector.cpp:21:
/usr/include/c++/7/bits/stl_algo.h:4281:5: note: candidate: template _OIter std::transform(_IIter, 
_IIter, _OIter, _UnaryOperation)
 transform(_InputIterator __first, _InputIterator __last,
 ^
/usr/include/c++/7/bits/stl_algo.h:4281:5: note:   template argument 
deduction/substitution failed:
/<>/src/injector.cpp:51:92: note:   deduced conflicting types for 
parameter '_IIter' ('std::vector' and 
'std::function')
  _pimpl.reset(new ::injeqt::internal::injector_impl{transform(super_injectors, 
extract_impl), std::move(modules)});

^
/<>/src/injector.cpp:51:113: error: no matching function for call 
to 'injeqt::internal::injector_impl::injector_impl()'
  _pimpl.reset(new ::injeqt::internal::injector_impl{transform(super_injectors, 
extract_impl), std::move(modules)});

 ^
In file included from /<>/src/injector.cpp:28:0:
/<>/src/internal/injector-impl.h:102:11: note: candidate: 
injeqt::internal::injector_impl::injector_impl(std::vector,
 std::vector)
  explicit injector_impl(std::vector super_injectors, 
std::vector> modules);
   ^
/<>/src/internal/injector-impl.h:102:11: note:   conversion of 
argument 1 would be ill-formed:
/<>/src/internal/injector-impl.h:82:11: note: candidate: 
injeqt::internal::injector_impl::injector_impl(std::vector)
  explicit injector_impl(std::vector> 
modules);
   ^
/<>/src/internal/injector-impl.h:82:11: note:   candidate expects 
1 argument, 2 provided
/<>/src/internal/injector-impl.h:63:2: note: candidate: 
injeqt::internal::injector_impl::injector_impl()
  

Bug#871591: marked as done ([src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect gcc-7)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 15:00:31 +
with message-id 
and subject line Bug#871591: fixed in llvm-toolchain-snapshot 1:6.0~svn310776-1
has caused the Debian Bug report #871591,
regarding [src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect 
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.)


-- 
871591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-snapshot
Version: 1:5.0~svn305653-1
Severity: serious
Tags: patch sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Dear LLVM packagers,

I've noticed that llvm-toolchain-snapshot goes FTBFS because
`debian/rules' in the packge fails to detect gcc-7 (it tries to use
gcc-7.1). The Jenkins builds seem to be failing due to the same bug.
http://llvm-jenkins.debian.net/view/Debian%20unstable/job/llvm-toolchain-binaries/architecture=amd64,distribution=unstable/898/console

Here I send a patch to fix this by ensuring the existence of
/usr/bin/g++-$(GCC_VERSION) on the build system.

Could you take a look at it please?
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/changelog llvm-toolchain-snapshot-5.0~svn305653/debian/changelog
--- llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-08-09 23:32:40.0 +0900
@@ -1,3 +1,10 @@
+llvm-toolchain-snapshot (1:5.0~svn305653-1.1) UNRELEASED; urgency=medium
+
+  * Ensure /usr/bin/g++-$(GCC_VERSION) exists
+
+ -- Katsuhiko Nishimra   Wed, 09 Aug 2017 23:32:40 +0900
+
 llvm-toolchain-snapshot (1:5.0~svn305653-1) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/rules llvm-toolchain-snapshot-5.0~svn305653/debian/rules
--- llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-08-09 23:32:40.0 +0900
@@ -2,9 +2,11 @@
 
 TARGET_BUILD	:= build-llvm
 DEB_INST		:= $(CURDIR)/debian/tmp/
-# The 5|6| in the regexp is a crappy workaround. g++ 5.2 in Debian is not providing a g++-5.2 binary (only g++-5)
-# accomodate that by hardcoding the 5 detection
-GCC_VERSION := $(shell dpkg-query -W -f '$${Version}' g++ | sed -rne 's,^([0-9]+:)?(5|6|[0-9]+\.[0-9]+|[0-9]+).*$$,\2,p')
+
+GXX_VERSIONED_PACKAGE:= $(shell dpkg-query -W -f '$${Depends}' g++ | grep -o 'g++-[0-9][0-9.]*' | tail -n1 )
+GXX_VERSIONED_EXECUTABLE := $(shell dpkg -L $(GXX_VERSIONED_PACKAGE) | grep '/usr/bin/g++-[0-9][0-9.]*' | xargs ls -d | tail -n1 )
+GCC_VERSION  := $(subst /usr/bin/g++-,,$(GXX_VERSIONED_EXECUTABLE))
+
 LLVM_VERSION	:= 5.0
 LLVM_VERSION_FULL := $(LLVM_VERSION).0
 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-snapshot
Source-Version: 1:6.0~svn310776-1

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-snapshot, 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.
Sylvestre Ledru  (supplier of updated 
llvm-toolchain-snapshot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Jul 2017 23:16:06 +0200
Source: llvm-toolchain-snapshot
Binary: clang-6.0 clang-format-6.0 clang-tidy-6.0 clang-6.0-doc libclang1-6.0 
libclang1-6.0-dbg libclang-6.0-dev libclang-common-6.0-dev libfuzzer-6.0-dev 
python-clang-6.0 clang-6.0-examples libllvm6.0 libllvm6.0-dbg llvm-6.0 
llvm-6.0-runtime llvm-6.0-dev llvm-6.0-tools libllvm-6.0-ocaml-dev llvm-6.0-doc 
llvm-6.0-examples lld-6.0 liblld-6.0 liblld-6.0-dbg liblld-6.0-dev lldb-6.0 
liblldb-6.0 liblldb-6.0-dbg python-lldb-6.0 liblldb-6.0-dev
Architecture: source amd64 all
Version: 1:6.0~svn310776-1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-6.0  - 

Bug#871300: marked as done (libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 15:00:16 +
with message-id 
and subject line Bug#871300: fixed in imagemagick 8:6.9.9.6+dfsg-1
has caused the Debian Bug report #871300,
regarding libmagick++-6.q16-7: 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.)


-- 
871300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmagick++-6.q16-7
Version: 8:6.9.7.4+dfsg-16
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: imagemagick
Source-Version: 8:6.9.9.6+dfsg-1

We believe that the bug you reported is fixed in the latest version of
imagemagick, 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.
Bastien Roucariès  (supplier of updated imagemagick 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, 11 Aug 2017 17:09:53 +0200
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-5 
libmagickcore-6.q16-5-extra libmagickcore-6.q16-dev libmagickwand-6.q16-5 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-5 
libmagickcore-6.q16hdri-5-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-5 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-8 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source all amd64
Version: 8:6.9.9.6+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Bug#871814: marked as done (csound-manual FTBFS: python: Command not found)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 15:00:11 +
with message-id 
and subject line Bug#871814: fixed in csound-manual 1:6.09.0~dfsg-2
has caused the Debian Bug report #871814,
regarding csound-manual FTBFS: python: Command 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.)


-- 
871814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: csound-manual
Version: 1:6.09.0~dfsg-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=csound-manual=all=1%3A6.09.0~dfsg-1=1502411845=0

...
dh_auto_build
make -j4
make[2]: Entering directory '/<>'
[ -d "/usr/share/xml/docbook/stylesheet/nwalsh/" ] || (  \
 echo "The XSL_BASE_PATH variable must be set to the XSL stylesheets 
installation directory" ; \
 false )
sed -e 's|@xsl_base_path@|/usr/share/xml/docbook/stylesheet/nwalsh/|' 
xsl/customXHTMLchunk.xsl.in > xsl/customXHTMLchunk.xsl
mkdir -p examples-xml
python csd2docbook.py
make[2]: python: Command not found
Makefile:702: recipe for target 'examples-xml/stamp' failed
make[2]: *** [examples-xml/stamp] Error 12
--- End Message ---
--- Begin Message ---
Source: csound-manual
Source-Version: 1:6.09.0~dfsg-2

We believe that the bug you reported is fixed in the latest version of
csound-manual, 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.
Felipe Sateler  (supplier of updated csound-manual package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Aug 2017 19:58:07 -0400
Source: csound-manual
Binary: csound-doc
Architecture: source all
Version: 1:6.09.0~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 csound-doc - documentation for csound
Closes: 871814
Changes:
 csound-manual (1:6.09.0~dfsg-2) unstable; urgency=medium
 .
   * Add missing build-dependencies (Closes: #871814)
Checksums-Sha1:
 fd83bbdf5dbb2897dc47c1439021fb67428c6d83 2145 csound-manual_6.09.0~dfsg-2.dsc
 cadefe10e984399a1fa9ed7ca7a43a015c24ef00 6964 
csound-manual_6.09.0~dfsg-2.debian.tar.xz
 fc7f68e56f751756a7c33ba588d7e03fe393f26c 11420350 
csound-doc_6.09.0~dfsg-2_all.deb
 d03ac75049adb541124e79d0791f45f2ab597de8 6388 
csound-manual_6.09.0~dfsg-2_amd64.buildinfo
Checksums-Sha256:
 c8e403bb2b9d0b8991d7e65955c0f0424ea884387c39dba49f4296a98596b3e1 2145 
csound-manual_6.09.0~dfsg-2.dsc
 6a189f6d22a4fbd43f3825cb91a89ececa5c3e50050b593c55fde3b3d9e39bb4 6964 
csound-manual_6.09.0~dfsg-2.debian.tar.xz
 7dc1dc4696a061f1d4f64d84671c5614c954a73dbd9e33a7077e639ab18a8a90 11420350 
csound-doc_6.09.0~dfsg-2_all.deb
 647ef1170e6c02ce8838170a77196af77f3145996480bb6785ce2624a5eb0b9f 6388 
csound-manual_6.09.0~dfsg-2_amd64.buildinfo
Files:
 8a98630519eb71257a463bf8edfd6f69 2145 doc optional 
csound-manual_6.09.0~dfsg-2.dsc
 14ef61ece21b4bf9d1a948bbf6dec42b 6964 doc optional 
csound-manual_6.09.0~dfsg-2.debian.tar.xz
 7a6da9fccf416686dcc87aa7618be428 11420350 doc optional 
csound-doc_6.09.0~dfsg-2_all.deb
 7515612dd353e593b05fd88eea5079bc 6388 doc optional 
csound-manual_6.09.0~dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAlmQWtIUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s+r/BAApT8cS1ZQFoHif5zV9WpKdBYClNM1
mi9I5xBUqcIRrew5Pwv+ruPtJIv2UhcDWInZJ6qAG5Pc0vbroV2cqxT8czhwt/tG
vM+99Q+k2Ogds3I8A56gq77ObiF2cO3Xjy2wAJajaF1sTdbjyVIiOKvPRli+dZDW
JJeN9GuF28NqsGDZFrPVB6EUQWEFdjMwc9uK2pgLiZoHGCdD8N61u6ct44VaU+mg
3zNdU+L9WZUxMjtqkITiTYS2Q6gTuZlV0ZcySkTeKgZNgqP/QD7iPz8RMvaoBWaO
hqcvGMbq786YUX0Tu1XXghYObmqNTDbHg7uosPHQpOn4zeJRUfNeNXliAV3C962E
s+zbthgC/j1F7HjBZSuIfiEoubmG4/p96vhLhJTF3QGqV+JJng1UojT6Jvonxm1h
HaDQQzSzGhddG2M1cEhahtAUbza7hQJcYNpUSm+vV6pvsH6a6OyLIYXP+e/ygBG8
nxSmnJ23coVnWYV6hKV/GdigW2yzYJ1BPwHUurjwgWFqAArOgkmccmzrjDU9Pa+Y
rjogg0D/wv00TkPdX+PgCIUoj7qRPb/JlmbnAjHW4JEzBAn0kqsd+FTss2dfbTIK
TuIpWDCUSTMonLZibTHcEhuj30Kz8hnnwDU8tLliSGBxnCC5ev/GGpLyaHQYutSN

Bug#843926: marked as done (jemalloc uses a hard coded page size detected during build)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 15:00:17 +
with message-id 
and subject line Bug#843926: fixed in jemalloc 5.0.1-1
has caused the Debian Bug report #843926,
regarding jemalloc uses a hard coded page size detected during build
to be marked as done.

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

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


-- 
843926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.0
Version: 10.0.26-0+deb8u1
Severity: serious
Justification: FTBFS

Hi

The recent mariadb-10.0 upload of 10.0.26-0+deb8u1 for jessie-security
FTBFS on powerpc. I have attached the build log from buildd and the
hanging build was reproducible on porterbox partch.debian.org for
powerpc.

Regards,
Salvatore


mariadb-10.0_10.0.26-0+deb8u1_powerpc-20160726-0537.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: jemalloc
Source-Version: 5.0.1-1

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

Debian distribution maintenance software
pp.
Faidon Liambotis  (supplier of updated jemalloc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Aug 2017 00:57:08 +0300
Source: jemalloc
Binary: libjemalloc-dev libjemalloc2
Architecture: source amd64
Version: 5.0.1-1
Distribution: experimental
Urgency: medium
Maintainer: Stig Sandbeck Mathisen 
Changed-By: Faidon Liambotis 
Description:
 libjemalloc-dev - development files and documentation for jemalloc
 libjemalloc2 - general-purpose scalable concurrent malloc(3) implementation
Closes: 809239 843926
Changes:
 jemalloc (5.0.1-1) experimental; urgency=medium
 .
   * New upstream release. (Closes: #809239)
 - Rename to libjemalloc2 to account for upstream's ABI/SONAME bump.
 - Update debian/copyright.
 - Drop patch disable-HAVE_SSE2, was a backport
 - Update GNU/kFreeBSD support patch.
   * Build with a 64k page size on arm64, mips, mips64el, mipsel, powerpc,
 ppc64 and ppc64el. (Closes: #843926)
   * Move the m68k, nios2 and SH3 architecture support from debian/rules to
 debian/patches and forward it upstream.
   * Drop the attempts at Hurd support. They haven't worked, more issues were
 introduced with 5.0.1 and, in general, it's debatable whether it's worth
 building a memory allocator optimized for multiprocessing on an
 architecture that doesn't support SMP is of any value.
   * Cleanup debian/rules from old compiler flags and other artifacts.
   * Bump Standards-Version to 4.0.1.
   * Ship pkg-config file in libjemalloc-dev.
Checksums-Sha1:
 c300702c70a3800e058db4153c817879fa674bbe 2053 jemalloc_5.0.1-1.dsc
 5c2c74b8bf773df6e813f0709f55d40a8256104d 499300 jemalloc_5.0.1.orig.tar.bz2
 ff1c4fddcc7cba3ad45b0751df10f215c239e563 13680 jemalloc_5.0.1-1.debian.tar.xz
 ffe7cfb34b47b3e585307f948fd8fd606a6b8a64 6011 jemalloc_5.0.1-1_amd64.buildinfo
 a432bb8647bc3251939f655cf795805400b243af 324046 
libjemalloc-dev_5.0.1-1_amd64.deb
 fb36d222bd46a4b5d3599519209390e6843ff5ea 1018480 
libjemalloc2-dbgsym_5.0.1-1_amd64.deb
 440e694ce44c2c1f1420e4d7ab9eb7eca4996e02 198358 libjemalloc2_5.0.1-1_amd64.deb
Checksums-Sha256:
 2244d56d744fcf5f36737ca84c0f699933a14894e354be44bb67721c8e23fa2d 2053 
jemalloc_5.0.1-1.dsc
 4814781d395b0ef093b21a08e8e6e0bd3dab8762f9935bbfb71679b0dea7c3e9 499300 
jemalloc_5.0.1.orig.tar.bz2
 cfe3644622e669a3179c5bc1000524d20046ba5c18b91343c7574c4dabf8ec4f 13680 
jemalloc_5.0.1-1.debian.tar.xz
 96836296b1d00751ec550ca863bf5c8268914b4577978288a7a4a03a35d9f123 6011 
jemalloc_5.0.1-1_amd64.buildinfo
 978921f1e3eba42a8851fdb47910d7d46e331f7e1cddb768057fd492c48eb576 324046 
libjemalloc-dev_5.0.1-1_amd64.deb
 bedf9dbcfe3bc2c1c8d53f79478e3f5cb98bb350d14efe1830bbc9f0d708549c 1018480 
libjemalloc2-dbgsym_5.0.1-1_amd64.deb
 32fad1a4f806ca51eb751aa7736f44ecec5750f84f23ee32c400e981a6110309 198358 
libjemalloc2_5.0.1-1_amd64.deb
Files:
 31c911e5ad9074280160ddf97a1a741c 2053 libs optional 

Bug#872738: contextfree FTBFS on ppc64el: error: 'CTL_HW' was not declared in this scope

[John Horigan]

I have applied Frederic'c patch to the upstream source as well as fixes for
the FTBFS issues with other platforms (ppc, alpha, hurd-i386, x32). I also
eliminated the use of the deprecated readdir_r() function. Context Free
3.0.11.5 package is being reviewed by the package sponsor.

-- john

On Sun, Aug 20, 2017 at 10:09 AM Adrian Bunk  wrote:

> Source: contextfree
> Version: 3.0.11.4+dfsg1-1
> Severity: serious
>
>
> https://buildd.debian.org/status/fetch.php?pkg=contextfree=ppc64el=3.0.11.4%2Bdfsg1-1=1503230603=0
>
> ...
> g++ -g -O2 -fdebug-prefix-map=/<>/contextfree-3.0.11.4+dfsg1=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Isrc-common -Isrc-unix -Iobjs -Isrc-common/agg-extras
> -Isrc-ffmpeg/include -I/usr/local/include -O2 -Wall -Wextra
> -Wno-parentheses -std=c++14  -c -o objs/posixSystem.o
> src-unix/posixSystem.cpp
> src-unix/posixSystem.cpp: In member function 'virtual
> std::vector
> PosixSystem::findTempFiles()':
> src-unix/posixSystem.cpp:220:53: warning: 'int readdir_r(DIR*, dirent*,
> dirent**)' is deprecated [-Wdeprecated-declarations]
>  while (readdir_r(dirp.get(), , ) == 0 && der) {
>  ^
> In file included from src-unix/posixSystem.cpp:36:0:
> /usr/include/dirent.h:183:12: note: declared here
>  extern int readdir_r (DIR *__restrict __dirp,
> ^
> src-unix/posixSystem.cpp: In member function 'virtual size_t
> PosixSystem::getPhysicalMemory()':
> src-unix/posixSystem.cpp:246:14: error: 'CTL_HW' was not declared in this
> scope
>  mib[0] = CTL_HW;
>   ^~
> src-unix/posixSystem.cpp:246:14: note: suggested alternative: 'CTL_PM'
>  mib[0] = CTL_HW;
>   ^~
>   CTL_PM
> Makefile:206: recipe for target 'objs/posixSystem.o' failed
> make[1]: *** [objs/posixSystem.o] Error 1
>

Bug#868609: le FTBFS with latest ncurses

[Raphael Geissert]

On 23 August 2017 at 14:56, Alexander V. Lukyanov  wrote:
> On Fri, Aug 18, 2017 at 12:39:00PM +0200, Raphael Geissert wrote:
>> Do you plan to make a new release with the fixes? or should I grab the
>> patches from github?
>
> 1.16.5 has been released.

Awesome, thanks. I'll take care of the upload.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

Processed: Bug#870121 marked as pending

[Debian Bug Tracking System]

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

> tag 870121 pending
Bug #870121 [mate-power-manager] mate-power-manager: crashes with upower 0.99.5 
on any device with a backlit keyboard
Added tag(s) pending.
> 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#870121: marked as pending

[Mike Gabriel]

tag 870121 pending
thanks

Hello,

Bug #870121 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-mate/mate-power-manager.git/commit/?id=0253bbe

---
commit 0253bbe053bf5871c74bc62666746707cbf65a3b
Author: Mike Gabriel 
Date:   Wed Aug 23 16:20:38 2017 +0200

upload to unstable (debian/1.18.0-2)

diff --git a/debian/changelog b/debian/changelog
index d44af8c..b307235 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,11 @@
-mate-power-manager (1.18.0-2) UNRELEASED; urgency=medium
+mate-power-manager (1.18.0-2) unstable; urgency=medium
 
-  * debian/patches: Add
-0001_do_not_abort_on_unknown_DBus_signal_name.patch. (LP: #1707300)
+  [ Martin Wimpress ]
+  * debian/patches:
++ Add 0001_do_not_abort_on_unknown_DBus_signal_name.patch.
+  (LP: #1707300). (Closes: #870121).
 
- -- Martin Wimpress   Thu, 17 Aug 2017 00:24:15 
+0100
+ -- Mike Gabriel   Wed, 23 Aug 2017 16:13:18 +0200
 
 mate-power-manager (1.18.0-1) unstable; urgency=medium
 

Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

[James Cowgill]

Hi,

The attached patch seems to work (ie replace atomic-library with it).
Using target_link_libraries should put any linker arguments at the end
instead of the beginning.

Thanks,
James
--- a/tools/cmake/MakeLib.cmake
+++ b/tools/cmake/MakeLib.cmake
@@ -114,6 +114,7 @@ if(enable_smpi AND APPLE)
   set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,-U -Wl,_smpi_simulated_main")
 endif()
 
+set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,--as-needed -latomic -Wl,--no-as-needed")
 target_link_libraries(simgrid  ${SIMGRID_DEP})
 
 # Dependencies from maintainer mode


signature.asc
Description: OpenPGP digital signature

Bug#853452: NMU diff

[Adam Borowski]

Here's the debdiff for Mateusz Łukasik's NMU I'm about to upload.

Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀-- Genghis Ht'rok'din
⠈⠳⣄ 
diff -Nru injeqt-1.1.0/debian/changelog injeqt-1.1.0/debian/changelog
--- injeqt-1.1.0/debian/changelog   2016-11-25 11:49:09.0 +0100
+++ injeqt-1.1.0/debian/changelog   2017-08-18 14:16:12.0 +0200
@@ -1,3 +1,10 @@
+injeqt (1.1.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix ftbfs with GCC-7. (Closes: #853452)
+
+ -- Mateusz Łukasik   Fri, 18 Aug 2017 14:16:12 +0200
+
 injeqt (1.1.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru injeqt-1.1.0/debian/patches/fix-ftbfs-with-gcc7.patch 
injeqt-1.1.0/debian/patches/fix-ftbfs-with-gcc7.patch
--- injeqt-1.1.0/debian/patches/fix-ftbfs-with-gcc7.patch   1970-01-01 
01:00:00.0 +0100
+++ injeqt-1.1.0/debian/patches/fix-ftbfs-with-gcc7.patch   2017-08-18 
14:15:17.0 +0200
@@ -0,0 +1,22 @@
+From de025e0c472bdb2fcabbc9dc2fd443b91ab28e28 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Bart=C5=82omiej=20Burdukiewicz?=
+ 
+Date: Wed, 24 May 2017 18:52:20 +0200
+Subject: [PATCH] fix compilation for GCC 7.1.0
+
+---
+ src/internal/containers.h | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/internal/containers.h b/src/internal/containers.h
+index 8da4298..78dd212 100644
+--- a/src/internal/containers.h
 b/src/internal/containers.h
+@@ -23,6 +23,7 @@
+ #include "internal.h"
+ 
+ #include 
++#include 
+ #include 
+ 
+ /**
diff -Nru injeqt-1.1.0/debian/patches/series injeqt-1.1.0/debian/patches/series
--- injeqt-1.1.0/debian/patches/series  1970-01-01 01:00:00.0 +0100
+++ injeqt-1.1.0/debian/patches/series  2017-08-18 14:15:26.0 +0200
@@ -0,0 +1 @@
+fix-ftbfs-with-gcc7.patch

Bug#864936: marked as done (yagv: segmentation fault on startup)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 13:05:06 +
with message-id 
and subject line Bug#864936: fixed in pyglet 1.3.0~rc1-1
has caused the Debian Bug report #864936,
regarding yagv: segmentation fault on startup
to be marked as done.

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

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


-- 
864936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: yagv: segmentation fault on startup
Package: yagv
Version: 0.4~20130422.r5bd15ed+dfsg-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,

starting yagv with any G-code file (random example attached) causes it
to SEGV, right after displaying rendering window.
console output from a run:


Yet Another GCode Viewer v0.4
loading file '3d_cube.gcode' ...

Parsing '3d_cube.gcode'...

[WARN] Line 10: Unknown code 'M107' (Text:'M107')
[WARN] Line 11: G28 unimplemented (Text:'G28 ; home all axes')
[WARN] Line 13: Unknown code 'M190' (Text:'M190 S70 ; bed temp')
[WARN] Line 14: Unknown code 'M104' (Text:'M104 S210 ; noozle temp')
[WARN] Line 17: Unknown code 'M82' (Text:'M82 ; use absolute distances
for extrusion')
[WARN] Line 164: Unknown code 'M106' (Text:'M106 S252.45')
[WARN] Line 165: Unknown code 'M104' (Text:'M104 S200 ; set temperature')
[WARN] Line 334: Unknown code 'M106' (Text:'M106 S255')
[WARN] Line 356: Unknown code 'M106' (Text:'M106 S255')
[WARN] Line 470: Unknown code 'M106' (Text:'M106 S255')
[WARN] Line 4281: Unknown code 'M106' (Text:'M106 S255')
[WARN] Line 4395: Unknown code 'M106' (Text:'M106 S255')
[WARN] Line 4396: Unknown code 'M106' (Text:'M106 S252.45')
[WARN] Line 4567: Unknown code 'M106' (Text:'M106 S229.5')
[WARN] Line 4740: Unknown code 'M107' (Text:'M107')
[WARN] Line 4741: Unknown code 'M104' (Text:'M104 S0 ; turn off
temperature')
[WARN] Line 4742: Unknown code 'M140' (Text:'M140 S0 ; turn off heatbed')
[WARN] Line 4743: G28 unimplemented (Text:'G28 X0  ; home X axis')
[WARN] Line 4744: Unknown code 'M84' (Text:'M84 ; disable motors')

Done! >

rendering vertices...
end renderColors in 2.908 ms
rendering indexed colors...
end renderIndexedColors in 1.075 ms
rendering true colors...
end renderColors in 5.870 ms
generating graphics...
end generateGraphics in 57.268 ms
Done
loaded file in 144.799 ms
Segmentation fault



-- System Information:
Debian Release: 9.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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)

Versions of packages yagv depends on:
ii  python 2.7.13-2
ii  python-pyglet  1.1.4.dfsg-3

yagv recommends no packages.

yagv suggests no packages.

-- no debconf information

-- 
pozdrawiam serdecznie / best regards,
bartek 'basz' szurgot
/* https://www.baszerr.eu */
/* https://www.baszerr.eu/lib/exe/fetch.php/about_me/basz_pub_key.txt */



3d_cube.tar.bz2
Description: Binary data


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyglet
Source-Version: 1.3.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
pyglet, 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.
Yaroslav Halchenko  (supplier of updated pyglet 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, 23 Aug 2017 01:30:59 -0400
Source: pyglet
Binary: python-pyglet
Architecture: source all
Version: 1.3.0~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Yaroslav Halchenko 
Description:
 python-pyglet - cross-platform windowing and multimedia library
Closes: 786897 864936 871487
Changes:
 pyglet (1.3.0~rc1-1) unstable; urgency=medium
 .
   [ Ondřej Nový 

Bug#871145: marked as done (hfst: FTBFS: ./../include/fst/replace.h:1061:46: error: expected ';' before '::' token)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2017 13:00:10 +
with message-id 
and subject line Bug#871145: fixed in hfst 3.12.2~r3289-1
has caused the Debian Bug report #871145,
regarding hfst: FTBFS: ./../include/fst/replace.h:1061:46: error: expected ';' 
before '::' token
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.)


-- 
871145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hfst
Version: 3.10.0~r2798-3
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):
> /bin/bash ../../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
> -I. -I../../../.. -I../../../../libhfst/src  -I ./../include  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -c -o 
> util.lo util.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c flags.cc  -fPIC -DPIC -o .libs/flags.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c fst.cc  -fPIC -DPIC -o .libs/fst.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c symbol-table.cc  -fPIC -DPIC -o 
> .libs/symbol-table.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c util.cc  -fPIC -DPIC -o .libs/util.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c symbol-table-ops.cc  -fPIC -DPIC -o 
> .libs/symbol-table-ops.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c properties.cc  -fPIC -DPIC -o 
> .libs/properties.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. 
> -I../../../../libhfst/src -I ./../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++0x -c compat.cc  -fPIC -DPIC -o .libs/compat.o
> In file included from ./../include/fst/accumulator.h:44:0,
>  from ./../include/fst/label-reachable.h:39,
>  from ./../include/fst/lookahead-matcher.h:28,
>  from ./../include/fst/matcher-fst.h:26,
>  from fst.cc:27:
> ./../include/fst/replace.h: In constructor 
> 'fst::ArcIterator >::ArcIterator(const 
> fst::ReplaceFst&, fst::ArcIterator >::StateId)':
> ./../include/fst/replace.h:1061:46: error: expected ';' before '::' token
>(fst_.GetImpl())->template CacheImpl::InitArcIterator(state_,
>   ^~
> Makefile:422: recipe for target 'fst.lo' failed
> make[7]: *** [fst.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/hfst_3.10.0~r2798-3_unstable.log

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

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

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

A 

Bug#871062: collectd: FTBFS: client.c:621:23: error: '%s' directive output may be truncated writing up to 1023 bytes into a region of size 1010 [-Werror=format-truncation=]

[Marc Fournier]

Hello Michael,

On Mon, Aug 21, 2017 at 06:11:02PM +0200, Michael Stapelberg wrote:
> Hi,
> 
> Steve Langasek  writes:
> > The attached one-liner patch corrects this build failure by simply ignoring
> > the (IMHO uninteresting) new gcc-7 warning.  I think this is a reasonable
> > way to handle this until it gets fixed upstream.
> 
> Marc, Sebastian, does either of you have time to upload this patch, or
> would you prefer an NMU?
> 
> This is somewhat time-critical, because this RC bug will cause
> freeradius to be removed from testing.

Thanks for the heads-up ! Sorry for having let these FTBFS issues pile up :-(

I'm getting back on track and will take care of uploading 5.7.2 + the misc
fixes needed so the package builds again.

For this specific issue, I feel this fix would be better suited:
https://github.com/collectd/collectd/issues/2200

Cheers,
Marc

Bug#868609: le FTBFS with latest ncurses

[Alexander V. Lukyanov]

On Fri, Aug 18, 2017 at 12:39:00PM +0200, Raphael Geissert wrote:
> Do you plan to make a new release with the fixes? or should I grab the
> patches from github?

1.16.5 has been released.

--
   Alexander.

Bug#864936: marked as pending

[Yaroslav Halchenko]

tag 864936 pending
thanks

Hello,

Bug #864936 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/python-modules/packages/pyglet.git/commit/?id=0039ad9

---
commit 0039ad94d0f57e7e77a96291caf66d9f19023f76
Author: Yaroslav Halchenko 
Date:   Tue Aug 22 23:14:15 2017 -0400

forgotten fontconfig lib and closing statements

diff --git a/debian/changelog b/debian/changelog
index 0b68155..c331f42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,8 @@ pyglet (1.3.0~rc1-1) experimental; urgency=medium
   * Fixed VCS URL (https)
 
   [ Yaroslav Halchenko ]
+  * Fresh upstream rc (Closes: #786897, #871487)
+- resolves some of the segfaulting issues (Closes: #864936)
   * d/watch - point to pypi
   * d/patch - only 1 left not upstreamed (minor - string exception, PR sent)
   * d/rules + changelog -- no .dfsg suffix any longer.  It seems that all the