Processed: severity of 873802 is serious

[Debian Bug Tracking System]

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

> # fixed in stable
> severity 873802 serious
Bug #873802 [src:ruby2.3] Multiple vulnerabilities in rubygems (CVE-2017-0899 
to CVE-2017-0902)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#874417: sugar-icon-theme, sugar-themes: fails to upgrade from 'stretch' - trying to overwrite ...

[Andreas Beckmann]

Package: sugar-icon-theme,sugar-themes
Version: 0.110.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package sugar-icon-theme.
  Preparing to unpack .../sugar-icon-theme_0.110.0-2_all.deb ...
  Unpacking sugar-icon-theme (0.110.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/sugar-icon-theme_0.110.0-2_all.deb (--unpack):
   trying to overwrite 
'/usr/share/icons/sugar/cursors/08e8e1c95fe2fc01f976f1e063a24ccd', which is 
also in package sugar-artwork-0.88 0.88.1-4
  Selecting previously unselected package sugar-themes.
  Preparing to unpack .../sugar-themes_0.110.0-2_all.deb ...
  Unpacking sugar-themes (0.110.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/sugar-themes_0.110.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/themes/sugar-100/gtk-2.0/gtkrc', which is 
also in package sugar-artwork-0.88 0.88.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/sugar-icon-theme_0.110.0-2_all.deb
   /var/cache/apt/archives/sugar-themes_0.110.0-2_all.deb


cheers,

Andreas


sugar-artwork-0.88=0.88.1-4_sugar-themes=0.110.0-2.log.gz
Description: application/gzip

Bug#874418: libdislocker0.7: fails to upgrade from 'stretch' - trying to overwrite /usr/lib/libdislocker.so

[Andreas Beckmann]

Package: libdislocker0.7
Version: 0.7.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libdislocker0.7.
  Preparing to unpack .../libdislocker0.7_0.7.1-2_amd64.deb ...
  Unpacking libdislocker0.7 (0.7.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdislocker0.7_0.7.1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/libdislocker.so', which is also in package 
libdislocker0.6 0.6.1-7
  Errors were encountered while processing:
   /var/cache/apt/archives/libdislocker0.7_0.7.1-2_amd64.deb

Why is this .so link in the shared library package and not in
the -dev package?

And please get rid of the insane idea of a libdislocker0.6
transitional package in sid.


cheers,

Andreas


libdislocker0.6=0.6.1-7_libdislocker0.7=0.7.1-2.log.gz
Description: application/gzip

Bug#867648: Pending fixes for bugs in the jruby-maven-plugins package

[pkg-java-maintainers]

tag 867648 + pending
thanks

Some bugs in the jruby-maven-plugins package are closed in revision
b5b18945b8fa0db45e2adfdd0de73de61b22e261 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jruby-maven-plugins.git/commit/?id=b5b1894

Commit message:

Fixed a flawed assertion that fail to compile with the source level 1.7 
(Closes: #867648)

Bug#853516: marked as done (libwfut: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 03:07:24 +
with message-id 
and subject line Bug#853516: fixed in libwfut 0.2.3-5
has caused the Debian Bug report #853516,
regarding libwfut: 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.)


-- 
853516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libwfut
Version: 0.2.3-4
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/libwfut_0.2.3-4_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

[...]
- (optional=GCC6_removed)_ZN9TiXmlNode9ToElementEv@Base 0.2.3
- 
(optional=templinst)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4WFUT10FileObjectEED1Ev@Base
 0.2.3
- 
(optional=templinst)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4WFUT10FileObjectEED2Ev@Base
 0.2.3
- (optional=templinst)_ZNSt5dequeIPvSaIS0_EE16_M_push_back_auxERKS0_@Base 0.2.3
- 
(optional=GCC6_removed)_ZNSt5dequeIPvSaIS0_EE16_M_push_back_auxIIRKS0_EEEvDpOT_@Base
 0.2.3
+ 
_ZN4sigc8internal9slot_callINS_18bound_mem_functor2IvN4WFUT10WFUTClientERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESC_EEvJSC_SC_EE7call_itEPNS0_8slot_repESC_SC_@Base
 0.2.3-4
+ 
_ZN4sigc8internal9slot_callINS_18bound_mem_functor3IvN4WFUT10WFUTClientERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESC_SC_EEvJSC_SC_SC_EE7call_itEPNS0_8slot_repESC_SC_SC_@Base
 0.2.3-4
+#MISSING: 0.2.3-4# (optional=GCC6_removed)_ZN9TiXmlNode9ToElementEv@Base 0.2.3
+#MISSING: 0.2.3-4# 
(optional=templinst)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4WFUT10FileObjectEED1Ev@Base
 0.2.3
+#MISSING: 0.2.3-4# 
(optional=templinst)_ZNSt4pairIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN4WFUT10FileObjectEED2Ev@Base
 0.2.3
+#MISSING: 0.2.3-4# 
(optional=templinst)_ZNSt5dequeIPvSaIS0_EE16_M_push_back_auxERKS0_@Base 0.2.3
+#MISSING: 0.2.3-4# 
(optional=GCC6_removed)_ZNSt5dequeIPvSaIS0_EE16_M_push_back_auxIIRKS0_EEEvDpOT_@Base
 0.2.3
  _ZNSt5dequeIPvSaIS0_EE16_M_push_back_auxIJRKS0_EEEvDpOT_@Base 0.2.3
  
(optional=templinst)_ZNSt5dequeIPvSaIS0_EE8_M_eraseESt15_Deque_iteratorIS0_RS0_PS0_E@Base
 0.2.3
- 
(optional=templinst)_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.2.3
- 
(optional=GCC6_removed)_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE19_M_emplace_back_auxIIRKS1_EEEvDpOT_@Base
 0.2.3
- 
_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_@Base
 0.2.3
+#MISSING: 0.2.3-4# 
(optional=templinst)_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.2.3
+ 
_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.2.3-4
+#MISSING: 0.2.3-4# 
(optional=GCC6_removed)_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE19_M_emplace_back_auxIIRKS1_EEEvDpOT_@Base
 0.2.3
+#MISSING: 0.2.3-4# 
_ZNSt6vectorIN4WFUT12MirrorObjectESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_@Base
 0.2.3
  
(optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base
 0.2.3
  
(optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base
 0.2.3
  
(optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base
 0.2.3
  

Processed: Re: Bug#874365: ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #874365 [ruby-gdk3] ruby-gdk3: Typelib file for namespace 'Gdk' (any 
version) not found (GLib::Error)
Severity set to 'grave' from 'important'
> tag -1 stretch
Bug #874365 [ruby-gdk3] ruby-gdk3: Typelib file for namespace 'Gdk' (any 
version) not found (GLib::Error)
Added tag(s) stretch.

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

Bug#792189: marked as done (umockdev: FTBFS on lxc: test-umockdev-record.c: t_system_single: /dev/loop0: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 05:50:21 +
with message-id 
and subject line Bug#792189: fixed in umockdev 0.9.3-1
has caused the Debian Bug report #792189,
regarding umockdev: FTBFS on lxc: test-umockdev-record.c: t_system_single: 
/dev/loop0: No such file or directory
to be marked as done.

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

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


-- 
792189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: umockdev
Version: 0.8.11-2
Severity: wishlist

Dear Maintainer,

The package fails tests when running on lxc (or another similar setup with 
missing /dev/loop0):

/umockdev-record/system-single: **
ERROR:tests/test-umockdev-record.c:731:t_system_single: assertion failed 
(_tmp12_ == ""): ("Cannot access device /dev/loop0: No such file or 
directory\n" == "")
/bin/bash: line 1: 22989 Aborted (core dumped) TOP_BUILDD[..]
ckdev-wrapper $f
Makefile:2071: recipe for target 'check-local' failed

Annoyingly, t_system_single looks to contain code that tries to detect if /sys 
is broken,
and skip the test in this case.  Maybe the check could be extended to detect 
the lack of /dev/loop0?

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

Kernel: Linux 3.19.0-22-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: umockdev
Source-Version: 0.9.3-1

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

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated umockdev 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, 06 Sep 2017 07:25:13 +0200
Source: umockdev
Binary: umockdev libumockdev0 libumockdev-dev gir1.2-umockdev-1.0
Architecture: source amd64
Version: 0.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt 
Changed-By: Martin Pitt 
Description:
 gir1.2-umockdev-1.0 - introspection data for umockdev library
 libumockdev-dev - development files and documentation for libumockdev
 libumockdev0 - hardware mocking testbed for bug reports and regression tests
 umockdev   - record/mock hardware devices for bug reports and regression tests
Closes: 792189
Changes:
 umockdev (0.9.3-1) unstable; urgency=medium
 .
   * New upstream version:
 - In the /umockdev-record/system-single test, stop assuming that
   /dev/loop0 always exists, as that is not the case in containers and
   some other build machines. Use /dev/zero as second device instead.
   (Closes: #792189)
   * Bump debhelper compat to 10. This provides autoreconf as mandated by
 policy 4.0.
   * Bump Standards-Version to 4.0.1.
   * Strictly version libumockdev-dev's gir dependency.
Checksums-Sha1:
 e6591069c3c6f6d0e4d3c7e6ff1db36d8b6c7fed 2601 umockdev_0.9.3-1.dsc
 669b95bcc8000b06e9c0e7766af7fe19080d3c48 753960 umockdev_0.9.3.orig.tar.xz
 17ba634688c6471ee9af4f639aea50e2145c0e1d 117192 umockdev_0.9.3-1.debian.tar.xz
 1f6c137c3325c7881d4d499ab543eee46e4d97ce 5226 
gir1.2-umockdev-1.0_0.9.3-1_amd64.deb
 606ad5a585c00e72b6f3b43e08d0e86f42bf0d16 23048 
libumockdev-dev_0.9.3-1_amd64.deb
 025758ddfc5550f5847df0cd1677a5a44fd8c11b 111020 
libumockdev0-dbgsym_0.9.3-1_amd64.deb
 5befcf9597f5fa56be1692d9555393bd51c225d5 33408 libumockdev0_0.9.3-1_amd64.deb
 4c6d2189ecf756e68bc3914a1a9ac53edc4834ef 97526 
umockdev-dbgsym_0.9.3-1_amd64.deb
 bc28d370f9f1f76ade9831179ffec95a653b37e5 10721 umockdev_0.9.3-1_amd64.buildinfo
 b1bfae3e41bf564f4fa6cda715ba6cf5c353c2b5 43214 umockdev_0.9.3-1_amd64.deb
Checksums-Sha256:
 b47d53c54019ea55c2abc7cb5d2078d8e11eedac6062858e461f478b3aecdb23 2601 
umockdev_0.9.3-1.dsc
 e2f7c55f96b9bb02791cfd378bdad1e78eccaf6101a77f71ec211e386afd3d51 753960 
umockdev_0.9.3.orig.tar.xz
 

Bug#853635: qwtplot3d: ftbfs with GCC-7

[Satoru KURASHIKI]

Source: qwtplot3d
Followup-For: Bug #853635
Control: tags - 1 patch

hi,

I've prepared a patch which simply update library symbols.

hope it helps.

regards,
-- 
KURASHIKI Satoru
diff -uNr a/debian/libqwtplot3d-qt4-0v5.symbols 
b/debian/libqwtplot3d-qt4-0v5.symbols
--- a/debian/libqwtplot3d-qt4-0v5.symbols   2016-12-23 21:26:35.0 
+0900
+++ b/debian/libqwtplot3d-qt4-0v5.symbols   2017-09-06 11:39:29.66400 
+0900
@@ -243,10 +243,10 @@
  _ZN5Qwt3D4Axis9setMajorsEi@Base 0.2.7
  _ZN5Qwt3D4Axis9setMinorsEi@Base 0.2.7
  _ZN5Qwt3D4AxisC1ENS_6TripleES1_@Base 0.2.7
- (optional=templinst)_ZN5Qwt3D4AxisC1ERKS0_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# (optional=templinst)_ZN5Qwt3D4AxisC1ERKS0_@Base 
0.2.7
  _ZN5Qwt3D4AxisC1Ev@Base 0.2.7
  _ZN5Qwt3D4AxisC2ENS_6TripleES1_@Base 0.2.7
- (optional=templinst)_ZN5Qwt3D4AxisC2ERKS0_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# (optional=templinst)_ZN5Qwt3D4AxisC2ERKS0_@Base 
0.2.7
  _ZN5Qwt3D4AxisC2Ev@Base 0.2.7
  _ZN5Qwt3D4AxisD0Ev@Base 0.2.7
  _ZN5Qwt3D4AxisD1Ev@Base 0.2.7
@@ -268,7 +268,7 @@
  _ZN5Qwt3D5ArrowD0Ev@Base 0.2.7
  _ZN5Qwt3D5ArrowD1Ev@Base 0.2.7
  _ZN5Qwt3D5ArrowD2Ev@Base 0.2.7
- 
(optional=templinst)_ZN5Qwt3D5Color12createVectorERSt6vectorINS_4RGBAESaIS2_EE@Base
 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZN5Qwt3D5Color12createVectorERSt6vectorINS_4RGBAESaIS2_EE@Base
 0.2.7
  _ZN5Qwt3D5GL2QtEddd@Base 0.2.7
  _ZN5Qwt3D5Label11setPositionENS_6TripleENS_6ANCHORE@Base 0.2.7
  _ZN5Qwt3D5Label12devicefonts_E@Base 0.2.7
@@ -380,9 +380,9 @@
  _ZN5Qwt3D6Plot3DD0Ev@Base 0.2.7
  _ZN5Qwt3D6Plot3DD1Ev@Base 0.2.7
  _ZN5Qwt3D6Plot3DD2Ev@Base 0.2.7
- (optional=templinst)_ZN5Qwt3D7MappingD0Ev@Base 0.2.7
- (optional=templinst)_ZN5Qwt3D7MappingD1Ev@Base 0.2.7
- (optional=templinst)_ZN5Qwt3D7MappingD2Ev@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# (optional=templinst)_ZN5Qwt3D7MappingD0Ev@Base 
0.2.7
+#MISSING: 0.2.7+svn191-10.1# (optional=templinst)_ZN5Qwt3D7MappingD1Ev@Base 
0.2.7
+#MISSING: 0.2.7+svn191-10.1# (optional=templinst)_ZN5Qwt3D7MappingD2Ev@Base 
0.2.7
  _ZN5Qwt3D8CellData5clearEv@Base 0.2.7
  _ZN5Qwt3D8CellDataD0Ev@Base 0.2.7
  _ZN5Qwt3D8CellDataD1Ev@Base 0.2.7
@@ -465,7 +465,7 @@
  _ZNK5Qwt3D6Plot3D15keyboardEnabledEv@Base 0.2.7
  _ZNK5Qwt3D6Plot3D15lightingEnabledEv@Base 0.2.7
  _ZNK5Qwt3D6Plot3D8keySpeedERdS1_S1_@Base 0.2.7
- _ZNK5Qwt3D6TripleneES0_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# _ZNK5Qwt3D6TripleneES0_@Base 0.2.7
  _ZNK5Qwt3D7Mapping4nameEv@Base 0.2.7
  _ZNK5Qwt3D8CellData5emptyEv@Base 0.2.7
  _ZNK5Qwt3D8GridData4rowsEv@Base 0.2.7
@@ -474,40 +474,44 @@
  _ZNK5Qwt3D8LogScale5cloneEv@Base 0.2.7
  _ZNK5Qwt3D8LogScale8ticLabelEj@Base 0.2.7
  _ZNK5Qwt3D9CrossHair5cloneEv@Base 0.2.7
- 
(optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS2_S4_EERKS2_@Base
 0.2.7
- 
(optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS2_S4_EERKS2_@Base
 0.2.7
+ 
_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.2.7+svn191-10.1
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EED1Ev@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EED2Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED1Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED2Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EEaSERKS3_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED1Ev@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED2Ev@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EEaSERKS3_@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D4RGBAESaIS1_EEaSERKS3_@Base 0.2.7
- 
(optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base
 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base
 0.2.7
  
(optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EE17_M_default_appendEm@Base
 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EED1Ev@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EED2Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EEaSERKS3_@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D6Plot3D5LightESaIS2_EEaSERKS4_@Base 
0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EEaSERKS3_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 

Bug#874365: marked as done (ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found (GLib::Error))

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 04:07:06 +
with message-id 
and subject line Bug#874365: fixed in ruby-gnome2 3.1.8-7
has caused the Debian Bug report #874365,
regarding ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found 
(GLib::Error)
to be marked as done.

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

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


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

Hello there,

I was attempting to make a small thing with gtk3 (via ruby) this morning
and ran into an error with one of its dependencies:

```
/usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:37:in `require': 
Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)
from /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:37:in 
`load'
from /usr/lib/ruby/vendor_ruby/gdk3.rb:56:in `init'
from /usr/lib/ruby/vendor_ruby/gtk3.rb:64:in `init'
from /usr/lib/ruby/vendor_ruby/gtk3.rb:40:in `const_missing'
from ./pomodoro:5:in `'
```

It seems to fail with some pretty basic usage:

```
#!/usr/bin/env ruby

require 'gtk3'

window = Gtk::Window.new('test')
window.show
Gtk.init
Gtk.main
```

As the error refers missing files, I figure this would be a bug related
to the package. Please let me know if I'm mistaken.

Cheers,
JD

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (600, 'stable'), (500, 'stable'), (300, 'testing'), (1, 
'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages ruby-gdk3 depends on:
ii  ruby1:2.3.3
ii  ruby-atk3.1.0-1
ii  ruby-cairo-gobject  3.1.0-1
ii  ruby-gdk-pixbuf23.1.0-1
ii  ruby-gobject-introspection  3.1.0-1
ii  ruby-pango  3.1.0-1

ruby-gdk3 recommends no packages.

ruby-gdk3 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-gnome2
Source-Version: 3.1.8-7

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

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated ruby-gnome2 
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, 06 Sep 2017 12:19:59 +0900
Source: ruby-gnome2
Binary: ruby-glib2 ruby-atk ruby-cairo-gobject ruby-clutter ruby-clutter-gdk 
ruby-clutter-gtk ruby-gdk-pixbuf2 ruby-gdk3 ruby-gio2 ruby-gnome2 
ruby-gnome2-dev ruby-gobject-introspection ruby-gstreamer ruby-gtk2 ruby-gtk3 
ruby-gtksourceview2 ruby-gtksourceview3 ruby-pango ruby-poppler ruby-rsvg2 
ruby-webkit2-gtk
Architecture: source all amd64
Version: 3.1.8-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 ruby-atk   - ATK bindings for the Ruby language
 ruby-cairo-gobject - CairoGObject bindings for the Ruby language
 ruby-clutter - Clutter bindings for the Ruby language
 ruby-clutter-gdk - Clutter-Gdk bindings for the Ruby language
 ruby-clutter-gtk - Clutter-Gtk bindings for the Ruby language
 ruby-gdk-pixbuf2 - Gdk-Pixbuf 2 bindings for the Ruby language
 ruby-gdk3  - GDK 3 bindings for the Ruby language
 ruby-gio2  - GIO bindings for the Ruby language
 ruby-glib2 - GLib 2 bindings for the Ruby language
 ruby-gnome2 - GNOME-related bindings for the Ruby language
 ruby-gnome2-dev - GNOME-related bindings for the Ruby language (development 
files)
 ruby-gobject-introspection - GObject Introspection bindings for the Ruby 
language
 ruby-gstreamer - GStreamer bindings for the Ruby language
 ruby-gtk2  - 

Bug#874429: bzr: bzr+ssh URLs don't strip SSH options

[Salvatore Bonaccorso]

Source: bzr
Version: 2.6.0+bzr6595-6
Severity: grave
Tags: upstream security
Justification: user security hole
Control: fixed -1 2.7.0+bzr6622-7

Hi

This is handled already in unstable with 2.7.0+bzr6622-7, this bug is
to track the issue until the CVE is assigned and properly identified
via a CVE. A CVE was apparently requested, reading LP #1710979.

bzr (2.7.0+bzr6622-7) unstable; urgency=high

  * Add patch 27_fix_sec_ssh: Strip out hostnames starting with dash in
bzr+ssh URLs, as they might allow an attacker to provide SSH command-
line flags. LP: #1710979

https://bugs.launchpad.net/bzr/+bug/1710979

Regards,
Salvatore

Processed: bzr: bzr+ssh URLs don't strip SSH options

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.7.0+bzr6622-7
Bug #874429 [src:bzr] bzr: bzr+ssh URLs don't strip SSH options
Marked as fixed in versions bzr/2.7.0+bzr6622-7.

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

Bug#874430: openjpeg2: CVE-2017-14151: heap-based buffer overflow in opj_mqc_flush

[Salvatore Bonaccorso]

Source: openjpeg2
Version: 2.1.2-1.3
Severity: grave
Tags: security upstream patch
Forwarded: https://github.com/uclouvain/openjpeg/issues/982

Hi,

the following vulnerability was published for openjpeg2.

CVE-2017-14151[0]:
| An off-by-one error was discovered in
| opj_tcd_code_block_enc_allocate_data in lib/openjp2/tcd.c in OpenJPEG
| 2.2.0. The vulnerability causes an out-of-bounds write, which may lead
| to remote denial of service (heap-based buffer overflow affecting
| opj_mqc_flush in lib/openjp2/mqc.c and opj_t1_encode_cblk in
| lib/openjp2/t1.c) or possibly remote code execution.

Verifiable with an ASAN build of openjpeg2.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14151
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14151
[1] https://github.com/uclouvain/openjpeg/issues/982
[2] 
https://blogs.gentoo.org/ago/2017/08/16/openjpeg-heap-based-buffer-overflow-in-opj_mqc_flush-mqc-c/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: tagging 874419

[Debian Bug Tracking System]

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

> tags 874419 + pending
Bug #874419 [kexi-data] kexi-data: fails to upgrade from 'stretch' - trying to 
overwrite /usr/share/locale/tr/LC_MESSAGES/kexi.mo
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#874431: openjpeg2: CVE-2017-14152: heap-based buffer overflow in opj_write_bytes_LE

[Salvatore Bonaccorso]

Source: openjpeg2
Version: 2.1.2-1.3
Severity: grave
Tags: upstream patch security
Forwarded: https://github.com/uclouvain/openjpeg/issues/985

Hi,

the following vulnerability was published for openjpeg2.

CVE-2017-14152[0]:
| A mishandled zero case was discovered in opj_j2k_set_cinema_parameters
| in lib/openjp2/j2k.c in OpenJPEG 2.2.0. The vulnerability causes an
| out-of-bounds write, which may lead to remote denial of service
| (heap-based buffer overflow affecting opj_write_bytes_LE in
| lib/openjp2/cio.c and opj_j2k_write_sot in lib/openjp2/j2k.c) or
| possibly remote code execution.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14152
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14152
[1] https://github.com/uclouvain/openjpeg/issues/985

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#873654: python-py-zipkin: Incomplete debian/copyright?

[olivier sallou]

Le mar. 5 sept. 2017 à 21:00, Ben Plotnick  a écrit :

> Hi Chris,
>
> On Tue, 29 Aug 2017 20:24:55 +0100 Chris Lamb  wrote:
> > Source: python-py-zipkin
> > Version: 0.9.0-1
> > Severity: serious
> > Justication: Policy 12.5
> > X-Debbugs-CC: Olivier Sallou 
> >
> > Hi,
> >
> > I just ACCEPTed python-py-zipkin from NEW but noticed it was missing
> > attribution in debian/copyright for at least Twitter, Inc.
> I don't understand this. What needs to be attributed to Twitter, Inc.?
>
> The py_zipkin copyright is owned by Yelp, Inc, and the Zipkin code
> (which is not contained in py_zipkin) is now owned by The OpenZipkin
> Authors.
>

Indeed, license upstream file specifies that copyright is from Yelp, no
reference to Twitter (at least I saw none). Did I miss something or can I
close the bug?


>
> >
> > (This is not exhaustive so please check over the entire package
> > carefully and address these on your next upload.)
> >
> >
> > Best wishes,
> >
> > --
> >   ,''`.
> >  : :'  : Chris Lamb
> >  `. `'`  la...@debian.org / chris-lamb.co.uk
> >`-
> >
> >
>
> Thanks,
> Ben Plotnick
>

Bug#853485: marked as done (libcec: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 22:06:54 +
with message-id 
and subject line Bug#853485: fixed in libcec 4.0.2+dfsg1-1
has caused the Debian Bug report #853485,
regarding libcec: 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.)


-- 
853485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcec
Version: 4.0.1+dfsg1-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/libcec_4.0.1+dfsg1-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

[...]
- 
(arch-bits=64)_ZNSt11_Deque_baseIPN3CEC28CCECAdapterMessageQueueEntryESaIS2_EE17_M_initialize_mapEm@Base
 3.1.0
+#MISSING: 4.0.1+dfsg1-1# 
(arch-bits=64)_ZNSt11_Deque_baseIPN3CEC28CCECAdapterMessageQueueEntryESaIS2_EE17_M_initialize_mapEm@Base
 3.1.0
  
(optional=templinst|arch=armel)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base
 3.1.0
  
(optional=templinst|arch=!armel)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 3.0.1
  
(optional=templinst|arch=armel)_ZNSt15_Sp_counted_ptrIPN3CEC10CCECClientELN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base
 3.1.0
@@ -959,19 +960,25 @@
  
(optional=templinst|arch=!armel)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base
 3.0.1
  
(optional=templinst|arch=!armel)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base
 3.0.1
  
(optional=templinst)_ZNSt5dequeIN3CEC11cec_commandESaIS1_EE16_M_push_back_auxIJRKS1_EEEvDpOT_@Base
 3.0.1
- 
(optional=templinst)_ZNSt5dequeIPN3CEC13CCallbackWrapESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base
 3.0.1
+#MISSING: 4.0.1+dfsg1-1# 
(optional=templinst)_ZNSt5dequeIPN3CEC13CCallbackWrapESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base
 3.0.1
  
(optional=templinst)_ZNSt5dequeIPN3CEC28CCECAdapterMessageQueueEntryESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base
 3.0.1
- 
(optional=templinst)_ZNSt6vectorIN3CEC11cec_commandESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_@Base
 3.0.1
- 
(optional=templinst)_ZNSt6vectorIN3CEC20device_type_change_tESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_@Base
 3.0.1
+ 
_ZNSt6vectorIN3CEC11cec_commandESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 4.0.1+dfsg1-1
+#MISSING: 4.0.1+dfsg1-1# 
(optional=templinst)_ZNSt6vectorIN3CEC11cec_commandESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_@Base
 3.0.1
+ 
_ZNSt6vectorIN3CEC20device_type_change_tESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 4.0.1+dfsg1-1
+#MISSING: 4.0.1+dfsg1-1# 
(optional=templinst)_ZNSt6vectorIN3CEC20device_type_change_tESaIS1_EE19_M_emplace_back_auxIJRKS1_EEEvDpOT_@Base
 3.0.1
  
(optional=templinst)_ZNSt6vectorIN3CEC20device_type_change_tESaIS1_EED1Ev@Base 
3.0.1
  
(optional=templinst)_ZNSt6vectorIN3CEC20device_type_change_tESaIS1_EED2Ev@Base 
3.0.1
- 
(optional=templinst)_ZNSt6vectorIPN3CEC13CCECBusDeviceESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 3.0.1
- 
(optional=templinst)_ZNSt6vectorIPN3CEC13CCECBusDeviceESaIS2_EE19_M_emplace_back_auxIJS2_EEEvDpOT_@Base
 3.0.1
+ 
_ZNSt6vectorIPN3CEC13CCECBusDeviceESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 4.0.1+dfsg1-1
+ 
_ZNSt6vectorIPN3CEC13CCECBusDeviceESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 4.0.1+dfsg1-1
+#MISSING: 

Processed: severity of 842432 is serious

[Debian Bug Tracking System]

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

> # fixed in stable
> severity 842432 serious
Bug #842432 [src:ruby2.3] ruby2.3: CVE-2016-7798: IV Reuse in GCM Mode
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 864860 is serious

[Debian Bug Tracking System]

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

> # fixed in stable
> severity 864860 serious
Bug #864860 [src:ruby2.3] ruby2.3: CVE-2015-9096: SMTP command injection via 
CRLF sequences in RCPT TO or MAIL FROM commands in Net::SMTP
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#874419: kexi-data: fails to upgrade from 'stretch' - trying to overwrite /usr/share/locale/tr/LC_MESSAGES/kexi.mo

[Andreas Beckmann]

Package: kexi-data
Version: 1:3.0.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package kexi-data.
  Preparing to unpack .../kexi-data_1%3a3.0.2-2_all.deb ...
  Unpacking kexi-data (1:3.0.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kexi-data_1%3a3.0.2-2_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/tr/LC_MESSAGES/kexi.mo', which is 
also in package calligra-l10n-tr 1:2.9.11-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kexi-data_1%3a3.0.2-2_all.deb


cheers,

Andreas


calligra-l10n-tr=1%2.9.11-1_kexi-data=1%3.0.2-2.log.gz
Description: application/gzip

Bug#853718: marked as done (zoom-player: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:51:34 +
with message-id 
and subject line Bug#853718: fixed in zoom-player 1.1.5~dfsg-4
has caused the Debian Bug report #853718,
regarding zoom-player: 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.)


-- 
853718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zoom-player
Version: 1.1.5~dfsg-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/zoom-player_1.1.5~dfsg-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

[...]
blorb.c:425:19: warning: variable 'rec' set but not used 
[-Wunused-but-set-variable]
unsigned char* rec;
   ^~~
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -finline-functions -funroll-loops 
-fomit-frame-pointer  -I/usr/include/freetype2  -DDATADIR="\"/usr/share/zoom\"" 
-c -o image_libpng.o image_libpng.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -finline-functions -funroll-loops 
-fomit-frame-pointer  -I/usr/include/freetype2  -DDATADIR="\"/usr/share/zoom\"" 
-c -o image_ximage.o image_ximage.c
image_ximage.c: In function 'image_to_ximage_render':
image_ximage.c:237:8: warning: pointer targets in assignment differ in 
signedness [-Wpointer-sign]
row = xim->data;
^
image_ximage.c:273:8: warning: pointer targets in assignment differ in 
signedness [-Wpointer-sign]
row = xim->data;
^
image_ximage.c: In function 'image_to_ximage_truecolour':
image_ximage.c:370:8: warning: pointer targets in assignment differ in 
signedness [-Wpointer-sign]
row = xim->data;
^
image_ximage.c:405:8: warning: pointer targets in assignment differ in 
signedness [-Wpointer-sign]
row = xim->data;
^
image_ximage.c: In function 'image_to_mask_truecolour':
image_ximage.c:478:11: warning: pointer targets in assignment differ in 
signedness [-Wpointer-sign]
   row = xim->data + (y*xim->bytes_per_line);
   ^
image_ximage.c:479:14: warning: pointer targets in assignment differ in 
signedness [-Wpointer-sign]
   oldrow = orig->data + (y*orig->bytes_per_line);
  ^
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -finline-functions -funroll-loops 
-fomit-frame-pointer  -I/usr/include/freetype2  -DDATADIR="\"/usr/share/zoom\"" 
-c -o image_carbon.o image_carbon.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -finline-functions -funroll-loops 
-fomit-frame-pointer  -I/usr/include/freetype2  -DDATADIR="\"/usr/share/zoom\"" 
-c -o image_none.o image_none.c
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -finline-functions -funroll-loops 
-fomit-frame-pointer  -I/usr/include/freetype2  -DDATADIR="\"/usr/share/zoom\"" 
 -Wl,-z,relro -Wl,-z,now -o zoom  main.o interp.o file.o options.o zmachine.o 
zscii.o display.o xdisplay.o hash.o tokenise.o stream.o font3.o state.o rc.o 
rc_parse.o rc_lex.o menu.o xfont.o windisplay.o winfont.o 

Processed: Pending fixes for bugs in the jruby-maven-plugins package

[Debian Bug Tracking System]

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

> tag 867648 + pending
Bug #867648 [src:jruby-maven-plugins] jruby-maven-plugins: FTBFS: 
RailsService.java:[26,20] variable session might not have been initialized
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867648: marked as done (jruby-maven-plugins: FTBFS: RailsService.java:[26,20] variable session might not have been initialized)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 22:06:26 +
with message-id 
and subject line Bug#867648: fixed in jruby-maven-plugins 1.1.5+ds1-2
has caused the Debian Bug report #867648,
regarding jruby-maven-plugins: FTBFS: RailsService.java:[26,20] variable 
session might not have been initialized
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.)


-- 
867648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jruby-maven-plugins
Version: 1.1.5+ds1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 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 '/<>/jruby-maven-plugins-1.1.5+ds1'
> dh_auto_build -- install
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/jruby-maven-plugins-1.1.5\+ds1
>  -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/jruby-maven-plugins-1.1.5\+ds1/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/jruby-maven-plugins-1.1.5\+ds1/debian 
> -Dmaven.repo.local=/<>/jruby-maven-plugins-1.1.5\+ds1/debian/maven-repo
>  install -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] JRuby Maven Mojos
> [INFO] Mojo Parent
> [INFO] Ruby Tools
> [INFO] JRuby Maven Mojo
> [INFO] Gem Maven Mojo
> [INFO] 
> [INFO] 
> 
> [INFO] Building JRuby Maven Mojos 1.1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install 
> (default-install) @ jruby-maven-plugins ---
> [INFO] Installing 
> /<>/jruby-maven-plugins-1.1.5+ds1/pom.xml to 
> /<>/jruby-maven-plugins-1.1.5+ds1/debian/maven-repo/de/saumya/mojo/jruby-maven-plugins/1.1.5/jruby-maven-plugins-1.1.5.pom
> [INFO] 
> [INFO] 
> 
> [INFO] Building Mojo Parent 1.1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-plugin-plugin:3.5:helpmojo 
> (default) @ parent-mojo ---
> [WARNING] Unsupported packaging type pom, execution skipped
> [INFO] 
> [INFO] >>> maven-source-plugin:2.4:jar 
> (default) > generate-sources @ parent-mojo 
> >>>
> [INFO] 
> [INFO] <<< maven-source-plugin:2.4:jar 
> (default) < generate-sources @ parent-mojo 
> <<<
> [INFO] 
> [INFO] 
> [INFO] --- maven-source-plugin:2.4:jar 
> (default) @ parent-mojo ---
> [INFO] Skipping source per configuration.
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install 
> (default-install) @ parent-mojo ---
> [INFO] Installing 
> /<>/jruby-maven-plugins-1.1.5+ds1/parent-mojo/pom.xml to 
> /<>/jruby-maven-plugins-1.1.5+ds1/debian/maven-repo/de/saumya/mojo/parent-mojo/1.1.5/parent-mojo-1.1.5.pom
> [INFO] 
> [INFO] 
> 
> [INFO] Building Ruby Tools 1.1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-dependency-plugin:2.8:copy (copy 
> jruby) @ ruby-tools ---
> [INFO] Configured Artifact: org.jruby:jruby-complete:debian:jar
> [INFO] Copying jruby-complete-debian.jar to 
> 

Processed: Re: ruby-rack-proxy: accesses the internet during build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #860198 [src:ruby-rack-proxy] ruby-rack-proxy: accesses the internet during 
build
Severity set to 'serious' from 'important'

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

Bug#873679: dislocker: libdislocker* renamed without transition packages

[Andreas Beckmann]

On Wed, 30 Aug 2017 00:31:15 -0300 Giovani Augusto Ferreira
 wrote:
> The libdislocker* packages were renamed without following
> the guidelines at https://wiki.debian.org/RenamingPackages
> and this will cause failures during upgrade.

WTF? Transitional packages for shared libraries are an insane idea.
That's what we have library transitions for.


Andreas

Bug#873654: python-py-zipkin: Incomplete debian/copyright?

[Chris Lamb]

Hi Olivier,

> Indeed, license upstream file specifies that copyright is from Yelp, no
> reference to Twitter (at least I saw none)

Really?

  $ grep -r Twitter . | wc -l
  1

;)

If this is a false positive, please clarify it clearly in debian/copyright;
having clarifications on a bug or, worse, sent directly to ftpmasters means
at the very least that our derivatives cannot find such valuable info.


Regards,

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

Bug#871234: marked as done (cufflinks: FTBFS with GCC-7: error: type/value mismatch at argument 1 in template parameter list for 'template struct std::hash')

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 22:19:51 +
with message-id 
and subject line Bug#871234: fixed in cufflinks 2.2.1+dfsg.1-1
has caused the Debian Bug report #871234,
regarding cufflinks: FTBFS with GCC-7: error: type/value mismatch at argument 1 
in template parameter list for 'template struct std::hash'
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.)


-- 
871234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cufflinks
Version: 2.2.1-3
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

cufflinks FTBFS since GCC-7 was made the default compiler:

[...]
In file included from gff.h:12:0,
 from gtf_tracking.h:12,
 from bundles.h:22,
 from replicates.h:10,
 from common.cpp:28:
GHash.hh: In member function 'GHash::GHashEntry* GHash::NextEntry()':
GHash.hh:91:44: error: type/value mismatch at argument 1 in template parameter 
list for 'template struct std::hash'
 while (pos::NextKey()':
GHash.hh:415:41: error: type/value mismatch at argument 1 in template parameter 
list for 'template struct std::hash'
  while (pos::NextData()':
GHash.hh:428:41: error: type/value mismatch at argument 1 in template parameter 
list for 'template struct std::hash'
  while (pos::NextData(char*&)':
GHash.hh:442:41: error: type/value mismatch at argument 1 in template parameter 
list for 'template struct std::hash'
  while (pos

cufflinks_2.2.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cufflinks
Source-Version: 2.2.1+dfsg.1-1

We believe that the bug you reported is fixed in the latest version of
cufflinks, 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.
Alexandre Mestiashvili  (supplier of updated 
cufflinks 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, 05 Sep 2017 23:42:17 +0200
Source: cufflinks
Binary: cufflinks
Architecture: source amd64
Version: 2.2.1+dfsg.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Alexandre Mestiashvili 
Description:
 cufflinks  - Transcript assembly, differential expression and regulation for R
Closes: 871234
Changes:
 cufflinks (2.2.1+dfsg.1-1) unstable; urgency=medium
 .
   [ Mattia Rizzolo ]
   * add a closes to the previous changelog entry
 .
   [ Alexandre Mestiashvili ]
   * Update d/watch
   * Update d/copyright, add Files-Excluded section,
 use https for copyrigth-format, add Upstream-Name
   * New upstream version 2.2.1+dfsg.1
   * Update d/rules, use variables provided by /usr/share/dpkg/default.mk
   * Add patch fixing ftbfs with gcc-7, Closes: #871234
 thanks to Jeff Epler 
   * Update 0003-fix_includes_path.patch and 0001-fix_spelling.patch
   * Bump Standards-Version in d/control
Checksums-Sha1:
 1e8e7e905db9e74c895b0c0319ca652446f3e866 2233 cufflinks_2.2.1+dfsg.1-1.dsc
 9fdcb7443683c21c93a16213dd86e18e59722cbf 637715 
cufflinks_2.2.1+dfsg.1.orig.tar.gz
 2edd7dc90c0c872292e56ad2fc94b126332a238c 12708 
cufflinks_2.2.1+dfsg.1-1.debian.tar.xz
 ab1d30988ccce1b8b5d5cb9a757a59837da6effb 54016460 
cufflinks-dbgsym_2.2.1+dfsg.1-1_amd64.deb
 2e5ae774f71baf13332fafab3d6c2044aefc716a 7609 
cufflinks_2.2.1+dfsg.1-1_amd64.buildinfo
 35a1a5e8abe644dac157af75625a70c1c7bc10a8 1508360 
cufflinks_2.2.1+dfsg.1-1_amd64.deb
Checksums-Sha256:
 6e2a32998ae0cb60bc7dcb7ec579791d872b59f1b7c2fec5b40dc4edbd71a0ee 2233 
cufflinks_2.2.1+dfsg.1-1.dsc
 3759d56fe85365ebca156bc302b5248a95bd386d34eb7c5e4900f267414e8ea3 637715 
cufflinks_2.2.1+dfsg.1.orig.tar.gz
 61899aabd39abcfb23f441f197b22f94c6e91b3d72c9f4b694fe08a132e11e17 12708 
cufflinks_2.2.1+dfsg.1-1.debian.tar.xz
 6f30e8bd4a97e94794980d9f923346508c2a6b20ddf6d7fe966310898a529edc 54016460 
cufflinks-dbgsym_2.2.1+dfsg.1-1_amd64.deb
 

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Andreas Beckmann]

Package: python3-cliapp
Version: 1.20170827-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python3-cliapp.
  Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
  Unpacking python3-cliapp (1.20170827-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also in 
package python-cliapp 1.20160724-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb


cheers,

Andreas


python-cliapp=1.20160724-2_python3-cliapp=1.20170827-1.log.gz
Description: application/gzip

Bug#853706: marked as done (wfmath: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 22:22:56 +
with message-id 
and subject line Bug#853706: fixed in wfmath 1.0.2+dfsg1-4
has caused the Debian Bug report #853706,
regarding wfmath: 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.)


-- 
853706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wfmath
Version: 1.0.2+dfsg1-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/wfmath_1.0.2+dfsg1-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

[...]
  _ZN6WFMath9IntersectINS_5PointILi2EEENS_7SegmentILi2EbRKT_RKT0_b@Base 
0.3.11
  _ZN6WFMath9IntersectINS_5PointILi3EEENS_4BallILi3EbRKT_RKT0_b@Base 0.3.11
  _ZN6WFMath9IntersectINS_5PointILi3EEENS_6RotBoxILi3EbRKT_RKT0_b@Base 
0.3.11
@@ -1007,24 +1007,28 @@
  _ZNK6WFMath9RotMatrixILi3EE9isEqualToERKS1_f@Base 1.0.0
  _ZNK6WFMath9RotMatrixILi3EEeqERKS1_@Base 0.3.11
  _ZNK6WFMath9RotMatrixILi3EEneERKS1_@Base 0.3.11
- 
(optional=inline)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base
 0.3.12
- 
(optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base
 0.3.12
- 
(optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base
 0.3.12
- 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2
- 
_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE13_M_insert_auxIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2
+#MISSING: 1.0.2+dfsg1-3# 
(optional=inline)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base
 0.3.12
+#MISSING: 1.0.2+dfsg1-3# 
(optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base
 0.3.12
+#MISSING: 1.0.2+dfsg1-3# 
(optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base
 0.3.12
+#MISSING: 1.0.2+dfsg1-3# 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2
+#MISSING: 1.0.2+dfsg1-3# 
_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE13_M_insert_auxIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2
  
(regex)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE17_M_default_appendE[jm]@Base 
1.0.2
- 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.2
- 
_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 1.0.2
+ 
_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2+dfsg1-3
+#MISSING: 1.0.2+dfsg1-3# 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.2
+#MISSING: 1.0.2+dfsg1-3# 
_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
 1.0.2
  (optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EEaSERKS4_@Base 
0.3.11
- 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi3EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
- 
_ZNSt6vectorIN6WFMath5PointILi3EEESaIS2_EE13_M_insert_auxIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
+#MISSING: 1.0.2+dfsg1-3# 

Bug#874420: node-babel-cli: /usr/bin/babel is already provided by openbabel

[Andreas Beckmann]

Package: node-babel-cli
Version: 6.25.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package node-babel-cli.
  Preparing to unpack .../62-node-babel-cli_6.25.0+dfsg-2_all.deb ...
  Unpacking node-babel-cli (6.25.0+dfsg-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-J0N6hl/62-node-babel-cli_6.25.0+dfsg-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/babel', which is also in package openbabel 
2.3.2+dfsg-3+b2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-J0N6hl/62-node-babel-cli_6.25.0+dfsg-2_all.deb


This does *not* look like adding Breaks+Replaces would be the correct solution.


cheers,

Andreas


openbabel=2.3.2+dfsg-3+b2_node-babel-cli=6.25.0+dfsg-2.log.gz
Description: application/gzip

Processed: found 873312 in 2.3.1+dfsg-1, found 873312 in 3.0.10-2, found 874420 in 6.25.0+dfsg-1, tagging 864927 ...

[Debian Bug Tracking System]

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

> found 873312 2.3.1+dfsg-1
Bug #873312 [python-simpy-doc,python-simpy3-doc] python-simpy3-doc and 
python-simpy-doc: error when trying to install together
There is no source info for the package 'python-simpy3-doc' at version 
'2.3.1+dfsg-1' with architecture ''
Marked as found in versions python-simpy/2.3.1+dfsg-1.
> found 873312 3.0.10-2
Bug #873312 [python-simpy-doc,python-simpy3-doc] python-simpy3-doc and 
python-simpy-doc: error when trying to install together
There is no source info for the package 'python-simpy-doc' at version 
'3.0.10-2' with architecture ''
Marked as found in versions python-simpy3/3.0.10-2.
> found 874420 6.25.0+dfsg-1
Bug #874420 [node-babel-cli] node-babel-cli: /usr/bin/babel is already provided 
by openbabel
Marked as found in versions node-babel/6.25.0+dfsg-1.
> tags 864927 + experimental
Bug #864927 {Done: Maximiliano Curia } 
[plasma-desktop-data,kde-l10n-sr] kde-l10n-sr and plasma-desktop-data: error 
when trying to install together
Added tag(s) experimental.
> reassign 864927 kde-l10n-sr 4:16.04.3-1
Bug #864927 {Done: Maximiliano Curia } 
[plasma-desktop-data,kde-l10n-sr] kde-l10n-sr and plasma-desktop-data: error 
when trying to install together
Bug reassigned from package 'plasma-desktop-data,kde-l10n-sr' to 'kde-l10n-sr'.
No longer marked as found in versions live-task-kde/0.1, kde-l10n/4:16.04.3-1, 
and plasma-desktop/4:5.8.7.1-1.
No longer marked as fixed in versions kde-l10n/4:17.04.3-1.
Bug #864927 {Done: Maximiliano Curia } [kde-l10n-sr] 
kde-l10n-sr and plasma-desktop-data: error when trying to install together
Marked as found in versions kde-l10n/4:16.04.3-1.
> affects 864927 + plasma-desktop-data
Bug #864927 {Done: Maximiliano Curia } [kde-l10n-sr] 
kde-l10n-sr and plasma-desktop-data: error when trying to install together
Added indication that 864927 affects plasma-desktop-data
> fixed 864927 4:17.04.3-1
Bug #864927 {Done: Maximiliano Curia } [kde-l10n-sr] 
kde-l10n-sr and plasma-desktop-data: error when trying to install together
Marked as fixed in versions kde-l10n/4:17.04.3-1.
> thanks
Stopping processing here.

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

Bug#873608: uhd: NEON-related FTBFS on armhf

[A. Maitland Bottoms]

So yeah, we cannot expect NEON on Debian armhf.

But I did not expect these compile time errors... I would hope that
one could at least compile some NEON code on Debian armhf, and then
maybe do some runtime conditional test to only execute NEON if it
is available.

This code has not compiled on Debian for a while, so I am bringing back
a debian-armhf-convert-without-neon patch I used before.

-Maitland

Bug#870861: marked as done (polari FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Tue, 5 Sep 2017 22:40:46 -0400
with message-id 

and subject line Re: polari FTBFS: test failure
has caused the Debian Bug report #870861,
regarding polari FTBFS: test failure
to be marked as done.

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

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


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

Some recent change in unstable makes polari FTBFS:

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

...
   dh_auto_test
make -j16 check VERBOSE=1
make[1]: Entering directory '/build/1st/polari-3.22.2'
Making check in src
make[2]: Entering directory '/build/1st/polari-3.22.2/src'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/build/1st/polari-3.22.2/src'
Making check in data
make[2]: Entering directory '/build/1st/polari-3.22.2/data'
Making check in appdata
make[3]: Entering directory '/build/1st/polari-3.22.2/data/appdata'
/usr/bin/msgfmt --xml --template org.gnome.Polari.appdata.xml.in -d ../../po -o 
org.gnome.Polari.appdata.xml
if test -f "org.gnome.Polari.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}org.gnome.Polari.appdata.xml; fi \
&& touch org.gnome.Polari.appdata.valid
org.gnome.Polari.appdata.xml: 
(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.
FAILED:
? attribute-invalid :  is invalid [HighContast]
Validation of files failed
Makefile:513: recipe for target 'org.gnome.Polari.appdata.valid' failed
make[3]: *** [org.gnome.Polari.appdata.valid] Error 1
make[3]: Leaving directory '/build/1st/polari-3.22.2/data/appdata'
Makefile:563: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/build/1st/polari-3.22.2/data'
Makefile:463: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/1st/polari-3.22.2'
dh_auto_test: make -j16 check VERBOSE=1 returned exit code 2
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Version: 3.24.2-1

Oops, sorry for not checking the bug tracker before uploading but this
issue has been fixed in the new version uploaded today:

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

Thanks,
Jeremy Bicha--- End Message ---

Bug#874422: python-pycoast-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc-base/pycoast

[Andreas Beckmann]

Package: python-pycoast-doc
Version: 1.0.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-pycoast-doc.
  Preparing to unpack .../5-python-pycoast-doc_1.0.0+dfsg-1_all.deb ...
  Unpacking python-pycoast-doc (1.0.0+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Mstk25/5-python-pycoast-doc_1.0.0+dfsg-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/doc-base/pycoast', which is also in package 
python-pycoast 0.5.4+dfsg-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Mstk25/5-python-pycoast-doc_1.0.0+dfsg-1_all.deb


cheers,

Andreas


python-pycoast=0.5.4+dfsg-1_python-pycoast-doc=1.0.0+dfsg-1.log.gz
Description: application/gzip

Bug#874423: libpinyin-data: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libpinyin/data/addon_phrase_index.bin

[Andreas Beckmann]

Package: libpinyin-data
Version: 2.0.92-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libpinyin-data:amd64.
  Preparing to unpack .../libpinyin-data_2.0.92-1~exp1_amd64.deb ...
  Unpacking libpinyin-data:amd64 (2.0.92-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libpinyin-data_2.0.92-1~exp1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libpinyin/data/addon_phrase_index.bin', which is 
also in package libpinyin7:amd64 1.3.0-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libpinyin-data_2.0.92-1~exp1_amd64.deb


cheers,

Andreas


libpinyin7=1.3.0-3_libpinyin-data=2.0.92-1~exp1.log.gz
Description: application/gzip

Bug#874424: soapdenovo: please Build-Depend on rename

[Dominic Hargreaves]

Source: soapdenovo
Version: 1.05-3
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl 5.26.0-7 (just uploaded to unstable) as
a result. Please add a Build-Depends: rename to your package, and all
will be well again:

cd debian/soapdenovo/usr/bin/;rename 's/SOAP/soap/' SOAP*
/bin/sh: 1: rename: not found
debian/rules:13: recipe for target 'override_dh_install' failed

Let me know if you would prefer an NMU to get this trivial change made. 

Cheers,
Dominic.

[1] 

Bug#874425: soapdenovo2: please Build-Depend on rename

[Dominic Hargreaves]

Source: soapdenovo2
Version: 240+dfsg1-2
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl 5.26.0-7 (just uploaded to unstable) as
a result. Please add a Build-Depends: rename to your package, and all
will be well again:

cd debian/soapdenovo2/usr/bin/;rename 's/SOAPdenovo/soapdenovo2/' SOAP*
/bin/sh: 1: rename: not found
debian/rules:24: recipe for target 'override_dh_install' failed

Let me know if you would prefer an NMU to get this trivial change made. 

Cheers,
Dominic.

[1] 

Processed: tagging 874425

[Debian Bug Tracking System]

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

> tags 874425 + sid buster
Bug #874425 [src:soapdenovo2] soapdenovo2: please Build-Depend on rename
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 874424

[Debian Bug Tracking System]

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

> tags 874424 + sid buster
Bug #874424 [src:soapdenovo] soapdenovo: please Build-Depend on rename
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#873608: marked as done (uhd: NEON-related FTBFS on armhf)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 00:20:16 +
with message-id 
and subject line Bug#873608: fixed in uhd 3.10.2.0-2
has caused the Debian Bug report #873608,
regarding uhd: NEON-related FTBFS on armhf
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=uhd=armhf=3.10.2.0-1=1503874671=0

...
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h: In member function 
'virtual void __convert_fc32_1_sc16_item32_le_1_PRIORITY_SIMD::operator()(const 
input_type&, const output_type&, size_t)':
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:6740:1: error: inlining 
failed in call to always_inline 'float32x4_t vdupq_n_f32(float32_t)': target 
specific option mismatch
 vdupq_n_f32 (float32_t __a)
 ^~~
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:36:53: note: called from 
here
 float32x4_t Q0 = vdupq_n_f32(float(scale_factor));
 ^
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:10844:1: error: inlining 
failed in call to always_inline 'void vst1_s16(int16_t*, int16x4_t)': target 
specific option mismatch
 vst1_s16 (int16_t * __a, int16x4_t __b)
 ^~~~
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:65:17: note: called from 
here
 vst1_s16((reinterpret_cast([i+6])), D15);
 ^~
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:9027:1: error: inlining 
failed in call to always_inline 'int16x4_t vrev32_s16(int16x4_t)': target 
specific option mismatch
 vrev32_s16 (int16x4_t __a)
 ^~
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:64:39: note: called from 
here
 int16x4_t D15 = vrev32_s16(D14);
   ^
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:7552:1: error: inlining 
failed in call to always_inline 'int16x4_t vmovn_s32(int32x4_t)': target 
specific option mismatch
 vmovn_s32 (int32x4_t __a)
 ^
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:63:38: note: called from 
here
 int16x4_t D14 = vmovn_s32(Q13);
  ^
...



NEON is not part of the armhf port baseline.
--- End Message ---
--- Begin Message ---
Source: uhd
Source-Version: 3.10.2.0-2

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated uhd 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, 05 Sep 2017 18:48:41 -0400
Source: uhd
Binary: uhd-host libuhd003.010.002 libuhd-dev
Architecture: source
Version: 3.10.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 libuhd-dev - universal hardware driver for Ettus Research products - headers
 libuhd003.010.002 - universal hardware driver for Ettus Research products - 
library
 uhd-host   - universal hardware driver for Ettus Research products - host apps
Closes: 873608
Changes:
 uhd (3.10.2.0-2) unstable; urgency=medium
 .
   * avoid gcc 7 and armhf neon for now (Closes: 873608)
 by bringing back debian-armhf-convert-without-neon patch
Checksums-Sha1:
 41106d8ad12e6676a1f221d372a98c65f9b5fe29 2721 uhd_3.10.2.0-2.dsc
 99034f931e1ef56822d5dea235aad9c489f97247 237544 uhd_3.10.2.0-2.debian.tar.xz
 d85b680bdc132c859e2e8f8c3291f82aa7fc3677 11939 

Processed: r-bioc-rtracklayer: FTBFS: Error: package or namespace load failed for 'rtracklayer' in dyn.load(file, DLLpath = DLLpath, ...):

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - buster
Bug #871333 {Done: Andreas Tille } [src:r-bioc-rtracklayer] 
r-bioc-rtracklayer: FTBFS: Error: package or namespace load failed for 
'rtracklayer' in dyn.load(file, DLLpath = DLLpath, ...):
Removed tag(s) buster.

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

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

[Graham Inggs]

Control: tags -1 - buster

r-bioc-rtracklayer 1.34.1-1 builds fine in testing

Bug#873778: Fix for the mozjs52 build on armel

[Jeremy Bicha]

On Mon, Sep 4, 2017 at 7:45 AM, Adrian Bunk  wrote:
> Changes in this patch:

Thanks. Uploading that patch now with 52.3.1-4 but not closing this
bug since there are other issues remaining here.

Jeremy Bicha

Bug#874337: src:gr-iio: maintainer address bounces

[Ansgar Burchardt]

Source: gr-iio
Version: 0.2.36-1
Severity: serious

[ X-Debbugs-Cc'ed last uploader. ]

The maintainer address for gr-iio bounces (same for libad9361 and
libiio), see below.

Ansgar

> Delivery has failed to these recipients or groups:
>
> Paul Cercueil (paul.cercu...@analog.com)
> The e-mail address you entered couldn't be found. Please check the 
> recipient's e-mail address and try to resend the message. If the problem 
> continues, please contact your helpdesk.
>
>
>
>
>
>
>
> Diagnostic information for administrators:
>
> Generating server: analog.com
>
> paul.cercu...@analog.com
> #550 5.1.1 RESOLVER.ADR.RecipNotFound; not found 
> ##rfc822;paul.cercu...@analog.com
>
> Original message headers:
>
> Received: from nwd2feex2.utm.analog.com (137.71.25.64) by
>  NWD2HUBCAS9.ad.analog.com (10.64.69.109) with Microsoft SMTP Server (TLS) id
>  14.3.210.2; Tue, 5 Sep 2017 00:35:13 -0400
> Received: from localhost.localdomain (localhost [127.0.0.1])by
>  nwd2feex2.utm.analog.com (Postfix) with SMTP id 3xmYmK47Pcz3jp7c   for
>  ; Tue,  5 Sep 2017 00:35:13 -0400 (EDT)
> Received: from nwd2mta4.analog.com (nwd2mta2.analog.com [137.71.25.57]) by
>  nwd2feex2.utm.analog.com (Postfix) with ESMTPS id 3xmYmK237Rz3jp7Y for
>  ; Tue,  5 Sep 2017 00:35:13 -0400 (EDT)
> Received: from NAM01-SN1-obe.outbound.protection.outlook.com
>  (mail-sn1nam01lp0117.outbound.protection.outlook.com [207.46.163.117]) by
>  nwd2mta4.analog.com (8.13.8/8.13.8) with ESMTP id v854ZCi0011334
> (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK)  for
>  ; Mon, 4 Sep 2017 21:35:12 -0700
> Received: from BN3PR03CA0055.namprd03.prod.outlook.com (10.167.1.143) by
>  CO2PR03MB2360.namprd03.prod.outlook.com (10.166.93.20) with Microsoft SMTP
>  Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
>  15.20.13.10; Tue, 5 Sep 2017 04:35:11 +
> Received: from BN1AFFO11FD010.protection.gbl (2a01:111:f400:7c10::182) by
>  BN3PR03CA0055.outlook.office365.com (2a01:111:e400:7a4d::15) with Microsoft
>  SMTP Server (version=TLS1_2,
>  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.13.10 via
>  Frontend Transport; Tue, 5 Sep 2017 04:35:10 +
> Authentication-Results: spf=none (sender IP is 209.87.16.33)
>  smtp.mailfrom=ftp-master.debian.org; analog.com; dkim=none (message not
>  signed) header.d=none;analog.com; dmarc=none action=none
>  header.from=ftp-master.debian.org;
> Received-SPF: None (protection.outlook.com: ftp-master.debian.org does not
>  designate permitted sender hosts)
> Received: from muffat.debian.org (209.87.16.33) by
>  BN1AFFO11FD010.mail.protection.outlook.com (10.58.52.70) with Microsoft SMTP
>  Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
>  15.1.1385.11 via Frontend Transport; Tue, 5 Sep 2017 04:35:10 +
> Received: from [138.16.160.17] (helo=fasolo.debian.org) from C=NA,ST=NA,L=Ankh
>  Morpork,O=Debian SMTP,OU=Debian SMTP
>  CA,CN=fasolo.debian.org,EMAIL=hostmas...@fasolo.debian.org (verified)  by
>  muffat.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)  
>   (Exim
>  4.89)  (envelope-from )id 
> 1dp5Zs-0007CU-2h;
>  Tue, 05 Sep 2017 04:35:08 +
> Received: from dak by fasolo.debian.org with local (Exim 4.84_2)
> (envelope-from )id 
> 1dp5Zr-000GDk-3Y; Tue, 05
>  Sep 2017 04:35:07 +
> X-FireEye: Clean
> From: Debian FTP Masters 
> To: "A. Maitland Bottoms" , Paul Cercueil
> 
> X-DAK: dak process-upload
> X-Debian: DAK
> X-Debian-Package: gr-iio
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: gr-iio_0.2.36-1_amd64.changes ACCEPTED into unstable
> Message-ID: 
> Date: Tue, 5 Sep 2017 04:35:07 +
> X-EOPAttributedMessage: 0
> X-EOPTenantAttributedMessage: eaa689b4-8f87-40e0-9c6f-7228de4d754a:0
> X-MS-Office365-Filtering-HT: Tenant
> X-Forefront-Antispam-Report: 
> CIP:209.87.16.33;IPV:NLI;CTRY:CA;EFV:NLI;SFV:NSPM;SFS:(6009001)(8196002)(299032)(428002)(50944005)(199003)(288314003)(54524002)(189002)(7596002)(305945005)(345774005)(23676002)(50466002)(7636002)(42882006)(311042)(90996001)(47776003)(287071)(46656002)(356003)(83832001)(246002)(9686003)(106466001)(575784001)(57986006)(626005)(566031)(83796002)(63266004)(101416001)(189998001)(9746002)(34003)(93136999)(105586002)(9786002)(50986999)(8666007)(1096003)(8676002)(54356999)(2440051);DIR:INB;SFP:;SCL:1;SRVR:CO2PR03MB2360;H:muffat.debian.org;FPR:;SPF:None;PTR:muffat.debian.org;A:1;MX:1;LANG:en;
> X-MS-PublicTrafficType: Email
> X-MS-Office365-Filtering-Correlation-Id: 

Bug#869929: marked as done (partitionmanager depends and build-depends on cruft packages.)

[Debian Bug Tracking System]

Your message dated Tue, 5 Sep 2017 11:10:22 +0200
with message-id <9e196c92-058e-d7af-7de0-2c61502df...@debian.org>
and subject line Fixed in 3.1.0-1
has caused the Debian Bug report #869929,
regarding partitionmanager depends and build-depends on cruft packages.
to be marked as done.

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

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


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

Package: partitionmanager
Severity: serious
Tags: buster sid
Version: 3.0.1-1

Partitionmanager depends and build-depends on libkpmcore4 and libkpmcore4-dev 
respectively. These packages are no longer built by the kpmcore source package 
(they appear to have been replaced by libkpmcore5 and libkpmcore-dev).
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 80736--- End Message ---

Processed: tagging 853718

[Debian Bug Tracking System]

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

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

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

Processed: uim 1:1.8.6+gh20161003.0.d63dadd-5~exp1

[Debian Bug Tracking System]

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

> tags 863664 + fixed-in-experimental
Bug #863664 [uim-gtk2.0] uim-gtk2.0: gtk{2,3}/qt/qt5 IM plugins are not 
multi-arch co-installable
Added tag(s) fixed-in-experimental.
> tags 873739 + fixed-in-experimental
Bug #873739 [uim-anthy] uim-anthy: Package uim-anthy is uninstallable
Added tag(s) fixed-in-experimental.
> tags 873155 + fixed-in-experimental
Bug #873155 [uim-gtk3] [uim-gtk3] Invokes segmentation fault with ibus 
integrated into gnome
Added tag(s) fixed-in-experimental.
> tags 873874 + fixed-in-experimental
Bug #873874 [src:uim] uim FTBFS with libanthy-dev 1:0.3-5
Added tag(s) fixed-in-experimental.
> tags 873123 + fixed-in-experimental
Bug #873123 [uim-xim] uim-xim segfaults with anthy
Added tag(s) fixed-in-experimental.
> tags 731672 = upstream wontfix
Bug #731672 [uim-gtk3] uim-gtk3: uim systray not appearing in gnome shell
Added tag(s) upstream and wontfix; removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#873841: marked as done (opengrm-ngram: Fix mips/mipsel FTBFS by reducing g++ memory usage)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 15:26:06 +
with message-id 
and subject line Bug#873841: fixed in opengrm-ngram 1.3.2-3
has caused the Debian Bug report #873841,
regarding opengrm-ngram: Fix mips/mipsel FTBFS by reducing g++ memory usage
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.)


-- 
873841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opengrm-ngram
Version: 1.3.2-2
Severity: serious
Tags: patch

https://buildd.debian.org/status/package.php?p=opengrm-ngram=sid

...
libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
hist-arc.cc  -fPIC -DPIC -o .libs/hist-arc.o
...
virtual memory exhausted: Cannot allocate memory
Makefile:481: recipe for target 'hist-arc.lo' failed
make[4]: *** [hist-arc.lo] Error 1


Fix:

--- debian/rules.old2017-08-30 11:17:38.431222040 +
+++ debian/rules2017-08-30 11:19:57.964547509 +
@@ -1,5 +1,12 @@
 #!/usr/bin/make -f
 
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
+# reduce g++ memory usage to fix FTBFS
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+export DEB_CXXFLAGS_MAINT_APPEND = --param ggc-min-expand=10
+endif
+
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_CFLAGS_MAINT_APPEND = -Wall
 include /usr/share/dpkg/buildflags.mk



The mips64el FTBFS is unrelated, this is likely caused by the
known gcc-7 breakage on mips64el (#871514).
--- End Message ---
--- Begin Message ---
Source: opengrm-ngram
Source-Version: 1.3.2-3

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

Debian distribution maintenance software
pp.
Giulio Paci  (supplier of updated opengrm-ngram package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Sep 2017 07:05:53 +0200
Source: opengrm-ngram
Binary: libngram-tools libngram-dev libngram2
Architecture: source
Version: 1.3.2-3
Distribution: unstable
Urgency: medium
Maintainer: Giulio Paci 
Changed-By: Giulio Paci 
Description:
 libngram-dev - OpenGRM n-gram Language Modeling toolkit - development files
 libngram-tools - OpenGRM n-gram Language Modeling toolkit
 libngram2  - OpenGRM n-gram Language Modeling toolkit - runtime library
Closes: 873841
Changes:
 opengrm-ngram (1.3.2-3) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Fix mips/mipsel FTBFS by reducing g++ memory usage (Closes: #873841).
 .
   [ Giulio Paci ]
   * Use the mips/mipsel g++ memory usage reduction strategy on sh4.
Checksums-Sha1:
 0e5992b42f503db3f164a4ca547faa924f02c5e8 1844 opengrm-ngram_1.3.2-3.dsc
 56928ae06cb73929774a788082b5f7e3a42ebe49 10180 
opengrm-ngram_1.3.2-3.debian.tar.xz
 b545be36512a8be7c87f1905525bdcd6912d5d70 6566 
opengrm-ngram_1.3.2-3_source.buildinfo
Checksums-Sha256:
 4b8f668ae5e47992efd569804f60b294aca2f40384e4daeafdce2a7032f5b75e 1844 
opengrm-ngram_1.3.2-3.dsc
 a0c923f1b06bdf82d3326dde1f025d6c2b6a02267e0f456b0743ae72dc4610ea 10180 
opengrm-ngram_1.3.2-3.debian.tar.xz
 300af28e0da3d2c6440c57bcf771f3664107e92ac5a37b1eedf90ecc3e6e2a07 6566 
opengrm-ngram_1.3.2-3_source.buildinfo
Files:
 ea4061282cd4215039d80ef2b24dfe2c 1844 science optional 
opengrm-ngram_1.3.2-3.dsc
 c11961782af7ed1565f41d81708aabb0 10180 science optional 
opengrm-ngram_1.3.2-3.debian.tar.xz
 1504ca37947f51ff97dc2af2c02a7a91 6566 science optional 
opengrm-ngram_1.3.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlmurD8ACgkQLDtDb+rG
gQE5bwf6AtDcfT4VLF54ruZR2mVZNUfZu2NdliZrKRZnmPer1mVUiDbs4yrH4zDO
npbeW/IsijV47kSy6e17NKSavpDFAx+4vuX0JFs7pLn13NsxxqGDqWEJEDl645ZN
fpGRqLLdjgAxfHAoeeFQoq1hqiVRdXLKjrUyv5nlP6y3t1enHO29tFWfBoAlOv4Y
J3yu9RRKAPyCxryJiewefdQzNOoBrpdDhjNGa07jgeKxS0iF8HGZ83WWFfnd0Zrg
p1O256xZjnpcKBcupAiaZO4tQFRWtXrA7XMcI5fD6sdYvGmhyQwsCM2hta3dfVu2

Bug#871234: Help needed for #871234 FTBFS with GCC-7: error: type/value mismatch

[Juhani Numminen]

Hi Alex!

Alex Mestiashvili kirjoitti 05.09.2017 klo 14:55:

parameter list for 'template struct std::hash'
  while (pos
I think the problem is we don't want std::hash but GHash::hash and
GHash::GHashEntry::hash.
(Sorry, I haven't looked deeper into how to get the correct 'hash'.)

Cheers,
Juhani

Processed: Re: [Pkg-mailman-hackers] Bug#873505: Acknowledgement (mailman: Runner crashes when processing incoming email)

[Debian Bug Tracking System]

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

> forcemerge 838288 873505
Bug #838288 [mailman] mailman: SpamAssassin module broken in Testing and 
Unstable
Bug #873505 [mailman] mailman: Runner crashes when processing incoming email
Severity set to 'important' from 'grave'
Added tag(s) pending, stretch, and patch.
Merged 838288 873505
> thanks
Stopping processing here.

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

Bug#873505: [Pkg-mailman-hackers] Bug#873505: Acknowledgement (mailman: Runner crashes when processing incoming email)

[Thijs Kinkhorst]

forcemerge 838288 873505
thanks

On Wed, August 30, 2017 00:58, Pete Donnell wrote:
> Apologies, turns out that this is a duplicate of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838288
>
> Applying the patch included there fixed it.

Thanks for the extra confirmation.

I've uploaded a fixed version to unstable, when that yields no problems
I'll prepare a stable update.


Cheers,
Thijs

Bug#874187: marked as done (qtermwidget FTBFS with Qt 5.9: symbol differences)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 15:35:03 +
with message-id 
and subject line Bug#874187: fixed in qtermwidget 0.7.1-5
has caused the Debian Bug report #874187,
regarding qtermwidget FTBFS with Qt 5.9: symbol differences
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.)


-- 
874187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtermwidget
Version: 0.7.1-4
Severity: serious

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

...
   dh_makeshlibs -O--buildsystem=cmake -O--fail-missing
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/libqtermwidget5-0/DEBIAN/symbols doesn't match 
completely debian/libqtermwidget5-0.symbols
--- debian/libqtermwidget5-0.symbols (libqtermwidget5-0_0.7.1-4_amd64)
+++ dpkg-gensymbolsY7a7UW   2018-10-06 15:07:51.983955567 -1200
@@ -115,18 +115,18 @@
  (c++)"Konsole::AutoScrollHandler::~AutoScrollHandler()@Base" 0.6.0
  (c++)"Konsole::BlockArray::BlockArray()@Base" 0.6.0
  (c++)"Konsole::BlockArray::append(Konsole::Block*)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::at(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::at(unsigned int)@Base" 
0.6.0
  (optional|c++)"Konsole::BlockArray::at(unsigned long)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::decreaseBuffer(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::decreaseBuffer(unsigned 
int)@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::decreaseBuffer(unsigned long)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::has(unsigned int) const@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::has(unsigned int) 
const@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::has(unsigned long) const@Base" 0.6.0
  (c++)"Konsole::BlockArray::increaseBuffer()@Base" 0.6.0
  (c++)"Konsole::BlockArray::lastBlock() const@Base" 0.6.0
  (c++)"Konsole::BlockArray::newBlock()@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::setHistorySize(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::setHistorySize(unsigned 
int)@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::setHistorySize(unsigned long)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::setSize(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::setSize(unsigned 
int)@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::setSize(unsigned long)@Base" 0.6.0
  (c++)"Konsole::BlockArray::unmap()@Base" 0.6.0
  (c++)"Konsole::BlockArray::~BlockArray()@Base" 0.6.0
@@ -172,7 +172,7 @@
  (c++)"Konsole::ColorSchemeManager::loadCustomColorScheme(QString 
const&)@Base" 0.6.0
  (c++)"Konsole::ColorSchemeManager::loadKDE3ColorScheme(QString const&)@Base" 
0.6.0
  (c++)"Konsole::ColorSchemeManager::~ColorSchemeManager()@Base" 0.6.0
- (optional|c++)"Konsole::CompactHistoryBlock::allocate(unsigned int)@Base" 
0.6.0
+#MISSING: 0.7.1-4# 
(optional|c++)"Konsole::CompactHistoryBlock::allocate(unsigned int)@Base" 0.6.0
  (optional|c++)"Konsole::CompactHistoryBlock::allocate(unsigned long)@Base" 
0.6.0
  (c++)"Konsole::CompactHistoryBlock::contains(void*)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlock::deallocate()@Base" 0.6.0
@@ -180,7 +180,7 @@
  (c++)"Konsole::CompactHistoryBlock::length()@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlock::remaining()@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlock::~CompactHistoryBlock()@Base" 0.6.0
- (optional|c++)"Konsole::CompactHistoryBlockList::allocate(unsigned int)@Base" 
0.6.0
+#MISSING: 0.7.1-4# 
(optional|c++)"Konsole::CompactHistoryBlockList::allocate(unsigned int)@Base" 
0.6.0
  (optional|c++)"Konsole::CompactHistoryBlockList::allocate(unsigned 
long)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlockList::deallocate(void*)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlockList::~CompactHistoryBlockList()@Base" 0.6.0
@@ -189,7 +189,7 @@
  (c++)"Konsole::CompactHistoryLine::getCharacters(Konsole::Character*, int, 
int)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryLine::getLength() const@Base" 0.6.0
  (c++)"Konsole::CompactHistoryLine::isWrapped() const@Base" 0.6.0
- (optional|c++)"Konsole::CompactHistoryLine::operator new(unsigned int, 
Konsole::CompactHistoryBlockList&)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::CompactHistoryLine::operator 
new(unsigned int, 

Bug#853388: marked as done (libvarconf-1.0-8v5: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 16:20:57 +
with message-id 
and subject line Bug#853388: fixed in varconf 1.0.1-4
has caused the Debian Bug report #853388,
regarding libvarconf-1.0-8v5: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:401:41: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 const std::string& asString() const throw (WrongTypeException)
 ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:407:29: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 std::string& asString() throw (WrongTypeException)
 ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:421:34: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 const MapType& asMap() const throw (WrongTypeException)
  ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:427:22: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 MapType& asMap() throw (WrongTypeException)
  ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:441:36: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 const ListType& asList() const throw (WrongTypeException)
^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:447:24: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 ListType& asList() throw (WrongTypeException)
^
In file included from /usr/include/varconf-1.0/varconf/varconf.h:4:0,
 from ../../src/services/config/ConfigService.h:26,
 from ../../src/main/Application.cpp:32:
/usr/include/varconf-1.0/varconf/config.h:97:52: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
   void parseStream(std::istream & in, Scope scope) throw (ParseError);
^
/bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<>/ember-0.7.2+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/X11R6/include -I/usr/include 
-I/usr/include/AL -I/usr/include/AL -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/Eris-1.3 
-I/usr/include/skstream-0.3 -I/usr/lib/x86_64-linux-gnu/skstream-0.3/include 
-I/usr/include/varconf-1.0 -I/usr/include/Mercator-0.3 
-I/usr/include/Atlas-C++-0.6 -I/usr/include/wfmath-1.0 
-I/usr/include/libwfut-0.2 -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/x86_64-linux-gnu 
-pthread -I/usr/include/OGRE -pthread -I/usr/include/OGRE/Overlay 
-I/usr/include/OGRE -pthread 

Bug#871287: marked as done (libvarconf-1.0-8v5: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 16:20:57 +
with message-id 
and subject line Bug#853388: fixed in varconf 1.0.1-4
has caused the Debian Bug report #853388,
regarding libvarconf-1.0-8v5: 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.)


-- 
853388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvarconf-1.0-8v5
Version: 1.0.1-3
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: varconf
Source-Version: 1.0.1-4

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

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated varconf 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, 02 Sep 2017 22:01:28 -0500
Source: varconf
Binary: libvarconf-1.0-8v5 libvarconf-dev
Architecture: source amd64
Version: 1.0.1-4
Distribution: unstable
Urgency: high
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Description:
 libvarconf-1.0-8v5 - WorldForge configuration file handling library
 libvarconf-dev - WorldForge configuration file handling library - development 
file
Closes: 853388
Changes:
 varconf (1.0.1-4) unstable; urgency=high
 .
   * Update dh compat to 10
   * Update symbols for GCC 7 (Closes: #853388)
   * Update standards to 4.1.0
 - d/control: document new standards version
 - d/copyright: use https in Format field
   * Update d/copyright: new copyright year for debian directory
Checksums-Sha1:
 e5c9f0ed25faad7ebd31fc5dbfacd14c3fef1626 1999 varconf_1.0.1-4.dsc
 0f15b3b299e76f192f97dfbd0e18ba3751910454 244880 varconf_1.0.1.orig.tar.xz
 16328cf153470adb6ddbb156ce55ce16c20435d0 5976 varconf_1.0.1-4.debian.tar.xz
 

Bug#874364: More information

[Iiro Laiho]

I have been wondering ifsome update script could grab the keyboard
layout from a desktop environment where the upgrade is initiated?

I really don't like submitting bug reports with this little data about
reproductivity, but the risk of system becoming unbootable is a big deal
and I felt it was necessary.

Bug#872568: marked as done (rsyslog: FTBFS on mips, mipsel - error: 'pThis' undeclared)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 18:06:51 +
with message-id 
and subject line Bug#872568: fixed in rsyslog 8.29.0-2
has caused the Debian Bug report #872568,
regarding rsyslog: FTBFS on mips, mipsel - error: 'pThis' undeclared
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.)


-- 
872568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rsyslog
Version: 8.29.0-1
Severity: serious
Tags: sid buster patch

Hi,

rsyslog FTBFS on mips, mipsel and various ports architectures with the
error:
> In file included from ../../runtime/prop.h:25:0,
>  from ../../runtime/glbl.h:38,
>  from ../../runtime/stream.h:73,
>  from ../../runtime/obj.h:48,
>  from ../../runtime/rsyslog.h:634,
>  from imptcp.c:61:
> imptcp.c: In function 'AcceptConnReq':
> imptcp.c:831:39: error: 'pThis' undeclared (first use in this function)
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>^
> ../../runtime/atomic.h:206:22: note: in definition of macro 
> 'ATOMIC_INC_uint64'
>pthread_mutex_lock(phlpmut); \
>   ^~~
> imptcp.c:831:2: note: in expansion of macro 'STATSCOUNTER_INC'
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>   ^~~~
> imptcp.c:831:39: note: each undeclared identifier is reported only once for 
> each function it appears in
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>^
> ../../runtime/atomic.h:206:22: note: in definition of macro 
> 'ATOMIC_INC_uint64'
>pthread_mutex_lock(phlpmut); \
>   ^~~
> imptcp.c:831:2: note: in expansion of macro 'STATSCOUNTER_INC'
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>   ^~~~

As the error suggests, pThis is not declared in that function. The code
is only used on architectures which do not have 64-bit atomics which is
why it only fails on some architectures.

There is an upstream pull request to fix this:
https://github.com/rsyslog/rsyslog/pull/1725

I've also attached the patch from that PR which should fix this.

Thanks,
James
From 2ea84c47b208214370034500f0aab19fe93cce7f Mon Sep 17 00:00:00 2001
From: Pete Nelson 
Date: Wed, 16 Aug 2017 17:19:33 -0400
Subject: [PATCH] correct paste oversight on mutex arg

Remove the 'pThis->' from the second argument to STATSCOUNTER_INC macro.
This only affects architectures without atomic uint64 actions, like aarm64.
Others do not use the mut argument, and it gets compiled out.
---
 plugins/imptcp/imptcp.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/plugins/imptcp/imptcp.c b/plugins/imptcp/imptcp.c
index c373c17e6..ab2a17e5b 100644
--- a/plugins/imptcp/imptcp.c
+++ b/plugins/imptcp/imptcp.c
@@ -828,7 +828,7 @@ AcceptConnReq(ptcplstn_t *pLstn, int *newSock, prop_t **peerName, prop_t **peerI
 		LogMsg(0, RS_RET_NO_ERRCODE, LOG_INFO, "imptcp: connection established with host: %s", propGetSzStr(*peerName));
 	}
 
-	STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
+	STATSCOUNTER_INC(pLstn->ctrSessOpen, pLstn->mutCtrSessOpen);
 	*newSock = iNewSock;
 
 finalize_it:
@@ -837,7 +837,7 @@ AcceptConnReq(ptcplstn_t *pLstn, int *newSock, prop_t **peerName, prop_t **peerI
 		if(iRet != RS_RET_NO_MORE_DATA && pLstn->pSrv->bEmitMsgOnOpen) {
 			LogError(0, NO_ERRCODE, "imptcp: connection could not be established with host: %s", propGetSzStr(*peerName));
 		}
-		STATSCOUNTER_INC(pLstn->ctrSessOpenErr, pThis->pLstn->mutCtrSessOpenErr);
+		STATSCOUNTER_INC(pLstn->ctrSessOpenErr, pLstn->mutCtrSessOpenErr);
 		/* the close may be redundant, but that doesn't hurt... */
 		if(iNewSock != -1)
 			close(iNewSock);


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rsyslog
Source-Version: 8.29.0-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of 

Bug#874185: marked as done (_solve_toeplitz.x86_64-linux-gnu.so: undefinedsymbol: PyFPE_jbuf)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 18:35:59 +
with message-id 
and subject line Bug#873791: fixed in python2.7 2.7.14~rc1-3
has caused the Debian Bug report #873791,
regarding _solve_toeplitz.x86_64-linux-gnu.so: undefinedsymbol: PyFPE_jbuf
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.)


-- 
873791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-scipy
Version: 0.18.1-2+b2
Severity: serious

The linalg submodule currently cannot be loaded in sid:

$ python -c "from scipy import linalg"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/__init__.py", line 175, 
in 
from .basic import *
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/basic.py", line 21, in 

from ._solve_toeplitz import levinson
ImportError: 
/usr/lib/python2.7/dist-packages/scipy/linalg/_solve_toeplitz.x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf

This issue seems related to #873791.

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python2.7
Source-Version: 2.7.14~rc1-3

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python2.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: Tue, 05 Sep 2017 20:16:23 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal 
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev 
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg 
libpython2.7-dbg
Architecture: source
Version: 2.7.14~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python2.7 - IDE for Python (v2.7) using Tkinter
 libpython2.7 - Shared Python runtime library (version 2.7)
 libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 libpython2.7-dev - Header files and a static library for Python (v2.7)
 libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
 libpython2.7-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
 python2.7  - Interactive high-level object-oriented language (version 2.7)
 python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 python2.7-dev - Header files and a static library for Python (v2.7)
 python2.7-doc - Documentation for the high-level object-oriented language 
Python
 python2.7-examples - Examples for the Python language (v2.7)
 python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 873791 873899 873915
Changes:
 python2.7 (2.7.14~rc1-3) unstable; urgency=medium
 .
   * Add package breaks for extensions referencing symbols for the removed
 _PyFPE module. Closes: #873791, #873915, #873899.
   * Expect the regrtest test to fail on s390x.
Checksums-Sha1:
 e04173f3f66974abb283f3af5b50785aece66ddc 3395 python2.7_2.7.14~rc1-3.dsc
 7db6dfeb1c409091664c71ba403c52f04991f71c 286110 python2.7_2.7.14~rc1-3.diff.gz
 0f6b7cc0177c2b37eff78e0daf1fc9382096fb14 9585 
python2.7_2.7.14~rc1-3_source.buildinfo
Checksums-Sha256:
 b4033855155abf0255bffb955b06ef0b305dea067a94fae0259c79f24a06d28c 3395 
python2.7_2.7.14~rc1-3.dsc
 a503fd9621b55a00cbcf7e79fd60f005a7b53ba490d7afdc7aaf81983f8b8770 286110 
python2.7_2.7.14~rc1-3.diff.gz
 7cc05c47ec0d8212646ac4c10ca73f45d357c9af9072162911617442dc3b6e95 9585 
python2.7_2.7.14~rc1-3_source.buildinfo
Files:
 81f1a9d8e020db7a0b7ae16605a406d3 3395 python optional 
python2.7_2.7.14~rc1-3.dsc
 5ac5302b7dfe91ab21c8eddc68ac937f 286110 python optional 
python2.7_2.7.14~rc1-3.diff.gz
 

Bug#874272: marked as done (new version breaks xpra, PyFPE_jbuf missing)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 18:35:59 +
with message-id 
and subject line Bug#873791: fixed in python2.7 2.7.14~rc1-3
has caused the Debian Bug report #873791,
regarding new version breaks xpra, PyFPE_jbuf missing
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.)


-- 
873791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-numpy
Version: 1:1.12.1-3+b2
Severity: important

Hi,

after upgrading python and python-numpy, the xpra server won't start any
more:

xpra main error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 126, in 
main
return run_mode(script_file, err, options, args, mode, defaults)
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 1008, in 
run_mode
return run_server(error_cb, options, mode, script_file, args, 
current_display)
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/server.py", line 1207, in 
run_server
from xpra.x11.gtk2.wm import wm_check
  File "/usr/lib/python2.7/dist-packages/xpra/x11/gtk2/wm.py", line 25, in 

from xpra.x11.bindings.keyboard_bindings import X11KeyboardBindings 
#@UnresolvedImport
ImportError: 
/usr/lib/python2.7/dist-packages/xpra/x11/bindings/keyboard_bindings.x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf

Downgrading python-numpy and python to the versions listed below makes
xpra run again.

Since googling for PyFPE_jbuf brings up references to python-numpy, I am
filing this against python-numpy. Please reassign if appropriate, and
also handle the (probably deflated) severity of this bug report.

Greetings
Marc



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

Kernel: Linux 4.12.9-zgws1 (SMP w/6 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-numpy depends on:
ii  libblas3 [libblas.so.3]  3.7.1-1
ii  libc62.24-15
ii  liblapack3 [liblapack.so.3]  3.7.1-1
ii  python   2.7.13-2
ii  python2.72.7.13-4

python-numpy recommends no packages.

Versions of packages python-numpy suggests:
ii  gcc   4:7.1.0-2
pn  gfortran  
pn  python-dev
pn  python-nose   
pn  python-numpy-dbg  
pn  python-numpy-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python2.7
Source-Version: 2.7.14~rc1-3

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python2.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: Tue, 05 Sep 2017 20:16:23 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal 
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev 
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg 
libpython2.7-dbg
Architecture: source
Version: 2.7.14~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python2.7 - IDE for Python (v2.7) using Tkinter
 libpython2.7 - Shared Python runtime library (version 2.7)
 libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 libpython2.7-dev - Header files and a static library for Python (v2.7)
 libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
 libpython2.7-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
 python2.7  - Interactive high-level object-oriented language (version 2.7)
 python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 

Bug#874210: marked as done ([python-tk] Missing function, breaks python game)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 18:35:59 +
with message-id 
and subject line Bug#873791: fixed in python2.7 2.7.14~rc1-3
has caused the Debian Bug report #873791,
regarding [python-tk] Missing function, breaks python game
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.)


-- 
873791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tk
Version: 2.7.13-1
Severity: critical

--- Please enter the report below this line. ---
Running the game pysolfc, get the following traceback:
~$ pysolfc 
Traceback (most recent call last):
  File "/usr/games/pysolfc", line 26, in 
init()
  File "/usr/share/games/pysolfc/pysollib/init.py", line 119, in init
import Tkinter
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 42, in 
raise ImportError, str(msg) + ', please install the python-tk package'
ImportError: /usr/lib/python2.7/lib-dynload/_tkinter.so: undefined symbol: 
PyFPE_jbuf, please install the python-tk package

Package in installed, most recent Sid.

--- System information. ---
Architecture: 
Kernel:   Linux 4.11.0-1-amd64

Debian Release: buster/sid
  500 yakkety ppa.launchpad.net 
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
  100 jessie-backports ftp.us.debian.org 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-
python  (>= 2.7) | 2.7.13-2
python  (<< 2.8) | 2.7.13-2
blt  (>= 2.4z-9) | 2.5.3+dfsg-3
libc6   (>= 2.4) | 
libtcl8.6 (>= 8.6.0) | 
libtk8.6  (>= 8.6.0) | 
libx11-6 | 
tk8.6-blt2.5  (>= 2.5.3) | 


Package's Recommends field is empty.

Suggests   (Version) | Installed
-+-===
tix  | 
python-tk-dbg| 
--- End Message ---
--- Begin Message ---
Source: python2.7
Source-Version: 2.7.14~rc1-3

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python2.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: Tue, 05 Sep 2017 20:16:23 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal 
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev 
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg 
libpython2.7-dbg
Architecture: source
Version: 2.7.14~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python2.7 - IDE for Python (v2.7) using Tkinter
 libpython2.7 - Shared Python runtime library (version 2.7)
 libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 libpython2.7-dev - Header files and a static library for Python (v2.7)
 libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
 libpython2.7-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
 python2.7  - Interactive high-level object-oriented language (version 2.7)
 python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 python2.7-dev - Header files and a static library for Python (v2.7)
 python2.7-doc - Documentation for the high-level object-oriented language 
Python
 python2.7-examples - Examples for the Python language (v2.7)
 python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 873791 873899 873915
Changes:
 python2.7 (2.7.14~rc1-3) unstable; urgency=medium
 .
   * Add package breaks for extensions referencing symbols for the removed
 _PyFPE module. Closes: #873791, #873915, #873899.
   * 

Bug#873791: marked as done (python2.7: fpectl extension removal broke the ABI for C extensions)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 18:35:59 +
with message-id 
and subject line Bug#873791: fixed in python2.7 2.7.14~rc1-3
has caused the Debian Bug report #873791,
regarding python2.7: fpectl extension removal broke the ABI for C extensions
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.)


-- 
873791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-numpy
Version: 1.12.1-3+b2
Severity: serious
Affects: src:casacore

On several platforms, numpy cannot be loaded successfully due to missing
symbols:

import numpy as NUM;
  File "/usr/lib/python2.7/dist-packages/numpy/__init__.py", line 166,
in 
from . import random
  File "/usr/lib/python2.7/dist-packages/numpy/random/__init__.py", line
99, in 
from .mtrand import *
ImportError:
/usr/lib/python2.7/dist-packages/numpy/random/mtrand.aarch64-linux-gnu.so:
undefined symbol: PyFPE_jbuf


The symbol that is reported as undefined varies between the platforms:

* arm64, s390x, alpha, hurd-i386: PyFPE_jbuf
* mips, mipsel, ppc64el, powerpc, ppc64: PyFPE_counter

These errors cause FTBFS for the "casacore" package:

https://buildd.debian.org/status/logs.php?pkg=casacore=2.3.0-4

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: python2.7
Source-Version: 2.7.14~rc1-3

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python2.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: Tue, 05 Sep 2017 20:16:23 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal 
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev 
libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg 
libpython2.7-dbg
Architecture: source
Version: 2.7.14~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python2.7 - IDE for Python (v2.7) using Tkinter
 libpython2.7 - Shared Python runtime library (version 2.7)
 libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 libpython2.7-dev - Header files and a static library for Python (v2.7)
 libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
 libpython2.7-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython2.7-testsuite - Testsuite for the Python standard library (v2.7)
 python2.7  - Interactive high-level object-oriented language (version 2.7)
 python2.7-dbg - Debug Build of the Python Interpreter (version 2.7)
 python2.7-dev - Header files and a static library for Python (v2.7)
 python2.7-doc - Documentation for the high-level object-oriented language 
Python
 python2.7-examples - Examples for the Python language (v2.7)
 python2.7-minimal - Minimal subset of the Python language (version 2.7)
Closes: 873791 873899 873915
Changes:
 python2.7 (2.7.14~rc1-3) unstable; urgency=medium
 .
   * Add package breaks for extensions referencing symbols for the removed
 _PyFPE module. Closes: #873791, #873915, #873899.
   * Expect the regrtest test to fail on s390x.
Checksums-Sha1:
 e04173f3f66974abb283f3af5b50785aece66ddc 3395 python2.7_2.7.14~rc1-3.dsc
 7db6dfeb1c409091664c71ba403c52f04991f71c 286110 python2.7_2.7.14~rc1-3.diff.gz
 0f6b7cc0177c2b37eff78e0daf1fc9382096fb14 9585 
python2.7_2.7.14~rc1-3_source.buildinfo
Checksums-Sha256:
 b4033855155abf0255bffb955b06ef0b305dea067a94fae0259c79f24a06d28c 3395 
python2.7_2.7.14~rc1-3.dsc
 a503fd9621b55a00cbcf7e79fd60f005a7b53ba490d7afdc7aaf81983f8b8770 286110 
python2.7_2.7.14~rc1-3.diff.gz
 7cc05c47ec0d8212646ac4c10ca73f45d357c9af9072162911617442dc3b6e95 9585 
python2.7_2.7.14~rc1-3_source.buildinfo
Files:
 81f1a9d8e020db7a0b7ae16605a406d3 3395 python optional 
python2.7_2.7.14~rc1-3.dsc
 5ac5302b7dfe91ab21c8eddc68ac937f 286110 python optional 

Bug#784475: Done some work but crash before main()

[Bastien ROUCARIES]

Hi,

I have done porting work but now it fail before main():

*** Error in 
`/home/bastien/Documents/Personnel/soft/debian/kbibtex/kbibtex/obj-x86_64-linux-gnu/src/program/kbibtex':
realloc(): invalid pointer: 0x559b5f549500 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fbba63b6bfb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fbba63bcfc6]
/lib/x86_64-linux-gnu/libc.so.6(realloc+0x219)[0x7fbba63c17d9]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN9QListData12realloc_growEi+0x31)[0x7fbb9e1b2211]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN9QListData6appendEi+0x4f)[0x7fbb9e1b22af]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x1cc378)[0x7fbb9e277378]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_Z21qRegisterResourceDataiPKhS0_S0_+0x38d)[0x7fbb9e272b2d]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x7d533)[0x7fbb9e128533]
/lib64/ld-linux-x86-64.so.2(+0xf89a)[0x7fbbaa27489a]
/lib64/ld-linux-x86-64.so.2(+0xf9ab)[0x7fbbaa2749ab]
/lib64/ld-linux-x86-64.so.2(+0xc5a)[0x7fbbaa265c5a]
=== Memory map: 
559b5f2e7000-559b5f345000 r-xp  00:2c 9432217
  
/home/bastien/Documents/Personnel/soft/debian/kbibtex/kbibtex/obj-x86_64-linux-gnu/src/program/kbibtex
559b5f544000-559b5f548000 r--p 0005d000 00:2c 9432217
  
/home/bastien/Documents/Personnel/soft/debian/kbibtex/kbibtex/obj-x86_64-linux-gnu/src/program/kbibtex
559b5f548000-559b5f54a000 rw-p 00061000 00:2c 9432217
  
/home/bastien/Documents/Personnel/soft/debian/kbibtex/kbibtex/obj-x86_64-linux-gnu/src/program/kbibtex
559b5f54a000-559b5f54b000 rw-p  00:00 0
559b601f8000-559b60219000 rw-p  00:00 0  [heap]
7fbb9000-7fbb90021000 rw-p  00:00 0
7fbb90021000-7fbb9400 ---p  00:00 0
7fbb96b6e000-7fbb96b82000 r-xp  00:25 18223187
  /lib/x86_64-linux-gnu/libgpg-error.so.0.22.0
7fbb96b82000-7fbb96d81000 ---p 00014000 00:25 18223187
  /lib/x86_64-linux-gnu/libgpg-error.so.0.22.0
7fbb96d81000-7fbb96d82000 r--p 00013000 00:25 18223187
  /lib/x86_64-linux-gnu/libgpg-error.so.0.22.0
7fbb96d82000-7fbb96d83000 rw-p 00014000 00:25 18223187
  /lib/x86_64-linux-gnu/libgpg-error.so.0.22.0
7fbb96d83000-7fbb96dae000 r-xp  00:25 18226505
  /usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
7fbb96dae000-7fbb96fad000 ---p 0002b000 00:25 18226505
  /usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
7fbb96fad000-7fbb96faf000 r--p 0002a000 00:25 18226505
  /usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
7fbb96faf000-7fbb96fb rw-p 0002c000 00:25 18226505
  /usr/lib/x86_64-linux-gnu/libgraphite2.so.3.0.1
7fbb96fb-7fbb96fc r-xp  00:25 20304808
  /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0
7fbb96fc-7fbb971bf000 ---p 0001 00:25 20304808
  /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0
7fbb971bf000-7fbb971c r--p f000 00:25 20304808
  /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0
7fbb971c-7fbb971c1000 rw-p 0001 00:25 20304808
  /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0
7fbb971c1000-7fbb971c6000 r-xp  00:25 16672579
  /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0
7fbb971c6000-7fbb973c5000 ---p 5000 00:25 16672579
  /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0
7fbb973c5000-7fbb973c6000 r--p 4000 00:25 16672579
  /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0
7fbb973c6000-7fbb973c7000 rw-p 5000 00:25 16672579
  /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0
7fbb973c7000-7fbb973cb000 r-xp  00:25 13200896
  /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0
7fbb973cb000-7fbb975ca000 ---p 4000 00:25 13200896
  /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0
7fbb975ca000-7fbb975cb000 r--p 3000 00:25 13200896
  /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0
7fbb975cb000-7fbb975cc000 rw-p 4000 00:25 13200896
  /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0
7fbb975cc000-7fbb975e4000 r-xp  00:25 13214250
  /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7fbb975e4000-7fbb977e4000 ---p 00018000 00:25 13214250
  /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7fbb977e4000-7fbb977e6000 r--p 00018000 00:25 13214250
  /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7fbb977e6000-7fbb977e7000 rw-p 0001a000 00:25 13214250
  /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7fbb977e7000-7fbb977e8000 r-xp  00:25 15688696
  /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0
7fbb977e8000-7fbb979e7000 ---p 1000 00:25 15688696
  /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0
7fbb979e7000-7fbb979e8000 r--p  00:25 15688696
  /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0
7fbb979e8000-7fbb979e9000 rw-p 1000 00:25 15688696
  /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0
7fbb979e9000-7fbb979eb000 r-xp  00:25 21156571
  /usr/lib/x86_64-linux-gnu/libXdamage.so.1.1.0
7fbb979eb000-7fbb97bea000 ---p 2000 00:25 21156571
  /usr/lib/x86_64-linux-gnu/libXdamage.so.1.1.0
7fbb97bea000-7fbb97beb000 r--p 1000 00:25 21156571
  /usr/lib/x86_64-linux-gnu/libXdamage.so.1.1.0
7fbb97beb000-7fbb97bec000 rw-p 2000 00:25 21156571
  

Bug#873654: python-py-zipkin: Incomplete debian/copyright?

[Ben Plotnick]

Hi Chris,

On Tue, 29 Aug 2017 20:24:55 +0100 Chris Lamb  wrote:
> Source: python-py-zipkin
> Version: 0.9.0-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Olivier Sallou 
>
> Hi,
>
> I just ACCEPTed python-py-zipkin from NEW but noticed it was missing
> attribution in debian/copyright for at least Twitter, Inc.
I don't understand this. What needs to be attributed to Twitter, Inc.?

The py_zipkin copyright is owned by Yelp, Inc, and the Zipkin code
(which is not contained in py_zipkin) is now owned by The OpenZipkin
Authors.

>
> (This is not exhaustive so please check over the entire package
> carefully and address these on your next upload.)
>
>
> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>
>

Thanks,
Ben Plotnick

Bug#874202: marked as done ([borgbackup] undefined symbol: PyFPE_jbuf in crypto.cpython-35m-x86_64-linux-gnu.so)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding [borgbackup] undefined symbol: PyFPE_jbuf in 
crypto.cpython-35m-x86_64-linux-gnu.so
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.)


-- 
873921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgbackup
Version: 1.0.11-3
Severity: grave

--- Please enter the report below this line. ---
Hi,
I have the following python stacktrace:
# borg
Traceback (most recent call last):
  File "/usr/bin/borg", line 11, in 
    load_entry_point('borgbackup==1.0.11', 'console_scripts', 'borg')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
564, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2662, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2316, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2322, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 22, in

    from .helpers import Error, location_validator,
archivename_validator, format_line, format_time, format_file_size, \
  File "/usr/lib/python3/dist-packages/borg/helpers.py", line 35, in

    from . import crypto
ImportError:
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-x86_64-linux-gnu.so:
undefined symbol: PyFPE_jbuf

I cannot use borg at the moment. However, I don't understand why, since
it is already installed on another server (though using the testing
channel), and it didn't have the issue.

Thanks for the help,
Adrien

--- System information. ---
Architecture:
Kernel: Linux 4.12.0-1-amd64

Debian Release: buster/sid
500 unstable ftp.fr.debian.org
500 testing download.jitsi.org
1 experimental ftp.fr.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-==
fuse | 2.9.7-1
python3-llfuse (<< 2.0) | 1.2+dfsg-1+b1
python3-msgpack (>= 0.4.6~) | 0.4.8-1+b1
python3-pkg-resources | 36.2.7-2
python3 (<< 3.6) | 3.5.3-3
python3 (>= 3.5~) | 3.5.3-3
python3:any (>= 3.3.2-2~) |
libacl1 (>= 2.2.51-8) | 2.2.52-3+b1
libc6 (>= 2.14) | 2.24-17
liblz4-1 (>= 0.0~r114) | 0.0~r131-2+b1
libssl1.1 (>= 1.1.0) | 1.1.0f-5


Package's Recommends field is empty.

Suggests (Version) | Installed
=-+-===
borgbackup-doc |
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.5-testsuite - Testsuite for the Python standard library 

Bug#874253: marked as done (Needs rebuild due to PyFPE)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding Needs rebuild due to PyFPE
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.)


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

Package: python3-pandas-lib
Version: 0.20.3-1
Severity: important

python stopped building the fpectl extension, which results in this:

ImportError: C extension: 
/usr/lib/python3/dist-packages/pandas/_libs/tslib.cpython-35m-x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf not built. If you want to import pandas from the 
source directory, you may need to run 'python setup.py build_ext --inplace 
--force' to build the C extensions first.

The python package added some Breaks against numpy, however it seems that
pandas-lib was skipped.

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

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

Versions of packages python3-pandas-lib depends on:
ii  libc6   2.24-17
ii  libgcc1 1:7.2.0-3
ii  libstdc++6  7.2.0-3
ii  python3 3.5.3-3
ii  python3-numpy [python3-numpy-abi9]  1:1.12.1-3.2

python3-pandas-lib recommends no packages.

python3-pandas-lib suggests no packages.
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.5-testsuite - Testsuite for the Python standard library (v3.5)
 python3.5  - Interactive high-level object-oriented language (version 3.5)
 python3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 python3.5-dev - Header files and a static library for Python (v3.5)
 python3.5-doc - Documentation for the high-level object-oriented language 
Python
 python3.5-examples - Examples for the Python language (v3.5)
 python3.5-minimal - Minimal subset of the Python language (version 3.5)
 python3.5-venv - Interactive high-level object-oriented language (pyvenv 
binary, v
Closes: 873921
Changes:
 python3.5 (3.5.4-4) unstable; urgency=medium
 .
   * Add package breaks for extensions referencing symbols for the removed
 _PyFPE module. Closes: #873921.
Checksums-Sha1:
 c63ec384041697d5d674a65905415d1fe042a8d3 3367 python3.5_3.5.4-4.dsc
 debea0efe6a112c377300e39bf462a7ae198e94d 235636 python3.5_3.5.4-4.debian.tar.xz
 170fc44934fe1e96f95ac8f4d9eade82422de48c 9353 
python3.5_3.5.4-4_source.buildinfo
Checksums-Sha256:
 

Bug#873921: marked as done (python3.5_3.5.4-3 breaks borgbackup: undefined symbol: PyFPE_jbuf)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding python3.5_3.5.4-3 breaks borgbackup: undefined symbol: PyFPE_jbuf
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.)


-- 
873921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgbackup
Version: 1.0.11-3
Severity: grave

Hi!

I am reporting this bug against borgbackup, because I am not sure if the
bug is in python3.5 or borgbackup just needs to be binNMUd. Please
reassign as you see fit.

The upload of python3.5 (3.5.4-3) disables the fpectl extension and
breaks borgbackup:

$ borg
Traceback (most recent call last):
  File "/usr/bin/borg", line 11, in 
load_entry_point('borgbackup==1.0.11', 'console_scripts', 'borg')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 564, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2662, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2316, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2322, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 22, in 
from .helpers import Error, location_validator, archivename_validator, 
format_line, format_time, format_file_size, \
  File "/usr/lib/python3/dist-packages/borg/helpers.py", line 35, in 
from . import crypto
ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-i386-linux-gnu.so: 
undefined symbol: PyFPE_jbuf

Grüße,
Sven.

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

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

Versions of packages borgbackup depends on:
ii  fuse   2.9.7-1
ii  libacl12.2.52-3+b1
ii  libc6  2.24-17
ii  liblz4-1   0.0~r131-2+b1
pn  libssl1.1  
ii  python33.5.3-3
ii  python3-llfuse 1.2+dfsg-1+b1
ii  python3-msgpack0.4.8-1+b1
ii  python3-pkg-resources  36.2.7-2

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language 

Bug#873941: marked as done (ImportError: undefined symbol: PyFPE_jbuf on some modules)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding ImportError: undefined symbol: PyFPE_jbuf on some modules
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.)


-- 
873921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3.5
Version: 3.5.4-3
Severity: normal

Hi,

I upgraded today to python3.5=3.5.4-3, and some modules can no more be
imported, causing the subject-given exception.

As an example, importing SFML on the interpretor:

seth@fadreils: ~$ python3
Python 3.5.4 (default, Aug 31 2017, 12:22:39)
[GCC 7.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

~~~> import sfml
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/sfml/__init__.py", line 3, in 
import sfml.graphics
ImportError: /usr/lib/python3/dist-
packages/sfml/graphics.cpython-35m-x86_64-linux-gnu.so: undefined symbol:
PyFPE_jbuf
~~~>

I have the same problem with some home-made python modules compiled to .so
using cython3 (but import the .py source file instead works perfectly).

I tried to downgrade to the 3.5.4-2 version of the package, which immediatly
solved the problem. Going back to the newest version make it immediatly
reappear.



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

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

Versions of packages python3.5 depends on:
ii  libpython3.5-stdlib  3.5.4-3
ii  mime-support 3.60
ii  python3.5-minimal3.5.4-3

python3.5 recommends no packages.

Versions of packages python3.5 suggests:
ii  binutils2.29-8
pn  python3.5-doc   
pn  python3.5-venv  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.5-testsuite - Testsuite for the Python standard library (v3.5)
 python3.5  - Interactive high-level object-oriented language (version 3.5)
 python3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 python3.5-dev - Header files and a static library for Python (v3.5)
 python3.5-doc - Documentation for the high-level object-oriented language 
Python
 python3.5-examples - Examples for the Python language (v3.5)
 python3.5-minimal - Minimal subset of the Python language (version 3.5)
 python3.5-venv - Interactive high-level object-oriented language (pyvenv 
binary, v
Closes: 873921
Changes:
 python3.5 (3.5.4-4) unstable; urgency=medium
 

Bug#874267: marked as done (borgbackup: exits immediately with an ImportError)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding borgbackup: exits immediately with an ImportError
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.)


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

Borg comands exit immediately with the following traceback:

user@host % borg
Traceback (most recent call last):
  File "/usr/bin/borg", line 11, in 
load_entry_point('borgbackup==1.0.11', 'console_scripts', 'borg')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 564, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2662, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2316, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2322, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 22, in 
from .helpers import Error, location_validator, archivename_validator, 
format_line, format_time, format_file_size, \
  File "/usr/lib/python3/dist-packages/borg/helpers.py", line 35, in 
from . import crypto
ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-x86_64-linux-gnu.so: 
undefined symbol: PyFPE_jbuf

<3,
taziden

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

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

Versions of packages borgbackup depends on:
ii  fuse   2.9.7-1
ii  libacl12.2.52-3+b1
ii  libc6  2.24-17
ii  liblz4-1   0.0~r131-2+b1
ii  libssl1.1  1.1.0f-5
ii  python33.5.3-3
ii  python3-llfuse 1.2+dfsg-1+b1
ii  python3-msgpack0.4.8-1+b1
ii  python3-pkg-resources  36.2.7-2

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.5-testsuite - Testsuite for the Python standard library (v3.5)
 python3.5  - Interactive high-level object-oriented language 

Bug#874081: marked as done (borgbackup: Won't start: ImportError: /usr/lib/python3/dist-packages/borg/crypto.cpython-35m-x86_64-linux-gnu.so: undefined symbol: PyFPE_jbuf)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding borgbackup: Won't start: ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-x86_64-linux-gnu.so: 
undefined symbol: PyFPE_jbuf
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.)


-- 
873921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgbackup
Version: 1.0.11-3
Severity: normal

Merely starting borg after upgrading to python3.5 3.5.4-3 fails:


$ borg
Traceback (most recent call last):
  File "/usr/bin/borg", line 11, in 
load_entry_point('borgbackup==1.0.11', 'console_scripts', 'borg')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 564, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2662, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2316, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2322, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 22, in 
from .helpers import Error, location_validator, archivename_validator, 
format_line, format_time, format_file_size, \
  File "/usr/lib/python3/dist-packages/borg/helpers.py", line 35, in 
from . import crypto
ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-x86_64-linux-gnu.so: 
undefined symbol: PyFPE_jbuf


I believe this is related to this change in python3.5:


python3.5 (3.5.4-3) unstable; urgency=medium

  * Stop building the fpectl extension.
  * Break python3-numpy (<< 1:1.12.1-3.1), referencing the now missing fpectl
modules. Addresses: #873791.

 -- Matthias Klose   Thu, 31 Aug 2017 14:22:39 +0200


There is a mail on debian-python about this change, expecting possible
breakage:

   https://lists.debian.org/debian-python/2017/09/msg0.html

Sami


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

Kernel: Linux 4.12.7 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.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 borgbackup depends on:
ii  fuse   2.9.7-1
ii  libacl12.2.52-3+b1
ii  libc6  2.24-17
ii  liblz4-1   0.0~r131-2+b1
ii  libssl1.1  1.1.0f-5
ii  python33.5.3-3
ii  python3-llfuse 1.2+dfsg-1+b1
ii  python3-msgpack0.4.8-1+b1
ii  python3-pkg-resources  36.2.7-2

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg 

Bug#874180: marked as done (python3-tk: undefined symbol in _tkinter.cpython-35m-x86_64-linux-gnu.so)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding python3-tk: undefined symbol in 
_tkinter.cpython-35m-x86_64-linux-gnu.so
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.)


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

