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

[Tino Didriksen]

On 7 September 2017 at 03:15, Paul Wise  wrote:

> Why do the tests for hfst need to be disabled?
>
> I think it would be better to keep them enabled so that we can ensure
> that hfst works correctly. Broken binaries are worse than FTBFS. You
> can ask for removal of the existing binaries from the architectures
> where the FTBFS happens by using `reportbug ftp.debian.org`.



The binaries are not broken, though. It's one out of a hundred tests that
fails.

It's more that some of the file formats are not endian-neutral (e.g.
OpenFST). For the purpose of working with HFST locally and exchanging the
neutral files, it works fine.

-- Tino Didriksen

Bug#873008: marked as done (hfst FTBFS on big endian: FAIL: test)

[Debian Bug Tracking System]

Your message dated Thu, 07 Sep 2017 05:04:38 +
with message-id 
and subject line Bug#873008: fixed in hfst 3.12.2~r3289-2
has caused the Debian Bug report #873008,
regarding hfst FTBFS on big endian: FAIL: test
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.)


-- 
873008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hfst
Version: 3.12.2~r3289-1
Severity: serious

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

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

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Matthias Klose]

On 06.09.2017 19:19, Emmanuel Bourg wrote:
> Le 6/09/2017 à 18:56, Matthias Klose a écrit :
> 
>>> - remove the suffix from the version in the pom
>>
>> doesn't work
>>
>>> - remove the --has-package-version flag
>>
>> doesn't work
> 
> You did that on libsejda-io-java right?

yes, and then trying to build the libsambox-java package.

Bug#874144: marked as done (octave-control FTBFS on arm64/i386 with octave-pkg-dev 1.5.0)

[Debian Bug Tracking System]

Your message dated Thu, 07 Sep 2017 03:49:34 +
with message-id 
and subject line Bug#874144: fixed in octave-control 3.0.0-3
has caused the Debian Bug report #874144,
regarding octave-control FTBFS on arm64/i386 with octave-pkg-dev 1.5.0
to be marked as done.

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

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


-- 
874144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-control
Version: 3.0.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/octave-control.html

...
Summary: 328 tests, 313 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1
--- End Message ---
--- Begin Message ---
Source: octave-control
Source-Version: 3.0.0-3

