Bug#896644: postinst failure

[Aaron Schrab]

Although the script starts with `set -e` it also has:


update-alternatives --query mpi | grep --silent libmpi
if [ $? -eq 0 ] ; then


Checking the status of a command afterward isn't going to work, since 
the `set -e` will cause the script to abort before the if statement is 
reached. That should be:



if update-alternatives --query mpi | grep --silent libmpi
then


signature.asc
Description: PGP signature

Bug#893554: marked as done (range-v3 FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 23 Apr 2018 08:27:18 +0300
with message-id <20180423052718.GL3347@localhost>
and subject line Re: Bug#893554: range-v3 FTBFS
has caused the Debian Bug report #893554,
regarding range-v3 FTBFS
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.)


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

Some recent change in unstable makes range-v3 FTBFS:

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

...
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: no 
matching function for call to 'initializer_list(const volatile 
std::initializer_list&)'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(const std::initializer_list&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: note:   conversion of argument 1 
would be ill-formed:
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: binding 
reference of type 'const std::initializer_list&' to 'const volatile 
std::initializer_list' discards qualifiers
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(std::initializer_list&&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: note:   conversion of argument 1 
would be ill-formed:
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: cannot 
bind rvalue reference of type 'std::initializer_list&&' to lvalue of type 
'const volatile std::initializer_list'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:89:5: note:   initializing argument 1 of 
'constexpr const _Tp* std::begin(std::initializer_list<_Tp>) [with _Tp = int]'
 begin(initializer_list<_Tp> __ils) noexcept
 ^
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: no 
matching function for call to 

Processed: affects 896189

[Debian Bug Tracking System]

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

> affects 896189 src:gdcm
Bug #896189 [openmpi-bin] update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Added indication that 896189 affects src:gdcm
> thanks
Stopping processing here.

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

Processed: affects 896189

[Debian Bug Tracking System]

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

> affects 896189 src:gromacs
Bug #896189 [openmpi-bin] update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Added indication that 896189 affects src:gromacs
> thanks
Stopping processing here.

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

Processed: affects 896189

[Debian Bug Tracking System]

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

> affects 896189 src:paraview
Bug #896189 [openmpi-bin] update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Added indication that 896189 affects src:paraview
> thanks
Stopping processing here.

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

Processed: affects 896189

[Debian Bug Tracking System]

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

> affects 896189 src:vtk7
Bug #896189 [openmpi-bin] update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Added indication that 896189 affects src:vtk7
> thanks
Stopping processing here.

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

Processed: bug 896604 is forwarded to https://issues.apache.org/jira/browse/SOLR-11971 ...

[Debian Bug Tracking System]

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

> forwarded 896604 https://issues.apache.org/jira/browse/SOLR-11971
Bug #896604 [lucene-solr] lucene-solr: CVE-2018-1308 XXE in DataImportHandler
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/SOLR-11971'.
> # mark as found in common anchestor for all suites for BTS graph
> found 896604 3.6.0+dfsg-1
Bug #896604 [lucene-solr] lucene-solr: CVE-2018-1308 XXE in DataImportHandler
There is no source info for the package 'lucene-solr' at version '3.6.0+dfsg-1' 
with architecture ''
Unable to make a source version for version '3.6.0+dfsg-1'
Marked as found in versions 3.6.0+dfsg-1.
> thanks
Stopping processing here.

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

Bug#896189: fixed in openmpi 3.0.1-7

[Fomalhaut Weisszwerg]

NOT fixed yet.

$ apt download openmpi-bin
Get:1 http://ftp.us.debian.org/debian sid/main amd64 openmpi-bin amd64
3.0.1-7 [202 kB]
Fetched 202 kB in 1s (164 kB/s)
$ sha256sum openmpi-bin_3.0.1-7_amd64.deb
f4eada195747f35572339ae006f02faa9c51237f4a25c321c4c40acbae61182b
openmpi-bin_3.0.1-7_amd64.deb
$ sudo dpkg -i openmpi-bin_3.0.1-7_amd64.deb
(Reading database ... 338452 files and directories currently installed.)
Preparing to unpack openmpi-bin_3.0.1-7_amd64.deb ...
Unpacking openmpi-bin (3.0.1-7) over (3.0.1-7) ...
Setting up openmpi-bin (3.0.1-7) ...
dpkg: error processing package openmpi-bin (--install):
 installed openmpi-bin package post-installation script subprocess returned
error exit status 1
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
 openmpi-bin


On Sun, 22 Apr 2018 16:20:37 + Alastair McKinstry 
wrote:

> Source: openmpi

> Source-Version: 3.0.1-7

>

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

> openmpi, 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 896...@bugs.debian.org,

> and the maintainer will reopen the bug report if appropriate.

>

> Debian distribution maintenance software

> pp.

> Alastair McKinstry  (supplier of updated openmpi
package)

>

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

> believe that there is a problem with it please contact the archive

> administrators by mailing ftpmas...@ftp-master.debian.org)

>

>

> -BEGIN PGP SIGNED MESSAGE-

> Hash: SHA256

>

> Format: 1.8

> Date: Sun, 22 Apr 2018 15:20:35 +0100

> Source: openmpi

> Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc

> Architecture: source amd64 all

> Version: 3.0.1-7

> Distribution: unstable

> Urgency: medium

> Maintainer: Alastair McKinstry 

> Changed-By: Alastair McKinstry 

> Description:

>  libopenmpi-dev - high performance message passing library -- header files

>  libopenmpi3 - high performance message passing library -- shared library

>  openmpi-bin - high performance message passing library -- binaries

>  openmpi-common - high performance message passing library -- common files

>  openmpi-doc - high performance message passing library -- man pages

> Closes: 896189

> Changes:

>  openmpi (3.0.1-7) unstable; urgency=medium

>  .

>* Delete old non-mpi alternatives if needed. Closes: #896189

> Checksums-Sha1:

>  f65701efd4b63c7dbc51cba90c34314c04aac38f 2713 openmpi_3.0.1-7.dsc

>  a7e318fde987f8ab1c7b92bfbc40a56d97f2aa55 60692
openmpi_3.0.1-7.debian.tar.xz

>  4f5c3fe53c50381cb77bcfd779e12304aaba62ce 9488
libopenmpi-dev-dbgsym_3.0.1-7_amd64.deb

>  afa78da184421a6bc84f02ee45734f7a68bf8d37 935376
libopenmpi-dev_3.0.1-7_amd64.deb

>  4baf877125ad62487e5197c0c08549363b06256c 27134064
libopenmpi3-dbgsym_3.0.1-7_amd64.deb

>  c876ac9d4f27a9dd18aa6756d8c9880a84d59b23 2093120
libopenmpi3_3.0.1-7_amd64.deb

>  849e22eac13ff000c08323170e7243055dcf842d 227368
openmpi-bin-dbgsym_3.0.1-7_amd64.deb

>  a147735f2e674855f7d304838f287fc6949fa6b3 201748
openmpi-bin_3.0.1-7_amd64.deb

>  63a7f3329573ffb47be28bab35c6bd5d680a2862 158196
openmpi-common_3.0.1-7_all.deb

>  64cd3450ecef51287b2429740cfab750a9fe2547 758312
openmpi-doc_3.0.1-7_all.deb

>  afd1d4851019870ceb33cba0d384b001672215d5 13672
openmpi_3.0.1-7_amd64.buildinfo

> Checksums-Sha256:

>  861be426ac51a82a5558460e02e30abf1e6d645e6d7b16f58f58017bd725a2c0 2713
openmpi_3.0.1-7.dsc

Windows 10 版のメール から送信

Bug#896162: marked as done (mruby FTBFS: RuntimeError: IO#isatty => open /dev/tty (mrbgems: mruby-io))

[Debian Bug Tracking System]

Your message dated Mon, 23 Apr 2018 03:20:21 +
with message-id 
and subject line Bug#896162: fixed in mruby 1.4.0+20180418+git54905e98-3
has caused the Debian Bug report #896162,
regarding mruby FTBFS: RuntimeError: IO#isatty => open /dev/tty (mrbgems: 
mruby-io)
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.)


-- 
896162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mruby
Version: 1.4.0+20180418+git54905e98-1
Severity: serious

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

...
RuntimeError: IO#isatty => open /dev/tty (mrbgems: mruby-io)
backtrace:

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/mrblib/file.rb:14:in
 initialize

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/mrblib/io.rb:15:in
 open

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/test/io.rb:347:in
 call
/<>/mruby-1.4.0+20180418+git54905e98/test/assert.rb:48:in 
assert

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/test/io.rb:345
Skip: File#mtime => File#mtime require Time (mrbgems: mruby-io)
Skip: File.expand_path (with ENV) =>  (mrbgems: mruby-io)
Skip: Struct.new removes existing constant => redefining Struct with same name 
cause warnings (mrbgems: mruby-struct)
Skip: Module#prepend super in alias => super does not currently work in aliased 
methods (mrbgems: mruby-test)
Total: 1074
   OK: 1073
   KO: 0
Crash: 1
 Time: 0.24 seconds