Dear Maintainer,

After updating my system, python3-tk stopped functionning:

>>> import _tkinter
Traceback (most recent call last):
  File "", line 1, in 
ImportError: 
/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so: 
undefined symbol: PyFPE_jbuf

Here is the output of ldd:

$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libpython3.5m.so ldd -r 
/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so 
linux-vdso.so.1 (0x7ffd1fdfe000)
/usr/lib/x86_64-linux-gnu/libpython3.5m.so (0x7fca1211f000)
libBLT.2.5.so.8.6 => /usr/lib/libBLT.2.5.so.8.6 (0x7fca11db)
libtk8.6.so => /usr/lib/x86_64-linux-gnu/libtk8.6.so (0x7fca11a52000)
libtcl8.6.so => /usr/lib/x86_64-linux-gnu/libtcl8.6.so (0x7fca1169b000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fca1135b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fca1113e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fca10da1000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x7fca10b76000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fca1095c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fca10758000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fca10555000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fca10251000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7fca1003a000)
libXft.so.2 => /usr/lib/x86_64-linux-gnu/libXft.so.2 (0x7fca0fe24000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7fca0fbe)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7fca0f92b000)
libXss.so.1 => /usr/lib/x86_64-linux-gnu/libXss.so.1 (0x7fca0f728000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7fca0f516000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7fca0f2ee000)
/lib64/ld-linux-x86-64.so.2 (0x7fca129b)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 
(0x7fca0f0e4000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7fca0eeb1000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x7fca0ecad000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x7fca0eaa7000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7fca0e892000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fca0e68a000)
  undefined symbol: 