We believe that the bug you reported is fixed in the latest version of
octave-control, 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.
Rafael Laboissiere  (supplier of updated octave-control 
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:49:34 -0300
Source: octave-control
Binary: octave-control
Architecture: source amd64
Version: 3.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissiere 
Description:
 octave-control - computer-aided control system design (CACSD) for Octave
Closes: 874144
Changes:
 octave-control (3.0.0-3) unstable; urgency=medium
 .
   [ Sébastien Villemot ]
   * d/copyright: use secure URL for format.
   * d/watch: bump to format version 4.
 .
   [ Rafael Laboissiere ]
   * d/p/comment-out-failing-unit-tests.patch: New patch.
 The package FTBFS with octave-pkg-dev 1.5.0 because it now exits with
 a code error when unit tests fail.  We comment out, for now, the
 failing tests, but this must be addressed in a proper way, since it
 may hide problems in the package. (Closes: #874144)
   * d/control:
 + Bump Standards-Version to 4.1.0 (no changes needed)
 + Use cgit instead of gitweb in Vcs-Browser URL
Checksums-Sha1:
 0f1c06906d100a7ee8765a27760d3aa42c8dad63 2117 octave-control_3.0.0-3.dsc
 8aff7414a47a0ce5f2e174071f11162cc83258c4 5604 
octave-control_3.0.0-3.debian.tar.xz
 2b18a05b3eabfeaf9ed3e3cf914bfb3869d2b5af 1051780 
octave-control-dbgsym_3.0.0-3_amd64.deb
 1bc6662eb69dbfa18a8aca93842bc96f11a44477 11296 
octave-control_3.0.0-3_amd64.buildinfo
 1c9834aa6b109c1471a5382377cdb0cfad8c754d 802796 
octave-control_3.0.0-3_amd64.deb
Checksums-Sha256:
 8cf7217c77010b19d869a13cce2efba327bdf088da29f11f50460b4b724a3c59 2117 
octave-control_3.0.0-3.dsc
 e78c88fcac3fdae73734eecd38474322dd6ffab3f0d3302ef2706f383cdda110 5604 
octave-control_3.0.0-3.debian.tar.xz
 a910e85b74c71d60b172521e03454de28361551f96b402d7c06cfe4e8a8a0e12 1051780 
octave-control-dbgsym_3.0.0-3_amd64.deb
 65077c2f0907f527b0575614f82e01b3572e505dc946d2be07551301bdc49e13 11296 
octave-control_3.0.0-3_amd64.buildinfo
 0b036e1633f2ddab9d2721f2f4438e31ea06411dcb3227fb3745194f9260babe 802796 
octave-control_3.0.0-3_amd64.deb
Files:
 bdb22b7d991712ac0274669cc5f03738 2117 math optional octave-control_3.0.0-3.dsc
 9cb4d97f26fcdc894cac5223b119b496 5604 math optional 
octave-control_3.0.0-3.debian.tar.xz
 8714521fbf7f4602d36082d88bb8dd66 1051780 debug extra 
octave-control-dbgsym_3.0.0-3_amd64.deb
 33fb8fc5315e5a3239365daa3f892d0e 11296 math optional 
octave-control_3.0.0-3_amd64.buildinfo
 943b15d4821abee39dc18659d46d921d 802796 math optional 
octave-control_3.0.0-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlmwvmAACgkQISSqGYN4
XJDo0w//WCMPOv0bOXIN+fylQ9eo4aO68ZVnIUuCCthSrTemlt8eZcNggZtOuoeH
v/oR4o519kg2+mT/SFJykVebkvg8WPzZ6BK53kPF5HJ/4d6QTk6Vk+UHpQl6BU1B
aP0RRzY4YZqXGK9yKVPVN77zpV2oMegsQH8irICLPQt2fXumolkP6J82HC3zf/Hn
75Sx5CnnlcqddgmbPXW5NMnUZdtlGy8ap33vHyRf9tKXSjh3GKvUPtgYxDx+xern
zOeuvgO/sU1e4rUG7okz7IFNNEY4oDB/GPULLVCI7X40xl2RQfyYqkXOlQwfaZM7
sEuCk5+WHeqGgxBC7+BnD+ZjNB6tTulJA4ia8kzpMVmsf4f1vGxs/v3/Z2MWMKYi
5np1Fl2lV

Bug#873639: marked as done (python-scipy FTBFS on ppc64el: python3.5-dbg segfaults)

[Debian Bug Tracking System]

Your message dated Thu, 7 Sep 2017 05:49:33 +0200
with message-id <3986cbfd-0f77-57f7-7823-c08d6880e...@debian.org>
and subject line Re: python-scipy FTBFS on ppc64el: python3.5-dbg segfaults
has caused the Debian Bug report #873639,
regarding python-scipy FTBFS on ppc64el: python3.5-dbg segfaults
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.)


-- 
873639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-scipy
Version: 0.18.1-2
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/logs.php?pkg=python-scipy&arch=ppc64el

...
scipy/sparse/linalg/dsolve/SuperLU/SRC/sgsrfs.c: In function 'sgsrfs':
scipy/sparse/linalg/dsolve/SuperLU/SRC/sgsrfs.c:416:3: warning: 'transt' may be 
used uninitialized in this function [-Wmaybe-uninitialized]
   sgstrs (transt, L, U, perm_c, perm_r, &Bjcol, stat, info);
   ^
scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c: In function 'zlacon2_':
scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c:165:5: warning: implicit 
declaration of function 'zcopy_'; did you mean 'zlacon2_'? 
[-Wimplicit-function-declaration]
 zcopy_(n, x, &c__1, v, &c__1);
 ^~
 zlacon2_
scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c:171:1: warning: label 'L90' 
defined but not used [-Wunused-label]
 L90:
 ^~~
powerpc64le-linux-gnu-gcc: scipy/sparse/linalg/dsolve/SuperLU/SRC/sgssvx.c
In file included from scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_cdefs.h:87:0,
 from scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c:23:
scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_util.h:373:1: warning: function 
declaration isn't a prototype [-Wstrict-prototypes]
 extern double  SuperLU_timer_ ();
 ^~
powerpc64le-linux-gnu-gcc: scipy/sparse/linalg/dsolve/SuperLU/SRC/dpruneL.c
scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c: In function 
'ccopy_to_ucol':
scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c:77:11: warning: suggest 
parentheses around assignment used as truth value [-Wparentheses]
   if (mem_error = cLUMemXpand(jcol, nextu, UCOL, &nzumax, Glu))
   ^
In file included from scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_zdefs.h:87:0,
 from scipy/sparse/linalg/dsolve/SuperLU/SRC/zpanel_dfs.c:25:
scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_util.h:373:1: warning: function 
declaration isn't a prototype [-Wstrict-prototypes]
 extern double  SuperLU_timer_ ();
 ^~
scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c:80:11: warning: suggest 
parentheses around assignment used as truth value [-Wparentheses]
   if (mem_error = cLUMemXpand(jcol, nextu, USUB, &nzumax, Glu))
   ^
In file included from scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_zdefs.h:87:0,
 from scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:12:
scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_util.h:373:1: warning: function 
declaration isn't a prototype [-Wstrict-prototypes]
 extern double  SuperLU_timer_ ();
 ^~
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c: In function 'zgsisx':
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:578:7: warning: suggest 
parentheses around operand of '!' or change '&' to '&&' or '!' to '~' 
[-Wparentheses]
  if ( !mc64 & equil ) { /* Only perform equilibration, no row perm */
   ^
powerpc64le-linux-gnu-gcc: scipy/sparse/linalg/dsolve/SuperLU/SRC/qselect.c
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:667:24: warning: unused 
variable 'rhs_work' [-Wunused-variable]
 doublecomplex *rhs_work;
^~~~
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:413:15: warning: variable 
'diag_pivot_thresh' set but not used [-Wunused-but-set-variable]
 doublediag_pivot_thresh;
   ^
Segmentation fault
debian/rules:36: recipe for target 'build-python3.5' failed
make[1]: *** [build-python3.5] Error 139
make[1]: Leaving directory '/<>'
debian/rules:43: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2



Reproduced on plummer, top part of the backtrace:

#0  PyTuple_GetItem (op=0x0, i=0) at ../Objects/tupleobject.c:138
#1  0x33ea184c in PyEval_EvalFrameEx (
f=Frame 0x3fff38000bc8, for file 
/usr/lib/python3/dist-packages/numpy/distutils/exec_command.py, line 279, in 
_exec_command_posix (command=['powerpc64le-linux-gnu-gcc', '-pthread', '-g', 
'-Og', '-Wall', '-Wstrict-prototypes', '-g', '-ggdb', '-Wdate-time', 
'-D_FORTIFY_SOURCE=2', '-fPIC', '-DUSE_VENDOR_BLAS=

Bug#874344: marked as done (python-scipy: Fail to import with "undefined symbol: PyFPE_jbuf")

[Debian Bug Tracking System]

Your message dated Thu, 7 Sep 2017 05:48:10 +0200
with message-id 
and subject line Re: python-scipy: Fail to import with "undefined symbol: 
PyFPE_jbuf"
has caused the Debian Bug report #874344,
regarding python-scipy: Fail to import with "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.)


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

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
--- End Message ---
--- Begin Message ---
Version: 0.18.1-2.1

Fixed.--- End Message ---

Processed: affects 872977

[Debian Bug Tracking System]

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

> affects 872977 + src:udisks2
Bug #872977 [src:libblockdev] libblockdev FTBFS on s390x: fatal error: 
s390utils/vtoc.h: No such file or directory
Added indication that 872977 affects src:udisks2
> thanks
Stopping processing here.

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

Processed: severity of 872977 is serious

[Debian Bug Tracking System]

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

> # this is blocking udisks2 from migrating to testing
> severity 872977 serious
Bug #872977 [src:libblockdev] libblockdev FTBFS on s390x: fatal error: 
s390utils/vtoc.h: No such file or directory
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#874533: llvm-toolchain-4.0: Can't exec "gcc-7.1": No such file or directory

[Igor Liferenko]

Package: clang-4.0
Version: 1:4.0.1-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

Your package failed to build on amd64:

apt-get source clang-4.0
Reading package lists... Done
Picking 'llvm-toolchain-4.0' as source package instead of 'clang-4.0'
NOTICE: 'llvm-toolchain-4.0' packaging is maintained in the 'Svn' version 
control system at:
svn://anonscm.debian.org/svn/pkg-llvm/llvm-toolchain/branches/4.0/
Need to get 54.4 MB of source archives.
Get:1 http://ftp.us.debian.org/debian testing/main llvm-toolchain-4.0 1:4.0.1-1 
(dsc) [7,301 B]
...


$ dpkg-buildpackage -uc -us -rfakeroot -b
dpkg-buildpackage: info: source package llvm-toolchain-4.0
dpkg-buildpackage: info: source version 1:4.0.1-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Sylvestre Ledru 

dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build llvm-toolchain-4.0-4.0.1
 fakeroot debian/rules clean
dpkg-query: no packages found matching g++-7.1
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
dpkg-query: no packages found matching g++-7.1
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
dpkg-query: no packages found matching g++-7.1
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
dh clean --with ocaml
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/tex_tmp/llvm-toolchain-4.0-4.0.1'
Can't exec "gcc-7.1": No such file or directory at 
/usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
dpkg-query: no packages found matching g++-7.1
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
Can't exec "gcc-7.1": No such file or directory at 
/usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
dpkg-query: no packages found matching g++-7.1
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
dpkg-query: no packages found matching g++-7.1
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
Can't exec "gcc-7.1": No such file or directory at 
/usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
Can't exec "gcc-7.1": No such file or directory at 
/usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
Can't exec "gcc-7.1": No such file or directory at 
/usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: 

Processed: Re: aggressive polling by libmtp resulting in multiple messages.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #874216 [gvfs-backends] (no subject)
Severity set to 'normal' from 'grave'

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

Bug#874216: aggressive polling by libmtp resulting in multiple messages.

[Jeremy Bicha]

Control: severity -1 normal

The 'grave' severity is reserved for major security bugs or bugs where
users lose data, etc.

https://www.debian.org/Bugs/Developer#severities

Thanks,
Jeremy Bicha

Bug#874531: mesa: FTBFS on armel: __atomic_fetch_add_8 undefined

[Aaron M. Ucko]

Source: mesa
Version: 17.2.0-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of mesa for armel have been failing lately:

  glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function 
`disk_cache_remove':
  ./build/src/util/../../../src/util/disk_cache.c:643: undefined reference to 
`__atomic_fetch_add_8'
  collect2: error: ld returned 1 exit status
  Makefile:2110: recipe for target 'glsl_compiler' failed
  make[5]: *** [glsl_compiler] Error 1
  make[5]: Leaving directory '/<>/build/src/compiler'

Please link glsl_compiler (and anything else that uses libstandalone)
against -latomic.  If you don't want that dependency on architectures
that don't need it, you can either conditionalize on architecture or
precede -latomic with -Wl,--as-needed (and follow it with
-Wl,--no-as-needed if desired).

Thanks!

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

Bug#874530: msxpertsuite: FTBFS: cannot find .../massxpert-doc.pdf

[Aaron M. Ucko]

Source: msxpertsuite
Version: 3.6.1-1
Severity: serious
Justification: fails to build from source

Thanks for looking into #873892.  Alas, builds of msxpertsuite
covering only its architecture-dependent binary packages (as on the
autobuilders, or with dpkg-buildpackage -B) have been failing:

  CMake Error at user-manual/cmake_install.cmake:44 (file):
file INSTALL cannot find

"/<>/debian/build/massxpert/user-manual/build-user-manual/massxpert-doc.pdf".
  Call Stack (most recent call first):
cmake_install.cmake:74 (include)


  Makefile:120: recipe for target 'install' failed
  make[1]: *** [install] Error 1
  make[1]: Leaving directory '/<>/debian/build/massxpert'
  debian/rules:148: recipe for target 'install-arch-stamp' failed
  make: *** [install-arch-stamp] Error 2

Could you please take another look at this setup?

Thanks!

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

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

[Paul Wise]

On Thu, 24 Aug 2017 14:27:17 +0200 Tino Didriksen wrote:

> I forgot to re-disable tests for hfst.

Why do the tests for hfst need to be disabled?

I think it would be better to keep them enabled so that we can ensure
that hfst works correctly. Broken binaries are worse than FTBFS. You
can ask for removal of the existing binaries from the architectures
where the FTBFS happens by using `reportbug ftp.debian.org`.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: Re: Bug#846314: fixed in alot 0.6-1

[Debian Bug Tracking System]

Processing control commands:

> found -1 alot/0.6-1
Bug #846314 {Done: Jordan Justen } [alot] alot: 
please use python-gpg instead of python-gpgme
Bug #866027 {Done: Jordan Justen } [alot] alot: 
Migrate from pygpgme to python-gpg
Marked as found in versions alot/0.6-1; no longer marked as fixed in versions 
alot/0.6-1 and reopened.
Marked as found in versions alot/0.6-1; no longer marked as fixed in versions 
alot/0.6-1 and reopened.

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

Bug#846314: fixed in alot 0.6-1

[Paul Wise]

Control: found -1 alot/0.6-1

On Thu, 24 Aug 2017 03:34:11 + Jordan Justen wrote:

>* Depend on python-gpg rather than pygpgme (Closes: #846314, #866027)

Looks like you made it depend on both instead:

$ apt-cache show alot | grep -oE 'Version.*|python-gpg[a-z]*'
Version: 0.6-1
python-gpgme
python-gpg

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

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

[Bastien ROUCARIES]

control: tags -1 + pending

I have uploaded a new version waiting ftpmaster

On Tue, Sep 5, 2017 at 9:11 PM, Lisandro Damián Nicanor Pérez Meyer
 wrote:
> 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.

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #784475 [src:kbibtex] [kbibtex] Qt4's WebKit removal
Added tag(s) pending.

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

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Emmanuel Bourg]

Le 6/09/2017 à 22:58, Markus Koschany a écrit :

> If I understand correctly the behavior changed in maven-debian-helper
> 2.2 and all Maven packages that build-depend on a package which
> specifies --has-package-version will automatically use a version
> constraint from now on?

That's correct. When --has-package-version is specified, the
debian.hasPackageVersion property is added to the pom installed in the
package. mh_installpom did that in maven-repo-helper, but not
maven-debian-helper before the version 2.2.


> Please note that --has-package-version is used
> by default when new packages are created with mh_make and I believe most
> Maven packages that I have touched use this flag in some way.

I checked mh_make, it handles this properly. The --has-package-version
flag is only added if the version of the package matches the version of
the pom.


> I can remove the --has-package-version again and work around the version
> constraint but I believe the issue is more complex. In my opinion there
> shouldn't be an automatic version constraint unless explicitly specified
> by the maintainer.

> I fear a lot more packages are affected and version
> constraints will be too strict and cause more of these issues. Do we
> really need to remove --has-package-version if we don't want a versioned
> constraint or can't we just treat --has-package-version and automatic
> version constraints differently in m-d-h to get back a more fine-grained
> control?

Intuitively I think the version constraints on the binary packages
should be picked from the version constraints of the source package (so
controlled by the maintainer). On the other hand, it's rather common to
forget versioning the build dependencies, and this --has-package-version
mechanism is often handy to prevent accidental migrations to testing of
packages that actually need another dependency still blocked for some
reason. This greatly improves the consistency of the migrations.

We probably need a lintian rule that checks if the version of the pom
matches the version of the package when --has-package-version is
specified (actually the pom version must be less than the package
version, this allows some divergences such as a package with the version
1.2.3+ds1 and the pom with the version 1.2.3). This will allow us to
easily identify and fix the packages affected.

Emmanuel Bourg

Bug#874526: Keyboard grab doesn't work under Wayland

[Josh Triplett]

Package: gnome-boxes
Version: 3.25.91-1
Severity: serious

[I don't know whether this bug lies in gnome-boxes or gnome-shell or
some combination of both. Release-critical because this completely
breaks the ability to log into many Windows VMs with gnome-boxes under
the default GNOME Wayland session.]

The mechanism gnome-boxes uses to grab the keyboard doesn't work under
the default GNOME Wayland session. This makes it impossible to send
Ctrl-Alt-Delete; it always goes to gnome-shell instead.

(It might also help to add Ctrl-Alt-Delete to the list of shortcuts
provided in the gnome-boxes keyboard menu, alongside Ctrl-Alt-Backspace
and similar.)

-- 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.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-boxes depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libarchive13 3.2.2-2
ii  libc62.24-17
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libgdk-pixbuf2.0-0   2.36.5-4
ii  libglib2.0-0 2.53.6-1
ii  libgovirt2   0.3.4-2
ii  libgtk-3-0   3.22.19-1
ii  libgtk-vnc-2.0-0 0.7.1-1
ii  libgudev-1.0-0   232-1
ii  libosinfo-1.0-0  1.1.0-1
ii  libosinfo-bin1.1.0-1
ii  libpango-1.0-0   1.40.11-1
ii  libpangocairo-1.0-0  1.40.11-1
ii  librest-0.7-00.8.0-2
ii  libsecret-1-00.18.5-3.1
ii  libsoup2.4-1 2.59.90.1-1
ii  libspice-client-glib-2.0-8   0.34-1.1
ii  libspice-client-gtk-3.0-50.34-1.1
ii  libtracker-sparql-1.0-0  1.12.1-1
ii  libusb-1.0-0 2:1.0.21-2
ii  libvirt-daemon   3.6.0-1
ii  libvirt-glib-1.0-0   1.0.0-1
ii  libxml2  2.9.4+dfsg1-4
ii  mtools   4.0.18-2+b1
ii  tracker  1.12.1-1

Versions of packages gnome-boxes recommends:
ii  qemu-system-x86  1:2.8+dfsg-7

gnome-boxes suggests no packages.

-- no debconf information

Bug#874524: Invalid symlink: /usr/bin/r2-indent -> /build/radare2-1.6.0+dfsg/sys/indent.sh

[Julian Andres Klode]

Package: radare2
Version: 1.6.0+dfsg-1
Severity: serious

This symlink is obviously wrong:

/usr/bin/r2-indent -> /build/radare2-1.6.0+dfsg/sys/indent.sh

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

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

Versions of packages radare2 depends on:
ii  libc6   2.24-17
ii  libradare2-1.6  1.6.0+dfsg-1
ii  libzip4 1.1.2-1.1+b1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages radare2 recommends:
ii  libradare2-dev  1.6.0+dfsg-1

radare2 suggests no packages.

-- no debconf information

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#872281: marked as done (why FTBFS with frama-c 20170501+phosphorus+dfsg-1)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 21:17:34 +
with message-id 
and subject line Bug#872281: fixed in why 2.39-1
has caused the Debian Bug report #872281,
regarding why FTBFS with frama-c 20170501+phosphorus+dfsg-1
to be marked as done.

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

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


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

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

...
   dh_install -O--no-parallel
dh_install: Cannot find (any matches for) "frama-c-plugin/top/Jessie.o" (tried 
in ., debian/tmp)

dh_install: why missing files: frama-c-plugin/top/Jessie.o
dh_install: missing files, aborting
install -d debian/.debhelper/generated/why
install -d debian/.debhelper/generated/libwhy-coq
debian/rules:67: recipe for target 'binary' failed
make: *** [binary] Error 25
--- End Message ---
--- Begin Message ---
Source: why
Source-Version: 2.39-1

We believe that the bug you reported is fixed in the latest version of
why, 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.
Ralf Treinen  (supplier of updated why 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 21:34:58 +0200
Source: why
Binary: why libwhy-coq
Architecture: source
Version: 2.39-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 libwhy-coq - Why library for Coq
 why- Software verification tool for C and Java
Closes: 872281
Changes:
 why (2.39-1) unstable; urgency=medium
 .
   * New upstream version (closes: #872281)
   * Bumped build-dependency on frama-c-base to 20170501+phosphorus+dfsg
   * debian/copyright:
 - migrate to machine-readable format 1.0
 - fix upstream contact (Claude Marché)
   * Standards-Version 4.0.1 (no change)
   * Dropped build-dep on autotools-dev, which is obsolete with DH level 10.
Checksums-Sha1:
 7cb4fe9e97c280680c5030d6f1d30b185546f50b 2416 why_2.39-1.dsc
 1483e8ebc9f759e70900ea592da5b347259810d6 1694571 why_2.39.orig.tar.gz
 c9ce00aa4b582a3c667c107645487b7401019ac1 11688 why_2.39-1.debian.tar.xz
 e0937126e4be7c5b7ef3616cc862d28ef5de4c8a 8641 why_2.39-1_source.buildinfo
Checksums-Sha256:
 9e53174db6c599c4a772ee489f77a6aacf15a6cae198eeb67810b4d02f6cc9ea 2416 
why_2.39-1.dsc
 4815111efa3d31c2e209ec98346ac67dd3578fb355adf9d04ff86800a83cc159 1694571 
why_2.39.orig.tar.gz
 6ec76cd7fb5a69a388b105c7745419a5486564e9f3054da5a8c44382908ed7c3 11688 
why_2.39-1.debian.tar.xz
 5e03508838a1753149fadbf796680bf3b2dd24fc1843151480dbbb60950d7d68 8641 
why_2.39-1_source.buildinfo
Files:
 42ea6631d60a5b788a74fe1bf98b9b9b 2416 math optional why_2.39-1.dsc
 d03ea54b2d37039d26a1f2f82b61d860 1694571 math optional why_2.39.orig.tar.gz
 1bda2c15b8c573c6255229dfd49e25b3 11688 math optional why_2.39-1.debian.tar.xz
 81255ce7a871a815aff56d510ddd7138 8641 math optional why_2.39-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAlmwVCcACgkQdFxHZtTK
zf8wsQ//WMc7rOUGxiWMsloprIYkkFschKvfeSX6fsDpxcCIYxRQKthdSkrdHv4w
Nu4Q/zkVGDDat0sdKjoTUwgYUZYOQ18GOAs4iNDvqIAW+6y4qq3h/CSBDXJFi/8O
uRkf8lurKWGoFDhtoMChjCCJmV/fMPQRq5/Zpzvpu3RNRZ+m/GqFlHiAjDIO1HD/
L8GektzHLMZkNJawHqMtX/iepghCiYvS8gChyTk1ksVuxA3M0+worc2wTY7MBhcy
m/25eqm2XYCplBmqxYs0sjH/+BIHGFkele6/RFm55ChHMmcvELCIW/RUtTmRlprJ
420HbBOaW8KAoWktqQW93XJEBocGKd/eX5S+zcK3TaxcypjyHFwttA+kCRNQZO7p
amWVgbON2q7w3LEdzT6q2I71h7c2Kxn8Uz+QLnJdeyEekmmrnxkuD7kWPsOJPO+B
MSOatOIjhEgEufAMooUFBmZq2G0JmhR+mLYo++VQGbAWbFL73MYckhOfMYi62Kt3
15/5Np+cGsfyUgaSLprmFufBUeYnaZQl3MX/4isjPKQCDSmfuKgUtylACE6GATgS
AOndFRlbUFoUeF+51wnrflXC8448hAu0jdIWz2ATWvevIeg4Jfqueb8mLD9RKrou
67LVbqvENihrF0VkC3eS3vOY8JmA+3ZJ3DYBigDacx/XTDRElSw=
=NtpJ
-END PGP SIGNATURE End Message ---

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Markus Koschany]

Am 06.09.2017 um 15:08 schrieb Emmanuel Bourg:
> Le 6/09/2017 à 14:51, Matthias Klose a écrit :
> 
>> rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>=
>> 1.1.3.RELEASE)
>>
>> $ dpkg -I ../libsambox-java_1.0.34-1_all.deb | grep Depends
>>  Depends: libcommons-io-java, libfontbox2-java (>= 2.0.7), libsejda-io-java 
>> (>=
>> 1.1.3.RELEASE), libslf4j-java (>= 1.7.25)
> 
> This is an issue with libsejda-io-java, the --has-package-version flag
> was mistakenly used [1]. This led maven-debian-helper to think that it
> could use the version in the pom as a version constraint at the package
> level, which is wrong in this case due to the ".RELEASE" suffix (this
> behavior was broken before maven-debian-helper 2.2, see #862894).

If I understand correctly the behavior changed in maven-debian-helper
2.2 and all Maven packages that build-depend on a package which
specifies --has-package-version will automatically use a version
constraint from now on? Please note that --has-package-version is used
by default when new packages are created with mh_make and I believe most
Maven packages that I have touched use this flag in some way.

> The solution is to either:
> - add the ".RELEASE" suffix to the package version
> - remove the suffix from the version in the pom
> - remove the --has-package-version flag

I can remove the --has-package-version again and work around the version
constraint but I believe the issue is more complex. In my opinion there
shouldn't be an automatic version constraint unless explicitly specified
by the maintainer. I fear a lot more packages are affected and version
constraints will be too strict and cause more of these issues. Do we
really need to remove --has-package-version if we don't want a versioned
constraint or can't we just treat --has-package-version and automatic
version constraints differently in m-d-h to get back a more fine-grained
control?





signature.asc
Description: OpenPGP digital signature

Bug#874521: fwupd segfaults at start

[Mario.Limonciello]

Is this 100% reproductible for you?

Can you describe more about your machine?

I suspect this is an upstream issue, it may be useful to file it upstream so 
that it can be debugged there.

Sent from VMware Boxer

On Sep 6, 2017 15:27, Laurent Bigonville  wrote:

Package: fwupd
Version: 0.9.7-2
Severity: grave
Justification: renders package unusable

Hi,

fwupd segfaults at start with the following trace:

#0  0x556f337e7dd2 in FU_IS_DEVICE (ptr=0x556f34bdc170) at 
../src/fu-device.h:31
#1  0x556f337e7dd2 in fu_plugin_device_add (plugin=0x556f34bab840 
[FuPlugin], device=0x556f34bdc170) at ../src/fu-plugin.c:317
#2  0x556f337e7eed in fu_plugin_device_add_delay_cb 
(user_data=0x556f34bdedf0, user_data@entry=) at ../src/fu-plugin.c:374
#3  0x7fe839841853 in g_timeout_dispatch 
(source=source@entry=0x556f34bde830, callback=, 
user_data=) at ../../../../glib/gmain.c:4633
#4  0x7fe839840dd5 in g_main_dispatch (context=0x556f34b6c800) at 
../../../../glib/gmain.c:3148
#5  0x7fe839840dd5 in g_main_context_dispatch 
(context=context@entry=0x556f34b6c800) at ../../../../glib/gmain.c:3813
#6  0x7fe8398411a0 in g_main_context_iterate (context=0x556f34b6c800, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../../glib/gmain.c:3886
#7  0x7fe8398414b2 in g_main_loop_run (loop=0x556f34b4edf0) at 
../../../../glib/gmain.c:4082
#8  0x556f337d9dca in main (argc=, argv=) at 
../src/fu-main.c:947

Regards,

Laurent Bigonville

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

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

Versions of packages fwupd depends on:
ii  libappstream-glib8 0.7.1-2
ii  libarchive13   3.2.2-2
ii  libc6  2.24-17
ii  libcolorhug2   1.3.3-2
ii  libdfu10.9.7-2
ii  libefivar1 31-1
ii  libfwup1   9-2
ii  libfwupd1  0.9.7-2
ii  libglib2.0-0   2.53.6-1
ii  libgnutls303.5.15-2
ii  libgpg-error0  1.27-3
ii  libgpgme11 1.9.0-4
ii  libgudev-1.0-0 232-1
ii  libgusb2   0.2.11-1
ii  libpolkit-gobject-1-0  0.113-6
ii  libsmbios2 2.3.1-2
ii  libsoup2.4-1   2.59.90.1-1
ii  libsqlite3-0   3.20.1-1
ii  libuuid1   2.29.2-4

Versions of packages fwupd recommends:
ii  fwupdate  9-2
ii  python3   3.5.3-3

fwupd suggests no packages.

-- no debconf information

Bug#842815: Help needed for HDF5 1.10 transition of libsis-jhdf5-java

[Bernd Rinn]

Hi Andreas,

No, unfortunately not.

Kind regards,
Bernd

On 09/06/2017 12:50 PM, Andreas Tille wrote:
> Hello Bernd,
> 
> On Wed, 23 Nov 2016 06:54:21 +0100, you wrote
>> the migration of JHDF5 to HDF5 1.10 is ongoing and mostly depend on me
>> having a block of time I can spend on it. Your analysis of the work that
>> needs to be done is right from what I can see. The plan is to switch to
>> using the JNI library from the HDF group wherever possible (it may still
>> be necessary to have a small JNI library though as some calls appear to
>> be missing).
>>
>> I will keep you updated.
> 
> Is there any news, may be only a patch for the existing version we
> could try to fix the Debian package?
> 
> Kind regards
> 
>Andreas.
> 



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#874521: fwupd segfaults at start

[Laurent Bigonville]

Package: fwupd
Version: 0.9.7-2
Severity: grave
Justification: renders package unusable

Hi,

fwupd segfaults at start with the following trace:

#0  0x556f337e7dd2 in FU_IS_DEVICE (ptr=0x556f34bdc170) at 
../src/fu-device.h:31
#1  0x556f337e7dd2 in fu_plugin_device_add (plugin=0x556f34bab840 
[FuPlugin], device=0x556f34bdc170) at ../src/fu-plugin.c:317
#2  0x556f337e7eed in fu_plugin_device_add_delay_cb 
(user_data=0x556f34bdedf0, user_data@entry=) at ../src/fu-plugin.c:374
#3  0x7fe839841853 in g_timeout_dispatch 
(source=source@entry=0x556f34bde830, callback=, 
user_data=) at ../../../../glib/gmain.c:4633
#4  0x7fe839840dd5 in g_main_dispatch (context=0x556f34b6c800) at 
../../../../glib/gmain.c:3148
#5  0x7fe839840dd5 in g_main_context_dispatch 
(context=context@entry=0x556f34b6c800) at ../../../../glib/gmain.c:3813
#6  0x7fe8398411a0 in g_main_context_iterate (context=0x556f34b6c800, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../../glib/gmain.c:3886
#7  0x7fe8398414b2 in g_main_loop_run (loop=0x556f34b4edf0) at 
../../../../glib/gmain.c:4082
#8  0x556f337d9dca in main (argc=, argv=) at 
../src/fu-main.c:947

Regards,

Laurent Bigonville

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

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

Versions of packages fwupd depends on:
ii  libappstream-glib8 0.7.1-2
ii  libarchive13   3.2.2-2
ii  libc6  2.24-17
ii  libcolorhug2   1.3.3-2
ii  libdfu10.9.7-2
ii  libefivar1 31-1
ii  libfwup1   9-2
ii  libfwupd1  0.9.7-2
ii  libglib2.0-0   2.53.6-1
ii  libgnutls303.5.15-2
ii  libgpg-error0  1.27-3
ii  libgpgme11 1.9.0-4
ii  libgudev-1.0-0 232-1
ii  libgusb2   0.2.11-1
ii  libpolkit-gobject-1-0  0.113-6
ii  libsmbios2 2.3.1-2
ii  libsoup2.4-1   2.59.90.1-1
ii  libsqlite3-0   3.20.1-1
ii  libuuid1   2.29.2-4

Versions of packages fwupd recommends:
ii  fwupdate  9-2
ii  python3   3.5.3-3

fwupd suggests no packages.

-- no debconf information

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Emmanuel Bourg]

Le 6/09/2017 à 14:51, Matthias Klose a écrit :

> rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>=
> 1.1.3.RELEASE)
> 
> $ dpkg -I ../libsambox-java_1.0.34-1_all.deb | grep Depends
>  Depends: libcommons-io-java, libfontbox2-java (>= 2.0.7), libsejda-io-java 
> (>=
> 1.1.3.RELEASE), libslf4j-java (>= 1.7.25)

This is an issue with libsejda-io-java, the --has-package-version flag
was mistakenly used [1]. This led maven-debian-helper to think that it
could use the version in the pom as a version constraint at the package
level, which is wrong in this case due to the ".RELEASE" suffix (this
behavior was broken before maven-debian-helper 2.2, see #862894).

The solution is to either:
- add the ".RELEASE" suffix to the package version
- remove the suffix from the version in the pom
- remove the --has-package-version flag

[1]
https://sources.debian.net/src/libsejda-io-java/1.1.3-1/debian/libsejda-io-java.poms/#L28

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

[Salvatore Bonaccorso]

On Wed, Sep 06, 2017 at 06:58:36AM +0200, Salvatore Bonaccorso wrote:
> 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

When fixing this issue make sure to apply the complete fix to not open
openjpeg2 to CVE-2017-14164. Applying both 

https://github.com/uclouvain/openjpeg/commit/4241ae6fbbf1de9658764a80944dc8108f2b4154

and 

https://github.com/uclouvain/openjpeg/commit/dcac91b8c72f743bda7dbfa9032356bc8110098a

should completely resolve CVE-2017-14152 (double check!).

Regards,
Salvatore

Processed: Fix metadata

[Debian Bug Tracking System]

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

> forwarded 874205 https://gitlab.com/esr/open-adventure/issues/41
Bug #874205 [src:open-adventure] open-adventure FTBFS on !amd64/arm64: test 
failure
Set Bug forwarded-to-address to 
'https://gitlab.com/esr/open-adventure/issues/41'.
> thanks
Stopping processing here.

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

Bug#873557: mbedtls: CVE-2017-14032: authentication bypass

[James Cowgill]

Hi,

On 05/09/17 05:46, Salvatore Bonaccorso wrote:
> Hi James
> 
> Apologies for the delay!
> 
> On Fri, Sep 01, 2017 at 11:03:45AM +0100, James Cowgill wrote:
>> Hi,
>>
>> On 30/08/17 20:48, Salvatore Bonaccorso wrote:
>>> Control: retitle mbedtls: CVE-2017-14032: authentication bypass
>>>
>>> Hi
>>>
>>> On Tue, Aug 29, 2017 at 12:09:30AM +0100, James Cowgill wrote:
 Source: mbedtls
 Version: 2.1.2-1
 Severity: grave
 Tags: security

 Hi,

 The following security advisory was published for mbedtls:
 https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02
>>>
>>> MITRE has assigned CVE-2017-14032 for this issue.
>>
>> Does the attached patch look OK for stretch? I did a bit of testing with
>> it and it seems to fix the issue for me.
> 
> Thank you. Looks good to me (although without tests). If your are
> confident enough with the results of your testing, please go ahead
> with the upload to security-master. Keep in mind that you need to
> build with -sa to include the orig tarball, since it's new to dak on
> security-master.

Thanks! Uploaded. Upstream does have some tests for this, although
unfortunately it's accompanied by about 200K of test data.

James



signature.asc
Description: OpenPGP digital signature

Bug#873623: sudo: occasionally stalls infinitely instead of running command

[Christoph Berg]

Re: Thorsten Glaser 2017-08-29 
<150402112366.4803.7797051343542216967.report...@tglase.lan.tarent.de>
> Package: sudo
> Version: 1.8.21-1
> Severity: grave
> Justification: renders package unusable
> 
> After an upgrade from 1.8.20p2-1 sudo became somewhat unusable:

Confirmed. It's very easy to reproduce:

$ while date; do sudo true; done
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
Mi 6. Sep 19:42:54 CEST 2017
^CMi 6. Sep 19:42:58 CEST 2017
Mi 6. Sep 19:42:58 CEST 2017
^CMi 6. Sep 19:42:59 CEST 2017

strace: Process 20436 attached
restart_syscall(<... resuming interrupted poll ...>

Christoph

Processed: severity of 874065 is serious

[Debian Bug Tracking System]

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

> severity 874065 serious
Bug #874065 [src:unrar-free] unrar-free: Should unrar-free be removed from the 
archive? Alternatives (libarchive) exist; unmaintained upstream; has security 
issues
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Emmanuel Bourg]

Le 6/09/2017 à 18:56, Matthias Klose a écrit :

>> - remove the suffix from the version in the pom
> 
> doesn't work
> 
>> - remove the --has-package-version flag
> 
> doesn't work

You did that on libsejda-io-java right?

Processed: Re: unrar-free: CVE-2017-14120: directory traversal vulnerability

[Debian Bug Tracking System]

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

> tags 874059 + patch
Bug #874059 [src:unrar-free] unrar-free: CVE-2017-14120: directory traversal 
vulnerability
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#874059: unrar-free: CVE-2017-14120: directory traversal vulnerability

[Chris Lamb]

Hi,

Updated patch attached; I forgot to add shunit2 to the autopkgtest
dependencies.

Apologies for the noise.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/tests/0001-smoketest b/debian/tests/0001-smoketest
new file mode 100755
index 000..be5e756
--- /dev/null
+++ b/debian/tests/0001-smoketest
@@ -0,0 +1,35 @@
+#!/bin/sh
+#
+# Simple smoketest of unrar extraction
+
+setUp() {
+   uudecode >archive.rar 

Bug#874059: unrar-free: CVE-2017-14120: directory traversal vulnerability

[Chris Lamb]

tags 874059 + patch
thanks

Patch attached. 

It includes autopkgtests checking this CVE and a smoketest of a
regular (ie. non-exploit) extraction to prevent a regression.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/tests/0001-smoketest b/debian/tests/0001-smoketest
new file mode 100755
index 000..be5e756
--- /dev/null
+++ b/debian/tests/0001-smoketest
@@ -0,0 +1,35 @@
+#!/bin/sh
+#
+# Simple smoketest of unrar extraction
+
+setUp() {
+   uudecode >archive.rar 

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Matthias Klose]

On 06.09.2017 15:08, Emmanuel Bourg wrote:
> Le 6/09/2017 à 14:51, Matthias Klose a écrit :
> 
>> rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>=
>> 1.1.3.RELEASE)
>>
>> $ dpkg -I ../libsambox-java_1.0.34-1_all.deb | grep Depends
>>  Depends: libcommons-io-java, libfontbox2-java (>= 2.0.7), libsejda-io-java 
>> (>=
>> 1.1.3.RELEASE), libslf4j-java (>= 1.7.25)
> 
> This is an issue with libsejda-io-java, the --has-package-version flag
> was mistakenly used [1]. This led maven-debian-helper to think that it
> could use the version in the pom as a version constraint at the package
> level, which is wrong in this case due to the ".RELEASE" suffix (this
> behavior was broken before maven-debian-helper 2.2, see #862894).
> 
> The solution is to either:
> - add the ".RELEASE" suffix to the package version

I didn't try that.

> - remove the suffix from the version in the pom

doesn't work

> - remove the --has-package-version flag

doesn't work

Matthias

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Uwe Kleine-König]

Hello Christopher,

On Wed, Sep 06, 2017 at 11:18:04AM -0400, Christopher Li wrote:
> On Wed, Sep 6, 2017 at 10:44 AM, Uwe Kleine-König  
> wrote:
> > and while it's ok to test the core stuff and not wanting the system
> > includes to interfere, there should also be tests that check "ordinary"
> > userspace programs which naturally depend on the system headers.
> 
> There is one. The "selfcheck" target was checking sparse on its own
> source file. That will definitively use the system header file. However,
> there are some warning trigger in the system header file can't be fixed
> in the sparse source code. It need to change the system header to make
> some warning go away, or disable that warning.
> 
> >
> > No, it's not solved. But given that it is somehow known that sparse
> > (without cgcc) fails to work well on userspace stuff, I think the
> > following would be fine for the Debian side:
> >
> >  a) let horst use cgcc instead of sparse
> >  b) downgrade bug to important (or even normal) pointing out that
> > cgcc should be used for userspace programs
> 
> That seems to be the right thing to do for now. That is until
> sparse are smarter on user space header regarding architecture stuff.