rake aborted!
Command Failed: ["build/test/bin/mrbtest" -v]
Rakefile:123:in `block (2 levels) in '
Makefile:12: recipe for target 'test' failed
make[1]: *** [test] Error 1
--- End Message ---
--- Begin Message ---
Source: mruby
Source-Version: 1.4.0+20180418+git54905e98-3

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated mruby 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: Mon, 23 Apr 2018 10:27:32 +0900
Source: mruby
Binary: mruby libmruby-dev
Architecture: source amd64
Version: 1.4.0+20180418+git54905e98-3
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Description:
 libmruby-dev - lightweight implementation of the Ruby language (development 
file
 mruby  - lightweight implementation of the Ruby language
Closes: 896162
Changes:
 mruby (1.4.0+20180418+git54905e98-3) unstable; urgency=medium
 .
   * Fix FTBFS RuntimeError: IO#isatty => open /dev/tty (mrbgems: mruby-io)
 Remove patches/Skip-mruby-io-test-if-there-is-no-dev-tty.patch, and
 add patches/Skip-mruby-tty-test-in-io.patch.
 (Closes: #896162)
Checksums-Sha1:
 9a5b16c49725cd938ba2f584505cbfe697fd2a26 2033 
mruby_1.4.0+20180418+git54905e98-3.dsc
 8074fee879e2bc42d50f585dcb60d30e15023bfc 5144 
mruby_1.4.0+20180418+git54905e98-3.debian.tar.xz
 1c2c25a9782a5add2afe592afb921bd5a0b9bb97 314164 
libmruby-dev_1.4.0+20180418+git54905e98-3_amd64.deb
 89e2df430c016c45f031a424f595a934c7dfcc84 2247248 
mruby-dbgsym_1.4.0+20180418+git54905e98-3_amd64.deb
 340162f892f24b98c63e66558a01f8698e8eca64 6611 
mruby_1.4.0+20180418+git54905e98-3_amd64.buildinfo
 ca5c4b890fa6706152157a10a6dbe45227549458 334476 
mruby_1.4.0+20180418+git54905e98-3_amd64.deb
Checksums-Sha256:
 6104cf3dbc198ca116b9e861ae148fd20ea97146ef96fbdd1261547f375e9e64 2033 
mruby_1.4.0+20180418+git54905e98-3.dsc
 0a9f73d7f58ae44c013be70691687c1ae6c86ae80d1a3c73cad39f58a565dee3 5144 
mruby_1.4.0+20180418+git54905e98-3.debian.tar.xz
 e8740afafa7db0e018b6f60475e3ded9f7856ae325776e2e5c3608d55cff90d0 314164 
libmruby-dev_1.4.0+20180418+git54905e98-3_amd64.deb
 2c162f96b6342cfe933d7f239645e3c73abb28474a0bec2ea6326d627609452c 2247248 
mruby-dbgsym_1.4.0+20180418+git54905e98-3_amd64.deb
 173baf38bddec9290f42467516d291dac4b3062d1e6c4cd5fa769624f7d83963 6611 
mruby_1.4.0+20180418+git54905e98-3_amd64.buildinfo
 

Processed: Re: [DRE-maint] Bug#896596: ruby-gnome2: Debci failure with poppler 0.63.0

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ruby-gnome2/ruby-gnome2/issues/1159
Bug #896596 [src:ruby-gnome2] ruby-gnome2: Debci failure with poppler 0.63.0
Set Bug forwarded-to-address to 
'https://github.com/ruby-gnome2/ruby-gnome2/issues/1159'.

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

Bug#896596: [DRE-maint] Bug#896596: ruby-gnome2: Debci failure with poppler 0.63.0

[dai]

Control: forwarded -1 https://github.com/ruby-gnome2/ruby-gnome2/issues/1159
-- 
Regards,
dai

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


signature.asc
Description: PGP signature

Bug#896644: Indeed not fixed in 3.0.1-7

[Diederik de Haas]

Forwarding msg send to #896189 to correct bug address ...

On maandag 23 april 2018 02:58:03 CEST Diederik de Haas wrote:
> Just got version 3.0.1-7 and it indeed (still) fails in postinst:
> 
> # aptitude safe-upgrade
> The following partially installed packages will be configured:
>   libopenmpi-dev openmpi-bin
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B of archives. After unpacking 0 B will be used.
> Setting up openmpi-bin (3.0.1-7) ...
> dpkg: error processing package openmpi-bin (--configure):
>  installed openmpi-bin package post-installation script subprocess returned
> error exit status 1 dpkg: dependency problems prevent configuration of
> libopenmpi-dev:amd64: libopenmpi-dev:amd64 depends on openmpi-bin (>=
> 3.0.0-1); however: Package openmpi-bin is not configured yet.
> 
> dpkg: error processing package libopenmpi-dev:amd64 (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  openmpi-bin
>  libopenmpi-dev:amd64
> 
> It looks like bug 896644 confirms it.



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

Bug#896189: Indeed not fixed in 3.0.1-7

[Diederik de Haas]

Just got version 3.0.1-7 and it indeed (still) fails in postinst:

# aptitude safe-upgrade
The following partially installed packages will be configured:
  libopenmpi-dev openmpi-bin 
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up openmpi-bin (3.0.1-7) ... 
dpkg: error processing package openmpi-bin (--configure):
 installed openmpi-bin package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of libopenmpi-dev:amd64:
 libopenmpi-dev:amd64 depends on openmpi-bin (>= 3.0.0-1); however:
  Package openmpi-bin is not configured yet.

dpkg: error processing package libopenmpi-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openmpi-bin
 libopenmpi-dev:amd64

It looks like bug 896644 confirms it.

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

Bug#896644: openmpi-bin: postinst script fails

[Boyuan Yang]

Package: openmpi-bin
Severity: serious
Version: 3.0.1-7

Dear maintainer,

With the latest openmpi, I would get the following result when running
"apt dist-upgrade":

% LANG=C sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up openmpi-bin (3.0.1-7) ...
dpkg: error processing package openmpi-bin (--configure):
 installed openmpi-bin package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of libopenmpi-dev:amd64:
 libopenmpi-dev:amd64 depends on openmpi-bin (>= 3.0.0-1); however:
  Package openmpi-bin is not configured yet.

dpkg: error processing package libopenmpi-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openmpi-bin
 libopenmpi-dev:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

--
Regards,
Boyuan Yang

Bug#885546: marked as done (wicd-gtk: Please don't recommend gksu)

[Debian Bug Tracking System]

Your message dated Mon, 23 Apr 2018 00:05:34 +
with message-id 
and subject line Bug#885546: fixed in wicd 1.7.4+tb2-6
has caused the Debian Bug report #885546,
regarding wicd-gtk: Please don't recommend gksu
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.)


-- 
885546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wicd-gtk
Severity: important
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gksu

gksu has been deprecated for years. The intent of gksu is to allow
running apps with elevated privileges but the way to do that is for
the app developer to use PolicyKit to request elevated privileges for
the specific actions that need done instead of for the whole app to
run as root.

For the next major stable release of Debian (codenamed Buster), the
Debian GNOME team plans to default to GNOME on Wayland where gksu does
not even work.

Therefore, the Debian GNOME team intends to either remove gksu or
replace it with a non-functional warning message. gksu is unmaintained
(last upload 2014) and is a security vulnerability.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: wicd
Source-Version: 1.7.4+tb2-6

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated wicd 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: Mon, 23 Apr 2018 01:10:23 +0200
Source: wicd
Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd
Architecture: source all
Version: 1.7.4+tb2-6
Distribution: unstable
Urgency: low
Maintainer: Debian WICD Packaging Team 
Changed-By: Axel Beckert 
Description:
 python-wicd - wired and wireless network manager - Python module
 wicd   - wired and wireless network manager - metapackage
 wicd-cli   - wired and wireless network manager - scriptable console client
 wicd-curses - wired and wireless network manager - Curses client
 wicd-daemon - wired and wireless network manager - daemon
 wicd-gtk   - wired and wireless network manager - GTK+ client
Closes: 789567 814090 885546 890179
Changes:
 wicd (1.7.4+tb2-6) unstable; urgency=low
 .
   * Set "Rules-Requires-Root: no".
   * Add debian/duck-override for "moved to" false positive on
 bugs.debian.org.
   * Declare compliance with Debian Policy 4.1.4. (No changes needed.)
   * Apply patch by Wasif Malik to fix "AttributeError in keypress():
 'Text' object has no attribute 'keypress'" in wicd-curses. Thanks
 Wasif! (Closes: #814090)
   * Update Vcs-* headers for move to salsa.debian.org.
   * Bump debhelper compatibility level to 11.
 + Update versioned debhelper build-dependency accordingly.
   * Fix several spelling errors in packaging found by Lintian.
   * Install upstream .service files, but patch them to fix multiple
 lintian warnings and to not disconnect the network connection on
 service stop. (Closes: #789567)
   * Replace dependency on python-gobject with python-gobject-2. (Closes:
 #890179)
   * Replace gksu and gksudo with pkexec and su-to-root. (Closes: #885546)
 + Update and rename patch 32-prefer_gksu.patch accordingly.
 + Recommend policykit-1 or menu (or kde-runtime for kdesu) instead of
   gksu.
   * Add a DEP12 upstream metadata file.
   * Add a note to /etc/default/wicd that the file is ignored if systemd is
 used as init system.
Checksums-Sha1:
 2411cb35a7a1c9fa341c8fd5d397aa675e24b42f 2238 wicd_1.7.4+tb2-6.dsc
 991fc55724de807be13ce2093d7e53ed0a1ce6fc 30500 wicd_1.7.4+tb2-6.debian.tar.xz
 0035c944554b73d121875f48c1791d2cf4f39532 55712 python-wicd_1.7.4+tb2-6_all.deb
 63e5fe7f6d88532a118266c48ded8d185c5d9e4b 28324 wicd-cli_1.7.4+tb2-6_all.deb
 6dd2eba5b3ac0789cd29ecc8c50269fca9b896b7 52816 wicd-curses_1.7.4+tb2-6_all.deb
 

Bug#896162: marked as done (mruby FTBFS: RuntimeError: IO#isatty => open /dev/tty (mrbgems: mruby-io))

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 23:21:41 +
with message-id 
and subject line Bug#896162: fixed in mruby 1.4.0+20180418+git54905e98-2
has caused the Debian Bug report #896162,
regarding mruby FTBFS: RuntimeError: IO#isatty => open /dev/tty (mrbgems: 
mruby-io)
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.)


-- 
896162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mruby
Version: 1.4.0+20180418+git54905e98-1
Severity: serious

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

...
RuntimeError: IO#isatty => open /dev/tty (mrbgems: mruby-io)
backtrace:

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/mrblib/file.rb:14:in
 initialize

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/mrblib/io.rb:15:in
 open

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/test/io.rb:347:in
 call
/<>/mruby-1.4.0+20180418+git54905e98/test/assert.rb:48:in 
assert

/<>/mruby-1.4.0+20180418+git54905e98/mrbgems/mruby-io/test/io.rb:345
Skip: File#mtime => File#mtime require Time (mrbgems: mruby-io)
Skip: File.expand_path (with ENV) =>  (mrbgems: mruby-io)
Skip: Struct.new removes existing constant => redefining Struct with same name 
cause warnings (mrbgems: mruby-struct)
Skip: Module#prepend super in alias => super does not currently work in aliased 
methods (mrbgems: mruby-test)
Total: 1074
   OK: 1073
   KO: 0
Crash: 1
 Time: 0.24 seconds
rake aborted!
Command Failed: ["build/test/bin/mrbtest" -v]
Rakefile:123:in `block (2 levels) in '
Makefile:12: recipe for target 'test' failed
make[1]: *** [test] Error 1
--- End Message ---
--- Begin Message ---
Source: mruby
Source-Version: 1.4.0+20180418+git54905e98-2

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated mruby package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Apr 2018 12:17:43 +0900
Source: mruby
Binary: mruby libmruby-dev
Architecture: source amd64
Version: 1.4.0+20180418+git54905e98-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Description:
 libmruby-dev - lightweight implementation of the Ruby language (development 
file
 mruby  - lightweight implementation of the Ruby language
Closes: 896162
Changes:
 mruby (1.4.0+20180418+git54905e98-2) unstable; urgency=medium
 .
   * Fix FTBFS RuntimeError: IO#isatty => open /dev/tty (mrbgems: mruby-io)
 Add patches/Skip-mruby-io-test-if-there-is-no-dev-tty.patch.
 (Closes: #896162)
Checksums-Sha1:
 5a3116426a07e70e5383cb6caa2371ca37fb2b77 2033 
mruby_1.4.0+20180418+git54905e98-2.dsc
 b163477f6542ea42b9870cfe89f0db7d7332b479 5140 
mruby_1.4.0+20180418+git54905e98-2.debian.tar.xz
 d6358e8f9b42c4ee70020e2653aae95e00e1f267 314764 
libmruby-dev_1.4.0+20180418+git54905e98-2_amd64.deb
 01c104fa489aa4025b06508f883c723036b3539f 2247460 
mruby-dbgsym_1.4.0+20180418+git54905e98-2_amd64.deb
 a563d48b6faaa996827a0a3b56c67bb5d0d26ade 6611 
mruby_1.4.0+20180418+git54905e98-2_amd64.buildinfo
 aacf74104f156732bf3ca84165166b50d89f6382 335156 
mruby_1.4.0+20180418+git54905e98-2_amd64.deb
Checksums-Sha256:
 4c5954c1c3218d05912883ae69f5176c87aa2bbb2659fe7c233ab4a5a9b92343 2033 
mruby_1.4.0+20180418+git54905e98-2.dsc
 ee0a44284f1961c7ccbc811199c15b438c7cf95b0e6da1b7a166f97fd5786458 5140 
mruby_1.4.0+20180418+git54905e98-2.debian.tar.xz
 90e59b7255c6b4f0a08b2ab65f07efee5ba66354a884b33f04e1da17ae9466a3 314764 
libmruby-dev_1.4.0+20180418+git54905e98-2_amd64.deb
 71fe5c26c192baf57207427bd3155fb0bedeae01a0b53376a56dc98e803a8f4f 2247460 
mruby-dbgsym_1.4.0+20180418+git54905e98-2_amd64.deb
 b9fe4e28d3f0b3208a8c3d6458f6e04b381398dbb5f6e7d4a88832aad3ea7f7b 6611 
mruby_1.4.0+20180418+git54905e98-2_amd64.buildinfo
 51855af91e903bba018a7ae739ef62e131882bb02d2c86cdd8709131692123c2 

Bug#895763: marked as done (python{,3}-matplotlib-dbg must depend on python{,3}-kiwisolver-dbg)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 23:21:29 +
with message-id 
and subject line Bug#895763: fixed in matplotlib 2.2.2-2
has caused the Debian Bug report #895763,
regarding python{,3}-matplotlib-dbg must depend on python{,3}-kiwisolver-dbg
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.)


-- 
895763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib
Version: 2.2.2-1
Severity: serious
User: ci-t...@tracker.debian.org
Usertags: triggers
Control: affects -1 python-ltfatpy
Control: affects -1 pyfai

With the upload of matplotlib version 2.2.2-1 the autopkgtest of pyfai¹
and pyton-ltfatpy² started failing with the following error:

  File "/usr/lib/python3/dist-packages/matplotlib/_layoutbox.py", line
23, in 
import kiwisolver as kiwi
ModuleNotFoundError: No module named 'kiwisolver'

As that file is from matplotlib, I believe it must have a Depends on
python(3)-kiwisolver.

Please fix this issue so that dependent packages can work reliably.

Paul

¹ https://ci.debian.net/packages/p/pyfai
² https://ci.debian.net/packages/p/python-ltfatpy



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 2.2.2-2

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Apr 2018 18:34:49 -0400
Source: matplotlib
Binary: python-matplotlib python3-matplotlib python-matplotlib-data 
python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg
Architecture: source all amd64
Version: 2.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-matplotlib - Python based plotting system in a style similar to Matlab
 python-matplotlib-data - Python based plotting system (data package)
 python-matplotlib-dbg - Python based plotting system (debug extension)
 python-matplotlib-doc - Python based plotting system (documentation package)
 python3-matplotlib - Python based plotting system in a style similar to Matlab 
(Python
 python3-matplotlib-dbg - Python based plotting system (debug extension, Python 
3)
Closes: 895763
Changes:
 matplotlib (2.2.2-2) unstable; urgency=medium
 .
   * debian/control
 - make -dbg packages depend on kiwisolver -dbg packages; Closes: #895763
Checksums-Sha1:
 10938f2175ec9599eb4a6e0a6b4799378cacaf2f 4111 matplotlib_2.2.2-2.dsc
 58f228824d5c620d7e0f47721e103fabd3da76a7 31476 matplotlib_2.2.2-2.debian.tar.xz
 262be99015bde4136e46dac40d5309d42ad5eeae 26286 
matplotlib_2.2.2-2_amd64.buildinfo
 c18890caea6293a758433a3615795ee7e4181923 4135740 
python-matplotlib-data_2.2.2-2_all.deb
 2dd2be4c0c31335f3f85a6a5dae872ee7d4ded63 6371584 
python-matplotlib-dbg_2.2.2-2_amd64.deb
 06203bd6e49afa35d5a685d18cb9119b11d7ff97 61483712 
python-matplotlib-doc_2.2.2-2_all.deb
 6a82ed99361f694461702a36e9fe9d76128360ab 5055740 
python-matplotlib_2.2.2-2_amd64.deb
 202e24189603487b4784ce1120ab8a69e2a658f2 424816 
python3-matplotlib-dbg_2.2.2-2_amd64.deb
 04d7ef27210cd1be2ce352f18ef15d85316b5667 5062900 
python3-matplotlib_2.2.2-2_amd64.deb
Checksums-Sha256:
 75b135011305db9d16ea8270b9c416e77547429fd52ed5712c57a790671a032e 4111 
matplotlib_2.2.2-2.dsc
 aece3c6a5b1d3911392d4681ca6f35915cded2ef476415ca298daf91b37a0100 31476 
matplotlib_2.2.2-2.debian.tar.xz
 a9b3f6d6db159420436c0b3393f2fa4bc3565d81e6a9014ad66b5606a21453dc 26286 
matplotlib_2.2.2-2_amd64.buildinfo
 74f00d1e28b502ea844cfc8eaa01d1feee876b393fa7687afc337070f193cd2a 4135740 
python-matplotlib-data_2.2.2-2_all.deb
 33ca023835d2321b8499d968c5c75edaea71fb2afb3d7139848392f4ca45d203 6371584 
python-matplotlib-dbg_2.2.2-2_amd64.deb
 20e0f2b82d64db663a4c813983a2072d8c64fe98dddefda73230c7f4629143cb 61483712 

Bug#896643: ros-robot-python-dev: Depends on NBS python-tf-conversions

[Jeremy Bicha]

Package: ros-robot-python-dev
Version: 1.9
Severity: serious
X-Debbugs-CC: jspri...@debian.org


ros-robot-python-dev depends on python-tf-conversions is no longer
built as of ros-geometry 1.11.9-3.

Thanks,
Jeremy Bicha

Processed: Bug #895763 in matplotlib marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895763 [src:matplotlib] python{,3}-matplotlib-dbg must depend on 
python{,3}-kiwisolver-dbg
Added tag(s) pending.

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

Bug#895763: Bug #895763 in matplotlib marked as pending

[morph]

Control: tag -1 pending

Hello,

Bug #895763 in matplotlib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/matplotlib/commit/27739a2a7d99acdfc33b73be9bf2fc274473a8fd


make -dbg packages depend on kiwisolver -dbg packages; Closes: #895763



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895763

Bug#895154: marked as done (ffmpeg: FTBFS - make[2]: write error: stdout)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 22:51:05 +
with message-id 
and subject line Bug#895154: fixed in ffmpeg 7:4.0-1
has caused the Debian Bug report #895154,
regarding ffmpeg: FTBFS - make[2]: write error: stdout
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.)


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

For some reason ffmpeg has started FTBFS with this error:
> TESTvsynth2-zlib
> /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" 
> "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt 
> yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 -pix_fmt 
> yuv420p -vsync 0 " -keep ""' '' 
> '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' '' 
> '' ''
>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f 
> rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags +bitexact 
> -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1 
> -thread_type frame+slice -i 
> /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct 
> simple -dct fastint -c zlib -flags +bitexact -sws_flags 
> +accurate_rnd+bitexact -fflags +bitexact -f avi -y 
> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi
>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all 
> -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact 
> -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i 
> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 1 
> -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags 
> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo -y 
> /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
> make[2]: Leaving directory '/<>/debian/standard'
> make[2]: write error: stdout
> dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code 1
> make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:192: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2

This can be seen on the reproducible builds first seen 2018-03-15
affecting 3.4 and 3.5 in experimental.

I'm guessing this has something to do with "make -O" which was enabled
recently in debhelper, but I haven't checked.

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ffmpeg
Source-Version: 7:4.0-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated ffmpeg 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: Sun, 22 Apr 2018 22:42:50 +0100
Source: ffmpeg
Binary: ffmpeg ffmpeg-doc libavcodec58 libavcodec-extra58 libavcodec-extra 
libavcodec-dev libavdevice58 libavdevice-dev libavfilter7 libavfilter-extra7 
libavfilter-extra libavfilter-dev libavformat58 libavformat-dev libavresample4 
libavresample-dev libavutil56 libavutil-dev libpostproc55 libpostproc-dev 
libswresample3 libswresample-dev libswscale5 libswscale-dev
Architecture: source
Version: 7:4.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 ffmpeg - Tools for transcoding, streaming and playing of multimedia files
 ffmpeg-doc - Documentation of the FFmpeg multimedia framework
 libavcodec-dev - FFmpeg library with de/encoders for audio/video codecs - 
developm
 libavcodec-extra - FFmpeg library with extra codecs (metapackage)
 libavcodec-extra58 - FFmpeg library with additional de/encoders for 
audio/video codecs
 libavcodec58 - FFmpeg library with de/encoders for audio/video codecs - runtime
 libavdevice-dev - FFmpeg library for 

Bug#896194: marked as done (gromacs FTBFS: GpuUtilsUnitTests (Timeout))

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 22:35:34 +
with message-id 
and subject line Bug#896194: fixed in gromacs 2018.1-2
has caused the Debian Bug report #896194,
regarding gromacs FTBFS: GpuUtilsUnitTests (Timeout)
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.)


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

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

...
  Start  9: GpuUtilsUnitTests

9: Test command: /<>/build/openmpi/bin/gpu_utils-test 
"--gtest_output=xml:/<>/build/openmpi/Testing/Temporary/GpuUtilsUnitTests.xml"
9: Test timeout computed to be: 30
9: [==] Running 30 tests from 6 test cases.
9: [--] Global test environment set-up.
9: [--] 7 tests from HostAllocatorTest/0, where TypeParam = int
9: [ RUN  ] HostAllocatorTest/0.EmptyMemoryAlwaysWorks
9: [   OK ] HostAllocatorTest/0.EmptyMemoryAlwaysWorks (0 ms)
9: [ RUN  ] HostAllocatorTest/0.VectorsWithDefaultHostAllocatorAlwaysWorks
9: [   OK ] HostAllocatorTest/0.VectorsWithDefaultHostAllocatorAlwaysWorks 
(0 ms)
9: [ RUN  ] HostAllocatorTest/0.TransfersWithoutPinningWork
9: [   OK ] HostAllocatorTest/0.TransfersWithoutPinningWork (0 ms)
9: [ RUN  ] HostAllocatorTest/0.FillInputAlsoWorksAfterCallingReserve
9: [   OK ] HostAllocatorTest/0.FillInputAlsoWorksAfterCallingReserve (0 ms)
9: [ RUN  ] HostAllocatorTest/0.ChangingPinningPolicyRequiresCuda
9: 
9: [WARNING] 
/<>/src/external/gmock-1.7.0/gtest/src/gtest-death-test.cc:825:: 
Death tests use fork(), which is unsafe particularly in a threaded context. For 
this test, Google Test couldn't detect the number of threads.
 9/24 Test  #9: GpuUtilsUnitTests ***Timeout  30.02 sec
[==] Running 30 tests from 6 test cases.
[--] Global test environment set-up.
[--] 7 tests from HostAllocatorTest/0, where TypeParam = int
[ RUN  ] HostAllocatorTest/0.EmptyMemoryAlwaysWorks
[   OK ] HostAllocatorTest/0.EmptyMemoryAlwaysWorks (0 ms)
[ RUN  ] HostAllocatorTest/0.VectorsWithDefaultHostAllocatorAlwaysWorks
[   OK ] HostAllocatorTest/0.VectorsWithDefaultHostAllocatorAlwaysWorks (0 
ms)
[ RUN  ] HostAllocatorTest/0.TransfersWithoutPinningWork
[   OK ] HostAllocatorTest/0.TransfersWithoutPinningWork (0 ms)
[ RUN  ] HostAllocatorTest/0.FillInputAlsoWorksAfterCallingReserve
[   OK ] HostAllocatorTest/0.FillInputAlsoWorksAfterCallingReserve (0 ms)
[ RUN  ] HostAllocatorTest/0.ChangingPinningPolicyRequiresCuda

[WARNING] 
/<>/src/external/gmock-1.7.0/gtest/src/gtest-death-test.cc:825:: 
Death tests use fork(), which is unsafe particularly in a threaded context. For 
this test, Google Test couldn't detect the number of threads.
...
The following tests FAILED:
  9 - GpuUtilsUnitTests (Timeout)
Errors while running CTest
make: *** [debian/rules:172: build-openmpi] Error 8


This might be related to the recent updates
of openmpi and mpich in unstable.
--- End Message ---
--- Begin Message ---
Source: gromacs
Source-Version: 2018.1-2

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