PyFPE_jbuf(/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so)
  undefined symbol: 
PyFPE_counter(/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so)

Philippe

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/6 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 python3-tk depends on:
ii  blt   2.5.3+dfsg-3
ii  libc6 2.24-17
ii  libtcl8.6 8.6.7+dfsg-1
ii  libtk8.6  8.6.7-1
ii  libx11-6  2:1.6.4-3
ii  python3   3.5.3-3
ii  tk8.6-blt2.5  2.5.3+dfsg-3

python3-tk recommends no packages.

Versions of packages python3-tk suggests:
pn  python3-tk-dbg  
pn  tix 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

We believe that the bug you reported is fixed in the latest version of
python3.5, 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 873...@bugs.debian.org,
and the maintainer will reopen 

Bug#874258: marked as done (Requires rebuild due to pyfpe ABI change)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 19:06:54 +
with message-id 
and subject line Bug#873921: fixed in python3.5 3.5.4-4
has caused the Debian Bug report #873921,
regarding Requires rebuild due to pyfpe ABI change
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.)


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

Package: python3-scipy
Version: 0.18.1-2+b2
Severity: important

python3 stopped building the fpectl module, requiring a rebuild of the affected 
modules.
scipy.linalg is affected:


import scipy
import scipy.linalg

Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/scipy/linalg/__init__.py", line 175, in 

   from .basic import *
 File "/usr/lib/python3/dist-packages/scipy/linalg/basic.py", line 21, in 

   from ._solve_toeplitz import levinson