ok, Antoine, can you talk to the horst people and ask them to switch to
cgcc then?

> > For sparse it would be cool to:
> >
> >  c) drop the #weak_define of __amd64__ to make this "problem" more
> > apparent. (Assuming this doesn't break e.g. a kernel build.)
> 
> You mean remove define of "__x86_64__".

ack.

> It will likely break some other stuff. For the record the "selfcheck" target
> already using cgcc. We still need to fix the breakage.
> 
> Any suggestion how to test sparse running on other platform headfile
> without have to get access to ppc64 for example? I think that is the biggest
> obstacle right now. I can make some changes, but I don't have a good way
> to test it other than x86 platform.

There is https://dsa.debian.org/doc/guest-account/ which would give you
the possibility to access some Debian machines. Other than that I intend
to upload 0.5.1 to Debian soon and then can provide you links to build
failures in the build server farm :-) And if you have a patch, I can
volunteer to make the test monkey for you.

> >  d) fix the test suite, at least mark the tests that are expected to
> > fail on !x86 as such to make $(make check) succeed. (Otherwise I'd
> > have to disable or ignore the testsuite which isn't that great.)
> 
> We can make the test-suite not depend on system header files.
> That seems to be the right think to do. I also send out a patch
> to let the llvm back end test-suite use cgcc last week. Removing
> system header usage in test suite is better.

Testing that patch is on my todo list.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Christopher Li]