Debian distribution maintenance software
pp.
Nicholas Breen  (supplier of updated gromacs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Apr 2018 14:34:48 -0700
Source: gromacs
Binary: gromacs gromacs-data libgromacs3 libgromacs-dev gromacs-mpich 
gromacs-openmpi
Architecture: source
Version: 2018.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Nicholas Breen 
Description:
 gromacs- Molecular dynamics simulator, with building and analysis tools
 gromacs-data - GROMACS molecular dynamics sim, data and documentation
 gromacs-mpich - Molecular dynamics sim, binaries for MPICH parallelization
 gromacs-openmpi - 

Bug#896292: marked as done (python3-easydev: easydev fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 22:21:51 +
with message-id 
and subject line Bug#896292: fixed in python-easydev 0.9.35+dfsg-2
has caused the Debian Bug report #896292,
regarding python3-easydev: easydev fails to import
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.)


-- 
896292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-easydev
Version: 0.9.35+dfsg-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-easydev importing the module easydev
into a python interpreter fails with the following error:

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

import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-easydev
Source-Version: 0.9.35+dfsg-2

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

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated python-easydev package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Apr 2018 17:53:49 -0400
Source: python-easydev
Binary: python-easydev python3-easydev
Architecture: source
Version: 0.9.35+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Afif Elghraoui 
Description:
 python-easydev - common utilities to ease the development of Python packages 