ImportError: 
/usr/lib/python3/dist-packages/scipy/linalg/_solve_toeplitz.cpython-35m-x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf

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

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

Versions of packages python3-scipy depends on:
ii  libblas3 [libblas.so.3] 3.7.1-1+b1
ii  libc6   2.24-17
ii  libgcc1 1:7.2.0-3
ii  libgfortran47.2.0-3
ii  liblapack3 [liblapack.so.3] 3.7.1-1+b1
ii  libopenblas-base [liblapack.so.3]   0.2.20+ds-2+b1
ii  libquadmath07.2.0-3
ii  libstdc++6  7.2.0-3
ii  python3 3.5.3-3
ii  python3-decorator   4.1.1-1
ii  python3-numpy [python3-numpy-abi9]  1:1.12.1-3.2

Versions of packages python3-scipy recommends:
ii  g++ [c++-compiler]4:7.1.0-2
ii  g++-7 [c++-compiler]  7.2.0-3

Versions of packages python3-scipy suggests:
ii  python-scipy-doc  0.18.1-2
--- End Message ---
--- Begin Message ---
Source: python3.5
Source-Version: 3.5.4-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.5 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, 05 Sep 2017 20:32:10 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal 
libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev 
libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc 
python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.5-testsuite - Testsuite for the Python standard library (v3.5)
 python3.5  - Interactive high-level object-oriented language (version 3.5)
 python3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 python3.5-dev - Header files and a static library for Python (v3.5)
 python3.5-doc - Documentation for the high-level object-oriented language 