On Wed, Sep 6, 2017 at 10:44 AM, Uwe Kleine-König  
wrote:
>
> and while it's ok to test the core stuff and not wanting the system
> includes to interfere, there should also be tests that check "ordinary"
> userspace programs which naturally depend on the system headers.
>

There is one. The "selfcheck" target was checking sparse on its own
source file. That will definitively use the system header file. However,
there are some warning trigger in the system header file can't be fixed
in the sparse source code. It need to change the system header to make
some warning go away, or disable that warning.

>
> No, it's not solved. But given that it is somehow known that sparse
> (without cgcc) fails to work well on userspace stuff, I think the
> following would be fine for the Debian side:
>
>  a) let horst use cgcc instead of sparse
>  b) downgrade bug to important or even normal pointing out that cgcc
> should be used for userspace programs

That seems to be the right thing to do for now. That is until
sparse are smarter on user space header regarding architecture stuff.

> For sparse it would be cool to:
>
>  c) drop the #weak_define of __amd64__ to make this "problem" more
> apparent. (Assuming this doesn't break e.g. a kernel build.)

You mean remove define of "__x86_64__".

It will likely break some other stuff. For the record the "selfcheck" target
already using cgcc. We still need to fix the breakage.

Any suggestion how to test sparse running on other platform headfile
without have to get access to ppc64 for example? I think that is the biggest
obstacle right now. I can make some changes, but I don't have a good way
to test it other than x86 platform.

>  d) fix the test suite, at least mark the tests that are expected to
> fail on !x86 as such to make $(make check) succeed. (Otherwise I'd
> have to disable or ignore the testsuite which isn't that great.)

We can make the test-suite not depend on system header files.
That seems to be the right think to do. I also send out a patch
to let the llvm back end test-suite use cgcc last week. Removing
system header usage in test suite is better.

Chris

Bug#869581: marked as done (libzstd examples not redistributable)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 15:13:57 +
with message-id 
and subject line Bug#869581: fixed in libzstd 1.3.1+dfsg-1
has caused the Debian Bug report #869581,
regarding libzstd examples not redistributable
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.)


-- 
869581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libzstd
Version: 1.1.2-1
Severity: serious
Tags: Upstream
Justification: Fails DFSG#6: examples cannot be used for commercial purposes
Control: forwarded -1 https://github.com/facebook/zstd/issues/774

Dear Maintainer,

The files in 'examples' in the source package cannot be shipped in the 'main'
part of the archive as they are not freely reusable by others.

  The examples provided by Facebook are for non-commercial testing and 
evaluation
  purposes only. Facebook reserves all rights not expressly granted.

  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
  FACEBOOK BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
  ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
  WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

cheers
Stuart