(Pyth
 python3-easydev - common utilities to ease the development of Python packages 
(Pyth
Closes: 896292 896402
Changes:
 python-easydev (0.9.35+dfsg-2) unstable; urgency=medium
 .
   * Correct ITP bug number in previous changelog entry
   * Add dependencies on python-pkg-resources (Closes: #896292, #896402)
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 1fcb51bc828c7e6d9abc2ba425513f375f60011a 2307 python-easydev_0.9.35+dfsg-2.dsc
 e06a519c483cfc53325cfe342527784b36fdb182 4040 
python-easydev_0.9.35+dfsg-2.debian.tar.xz
 097cc7fead9ad70fe85c583c5a4904935bb632e5 6389 
python-easydev_0.9.35+dfsg-2_source.buildinfo
Checksums-Sha256:
 602d4d4ec6e897a106e2beb2cc938ba81dd8130fe15ca37252d81951d425db49 2307 
python-easydev_0.9.35+dfsg-2.dsc
 0f337f70da6fc9bf3d68359f162199df1178068fa5e446a49a712c542a0031e0 4040 
python-easydev_0.9.35+dfsg-2.debian.tar.xz
 01ac86f96fd1ad8aaf2d69a9a36e7ea0d5b195ab43ecc30088be8ea9b31bb93e 6389 
python-easydev_0.9.35+dfsg-2_source.buildinfo
Files:
 642bdfd7c7467b6768f510fd7f651083 2307 python optional 
python-easydev_0.9.35+dfsg-2.dsc
 34dfdb35b974bfcaa7294d2fd88b69e8 4040 python optional 
python-easydev_0.9.35+dfsg-2.debian.tar.xz
 e7dc5e8e899b94d4ccd216361bc62683 6389 python optional 
python-easydev_0.9.35+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6rcjomb2J+aAVWFfWbIwbzr53cEFAlrdBJsQHGFmaWZAZGVi
aWFuLm9yZwAKCRBZsjBvOvndwSLjD/9vVVqqy3yjpO+rpeXkEPhsx0+M4CWMB/gU
evob04nSe9ynKB39mopa7rxScT5q5vI964NRJ81M+aoSDjm+WpPmXbG05N1oqkOP
uitDCfj+k49OoJicGR7RfTav6Y0/JVVRBE2y0IQT8xunAn7CTkMtwdfEms5qpO+X
floIB8N9eCjQ+7fV2U1clSuIRpa0v2j+qtM0Zcs1PqT9Cf4htxO1w2dy8AWRZW00
hkbKlu0jWXLlXgAV08/MNyHcTllqO3AxtlZQ118OYqbyp97YeFmwyhWTaIaEIi6l
TBoTgmzgxslrKSHr24fvlMH0YfS+bQUwhepvclYPZde6Oe1TWvvg8IhglBs7HIMw
O0lSx29w0RkbfPvIBZL84ba897m110wdE7gnnppTolv4y1YxgPvEBzoFHoVIuPXV
OR8k4b5T1KgGbllgXkGF+ehds+YZZTs794kxMt9WfkIf5At6KVB2/k8mwqzLEXId

Bug#896402: marked as done (python-easydev: easydev fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 22:21:51 +
with message-id 
and subject line Bug#896402: fixed in python-easydev 0.9.35+dfsg-2
has caused the Debian Bug report #896402,
regarding python-easydev: easydev fails to import
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.)


-- 
896402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-easydev
Version: 0.9.35+dfsg-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-easydev importing the module easydev
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/easydev/__init__.py", line 23, in 

import pkg_resources
ImportError: No module named pkg_resources

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-easydev
Source-Version: 0.9.35+dfsg-2

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

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated python-easydev package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Apr 2018 17:53:49 -0400
Source: python-easydev
Binary: python-easydev python3-easydev
Architecture: source
Version: 0.9.35+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Afif Elghraoui 
Description:
 python-easydev - common utilities to ease the development of Python packages 
(Pyth
 python3-easydev - common utilities to ease the development of Python packages 
(Pyth
Closes: 896292 896402
Changes:
 python-easydev (0.9.35+dfsg-2) unstable; urgency=medium
 .
   * Correct ITP bug number in previous changelog entry
   * Add dependencies on python-pkg-resources (Closes: #896292, #896402)
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 1fcb51bc828c7e6d9abc2ba425513f375f60011a 2307 python-easydev_0.9.35+dfsg-2.dsc
 e06a519c483cfc53325cfe342527784b36fdb182 4040 
python-easydev_0.9.35+dfsg-2.debian.tar.xz
 097cc7fead9ad70fe85c583c5a4904935bb632e5 6389 
python-easydev_0.9.35+dfsg-2_source.buildinfo
Checksums-Sha256:
 602d4d4ec6e897a106e2beb2cc938ba81dd8130fe15ca37252d81951d425db49 2307 
python-easydev_0.9.35+dfsg-2.dsc
 0f337f70da6fc9bf3d68359f162199df1178068fa5e446a49a712c542a0031e0 4040 
python-easydev_0.9.35+dfsg-2.debian.tar.xz
 01ac86f96fd1ad8aaf2d69a9a36e7ea0d5b195ab43ecc30088be8ea9b31bb93e 6389 
python-easydev_0.9.35+dfsg-2_source.buildinfo
Files:
 642bdfd7c7467b6768f510fd7f651083 2307 python optional 
python-easydev_0.9.35+dfsg-2.dsc
 34dfdb35b974bfcaa7294d2fd88b69e8 4040 python optional 
python-easydev_0.9.35+dfsg-2.debian.tar.xz
 e7dc5e8e899b94d4ccd216361bc62683 6389 python optional 
python-easydev_0.9.35+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6rcjomb2J+aAVWFfWbIwbzr53cEFAlrdBJsQHGFmaWZAZGVi
aWFuLm9yZwAKCRBZsjBvOvndwSLjD/9vVVqqy3yjpO+rpeXkEPhsx0+M4CWMB/gU
evob04nSe9ynKB39mopa7rxScT5q5vI964NRJ81M+aoSDjm+WpPmXbG05N1oqkOP
uitDCfj+k49OoJicGR7RfTav6Y0/JVVRBE2y0IQT8xunAn7CTkMtwdfEms5qpO+X
floIB8N9eCjQ+7fV2U1clSuIRpa0v2j+qtM0Zcs1PqT9Cf4htxO1w2dy8AWRZW00
hkbKlu0jWXLlXgAV08/MNyHcTllqO3AxtlZQ118OYqbyp97YeFmwyhWTaIaEIi6l
TBoTgmzgxslrKSHr24fvlMH0YfS+bQUwhepvclYPZde6Oe1TWvvg8IhglBs7HIMw
O0lSx29w0RkbfPvIBZL84ba897m110wdE7gnnppTolv4y1YxgPvEBzoFHoVIuPXV
OR8k4b5T1KgGbllgXkGF+ehds+YZZTs794kxMt9WfkIf5At6KVB2/k8mwqzLEXId

Bug#895890: marked as done (pandas: FTBFS on mips and powerpc: test_unstack_odd_failure crashes)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 22:20:59 +
with message-id 
and subject line Bug#895890: fixed in pandas 0.22.0-4
has caused the Debian Bug report #895890,
regarding pandas: FTBFS on mips and powerpc: test_unstack_odd_failure crashes
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.)


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

Source: pandas
Version: 0.22.0-2
Severity: serious

Hi Science Team

Since the upload of 0.22.0-2, pandas has FTBFS on mips and powerpc with 
errors similar to the following:


../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/test_multilevel.py::TestMultiLevel::test_unstack_odd_failure 
realloc(): invalid next size

Aborted
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":99"

make[1]: *** [debian/rules:127: python-test2.7] Error 134
make[1]: Leaving directory '/<>'

The errors I have found in the build logs are:
realloc(): invalid next size
malloc(): smallbin double linked list corrupted
Segmentation fault
corrupted double-linked list

Pandas 0.22.0-1 failed for an unrelated reason.
The test_unstack_odd_failure did not fail with any of the 0.20.3-* 
uploads (it either passed, or the build failed for other reasons).


I'm marking this serious as the failure on mips prevents the migration 
of pandas to testing.


Regards
Graham
--- End Message ---
--- Begin Message ---
Source: pandas
Source-Version: 0.22.0-4

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated pandas 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: Sun, 22 Apr 2018 21:48:27 +
Source: pandas
Binary: python-pandas python3-pandas python-pandas-doc python-pandas-lib 
python3-pandas-lib
Architecture: source
Version: 0.22.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Graham Inggs 
Description:
 python-pandas - data structures for "relational" or "labeled" data
 python-pandas-doc - documentation and examples for pandas
 python-pandas-lib - low-level implementations and bindings for pandas
 python3-pandas - data structures for "relational" or "labeled" data - Python 3
 python3-pandas-lib - low-level implementations and bindings for pandas - 
Python 3
Closes: 895890
Changes:
 pandas (0.22.0-4) unstable; urgency=medium
 .
   * Team upload
   * Fix more tests expecting little-endian results
   * Fix heap corruption in read_csv on 32-bit, big-endian architectures
 (Closes: #895890)
Checksums-Sha1:
 fe6c11ce862197251c7e7d85608d24bb6ef5c974 3648 pandas_0.22.0-4.dsc
 d0d344efee8396de4b6bb813336857473896e0d1 3191748 pandas_0.22.0-4.debian.tar.xz
Checksums-Sha256:
 2c4587f7a7de080a252c756afa7762b13cd114eb9f2976bc5ef1be5aad6bbd81 3648 
pandas_0.22.0-4.dsc
 e8488a6f3a002b25910750f12fa30c48918f01f0fb1ad688de7ac5cab1b54860 3191748 
pandas_0.22.0-4.debian.tar.xz
Files:
 73c0a9ebe9b7a92a3cac25cf6c9bea06 3648 python optional pandas_0.22.0-4.dsc
 a760463129a145dc88c60d4c1318c8c4 3191748 python optional 
pandas_0.22.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAlrdBQ8ACgkQr8/sjmac
4cKN8A/8DtzxA2vMcNNiLMVMnWQOGfXRib+0pglqa+6dxrXeBJxySzWwazl0F0ze
Pvc11lmvMvxoiCPQcPR5HCwkV9QsJLfMLfJZTgUQJ+CnX4cBeDMu3myJckv5o3ff
naxfDbrIn0GFn6mMhnnEfhTGKS0BXPbOVnOFyob51MTOvVtX+8m2XY63P7vgZIjY
g7uuRwyFyEtsrfRDwbwrVJY3tx5K/dnqRcT24AQL/PJokOa3cSsPE7h3r5Ol1K8K
h19DaKXlHsyYLhG7OEtlOuBzkmoxp+6rIIzXK0i7XBSPPA4kTCstuj2wXF80bCMr
bBv0WgmI0/RBU/ekhtzr3D5JxB7b9MVGBrix+QAYgo56MdngazoUaz1HCePeEmUu
KzHNf5mYlJMsXvqUcBKNbmReTPrzV78Skks6+bPIXKRRD9MkTDy0HOnTLo7cq0HG
a70TKu3em3cnhfSujL0mpMm7dpdlxTDs5PgfhDIUc98dqG42IX3jNtTaKgCKQ0Q5
VnjnPIEsguQ5ExYWkybuDsZRwVCxSuuwfRo0rz8liHXgmvofucZhMDBhgsRrhADG
z0wciT0Mi4b10m09xLKriGOLrmdBkdbgAgXYea27DgvAXgKDylvXauE3gBVQxYRX

Bug#892088: marked as done (golang-1.10: FTBFS on mips when built on Octeon III buildds)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 22:05:49 +
with message-id 
and subject line Bug#892088: fixed in golang-1.10 1.10.1-3
has caused the Debian Bug report #892088,
regarding golang-1.10: FTBFS on mips when built on Octeon III buildds
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.)


-- 
892088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.10
Version: 1.10-1
Severity: serious
Tags: upstream patch
Forwarded: https://go-review.googlesource.com/c/go/+/97735
X-Debbugs-CC: debian-m...@lists.debian.org

[CC the list for the HW issue]

Hi,

golang-1.10 (and 1.9) FTBFS on mips big-endian with various floating
point test errors, but only when built on the Octeon III buildds.

After tearing my head out investigating this, I have concluded that
there is a hardware bug in the Octeon IIIs. The bug occurs when:
- You run a big floating point double operation (like div.d).
- Wait a few instructions (a store here seems to be important).
- Read the *odd* register which the above float operation stored into.
This ends up reading the value from before the double operation instead
of the result of the operation. I've attached a small C program which
reproduces this. It should happen 99% of the time (it will only fail if
you are unlucky and get an interrupt at the wrong time).

I think this does not affect the wider Debian archive because:
- MFHC1 (move from high float) seems to be unaffected (probably...)
- If mips32r2 and fpxx are enabled, GCC only reads the high part of a
float register using MFHC1 (in the few cases it needs to do this - like
integer <-> float conversion).

However, golang is affected because it uses FP32 and on big endian, all
double loads are split into word loads with the odd register loaded
first. I have attached a patch which fixes this which I have also
submitted upstream.

Thanks,
James
#include 
#include 

static void div_octeon_bug(double a, double b, uint32_t* buf)
{
	asm(
		"mtc1 %[fake_clobber], $f5\n"
		"div.d $f4, %[a], %[b]\n"
		"nop\n"
		"nop\n"
		"nop\n"
		"nop\n"
		"swc1 $f0, 0(%[buf])\n"
		"swc1 $f0, 0(%[buf])\n"
		"swc1 $f5, 0(%[buf])\n"
		"swc1 $f4, 4(%[buf])\n"
		"swc1 $f5, 8(%[buf])\n"
		"swc1 $f4, 12(%[buf])\n"
		:
		: [buf]"r"(buf), [fake_clobber]"r"(0xdeadbeef), [a]"f"(a), [b]"f"(b)
		: "memory", "f4", "$f5");
}

int main(void)
{
	uint32_t buf[4];
	div_octeon_bug(1.0, 21.63538985889851, buf);
	printf("%08x %08x\n", buf[0], buf[1]);
	printf("%08x %08x\n", buf[2], buf[3]);
	return 0;
}
From 5ab26b4e5996a3557a1d6f1af7f1e54104448a79 Mon Sep 17 00:00:00 2001
From: James Cowgill 
Date: Wed, 28 Feb 2018 16:10:14 +
Subject: [PATCH] cmd/internal/obj/mips: load/store even float registers first

There is a bug in Octeon III processors where storing an odd floating
point register after it has recently been written to by a double
floating point operation will store the old value from before the double
operation (there are some extra details - the operation and store
must be a certain number of cycles apart). However, this bug does not
occur if the even register is stored first. Currently the bug only
happens on big endian because go always loads the even register first on
little endian.

Workaround the bug by always loading / storing the even floating point
register first. Since this is just an instruction reordering, it should
have no performance penalty. This follows other compilers like GCC which
will always store the even register first (although you do have to set
the ISA level to MIPS I to prevent it from using SDC1).

Change-Id: I5e73daa4d724ca1df7bf5228aab19f53f26a4976
---
 src/cmd/internal/obj/mips/obj0.go | 18 ++
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/src/cmd/internal/obj/mips/obj0.go b/src/cmd/internal/obj/mips/obj0.go
index 2b9f18c942..c3bab5c48e 100644
--- a/src/cmd/internal/obj/mips/obj0.go
+++ b/src/cmd/internal/obj/mips/obj0.go
@@ -558,20 +558,22 @@ func preprocess(ctxt *obj.Link, cursym *obj.LSym, newprog obj.ProgAlloc) {
 			p.Link = q
 			p1 = q.Link
 
-			var regOff int16
+			var addrOff int64
 			if c.ctxt.Arch.ByteOrder == binary.BigEndian {
-regOff = 1 // load odd register first
+addrOff = 4 // swap load/save order
 			}
 			if p.From.Type == obj.TYPE_MEM {
 reg := REG_F0 + (p.To.Reg-REG_F0)&^1
-p.To.Reg = reg + regOff
-q.To.Reg = reg + 1 - regOff
-q.From.Offset += 4
+p.To.Reg = reg
+q.To.Reg = reg + 1
+p.From.Offset += addrOff
+

Bug#896402: Bug #896402 in python-easydev marked as pending

[afif]

Control: tag -1 pending

Hello,

Bug #896402 in python-easydev reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/med-team/python-easydev/commit/37df25edf4e95f2d0bd296f4d18c06fb216d7a2c


Add dependencies on python-pkg-resources

Closes: #896292, #896402



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896402

Processed: Bug #896292 in python-easydev marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896292 [python3-easydev] python3-easydev: easydev fails to import
Added tag(s) pending.

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

Processed: Bug #896402 in python-easydev marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896402 [python-easydev] python-easydev: easydev fails to import
Added tag(s) pending.

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

Bug#896292: Bug #896292 in python-easydev marked as pending

[afif]

Control: tag -1 pending

Hello,

Bug #896292 in python-easydev reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/med-team/python-easydev/commit/37df25edf4e95f2d0bd296f4d18c06fb216d7a2c


Add dependencies on python-pkg-resources

Closes: #896292, #896402



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896292

Processed: Bug #892088 in golang marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892088 [src:golang-1.10] golang-1.10: FTBFS on mips when built on Octeon 
III buildds
Added tag(s) pending.

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

Bug#892088: Bug #892088 in golang marked as pending

[tincho]

Control: tag -1 pending

Hello,

Bug #892088 in golang reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/go-team/compiler/golang/commit/4cea88212630d61115068590d2bf80ce98253aa3


Backport fix for FP bug in mips/Octeon III. Closes: #892088.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892088

Bug#896365: marked as done (python3-setuptools-scm: setuptools_scm fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:36:41 +
with message-id 
and subject line Bug#896365: fixed in setuptools-scm 1.17.0-2
has caused the Debian Bug report #896365,
regarding python3-setuptools-scm: setuptools_scm fails to import
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.)


-- 
896365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-setuptools-scm
Version: 1.17.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-setuptools-scm importing the module setuptools_scm
into a python interpreter fails with the following error:

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

from .version import format_version, meta, ScmVersion
  File "/usr/lib/python3/dist-packages/setuptools_scm/version.py", line 7, in 

from pkg_resources import iter_entry_points
ModuleNotFoundError: No module named 'pkg_resources'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: setuptools-scm
Source-Version: 1.17.0-2

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated setuptools-scm 
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: Sun, 22 Apr 2018 23:01:46 +0200
Source: setuptools-scm
Binary: python-setuptools-scm python3-setuptools-scm pypy-setuptools-scm
Architecture: source all
Version: 1.17.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Julien Puydt 
Description:
 pypy-setuptools-scm - blessed package to manage your versions by scm tags for 
PyPy
 python-setuptools-scm - blessed package to manage your versions by scm tags 
for Python 2
 python3-setuptools-scm - blessed package to manage your versions by scm tags 
for Python 3
Closes: 896365 896418
Changes:
 setuptools-scm (1.17.0-2) unstable; urgency=medium
 .
   * Refresh packaging:
 - Bump std-vers to 4.1.4.
 - Bump dh compat to 11.
 - Add basic autopkgtest (import).
   * Add missing depends (Closes: #896418, #896365).
Checksums-Sha1:
 bee06b693d075060eae0490bb5466d53422fd393 2450 setuptools-scm_1.17.0-2.dsc
 a936748b1a96c47f5032d45fd24962276fd145ca 3672 
setuptools-scm_1.17.0-2.debian.tar.xz
 81cf7b0b8b267eb01caa79b1c7e0923aa80edc25 18720 
pypy-setuptools-scm_1.17.0-2_all.deb
 a6381053cc03ab18e84d1e0730cc8edb02568f6d 19168 
python-setuptools-scm_1.17.0-2_all.deb
 1a08c0a72a8f18397a86dab1fc7189be687306ee 18736 
python3-setuptools-scm_1.17.0-2_all.deb
 ae759ecb8b17cc7d1fbd16ce23b5520d9f20b809 8679 
setuptools-scm_1.17.0-2_amd64.buildinfo
Checksums-Sha256:
 4c6d1050692f84411ac94d352383f0c118f8bf11571e6dee0cf5a4e0638ccb1b 2450 
setuptools-scm_1.17.0-2.dsc
 1bea4fd487230bf0da1ddb85f8406367a2b31fb696848d5b89370c4e8ab87210 3672 
setuptools-scm_1.17.0-2.debian.tar.xz
 fc8d0cbc03562cfeb8d94e7c7ae1c244af2c4b82bc2b7c5d2b4b5708a17d84d7 18720 
pypy-setuptools-scm_1.17.0-2_all.deb
 1d1b3e0350e959a520426c5c9834618a021107f7137f94de884ecc119ff04bcf 19168 
python-setuptools-scm_1.17.0-2_all.deb
 8c2deac13502985f657d88f84fd1e4a8812fe925cea8d8276949f5afca82855f 18736 
python3-setuptools-scm_1.17.0-2_all.deb
 16b982fd46bbfafc771fc94956100b27e20a7f6a81936b6818c6e9436eb6e111 8679 
setuptools-scm_1.17.0-2_amd64.buildinfo
Files:
 a5f047bac9cd63cfa5806027d45916fd 2450 python 

Bug#896418: marked as done (python-setuptools-scm: setuptools_scm fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:36:41 +
with message-id 
and subject line Bug#896418: fixed in setuptools-scm 1.17.0-2
has caused the Debian Bug report #896418,
regarding python-setuptools-scm: setuptools_scm fails to import
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.)


-- 
896418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-setuptools-scm
Version: 1.17.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-setuptools-scm importing the module setuptools_scm
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/setuptools_scm/__init__.py", line 10, 
in 
from .version import format_version, meta, ScmVersion
  File "/usr/lib/python2.7/dist-packages/setuptools_scm/version.py", line 7, in 

from pkg_resources import iter_entry_points
ImportError: No module named pkg_resources

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: setuptools-scm
Source-Version: 1.17.0-2

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated setuptools-scm 
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: Sun, 22 Apr 2018 23:01:46 +0200
Source: setuptools-scm
Binary: python-setuptools-scm python3-setuptools-scm pypy-setuptools-scm
Architecture: source all
Version: 1.17.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Julien Puydt 
Description:
 pypy-setuptools-scm - blessed package to manage your versions by scm tags for 
PyPy
 python-setuptools-scm - blessed package to manage your versions by scm tags 
for Python 2
 python3-setuptools-scm - blessed package to manage your versions by scm tags 
for Python 3
Closes: 896365 896418
Changes:
 setuptools-scm (1.17.0-2) unstable; urgency=medium
 .
   * Refresh packaging:
 - Bump std-vers to 4.1.4.
 - Bump dh compat to 11.
 - Add basic autopkgtest (import).
   * Add missing depends (Closes: #896418, #896365).
Checksums-Sha1:
 bee06b693d075060eae0490bb5466d53422fd393 2450 setuptools-scm_1.17.0-2.dsc
 a936748b1a96c47f5032d45fd24962276fd145ca 3672 
setuptools-scm_1.17.0-2.debian.tar.xz
 81cf7b0b8b267eb01caa79b1c7e0923aa80edc25 18720 
pypy-setuptools-scm_1.17.0-2_all.deb
 a6381053cc03ab18e84d1e0730cc8edb02568f6d 19168 
python-setuptools-scm_1.17.0-2_all.deb
 1a08c0a72a8f18397a86dab1fc7189be687306ee 18736 
python3-setuptools-scm_1.17.0-2_all.deb
 ae759ecb8b17cc7d1fbd16ce23b5520d9f20b809 8679 
setuptools-scm_1.17.0-2_amd64.buildinfo
Checksums-Sha256:
 4c6d1050692f84411ac94d352383f0c118f8bf11571e6dee0cf5a4e0638ccb1b 2450 
setuptools-scm_1.17.0-2.dsc
 1bea4fd487230bf0da1ddb85f8406367a2b31fb696848d5b89370c4e8ab87210 3672 
setuptools-scm_1.17.0-2.debian.tar.xz
 fc8d0cbc03562cfeb8d94e7c7ae1c244af2c4b82bc2b7c5d2b4b5708a17d84d7 18720 
pypy-setuptools-scm_1.17.0-2_all.deb
 1d1b3e0350e959a520426c5c9834618a021107f7137f94de884ecc119ff04bcf 19168 
python-setuptools-scm_1.17.0-2_all.deb
 8c2deac13502985f657d88f84fd1e4a8812fe925cea8d8276949f5afca82855f 18736 
python3-setuptools-scm_1.17.0-2_all.deb
 16b982fd46bbfafc771fc94956100b27e20a7f6a81936b6818c6e9436eb6e111 8679 
setuptools-scm_1.17.0-2_amd64.buildinfo
Files:
 a5f047bac9cd63cfa5806027d45916fd 2450 python optional 

Bug#873972: marked as done (FTBFS with Java 9 due to -source/-target only)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:34:23 +
with message-id 
and subject line Bug#873972: fixed in cadencii 3.3.9+svn20110818.r1732-6
has caused the Debian Bug report #873972,
regarding FTBFS with Java 9 due to -source/-target only
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.)


-- 
873972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cadencii
Version: 3.3.9+svn20110818.r1732
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

./build/java/org/kbinani/windows/forms/*.java 
./build/java/org/kbinani/xml/*.java -encoding UTF8 -target 1.5 -source 1.5
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
Makefile:1081: recipe for target 'jcadencii' failed

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: cadencii
Source-Version: 3.3.9+svn20110818.r1732-6

We believe that the bug you reported is fixed in the latest version of
cadencii, 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.
Ying-Chun Liu (PaulLiu)  (supplier of updated cadencii 
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: Mon, 23 Apr 2018 03:15:19 +0800
Source: cadencii
Binary: jcadencii
Architecture: source all
Version: 3.3.9+svn20110818.r1732-6
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 jcadencii  - Piano roll editor for singing synthesis
Closes: 873972
Changes:
 cadencii (3.3.9+svn20110818.r1732-6) unstable; urgency=low
 .
   [ Markus Koschany  ]
   * Fix FTBFS with Java 9. (Closes: #873972)
 .
   [ Ying-Chun Liu (PaulLiu)  ]
   * Fix upstream URL and copyright file
   * More lintian-overrides about missing source of javascript code.
 - It is source but just with a long data line.
Checksums-Sha1:
 263508f5369febd11815ecc2a210849de0368534 1930 
cadencii_3.3.9+svn20110818.r1732-6.dsc
 e2efd798bf77a6bedf73a6c0e5d1dee0855eb9bb 8916 
cadencii_3.3.9+svn20110818.r1732-6.debian.tar.xz
 7383b5eb1b56ecad4745490257604b28767dc8e5 11839 
cadencii_3.3.9+svn20110818.r1732-6_amd64.buildinfo
 41bbffe0e34f95fd1c69d819fdcc621cf266fb83 6032624 
jcadencii_3.3.9+svn20110818.r1732-6_all.deb
Checksums-Sha256:
 c1382aba7ceba0c856f7599fd004dc2be99beccb2ceb1b23fcad5c81ac395c8a 1930 
cadencii_3.3.9+svn20110818.r1732-6.dsc
 f30120f402677ab2a241338250bf9e00f92e8791d79fc8c8f84b0de98dc9aff1 8916 
cadencii_3.3.9+svn20110818.r1732-6.debian.tar.xz
 08ce91226665a2f8373aeb4cf635e37a4bc44d35ae1970664867e3c456091ce2 11839 
cadencii_3.3.9+svn20110818.r1732-6_amd64.buildinfo
 8292159a4159b6c7140d5894019ed1e1270494848e3ae25fd39a5a3a9899a93a 6032624 
jcadencii_3.3.9+svn20110818.r1732-6_all.deb
Files:
 92fdf67e3c75cfe4b4f40f7cc240fd7e 1930 sound optional 
cadencii_3.3.9+svn20110818.r1732-6.dsc
 325314f3294957c91fbfef1b32541f75 8916 sound optional 
cadencii_3.3.9+svn20110818.r1732-6.debian.tar.xz
 79874ddc9d2e6ea4905df7e08945292f 11839 sound optional 
cadencii_3.3.9+svn20110818.r1732-6_amd64.buildinfo
 e72e425661609e39d6349e046247aec7 6032624 sound optional 

Bug#893196: marked as done (javassist FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:09:19 +
with message-id 
and subject line Bug#893196: fixed in javassist 1:3.21.0-2
has caused the Debian Bug report #893196,
regarding javassist FTBFS with openjdk-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.)


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

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

...
[ERROR] Failed to execute goal on project javassist: Could not resolve 
dependencies for project org.javassist:javassist:bundle:3.21.0-GA: Could not 
find artifact com.sun:tools:jar:debian at specified path 
/usr/lib/jvm/java-9-openjdk-amd64/../lib/tools.jar -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/javassist-3.21.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/javassist-3.21.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/javassist-3.21.0/debian 
-Dmaven.repo.local=/build/1st/javassist-3.21.0/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Source: javassist
Source-Version: 1:3.21.0-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated javassist 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: Sun, 22 Apr 2018 22:14:58 +0200
Source: javassist
Binary: libjavassist-java libjavassist-java-doc
Architecture: source
Version: 1:3.21.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libjavassist-java - library for editing bytecodes in Java
 libjavassist-java-doc - library for editing bytecodes in Java -- documentation
Closes: 893196
Changes:
 javassist (1:3.21.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Switch to compat level 11.
   * wrap-and-sort -sa.
   * Declare compliance with Debian Policy 4.1.4.
   * Add java9.patch and disable the tests. (Closes: #893196)
Checksums-Sha1:
 78c90918286144fd7a9130c12dc5a85b248d0c87 2333 javassist_3.21.0-2.dsc
 24de7fd597ae3505e1bc6ee9b6962db65f6f0831 5464 javassist_3.21.0-2.debian.tar.xz
 2ce8efefcee909d6ac47b8fd36fb27767d0bff8b 16101 
javassist_3.21.0-2_amd64.buildinfo
Checksums-Sha256:
 420981f57afe5cd2577195a83752cea10dddb3bfd9febbad778c5f410dcdbe66 2333 
javassist_3.21.0-2.dsc
 b1f6a1fdf7503f8afb081275cb60a2a6f558ae404861c27a09d6fbefdede7564 5464 
javassist_3.21.0-2.debian.tar.xz
 44426baf45bf2de1c9791ea53a6199b75acfdf3e92145697a43b13157fb40154 16101 
javassist_3.21.0-2_amd64.buildinfo
Files:
 948d029c81658a43970a05b1acbc7d56 2333 java optional javassist_3.21.0-2.dsc
 bea27f401e17f98413a43d138b9c988f 5464 java optional 
javassist_3.21.0-2.debian.tar.xz
 c66aae972333fb0c55c2bc60d07b6a55 16101 java optional 
javassist_3.21.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlrc7tFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD

Bug#896593: marked as done (redisearch: baseline violation in i386/amd64 and FTBFS everywhere else)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:10:31 +
with message-id 
and subject line Bug#896593: fixed in redisearch 1.0.10-2
has caused the Debian Bug report #896593,
regarding redisearch: baseline violation in i386/amd64 and FTBFS everywhere else
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.)


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

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

...
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-unused-function 
-Wno-unused-variable -Wno-unused-result -fPIC 
-Werror=implicit-function-declaration -D_GNU_SOURCE -std=gnu99 
-I"/<>/src" -DREDIS_MODULE_TARGET -DREDISMODULE_EXPERIMENTAL_API  
-g -ggdb -O3  -mpopcnt -Wdate-time -D_FORTIFY_SOURCE=2  -c 
/<>/src/buffer.c -o /<>/src/buffer.o -MMD -MF 
/<>/src/buffer.d
cc: error: unrecognized command line option '-mpopcnt'
Makefile:74: recipe for target '/<>/src/buffer.o' failed
make[2]: *** [/<>/src/buffer.o] Error 1
--- End Message ---
--- Begin Message ---
Source: redisearch
Source-Version: 1.0.10-2

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redisearch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Apr 2018 22:16:23 +0200
Source: redisearch
Binary: redis-redisearch redis-redisearch-doc
Architecture: source amd64 all
Version: 1.0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 redis-redisearch - Full-text and secondary search index engine module for Redis
 redis-redisearch-doc - Full-text and secondary search index engine module for 
Redis (doc
Closes: 896593
Changes:
 redisearch (1.0.10-2) unstable; urgency=medium
 .
   * Drop -mpopcnt from CLAGS. This was added upstream in
 
.
 (Closes: #896593)
Checksums-Sha1:
 f277991644edfb5d224ece2179f9b1254ad45605 1971 redisearch_1.0.10-2.dsc
 742b1d7a242119f8a51b6bbe085a8cb216370cab 10632 
redisearch_1.0.10-2.debian.tar.xz
 b91a2a96c3b8ae623ffd72e45160525443d52898 921180 
redis-redisearch-dbgsym_1.0.10-2_amd64.deb
 34ec137051e7dc1ddd9668fb638bfd4d796a5122 112724 
redis-redisearch-doc_1.0.10-2_all.deb
 e8d00a8abc27eca04ecac4297eab585d8ac85a75 1042796 
redis-redisearch_1.0.10-2_amd64.deb
 e72b47b3f1bbec680805f159ad0508a2d0a60f6b 5932 
redisearch_1.0.10-2_amd64.buildinfo
Checksums-Sha256:
 17d8acdda7e71a6ee160625166301553ebaf4a8ab510c1fbf0b7627a61cce6dc 1971 
redisearch_1.0.10-2.dsc
 6e6a0d022a607bbec4cf127a1aab8d4d92c526f92d9416f9e37776ae7bd31406 10632 
redisearch_1.0.10-2.debian.tar.xz
 0c607be22c7572e90a290b39c8c7bcd9f82364ba87f8040c830eb17e08150b57 921180 
redis-redisearch-dbgsym_1.0.10-2_amd64.deb
 74828b71f9e715d2f862db24eb6c1c9cf5c8e5d93944139ec604f0a9bc5c0c85 112724 
redis-redisearch-doc_1.0.10-2_all.deb
 da74474c2fdc806cb7fab440ba24348ca16ec51868b5e41b8acc8140466d2033 1042796 
redis-redisearch_1.0.10-2_amd64.deb
 19cf85265ef33c099d09aff3d6073468c10b8f5efddd4e8d06cd116342091799 5932 
redisearch_1.0.10-2_amd64.buildinfo
Files:
 7b33928ad9e0a88203ac87687d5e081a 1971 python optional redisearch_1.0.10-2.dsc
 e16c2afe7958a7de9585c39dbd2847c1 10632 python optional 
redisearch_1.0.10-2.debian.tar.xz
 b370b9edec65b3b869ce95fe0f5a09e5 921180 debug optional 
redis-redisearch-dbgsym_1.0.10-2_amd64.deb
 24b25c653d64383d9e14d085e5b30a9c 112724 doc optional 
redis-redisearch-doc_1.0.10-2_all.deb
 2915df9fad834d8d59cb474d672c90ee 1042796 python optional 
redis-redisearch_1.0.10-2_amd64.deb
 d0ab11ec69d5a2802c69734a9f46ca23 5932 python optional 
redisearch_1.0.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#896612: marked as done (pywps FTBFS with sphinx 1.7.2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:10:13 +
with message-id 
and subject line Bug#896612: fixed in pywps 4.0.0-5
has caused the Debian Bug report #896612,
regarding pywps FTBFS with sphinx 1.7.2
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.)


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

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

...
sphinx-build -W -b html -d _build/doctrees   . _build/html
Running Sphinx v1.7.2
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 12 source files that are out of date
updating environment: 12 added, 0 changed, 0 removed
reading sources... [  8%] api
reading sources... [ 16%] configuration
reading sources... [ 25%] deployment
reading sources... [ 33%] development
reading sources... [ 41%] exceptions
reading sources... [ 50%] external-tools
reading sources... [ 58%] index
reading sources... [ 66%] install
reading sources... [ 75%] migration
reading sources... [ 83%] process
reading sources... [ 91%] pywps
reading sources... [100%] wps


Warning, treated as error:
/build/1st/pywps-4.0.0/docs/process.rst:128:parsing 
u'/build/1st/pywps-4.0.0/docs/demobuffer.py' failed: SyntaxError('invalid 
syntax', ('', 61, 18, 'inputs=inputs,\n'))
make[2]: *** [Makefile:29: html] Error 2
--- End Message ---
--- Begin Message ---
Source: pywps
Source-Version: 4.0.0-5

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated pywps 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: Sun, 22 Apr 2018 22:09:16 +0200
Source: pywps
Binary: python-pywps pywps pywps-wsgi pywps-doc
Architecture: source all
Version: 4.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 python-pywps - Implementation of OGC's Web Processing Service - Python 2 module
 pywps  - Implementation of OGC's Web Processing Service
 pywps-doc  - Implementation of OGC's Web Processing Service - Documentation
 pywps-wsgi - Implementation of OGC's Web Processing Service - WSGI example
Closes: 896612
Changes:
 pywps (4.0.0-5) unstable; urgency=medium
 .
   * Add python3-sphinx to build dependencies.
   * Bump Standards-Version to 4.1.4, no changes.
   * Update copyright-format URL to use HTTPS.
   * Update Vcs-* URLs for Salsa.
   * Add patch fix SyntaxError in demobuffer.py.
 (closes: #896612)
   * Add lintian override for python-foo-but-no-python3-foo.
Checksums-Sha1:
 df786047ed551932c004efd6b519a3026296 2315 pywps_4.0.0-5.dsc
 f210caa2174a4046635ab6ce05c37b2cebf0d1b4 8636 pywps_4.0.0-5.debian.tar.xz
 cdcd6ef3002f7585e363ccf000999f17538cb249 43196 python-pywps_4.0.0-5_all.deb
 14fb9783bb9cea571549f0fde1511b9a441e2201 227432 pywps-doc_4.0.0-5_all.deb
 b569a889d44ad53fc8f453202a1205760dbb048f 6892 pywps-wsgi_4.0.0-5_all.deb
 7af1df89dd6379f1d1cdf99fae4d797ffc2f51f7 5012 pywps_4.0.0-5_all.deb
 5df8ecc4d4f2081ed6d140e7b2e2f8d5de591f52 12189 pywps_4.0.0-5_amd64.buildinfo
Checksums-Sha256:
 28b3777544670d3435539a0cb14c9a1baf62a196f962fa1a2fbe53cdacc1efad 2315 
pywps_4.0.0-5.dsc
 1222ae469fac31071be3488a6b0b09dc58c7445be9961676309f729c25ffa390 8636 
pywps_4.0.0-5.debian.tar.xz
 5531b6c157deae5337a4afd856e1ef54fac1faece768406bf88ab53007f64ad1 43196 
python-pywps_4.0.0-5_all.deb
 73ed1a7b326e04dfff645bde73a78447099b29d8f74bb2906d2ffcfad10f1997 227432 
pywps-doc_4.0.0-5_all.deb
 ba62e50b27b6d279bbbeb32b5becd4e553b273a3ded70a5f256d093aedb8b42b 6892 
pywps-wsgi_4.0.0-5_all.deb
 7deb73ce4868f405493b71e5f9b1f6689ec380163ec1cbe1ae2da6c956280743 5012 
pywps_4.0.0-5_all.deb
 

Bug#896598: [Debian-med-packaging] Bug#896598: libglademm2.4: Intent to Adopt

[Gert Wollny]

Hi Adrian, 

while I generally agree that dropping all the gnome2 related libraries
from Debian is not a good idea, in this case, where aeskulap is the
only reverse dependency I'm aware of, I wonder whether is is really a
good idea to put effort into providing this library package?

Best,
Gert

Bug#896178: marked as done (chktex FTBFS with TeX Live 2018)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:06:52 +
with message-id 
and subject line Bug#896178: fixed in chktex 1.7.6-2
has caused the Debian Bug report #896178,
regarding chktex FTBFS with TeX Live 2018
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.)


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

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

...
/usr/bin/latex ChkTeX.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./ChkTeX.tex
LaTeX2e <2018-04-01> patch level 2
Babel <3.18> and hyphenation patterns for 3 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
No file ChkTeX.aux.
(/usr/share/texlive/texmf-dist/tex/latex/base/t1cmtt.fd)
(/usr/share/texlive/texmf-dist/tex/latex/base/omscmr.fd) [1] [2] [3]
Overfull \hbox (2.21458pt too wide) in paragraph at lines 271--274
[]\T1/cmr/m/n/10 User de-fined reg-u-lar ex-pres-sions are de-fined us-ing \T1/
cmtt/m/n/10 UserWarnRegex
[4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]

! Package inputenc Error: Invalid UTF-8 byte 180.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
 ...  
  
l.1158 ``There�
   s quotes and there�s quotes�� \\* % ''
? 
! Emergency stop.
 ...  
  
l.1158 ``There�
   s quotes and there�s quotes�� \\* % ''
Output written on ChkTeX.dvi (16 pages, 54240 bytes).
Transcript written on ChkTeX.log.
make[1]: *** [Makefile:265: ChkTeX.dvi] Error 1
--- End Message ---
--- Begin Message ---
Source: chktex
Source-Version: 1.7.6-2

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated chktex 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: Sun, 22 Apr 2018 18:40:03 +0200
Source: chktex
Binary: chktex
Architecture: source amd64
Version: 1.7.6-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 chktex - Finds typographic errors in LaTeX
Closes: 896178
Changes:
 chktex (1.7.6-2) unstable; urgency=medium
 .
   * debian/control: add salsa URLs
   * debian/control: use dh11
   * debian/control: bump standard to 4.1.4 (no changes)
   * add patch to fix FTBFS with TeX Live 2018 (Closes: #896178)
 (thanks to Adrian Bunk for the patch)
Checksums-Sha1:
 fbd2df4aa77a7aac73d0bb00907007a575fbc9f0 2048 chktex_1.7.6-2.dsc
 f1deb9ef9d5bd7732334f09c64587ff2c30cdb5f 153071 chktex_1.7.6.orig.tar.gz
 fdf74257e76b2b1e79f74151503fd1a87211aad1 42804 chktex_1.7.6-2.debian.tar.xz
 df2bba7fc6cb6c9e2f486697f409dafd249a0cc2 52516 chktex-dbgsym_1.7.6-2_amd64.deb
 b090c858b9928995293bd8a2dc89c131677a7cd0 8891 chktex_1.7.6-2_amd64.buildinfo
 69bceba03009ed15b12a75ac97a35417bec12b28 97960 chktex_1.7.6-2_amd64.deb
Checksums-Sha256:
 c358436be4e1a1a82cb398cea19a256b7360c58e7814ec5ad2aead0750f29018 2048 
chktex_1.7.6-2.dsc
 8ac0e5ca213b2012d44c28f9e4feb9783df44750eb0c30a237d81ff58ef34c8d 153071 

Bug#896517: marked as done (python-ccnet: missing Breaks+Replaces: libccnet0 (<< 6.1.7))

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 21:06:35 +
with message-id 
and subject line Bug#896517: fixed in ccnet 6.1.7-2
has caused the Debian Bug report #896517,
regarding python-ccnet: missing Breaks+Replaces: libccnet0 (<< 6.1.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.)


-- 
896517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ccnet
Version: 6.1.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python-ccnet.
  Preparing to unpack .../python-ccnet_6.1.7-1_all.deb ...
  Unpacking python-ccnet (6.1.7-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-ccnet_6.1.7-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/ccnet/__init__.py', 
which is also in package libccnet0:amd64 6.1.5-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-ccnet_6.1.7-1_all.deb


cheers,

Andreas


libccnet0=6.1.5-1_python-ccnet=6.1.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ccnet
Source-Version: 6.1.7-2

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

Debian distribution maintenance software
pp.
Moritz Schlarb  (supplier of updated ccnet 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: Sun, 22 Apr 2018 22:10:12 +0200
Source: ccnet
Binary: ccnet libccnet0 libccnet-dev python-ccnet
Architecture: source amd64 all
Version: 6.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Moritz Schlarb 
Description:
 ccnet  - Common tools, client and server for the Ccnet framework
 libccnet-dev - Development files for the Ccnet framework
 libccnet0  - Shared library for the Ccnet framework
 python-ccnet - Python bindings for the Ccnet framework
Closes: 896517
Changes:
 ccnet (6.1.7-2) unstable; urgency=medium
 .
   * Add Breaks+Replaces (Closes: #896517)
   * Update debhelper to current standard
   * Remove unused lintian override possible-gpl-code-linked-with-openssl
   * Update debian/patches from gbp pq
Checksums-Sha1:
 1b62e12a2c36c75c6852404e0f5eb79b48742323 2241 ccnet_6.1.7-2.dsc
 ccf78bec53a959476fc36a19dd4cb76c8141e461 6972 ccnet_6.1.7-2.debian.tar.xz
 c4dc54123a05772b366357f4d32f23fe2f0ca8ec 346264 ccnet-dbgsym_6.1.7-2_amd64.deb
 bf47207d6733e119c2bc01ce6a3b4b21f1078129 9228 ccnet_6.1.7-2_amd64.buildinfo
 52e1a732d9eaae863828b4d1079cc35473d4f662 69272 ccnet_6.1.7-2_amd64.deb
 b18a57003baa1ac74838dbfcfc6acf311b889e43 52356 libccnet-dev_6.1.7-2_amd64.deb
 05a6fe4b65f05e90ff19acf708050201dd2d2b36 161628 
libccnet0-dbgsym_6.1.7-2_amd64.deb
 c8022e12c67ac178f147123a5b3c3775b7606f9c 40444 libccnet0_6.1.7-2_amd64.deb
 59aef3861cb462cf984635ad93f39a212cb60b3a 14376 python-ccnet_6.1.7-2_all.deb
Checksums-Sha256:
 49476b4b5d6b82aa8580c40b5992d9a086b329f4aa9d777c48c7cc483934b5ec 2241 
ccnet_6.1.7-2.dsc
 c01d787e7b8bbe19d93655346b9ac4fcd5522471675c77fb337cb42bea48df3c 6972 
ccnet_6.1.7-2.debian.tar.xz
 7f8ffde1aa9012680f865fdeb6dd1caf9a5474d8889e18b7bd559ada42e155ce 346264 
ccnet-dbgsym_6.1.7-2_amd64.deb
 c0e6d312fb10fa12f25092761992d9a08c9c9e429dbf3c06cdc18bc8cf2a6000 9228 
ccnet_6.1.7-2_amd64.buildinfo
 964fd1715b0a60caea311b86bdbe6e855458f5dd4111a34a6502cc98c74ff9ee 69272 
ccnet_6.1.7-2_amd64.deb
 a363d0777fe2dbb89a8a9db2c2a514576f0929d353cd3e4306ab441942bbe1e1 52356 
libccnet-dev_6.1.7-2_amd64.deb
 

Bug#893554: range-v3 FTBFS

[Коля Гурьев]

Hi,

19.03.2018 23:54, Adrian Bunk пишет:
> Some recent change in unstable makes range-v3 FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/range-v3.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/range-v3.html

I can't reproduce these errors with gcc 7.3.0-15 or above. That version
has fixed a bug[1] related to similar errors.

Could you please rebuild the range-v3 package by yourself and tell about
compilation results against the latest gcc-7 package?

 [1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85118

Processed: Re: Bug#893526: mrs: FTBFS on 32-bit arches - error: format not a string literal and no format arguments

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 mrs FTBFS: error: format not a string literal and no format 
> arguments
Bug #893526 [src:mrs] mrs: FTBFS on 32-bit arches - error: format not a string 
literal and no format arguments
Changed Bug title to 'mrs FTBFS: error: format not a string literal and no 
format arguments' from 'mrs: FTBFS on 32-bit arches - error: format not a 
string literal and no format arguments'.
> severity -1 serious
Bug #893526 [src:mrs] mrs FTBFS: error: format not a string literal and no 
format arguments
Severity set to 'serious' from 'important'

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

Processed: debian-cd: Unable to build CD image with unsigned repository

[Debian Bug Tracking System]

Processing control commands:

> block 879642 by -1
Bug #879642 [simple-cdd] simple-cdd: build-simple-cdd fails with unsigned local 
repository
879642 was not blocked by any bugs.
879642 was not blocking any bugs.
Added blocking bug(s) of 879642: 896638

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

Bug#896517: Bug #896517 in ccnet marked as pending

[schlarbm]

Control: tag -1 pending

Hello,

Bug #896517 in ccnet reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/debian/ccnet/commit/f0eba48ee6edfb30619fa2305b9e6728b0e67e44


Add Breaks+Replaces (Closes: #896517)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896517

Processed: Bug #896517 in ccnet marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896517 [python-ccnet] python-ccnet: missing Breaks+Replaces: libccnet0 (<< 
6.1.7)
Added tag(s) pending.

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

Processed: Re: redisearch: baseline violation in i386/amd64 and FTBFS everywhere else

[Debian Bug Tracking System]

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

> tags 896593 + pending
Bug #896593 [src:redisearch] redisearch: baseline violation in i386/amd64 and 
FTBFS everywhere else
Added tag(s) pending.
> forwarded 896593 https://github.com/RedisLabsModules/RediSearch/issues/313
Bug #896593 [src:redisearch] redisearch: baseline violation in i386/amd64 and 
FTBFS everywhere else
Set Bug forwarded-to-address to 
'https://github.com/RedisLabsModules/RediSearch/issues/313'.
> thanks
Stopping processing here.

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

Bug#896593: redisearch: baseline violation in i386/amd64 and FTBFS everywhere else

[Chris Lamb]

tags 896593 + pending
forwarded 896593 https://github.com/RedisLabsModules/RediSearch/issues/313
thanks

I've forwarded this upstream here and patched it locally for the
time being:

  https://github.com/RedisLabsModules/RediSearch/issues/313


Regards,

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

Processed: tagging 896612

[Debian Bug Tracking System]

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

> tags 896612 + pending
Bug #896612 [src:pywps] pywps FTBFS with sphinx 1.7.2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Split into individual bugs

[Debian Bug Tracking System]

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

> affects 896485 =
Bug #896485 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Removed indication that 896485 affects src:pyevolve, src:pygments, 
src:python-biom-format, src:alembic, src:python-numpy, src:mako, src:julia, 
src:python-scipy, src:bcfg2, src:python-cryptography, src:python-saharaclient, 
src:dipy, src:python-click, src:sphinx-argparse, src:bottleneck, 
src:python-expyriment, src:prospector, src:pymvpa2, src:heat, and src:pyfr
> clone 896485 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 
> -19
Bug #896485 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug 896485 cloned as bugs 896618-896636
> reassign 896485 src:alembic 0.9.7-1
Bug #896485 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:alembic'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896485 to the same values 
previously set
Bug #896485 [src:alembic] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Marked as found in versions alembic/0.9.7-1.
> tags 896485 buster sid
Bug #896485 [src:alembic] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Added tag(s) buster and sid.
> reassign -1 src:bcfg2 1.4.0~pre2+git141-g6d40dace6358-1
Bug #896618 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:bcfg2'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896618 to the same values 
previously set
Bug #896618 [src:bcfg2] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked as found in versions bcfg2/1.4.0~pre2+git141-g6d40dace6358-1.
> tags -1 buster sid
Bug #896618 [src:bcfg2] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Added tag(s) sid and buster.
> reassign -2 src:bottleneck 1.2.0-6
Bug #896619 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:bottleneck'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896619 to the same values 
previously set
Bug #896619 [src:bottleneck] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Marked as found in versions bottleneck/1.2.0-6.
> tags -2 buster sid
Bug #896619 [src:bottleneck] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Added tag(s) buster and sid.
> reassign -3 src:dipy 0.13.0-2
Bug #896620 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:dipy'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896620 to the same values 
previously set
Bug #896620 [src:dipy] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked as found in versions dipy/0.13.0-2.
> tags -3 buster sid
Bug #896620 [src:dipy] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Added tag(s) buster and sid.
> reassign -4 src:heat 1:10.0.0-2
Bug #896621 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:heat'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896621 to the same values 
previously set
Bug #896621 [src:heat] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked as found in versions heat/1:10.0.0-2.
> tags -4 buster sid
Bug #896621 [src:heat] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Added tag(s) buster and sid.
> reassign -5 src:julia 0.4.7-7
Bug #896622 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:julia'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896622 to the same values 
previously set
Bug #896622 [src:julia] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked as found in versions julia/0.4.7-7.
> tags -5 buster sid
Bug #896622 [src:julia] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Added tag(s) buster and sid.
> reassign -6 src:mako 1.0.7+ds1-1
Bug #896623 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Bug reassigned from package 'src:sphinx' to 'src:mako'.
No longer marked as found in versions sphinx/1.7.2-1.
Ignoring request to alter fixed versions of bug #896623 to the same values 
previously set
Bug #896623 [src:mako] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked as found in versions mako/1.0.7+ds1-1.
> tags -6 buster sid
Bug #896623 [src:mako] FTBFS with sphinx 1.7.2: 

Processed: tagging 896592

[Debian Bug Tracking System]

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

> tags 896592 + pending
Bug #896592 [src:val-and-rick] val-and-rick FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896591

[Debian Bug Tracking System]

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

> tags 896591 + pending
Bug #896591 [src:tumiki-fighters] tumiki-fighters FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896587

[Debian Bug Tracking System]

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

> tags 896587 + pending
Bug #896587 [src:projectl] projectl FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896590

[Debian Bug Tracking System]

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

> tags 896590 + pending
Bug #896590 [src:torus-trooper] torus-trooper FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896588

[Debian Bug Tracking System]

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

> tags 896588 + pending
Bug #896588 [src:tatan] tatan FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896584

[Debian Bug Tracking System]

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

> tags 896584 + pending
Bug #896584 [src:ii-esu] ii-esu FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896589

[Debian Bug Tracking System]

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

> tags 896589 + pending
Bug #896589 [src:titanion] titanion FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896585

[Debian Bug Tracking System]

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

> tags 896585 + pending
Bug #896585 [src:mu-cade] mu-cade FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896586

[Debian Bug Tracking System]

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

> tags 896586 + pending
Bug #896586 [src:parsec47] parsec47 FTBFS with gdc 8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896612, bug 896612 is forwarded to https://github.com/geopython/pywps/issues/339

[Debian Bug Tracking System]

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

> tags 896612 + upstream
Bug #896612 [src:pywps] pywps FTBFS with sphinx 1.7.2
Added tag(s) upstream.
> forwarded 896612 https://github.com/geopython/pywps/issues/339
Bug #896612 [src:pywps] pywps FTBFS with sphinx 1.7.2
Set Bug forwarded-to-address to 'https://github.com/geopython/pywps/issues/339'.
> thanks
Stopping processing here.

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

Bug#896616: sfepy FTBFS with sphinx 1.7.2

[Adrian Bunk]

Source: sfepy
Version: 2016.2-4
Severity: serious

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

...
optional arguments
---
/build/1st/sfepy-2016.2/doc/release_notes.rst:640: WARNING: Inline strong 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:816: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:1003: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:1004: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:1723: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:4324: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:4451: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:6151: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/doc/release_notes.rst:3470: WARNING: Undefined 
substitution referenced: "TL - UL".
/build/1st/sfepy-2016.2/doc/release_notes.rst:3470: WARNING: Undefined 
substitution referenced: "UL - UL_mixed".
/build/1st/sfepy-2016.2/doc/release_notes.rst:3746: WARNING: Unknown target 
name: "d_sd".
/build/1st/sfepy-2016.2/doc/release_notes.rst:5444: WARNING: Unknown target 
name: "call".
/build/1st/sfepy-2016.2/doc/release_notes.rst:6106: WARNING: Unknown target 
name: "dw".
/build/1st/sfepy-2016.2/doc/release_notes.rst:6106: WARNING: Unknown target 
name: "d".
WARNING: autodoc: failed to import module u'postproc'; the module executes 
module level statement and it might call sys.exit().
WARNING: autodoc: failed to import module u'gen_gallery'; the module executes 
module level statement and it might call sys.exit().
WARNING: autodoc: failed to import module u'gen_iga_patch'; the following 
exception was raised:
No module named _tkinter, please install the python-tk package
WARNING: autodoc: failed to import module u'gen_lobatto1d_c'; the following 
exception was raised:
No module named _tkinter, please install the python-tk package
WARNING: autodoc: failed to import module u'plot_condition_numbers'; the 
following exception was raised:
No module named _tkinter, please install the python-tk package
WARNING: autodoc: failed to import module u'plot_logs'; the following exception 
was raised:
No module named _tkinter, please install the python-tk package
WARNING: autodoc: failed to import module u'plot_mesh'; the following exception 
was raised:
No module named _tkinter, please install the python-tk package
WARNING: autodoc: failed to import module u'plot_quadratures'; the following 
exception was raised:
No module named _tkinter, please install the python-tk package
WARNING: autodoc: failed to import module u'plot_times'; the following 
exception was raised:
No module named _tkinter, please install the python-tk package
/build/1st/sfepy-2016.2/sfepy/discrete/fem/facets.py:docstring of 
sfepy.discrete.fem.facets:25: WARNING: Block quote ends without a blank line; 
unexpected unindent.
/build/1st/sfepy-2016.2/sfepy/discrete/fem/mesh.py:docstring of 
sfepy.discrete.fem.mesh.Mesh.from_file:13: WARNING: Inline emphasis 
start-string without end-string.
/build/1st/sfepy-2016.2/sfepy/discrete/fem/mesh.py:docstring of 
sfepy.discrete.fem.mesh.Mesh.from_file:15: WARNING: Inline emphasis 
start-string without end-string.
WARNING: autodoc: failed to import module u'sfepy.discrete.iga.plot_nurbs'; the 
following exception was raised:
No module named _tkinter, please install the python-tk package
docstring of sfepy.discrete.simplex_cubature.generate_permutations:2: WARNING: 
Inline interpreted text or phrase reference start-string without end-string.
docstring of sfepy.discrete.simplex_cubature.generate_unique_permutations:2: 
WARNING: Inline interpreted text or phrase reference start-string without 
end-string.

Exception occurred:
  File "/usr/lib/python2.7/dist-packages/sphinx/pycode/__init__.py", line 103, 
in parse
raise PycodeError('parsing %r failed: %r' % (self.srcname, exc))
PycodeError: parsing 
'/build/1st/sfepy-2016.2/sfepy/discrete/simplex_cubature.py' failed: 
AttributeError("'Tuple' object has no attribute 'id'",)
The full traceback has been saved in /tmp/sphinx-err-w0QH1X.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[3]: *** [Makefile:70: latex] Error 2

Bug#896614: pyxb FTBFS with sphinx 1.7.2

[Adrian Bunk]

Source: pyxb
Version: 1.2.6+dfsg-1
Severity: serious

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

...
PYTHONPATH=.:doc sphinx-build -b html -d _build/.doctrees -N doc _build/html
Running Sphinx v1.7.2
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 27 source files that are out of date
updating environment: 27 added, 0 changed, 0 removed
reading sources... [  3%] arch_binding
reading sources... [  7%] arch_component
reading sources... [ 11%] arch_content
reading sources... [ 14%] arch_namespaces
reading sources... [ 18%] architecture
reading sources... [ 22%] bundles
reading sources... [ 25%] examples
reading sources... [ 29%] index
reading sources... [ 33%] legal
reading sources... [ 37%] limitations
reading sources... [ 40%] maintref
reading sources... [ 44%] overview
reading sources... [ 48%] overview_how
reading sources... [ 51%] overview_what
reading sources... [ 55%] pyxb
reading sources... [ 59%] pyxb.binding
reading sources... [ 62%] pyxb.namespace
reading sources... [ 66%] pyxb.utils
/build/1st/pyxb-1.2.6+dfsg/pyxb/__init__.py:docstring of pyxb.cscRoot:16: 
WARNING: Duplicate ID: "module-pyxb".
/build/1st/pyxb-1.2.6+dfsg/pyxb/__init__.py:docstring of pyxb:6: WARNING: 
Unknown target name: "pyxb.exceptions".
/build/1st/pyxb-1.2.6+dfsg/pyxb/__init__.py:docstring of pyxb:6: WARNING: 
Unknown target name: "pyxb.exceptions".
/build/1st/pyxb-1.2.6+dfsg/pyxb/binding/facets.py:docstring of 
pyxb.binding.facets.Facet._setFromKeywords_vb:10: WARNING: Definition list ends 
without a blank line; unexpected unindent.
/build/1st/pyxb-1.2.6+dfsg/pyxb/utils/activestate.py:docstring of 
pyxb.utils.activestate.detectXMLEncoding:7: WARNING: Bullet list ends without a 
blank line; unexpected unindent.
/build/1st/pyxb-1.2.6+dfsg/pyxb/utils/activestate.py:docstring of 
pyxb.utils.activestate.detectXMLEncoding:10: WARNING: Bullet list ends without 
a blank line; unexpected unindent.
/build/1st/pyxb-1.2.6+dfsg/pyxb/utils/activestate.py:docstring of 
pyxb.utils.activestate.detectXMLEncoding:15: WARNING: Bullet list ends without 
a blank line; unexpected unindent.

Exception occurred:
  File "/usr/lib/python3.6/dbm/gnu.py", line 6, in 
raise ImportError(str(msg) + ', please install the python3-gdbm package')
ImportError: No module named '_gdbm', please install the python3-gdbm package
The full traceback has been saved in /tmp/sphinx-err-j94e23zt.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2

Bug#896613: cloud-sptheme FTBFS with sphinx 1.7.2

[Adrian Bunk]

Source: cloud-sptheme
Version: 1.8.0-1
Severity: serious
Tags: buster sid

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

...
Running Sphinx v1.7.2
WARNING: while setting up extension cloud_sptheme.ext.table_styling: directive 
'table' is already registered, it will be overridden
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 18 source files that are out of date
updating environment: 18 added, 0 changed, 0 removed
reading sources... [  5%] cloud_theme
reading sources... [ 11%] cloud_theme_test
reading sources... [ 16%] contents
reading sources... [ 22%] copyright
reading sources... [ 27%] history
reading sources... [ 33%] index
reading sources... [ 38%] install
reading sources... [ 44%] lib/cloud_sptheme
reading sources... [ 50%] lib/cloud_sptheme.ext.autoattribute_search_bases
reading sources... [ 55%] lib/cloud_sptheme.ext.autodoc_sections
reading sources... [ 61%] lib/cloud_sptheme.ext.docfield_markup
reading sources... [ 66%] lib/cloud_sptheme.ext.escaped_samp_literals
reading sources... [ 72%] lib/cloud_sptheme.ext.index_styling
reading sources... [ 77%] lib/cloud_sptheme.ext.issue_tracker
reading sources... [ 83%] lib/cloud_sptheme.ext.page_only
reading sources... [ 88%] lib/cloud_sptheme.ext.relbar_toc
reading sources... [ 94%] lib/cloud_sptheme.ext.role_index
reading sources... [100%] lib/cloud_sptheme.ext.table_styling

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  5%] cloud_theme
writing output... [ 11%] cloud_theme_test
writing output... [ 16%] contents
writing output... [ 22%] copyright
writing output... [ 27%] history
writing output... [ 33%] index
writing output... [ 38%] install
writing output... [ 44%] lib/cloud_sptheme
writing output... [ 50%] lib/cloud_sptheme.ext.autoattribute_search_bases
writing output... [ 55%] lib/cloud_sptheme.ext.autodoc_sections
writing output... [ 61%] lib/cloud_sptheme.ext.docfield_markup
writing output... [ 66%] lib/cloud_sptheme.ext.escaped_samp_literals
writing output... [ 72%] lib/cloud_sptheme.ext.index_styling
writing output... [ 77%] lib/cloud_sptheme.ext.issue_tracker
writing output... [ 83%] lib/cloud_sptheme.ext.page_only
writing output... [ 88%] lib/cloud_sptheme.ext.relbar_toc
writing output... [ 94%] lib/cloud_sptheme.ext.role_index
writing output... [100%] lib/cloud_sptheme.ext.table_styling

generating indices... genindex py-modindex

Exception occurred:
  File "/build/1st/cloud-sptheme-1.8.0/cloud_sptheme/ext/role_index.py", line 
58, in write_role_index
if app.buildername != "html":
AttributeError: 'Sphinx' object has no attribute 'buildername'
The full traceback has been saved in /tmp/sphinx-err-C2MCnx.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2

Bug#896611: portabase FTBFS with sphinx 1.7.2

[Adrian Bunk]

Source: portabase
Version: 2.1+git20120910-1.1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/portabase-2.1+git20120910'
for lang in en cs fr ja zh_TW; do \
dh_sphinxdoc -v usr/share/portabase/help/$lang ;\
done
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
dh_sphinxdoc: DOCUMENTATION_OPTIONS does not define HAS_SOURCE
make[1]: *** [debian/rules:56: override_dh_sphinxdoc] Error 2

Bug#896612: pywps FTBFS with sphinx 1.7.2

[Adrian Bunk]

Source: pywps
Version: 4.0.0-4
Severity: serious

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

...
sphinx-build -W -b html -d _build/doctrees   . _build/html
Running Sphinx v1.7.2
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 12 source files that are out of date
updating environment: 12 added, 0 changed, 0 removed
reading sources... [  8%] api
reading sources... [ 16%] configuration
reading sources... [ 25%] deployment
reading sources... [ 33%] development
reading sources... [ 41%] exceptions
reading sources... [ 50%] external-tools
reading sources... [ 58%] index
reading sources... [ 66%] install
reading sources... [ 75%] migration
reading sources... [ 83%] process
reading sources... [ 91%] pywps
reading sources... [100%] wps


Warning, treated as error:
/build/1st/pywps-4.0.0/docs/process.rst:128:parsing 
u'/build/1st/pywps-4.0.0/docs/demobuffer.py' failed: SyntaxError('invalid 
syntax', ('', 61, 18, 'inputs=inputs,\n'))
make[2]: *** [Makefile:29: html] Error 2

Bug#896179: qspeakers FTBFS with Qt 5.10

[Benoît Rouits]

Hello Georges,

Great, thank you.
Does the bug closes automagically thanks to changelog ?
or is there an action i should do for closing it now ?

P.S: i created ben-guest account on salsa.d.o
 can you add me as a member of qspeakers project ?

Thank you for having uploaded to Debian so quickly.
 Benoît
Le 22/04/2018 à 15:53, Georges Khaznadar a écrit :
> Hello Benoît,
> 
> I am making a few modifications : the VCS repository is changed to
> https://salsa.debian.org/georgesk/qspeakers.git, in order to fix the
> current error reported about it: 
> 
>   Last scan: 2018-04-22 02:10:10+00
>   Error: debian/changelog missing in 
> svn://svn.gtmp.org/qspeakers/branches/qtcharts/
> 
> I shall upload the package shortly.
> Please create a guest account at https://signup.salsa.debian.org/, so
> you can maintain the package there. Please use git branches and tags
> consistently: there should be at least two branches, "master" and
> "upstream", which are supposed to differ only by the debian/
> subdirectory in the "master" branch. Currently, tags are:
> 
>   debian/1.2.0-1
>   upstream/1.2.0
> 
> New tags should use such a naming scheme.
> 
> Best regards, Georges.
> 
> 
> Benoît Rouits a écrit :
>> Thank you for your report,
>>
>> This has been just fixed upstream, thanks to you.
>> The package is waiting to be uploaded by my mentor.
>>
>> https://mentors.debian.net/package/qspeakers
>>
>>  Benoît
>> Le 20/04/2018 à 16:17, Adrian Bunk a écrit :
>>> Source: qspeakers
>>> Version: 1.1.0-1
>>> Severity: serious
>>> Tags: buster sid
>>>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qspeakers.html
>>>
>>> ...
>>> g++ -Wl,-z,relro -o qspeakers main.o mainwindow.o speakerdialog.o 
>>> speakerdb.o speaker.o importexport.o box.o sealedbox.o portedbox.o 
>>> bandpassbox.o plot.o listdialog.o searchdialog.o system.o moc_mainwindow.o 
>>> moc_speakerdialog.o moc_plot.o moc_listdialog.o moc_searchdialog.o   
>>> -lQt5PrintSupport -lQt5Widgets -lQt5Gui -lQt5Xml -lQt5Core -lGL -lpthread 
>>> plot.o: In function `Plot::~Plot()':
>>> qspeakers_1.1.0-1/plot.cpp:34: undefined reference to 
>>> `QtCharts::QXYSeries::clear()'
>>> plot.o: In function `Plot::initializeCurve()':
>>> qspeakers_1.1.0-1/plot.cpp:67: undefined reference to 
>>> `QtCharts::QLineSeries::QLineSeries(QObject*)'
>>> qspeakers_1.1.0-1/plot.cpp:68: undefined reference to 
>>> `QtCharts::QAbstractSeries::setUseOpenGL(bool)'
>>> ...
>>>
>>>
>>> Due to the following in qspeakers.pro:
>>> greaterThan(QT_VERSION, 5.8): QT += charts
>>>
>>> This is interpreted as float, so 5.10 < 5.8
>>>
> 



signature.asc
Description: OpenPGP digital signature

Bug#896606: quark-sphinx-theme FTBFS with sphinx 1.7.2

[Adrian Bunk]

Source: quark-sphinx-theme
Version: 0.5.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/quark-sphinx-theme.html

...
==
ERROR: setUpClass (test.test_html_rewrite.TestHTMLCompatOutput)
--
Traceback (most recent call last):
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 102, in 
setUpClass
cls.tags)
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 84, in 
run_sphinx
(args, ret, stdout.getvalue()))
Exception: ['sphinx_build', '-b', 'html', '-N', '-t', 'test_html_compat_alias', 
'/build/1st/quark-sphinx-theme-0.5.0/test/testdoc-html_rewrite', 
'/tmp/tmp-sphinx-build-test-K4SbLi'] returned non-zero exit status 2
--- Output:
usage: setup.py [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
setup.py: error: too few arguments


==
ERROR: setUpClass (test.test_html_rewrite.TestHTMLRewriteFeatures)
--
Traceback (most recent call last):
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 102, in 
setUpClass
cls.tags)
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 84, in 
run_sphinx
(args, ret, stdout.getvalue()))
Exception: ['sphinx_build', '-b', 'html', '-N', '-D', 'quark_html_features=', 
'/build/1st/quark-sphinx-theme-0.5.0/test/testdoc-html_rewrite', 
'/tmp/tmp-sphinx-build-test-MFsQFG'] returned non-zero exit status 2
--- Output:
usage: setup.py [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
setup.py: error: too few arguments


==
ERROR: setUpClass (test.test_html_rewrite.TestHTMLRewriteOutput)
--
Traceback (most recent call last):
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 102, in 
setUpClass
cls.tags)
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 84, in 
run_sphinx
(args, ret, stdout.getvalue()))
Exception: ['sphinx_build', '-b', 'html', '-N', 
'/build/1st/quark-sphinx-theme-0.5.0/test/testdoc-html_rewrite', 
'/tmp/tmp-sphinx-build-test-bqVxkC'] returned non-zero exit status 2
--- Output:
usage: setup.py [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
setup.py: error: too few arguments


==
ERROR: setUpClass (test.test_theme.TestThemeAllSettingsUnset)
--
Traceback (most recent call last):
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 102, in 
setUpClass
cls.tags)
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 84, in 
run_sphinx
(args, ret, stdout.getvalue()))
Exception: ['sphinx_build', '-b', 'html', '-N', '-D', 
'html_theme_options.code_bgcolor=', '-D', 
'html_theme_options.admonition_border=', '-D', 'html_theme_options.body_font=', 
'-D', 'html_theme_options.admonition_fgcolor=', '-D', 
'html_theme_options.warning_fgcolor=', '-D', 
'html_theme_options.headerlink_color=', '-D', 'html_theme_options.xref_color=', 
'-D', 'html_theme_options.text_color=', '-D', 
'html_theme_options.navbar_bgcolor=', '-D', 
'html_theme_options.sidebar_bgcolor=', '-D', 
'html_theme_options.li_extra_indent=', '-D', 
'html_theme_options.sidebar_border=', '-D', 'html_theme_options.code_font=', 
'-D', 'html_theme_options.extra_css_files=', '-D', 
'html_theme_options.pre_bgcolor=', '-D', 'html_theme_options.link_color=', 
'-D', 'html_theme_options.code_font_size=', '-D', 
'html_theme_options.full_browser_extras=', '-D', 
'html_theme_options.admonition_bgcolor=', '-D', 
'html_theme_options.underline_navbar_links=', '-D', 
'html_theme_options.warning_bgcolor=', '-D', 
'html_theme_options.underline_links=', '-D', 
'html_theme_options.body_font_size=', '-D', 'html_theme_options.navbar_color=', 
'/build/1st/quark-sphinx-theme-0.5.0/test/testdoc-theme', 
'/tmp/tmp-sphinx-build-test-k4EDG7'] returned non-zero exit status 2
--- Output:
usage: setup.py [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
setup.py: error: too few arguments


==
ERROR: setUpClass (test.test_theme.TestThemeDefaults)
--
Traceback (most recent call last):
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 102, in 
setUpClass
cls.tags)
  File "/build/1st/quark-sphinx-theme-0.5.0/test/util.py", line 84, in 
run_sphinx
(args, ret, stdout.getvalue()))
Exception: ['sphinx_build', '-b', 'html', '-N', 
'/build/1st/quark-sphinx-theme-0.5.0/test/testdoc-theme', 
'/tmp/tmp-sphinx-build-test-HYoX9I'] returned non-zero exit status 2
--- Output:
usage: setup.py [OPTIONS] SOURCEDIR 

Processed: lucene-solr 896604

[Debian Bug Tracking System]

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

> found 896604 3.6.0+dfsg-1+deb7u3
Bug #896604 [lucene-solr] lucene-solr: CVE-2018-1308 XXE in DataImportHandler
There is no source info for the package 'lucene-solr' at version 
'3.6.0+dfsg-1+deb7u3' with architecture ''
Unable to make a source version for version '3.6.0+dfsg-1+deb7u3'
Marked as found in versions 3.6.0+dfsg-1+deb7u3.
> thanks
Stopping processing here.

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

Processed: affects 896485

[Debian Bug Tracking System]

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

> affects 896485 src:sphinx-argparse
Bug #896485 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Added indication that 896485 affects src:sphinx-argparse
> thanks
Stopping processing here.

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

Bug#896604: lucene-solr: CVE-2018-1308 XXE in DataImportHandler

[Markus Koschany]

Package: lucene-solr
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for lucene-solr.

CVE-2018-1308[0]:
| This vulnerability in Apache Solr 1.2 to 6.6.2 and 7.0.0 to 7.2.1
| relates to an XML external entity expansion (XXE) in the
| `dataConfig=inlinexml` parameter of Solr's
DataImportHandler. It
| can be used as XXE using file/ftp/http protocols in order to read
| arbitrary local files from the Solr server or the internal network.

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-2018-1308
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1308

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#896366: marked as done (python3-sphinx-paramlinks: sphinx_paramlinks fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 19:06:42 +
with message-id 
and subject line Bug#896366: fixed in sphinx-paramlinks 0.3.4-2
has caused the Debian Bug report #896366,
regarding python3-sphinx-paramlinks: sphinx_paramlinks fails to import
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.)


-- 
896366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sphinx-paramlinks
Version: 0.3.4-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-sphinx-paramlinks importing the module 
sphinx_paramlinks
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/sphinx_paramlinks/__init__.py", line 3, 
in 
from .sphinx_paramlinks import setup  # noqa
  File "/usr/lib/python3/dist-packages/sphinx_paramlinks/sphinx_paramlinks.py", 
line 6, in 
from sphinx.util.osutil import copyfile
ModuleNotFoundError: No module named 'sphinx'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: sphinx-paramlinks
Source-Version: 0.3.4-2

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sphinx-paramlinks 
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: Sun, 22 Apr 2018 21:49:37 +0300
Source: sphinx-paramlinks
Binary: python-sphinx-paramlinks python3-sphinx-paramlinks
Architecture: source
Version: 0.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-sphinx-paramlinks - Sphinx extension to make param links linkable 
(Python 2 version)
 python3-sphinx-paramlinks - Sphinx extension to make param links linkable 
(Python 3 version)
Closes: 896288 896366
Changes:
 sphinx-paramlinks (0.3.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove trailing whitespaces
 .
   [ Dmitry Shachnev ]
   * Depend on sphinx (closes: #896288, #896366).
   * Bump Standards-Version to 4.1.4, no changes needed.
   * Update to debhelper compat level 11.
Checksums-Sha1:
 181d827b69d7f2737750114f74ade2aa5a5c53a1 2244 sphinx-paramlinks_0.3.4-2.dsc
 da6ef4d897e3f210cf1ae10e2e2167f2373003dc 2656 
sphinx-paramlinks_0.3.4-2.debian.tar.xz
 bde09884958794ba904e45d8e3933ec631d8cadf 6022 
sphinx-paramlinks_0.3.4-2_source.buildinfo
Checksums-Sha256:
 e56e4f649bc0dc7b55add2493e1b4dc8d69301bd055cb583c28ab5738da5b420 2244 
sphinx-paramlinks_0.3.4-2.dsc
 0c5cff0714b55d431993b3afebd60f25566d5bf3e6345a28fd5983821edd8928 2656 
sphinx-paramlinks_0.3.4-2.debian.tar.xz
 4142bca4b29f3507f1dfb02457996c1491c4825a14ad08ef411a823827efd21a 6022 
sphinx-paramlinks_0.3.4-2_source.buildinfo
Files:
 eb6e89a6a95ab1d93e2e88485c311edd 2244 python optional 
sphinx-paramlinks_0.3.4-2.dsc
 592a04b49b934f49d7aef38a5882b0e2 2656 python optional 
sphinx-paramlinks_0.3.4-2.debian.tar.xz
 ef80fd4d0ab040e6f45a9a33647f271e 6022 python optional 
sphinx-paramlinks_0.3.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlrc2Y4ACgkQ1v5xA2P4
XdOQKA//Qd3qexArQ7nDFflYRz4u4lUFwnsdjSFqqV0dQgECMfXzzqIVHZ6BqAJj
Gwh22ZFGn44Q4+iG/cxY6DPe8nF/oDFZKKC4Rs5IcEGG/5eadv+X3iYtUMynrhm0

Bug#896288: marked as done (python-sphinx-paramlinks: sphinx_paramlinks fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 19:06:42 +
with message-id 
and subject line Bug#896288: fixed in sphinx-paramlinks 0.3.4-2
has caused the Debian Bug report #896288,
regarding python-sphinx-paramlinks: sphinx_paramlinks fails to import
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.)


-- 
896288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sphinx-paramlinks
Version: 0.3.4-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-sphinx-paramlinks importing the module sphinx_paramlinks
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/sphinx_paramlinks/__init__.py", line 
3, in 
from .sphinx_paramlinks import setup  # noqa
  File 
"/usr/lib/python2.7/dist-packages/sphinx_paramlinks/sphinx_paramlinks.py", line 
6, in 
from sphinx.util.osutil import copyfile
ImportError: No module named sphinx.util.osutil

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: sphinx-paramlinks
Source-Version: 0.3.4-2

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sphinx-paramlinks 
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: Sun, 22 Apr 2018 21:49:37 +0300
Source: sphinx-paramlinks
Binary: python-sphinx-paramlinks python3-sphinx-paramlinks
Architecture: source
Version: 0.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-sphinx-paramlinks - Sphinx extension to make param links linkable 
(Python 2 version)
 python3-sphinx-paramlinks - Sphinx extension to make param links linkable 
(Python 3 version)
Closes: 896288 896366
Changes:
 sphinx-paramlinks (0.3.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove trailing whitespaces
 .
   [ Dmitry Shachnev ]
   * Depend on sphinx (closes: #896288, #896366).
   * Bump Standards-Version to 4.1.4, no changes needed.
   * Update to debhelper compat level 11.
Checksums-Sha1:
 181d827b69d7f2737750114f74ade2aa5a5c53a1 2244 sphinx-paramlinks_0.3.4-2.dsc
 da6ef4d897e3f210cf1ae10e2e2167f2373003dc 2656 
sphinx-paramlinks_0.3.4-2.debian.tar.xz
 bde09884958794ba904e45d8e3933ec631d8cadf 6022 
sphinx-paramlinks_0.3.4-2_source.buildinfo
Checksums-Sha256:
 e56e4f649bc0dc7b55add2493e1b4dc8d69301bd055cb583c28ab5738da5b420 2244 
sphinx-paramlinks_0.3.4-2.dsc
 0c5cff0714b55d431993b3afebd60f25566d5bf3e6345a28fd5983821edd8928 2656 
sphinx-paramlinks_0.3.4-2.debian.tar.xz
 4142bca4b29f3507f1dfb02457996c1491c4825a14ad08ef411a823827efd21a 6022 
sphinx-paramlinks_0.3.4-2_source.buildinfo
Files:
 eb6e89a6a95ab1d93e2e88485c311edd 2244 python optional 
sphinx-paramlinks_0.3.4-2.dsc
 592a04b49b934f49d7aef38a5882b0e2 2656 python optional 
sphinx-paramlinks_0.3.4-2.debian.tar.xz
 ef80fd4d0ab040e6f45a9a33647f271e 6022 python optional 
sphinx-paramlinks_0.3.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlrc2Y4ACgkQ1v5xA2P4
XdOQKA//Qd3qexArQ7nDFflYRz4u4lUFwnsdjSFqqV0dQgECMfXzzqIVHZ6BqAJj
Gwh22ZFGn44Q4+iG/cxY6DPe8nF/oDFZKKC4Rs5IcEGG/5eadv+X3iYtUMynrhm0

Bug#896602: libglvnd: FTBFS on many architectures

[Andreas Beckmann]

Source: libglvnd
Version: 1.0.0+git20180308-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

the snapshot uploaded to sid FTBFS on many architectures where it
previously built.

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


Andreas

Processed: tagging 848073

[Debian Bug Tracking System]

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

> tags 848073 + pending
Bug #848073 [python3-django-macaddress] python3-django-macaddress: 
Compatibility of django-macaddress with django 1.10 in stretch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 896387, tagging 896221

[Debian Bug Tracking System]

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

> tags 896387 + pending
Bug #896387 [python-django-macaddress] python-django-macaddress: macaddress 
fails to import
Ignoring request to alter tags of bug #896387 to the same tags previously set
> tags 896221 + pending
Bug #896221 [python3-django-macaddress] python3-django-macaddress: macaddress 
fails to import
Ignoring request to alter tags of bug #896221 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#895880: marked as done (sphinxcontrib-websupport: autopkgtest fails since sphinx 1.7.2-1 (RemovedInSphinx17Warning))

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 18:50:50 +
with message-id 
and subject line Bug#895880: fixed in sphinxcontrib-websupport 1.0.1-3
has caused the Debian Bug report #895880,
regarding sphinxcontrib-websupport: autopkgtest fails since sphinx 1.7.2-1 
(RemovedInSphinx17Warning)
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.)


-- 
895880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-websupport
Version: 1.0.1-2
Severity: normal
User: debian...@lists.debian.org
Usertags: progression

Since the upload of sphinx version 1.7.2-1, your autopkgtest¹ fails with
the error copied below. Looking at the name of the module it complains
about, I think that the module RemovedInSphinx17Warning was removed in
sphinx version 1.7.x.

The error appears in the test code, but maybe it is also used in the
regular code (I didn't check). In that case this bug is more severe than
*normal*.

In any case, could you please fix your autopkgtests?

Paul

¹ https://ci.debian.net/packages/s/sphinxcontrib-websupport

 ERRORS

 ERROR collecting tests/test_searchadapters.py
_
ImportError while importing test module
'/tmp/autopkgtest-lxc.xun9timu/downtmp/autopkgtest_tmp/tests/test_searchadapters.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/test_searchadapters.py:16: in 
from test_websupport import sqlalchemy_missing
tests/test_websupport.py:26: in 
from util import rootdir, tempdir
tests/util.py:30: in 
from sphinx.deprecation import RemovedInSphinx17Warning
E   ImportError: cannot import name 'RemovedInSphinx17Warning'
__ ERROR collecting tests/test_websupport.py
___
ImportError while importing test module
'/tmp/autopkgtest-lxc.xun9timu/downtmp/autopkgtest_tmp/tests/test_websupport.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/test_websupport.py:26: in 
from util import rootdir, tempdir
tests/util.py:30: in 
from sphinx.deprecation import RemovedInSphinx17Warning
E   ImportError: cannot import name 'RemovedInSphinx17Warning'
!!! Interrupted: 2 errors during collection

=== 2 error in 0.80 seconds




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sphinxcontrib-websupport
Source-Version: 1.0.1-3

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated 
sphinxcontrib-websupport 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: Sun, 22 Apr 2018 21:28:09 +0300
Source: sphinxcontrib-websupport
Binary: python-sphinxcontrib.websupport python3-sphinxcontrib.websupport
Architecture: source
Version: 1.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-sphinxcontrib.websupport - API to integrate Sphinx documentation into 
Web applications (Pyth
 python3-sphinxcontrib.websupport - API to integrate Sphinx documentation into 
Web applications (Pyth
Closes: 895880
Changes:
 sphinxcontrib-websupport (1.0.1-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
 .
   [ Dmitry Shachnev ]
   * Backport upstream patch to fix tests with Sphinx 1.7 (closes: #895880).
   * Bump Standards-Version to 4.1.4, no changes needed.
Checksums-Sha1:
 938f23e1c211022ca790f425e9bfe44d1a5bcab9 2803 
sphinxcontrib-websupport_1.0.1-3.dsc
 40d0059300790b4c21b17ce9952b814b3dfffaa4 10428 
sphinxcontrib-websupport_1.0.1-3.debian.tar.xz

Bug#896366: Bug #896366 in sphinx-paramlinks marked as pending

[mitya57]

Control: tag -1 pending

Hello,

Bug #896366 in sphinx-paramlinks reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/sphinx-paramlinks/commit/68964672bbdac140be4e76274b187c91b5273a57


Depend on sphinx.

Closes: #896288, #896366.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896366

Processed: Bug #896366 in sphinx-paramlinks marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896366 [python3-sphinx-paramlinks] python3-sphinx-paramlinks: 
sphinx_paramlinks fails to import
Added tag(s) pending.

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

Processed: Bug #896288 in sphinx-paramlinks marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896288 [python-sphinx-paramlinks] python-sphinx-paramlinks: 
sphinx_paramlinks fails to import
Added tag(s) pending.

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

Bug#896288: Bug #896288 in sphinx-paramlinks marked as pending

[mitya57]

Control: tag -1 pending

Hello,

Bug #896288 in sphinx-paramlinks reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/sphinx-paramlinks/commit/68964672bbdac140be4e76274b187c91b5273a57


Depend on sphinx.

Closes: #896288, #896366.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896288

Bug#896221: Bug #896221 in django-macaddress marked as pending

[jmw]

Control: tag -1 pending

Hello,

Bug #896221 in django-macaddress reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/django-macaddress/commit/2f51e6158ff44974ec40c4f139597f0da727ab7c


Add missing dep on python{,3}-pkg-config

Closes: #896221, #896387



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896221

Bug#895880: Bug #895880 in sphinxcontrib-websupport marked as pending

[mitya57]

Control: tag -1 pending

Hello,

Bug #895880 in sphinxcontrib-websupport reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/sphinxcontrib-websupport/commit/6026ee0551bea121a520f7a2a951194d0c41b4be


Backport upstream patch to fix tests with Sphinx 1.7.

Closes: #895880.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895880

Bug#896387: Bug #896387 in django-macaddress marked as pending

[jmw]

Control: tag -1 pending

Hello,

Bug #896387 in django-macaddress reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/django-macaddress/commit/2f51e6158ff44974ec40c4f139597f0da727ab7c


Add missing dep on python{,3}-pkg-config

Closes: #896221, #896387



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896387

Processed: Bug #896221 in django-macaddress marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896221 [python3-django-macaddress] python3-django-macaddress: macaddress 
fails to import
Added tag(s) pending.

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

Processed: Bug #895880 in sphinxcontrib-websupport marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895880 [src:sphinxcontrib-websupport] sphinxcontrib-websupport: 
autopkgtest fails since sphinx 1.7.2-1 (RemovedInSphinx17Warning)
Added tag(s) pending.

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

Processed: Bug #896387 in django-macaddress marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896387 [python-django-macaddress] python-django-macaddress: macaddress 
fails to import
Added tag(s) pending.

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

Bug#856077: faumachine: Please drop the (build-)dependency against esound

[Stefan Potyra]

Hi Laurent,

sorry for not responding earlier.

We dropped the dependency of FAUmachine to esound upstream (but not yet
released). Don't block on FAUmachine with esound removal.

Cheers,
  Stefan.


signature.asc
Description: PGP signature

Bug#896443: marked as done (connectagram FTBFS with Qt 5.10)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 18:19:35 +
with message-id 
and subject line Bug#896443: fixed in connectagram 1.2.6-1
has caused the Debian Bug report #896443,
regarding connectagram FTBFS with Qt 5.10
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.)


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

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

...
Project ERROR: Connectagram requires Qt 5.2 or greater
dh_auto_configure: qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_RELEASE=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_DEBUG=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro 
-Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr PREFIX=/usr BINDIR=games returned exit 
code 3
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 2


connectagram.pro
lessThan(QT_VERSION, 5.2) {
error("Connectagram requires Qt 5.2 or greater")
}


This is interpreted as float, so 5.10 < 5.2
--- End Message ---
--- Begin Message ---
Source: connectagram
Source-Version: 1.2.6-1

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

Debian distribution maintenance software
pp.
Innocent De Marchi  (supplier of updated connectagram 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Apr 2018 17:13:23 +0100
Source: connectagram
Binary: connectagram connectagram-data
Architecture: source
Version: 1.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Innocent De Marchi 
Description:
 connectagram - word unscrambling game
 connectagram-data - word unscrambling game - data files
Closes: 896443
Changes:
 connectagram (1.2.6-1) unstable; urgency=medium
 .
   * New upstream version 1.2.6 (Closes: #896443).
   * Updated dates and write secure URI in debian/copyright file.
   * Bumped to debhelper and compat level 11.
   * Bumped to Standards-Version 4.1.4.
   * Migrated to the salsa repository.
   * Install upstream manpage (removed Debian manpage).
   * Removed unnecessary dh argument --parallel on d/rules.
   * Added hardening flags on debian/rules.
   * Drop deprecated debian/menu file.
   * Added Multi-Arch field on debian/control.
   * Added debian/upstream/metadata file.
Checksums-Sha1:
 50c2a7276562d584dd5114644322407183ff 2207 connectagram_1.2.6-1.dsc
 76c3c4a450d9b549ea2dfaf58b37dbc863a2b7e3 1495322 connectagram_1.2.6.orig.tar.gz
 273e014bd7a6497e31abe32280877e8b1da4acf9 3684 
connectagram_1.2.6-1.debian.tar.xz
 16788d3761af9214c6fdba6a88b7b6506767027f 11331 
connectagram_1.2.6-1_amd64.buildinfo
Checksums-Sha256:
 d7f17d5c81d593d86187270eefdcf9f7f5460f249b9b20b8f31c5705cc35a516 2207 
connectagram_1.2.6-1.dsc
 ed6933f7a8a7d9b99443b6dbab514c19f0de672cee57527cce319caa770b01d9 1495322 
connectagram_1.2.6.orig.tar.gz
 c344ee2a874cee63c1d6c4bde3561600e94b7d2ef841e115f4b7e8793d1c8db8 3684 
connectagram_1.2.6-1.debian.tar.xz
 1e54d6b8a73e005c8de1a22edfdc87b5e52838a6d1a802f462534fa89d2ff47d 11331 
connectagram_1.2.6-1_amd64.buildinfo
Files:
 8c7900b066d4ca9da16ccbfa84968e64 2207 games optional connectagram_1.2.6-1.dsc
 4abebbd5e0c26e165cc420997a04a6a8 1495322 games optional 
connectagram_1.2.6.orig.tar.gz
 25faca5eb74b65c434a833fe07744342 3684 games optional 
connectagram_1.2.6-1.debian.tar.xz
 9f5e118db40f066a4f638207bcfe0513 11331 games optional 

Bug#896444: marked as done (cutemaze FTBFS with Qt 5.10)

[Debian Bug Tracking System]

Your message dated Sun, 22 Apr 2018 18:20:15 +
with message-id 
and subject line Bug#896444: fixed in cutemaze 1.2.2-1
has caused the Debian Bug report #896444,
regarding cutemaze FTBFS with Qt 5.10
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.)


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

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

...
Project ERROR: CuteMaze requires Qt 5.2 or greater
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 3


cutemaze.pro:
lessThan(QT_VERSION, 5.2) {
error("CuteMaze requires Qt 5.2 or greater")
}


This is interpreted as float, so 5.10 < 5.2
--- End Message ---
--- Begin Message ---
Source: cutemaze
Source-Version: 1.2.2-1

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

Debian distribution maintenance software
pp.
Innocent De Marchi  (supplier of updated cutemaze 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Apr 2018 18:11:23 +0100
Source: cutemaze
Binary: cutemaze
Architecture: source
Version: 1.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Innocent De Marchi 
Description:
 cutemaze   - single player maze game
Closes: 896444
Changes:
 cutemaze (1.2.2-1) unstable; urgency=medium
 .
   * New upstream version 1.2.2 (Closes: #896444).
   * Bump standards to 4.1.4.
   * Updated dates and write secure URI in d/copyright.
   * Bumped to debhelper and compat level 11.
   * Bumped to Standards-Version 4.1.4.
   * Removed unnecessary dh argument --parallel on d/rules.
   * Added override_dh_installchangelogs to install upstream NEWS file.
   * Drop deprecated debian/menu file.
   * Install upstream manpage (removed debian manpage).
   * Migrated to the salsa repository.
   * Added debian/upstream/metadata file.
Checksums-Sha1:
 2cfb90b851ff51889780a806f6e9f71be7eedde2 2114 cutemaze_1.2.2-1.dsc
 9d9a24585393729d2b90f63a1e22f5b3004faf05 807649 cutemaze_1.2.2.orig.tar.gz
 4d9093c34bf5d7d90d75f971220dbb3018bc316d 4344 cutemaze_1.2.2-1.debian.tar.xz
 ddab3f5c61cbbbf3325c99d6c86bb6ffe943aa29 10811 cutemaze_1.2.2-1_amd64.buildinfo
Checksums-Sha256:
 23e2a98037fe5a765787c5a489b3b5acd22e3e707968e410691fab5e407c0ef8 2114 
cutemaze_1.2.2-1.dsc
 b1429b91015b01517b24a0670ffe807390b408b451c70b585e8ff4c26354eca4 807649 
cutemaze_1.2.2.orig.tar.gz
 d60e4007d957edb9b264bd1614eb5509d05ae5026aa22c318ab5defd6096dc45 4344 
cutemaze_1.2.2-1.debian.tar.xz
 60837345ba8d491c3b9b4e0762bad7e4acfaf63490f34c5e63099d4209fb0840 10811 
cutemaze_1.2.2-1_amd64.buildinfo
Files:
 f8b0065a23529fe7ad600c671f699573 2114 games optional cutemaze_1.2.2-1.dsc
 3dfc66ea1cc1a287c7f8bee1e460ec3d 807649 games optional 
cutemaze_1.2.2.orig.tar.gz
 75140dc36c7b32a07fa20517c707c67b 4344 games optional 
cutemaze_1.2.2-1.debian.tar.xz
 4eeca73a258a7d8f6288a10141a181ef 10811 games optional 
cutemaze_1.2.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlrcz+5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk5/4P/R5LhJCmfP20x1ng8AK6Wasnnn5x1Bft+blb
kIrMnXvs7MsZ+ugnFUwOHY+Dg+q+GPeLsr/nnVA5l3lGfx/rot2oKmUeDHayLFjm
sQkzD1Iyj1k4tjRwFwRNWF+Edt7s9HYrUSJDj/iGZYoi7ekttIcMH4gEwHq5UcB4
z+t9jRLHaVucJk6k3vZm6B5fKslQSevVWq6gbNb8cI/fetnKMnMHyWvEZEZ+r0Ze
YLj0z2YJbrfskbZYkiFKwoDD8oXJtq9P2ViBZvIJB+HJLnx+rzT3Os55YjT9+8Pd
MHzPauN3sHz+/t7+vyBctrLnk8TMPcRZuTxDq1kWmZRSrJ2vrCvhYBXMM5jEO0kl
3lFauQWLq5m1EWh2TEUj/dVR0wzekIlDUsMQ5jhf6pXO8Gbj+VcHs4gZTMcXhjjQ
S8Ek3zcfqAjLHCRuj2onvRFvDVePsvolZyMzDsOGTwlRNocfAqKlYQ2NXuvRLCa1
XzgrIHq5VbJerrU6TVijVU9hrZOfhm1n2x2kgIekCM4m1p73zKlayFkoqLb2psTo

Processed: tagging 885546

[Debian Bug Tracking System]

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

> tags 885546 + pending
Bug #885546 [wicd-gtk] wicd-gtk: Please don't recommend gksu
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#896597: python3-future: depend on python3-lib2to3

[Adrian Bunk]

Control: tags -1 moreinfo

On Sun, Apr 22, 2018 at 07:46:48PM +0200, Matthias Klose wrote:
> Package: src:python-future
> Version: 0.15.2-4
> Severity: serious
> Tags: sid buster patch
> 
> lib2to3 now lives in it's own package. python3-future needs a dependency pn
> python3-lib2to3.
>...

Please provide the actual error message,
I cannot see why this would be required.

cu
Adrian

-- 

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

Processed: Re: Bug#896597: python3-future: depend on python3-lib2to3

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #896597 [src:python-future] python3-future: depend on python3-lib2to3
Added tag(s) moreinfo.

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

Bug#896189: closed by Alastair McKinstry <mckins...@debian.org> (Bug#896189: fixed in openmpi 3.0.1-7)

[Adrian Bunk]

Control: reopen -1

On Sun, Apr 22, 2018 at 04:21:10PM +, Debian Bug Tracking System wrote:
>...
>  openmpi (3.0.1-7) unstable; urgency=medium
>  .
>* Delete old non-mpi alternatives if needed. Closes: #896189
>...

Doesn't seem to work:
https://buildd.debian.org/status/logs.php?pkg=netpipe=amd64

Note that these are fresh installations in newish chroots.

cu
Adrian

-- 

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

Processed: Re: Bug#896189 closed by Alastair McKinstry <mckins...@debian.org> (Bug#896189: fixed in openmpi 3.0.1-7)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #896189 {Done: Alastair McKinstry } [openmpi-bin] 
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link 
same as main link /usr/bin/mpicc
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openmpi/3.0.1-7.

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

Processed: Re: geogebra: Geogebra crashes with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #882550 [geogebra] geogebra: Geogebra crashes with openjdk-9
Severity set to 'serious' from 'important'

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

Bug#881205: Assistance for maintaining src:backintime

[Jonathan Wiltshire]

Hi,

On Sat, Jan 06, 2018 at 10:17:54AM +, Ghislain Vaillant wrote:
> I was wondering whether you need any help with the maintenance of the
> package, which I'd be happy to offer. It might also be useful to move
> the package to team-maintenance long term, under collab-maint or one of
> the Python packaging teams.

Yes please! I do not currently have time to maintain backintime properly,
so co-maintenance would be helpful.

I uploaded the current repository state to salsa [1].

Would you prepare an update to the latest upstream targetting sid?

1: https://salsa.debian.org/jmw/pkg-backintime

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#896598: libglademm2.4: Intent to Adopt

[Adrian Bunk]

Source: libglademm2.4
Version: 2.6.7-5
Severity: serious
Tags: buster sid

I hereby declare my intent to adopt pygtk.

Keeping it as a separate package is better than the current
copying of the sources in src:aeskulap.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#896597: python3-future: depend on python3-lib2to3

[Matthias Klose]

Package: src:python-future
Version: 0.15.2-4
Severity: serious
Tags: sid buster patch

lib2to3 now lives in it's own package. python3-future needs a dependency pn
python3-lib2to3.

patch at
https://patches.ubuntu.com/p/python-future/python-future_0.15.2-4ubuntu2.patch

Bug#896596: ruby-gnome2: Debci failure with poppler 0.63.0

[Adrian Bunk]

Source: ruby-gnome2
Version: 3.2.4-1
Severity: serious
Control: affects -1 src:ruby-cairo

https://ci.debian.net/packages/r/ruby-gnome2/unstable/amd64/

...
Started
..Poppler-INFO **: Syntax error at position -1: Document 
stream is empty
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/gobject-introspection/lib/gobject-introspection/loader.rb:317:in
 `block (2 levels) in load_constructor_infos'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/lib/poppler/document.rb:58:in
 `initialize'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-document.rb:10:in
 `new'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-document.rb:10:in
 `test_data'
from /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:793:in `run_test'
from /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:499:in `block (2 
levels) in run'
from /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:270:in `block in 
create_fixtures_runner'
from /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:270:in `block in 
create_fixtures_runner'
from /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:251:in `run_fixture'
from /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:286:in `run_setup'
from /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:497:in `block in 
run'
from /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:496:in `catch'
from /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:496:in `run'
from /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
from /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
from /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
from /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
from /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
from /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:67:in 
`run_suite'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:45:in 
`block (2 levels) in run'
from 
/usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:102:in 
`with_listener'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:41:in 
`block in run'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:39:in 
`catch'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:39:in 
`run'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunner.rb:40:in 
`start_mediator'
from /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunner.rb:25:in `start'
from 
/usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnerutilities.rb:24:in `run'
from /usr/lib/ruby/vendor_ruby/test/unit/autorunner.rb:435:in `block in 
run'
from /usr/lib/ruby/vendor_ruby/test/unit/autorunner.rb:491:in 
`change_work_directory'
from /usr/lib/ruby/vendor_ruby/test/unit/autorunner.rb:434:in `run'
from /usr/lib/ruby/vendor_ruby/test/unit/autorunner.rb:62:in `run'
from test/run-test.rb:56:in `'
E
===
Error: test_data(TestDocument::#initialize): Poppler::Error::Invalid: Failed to 
load document
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/gobject-introspection/lib/gobject-introspection/loader.rb:317:in
 `invoke'
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/gobject-introspection/lib/gobject-introspection/loader.rb:317:in
 `block (2 levels) in load_constructor_infos'
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/lib/poppler/document.rb:58:in
 `initialize'
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-document.rb:10:in
 `new'
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-document.rb:10:in
 `test_data'
  7:   context.show_text("Hello")
  8:   surface.finish
  9: 
  => 10:   document = Poppler::Document.new(:data => pdf.string)
 11:   assert_equal("Hello", document[0].text)
 12: end
 13:   end
===
.Poppler-INFO **: Syntax error at position -1: Document stream is empty
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/gobject-introspection/lib/gobject-introspection/loader.rb:317:in
 `block (2 levels) in load_constructor_infos'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/lib/poppler/document.rb:58:in
 `initialize'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-page.rb:98:in
 `new'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-page.rb:98:in
 `create_document'
from 
/tmp/autopkgtest-lxc.tw7vr2na/downtmp/build.m7f/src/poppler/test/test-page.rb:109:in
 

Processed: ruby-gnome2: Debci failure with poppler 0.63.0

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ruby-cairo
Bug #896596 [src:ruby-gnome2] ruby-gnome2: Debci failure with poppler 0.63.0
Added indication that 896596 affects src:ruby-cairo

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