Python
 python3.5-examples - Examples for the Python language (v3.5)
 python3.5-minimal - Minimal subset of the Python language (version 3.5)
 python3.5-venv - Interactive high-level object-oriented 

Bug#784475: Done some work but crash before main()

[Lisandro Damián Nicanor Pérez Meyer]

On 5 September 2017 at 15:51, Bastien ROUCARIES
 wrote:
> Hi,
>
> I have done porting work but now it fail before main():

I'm afraid that the version you are working against is not yet ready for Qt5.

Bug#874367: awscli: 'AWSHTTPSConnection' object has no attribute 'ssl_context'

[Olaf van der Spek]

Package: awscli
Version: 1.11.13-1
Severity: serious
Justification: unkn

Dear Maintainer,

$ aws s3 ls

'AWSHTTPSConnection' object has no attribute 'ssl_context'

Gr,

Olaf

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

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

Versions of packages awscli depends on:
ii  python3 3.5.3-1
ii  python3-botocore1.4.70-1
ii  python3-colorama0.3.7-1
ii  python3-docutils0.13.1+dfsg-2
ii  python3-rsa 3.4.2-1
ii  python3-s3transfer  0.1.9-1

awscli recommends no packages.

awscli suggests no packages.

-- no debconf information

Bug#874368: python-whisper: please Build-Depend on rename