-- System Information:
Debian Release: 9.1
  APT prefers proposed-updates
  APT policy: (550, 'proposed-updates'), (500, 'stable-debug'), (500, 
'stable'), (60, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libzstd
Source-Version: 1.3.1+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libzstd 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 15:29:29 +0200
Source: libzstd
Binary: libzstd-dev libzstd1 zstd
Architecture: source
Version: 1.3.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libzstd-dev - fast lossless compression algorithm -- development files
 libzstd1   - fast lossless compression algorithm
 zstd   - fast lossless compression algorithm -- CLI tool
Closes: 869581
Changes:
 libzstd (1.3.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version
   * Exclude examples from upstream tarball
 Closes: #869581
   * debhelper 10
   * cme fix dpkg-control
   * Standards-Version: 4.1.0 (no changes needed)
   * Fix copyright
Checksums-Sha1:
 2ef7751c312048b53d54525f6fa412e6ad414a19 2114 libzstd_1.3.1+dfsg-1.dsc
 f4225883cb762ce2622b5fcde8e007e0eb4c25e6 1016592 libzstd_1.3.1+dfsg.orig.tar.xz
 b4e64e72070654ac9b326cffadf2e56959f4c55b 9740 
libzstd_1.3.1+dfsg-1.debian.tar.xz
 50224cf6993c3ff402e19699df791d002c613e02 13473 
libzstd_1.3.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 ac2e1de6edfb270cbec7adea305213f419cf768ac2932e7337893a40d8e4afde 2114 
libzstd_1.3.1+dfsg-1.dsc
 ee03aa78734e7019b77e72b898b3bae3456e97584ea7b05e5c2f9853fdad142c 1016592 
libzstd_1.3.1+dfsg.orig.tar.xz
 84df76bb43002ae0758f44d15d84479f05a20a0e8d586a8d7554740482b39371 9740 
libzstd_1.3.1+dfsg-1.debian.tar.xz
 f4db53b6fd9a10a712c844c40931259e6e3de1bc5d6f407abbc0b488498a50f8 13473 
libzstd_1.3.1+dfsg-1_source.buildinfo
Files:
 8cc624aad60c7db7abcd35e73d697cb3 2114 libs optional libzstd_1.3.1+dfsg-1.dsc
 c0b21ce1cf2ada943ae539bf84a8ba05 1016592 libs optional 
libzstd_1.3.1+dfsg.orig.tar.xz
 e20c72dc47c8ed047eb9af765d121d48 9740 libs optional 
libzstd_1.3.1+dfsg-1.debian.tar.xz
 0f1a20177f10617130d06e4e75b7151b 13473 libs optional 
libzstd_1.3.1+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE--

Bug#871158: marked as done (apitrace: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 15:05:44 +
with message-id 
and subject line Bug#871158: fixed in apitrace 7.1+git20170623.d38a69d6+repack-2
has caused the Debian Bug report #871158,
regarding apitrace: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
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.)


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/cc -g -O2 
> -fdebug-prefix-map=/<>/apitrace-7.1+git20170623.d38a69d6+repack=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -Wl,-z,relro  -rdynamic 
> CMakeFiles/cmTC_14f95.dir/CheckSymbolExists.c.o  -o cmTC_14f95 
> CMakeFiles/cmTC_14f95.dir/CheckSymbolExists.c.o: In function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
>  undefined reference to `pthread_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/05/apitrace_7.1+git20170623.d38a69d6+repack-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
apitrace, 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.
Timo Aaltonen  (supplier of updated apitrace 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 17:10:50 +0300
Source: apitrace
Binary: apitrace apitrace-gui apitrace-tracers
Architecture: source
Version: 7.1+git20170623.d38a69d6+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Description:
 apitrace   - tools for debugging OpenGL applications and drivers - cli fronten
 apitrace-gui - tools for debugging OpenGL applications and drivers - graphical 
f
 apitrace-tracers - tools for debugging OpenGL applications and drivers - 
application
Closes: 871158
Changes:
 apitrace (7.1+git20170623.d38a69d6+repack-2) unstable; urgency=medium
 .
   * fix-gcc7-ftbfs.diff: Fix build with gcc7. (Closes: #871158)
Checksums-Sha1:
 32fb435c2068f3641be65b82e8e8bd1705e16c49 2413 
apitrace_7.1+git20170623.d38a69d6+repack-2.dsc
 ead8571899521fa86915be5c46dabad48187755c 6612 
apitrace_7.1+git20170623.d38a69d6+repack-2.debian.tar.xz
Checksums-Sha256:
 385def43a5436ef92d7911fcd20e620e63a5ecb13b4142df87ea33437b4b93c9 2413 
apitrace_7.1+git20170623.d38a69d6+repack-2.dsc
 59c80061b0149803e1c57b66c908799f6a07df9bae91a18a7551e29cad335550 6612 
apitrace_7.1+git20170623.d38a69d6+repack-2.debian.tar.xz
Files:
 040aeda15bec6f20bcc63848ede54b54 2413 graphics optional 
apitrace_7.1+git20170623.d38a69d6+repack-2.dsc
 d99a277edd95629be4ec36a02bee65b2 6612 graphics optional 
apitrace_7.1+git20170623.d38a69d6+repack-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZsAIwAAoJEMtwMWWoiYTcp9EP/1j/p7oZvgNbnB1HMpyJfDrC
yP1c3Rb5Ci+wTpuoUiw742A46vBTYAh/l3r9VB97GtoWrAWlf4Mh4056zf3KtsGa
HZRXAWZItz/5n7R1Th1Hl5sELGDaVymrFhuOiW9KdN+nuVjzFJXPGWhhz4eXcgH7
9GEa15PW6IVyXVdviKzaA1rIbdHSMKeyDCRnsrLgDB5nUkC26KYS3mw18itGS8M9
MivfwNQ3DiUR1aQryKD9aqvcdwLiTPc5Un1Llr4wMt/D1dW6VNg4pqBr+S03KExH
7aW+UY2aT7Wb1ZGEBqQO9BtgWV42

Processed: Re: Bug#860476: [mpi4py] Unstated dependency on libopenmpi-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #860476 [mpi4py] [mpi4py] Unstated dependency on libopenmpi-dev
Severity set to 'serious' from 'normal'
> found -1 2.0.0-2.1
Bug #860476 [mpi4py] [mpi4py] Unstated dependency on libopenmpi-dev
There is no source info for the package 'mpi4py' at version '2.0.0-2.1' with 
architecture ''
Unable to make a source version for version '2.0.0-2.1'
Marked as found in versions 2.0.0-2.1.

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

Bug#789927: Anthy library breakage

[Osamu Aoki]

Hi,

On Tue, Sep 05, 2017 at 09:00:52AM +0900, NIIBE Yutaka wrote:
> Osamu Aoki  wrote:
> 
> Thanks.  Now, I understand (I didn't know that fully).  I should have
> learned before uploading to Sid.


After I failed to make ibus transition like your case, I made a memo as:
 https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#libnames

This sites are useful:
 https://debconf4.debconf.org/talks/dependency-hell/img0.html
 https://wiki.debian.org/Teams/ReleaseTeam/Transitions

I will check the whole situation a bit carefully to make recommendation
later, if I can.

If upstream didn't bump so name for this UTF-8 change, that complicates
things.  Did he?

> I have been using Anthy since its birth, but I only use through Emacs
> with egg.  Even if I don't use, I should be careful when I touch Debian
> package.
> 
> Today, the Emacs module egg requires total rewrite for Emacs 25, due to
> the change of Emacs (display property thing).  I was considering making
> a loadable module for Emacs for Anthy.  That was another pressure.

I see.  I may need to update im-config once you do this.

> Any suggestions are welcome.  It seems for me that it would be better
> to change the -dev package name.

I think "Use the versioned -dev package names: libfoo7-dev and
libfoo8-dev" is the way to go for this case.  But I need to check more.

Use the versioned -dev package names: libfoo7-dev and libfoo8-dev

This is the special case.
Two versions of the library source packages are allowed simultaneously in the 
archive.

 * Make all dependent packages depend on libfoo-dev.
 * Make both libfoo7-dev and libfoo8-dev provide libfoo-dev.
 * The source package needs to be renamed as libfoo7-7.0.tar.gz and 
libfoo8-8.0.tar.gz respectively from libfoo-?.0.tar.gz.
 * The package specific install file path including libfoo7 and libfoo8 
respectively for header files etc. needs to be chosen to make them 
co-installable.

Regards,

Osamu

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Uwe Kleine-König]

[readding people to Cc assuming that's ok]

Hello Luc,

On Mon, Sep 04, 2017 at 10:36:47PM +0200, Luc Van Oostenryck wrote:
> On Mon, Sep 4, 2017 at 10:57 AM, Uwe Kleine-König  
> wrote:
> > On 09/03/2017 11:14 PM, Luc Van Oostenryck wrote:
> >> On Fri, Sep 1, 2017 at 9:02 AM, Josh Triplett  
> >> wrote:
> >>> Related to that: while it would mean we couldn't necessarily just rely
> >>> entirely on GCC's definitions for a target platform, I think in an ideal
> >>> world we could have a sparse binary that understood *all* target
> >>> platforms at once, such that you could ask Sparse on x86_64 to "compile"
> >>> as though targeting any arbitrary architecture. That would also have the
> >>> major advantage of making it easy to run the Sparse testsuite for
> >>> *every* target architecture without needing compilers for every such
> >>> architecture.
> >>
> >> I really think that the testsuite should not depend on system or library
> >> header.
> >
> > Assuming it's intended that sparse should be able to check userspace
> > programs, I don't agree here.
> 
> I understand this.
> I'll explain a bit better my point of view.
> First, I make a distinction between 'sparse core functionalities' and
> general usage.
> I was talking about this core usage and the testsuite is currently for this 
> core
> usage too.

and while it's ok to test the core stuff and not wanting the system
includes to interfere, there should also be tests that check "ordinary"
userspace programs which naturally depend on the system headers.

> Asking for the testsuite to not depends on system or library header is exactly
> the same as GCC people asking bug reports to be done on pre-processed file
> (so that they focus on the core problem and not some problem with an header).
> This, of course, doesn't mean that GCC should only be used on standalone
> source files nor that GCC shouldn't be tested on real code, using
> system headers.
> It's just something different.
> 
> So to answer to your objection: yes, you're right but it should be done in 
> some
> specific tests, not the core ones.

ah, we agree. Fine.

> Secondly, about "intended to check userspace programs":
> It's clear that sparse's main use is for the kernel, but it's also
> clear that it can
> and is used on other (userspace) projects.
> However, as you have seen yourself, you can't use sparse as is and expect
> to work on any environment, on any architecture. Even for the kernel it 
> doesn't:
> each architecture has to specify a few flags (like -m32/-m64) and a few 
> defines
> (-D__arm__, ...). For userspace, cgcc can do a part of this job for you.
> 
> Josh proposal to have what I called a 'universal' sparse, won't solve this,
> on the contrary.
> Compilers eschew part of this problem by having to configure the build
> 
> I'm all in favor to move cgcc logic to sparse and/or it's build system so that
> *for a native build* it can be used as-is in most cases.
> This would solve your problem, I think.
> 
> BTW, sorry I didn't follow last week but is your problem solved now?

No, it's not solved. But given that it is somehow known that sparse
(without cgcc) fails to work well on userspace stuff, I think the
following would be fine for the Debian side:

 a) let horst use cgcc instead of sparse
 b) downgrade bug to important or even normal pointing out that cgcc
should be used for userspace programs

For sparse it would be cool to:

 c) drop the #weak_define of __amd64__ to make this "problem" more
apparent. (Assuming this doesn't break e.g. a kernel build.)
 d) fix the test suite, at least mark the tests that are expected to
fail on !x86 as such to make $(make check) succeed. (Otherwise I'd
have to disable or ignore the testsuite which isn't that great.)
 
Best regards
Uwe


signature.asc
Description: PGP signature

Processed: aggressive polling by libmtp resulting in multiple messages.

[Debian Bug Tracking System]

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

> reassign 874216 gvfs-backends
Bug #874216 [android-libadb] (no subject)
Bug reassigned from package 'android-libadb' to 'gvfs-backends'.
No longer marked as found in versions 
android-platform-system-core/1:7.0.0+r33-2.
Ignoring request to alter fixed versions of bug #874216 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#874216: aggressive polling by libmtp resulting in multiple messages.

[shirish शिरीष]

reassign 874216 gvfs-backends
thanks

Hi there,

Thank you for maintaining libmtp all these years and at times it has
been a lifesaver.

Although now, It seems aggresive polling is being used by libmtp as I get
notifications of denial as shared in screenshots and there are a
multiple ones at that.

The only change I did (and this is months ago) was add developer
options and changed from MTP to charging options. I am on Android 6.0
marshmallow latest updated version. The phone is a Galaxy J5.

These are the options it shows me -

Transferring media files through MTP - This seems to be only one
way from phone to PC and not the other way around :(

Transferring images or files through a PTP connection (guess it's
a lower bandwidth connection)

Connecting MIDI devices

Charging.

and am using the last option charging. Is there a way to minimize
libmtp polling for usb devices or just have to live with that.

In 5 minutes I got about 40-50 notifications or copies of the
notifications as seen above,  Sharing another screenie as before. m

I am on Android Marshmallow 6.0 (latest update) and the phone is a
Samsung Galaxy J5 . Please let me know if any more info. is needed.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#871158: apitrace: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create'

[Timo Aaltonen]

On 07.08.2017 00:22, Lucas Nussbaum wrote:
> Source: apitrace
> Version: 7.1+git20170623.d38a69d6+repack-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170805 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> /usr/bin/cc -g -O2 
>> -fdebug-prefix-map=/<>/apitrace-7.1+git20170623.d38a69d6+repack=. 
>> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
>> -D_FORTIFY_SOURCE=2   -Wl,-z,relro  -rdynamic 
>> CMakeFiles/cmTC_14f95.dir/CheckSymbolExists.c.o  -o cmTC_14f95 
>> CMakeFiles/cmTC_14f95.dir/CheckSymbolExists.c.o: In function `main':
>> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
>>  undefined reference to `pthread_create'
>> collect2: error: ld returned 1 exit status

With current sid I don't get that error, but this instead:

Generating MOC predefs moc_predefs.h
AutoMoc: Error: moc predefs generation command failed
AutoMoc: Command:
/usr/bin/c++ -dM -E -c
/usr/share/cmake-3.9/Modules/CMakeCXXCompilerABI.cpp
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/obj-x86_64-linux-gnu/gui
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/gui
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/obj-x86_64-linux-gnu/gui/qapitrace_autogen/include
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/thirdparty/khronos
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/compat
-I/usr/src/gtest/include
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/lib/trace
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/lib/os
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/lib/image
-I/<>/apitrace-7.1+git20170623.d38a69d6+repack/lib/ubjson
-I/usr/include/x86_64-linux-gnu/qt5
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
-I/usr/include/x86_64-linux-gnu/qt5/QtGui
-I/usr/include/x86_64-linux-gnu/qt5/QtCore
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/usr/include
-DHAVE_BACKTRACE=1 -DHAVE_READPROC_H -DHAVE_X11 -DQT_CORE_LIB
-DQT_FORCE_ASSERTS -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -D_GNU_SOURCE -D__STDC_FORMAT_MACROS
-D__STDC_LIMIT_MACROS -nn
AutoMoc: Command output:
c++: error: unrecognized command line option ‘-nn’; did you mean ‘-Qn’?



-- 
t

Bug#874337: marked as done (src:gr-iio: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 13:22:19 +
with message-id 
and subject line Bug#874337: fixed in gr-iio 0.2.36-2
has caused the Debian Bug report #874337,
regarding src:gr-iio: maintainer address bounces
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.)


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

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Matthias Klose]

Package: src:libsambox-java
Version: 1.0.34-1
Severity: serious
Tags: sid buster

rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>=
1.1.3.RELEASE)

$ dpkg -I ../libsambox-java_1.0.34-1_all.deb | grep Depends
 Depends: libcommons-io-java, libfontbox2-java (>= 2.0.7), libsejda-io-java (>=
1.1.3.RELEASE), libslf4j-java (>= 1.7.25)

Bug#865851: drf-extensions FTBFS with Django 1.11

[Herbert Fortes]

On Sun, 25 Jun 2017 11:38:27 +0300 Adrian Bunk wrote:
> Source: drf-extensions
> Version: 0.3.1-1
> Severity: serious
> Tags: buster sid

[...]

> File "/usr/lib/python3/dist-packages/django_filters/fields.py", line 14, in
> from .widgets import RangeWidget, LookupTypeWidget, CSVWidget
> File "/usr/lib/python3/dist-packages/django_filters/widgets.py", line 13, in
> from django.forms.widgets import flatatt
> ImportError: cannot import name 'flatatt'
> ...

This bug should be sent to django-filter[0]. And
it is fixed[1].

[0] - https://packages.qa.debian.org/d/django-filter.html

[1] - 
https://anonscm.debian.org/cgit/python-modules/packages/django-filter.git/commit/?h=upstream/1.0.4&id=db8ca74ce3e50e30dbfe92d902740ce4ba4708e4

This bug can be closed.



Regards,
Herbert

Bug#872263: [rb-general] Bug#872263: linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports

[Ximin Luo]

Ben Hutchings:
> On Wed, 2017-08-16 at 17:51 +, Daniel Shahaf wrote:
>> Chris Lamb wrote on Wed, 16 Aug 2017 07:54 -0700:
 Still, it seems like there is a wider problem here: if the exact same
 code is ever built in two unrelated packages then their debug info
 packages will conflict even if the regular binary packages don't.
>>>
>>> I've seen this outside of reproducibility where I was shipping the exact
>>> same binary in the redis-server and redis-sentinel packages (it changes
>>> behaviour based on argv[0]).
>>>
>>> The -dbgsym packages then conflicted for the same reason.
>>
>> Stupid question, but why _do_ the packages conflict?  Couldn't the
>> package manager notice that the file versions that would be installed by
>> each package are equivalent [= same name, chmod, and bit-by-bit
>> contents], and keep the file existing so long as _either_ package is
>> installed?
> 
> In the case of the kernel packages, the identical binaries (vDSOs) are
> emebedded in kernel images with different filenames.  The identical
> debug info is installed with different filenames.  But the symlinks to
> them underneath /usr/lib/debug/.build-id therefore have the same (hash-
> based) name and *different* content.
> 

Could you reverse the symlink? So the target (the actual file) is in 
/usr/lib/debug and so both packages will have the same file installed at that 
path.

Then perhaps we could ask dpkg to add an exception for this Breaks/Replaces 
annotation for files under /usr/lib/debug when the file contents are the same 
(or just blanket-allow this case for all paths).

When the policy was originally written it would have taken extra technical 
effort to refcount which packages referred to the same file+filepath, but 
(IIRC) this logic has since been added in order to deal gracefully with 
Multi-Arch. Maybe it's time to extend it to more things?

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#874417: marked as done (sugar-icon-theme, sugar-themes: fails to upgrade from 'stretch' - trying to overwrite ...)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 11:19:44 +
with message-id 
and subject line Bug#874417: fixed in sugar-artwork 0.110.0-3
has caused the Debian Bug report #874417,
regarding sugar-icon-theme, sugar-themes: fails to upgrade from 'stretch' - 
trying to overwrite ...
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.)


-- 
874417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: sugar-artwork
Source-Version: 0.110.0-3

We believe that the bug you reported is fixed in the latest version of
sugar-artwork, 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.
Jonas Smedegaard  (supplier of updated sugar-artwork 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: Wed, 06 Sep 2017 13:03:20 +0200
Source: sugar-artwork
Binary: sugar-themes sugar-icon-theme gtk2-engines-sugar
Architecture: source
Version: 0.110.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team 
Changed-By: Jonas Smedegaard 
Description:
 gtk2-engines-sugar - Sugar Learning Platform - GTK+ 2.x theme engine
 sugar-icon-theme - Sugar Learning Platform - icon theme
 sugar-themes - Sugar Learning Platform - artwork
Closes: 874417
Changes:
 sugar-artwork (0.110.0-3) unstable; urgency=medium
 .
   * Fix revive transitional replaces/breaks for sugar-artwork-0.88:
 Still needed for stretch.
 Closes: Bug#874417. Thanks to Andreas Beckmann.
Checksums-Sha1:
 61240681dd321c7f2c8c5c4bb87cd411cc8ed603 2313 sugar-artwork_0.110.0-3.dsc
 833720085a734a53d054b638052ee4f86d713f20 12580 
sugar-artwork_0.110.0-3.debian.tar.xz
 cddf4a72ed2b7c74e08f9bcec61fdc122d6fe5f0 15164 
sugar-artwork_0.110.0-3_amd64.buildinfo
Checksums-Sha256:
 e0adac7fc8e84e1f557465a6202bec8ed3c2f855a70f8eb8b1ed29b912be969c 2313 
sugar-artwork_0.110.0-3.dsc
 5410211a96ded1683a4f1b2e40dcd3d1f6a0c1db6b58a67c1192f85b78004ec8 12580 
sugar-artwork_0.110.0-3.debian.tar.xz
 81954541554d30ac7a8c508782e850eceda09c3ccc5caa78f3569c6dd8f88dcd 15164 
sugar-artwork_0.110.0-3_amd64.buildinfo
Files:
 50766b9169cb7c7333bb6a6970328bb3 2313 x11 optional sugar-artwork_0.110.0-3.dsc
 69a18d74a6413fb269f6981c1d377a36 12580 x11 optional 
sugar-artwork_0.110.0-3.debian.tar.xz
 834372c3e83710423d1783d26563db6f 15164 x11 optional 
sugar-artwork_0.110.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmv178ACgkQLHwxRsGg

Bug#842815: Help needed for HDF5 1.10 transition of libsis-jhdf5-java

[Andreas Tille]

Hello Bernd,

On Wed, 23 Nov 2016 06:54:21 +0100, you wrote
> the migration of JHDF5 to HDF5 1.10 is ongoing and mostly depend on me
> having a block of time I can spend on it. Your analysis of the work that
> needs to be done is right from what I can see. The plan is to switch to
> using the JNI library from the HDF group wherever possible (it may still
> be necessary to have a small JNI library though as some calls appear to
> be missing).
> 
> I will keep you updated.

Is there any news, may be only a patch for the existing version we
could try to fix the Debian package?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#873166: marked as done (imms: FTBFS against audacious 3.9)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 10:38:23 +
with message-id 
and subject line Bug#874252: Removed package(s) from unstable
has caused the Debian Bug report #873166,
regarding imms: FTBFS against audacious 3.9
to be marked as done.

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

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


-- 
873166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imms
Version: 3.1.0~svn301-5
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

imms fails to build against audacious 3.9:
| g++   -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fno-rtti -std=c++11 `pkg-config glib-2.0 
--cflags` -Wdate-time -D_FORTIFY_SOURCE=2  -O3 -Wall -fPIC -D_REENTRANT -I../ 
-I../immscore -I../clients -c  ../clients/audacious/audplugin.cc -o  audplugin.o
| In file included from ../clients/clientstub.h:22:0,
|  from ../clients/audacious/audplugin.cc:36:
| ../immscore/giosocket.h: In member function 'void GIOSocket::close()':
| ../immscore/giosocket.h:74:35: warning: 'void 
g_io_channel_close(GIOChannel*)' is deprecated: Use 'g_io_channel_shutdown' 
instead [-Wdeprecated-declarations]
|  g_io_channel_close(con);
|^
| In file included from /usr/include/glib-2.0/glib.h:54:0,
|  from ../immscore/giosocket.h:22,
|  from ../clients/clientstub.h:22,
|  from ../clients/audacious/audplugin.cc:36:
| /usr/include/glib-2.0/glib/giochannel.h:183:11: note: declared here
|  void  g_io_channel_close(GIOChannel*channel);
|^~
| In file included from ../clients/clientstub.h:22:0,
|  from ../clients/audacious/audplugin.cc:36:
| ../immscore/giosocket.h: In member function 'bool 
GIOSocket::write_event(GIOCondition)':
| ../immscore/giosocket.h:119:66: warning: 'GIOError 
g_io_channel_write(GIOChannel*, const gchar*, gsize, gsize*)' is deprecated: 
Use 'g_io_channel_write_chars' instead [-Wdeprecated-declarations]
|  GIOError e = g_io_channel_write(con, (char*)outp, len, &n);
|   ^
| In file included from /usr/include/glib-2.0/glib.h:54:0,
|  from ../immscore/giosocket.h:22,
|  from ../clients/clientstub.h:22,
|  from ../clients/audacious/audplugin.cc:36:
| /usr/include/glib-2.0/glib/giochannel.h:172:11: note: declared here
|  GIOError  g_io_channel_write(GIOChannel*channel,
|^~
| In file included from ../clients/clientstub.h:22:0,
|  from ../clients/audacious/audplugin.cc:36:
| ../immscore/giosocket.h: In member function 'bool 
GIOSocket::read_event(GIOCondition)':
| ../immscore/giosocket.h:152:73: warning: 'GIOError 
g_io_channel_read(GIOChannel*, gchar*, gsize, gsize*)' is deprecated: Use 
'g_io_channel_read_chars' instead [-Wdeprecated-declarations]
|  GIOError e = g_io_channel_read(con, buf, sizeof(buf) - 1, &n);
|  ^
| In file included from /usr/include/glib-2.0/glib.h:54:0,
|  from ../immscore/giosocket.h:22,
|  from ../clients/clientstub.h:22,
|  from ../clients/audacious/audplugin.cc:36:
| /usr/include/glib-2.0/glib/giochannel.h:166:13: note: declared here
|  GIOErrorg_io_channel_read   (GIOChannel*channel,
|  ^
| ../clients/audacious/audplugin.cc: In function 'std::__cxx11::string 
imms_get_playlist_item(int)':
| ../clients/audacious/audplugin.cc:87:14: error: 'aud_playlist_get_playing' 
was not declared in this scope
|  int pl = aud_playlist_get_playing();
|   ^~~~
| ../clients/audacious/audplugin.cc:87:14: note: suggested alternative: 
'aud_drct_get_playing'
|  int pl = aud_playlist_get_playing();
|   ^~~~
|   aud_drct_get_playing
| ../clients/audacious/audplugin.cc:88:18: error: 
'aud_playlist_entry_get_filename' was not declared in this scope
|  String uri = aud_playlist_entry_get_filename(pl, at);
|   ^~~
| ../clients/audacious/audplugin.cc:88:18: note: suggested alternative: 
'aud_plugin_get_basename'
|  String uri = aud_playlist_entry_get_filename(pl, at);
|   ^~~
|   aud_plugin_get_basename
| .

Bug#785518: marked as done (fprobe-ulog: FTBFS on linux >= 3.17(?): linux/netfilter_ipv4/ipt_ULOG.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 10:36:02 +
with message-id 
and subject line Bug#874055: Removed package(s) from unstable
has caused the Debian Bug report #785518,
regarding fprobe-ulog: FTBFS on linux >= 3.17(?): 
linux/netfilter_ipv4/ipt_ULOG.h: 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.)


-- 
785518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fprobe-ulog
Version: 1.1-7.3
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The package fails to build due to a missing header.

There are patches for similar problems in other netfilter projects:
http://git.netfilter.org/ulogd2/commit/?id=30e24dbfc7a8644e29664070e8c16e5c3997f87e

Build log excerpt:

gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/libipulog/include
  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security
  -Wall -D_BSD_SOURCE -D_REENTRANT -DWALL -W -Wall -c libipulog.c

In file included from libipulog.c:32:0:
.../../src/libipulog/include/libipulog/libipulog.h:15:43:
fatal error: linux/netfilter_ipv4/ipt_ULOG.h: No such file or directory

 #include 
   ^
compilation terminated.
Makefile:208: recipe for target 'libipulog.o' failed


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

Kernel: Linux 3.19.0-16-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)

Versions of packages fprobe-ulog depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18

fprobe-ulog recommends no packages.

fprobe-ulog suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 1.1-7.3+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#853385: marked as done (einspline: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 10:40:01 +
with message-id 
and subject line Bug#874361: Removed package(s) from unstable
has caused the Debian Bug report #853385,
regarding einspline: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
./src/time_multi.c:1885: undefined reference to `eval_UBspline_3d_c_vgh'
time_multi.o: In function `time_3d_real_float_all':
./src/time_multi.c:1973: undefined reference to `eval_UBspline_3d_s'
./src/time_multi.c:2006: undefined reference to `eval_UBspline_3d_s_vgh'
time_multi.o: In function `time_3d_real_double_all':
./src/time_multi.c:2102: undefined reference to `eval_UBspline_3d_d'
./src/time_multi.c:2135: undefined reference to `eval_UBspline_3d_d_vgh'
time_multi.o: In function `time_3d_complex_double_all':
./src/time_multi.c:2228: undefined reference to `eval_UBspline_3d_z'
./src/time_multi.c:2282: undefined reference to `eval_UBspline_3d_z_vgh'
time_multi.o: In function `test_complex_double_vgh':
./src/time_multi.c:2357: undefined reference to `eval_UBspline_3d_z_vgh'
./src/time_multi.c:2408: undefined reference to `eval_UBspline_3d_z_vgh'
time_multi.o: In function `test_double':
./src/time_multi.c:2479: undefined reference to `eval_UBspline_3d_d'
./src/time_multi.c:2511: undefined reference to `eval_UBspline_3d_d'
time_multi.o: In function `test_double_vgh':
./src/time_multi.c:2583: undefined reference to `eval_UBspline_3d_d_vgh'
./src/time_multi.c:2638: undefined reference to `eval_UBspline_3d_d_vgh'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s_vgh'
./.libs/libeinspline.so: undefined reference to `eval_UBspline_3d_z_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_d'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_d_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s_vgl'
./.libs/libeinspline.so: undefined reference to `eval_UBspline_3d_z_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z_vgh'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_d_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c_vgh'
collect2: error: ld returned 1 exit status
Makefile:864: recipe for target 'time_multi' failed
make[3]: *** [time_multi] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:678: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/src'
Makefile:473: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit co

Bug#854733: Your mail

[Andreas Beckmann]

On Sat, 02 Sep 2017 10:23:40 +0100 Chris Lamb  wrote:
> Version: 1.30.4+dfsg-1

same here - please remove either the wrong found or fixed version to
unconfuse the bts.


Andreas

Bug#854272: Your mail

[Andreas Beckmann]

On Sat, 02 Sep 2017 10:23:19 +0100 Chris Lamb  wrote:
> Version: 1.30.4+dfsg-1

Is this bug found or fixed in that version? I'm confused (and the bts is
confused as well) since this is now marked as both found and fixed in
this version (and treated by the bts as "not fixed"). Please remove the
wrong one.


Andreas

Bug#253513: this is a bug

[Daniel Pocock]

According to policy

/usr/share/doc/debian-policy/policy.txt.gz

"Non-conformance with
 guidelines denoted by _should_ (or _recommended_) will generally be
 considered a bug, but will not necessarily render a package unsuitable
 for distribution."

and further down:

"If your package needs to know what hostname to use on (for example)
 outgoing news and mail messages which are generated locally, you
 should use the file `/etc/mailname'.  It will contain the portion
 after the username and `@' (at) sign for email addresses of users on
 the machine (followed by a newline)."

Note that policy uses the word "should" for mailname, so wishlist doesn't 
appear to be a suitable severity for this issue.

This bug is for the sender address, the merged bug #509810 is for the recipient 
address, so it is actually a different issue and it remains a wishlist item, 
I've unmerged them.

I've observed that on a freshly installed stretch system, the mailutils 
implementation of the mail command is now the default:
  
   /etc/alternatives/mail -> /usr/bin/mail.mailutils

while on older systems, it was bsd-mailx:

   /etc/alternatives/mail -> /usr/bin/bsd-mailx

and so it impacts every new install.  Therefore I've chosen the severity 
"serious" for this issue.

People can work around this issue with:

   $ sudo apt install bsd-mailx

As a consequence of this issue, when people send outgoing mail from a stretch 
system using the /usr/bin/mail command, the sender domain may not be what they 
expect and their mail may not even be accepted by their relay host.  If all 
their older Debian systems are running bsd-mailx this is an issue that will 
take them by surprise on newly built systems.

Even if upstream doesn't want to support /etc/mailname because they consider it 
a Debian thing, as mentioned in the earlier message in this bug, the Debian 
version should probably contain a patch or it should not be the default 
/usr/bin/mail.

Processed (with 1 error): mailname

[Debian Bug Tracking System]

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

> unmerge 253513
Bug #253513 [mailutils] mailutils: read /etc/mailname
Bug #509810 [mailutils] localhost To: should honor /etc/mailname on Debian
Disconnected #253513 from all other report(s).
> severity 253513 serious
Bug #253513 [mailutils] mailutils: read /etc/mailname
Severity set to 'serious' from 'wishlist'
> severity 509810 wishlist
Bug #509810 [mailutils] localhost To: should honor /etc/mailname on Debian
Ignoring request to change severity of Bug 509810 to the same value.
> retitle 253513 sender (From:) - policy specifies use of /etc/mailname on
Bug #253513 [mailutils] mailutils: read /etc/mailname
Changed Bug title to 'sender (From:) - policy specifies use of /etc/mailname 
on' from 'mailutils: read /etc/mailname'.
> Debian
Unknown command or malformed arguments to command.
> retitle 509810 unqualified recipient (To:) - use /etc/mailname on Debian
Bug #509810 [mailutils] localhost To: should honor /etc/mailname on Debian
Changed Bug title to 'unqualified recipient (To:) - use /etc/mailname on 
Debian' from 'localhost To: should honor /etc/mailname on Debian'.
>
End of message, stopping processing here.

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

Bug#874425: marked as done (soapdenovo2: please Build-Depend on rename)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 09:50:55 +
with message-id 
and subject line Bug#874425: fixed in soapdenovo2 241+dfsg-1
has caused the Debian Bug report #874425,
regarding soapdenovo2: please Build-Depend on rename
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.)


-- 
874425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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] 
--- End Message ---
--- Begin Message ---
Source: soapdenovo2
Source-Version: 241+dfsg-1

We believe that the bug you reported is fixed in the latest version of
soapdenovo2, 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.
Andreas Tille  (supplier of updated soapdenovo2 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 10:55:51 +0200
Source: soapdenovo2
Binary: soapdenovo2
Architecture: source amd64
Version: 241+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 soapdenovo2 - short-read assembly method to build de novo draft assembly
Closes: 874425
Changes:
 soapdenovo2 (241+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
   * Fix watch file
   * Standards-Version: 4.1.0 (no changes needed)
   * Build-Depends: rename
 Closes: #874425
   * Remove another binary from source
   * Symlinks to manpages
Checksums-Sha1:
 098834021cb33c8b41927db2e40a434b9d455540 2106 soapdenovo2_241+dfsg-1.dsc
 8b470b4478798eea2f8a876dc06452551dabf712 250180 
soapdenovo2_241+dfsg.orig.tar.xz
 ed801b01b8481d11f8145326520d256b671483df 8848 
soapdenovo2_241+dfsg-1.debian.tar.xz
 e71fd5f6ad0e27fcb72259212faf4f9bfe2c16d6 730508 
soapdenovo2-dbgsym_241+dfsg-1_amd64.deb
 c3ddcfbebffd5151e33a867a5515a9013a16873e 5771 
soapdenovo2_241+dfsg-1_amd64.buildinfo
 1fdcd31c7259226d2d8e7e6598d8913bd061bc1b 240996 
soapdenovo2_241+dfsg-1_amd64.deb
Checksums-Sha256:
 d2223e3f6f2a46215eebad3cff57281a04dd814451900147cc3916245626707a 2106 
soapdenovo2_241+dfsg-1.dsc
 0b6d64d95e250cfc11fceb75933f90f468d1b9f595c8d91ff250a0bd4ed12abd 250180 
soapdenovo2_241+dfsg.orig.tar.xz
 ed7d3a4a7169bf0a8b85644cc4e0949b45a160d06d8b9154cc6c80044bdf816c 8848 
soapdenovo2_241+dfsg-1.debian.tar.xz
 9ba1651492a2e13fec90eaa7388cebe52217ad8a1152a559c264ffb319e0795a 730508 
soapdenovo2-dbgsym_241+dfsg-1_amd64.deb
 751caf6a840b4a3a9609d6b3bfe2cd6053e391665a55d0400661d423a925f03b 5771 
soapdenovo2_241+dfsg-1_amd64.buildinfo
 0a2190c9db3b9f87e1373776bcfd093e892c441ab4ed2407f4977ea755d1f8fc 240996 
soapdenovo2_241+dfsg-1_amd64.deb
Files:
 fb86ad25bca220421bfc30ee101c3988 2106 science optional 
soapdenovo2_241+dfsg-1.dsc
 2d1eed939b424d2fe4adb81d7cc420ba 250180 science optional 
soapdenovo2_241+dfsg.orig.tar.xz
 c960eab7dcb31d4e9326c6b6ce32282d 8848 science optional 
soapdenovo2_241+dfsg-1.debian.tar.xz
 d18697a1973ecd838eb8c701f19e18d0 730508 debug extra 
soapdenovo2-dbgsym_241+dfsg-1_amd64.deb
 cc35f69417205c78acea8ef36aeb8c6b 5771 science optional 
soapdenovo2_241+dfsg-1_amd64.buildinfo
 4c17b3afa02acc68b09c237c744599fd 240996 science optional 
soapdenovo2_241+dfsg-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZr7+CAAoJEFeKBJTRxkbRWeoP/1R4FozYCYynpaR2mQYw0goY
dO+q62fWjotfEwn33OlOec5d+

Bug#874424: marked as done (soapdenovo: please Build-Depend on rename)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 09:50:45 +
with message-id 
and subject line Bug#874424: fixed in soapdenovo 1.05-4
has caused the Debian Bug report #874424,
regarding soapdenovo: please Build-Depend on rename
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.)


-- 
874424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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] 
--- End Message ---
--- Begin Message ---
Source: soapdenovo
Source-Version: 1.05-4