[Dominic Hargreaves]

Source: python-whisper
Version: 0.9.15-1
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl from experimental as a result. Please
add a Build-Depends: rename to your package, and all will be well
again:

   debian/rules override_dh_install
make[1]: Entering directory '/<>'
rename 's/\.py//' debian/python-whisper/usr/bin/*.py
/bin/sh: 1: rename: not found

Let me know if you would prefer an NMU to get this trivial change made. 

Cheers,
Dominic.

[1] 

Processed: Re: Bug#874365: ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #874365 [ruby-gdk3] ruby-gdk3: Typelib file for namespace 'Gdk' (any 
version) not found (GLib::Error)
Severity set to 'important' from 'grave'
> tag -1 stretch
Bug #874365 [ruby-gdk3] ruby-gdk3: Typelib file for namespace 'Gdk' (any 
version) not found (GLib::Error)
Added tag(s) stretch.
> fixed -1 3.1.8-5
Bug #874365 [ruby-gdk3] ruby-gdk3: Typelib file for namespace 'Gdk' (any 
version) not found (GLib::Error)
Marked as fixed in versions ruby-gnome2/3.1.8-5.

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

Bug#874365: ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)

[dai]

Control: severity -1 important
Control: tag -1 stretch
Control: fixed -1 3.1.8-5

could you please install `gir1.2-gtk-3.0` package?
this error message tells missing `GObject introspection data`.

> /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:37:in `require': 
> Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#873892: marked as done (msxpertsuite: FTBFS: latex interference under make install)

[Debian Bug Tracking System]

Your message dated Tue, 5 Sep 2017 13:46:23 +0200
with message-id <20170905114623.y7ggysf3bxc7cqmw@pisa>
and subject line 873892 fixed
has caused the Debian Bug report #873892,
regarding msxpertsuite: FTBFS: latex interference under make install
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.)


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

Builds of msxpertsuite for several architectures failed because the
"make install" command wound up rebuilding(!) the user manual, without
the -j1 safeguard present for the initial make invocation.  Could you
please take a look?

Thanks!

FTR, I'm formally classifying this bug as a regression because it
could well affect binNMU attempts on architectures that succeeded this
time around.

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

The problem reported as

Bug#873892: msxpertsuite: FTBFS: latex interference under make install (Aaron
M. Ucko) appears to be fixed.

Many thanks to Aaron for reporting the problem.

Filippo

--
⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD   
⣾⠁⢰⠒⠀⣿⡁  public crypto key B053 304E 17D6 D419 DD9B 4651 41AB 484D 7694 CF42 @ pgp.mit.edu 
⢿⡄⠘⠷⠚⠋

⠈⠳⣄ --- End Message ---

Processed: r-cran-randomfieldsutils: FTBFS: init_RandomFieldsUtils.cc:62:10: error: 'R_NativeArgStyle' does not name a type

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - buster
Bug #868922 {Done: Andreas Tille } 
[src:r-cran-randomfieldsutils] r-cran-randomfieldsutils: FTBFS: 
init_RandomFieldsUtils.cc:62:10: error: 'R_NativeArgStyle' does not name a type
Removed tag(s) buster.

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

Bug#868922: r-cran-randomfieldsutils: FTBFS: init_RandomFieldsUtils.cc:62:10: error: 'R_NativeArgStyle' does not name a type

[Graham Inggs]

Control: tags -1 - buster

r-cran-randomfieldsutils 0.3.15-1 builds fine in testing

Bug#873821: marked as done (wcc Depends: binutils (< 2.29) but 2.29-8 is to be installed)

[Debian Bug Tracking System]

Your message dated Tue, 05 Sep 2017 11:09:26 +
with message-id 
and subject line Bug#873821: fixed in wcc 0.0.2+dfsg-2
has caused the Debian Bug report #873821,
regarding wcc Depends: binutils (< 2.29) but 2.29-8 is to be installed
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.)


-- 
873821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wcc
Version: 0.0.2+dfsg-1
Severity: serious

The following packages have unmet dependencies:
 wcc : Depends: binutils (< 2.29) but 2.29-8 is to be installed


-- System Information:
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: wcc
Source-Version: 0.0.2+dfsg-2

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

Debian distribution maintenance software
pp.
Philippe Thierry  (supplier of updated wcc 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, 31 Aug 2017 22:31:12 +0200
Source: wcc
Binary: wcc
Architecture: source
Version: 0.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Philippe Thierry 
Description:
 wcc- Collection of tools to manipulate binaries and shared objects
Closes: 873783 873821
Changes:
 wcc (0.0.2+dfsg-2) unstable; urgency=medium
 .
   * Various update (Closes: #873783): see belowing comments:
   * using packaged openlibm instead of embedded one.
 embedded openlibm was not able to be built on various arches
   * reducing target to amd64.
 the ldscript used to map relocated section in wsh has only been made for
 this target, making impossible to build wsh for other target than amd64
 without building specific ldscripts for each of them
   * add support to Debian/kfreebsd and Debian/Hurd.
 by embedding the elf-em macros list only when needed
   * This update also correct the binutils dependency (Closes: 873821).
 The error comes from an autogenerated dependency version build
 to binutils
 the udate as the same effect as a binNMU request, the package being
 rebuilt
   * Update std-version to 4.1.0
Checksums-Sha1:
 74315366bd426766c62a704190810bc311c6fe15 2120 wcc_0.0.2+dfsg-2.dsc
 33644e387a9dec43e8cb7d15cda097a07ee84478 14696 wcc_0.0.2+dfsg-2.debian.tar.xz
Checksums-Sha256:
 697c009e285db4482482395c97d7263350006b256df5f148d2b6adcb366b012a 2120 
wcc_0.0.2+dfsg-2.dsc
 220ff86944fa372f33785d985c803b21c786a64934dcbcd28d994b0f6dd6da41 14696 
wcc_0.0.2+dfsg-2.debian.tar.xz
Files:
 951ef2fea842411c6d83cdc3960c0244 2120 utils optional wcc_0.0.2+dfsg-2.dsc
 111c87854693a2932b739cdca5b88f12 14696 utils optional 
wcc_0.0.2+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZroAYAAoJEPNPCXROn13Z1v0P/3bZIUR7RWJZtiEr1XHf9wx7
pIiUmF8vxoMPPIvjE/eKyYRIuVFak5idyFrm0JFv6uN7oculXoqN/m42EIWaSPli
pJ3ymmWCbxgphujw+OG5i83/NSafEj/4gnZT5wp0DbzFq1WuMtuf+rvrGi2EqKIC
4f/SxUYx47h4r01dFqAlwUnelFIsw+wpvYuj9Ub9SgCuVmDI6a5tKkVRuj/IvKPw
Id6SmDqzuOZLVog6GLIL4Y60pJD7ByzjMB4cIcdiX6N20ShwwUyVEmb1fgFTXtzl
wDPthORAxU61fuaQ75McxI7Gk/XiBQKhLxMzQWBLP/qlHraqmJZy1eZi6BqOBg4V
nC8xq7/dbS5tHKhpoXB8rxx5guGS4loNox5lz2YJ40tVdp4nTZa7XJIIf8XyyMt+
nlqKG2la7V1OM47FRciOfyS+HQdpYkGB8AHb3oGGMFVLYZEa3hQz8Oj2pYT4gCbZ
JFQFtqjy1UZC4Yz8g6I3KkpwEhcmqZBlLNsIlNmH1mQICr2y9Kt/b7MQ+J4pYeeZ
JA19El175wFNvdv71/1vPYUwBwgzKoDUESKniZYMIW3xR23mJ0sIDkUp1MJsF8Xy
qTX5Cs2Dfr7ZutcXwaaRGWsZanJDVUEFeXtasOJT2T9Nwv57Vj0AitCwwW3hiFTd
iaELmgc65nkZWNPws9Zn
=zuvB
-END PGP SIGNATURE End Message ---

Processed (with 1 error): cufflinks: FTBFS with GCC-7: error: type/value mismatch at argument 1 in template parameter list for 'template struct std::hash'

[Debian Bug Tracking System]

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

> tag 871234 help FTBFS
Unknown tag/s: FTBFS.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer a11y etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #871234 [src:cufflinks] cufflinks: FTBFS with GCC-7: error: type/value 
mismatch at argument 1 in template parameter list for 'template 
struct std::hash'
Added tag(s) help.
>
End of message, stopping processing here.

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

Bug#874344: python-scipy: Fail to import with "undefined symbol: PyFPE_jbuf"

[Petter Reinholdtsen]

Package: python-scipy
Version: 0.18.1-2+b2
Severity: serious

I discovered this when trying to use gr-gsm in Debian Unstable.  Using
the library fail like this:

% python -c "from scipy.ndimage.filters import uniform_filter1d"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scipy/ndimage/__init__.py", line 161, 
in 
from .filters import *
  File "/usr/lib/python2.7/dist-packages/scipy/ndimage/filters.py", line 37, in 

from scipy.misc import doccer
  File "/usr/lib/python2.7/dist-packages/scipy/misc/__init__.py", line 51, in 

from scipy.special import comb, factorial, factorial2, factorialk
  File "/usr/lib/python2.7/dist-packages/scipy/special/__init__.py", line 638, 
in 
from .basic import *
  File "/usr/lib/python2.7/dist-packages/scipy/special/basic.py", line 19, in 

from . import orthogonal
  File "/usr/lib/python2.7/dist-packages/scipy/special/orthogonal.py", line 
101, in 
from scipy import linalg
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/__init__.py", line 175, 
in 
from .basic import *
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/basic.py", line 21, in 

from ._solve_toeplitz import levinson
ImportError: 
/usr/lib/python2.7/dist-packages/scipy/linalg/_solve_toeplitz.x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf
%

Setting severity to serious as it seem to make the library useless. :(

-- 
Happy hacking
Petter Reinholdtsen

Bug#874364: gnome: Gnome keyboard layout setting influences system-wide keyboard layout unpredictably

[Iiro Laiho]

Package: gnome
Version: 1:3.22+3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Gnome 3's keyboard layout setting seems to influence console keyboard layout,
but unpredictably. This can cause serious issues if one has a LUKS encrypted
filesystem: it is impossible to unlock it if the keys do not produce the
intended character. Therefore I am labelling this as critical as it can cause
the system to became impossible to boot up.

I have the "Finnish (DAS)" layout. That is in the -extra layouts. It is not
available to selection in debian-installer. I have enabled the -extra keyboard
layouts in Gnome and switched to that layout as default. After some time
(when?) the setting somehow propagates to the console keyboard layout. And when
the kernel is upgraded, it propagates to the initramfs and thus to the LUKS
password prompt.

IMO it is a bad design that settings of a non-root user influence the console
keyboard layout, but if this is 100% necessary, it should happen immediately
and predictably.

I am not sure if this is really a Gnome bug or a systemd bug.

A similar problem in Red Hat's bugzilla is number 1405539



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

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

Versions of packages gnome depends on:
ii  avahi-daemon 0.6.32-2
ii  cheese   3.22.1-1+b1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 9.0.2
ii  evolution3.22.6-1
ii  evolution-plugins3.22.6-1
ii  file-roller  3.22.3-1
ii  gedit-plugins3.22.0-1
ii  gimp 2.8.18-1
ii  gnome-calendar   3.22.4-2
ii  gnome-clocks 3.22.1-1
ii  gnome-color-manager  3.22.2-1
ii  gnome-core   1:3.22+3
ii  gnome-dictionary 3.20.0-3+b1
ii  gnome-documents  3.22.1-1
ii  gnome-getting-started-docs   3.22.0-1
ii  gnome-maps   3.22.2-1
ii  gnome-music  3.22.2-1
ii  gnome-orca   3.22.2-3
ii  gnome-screenshot 3.22.0-1+b1
ii  gnome-sound-recorder 3.21.92-2
ii  gnome-tweak-tool 3.22.0-1
ii  gnome-weather3.20.2-1
ii  gstreamer1.0-libav   1.10.4-1
ii  gstreamer1.0-plugins-ugly1.10.4-1
ii  inkscape 0.92.1-1
ii  libgsf-bin   1.14.41-1
ii  libgtk2-perl 2:1.2499-1
ii  libproxy1-plugin-networkmanager  0.4.14-2
ii  libreoffice-calc 1:5.2.7-1
ii  libreoffice-evolution1:5.2.7-1
ii  libreoffice-gnome1:5.2.7-1
ii  libreoffice-impress  1:5.2.7-1
ii  libreoffice-writer   1:5.2.7-1
ii  nautilus-sendto  3.8.4-2+b1
ii  network-manager-gnome1.4.4-1
ii  rhythmbox3.4.1-2+b1
ii  rhythmbox-plugin-cdrecorder  3.4.1-2+b1
ii  rhythmbox-plugins3.4.1-2+b1
ii  rygel-playbin0.32.1-3
ii  rygel-tracker0.32.1-3
ii  seahorse 3.20.0-3.1
ii  shotwell 0.25.4+really0.24.5-0.1
ii  simple-scan  3.23.2-1
ii  totem-plugins3.22.1-1
ii  vinagre  3.22.0-1+b1
ii  xdg-user-dirs-gtk0.10-1+b1

Versions of packages gnome recommends:
ii  brasero   3.12.1-4
ii  gnome-games   1:3.22+3
ii  polari3.22.2-1
ii  transmission-gtk  2.92-2

Versions of packages gnome suggests:
pn  alacarte 
pn  empathy  
pn  firefox-esr-l10n-all | firefox-l10n-all  
pn  goobox | sound-juicer
pn  xul-ext-gnome-keyring
pn  xul-ext-ublock-origin

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.22.0-1+deb9u1
ii  at-spi2-core  2.22.0-6
ii  baobab3.22.1-1
ii  caribou   0.4.21-1+b1
ii  chrome-gnome-shell8-4
ii  dconf-cli 0.26.0-2+b1
ii  dconf-gsettings-backend   0.26.0-2+b1
ii  eog   3.20.5-1+b1
ii  evince3.22.1-3+deb9u1
ii  evolution-data-server 3.22.7-1
ii  firefox-esr   52.3.0esr-1~deb9u1
ii  fonts-cantarell   0.0.25-2
ii  gdm3  3.22.3-3
ii  gedit 3.22.0-2
ii  gkbd-capplet  3.22.0.1-1+b1
ii  glib-networking   

Bug#874365: ruby-gdk3: Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)

[JD Friedrikson]

Package: ruby-gdk3
Version: 3.1.0-1
Severity: grave
Justification: renders package unusable

Hello there,

I was attempting to make a small thing with gtk3 (via ruby) this morning
and ran into an error with one of its dependencies:

```
/usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:37:in `require': 
Typelib file for namespace 'Gdk' (any version) not found (GLib::Error)
from /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:37:in 
`load'
from /usr/lib/ruby/vendor_ruby/gdk3.rb:56:in `init'
from /usr/lib/ruby/vendor_ruby/gtk3.rb:64:in `init'
from /usr/lib/ruby/vendor_ruby/gtk3.rb:40:in `const_missing'
from ./pomodoro:5:in `'
```

It seems to fail with some pretty basic usage:

```
#!/usr/bin/env ruby

require 'gtk3'

window = Gtk::Window.new('test')
window.show
Gtk.init
Gtk.main
```

As the error refers missing files, I figure this would be a bug related
to the package. Please let me know if I'm mistaken.

Cheers,
JD

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (600, 'stable'), (500, 'stable'), (300, 'testing'), (1, 
'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages ruby-gdk3 depends on:
ii  ruby1:2.3.3
ii  ruby-atk3.1.0-1
ii  ruby-cairo-gobject  3.1.0-1
ii  ruby-gdk-pixbuf23.1.0-1
ii  ruby-gobject-introspection  3.1.0-1
ii  ruby-pango  3.1.0-1

ruby-gdk3 recommends no packages.

ruby-gdk3 suggests no packages.

-- no debconf information

Processed: tagging 874368

[Debian Bug Tracking System]

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

> tags 874368 + sid buster
Bug #874368 [src:python-whisper] python-whisper: please Build-Depend on rename
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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