We believe that the bug you reported is fixed in the latest version of
soapdenovo, 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.
Andreas Tille  (supplier of updated soapdenovo 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 11:08:47 +0200
Source: soapdenovo
Binary: soapdenovo
Architecture: source amd64
Version: 1.05-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 soapdenovo - short-read assembly method to build de novo draft assembly
Closes: 874424
Changes:
 soapdenovo (1.05-4) unstable; urgency=medium
 .
   * Team upload
   * Moved packaging to Git
   * Build-Depends: rename
 Closes: #874424
   * Standards-Version: 4.1.0 (no changes needed)
Checksums-Sha1:
 bd2a23f89c9fc2ece324bce37fdaf96bfacf7dcd 1997 soapdenovo_1.05-4.dsc
 546dbe900252d8de5d3f17065e4592598c37cc2f 6596 soapdenovo_1.05-4.debian.tar.xz
 e899f54e31f5d02c80fa7ba6712d7d167aa7b000 14048 
soapdenovo-dbgsym_1.05-4_amd64.deb
 fcf8d473ce226010726ee7c98a3282b651e4e81f 5603 soapdenovo_1.05-4_amd64.buildinfo
 ddf1f8bdb4328592d43a14a9efb95498b55d5643 343802 soapdenovo_1.05-4_amd64.deb
Checksums-Sha256:
 14730b1bdf9b733ddc3ba7cb394640457ac9b1068767140bc361a56611a5a033 1997 
soapdenovo_1.05-4.dsc
 330e19f60bf7fa0ac038e05c761b3a66e157acca9558d21bb13761b5eb275669 6596 
soapdenovo_1.05-4.debian.tar.xz
 ea422f97a8efb3a47a1c88214e62e6b1fad5926de1c88d5e1a5b81e1c89e5cca 14048 
soapdenovo-dbgsym_1.05-4_amd64.deb
 a1216a2259d91e5f5958039a9f2fb6ea2f933502543d3b80c94a9318bbaf2f68 5603 
soapdenovo_1.05-4_amd64.buildinfo
 971735a4cd972a9a43c21bb9a955dc9d06d660390d275ea5d9008463e7ed2113 343802 
soapdenovo_1.05-4_amd64.deb
Files:
 6c1e13e052a6e9de80282e5b6c8f3cd2 1997 science optional soapdenovo_1.05-4.dsc
 2852ca28a592c48b9f34a7f416a12a11 6596 science optional 
soapdenovo_1.05-4.debian.tar.xz
 373164ba1e25eb03f65e89e264a37785 14048 debug extra 
soapdenovo-dbgsym_1.05-4_amd64.deb
 ec5addfd9366cce4cabb09723c8fbcd3 5603 science optional 
soapdenovo_1.05-4_amd64.buildinfo
 a693340906e9ffe1f97be8df304722ab 343802 science optional 
soapdenovo_1.05-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZr7+hAAoJEFeKBJTRxkbRTZgP/jjiHmPmwwv70zQe5fYci5lf
L7c0tyvweZcHvdgSuYTpPn8khiGNmrop1Q4AUbFE8yDLWMcPv8uuw/FxcNwuOq9W
o9zL49EZbz3H18nq8J5H8oewWJaYZUMsQtTGj8ug7FRrpEsIQLse/D/k7csylslO
51JOKKvpCz0N42Tl1dIqD9RJHPVyTErkc6UPaDvcCFke2RSfwcFAcr/q1M4Pb+ZG
4Ybq8ZVhNDkZWqto49xDfBdNKu2PzbpVANoV66IK9bwSM2JDuTIKQ70vKNDS+dQI
ap2Hqp+E5mCOSuiXxd0Lk/oBGLRYkJ4xK6OlyJ8iCH9cRIIqdT/Ka0p8aBXFbMx8
rhW7+K7e0FslDABxnKPKqvlAkKcth+7UAHjm/+qlRcaP5wkNTxG5rtaBgx017aEg
MGZI2GP25znd3zr8mIaTVYlHYdTqAzYeExiL08xzg64WJUUMkE3DluEXCtomBzDz
SqT6xJHZtE5w3NWVGgpvCFfeYplbfgXPJtB2NzBBXPjxb

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 09:50:17 +
with message-id 
and subject line Bug#874422: fixed in pycoast 1.0.0+dfsg-2
has caused the Debian Bug report #874422,
regarding python-pycoast-doc: fails to upgrade from 'stretch' - trying to 
overwrite /usr/share/doc-base/pycoast
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.)


-- 
874422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: pycoast
Source-Version: 1.0.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
pycoast, 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.
Bas Couwenberg  (supplier of updated pycoast 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: Wed, 06 Sep 2017 11:29:19 +0200
Source: pycoast
Binary: python-pycoast python3-pycoast python-pycoast-doc
Architecture: source all
Version: 1.0.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 python-pycoast - Draw coastlines, borders and rivers on images
 python-pycoast-doc - Draw coastlines, borders and rivers on images (common 
documentati
 python3-pycoast - Draw coastlines, borders and rivers on images (for Python 3)
Closes: 874422
Changes:
 pycoast (1.0.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Add Breaks/Replaces to -doc package.
 (closes: #874422)
Checksums-Sha1:
 a45bef990a3e8e72b3ecf0d6afbea473de074823 2336 pycoast_1.0.0+dfsg-2.dsc
 d385e3798dc88621ce828583d0eb675226a4ca94 11244 
pycoast_1.0.0+dfsg-2.debian.tar.xz
 151cecedf950187f029dfbc9d144055840fc2966 8979 
pycoast_1.0.0+dfsg-2_amd64.buildinfo
 0843947a2c267c4d157523c3b3c89a8a24446e16 4797424 
python-pycoast-doc_1.0.0+dfsg-2_all.deb
 ab60a1d10f3b5b981de8f210ab0a297c8465 26822 
python-pycoast_1.0.0+dfsg-2_all.deb
 eefc428b075227142bf4350d8713cda5d12e70e9 26618 
python3-pycoast_1.0.0+dfsg-2_all.deb
Checksums-Sha256:
 46267a7c991d2d870f7af2a4fa99b5c71341ab0cf45b259d9fece39a07626efc 2336 
pycoast_1.0.0+dfsg-2.dsc
 faea9bc3bcf75a9ebd25d5e6b1ed371c988a4485c938eeac5e8629c2924bdc5d 11244 
pycoast_1.0.0+dfsg-2.debian.tar.xz
 3022b6705c734af4871ca970dd21a6016070188134c35dede08eafe023a43b5b 8979 
pycoast_1.0.0+dfsg-2_amd64.buildinfo
 2e366f85fc48c55663818768416aa2cd8d2f6ac2151ea4b5f725e6be26dffe73 4797424 
python-pycoast-doc_1.0.0+dfsg-2_all.deb
 6cb02bab5822a2de57f1e6113646df91baaab4ee1317027601f8ce1168b60d2f 26822 
python-pycoast_1.0.0+dfsg-2_all.deb
 8281a42ab22cc652a2ef9f5a053d3c2dd3837f29e9c6ab36682c35bcc4817994 26618 
python3-pycoast_1.0.0+dfsg-2_all.deb
Files:
 76ffb78f18b689f9ee215e034bcfe20a 2336 python optional pycoast_1.0.0+dfsg-2.dsc
 7ab18af478ea847adfb49d671a95e497 11244 python optional 
pycoast_1.0.0+dfsg-2.debian.tar.xz
 4819467e072e77e2a3243ba581193cbe 8979 python optional 
pycoast_1.0.0+dfsg

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

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Andreas,

Thanks for reporting this issue. It's fixed in git and a new upload to
unstable will follow shortly.

Kind Regards,

Bas

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #874422 [python-pycoast-doc] python-pycoast-doc: fails to upgrade from 
'stretch' - trying to overwrite /usr/share/doc-base/pycoast
Added tag(s) pending.

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

Bug#871283: marked as done (libgyoto6: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 09:07:09 +
with message-id 
and subject line Bug#871283: fixed in gyoto 1.2.0-3
has caused the Debian Bug report #871283,
regarding libgyoto6: 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.)


-- 
871283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgyoto6
Version: 1.2.0-2
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, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string, std::allocator >()@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: gyoto
Source-Version: 1.2.0-3

We believe that the bug you reported is fixed in the latest version of
gyoto, 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.
Thibaut Paumard  (supplier of updated gyoto 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 14:57:29 +0200
Source: gyoto
Binary: gyoto gyoto-bin libgyoto6 gyoto-dbg libgyoto6-dev yorick-gyoto 
python-gyoto python3-gyoto gyoto-doc
Architecture: source
Version: 1.2.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Maintainers 

Changed-By: Thibaut Paumard 
Description:
 gyoto  - General relativistic geodesic integration and ray-tracing
 gyoto-bin  - General relativistic ray-tracing command-line interface
 gyoto-dbg  - debugging symbols for the Gyoto framework
 gyoto-doc  - documentation for the Gyoto library
 libgyoto6  - Gyoto framework main library an standard plug-in
 libgyoto6-dev - development files for libgyoto
 python-gyoto - General relativistic geodesic integration for the Python 2 
langua
 python3-gyoto - General relativistic geodesic integration for the Python 3 
langua
 yorick-gyoto - General relativistic geodesic integration for the Yorick 
language
Closes: 871283
Changes:
 gyoto (1.2.0-3) unstable; urgency=low
 .
   * Bug fix: "requires rebuild against GCC 7 and symbols/shlibs bump",
 thanks to jcowg...@debian.org; (Closes: #871283).
Checksums-Sha1:
 2e6707822f4117c50a1e504a1

Bug#874434: openjdk-8-jre-headless: uninstallable on armhf

[Gianfranco Costamagna]

Source: openjdk-8
Version: 8u144-b01-1
Severity: serious
Justification: breaks gdal and pdf2htmlex build-deps installability on armhf, 
breaks dpkg installation


As said, apt-get install openjdk-8-jre-headless on armhf fails.

# apt-get install openjdk-8-jre-headless
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  ca-certificates ca-certificates-java fontconfig-config fonts-dejavu-core 
java-common libavahi-client3 libavahi-common-data libavahi-common3 libbsd0 
libcups2 libdbus-1-3 libexpat1 libfontconfig1 libfreetype6
  libgssapi-krb5-2 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 
libkrb5support0 liblcms2-2 libnspr4 libnss3 libpcsclite1 libpng16-16 
libsqlite3-0 libssl1.1 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6
  libxext6 libxi6 libxrender1 libxtst6 openssl ucf x11-common
Suggested packages:
  default-jre cups-common krb5-doc krb5-user liblcms2-utils pcscd libnss-mdns 
fonts-dejavu-extra fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei 
fonts-wqy-zenhei fonts-indic
Recommended packages:
  dbus krb5-locales
The following NEW packages will be installed:
  ca-certificates ca-certificates-java fontconfig-config fonts-dejavu-core 
java-common libavahi-client3 libavahi-common-data libavahi-common3 libbsd0 
libcups2 libdbus-1-3 libexpat1 libfontconfig1 libfreetype6
  libgssapi-krb5-2 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 
libkrb5support0 liblcms2-2 libnspr4 libnss3 libpcsclite1 libpng16-16 
libsqlite3-0 libssl1.1 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6
  libxext6 libxi6 libxrender1 libxtst6 openjdk-8-jre-headless openssl ucf 
x11-common
0 upgraded, 40 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/34.8 MB of archives.
After this operation, 111 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libssl1.1:armhf.
(Reading database ... 14063 files and directories currently installed.)
Preparing to unpack .../00-libssl1.1_1.1.0f-5_armhf.deb ...
Unpacking libssl1.1:armhf (1.1.0f-5) ...
Selecting previously unselected package libkeyutils1:armhf.
Preparing to unpack .../01-libkeyutils1_1.5.9-9_armhf.deb ...
Unpacking libkeyutils1:armhf (1.5.9-9) ...
Selecting previously unselected package libkrb5support0:armhf.
Preparing to unpack .../02-libkrb5support0_1.15.1-2_armhf.deb ...
Unpacking libkrb5support0:armhf (1.15.1-2) ...
Selecting previously unselected package libk5crypto3:armhf.
Preparing to unpack .../03-libk5crypto3_1.15.1-2_armhf.deb ...
Unpacking libk5crypto3:armhf (1.15.1-2) ...
Selecting previously unselected package libkrb5-3:armhf.
Preparing to unpack .../04-libkrb5-3_1.15.1-2_armhf.deb ...
Unpacking libkrb5-3:armhf (1.15.1-2) ...
Selecting previously unselected package libgssapi-krb5-2:armhf.
Preparing to unpack .../05-libgssapi-krb5-2_1.15.1-2_armhf.deb ...
Unpacking libgssapi-krb5-2:armhf (1.15.1-2) ...
Selecting previously unselected package libsqlite3-0:armhf.
Preparing to unpack .../06-libsqlite3-0_3.20.1-1_armhf.deb ...
Unpacking libsqlite3-0:armhf (3.20.1-1) ...
Selecting previously unselected package ucf.
Preparing to unpack .../07-ucf_3.0036_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0036) ...
Selecting previously unselected package openssl.
Preparing to unpack .../08-openssl_1.1.0f-5_armhf.deb ...
Unpacking openssl (1.1.0f-5) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../09-ca-certificates_20170717_all.deb ...
Unpacking ca-certificates (20170717) ...
Selecting previously unselected package java-common.
Preparing to unpack .../10-java-common_0.59_all.deb ...
Unpacking java-common (0.59) ...
Selecting previously unselected package libavahi-common-data:armhf.
Preparing to unpack .../11-libavahi-common-data_0.6.32-2_armhf.deb ...
Unpacking libavahi-common-data:armhf (0.6.32-2) ...
Selecting previously unselected package libavahi-common3:armhf.
Preparing to unpack .../12-libavahi-common3_0.6.32-2_armhf.deb ...
Unpacking libavahi-common3:armhf (0.6.32-2) ...
Selecting previously unselected package libdbus-1-3:armhf.
Preparing to unpack .../13-libdbus-1-3_1.11.16+really1.10.22-1_armhf.deb ...
Unpacking libdbus-1-3:armhf (1.11.16+really1.10.22-1) ...
Selecting previously unselected package libavahi-client3:armhf.
Preparing to unpack .../14-libavahi-client3_0.6.32-2_armhf.deb ...
Unpacking libavahi-client3:armhf (0.6.32-2) ...
Selecting previously unselected package libcups2:armhf.
Preparing to unpack .../15-libcups2_2.2.4-5_armhf.deb ...
Unpacking libcups2:armhf (2.2.4-5) ...
Selecting previously unselected package liblcms2-2:armhf.
Preparing to unpack .../16-liblcms2-2_2.8-4_armhf.deb ...
Unpacking liblcms2-2:armhf (2.8-4) ...
Selecting previously unselected package libjpeg62-turbo:armhf.
Preparing to unpack .../17-libjpeg62-turbo_1%3a1.5.2-2_armhf.d

Bug#873654: marked as done (python-py-zipkin: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 07:19:53 +
with message-id 
and subject line Bug#873654: fixed in python-py-zipkin 0.9.0-2
has caused the Debian Bug report #873654,
regarding python-py-zipkin: Incomplete debian/copyright?
to be marked as done.

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

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


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

(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
   `-
--- End Message ---
--- Begin Message ---
Source: python-py-zipkin
Source-Version: 0.9.0-2

We believe that the bug you reported is fixed in the latest version of
python-py-zipkin, 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.
Olivier Sallou  (supplier of updated python-py-zipkin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Aug 2017 06:54:38 +
Source: python-py-zipkin
Binary: python3-py-zipkin
Architecture: source all
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Olivier Sallou 
Description:
 python3-py-zipkin - Library for using Zipkin in Python
Closes: 873654
Changes:
 python-py-zipkin (0.9.0-2) unstable; urgency=medium
 .
   * d/control: fix maintainers to set python module team
fix Vcs links
   * d/copyright: Add Twitter licensing info (Closes: #873654).
Checksums-Sha1:
 5433cd309385bfec2fb840fd9e8d3d0ec13aa8aa 2100 python-py-zipkin_0.9.0-2.dsc
 3c47bebd3e7f85e1e2d6396f92b5cc4e01958d11 1376 
python-py-zipkin_0.9.0-2.debian.tar.xz
 c0dc6cc8bdd2b157b5b47109c288d7513e035b31 5192 
python-py-zipkin_0.9.0-2_amd64.buildinfo
 8d690a150feb839d07a7d9c06e194ddda59cb60f 18192 
python3-py-zipkin_0.9.0-2_all.deb
Checksums-Sha256:
 43b757e904bd41f9a2136c9782a25b617a243aafd7edfc60e30f42d9e3ba280e 2100 
python-py-zipkin_0.9.0-2.dsc
 43811005f16b7ea3f14f56d90911da3417f284520e91fa677c8ccbe84d88c99a 1376 
python-py-zipkin_0.9.0-2.debian.tar.xz
 393e1d64f7207e71a3396ab77df46cdef64123b1391acce7baf5fdf5306b 5192 
python-py-zipkin_0.9.0-2_amd64.buildinfo
 5e308b58cd7aa3bf7a8332cd1fc99f403e0b3878cb464b9df08c0f58fc04decd 18192 
python3-py-zipkin_0.9.0-2_all.deb
Files:
 451339815eae5e57fe161fe96628a44e 2100 python optional 
python-py-zipkin_0.9.0-2.dsc
 dba6a3fd41fb1bd2d5840aa10b761277 1376 python optional 
python-py-zipkin_0.9.0-2.debian.tar.xz
 757c1e2098e40cffc438d8dc9fadab72 5192 python optional 
python-py-zipkin_0.9.0-2_amd64.buildinfo
 aca1623b3e2cacce241e81e2808881eb 18192 python optional 
python3-py-zipkin_0.9.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZr5xyAAoJEHjcaNsybYQ42PIP/REl8QiETiNfPwCWDO3uheS7
ib4i1jLPTkZVd+m+yzSXiUd63yVfpHxoZ+SAn5aoZOzduSW5CTR0DGpk1zqOe/Ac
pSUsald1Y5velKPsI/1rUwbjqvTL/jiG4bRjxgO5gF66dS4ON/ZD8T/9mJnC2Ual
xq9y7payIPw8H7oGNgPolzjn2LpUlsb2/ND36H+KE3q3lGDYJ9IsufjB0UWSeChk
53d9/tscnzIRnIk3qkWUegPqcXrPVB0CtWXa5dW7lMNAOSerKn4GZpsXSG0wsHRC
wEItYSyUalfV1uZjNRP4keZMEA4Xsi6iHVeiGtAQDz9u9iIGUBFwKsI+iUg3M3jm
JezWCWOrq8QiBeu2VUg/pCLeR+5ik//L4/Z0NmOOLk74tBVcyY3C9iZDIT833+M4
SbR2ogG7U44G70S4MOlgjGGBiRoZcO6MN6Na8GG3gPa+dWwiKHnkfGchTZ8Iib1W
SYA40OJi4fKY3zFdp2nZ7xc3lpRf/DrKz5s3N56hVeIhzAYip6fv9s3J7MMsEgjS
j3k68pKqSHCB8Fq2T+HImK1OVU2jH2LHVsL+YovqQarOz8c4cITOHSC47ay28b4k
gIGSrd4K8RDnCYymD5gQ3S5+IvjVUbYoecbEKkX7jaxCkAFOPlCqa3yYGiXL7/02
Az0NP5Zexwph0/aaJqBB
=F5sG
-END PGP SIGNATURE End Message ---

Processed: not "serious"

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #873642 [weboob-qt] weboob-qt: misses dependency on 
python-pyqt5.qtmultimedia
Severity set to 'normal' from 'serious'

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

Bug#873642: not "serious"

[VA]

Control: severity -1 normal

This bug is not "serious", only qvideoob is affected by this lack of 
dependency, other commands in weboob-qt do not have this issue. It does 
not make the package useless.
Furthermore, you can make qvideoob work by simply installing the 
aforementioned dependency...

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 874432 linux: Kernel panic due to duplicate AppArmor profiles
Bug #874432 [src:linux] linux: Kernel panic due to duplicate AppArmor profiles
Ignoring request to change the title of bug#874432 to the same title
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 874432 linux: Kernel panic due to duplicate AppArmor profiles
Bug #874432 [src:linux] linux: Kernel panic due to AppArmor policy_destroy 
after August update
Changed Bug title to 'linux: Kernel panic due to duplicate AppArmor profiles' 
from 'linux: Kernel panic due to AppArmor policy_destroy after August update'.
>
End of message, stopping processing here.

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

Bug#873152: marked as done (utopia-documents: Fails to build with qt5.9)

[Debian Bug Tracking System]

Your message dated Wed, 06 Sep 2017 07:05:55 +
with message-id 
and subject line Bug#873152: fixed in utopia-documents 3.0.2-1.1
has caused the Debian Bug report #873152,
regarding utopia-documents: Fails to build with qt5.9
to be marked as done.

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

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


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

Hi James,

In Ubuntu, we've found that utopia-documents fails to build against Qt5.9
with the following error:

[ 16%] Generating moc_bubble.cpp
cd /<>/utopia-build/libutopia2_qt/utopia2/qt && 
/usr/lib/x86_64-linux-gnu/qt5/bin/moc 
@/<>/utopia-build/libutopia2_qt/utopia2/qt/moc_bubble.cpp_parameters
/<>/libutopia2_qt/utopia2/qt/bubble.h:56: Error: Namespace 
declaration lacks Q_NAMESPACE macro.
libutopia2_qt/utopia2/qt/CMakeFiles/utopia2_qt_autogen.dir/build.make:80: 
recipe for target 'libutopia2_qt/utopia2/qt/moc_bubble.cpp' failed

Full build logs can be found at 
https://launchpad.net/ubuntu/+source/utopia-documents/3.0.2-1

Since the Qt stack is nearly identical between artful and Debian unstable, I
believe (but have not tested) that this build failure applies to Debian as
well.

I have attached the attached patch to fix the build failure in Ubuntu.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch 
utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch
--- utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch   
1969-12-31 16:00:00.0 -0800
+++ utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch   
2017-08-24 17:05:58.0 -0700
@@ -0,0 +1,17 @@
+Description: add required Q_NAMESPACE macro to namespace
+ Qt 5.9 doesn't like namespaces without Q_NAMESPACE macro.
+Author: Steve Langasek 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1710317
+
+Index: utopia-documents-3.0.2/libutopia2_qt/utopia2/qt/bubble.h
+===
+--- utopia-documents-3.0.2.orig/libutopia2_qt/utopia2/qt/bubble.h
 utopia-documents-3.0.2/libutopia2_qt/utopia2/qt/bubble.h
+@@ -55,6 +55,7 @@
+ 
+ namespace Utopia
+ {
++Q_NAMESPACE
+ 
+ typedef enum
+ {
diff -Nru utopia-documents-3.0.2/debian/patches/series 
utopia-documents-3.0.2/debian/patches/series
--- utopia-documents-3.0.2/debian/patches/series2017-04-10 
05:13:10.0 -0700
+++ utopia-documents-3.0.2/debian/patches/series2017-08-24 
16:58:24.0 -0700
@@ -1 +1,2 @@
 remove-utopia-update-check.diff
+fix-namespace-declaration.patch
--- End Message ---
--- Begin Message ---
Source: utopia-documents
Source-Version: 3.0.2-1.1

We believe that the bug you reported is fixed in the latest version of
utopia-documents, 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.
Gianfranco Costamagna  (supplier of updated 
utopia-documents 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 08:45:38 +0200
Source: utopia-documents
Binary: utopia-documents utopia-documents-dbg
Architecture: source
Version: 3.0.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: James Marsh 
Changed-By: Gianfranco Costamagna 
Description:
 utopia-documents - PDF reader that displays interactive annotations on 
scientific ar
 utopia-documents-dbg - debugging symbols for utopia-documents
Closes: 873152
Launchpad-Bugs-Fixed: 1710317
Changes:
 utopia-documents (3.0.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Steve Langasek ]
   * debian/patches/fix-namespac

Bug#873152: utopia-documents: Fails to build with qt5.9

[Gianfranco Costamagna]

Control: tags 873152 + pending

Dear maintainer,

I've prepared an NMU for utopia-documents (versioned as 3.0.2-1.1) and
uploaded it to unstable. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru utopia-documents-3.0.2/debian/changelog 
utopia-documents-3.0.2/debian/changelog
--- utopia-documents-3.0.2/debian/changelog 2017-04-10 14:13:10.0 
+0200
+++ utopia-documents-3.0.2/debian/changelog 2017-09-06 08:45:38.0 
+0200
@@ -1,3 +1,13 @@
+utopia-documents (3.0.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Steve Langasek ]
+  * debian/patches/fix-namespace-declaration.patch: add required
+Q_NAMESPACE macro to namespace. LP: #1710317. Closes: #873152
+
+ -- Gianfranco Costamagna   Wed, 06 Sep 2017 
08:45:38 +0200
+
 utopia-documents (3.0.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch 
utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch
--- utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch   
1970-01-01 01:00:00.0 +0100
+++ utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch   
2017-09-06 08:45:38.0 +0200
@@ -0,0 +1,17 @@
+Description: add required Q_NAMESPACE macro to namespace
+ Qt 5.9 doesn't like namespaces without Q_NAMESPACE macro.
+Author: Steve Langasek 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1710317
+
+Index: utopia-documents-3.0.2/libutopia2_qt/utopia2/qt/bubble.h
+===
+--- utopia-documents-3.0.2.orig/libutopia2_qt/utopia2/qt/bubble.h
 utopia-documents-3.0.2/libutopia2_qt/utopia2/qt/bubble.h
+@@ -55,6 +55,7 @@
+ 
+ namespace Utopia
+ {
++Q_NAMESPACE
+ 
+ typedef enum
+ {
diff -Nru utopia-documents-3.0.2/debian/patches/series 
utopia-documents-3.0.2/debian/patches/series
--- utopia-documents-3.0.2/debian/patches/series2017-04-10 
14:13:10.0 +0200
+++ utopia-documents-3.0.2/debian/patches/series2017-09-06 
08:45:38.0 +0200
@@ -1 +1,2 @@
 remove-utopia-update-check.diff
+fix-namespace-declaration.patch


signature.asc
Description: OpenPGP digital signature

Bug#874432: More info

[Vincas Dargis]

I have found the core issue.

It's not about kernel update, it's about the fact that Thunderbird package
now has usr.bin.thunderbird
AppArmor profile, and it conflicted with other profile
usr.lib.thunderbird.thunderbird I had enabled
earlier (attached).

Kernel upgrade just made me to reboot system and AppArmor tried to load
kinda duplicate profiles.

I could not reproduce crash on Debian 9 Stretch with duplicate profile.


usr.lib.thunderbird.thunderbird
Description: Binary data

Processed: Re: utopia-documents: Fails to build with qt5.9

[Debian Bug Tracking System]

Processing control commands:

> tags 873152 + pending
Bug #873152 [utopia-documents] utopia-documents: Fails to build with qt5.9
Added tag(s) pending.

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

Bug#873654: marked as pending

[Olivier Sallou]

tag 873654 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/python-py-zipkin.git/commit/?id=94f8277

---
commit 94f8277946f52c78dd6227c55969957e97d78bed
Author: Olivier Sallou 
Date:   Wed Sep 6 06:55:06 2017 +

fix licensing

diff --git a/debian/changelog b/debian/changelog
index 2cacb32..c2add21 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,8 @@
-python-py-zipkin (0.9.0-2) UNRELEASED; urgency=medium
+python-py-zipkin (0.9.0-2) unstable; urgency=medium
 
   * d/control: fix maintainers to set python module team
fix Vcs links
+  * d/copyright: Add Twitter licensing info (Closes: #873654).
 
  -- Olivier Sallou   Fri, 18 Aug 2017 06:54:38 +
 

Processed: Re: Bug#848183: last.fm : 'XML not UTF-8 encoded!'

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #848183 [mpd-sima] last.fm : 'XML not UTF-8 encoded!'
Marked Bug as done

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

Processed: Bug#873654 marked as pending

[Debian Bug Tracking System]

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

> tag 873654 pending
Bug #873654 [src:python-py-zipkin] python-py-zipkin: Incomplete 
debian/copyright?
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#848183: last.fm : 'XML not UTF-8 encoded!'

[Gianfranco Costamagna]

control: close -1
On Wed, 14 Dec 2016 18:25:39 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?= 
 wrote:
> On 2016-12-14 18:10:46, James Cowgill wrote:
> > Control: fixed -1 0.14.1-2
> >
> > On 14/12/16 22:53, Antoine Beaupré wrote:
> >> Package: mpd-sima
> >> Version: 0.10.0-2
> >> Severity: grave
> >> Tags: patch
> >> 
> >> This bug also affects Debian:
> >> 
> >> https://bugs.launchpad.net/ubuntu/+source/mpd-sima/+bug/1492589
> >> 
> >> Basically, things changed on last.fm's side and mpd-sima can't deal
> >> with that anymore in jessie.
> >> 
> >> I confirm the patch provided in the above bug reports works too.
> >
> > So this bug only affects jessie, not stretch?
> 

well, closing then, unless somebody wants to do a jessie-pu upload, it is now 
oldstable

G.



signature.asc
Description: OpenPGP digital signature