Bug#960899: [Python-modules-team] Bug#960899: paramiko: diff for NMU version 2.7.1-1.1

[Eriberto Mota]

Em sáb., 13 de jun. de 2020 às 01:21, Sandro Tosi  escreveu:
>
> On Wed, Jun 10, 2020 at 11:45 AM César Túlio  wrote:
> >
> > Control: tags 960899 + patch
> > Control: tags 960899 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for paramiko (versioned as 2.7.1-1.1) and
> > uploaded it to DELAYED/5. Please feel free to tell me if I
> > should delay it longer or cancel the NMU.
>
> hold off with this please; i'd much rather for you to submit an MR at
> https://salsa.debian.org/python-team/modules/paramiko

Hi Sandro,

It is part of a local sprint. I am cancelling the upload now.

Regards,

Eriberto

Bug#962739: qtcurve FTBFS: misses FrameworkIntegration

[Helmut Grohne]

Source: qtcurve
Version: 1.9-5
Severity: serious
Tags: ftbfs

qtcurve fails to build from source in unstable. cmake says:

| CMake Error at 
/usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
|   Could NOT find KF5 (missing: FrameworkIntegration) (found version "5.70.0")

It would seem that the relevant cmake file resides in libkf5style-dev,
but there is no build dependency ensuring presence of that package.

Helmut

Bug#962630: linking with libunwind does not reliably help

[Noah Meyerhans]

(This message was previously sent to the wrong bug by mistake...)

Linking against libunwind helps on (at least) armel, but it seems to
break on (at least) arm64.

The test suite reports the following when linked against libunwind on
arm64:

test-backtrace.c:14: Assert failed: strstr(str_c(bt), "test_backtrace") != NULL
backtrace_append . : FAILED
test-backtrace.c:38: Assert failed: strstr(bt, "test_backtrace") != NULL
backtrace_get  : FAILED

These are the failing lines:
https://salsa.debian.org/debian/dovecot/-/blob/master/src/lib/test-backtrace.c#L14
https://salsa.debian.org/debian/dovecot/-/blob/master/src/lib/test-backtrace.c#L38

In both cases, the issue is that the given symbol name (test_backtrace)
is not found in the string representing the stack trace.  On armel,
where the test passes, the stack trace appears complete and reasonably
useful:

#0 test_backtrace[0x0059efb8] -> #1 test_run_named_funcs[0x005d04b8] -> #2 
test_run_named_with_fatals[0x005d12cc] -> #3 __libc_start_main[0xf78e4c44] -> 
#4 _start[0x0059d3bc]

On arm64, it is:

./test-lib(+0x3f097) [0xe0c5b097] -> ./test-lib(+0x3f1e7) [0xe0c5b1e7] 
-> ./test-lib(+0x11f63) [0xe0c2df63] -> ./test-lib(+0x3bacb) 
[0xe0c57acb] -> ./test-lib(+0x3c77f) [0xe0c5877f] -> 
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0xe3) [0x8ac962eb] -> 
./test-lib(+0x106ab) [0xe0c2c6ab]

Note the lack of symbols.  I have not investigated whether the problem
is with dovecot's usage of libunwind or with libunwind itself.

Also notable is the fact that the second conditional preprocessor block
looks for the string "main" in the stack trace instead of
test_backtrace, so it would pass here, even though the trace itself is
of dubious value:
https://salsa.debian.org/debian/dovecot/-/blob/master/src/lib/test-backtrace.c#L21

Bug#962737: handlebars: Does not declare its dependencies

[nandhp]

Package: handlebars
Version: 3:4.1.0-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

The package handlebars does not declare any dependencies, except on
nodejs itself. However, the handlebars command fails to run unless I
also install at least node-optimist, node-async, and node-source-map:

$ handlebars
internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module 'optimist'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/usr/lib/nodejs/handlebars/bin/handlebars:3:16)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
$ handlebars
internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module 'async'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object.
(/usr/lib/nodejs/handlebars/dist/cjs/precompiler.js:3:38)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
$ handlebars
internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module 'source-map'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object.
(/usr/lib/nodejs/handlebars/dist/cjs/precompiler.js:17:42)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)

The version in unstable also does not declare any dependencies, so I
expect this problem is still present there.

Thanks.
-nandhp

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

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

Versions of packages handlebars depends on:
ii  nodejs  10.21.0~dfsg-1~deb10u1

handlebars recommends no packages.

handlebars suggests no packages.

-- no debconf information

Bug#960899: [Python-modules-team] Bug#960899: paramiko: diff for NMU version 2.7.1-1.1

[Sandro Tosi]

On Wed, Jun 10, 2020 at 11:45 AM César Túlio  wrote:
>
> Control: tags 960899 + patch
> Control: tags 960899 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for paramiko (versioned as 2.7.1-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer or cancel the NMU.

hold off with this please; i'd much rather for you to submit an MR at
https://salsa.debian.org/python-team/modules/paramiko

Additionally, did you talk to upstream about including this files in
their next release?

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#925746: marked as done (libidn: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jun 2020 02:52:11 +
with message-id 
and subject line Bug#925746: fixed in libidn 1.33-2.3
has caused the Debian Bug report #925746,
regarding libidn: ftbfs with GCC-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.)


-- 
925746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libidn
Version: 1.33-2.2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libidn_1.33-2.2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
PASS: test-thread_self
FAIL: test-thread_create
PASS: test-unistd
PASS: test-u8-check
PASS: test-u8-mbtoucr
PASS: test-u8-uctomb
PASS: test-unsetenv
PASS: test-verify
PASS: test-init.sh
PASS: test-verify.sh
=
   GNU Libidn 1.33: lib/gltests/test-suite.log
=

# TOTAL: 34
# PASS:  31
# SKIP:  1
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-lock
===

Starting test_lock ...FAIL test-lock (exit status: 134)

SKIP: test-setlocale1.sh


Skipping test: no locale for testing is installed
SKIP test-setlocale1.sh (exit status: 77)

FAIL: test-thread_create


glthread_create failed
FAIL test-thread_create (exit status: 1)


Testsuite summary for GNU Libidn 1.33

# TOTAL: 34
# PASS:  31
# SKIP:  1
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See lib/gltests/test-suite.log
Please report to bug-lib...@gnu.org

make[6]: *** [Makefile:2169: test-suite.log] Error 1
make[6]: Leaving directory '/<>/build/lib/gltests'
make[5]: *** [Makefile:2277: check-TESTS] Error 2
make[5]: Leaving directory '/<>/build/lib/gltests'
make[4]: *** [Makefile:2607: check-am] Error 2
make[4]: Leaving directory '/<>/build/lib/gltests'
make[3]: *** [Makefile:2061: check-recursive] Error 1
make[3]: Leaving directory '/<>/build/lib/gltests'
make[2]: *** [Makefile:2609: check] Error 2
make[2]: Leaving directory '/<>/build/lib/gltests'
make[1]: *** [Makefile:1346: check-recursive] Error 1
make[1]: Leaving directory '/<>/build'
dh_auto_test: cd build && make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:20: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: libidn
Source-Version: 1.33-2.3
Done: Marcelo Soares Mota 

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

Debian distribution maintenance software
pp.
Marcelo Soares Mota  (supplier of updated libidn 

Bug#962232: marked as done (vanguards indirectly build-depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jun 2020 02:23:50 +
with message-id 
and subject line Bug#962232: fixed in vanguards 0.3.1-2.1
has caused the Debian Bug report #962232,
regarding vanguards indirectly build-depends on cruft package.
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.)


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

Package: vanguards
Version: 0.3.1-2
Severity: serious

vanguards build-depends on pypy-pytest which depends on pypy-funcsigs which is 
no longer built by the python-funcsigs source package. The pytest maintainer 
has also said they would like to get rid of pypy support from pytest. Afaict 
vanguards is the only application that build-depends on pypy-pytest (there are 
also some module packages but they all look like they could drop pypy support 
at the same time pytest does).

The ideal fix would be to move to pypy3, but I understand that is currently 
blocked on tooling (see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932820 ). Over in bug 937769 
Chris Lamb proposed a patch to run the testsuite with python 3. Obviously 
running the testsuite with a different python version from that used to 
actually run the program is suboptimal but I think it's the lesser evil here.

I manually applied the patch, cleaning up some formatting and making the 
dependency versioning for the python3-stem build-dependency match that for the 
pypy-stem build-dependency. While testing I also noticed some clean target 
issues so I fixed them.

A debdiff is attatched, if I get no objections (and the maintainer doesn't 
upload this first) I will likely NMU this in a week or so.

diff -Nru vanguards-0.3.1/debian/changelog vanguards-0.3.1/debian/changelog
--- vanguards-0.3.1/debian/changelog2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/changelog2020-06-04 19:21:14.0 +
@@ -1,3 +1,12 @@
+vanguards (0.3.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Clean up pytest cache and egg info in clean target.
+  * Run testsuite with python 3 to get rid of build-depends on pypy-pytest
+(thanks to Chris Lamb for the initial patch)
+
+ -- Peter Michael Green   Thu, 04 Jun 2020 19:21:14 +
+
 vanguards (0.3.1-2) unstable; urgency=medium
 
   [ Nicolas Braud-Santoni ]
diff -Nru vanguards-0.3.1/debian/control vanguards-0.3.1/debian/control
--- vanguards-0.3.1/debian/control  2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/control  2020-06-04 19:21:14.0 +
@@ -8,8 +8,9 @@
dh-python,
pypy,
pypy-setuptools,
+   python3-pytest ,
+   python3-stem (>= 1.6.0-3.1) ,
pypy-stem (>= 1.6.0-3.1),
-   pypy-pytest,
pypy-ipaddress
 Standards-Version: 4.1.5
 Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/vanguards
diff -Nru vanguards-0.3.1/debian/rules vanguards-0.3.1/debian/rules
--- vanguards-0.3.1/debian/rules2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/rules2020-06-04 19:21:14.0 +
@@ -5,3 +5,10 @@
 
 override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
+
+override_dh_auto_test:
+   dh_auto_test -- --system=custom --test-args='cd {build_dir}; python3 -m 
pytest $(CURDIR)/tests'
+
+override_dh_auto_clean:
+   dh_auto_clean
+   rm -rf .pytest_cache src/vanguards.egg-info
--- End Message ---
--- Begin Message ---
Source: vanguards
Source-Version: 0.3.1-2.1
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated vanguards 
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: Sat, 13 Jun 2020 01:49:35 +
Source: vanguards
Architecture: source
Version: 0.3.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Peter 

Bug#962232: vanguards indirectly build-depends on cruft package.

[peter green]

I have now gone ahead with the NMU, the final debdiff is attatched (same as 
previous debdiff apart from changelog tweaks)

diff -Nru vanguards-0.3.1/debian/changelog vanguards-0.3.1/debian/changelog
--- vanguards-0.3.1/debian/changelog2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/changelog2020-06-13 01:49:35.0 +
@@ -1,3 +1,13 @@
+vanguards (0.3.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Clean up pytest cache and egg info in clean target.
+  * Run testsuite with python 3 and adjust build-depends accordingly
+to get rid of build-depends on pypy-pytest (Closes: 962232)
+(thanks to Chris Lamb for the initial patch)
+
+ -- Peter Michael Green   Sat, 13 Jun 2020 01:49:35 +
+
 vanguards (0.3.1-2) unstable; urgency=medium
 
   [ Nicolas Braud-Santoni ]
diff -Nru vanguards-0.3.1/debian/control vanguards-0.3.1/debian/control
--- vanguards-0.3.1/debian/control  2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/control  2020-06-04 19:31:34.0 +
@@ -8,8 +8,9 @@
dh-python,
pypy,
pypy-setuptools,
+   python3-pytest ,
+   python3-stem (>= 1.6.0-3.1) ,
pypy-stem (>= 1.6.0-3.1),
-   pypy-pytest,
pypy-ipaddress
 Standards-Version: 4.1.5
 Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/vanguards
diff -Nru vanguards-0.3.1/debian/rules vanguards-0.3.1/debian/rules
--- vanguards-0.3.1/debian/rules2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/rules2020-06-04 19:30:41.0 +
@@ -5,3 +5,10 @@
 
 override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
+
+override_dh_auto_test:
+   dh_auto_test -- --system=custom --test-args='cd {build_dir}; python3 -m 
pytest $(CURDIR)/tests'
+
+override_dh_auto_clean:
+   dh_auto_clean
+   rm -rf .pytest_cache src/vanguards.egg-info

Bug#962630: Acknowledgement (dovecot: FTBFS: test failures on 32-bit ARM)

[Noah Meyerhans]

Based on https://lists.debian.org/debian-glibc/2011/09/msg4.html, it
appears that adding -funwind-tables to CFLAGS solves the problem on
32-bit arm systems.  AFAICT, this is not documented in the gcc manual or
the docs for backtrace(3).

Adding -rdynamic to LDFLAGS makes the stack traces actually useful by
resolving addresses to symbol names.

I've tested this on armel and amd64 so far.

Work so far is on the backtrace-fixes branch in my salsa dovecot fork:
https://salsa.debian.org/noahm/dovecot/-/tree/backtrace-fixes

Unfortunately mips64 and mips64el seem to have other issues that make me
wonder if either (a) some other compilation options need to be enabled,
or (b) backtrace(3) doesn't work there at all.  It doesn't help that our
porter boxes are unbearably slow for exploring the situation...

Bug#962624: marked as done (libsrt1-openssl: missing Breaks+Replaces)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jun 2020 00:03:53 +
with message-id 
and subject line Bug#962624: fixed in srt 1.4.1-4
has caused the Debian Bug report #962624,
regarding libsrt1-openssl: missing Breaks+Replaces
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.)


-- 
962624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsrt1-openssl
Version: 1.4.1-2
Severity: serious

When installing libsrt1-openssl if libsrt1 is already installed:

Preparing to unpack .../libsrt1-openssl_1.4.1-2_amd64.deb ...
Unpacking libsrt1-openssl:amd64 (1.4.1-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libsrt1-openssl_1.4.1-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libsrt.so.1.4.1', which is also 
in package libsrt1:amd64 1.4.1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package libsrt-openssl-dev:amd64.
Preparing to unpack .../libsrt-openssl-dev_1.4.1-2_amd64.deb ...

Same issue for libsrt-openssl-dev if libsrt-dev is already installed:

Unpacking libsrt-openssl-dev:amd64 (1.4.1-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libsrt-openssl-dev_1.4.1-2_amd64.deb (--unpack):
 trying to overwrite '/usr/include/srt/logging_api.h', which is also in package 
libsrt-dev:amd64 1.4.1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libsrt1-openssl_1.4.1-2_amd64.deb
 /var/cache/apt/archives/libsrt-openssl-dev_1.4.1-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: srt
Source-Version: 1.4.1-4
Done: Federico Ceratto 

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated srt 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, 13 Jun 2020 00:17:35 +0100
Source: srt
Architecture: source
Version: 1.4.1-4
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 962624
Changes:
 srt (1.4.1-4) unstable; urgency=medium
 .
   * Add Break + Replaces (Closes: #962624)
 Thanks to Gianfranco Costamagna 
Checksums-Sha1:
 a9529731803e1ec58999ecc9ad2b5746dfad4dcb 2195 srt_1.4.1-4.dsc
 e393834a91d7b87c06d966cd2e470f2fdc47bf8f 8892 srt_1.4.1-4.debian.tar.xz
 564ed9bc8914cbaa542eba8926e96588be59aeca 10467 srt_1.4.1-4_amd64.buildinfo
Checksums-Sha256:
 bfb1e1d427391b3905f7c565c9653e7f2104d7229a5c21b7e84798de1c90b693 2195 
srt_1.4.1-4.dsc
 132c63a9c309a9cf7f3443b7f09ad9033db50bb6ea7248b71f279bce8d0c7aa4 8892 
srt_1.4.1-4.debian.tar.xz
 e14388e50cb74671530e15c59ef0db33630c3586b29c7b34d8b89877c08e0fb8 10467 
srt_1.4.1-4_amd64.buildinfo
Files:
 ed3b3b420070e23084810974c442e7dd 2195 libs optional srt_1.4.1-4.dsc
 a45da0ad1b3d4e4ee930f41cee908902 8892 libs optional srt_1.4.1-4.debian.tar.xz
 e1b47dc9c2577fa5130bacd2d1d1c13e 10467 libs optional 
srt_1.4.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAl7kEqkACgkQbzG8RPUX
faosfA/7B1f7bFIUjY9Ck1SXP8jJvmjY86t7IhdurQ+Tfo6A8XmYpcDQ+XErbFqK
Rw5nku7Ed6MFlrmSJ3yEXJcc2NTFMKjYfKL2UVNEnZCWfWu64J7eaSljmGfCtNXF
0nE2F0ph28nopKNOI43X1jG/K0KlnO/pA6NX8fCTPelQe8NZvFPXruaG0NiyFlYN
25hdZGZ74QsTy9PHxlA7FmLa7nDs1AAQLTbpdlNbnHHImKaWnMHPXrbQWjMvgUUo
HbAe6U4jlEGGiZb3pS0xdyEEXnWU8cAguE9Wt20dCa2YjvEMpyMj+LGZQglHHh51
DRjILlGJKaFU77cYSaS+UXcvPI+033CAjXBHNBubcx2aZRiQvHqxLqdJkaoR4Rdq
z4ziqkAEnzqc/CoKXj6+hZ1VjHOeNbfcBKC0KpJi6I8TfhuFyXMBJ+xDjGZLI125
kz2Kv7nkjhCYwvX5V5vii8oSpIU13pcFnXJbPf+bJuE57t4SohzR0ObjcwqogZc/
mtiaC3NDMYotpMvfUD948i82wmGz/H+yOF6zG/VPRARJ8jr35/hChsk/5t5ForBC
YipZjr2yg3YbJ910qzRwG8Xv2NBtv9j/bz9eB6bnHGunYlPuLfL3SLHx0S5TllXj
rNAyigVjs7fYogUmsypixaKArJ4g9Olm+UTlF6s+Cc/SnBlajg0=
=nPfw
-END PGP SIGNATURE End Message ---

Bug#962727: marked as done (libwww-mechanize-perl: build fails on IPv6-only buildds)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 23:18:40 +
with message-id 
and subject line Bug#962727: fixed in libwww-mechanize-perl 2.00-2
has caused the Debian Bug report #962727,
regarding libwww-mechanize-perl: build fails on IPv6-only 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.)


-- 
962727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libwww-mechanize-perl
Version: 2.00-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libwww-mechanize-perl=all=2.00-1=1591965277=0

...
# Test server http://127.0.0.1:39495 as PID 1878

#   Failed test 'First fetch works'
#   at t/cookies.t line 74.
#  got: '500'
# expected: '200'

#   Failed test 'First cookie matches'
#   at t/cookies.t line 78.
#  got: undef
# expected: 'Cookie #1'

#   Failed test 'Right title'
#   at t/cookies.t line 79.
#  got: undef
# expected: 'Home of Cookie #1'

#   Failed test 'Second fetch works'
#   at t/cookies.t line 84.
#  got: '500'
# expected: '200'

#   Failed test 'Second cookie matches'
#   at t/cookies.t line 88.
#  got: undef
# expected: 'Cookie #2'

#   Failed test 'Right title'
#   at t/cookies.t line 89.
#  got: undef
# expected: 'Home of Cookie #2'

#   Failed test 'Cookie did not change...'
#   at t/cookies.t line 97.
#  got: undef
# expected: 'Cookie #2'

#   Failed test '... but back to the first page title'
#   at t/cookies.t line 98.
#  got: undef
# expected: 'Home of Cookie #1'

#   Failed test 'Cookie did not change...'
#   at t/cookies.t line 106.
#  got: undef
# expected: 'Cookie #2'

#   Failed test 'On the proper 3rd page'
#   at t/cookies.t line 107.
#  got: undef
# expected: 'No cookies sent'

#   Failed test 'Got the third cookie'
#   at t/cookies.t line 115.
#  got: undef
# expected: 'Cookie #3'

#   Failed test 'Title is correct'
#   at t/cookies.t line 116.
#  got: undef
# expected: 'Home of Cookie #3'
# Looks like you failed 12 tests of 14.
t/cookies.t ..
1..14
TestServer: You can connect to your server at http://localhost:39495/
ok 1 - An object of class 'WWW::Mechanize' isa 'WWW::Mechanize'
not ok 2 - First fetch works
not ok 3 - First cookie matches
not ok 4 - Right title
not ok 5 - Second fetch works
not ok 6 - Second cookie matches
not ok 7 - Right title
not ok 8 - Cookie did not change...
not ok 9 - ... but back to the first page title
not ok 10 - Cookie did not change...
not ok 11 - On the proper 3rd page
not ok 12 - Got the third cookie
not ok 13 - Title is correct
ok 14 - Signaled the child process
Dubious, test returned 12 (wstat 3072, 0xc00)
Failed 12/14 subtests
...
Test Summary Report
---
t/cookies.t(Wstat: 3072 Tests: 14 Failed: 12)
  Failed tests:  2-13
  Non-zero exit status: 12
Files=61, Tests=798, 83 wallclock secs ( 0.29 usr  0.10 sys + 15.79 cusr  2.28 
csys = 18.46 CPU)
Result: FAIL
Failed 1/61 test programs. 12/798 subtests failed.
make[2]: *** [Makefile:948: test_dynamic] Error 255


See #962019 for discussion of a similar problem in a different package.
--- End Message ---
--- Begin Message ---
Source: libwww-mechanize-perl
Source-Version: 2.00-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libwww-mechanize-perl 
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, 13 Jun 2020 00:56:53 +0200
Source: libwww-mechanize-perl
Architecture: source
Version: 2.00-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 962727
Changes:
 libwww-mechanize-perl (2.00-2) unstable; urgency=medium
 .
   * Skip t/cookies.t during build and autopkgtest.
 The test fails on IPv6-only hosts, and this issue needs to 

Bug#941866: gtrayicon: Intent to remove from Debian

[Boyuan Yang]

Dear gtrayicon maintainers,

On Tue, 21 Jan 2020 13:03:49 -0500 Boyuan Yang 
wrote:
> X-Debbugs-CC: ripps...@gmail.com
> 
> On Sun, 6 Oct 2019 16:29:28 -0400 Jeremy Bicha 
wrote:
> > Source: gtrayicon
> > Version: 1.1-1
> > Severity: serious
> > 
> > As part of a major effort to reduce the amount of GTK2 software in
> > Debian, I or someone else will be requesting the removal of
gtrayicon
> > from Debian.
> > 
> > It has very low popcorn and hasn't been updated upstream or in
Debian
> > in more than a decade.
> > 
> > If you object, please comment here before the package is removed
from
> > Debian. Or better yet, convert it to gtk3 if you can. See
> > https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html
> 
> Dear developer,
> 
> since there has been no response since October, I will consider
starting the
> removal soon. The removal bug will be filed after one week (after
Jan. 28,
> 2020). If you have any objections, please let me know ASAP.

Since there has been no reply for 6 months, I will be submitting the
removal request now.

-- 
Regards,
Boyuan Yang


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

Processed: Bug#962727 marked as pending in libwww-mechanize-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #962727 [src:libwww-mechanize-perl] libwww-mechanize-perl: build fails on 
IPv6-only buildds
Added tag(s) pending.

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

Bug#962727: marked as pending in libwww-mechanize-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #962727 in libwww-mechanize-perl 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/perl-team/modules/packages/libwww-mechanize-perl/-/commit/7508c09762c873e578eb6e07ce7b628c4dad8ef5


Skip t/cookies.t during build and autopkgtest.

The test fails on IPv6-only hosts, and this issue needs to be fixed more
generally (cf. #962318).

Closes: #962727


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/962727

Bug#962265: marked as done (sword silently loses ICU support when built with ICU without icu-config)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 22:48:52 +
with message-id 
and subject line Bug#962265: fixed in sword 1.8.1+dfsg-8.1
has caused the Debian Bug report #962265,
regarding sword silently loses ICU support when built with ICU without 
icu-config
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.)


-- 
962265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sword
Version: 1.8.1+dfsg-8
Severity: serious
Tags: bullseye sid
Control: block 960193 by -1

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

...
checking for icu-config... no
*** The icu-config script installed by icu could not be found
*** compiling without ICU support
...
 Dependencies for standard use:
 REGEX:yes
 ZLIB: yes
 LIBICU:   no
 LIBCURL:  yes
 CLUCENE-CORE: yes 2.x
...


This is due to

icu (63.1-6) unstable; urgency=medium

  * Build without icu-config (closes: #898820).
...
 -- Laszlo Boszormenyi (GCS)   Wed, 23 Jan 2019 16:51:20 +
--- End Message ---
--- Begin Message ---
Source: sword
Source-Version: 1.8.1+dfsg-8.1
Done: Gleisson Jesuino Joaquim Cardoso 

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

Debian distribution maintenance software
pp.
Gleisson Jesuino Joaquim Cardoso  (supplier of updated 
sword 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, 08 Jun 2020 21:39:54 -0300
Source: sword
Architecture: source
Version: 1.8.1+dfsg-8.1
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packaging Team 

Changed-By: Gleisson Jesuino Joaquim Cardoso 
Closes: 962265
Changes:
 sword (1.8.1+dfsg-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixed ICU checking. Thanks to László Böszörményi .
 (Closes: #962265)
Checksums-Sha1:
 95adad4d3fb52ad4a169038dce585685f0aa852f 2429 sword_1.8.1+dfsg-8.1.dsc
 d1b87d3c2e041bb562638223ed4c0b7818bbb398 28160 
sword_1.8.1+dfsg-8.1.debian.tar.xz
 4abb636b7aeff8df8dc1d18f4ca6ba76961f5a5c 6119 
sword_1.8.1+dfsg-8.1_source.buildinfo
Checksums-Sha256:
 b413d6a5bc845b73bfcdc5fe909653d225019756b0029036a43efff42530362f 2429 
sword_1.8.1+dfsg-8.1.dsc
 7140123aa7acaf73344594be8aff5a422136fadac5680b449ab4deda2a1a5249 28160 
sword_1.8.1+dfsg-8.1.debian.tar.xz
 259bc8aa95f0a8ab9c24650e7d5d99b4b8b1d4dd27e10287b4b9180ea4bd1cf4 6119 
sword_1.8.1+dfsg-8.1_source.buildinfo
Files:
 12d25e646d118aea9f2561d27dc896c1 2429 libs optional sword_1.8.1+dfsg-8.1.dsc
 46b3bcd135a3eedc79679fd8edbb6b86 28160 libs optional 
sword_1.8.1+dfsg-8.1.debian.tar.xz
 5309e35431a596dcecaae6b2c61a049b 6119 libs optional 
sword_1.8.1+dfsg-8.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHTjuPGJPlVzh+jyFWjA1kfjNsIsFAl7hXYoACgkQWjA1kfjN
sIujJg/7Bvc4CSz+xfIfGJgLnp4kn3/prEpSlL0J642qlgWJ2oiHQ4ipR/iRFG1N
/cCu+k2hTJyL9Fg2k/ajnUWkuqj49BD/0IKAEAdDDQY/dhHk2ACqQVktXZdClzXV
vJufzyv/Fpdl9YvyklAh16M2d/C6RdlroLm7TmzMH79T3O/FivtrCQStaB6ZaaSM
shAkSNyI9ZB8eb4xMqgTGq4WWtbRBqOwoKky53pbdA8j/oSR7GUqX+GV07dfWuUt
BT9Yq/SCoEoHN8Y/lzm/upqkPsuTnRzJGwbWgh7o2yUCSdZ3iKvU9HYmrGl8LPgY
5OuSLxliKzrFDbm5luKN9T2wQf2pFZ/H7E//L/VKm4DVNZyQC1NMrxb6L+b1c8ge
qWKcMwXOIKuphWoRYYtDzyhCzTtu+i7Chsu7kfBzmrGxS9i/yv9XvlvpFISj8WwX
PbyapuljEn3ZY0yf3EX028TKxzyx7NB/4fyYzNhhju8eex7wJyMD/HbJh218OrG5
vZLPq2NhzprO1KyJOOvAG4dLLe+HTKD+ptJv4Tw862Veej35cR1Esb3PXtEdS61Q
0eTE2RhNyQqmNfCJ7Y3sOjn9LTyDub1AkacpG4Pji2W3jyjUBXfY3+YrCUU9FRh6
+6Ma7uSKVtJFH8NFon/EXWjYXDfvHI1Q/BlMvtcxrtQHrsUfm5U=
=3StZ
-END PGP SIGNATURE End Message ---

Processed: Bug#961501 marked as pending in remmina

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #961501 [remmina] remmina is calling home for update notifications
Added tag(s) pending.

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

Bug#961501: marked as pending in remmina

[Matteo F. Vescovi]

Control: tag -1 pending

Hello,

Bug #961501 in remmina 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-remote-team/remmina/-/commit/c6bb777f20879411e57256c8f95c4d11cd28f7bc


debian/rules: drop 'News' dialog on startup

Closes: #961501


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/961501

Bug#962703: mailplate: Should we remove this package from Debian?

[martin f krafft]

Thank you for your efforts! Removal of mailplate is definitely the 
best option.


--
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#962402: haskell-text-icu built

[Frédéric Bonnard]

Hi,
I wanted to check that FTBFS but it actually built, on different setup.
After a give back on ppc64el and s390x, everything went fine. Very few
changes between the failing and succeeding build. Same ghc, kernel.
For the record, linux-libc-dev, libgmpxx4ldbl, libgmp-dev, libkrb5support0,
libk5crypto3, libkrb5-3, libgssapi-krb5-2, libnghttp2-14, hscolour were
not the same.

F.


signature.asc
Description: PGP signature

Processed: closing 913561

[Debian Bug Tracking System]

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

> close 913561 0.12.0-1
Bug #913561 [src:qiskit-terra] qiskit-terra: binary-any FTBFS
Marked as fixed in versions qiskit-terra/0.12.0-1.
Bug #913561 [src:qiskit-terra] qiskit-terra: binary-any FTBFS
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#959479: FTBFS with Boost 1.71

[Adrian Bunk]

On Sat, May 02, 2020 at 09:33:24PM +0200, Giovanni Mascellani wrote:
>...
> More specifically, your package fails building because it uses some
> retired API from Boost.Asio. It appears, though, that upstream dogecoin
> has since long stopped using Asio, switching to libevent2 as IO library
> since commit 40b556d3742a1f65d67e2d4c760d0b13fe8be5b7 (dated Fri Jan 23
> 07:53:17 2015 +0100). I believe it would be more advisable to package an
> updated version of dogecoin rather than patch it for Boost 1.71.
>...

This seems fixed in 1.14.0-1 in unstable now, except that the symbols 
file also needs updating:
  https://buildd.debian.org/status/package.php?p=dogecoin=sid

cu
Adrian

Bug#962727: libwww-mechanize-perl: build fails on IPv6-only buildds

[Adrian Bunk]

Source: libwww-mechanize-perl
Version: 2.00-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libwww-mechanize-perl=all=2.00-1=1591965277=0

...
# Test server http://127.0.0.1:39495 as PID 1878

#   Failed test 'First fetch works'
#   at t/cookies.t line 74.
#  got: '500'
# expected: '200'

#   Failed test 'First cookie matches'
#   at t/cookies.t line 78.
#  got: undef
# expected: 'Cookie #1'

#   Failed test 'Right title'
#   at t/cookies.t line 79.
#  got: undef
# expected: 'Home of Cookie #1'

#   Failed test 'Second fetch works'
#   at t/cookies.t line 84.
#  got: '500'
# expected: '200'

#   Failed test 'Second cookie matches'
#   at t/cookies.t line 88.
#  got: undef
# expected: 'Cookie #2'

#   Failed test 'Right title'
#   at t/cookies.t line 89.
#  got: undef
# expected: 'Home of Cookie #2'

#   Failed test 'Cookie did not change...'
#   at t/cookies.t line 97.
#  got: undef
# expected: 'Cookie #2'

#   Failed test '... but back to the first page title'
#   at t/cookies.t line 98.
#  got: undef
# expected: 'Home of Cookie #1'

#   Failed test 'Cookie did not change...'
#   at t/cookies.t line 106.
#  got: undef
# expected: 'Cookie #2'

#   Failed test 'On the proper 3rd page'
#   at t/cookies.t line 107.
#  got: undef
# expected: 'No cookies sent'

#   Failed test 'Got the third cookie'
#   at t/cookies.t line 115.
#  got: undef
# expected: 'Cookie #3'

#   Failed test 'Title is correct'
#   at t/cookies.t line 116.
#  got: undef
# expected: 'Home of Cookie #3'
# Looks like you failed 12 tests of 14.
t/cookies.t ..
1..14
TestServer: You can connect to your server at http://localhost:39495/
ok 1 - An object of class 'WWW::Mechanize' isa 'WWW::Mechanize'
not ok 2 - First fetch works
not ok 3 - First cookie matches
not ok 4 - Right title
not ok 5 - Second fetch works
not ok 6 - Second cookie matches
not ok 7 - Right title
not ok 8 - Cookie did not change...
not ok 9 - ... but back to the first page title
not ok 10 - Cookie did not change...
not ok 11 - On the proper 3rd page
not ok 12 - Got the third cookie
not ok 13 - Title is correct
ok 14 - Signaled the child process
Dubious, test returned 12 (wstat 3072, 0xc00)
Failed 12/14 subtests
...
Test Summary Report
---
t/cookies.t(Wstat: 3072 Tests: 14 Failed: 12)
  Failed tests:  2-13
  Non-zero exit status: 12
Files=61, Tests=798, 83 wallclock secs ( 0.29 usr  0.10 sys + 15.79 cusr  2.28 
csys = 18.46 CPU)
Result: FAIL
Failed 1/61 test programs. 12/798 subtests failed.
make[2]: *** [Makefile:948: test_dynamic] Error 255


See #962019 for discussion of a similar problem in a different package.

Bug#956019: marked as done (mlpy: needs a source-only upload)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 19:49:00 +
with message-id 
and subject line Bug#956019: fixed in mlpy 3.5.0+ds-1.1
has caused the Debian Bug report #956019,
regarding mlpy: needs a source-only upload
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.)


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

Package: mlpy
Version: 3.5.0+ds-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only upload so your package can migrate.
--- End Message ---
--- Begin Message ---
Source: mlpy
Source-Version: 3.5.0+ds-1.1
Done: Carlos Henrique Lima Melara 

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

Debian distribution maintenance software
pp.
Carlos Henrique Lima Melara  (supplier of updated 
mlpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Jun 2020 23:28:38 -0300
Source: mlpy
Architecture: source
Version: 3.5.0+ds-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Carlos Henrique Lima Melara 
Closes: 956019
Changes:
 mlpy (3.5.0+ds-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Source-only upload. (Closes: #956019)
Checksums-Sha1:
 c23a9c8b32cab30309e84ea4d98f414a1b8a644d 2275 mlpy_3.5.0+ds-1.1.dsc
 662da026123135c63e82984e0f8f0606b9553455 4428 mlpy_3.5.0+ds-1.1.debian.tar.xz
 e76ae108adf30227f35b02ec2533739babb450b9 9137 
mlpy_3.5.0+ds-1.1_source.buildinfo
Checksums-Sha256:
 e11ee26928cf8dfefb26947487b204e577308ceb6d58e65da69d1e351a17a65d 2275 
mlpy_3.5.0+ds-1.1.dsc
 65b5acb192679c5da00733a9bace7bb8909a24c94f56948ba3a8a1aa635d2c8c 4428 
mlpy_3.5.0+ds-1.1.debian.tar.xz
 7dbf4aa6b0e97ccef587b7ae6bd31bf009fa593fbbff741e77b2fe4f373fc26d 9137 
mlpy_3.5.0+ds-1.1_source.buildinfo
Files:
 6aa440606a8de020dbf4cbfba5a898f8 2275 python optional mlpy_3.5.0+ds-1.1.dsc
 0e5aa80b91642d78589a4cfd57535500 4428 python optional 
mlpy_3.5.0+ds-1.1.debian.tar.xz
 abc704caf46ce2fbaa859ec635e6c97d 9137 python optional 
mlpy_3.5.0+ds-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAl7hMusACgkQeElO9yN1
pmxJDhAAoH0afjceeZUKbypzJaGfHO0fpZnGrc4CQDIwfbOTX28aktd7sbJ0hcLS
skdkgZ2l3nPnqgurBt7mVctdEMP7iOwJS8kxa1F2qcjC5ssH9OsaELEegt2re++w
MIJ6LvpD+mp2gjyhYOn+99qdr2x/YQ3t8s0nlNPvQvJNFAkP7KT0tyTQUHNlSl4l
rdK7WVgCuHofylB+mRPP43ABAYQ/9bsAxgxY1CDtc2hQf2cnlgv5zjKvoYylcgeL
JB1TI/cF82TLm3cjMXwpl9ROS7XWVyHnH04ADS2LTIdxrwPDn/9NCC5dLEq2o+O4
vzzNLV/i7WV5C8z/bjtD3YO+SPr2w2tMoOIqlw6B69ZUzcASE/7hr0WboseLWmfR
0+duO6tIprNWLjy9ceMacRwecVm1/vsvpkU2z1BzCFxqB09Dznz5maEnfMN95l4U
tRVzjcpCStnPipRQsOexHY5MRTpwdu7Eu57ClWtVh1mEMNUPCLLY/Ns9qEJUSymZ
LCX6bzujC6lW/2NAe81hmyuceMGH9qG120a9dRHhZxQ9PfDnsPqGmd9dcmUqsOc/
7SBzMRR7eEX5QTUaHXg9b5HUSwZrmmnAvLVqNe/kfQ2A/Ju5kow2ZUM3Os3s34Uv
ubVMUWGdobPS2gpYCWLmc6M13nAjgFrYCkEZ5tyEI4JGowDBpHw=
=vJbh
-END PGP SIGNATURE End Message ---

Bug#962685: wordpress 5.4.2 security release

[Salvatore Bonaccorso]

Hi Craig,

On Fri, Jun 12, 2020 at 06:33:14AM +0200, Salvatore Bonaccorso wrote:
> Hi Craig,
> 
> On Fri, Jun 12, 2020 at 09:40:34AM +1000, Craig Small wrote:
> > Source: wordpress
> > Version: 5.4.1+dfsg1-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > WordPress 5.4.2 is out and fixes the following vulnerabilities:
> [...]
> 
> Thanks for filling the bugreport about those, added tracking in the
> security-tracker correspondigly.
> 
> Are you requesting CVEs for those?

Looks that for all (but not your first mentioned issue) they have CVEs
assigned now (was not when I checked). They are at

https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-4vpv-fgg2-gcqc
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-87h4-phjv-rm6p
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-q6pw-gvf4-5fj5
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-8q2w-5m27-wm27
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-rpwf-hrh2-39jf

Regards,
Salvatore

Bug#962725: gst-plugins-bad1.0: depend on cruft package libsrt-dev

[Gianfranco Costamagna]

Source: gst-plugins-bad1.0
Version: 1.16.2-2.1
Severity: serious
tags: patch

Hello, I choose the gnutls flavour, matching what ffmpeg did
(libsrt was mentioned twice, I removed one of the two)

this is the patch:

diff --git a/debian/build-deps b/debian/build-deps
index 01a6f775..f3d4f4d0 100644
--- a/debian/build-deps
+++ b/debian/build-deps
@@ -65,7 +65,7 @@ librtmp-dev
 libsndfile1-dev (>= 1.0.16)
 libsoundtouch-dev (>= 1.5.0)
 libspandsp-dev
-libsrt-dev
+libsrt-gnutls-dev
 libsrtp2-dev (>= 2.1)
 libssl-dev
 libtool (>= 2.2.6)
diff --git a/debian/build-deps.in b/debian/build-deps.in
index bca081f3..41fe2883 100644
--- a/debian/build-deps.in
+++ b/debian/build-deps.in
@@ -81,6 +81,6 @@ liblcms2-dev (>= 2.7)
 libopenmpt-dev
 libnice-dev (>= 0.1.14)
 libpango1.0-dev (>= 1.22)
-libsrt-dev
+libsrt-gnutls-dev
 libaom-dev
 libusrsctp-dev
diff --git a/debian/control b/debian/control
index 7c8b9160..1163c0d8 100644
--- a/debian/control
+++ b/debian/control
@@ -16,7 +16,6 @@ Build-Depends:  libasound2-dev (>= 0.9.1) [linux-any],
libdrm-dev (>= 2.4.55) [linux-any],
wayland-protocols (>= 1.4) [linux-any],
libvulkan-dev [linux-any],
-   libsrt-dev [linux-any],
libgstreamer1.0-dev (>= 1.16.1),
autoconf (>= 2.69),
automake (>= 1.14),
@@ -83,7 +82,7 @@ Build-Depends:  libasound2-dev (>= 0.9.1) [linux-any],
libsndfile1-dev (>= 1.0.16),
libsoundtouch-dev (>= 1.5.0),
libspandsp-dev,
-   libsrt-dev,
+   libsrt-gnutls-dev,
libsrtp2-dev (>= 2.1),
libssl-dev,
libtool (>= 2.2.6),
diff --git a/debian/rules b/debian/rules
index dca960d8..2751a2e3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -74,7 +74,6 @@ gst_extra_build_depends += , libwayland-dev (>= 1.11.0) 
[linux-any]
 gst_extra_build_depends += , libdrm-dev (>= 2.4.55) [linux-any]
 gst_extra_build_depends += , wayland-protocols (>= 1.4) [linux-any]
 gst_extra_build_depends += , libvulkan-dev [linux-any]
-gst_extra_build_depends += , libsrt-dev [linux-any]
 
 PLUGINS += plugins-bad opencv
 ifeq ($(DEB_HOST_ARCH_OS),linux)

Bug#954148: marked as done (src:doit: autopkgtest requires packages outside the Debian archive)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 19:04:34 +
with message-id 
and subject line Bug#954148: fixed in doit 0.31.1-3.3
has caused the Debian Bug report #954148,
regarding src:doit: autopkgtest requires packages outside the Debian archive
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.)


-- 
954148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:doit
Version: 0.31.1-3.2
Severity: serious
Justification: Policy 2.2.1

This package uses python pip to download and install packages from outside the
Debian archive to run autopkgtests.  Main is required to be self-contained,
including for tests.  See the FTP Master's reject FAQ [1] item Non-Main II.

An excerpt from a recent autpkgtest log is included below to demonstrate the
issue with this package.

Scott K

[1] https://ftp-master.debian.org/REJECT-FAQ.html

autopkgtest [09:47:11]: test unittests: [---
Requirement already satisfied: pyflakes in /usr/lib/python3/dist-packages (from 
-r dev_requirements.txt (line 4)) (2.1.1)
Requirement already satisfied: pytest>=4.0 in /usr/lib/python3/dist-packages 
(from -r dev_requirements.txt (line 5)) (4.6.9)
Collecting pytest-ignore-flaky (from -r dev_requirements.txt (line 6))
  Downloading 
https://files.pythonhosted.org/packages/9b/ea/4264700ace0298cac8b78ae21e6328ba9da5106257af816aecf958b0981e/pytest_ignore_flaky-1.0.0-py3-none-any.whl
Requirement already satisfied: coverage>=4.0 in /usr/lib/python3/dist-packages 
(from -r dev_requirements.txt (line 7)) (4.5.2)
Collecting doit-py>=0.4.0 (from -r dev_requirements.txt (line 8))
  Downloading 
https://files.pythonhosted.org/packages/ed/75/725220e25308fb7e91080d62d532b9e5eb530f7570d8afd6d89dc26461dc/doit-py-0.4.0.tar.gz
Requirement already satisfied: importlib-metadata>=0.12 in 
/usr/lib/python3/dist-packages (from pytest>=4.0->-r dev_requirements.txt (line 
5)) (1.5.0)
Requirement already satisfied: more-itertools>=4.0.0 in 
/usr/lib/python3/dist-packages (from pytest>=4.0->-r dev_requirements.txt (line 
5)) (4.2.0)
Collecting configclass (from doit-py>=0.4.0->-r dev_requirements.txt (line 8))
  Downloading 
https://files.pythonhosted.org/packages/8d/bd/c408897e93e150f1108bdca05cd1e19fac96ab4c6f41c138fc2be93397c3/configclass-0.1.0.tar.gz
Requirement already satisfied: doit in /usr/lib/python3/dist-packages (from 
doit-py>=0.4.0->-r dev_requirements.txt (line 8)) (0.31.1)
Collecting mergedict>=0.2.0 (from configclass->doit-py>=0.4.0->-r 
dev_requirements.txt (line 8))
  Downloading 
https://files.pythonhosted.org/packages/b4/f2/98a8757575ae9eb2d2ac8a7dbced7da3214f394b4c7f0716abc8e3292569/mergedict-1.0.0-py3-none-any.whl
Requirement already satisfied: pyinotify in /usr/lib/python3/dist-packages 
(from doit->doit-py>=0.4.0->-r dev_requirements.txt (line 8)) (0.9.6)
Building wheels for collected packages: doit-py, configclass
  Running setup.py bdist_wheel for doit-py: started
  Running setup.py bdist_wheel for doit-py: finished with status 'done'
  Stored in directory: 
/home/debci/.cache/pip/wheels/ea/b1/ec/63ec025da799f4ff1005d1d55bb6bff4b4687a1868f57f58e1
  Running setup.py bdist_wheel for configclass: started
  Running setup.py bdist_wheel for configclass: finished with status 'done'
  Stored in directory: 
/home/debci/.cache/pip/wheels/0c/54/70/1ca35a8e24061cc30d138377cbf1e20d33c12fc58e2dd4f401
Successfully built doit-py configclass
Installing collected packages: pytest-ignore-flaky, mergedict, configclass, 
doit-py
Successfully installed configclass-0.1.0 doit-py-0.4.0 mergedict-1.0.0 
pytest-ignore-flaky-1.0.0
--- End Message ---
--- Begin Message ---
Source: doit
Source-Version: 0.31.1-3.3
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated doit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 May 2020 10:06:51 +0300
Source: doit
Architecture: source
Version: 0.31.1-3.3

Bug#962724: iptables: autopkgtest regression: nft Unsupported command?

[Paul Gevers]

Source: iptables
Version: 1.8.5-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of iptables the autopkgtest of iptables fails in
testing when that autopkgtest is run with the binary packages of
iptables from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
iptables   from testing1.8.5-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? (your package also
FTBFS everywhere but amd64).

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
iptables/1.8.5-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=iptables

https://ci.debian.net/data/autopkgtest/testing/amd64/i/iptables/5868533/log.gz

autopkgtest [04:50:24]: test command16: ip6tables-translate -h
autopkgtest [04:50:24]: test command16: [---
ip6tables-translate v1.8.5

Usage: ip6tables-translate -[ACD] chain rule-specification [options]
ip6tables-translate -I chain [rulenum] rule-specification [options]
ip6tables-translate -R chain rulenum rule-specification [options]
ip6tables-translate -D chain rulenum [options]
ip6tables-translate -[LS] [chain [rulenum]] [options]
ip6tables-translate -[FZ] [chain] [options]
ip6tables-translate -[NX] chain
ip6tables-translate -E old-chain-name new-chain-name
ip6tables-translate -P chain target [options]
ip6tables-translate -h (print this help information)

Commands:
Either long or short options are allowed.
  --append  -A chainAppend to chain
  --check   -C chainCheck for the existence of a rule
  --delete  -D chainDelete matching rule from chain
  --delete  -D chain rulenum
Delete rule rulenum (1 = first) from chain
  --insert  -I chain [rulenum]
Insert in chain as rulenum (default 1=first)
  --replace -R chain rulenum
Replace rule rulenum (1 = first) in chain
  --list-L [chain [rulenum]]
List the rules in a chain or all chains
  --list-rules -S [chain [rulenum]]
Print the rules in a chain or all chains
  --flush   -F [chain]  Delete all rules in  chain or all chains
  --zero-Z [chain [rulenum]]
Zero counters in chain or all chains
  --new -N chainCreate a new user-defined chain
  --delete-chain
 -X [chain] Delete a user-defined chain
  --policy  -P chain target
Change policy on chain to target
  --rename-chain
 -E old-chain new-chain
Change chain name, (moving any references)
Options:
--ipv4  -4  Nothing (line is ignored by ip6tables-restore)
--ipv6  -6  Error (line is ignored by iptables-restore)
[!] --proto -p protoprotocol: by number or name, eg. `tcp'
[!] --source-s address[/mask][...]
source specification
[!] --destination -d address[/mask][...]
destination specification
[!] --in-interface -i input name[+]
network interface name ([+] for wildcard)
 --jump -j target
target for rule (may load target extension)
  --goto  -g chain
   jump to chain with no return
  --match   -m match
extended match (may load extension)
  --numeric -n  numeric output of addresses and ports
[!] --out-interface -o output name[+]
network interface name ([+] for wildcard)
  --table   -t tabletable to manipulate (default: `filter')
  --verbose -v  verbose mode
  --wait-w [seconds]maximum wait to acquire xtables lock before 
give up
  --wait-interval -W [usecs]wait time to try to acquire xtables lock
default is 1 second
  --line-numbersprint line numbers when listing
  --exact   -x  expand numbers (display exact values)
[!] --fragment  -f  match second or further fragments only
  --modprobe=  

Bug#962723: libdogecoinconsensus-dev,libdogecoinconsensus0: missing Breaks+Replaces: dogecoin (<< 1.14)

[Andreas Beckmann]

Package: libdogecoinconsensus-dev,libdogecoinconsensus0
Version: 1.14.0-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Unpacking libdogecoinconsensus0:amd64 (1.14.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdogecoinconsensus0_1.14.0-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libdogecoinconsensus.so.0.0.0', which is also in 
package dogecoin 1.10.0-7.1+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Preparing to unpack .../libdogecoinconsensus-dev_1.14.0-1_amd64.deb ...
  Unpacking libdogecoinconsensus-dev:amd64 (1.14.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdogecoinconsensus-dev_1.14.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/dogecoinconsensus.h', which is also in 
package dogecoin 1.10.0-7.1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libdogecoinconsensus0_1.14.0-1_amd64.deb
   /var/cache/apt/archives/libdogecoinconsensus-dev_1.14.0-1_amd64.deb


cheers,

Andreas


dogecoin=1.10.0-7.1+b2_libdogecoinconsensus-dev=1.14.0-1.log.gz
Description: application/gzip

Bug#962720: gst-plugins-bad1.0: FTBFS in sid

[Gianfranco Costamagna]

Also this patch
https://aur.archlinux.org/cgit/aur.git/tree/0001-vulkan-Drop-use-of-VK_RESULT_BEGIN_RANGE.patch?h=lib32-gst-plugins-bad

looks needed because of new mesa

G.

Bug#954351: marked as done (FTBFS with Boost 1.71)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 18:21:38 +
with message-id 
and subject line Bug#954351: fixed in rdkit 201909.1-4.1
has caused the Debian Bug report #954351,
regarding FTBFS with Boost 1.71
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.)


-- 
954351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rdkit
Version: 201909.1-2
Severity: wishlist
User: team+bo...@tracker.debian.org
Usertags: boost1.71

Dear Maintainer,

your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:

  deb https://people.debian.org/~gio/reprepro gio main

This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.

More specifically, your package fails building because some problem in
the CMake scripts. I don't really understand the problem, because the
log clearly states that Boost libraries are found, but then for some
reason they cannot be used. I am not really expert of CMake, so I am not
sure of how to debug this.

From the log:

> -- Found Boost: 
> /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found 
> suitable version "1.71.0", minimum required is "1.56.0") found components:  
> serialization 
> == Using strict rotor definition
> -- Found Boost: 
> /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found 
> suitable version "1.71.0", minimum required is "1.56.0") found components:  
> system iostreams 
> -- maeparser include dir set as '/usr/include'
> -- maeparser libraries set as '/usr/lib/x86_64-linux-gnu/libmaeparser.so'
> -- Found maeparser: /usr/include  
> -- coordgen include dir set as /usr/include
> -- coordgen libraries set as '/usr/lib/x86_64-linux-gnu/libcoordgen.so'
> -- Found coordgen: /usr/include  
> Downloading 
> https://github.com/rareylab/RingDecomposerLib/archive/v1.1.3_rdkit.tar.gz...
> == Updating Filters.cpp from pains file
> == Done updating pains files
> -- Configuring done
> CMake Error at Code/cmake/Modules/RDKitUtils.cmake:153 (add_executable):
>   Target "testCoordGen" links to target "Boost::system" but the target was
>   not found.  Perhaps a find_package() call is missing for an IMPORTED
>   target, or an ALIAS target is missing?
> Call Stack (most recent call first):
>   External/CoordGen/CMakeLists.txt:110 (rdkit_test)
Thanks and all the best, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles


rdkit.log.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rdkit
Source-Version: 201909.1-4.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated rdkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 Jun 2020 16:07:07 +0300
Source: rdkit
Architecture: source
Version: 201909.1-4.1
Distribution: unstable
Urgency: high
Maintainer: Debichem Team 
Changed-By: Adrian Bunk 
Closes: 954351
Changes:
 rdkit (201909.1-4.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Add patch for FTBFS with Boost 1.71. (Closes: #954351)
Checksums-Sha1:
 6e7d410100b9f94cc07c496452d12d5ba0e469e0 2768 rdkit_201909.1-4.1.dsc
 6937d7b27b105bc9d8e10fbbcd75f7ff87ee552f 101768 
rdkit_201909.1-4.1.debian.tar.xz
Checksums-Sha256:
 31fd882041adcac007ca5c63710ba8255913cc7bf4d49a82b3710f1d0f044964 2768 
rdkit_201909.1-4.1.dsc
 3c7c32e7a63e30638c5f98ce540477bd115c830491dc132c1d8ea269e9a2b286 101768 
rdkit_201909.1-4.1.debian.tar.xz
Files:
 c3a8b6fc93da7bab1a9313141873495e 2768 science optional rdkit_201909.1-4.1.dsc
 89a6e3f946ba94316c3b1039b3080a8b 101768 science optional 
rdkit_201909.1-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#960756: marked as done (python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 17:49:28 +
with message-id 
and subject line Bug#960756: fixed in python-biopython 1.77+dfsg-1
has caused the Debian Bug report #960756,
regarding python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB 
failures
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.)


-- 
960756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biopython
Version: 1.76+dfsg-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-biopython=sid

...
==
FAIL: test_fasta_db_nucl (test_NCBI_BLAST_tools.BlastDB)
Test makeblastdb wrapper with nucleotide database.
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8/build/Tests/test_NCBI_BLAST_tools.py", 
line 249, in test_fasta_db_nucl
self.assertTrue(os.path.isfile("GenBank/NC_005816.fna.nhd"))
AssertionError: False is not true

==
FAIL: test_fasta_db_prot (test_NCBI_BLAST_tools.BlastDB)
Test makeblastdb wrapper with protein database.
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8/build/Tests/test_NCBI_BLAST_tools.py", 
line 208, in test_fasta_db_prot
self.assertTrue(os.path.isfile("GenBank/NC_005816.faa.phd"))
AssertionError: False is not true

--
Ran 518 tests in 330.272 seconds

FAILED (failures = 1)
Skipping any tests requiring internet access
Python version: 3.8.3 (default, May 14 2020, 11:03:12) 
[GCC 9.3.0]
Operating system: posix linux
E: pybuild pybuild:352: test: plugin custom failed with: exit code=1: set -e; \
 mkdir -p 
/<>/.pybuild/cpython3_3.8/build/home; \
 mkdir -p 
/<>/.pybuild/cpython3_3.8/build/Doc/examples; \
 cp -a Doc/Tutorial.tex 
/<>/.pybuild/cpython3_3.8/build/Doc; \
 cp -a Doc/Tutorial 
/<>/.pybuild/cpython3_3.8/build/Doc; \
 cp -a Doc/examples 
/<>/.pybuild/cpython3_3.8/build/Doc; \
 cp -a Tests 
/<>/.pybuild/cpython3_3.8/build; \
 cd 
/<>/.pybuild/cpython3_3.8/build/Tests; \
 env DIALIGN2_DIR=/usr/share/dialign 
EMBOSS_ROOT=/usr/lib/emboss 
HOME=/<>/.pybuild/cpython3_3.8/build/home python3.8 run_tests.py 
--offline
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 --test 
--system=custom "--test-args=set -e; \\\
 mkdir -p {build_dir}/home; \\\
 mkdir -p {build_dir}/Doc/examples; \\\
 cp -a Doc/Tutorial.tex {build_dir}/Doc; \\\
 cp -a Doc/Tutorial {build_dir}/Doc; \\\
 cp -a Doc/examples {build_dir}/Doc; \\\
 cp -a Tests {build_dir}; \\\
 cd {build_dir}/Tests; \\\
 env DIALIGN2_DIR=/usr/share/dialign 
EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py 
--offline" returned exit code 13
make[1]: *** [debian/rules:83: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: python-biopython
Source-Version: 1.77+dfsg-1
Done: Etienne Mollier 

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

Debian distribution maintenance software
pp.
Etienne Mollier  (supplier of updated 
python-biopython package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 11 Jun 2020 20:10:34 +0200
Source: python-biopython
Architecture: source
Version: 1.77+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: 

Bug#960418: marked as done (libkolabxml: FTBFS with boost 1.71)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 17:04:06 +
with message-id 
and subject line Bug#960418: fixed in libkolabxml 1.1.6-6.1
has caused the Debian Bug report #960418,
regarding libkolabxml: FTBFS with boost 1.71
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.)


-- 
960418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkolabxml
Version: 1.1.6-6
Severity: important
User: team+bo...@tracker.debian.org
Usertags: boost1.71

libkolabxml fails to build with boost 1.71 due to symbol changes. See
https://people.debian.org/~gio/boost_migration/libkolabxml.log.gz

Patch is available at
https://patches.ubuntu.com/libk/libkolabxml/libkolabxml_1.1.6-6ubuntu1.patch

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libkolabxml
Source-Version: 1.1.6-6.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libkolabxml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Jun 2020 00:08:22 +0300
Source: libkolabxml
Architecture: source
Version: 1.1.6-6.1
Distribution: unstable
Urgency: high
Maintainer: Debian Kolab Maintainers 
Changed-By: Adrian Bunk 
Closes: 960418
Changes:
 libkolabxml (1.1.6-6.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * libkolabxml1v5.symbols: Removed symbols that disappeared when
 rebuilding with Boost 1.71. (Closes: #960418)
Checksums-Sha1:
 c2c87606a7a5df5056f0353b6692f9ee707710ab 2371 libkolabxml_1.1.6-6.1.dsc
 fd3afd3f98a34708de41bd790fb6a86937082774 61144 
libkolabxml_1.1.6-6.1.debian.tar.xz
Checksums-Sha256:
 bf32c09c868e49aab5c4d1479b3f4d135e08c7158df1310addf55b8d3b147d7f 2371 
libkolabxml_1.1.6-6.1.dsc
 7c58d24ccc7987248063f479ab7ce10cdddc7685f7d79afac60199b8657cb78c 61144 
libkolabxml_1.1.6-6.1.debian.tar.xz
Files:
 4d33433213690631594bdc0dd8e39e07 2371 libs optional libkolabxml_1.1.6-6.1.dsc
 cd9e72809715c410be71ae54e2778297 61144 libs optional 
libkolabxml_1.1.6-6.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7hTWcACgkQiNJCh6LY
mLF/sg//dOc1+tskIyw9s2gApAaPH9FAvhZY50g9q4TrjyPyHu4fFAH5ecHaRVrs
QBBw00KuiIBi56q2fcV2PehHnltoEfajc5B/9rge4aCSUnDgrsh9d853BXkhNKfB
rLUniMm0rZ1Ns52d11t6FmkUQ6Xf1pWci050SCPlsdMQ5swBbcJzPrPqjbo1F7Rb
EmD5hmoMdYzhhrann8JLWV5xBV4MQo/nuMWLZKOqMxPPiNse1fHYuaNiMJoXzYPX
ngKFRvGp37NWu37uTJWg1C8hq0ueYLu4VSqvoobWZPqA9DLv70l/MpXInOwdRNRx
exIrLTY+Sn0wscQ2cHDN7TJTV2NAUs/Ysrqqk7xliamzXjxeNVUVPxP/E2g5VOyi
Xu+wa+bJN9kiatye0Bo+hmRBVyBvlOSUb3QHdr1L9ruWtODPu+Vc9uET3Oe/Bj3r
f/PyRMGaxJJOy1aKff7YXDj5bPnXKntXhWCK9w5m4veZEnclGEKWZBKu0iWCEn4n
W3fL56ZlfDrrSmDmWWQxlXHykxJth8ud9E0uqMXXZRXSHlRoWK3aHUaGAFgestEg
U18HVrPJqrYPJeqCBLHemk5Dxss3R2+82+bwUdeAn4Y1z8DVAH7XTvqBriWXhfQy
CsRAKrI9YWNOyxIkuttEAg8l1Wy+luKSRRdPWHRxWCiFVW8UGHo=
=NDRC
-END PGP SIGNATURE End Message ---

Bug#959552: marked as done (python-canmatrix: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 16:49:42 +
with message-id 
and subject line Bug#959552: fixed in python-canmatrix 0.9.1~github-1.1
has caused the Debian Bug report #959552,
regarding python-canmatrix: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
959552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-canmatrix
Version: 0.9.1~github-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-canmatrix
> dpkg-buildpackage: info: source version 0.9.1~github-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by IOhannes m zmölnig (Debian/GNU) 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from 
> python-canmatrix-0.9.1~github/debian/source/options: 
> --extend-diff-ignore=^[^/]+.egg-info/
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py clean 
> Warning: 'classifiers' should be a list, got type 'filter'
> running clean
> removing '/<>/.pybuild/cpython3_3.8_canmatrix/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from 
> python-canmatrix-0.9.1~github/debian/source/options: 
> --extend-diff-ignore=^[^/]+.egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-canmatrix using existing 
> ./python-canmatrix_0.9.1~github.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building python-canmatrix in 
> python-canmatrix_0.9.1~github-1.debian.tar.xz
> dpkg-source: info: building python-canmatrix in 
> python-canmatrix_0.9.1~github-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> Warning: 'classifiers' should be a list, got type 'filter'
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> Warning: 'classifiers' should be a list, got type 'filter'
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/types.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/convert.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/join.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/_version.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/j1939_decoder.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/log.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/compare.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/canmatrix.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/cancluster.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/copy.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> copying src/canmatrix/utils.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix
> creating 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix/tests
> copying src/canmatrix/tests/test_cli_compare.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix/tests
> copying src/canmatrix/tests/test_frame_decoding.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix/tests
> copying src/canmatrix/tests/test_cli_convert.py -> 
> /<>/.pybuild/cpython3_3.8_canmatrix/build/canmatrix/tests
> copying src/canmatrix/tests/test_wireshark.py -> 
> 

Bug#948450: marked as done (djview-plugin might be useless now)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 16:48:37 +
with message-id 
and subject line Bug#948450: fixed in djview4 4.11-3
has caused the Debian Bug report #948450,
regarding djview-plugin might be useless now
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.)


-- 
948450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: djview-plugin
Version: 4.11-2
Severity: serious

This package provides an NPAPI plugin.
All major browsers have dropped support for NPAPI.
--- End Message ---
--- Begin Message ---
Source: djview4
Source-Version: 4.11-3
Done: b...@debian.org (Barak A. Pearlmutter)

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated djview4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 12 Jun 2020 17:13:46 +0100
Source: djview4
Architecture: source
Version: 4.11-3
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Closes: 377468 886304 948450 962181
Changes:
 djview4 (4.11-3) unstable; urgency=medium
 .
   * track upstream fixes
 - include keywords in .desktop file which placates lintian
   * debhelper 13
   * bump standards version
   * lengthen long description to placate lintian
   * stop generating browser plugin package that doesn't work with modern
 browsers (closes: #377468, #948450, #962181)
   * remove quotes in mime entry to placate lintian
   * verbose build: don't suppress compiler commands
   * enable executable debugging info
   * pkg-config info quilt patch for FTCBFS issue (closes: #886304)
Checksums-Sha1:
 c684da318ffae61a0933862c1d939d9a99970c32 2107 djview4_4.11-3.dsc
 d678b6ca74b380bd76fd30e048dec84bf88ed19a 16904 djview4_4.11-3.debian.tar.xz
 ce97f98f774770544000e202945f46d4d0f310aa 14806 djview4_4.11-3_source.buildinfo
Checksums-Sha256:
 9fa0fbab6f035b10c1b3f64e38fb443ab1834876bbf56896c4b3f65f5f51888e 2107 
djview4_4.11-3.dsc
 52cb1d9b87111df846858a769942e8644d92673e04d07edb397ee3a3c7ec7a41 16904 
djview4_4.11-3.debian.tar.xz
 021708084b2925b36aa4ce19b029d382046d53aeeed1d682a1d012ed20c751b5 14806 
djview4_4.11-3_source.buildinfo
Files:
 33fee9a683036e1b0b100325177d695f 2107 graphics optional djview4_4.11-3.dsc
 287564b7129feabd335c992411c2853a 16904 graphics optional 
djview4_4.11-3.debian.tar.xz
 3718d85aa769b35a180ceed1fc924526 14806 graphics optional 
djview4_4.11-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAl7jrGgPHGJhcEBkZWJp
YW4ub3JnAAoJEBJbV0deGQ0YcfAQAIjWZcOrziACZoZsjPdzD3Vn4Bj4QEuLvzX1
pv/B60pKYtCxAh+HBOKqgVEeO6ghsD9ZBI4XvUaCOOrhKgDgEJ8uNhmkmS5LTSn+
gwgq91woGTTutjUZTiXhHngelwZnIAIV37IARODjds/Yc6K6VQwZ03+lzk3l33T8
3WTwM/nxfUtc2wacptzDUWBSdK+8U/YRCABdLJdXvURhaR83cDeLYfbDYYkzM51I
PJ714/F7p9K1XB7L4SwJdqaqZqM1Th1g86aEwkZPLEVkhq5h0L03FSESu+KRFkLT
TkQj41Yw3Zsh6iAd6xrq1xrey3ShCwMrdfY2Dkjm37ORQMSCDn6HSvXKNNNat95u
3Vf0GxQzzKI8xVJiYolrvoZHSaCnQRYpfckc7Lig/acjtUamMnfrhWqEdKY9YkYk
9AAK0UdgyLiX6ycrhyl22CI5dkcyR896nHXA0c7sckzXGeXREqp5w0fh/kLzhQSh
X7fiZ/2V3feIeEI6iGu2zkCizEhAiL1T8r5QauOT6vMf9mtFx68BnHwzqL00jycb
9KhNN5cJgncGzT7UyW2hlD/SeW6OuwXqfLfJQC9cesBx6PH8M+Dy2Iy6fdBcsAqw
1cWhRYtMqHZFLDSOBxphgSWRXrWKi02MHGMPZGD/0PWAwGEIBBFp15+3Jz6yd5fe
DJ5s3XHG
=uv3C
-END PGP SIGNATURE End Message ---

Bug#962645: qbittorrent-nox: Qbittorrent-nox is barely usable after the upgrade to 4.2.4-1+b1

[jim_p]

Package: qbittorrent-nox
Followup-For: Bug #962645

Downgrading to 4.2.4-1, the one from last week before the binary update, makes
qbittorrent work as it should, so I assume something went really wrong with
that boost 1.71 build.



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

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

Versions of packages qbittorrent-nox depends on:
ii  libboost-system1.67.0   1.67.0-18
ii  libc6   2.30-8
ii  libgcc-s1   10.1.0-3
ii  libqt5core5a5.12.5+dfsg-10+b1
ii  libqt5network5  5.12.5+dfsg-10+b1
ii  libqt5xml5  5.12.5+dfsg-10+b1
ii  libssl1.1   1.1.1g-1
ii  libstdc++6  10.1.0-3
ii  libtorrent-rasterbar10  1.2.5-1+b1
ii  zlib1g  1:1.2.11.dfsg-2

qbittorrent-nox recommends no packages.

Versions of packages qbittorrent-nox suggests:
pn  qbittorrent-dbg  

-- no debconf information

Bug#962318: libmojolicious-perl: build fails on IPv6-only buildds

[Niko Tyni]

On Tue, Jun 09, 2020 at 06:40:12PM +0200, gregor herrmann wrote:
> On Mon, 08 Jun 2020 10:18:09 +0300, Niko Tyni wrote:
> 
> > This seems to be a wider issue. Copying the debian-perl list for
> > discussion.
> 
> Thanks for the analysis!
>  
> > I'm left wondering if the IO::Socket::IP default behaviour is desirable,
> > or whether we should try to change it (maybe to special case localhost
> > and/or 0.0.0.0 ?)
> 
> Yes please. Patching all reverse dependencies sounds unattractive.

I've since test rebuilt the ~5000 packages that have a build or runtime
dependency on perl, on a system with IPv4 and IPv6 configured on the lo
device, and just a link-local IPv6 address on another device. I found
93 regressions, list below. My hunch is that more than half of them are
due to Net::EmptyPort (in libtest-tcp-perl) being broken.

I'm test rebuilding the whole archive now to see if other parts of the
archive have similar issues, but that's going to take quite a while.

I have not had the tuits yet for looking at IO::Socket::IP properly.
It seems to me that it could look at the address and pass AI_NUMERICHOST
to getaddrinfo(3) if it looks like an IPv4 address. I guess matching
against qr/^\d+\.\d+\.\d+\.\d+$/ would suffice.

I can try a rebuild with a patch like that next, but happy if somebody
else wants to pick this up. There's Perl 5.32 on my TODO list as well :)

IPv6-only regressions spotted:

alice_0.19-2
boxbackup_0.13~~git20200326.g8e8b63c-1
kgb-bot_1.56-1
libanyevent-connection-perl_0.06-5
libanyevent-connector-perl_0.03-2
libanyevent-memcached-perl_0.08-1
libanyevent-redis-perl_0.24-2
libapache-singleton-perl_0.17-1
libapache2-authcookie-perl_3.30-1
libapache2-reload-perl_0.13-3
libapp-termcast-perl_0.13-3
libaudio-mpd-perl_2.004-2
libcgi-application-plugin-captcha-perl_0.04-2
libcgi-application-server-perl_0.063-2
libcorona-perl_0.1004-4
libcpan-mini-inject-perl_0.35-1
libdancer-perl_1.3513+dfsg-1
libdanga-socket-perl_1.62-1
libfcgi-engine-perl_0.22-1
libfurl-perl_3.13-2
libgearman-client-perl_2.004.015-1
libhtml-html5-parser-perl_0.301-2
libhttp-async-perl_0.33-1
libhttp-daemon-ssl-perl_1.05-01-2
libhttp-server-simple-mason-perl_0.14-2
libio-socket-ssl-perl_2.067-1
libio-socket-timeout-perl_0.32-1
libjson-validator-perl_3.25+dfsg-1
liblwp-protocol-https-perl_6.07-2
libmime-tools-perl_5.509-1
libmojo-sqlite-perl_3.003-1
libmojolicious-perl_8.52+dfsg-2
libmojolicious-plugin-assetpack-perl_2.08-2
libmojolicious-plugin-authentication-perl_1.33-1
libmojolicious-plugin-authorization-perl_1.0302-2
libmojolicious-plugin-basicauth-perl_0.08-1
libmojolicious-plugin-bcrypt-perl_0.14-2
libmojolicious-plugin-cgi-perl_0.40-1
libmojolicious-plugin-i18n-perl_1.60-1
libmojolicious-plugin-mailexception-perl_0.20-1
libmojolicious-plugin-renderfile-perl_0.12-4
libmonitoring-livestatus-perl_0.80-1
libnet-facebook-oauth2-perl_0.12-1
libnet-http-perl_6.19-1
libnet-https-nb-perl_0.15-1
libnet-ldap-server-test-perl_0.22-1
libnet-server-mail-perl_0.28-1
libnet-server-perl_2.009-2
libnet-sip-perl_0.822-1
libperlio-via-timeout-perl_0.32-1
libplack-app-proxy-perl_0.29-1
libplack-handler-anyevent-fcgi-perl_0.01-1
libplack-handler-fcgi-ev-perl_0.01-1
libplack-middleware-deflater-perl_0.12-2
libplack-middleware-session-perl_0.33-1
libplack-perl_1.0047-2
libplack-test-agent-perl_1.4-2
libplack-test-externalserver-perl_0.02-1
libpod-webserver-perl_3.11-1
libproc-guard-perl_0.07-1
libprotocol-http2-perl_1.10-1
libredis-perl_1.9950-1
librest-client-perl_273-1
librpc-xml-perl_0.80-2
librt-client-rest-perl_0.60-1
libtest-fake-httpd-perl_0.08-1
libtest-http-server-simple-stashwarnings-perl_0.04-2
libtest-tcp-perl_2.22-1
libtest-www-declare-perl_0.02-4
libtest-www-mechanize-mojo-perl_0.0.20-1
libtest-www-mechanize-perl_1.52-1
libweb-id-perl_1.927-2
libweb-machine-perl_0.17-1
libwiki-toolkit-plugin-ping-perl_0.03-2
libwww-mechanize-perl_1.97-1
myproxy_6.2.6-1
perlbal_1.80-3
pinto_0.14000-1
request-tracker4_4.4.4-1
spamassassin_3.4.4-1
starman_0.4015-1
stunnel4_5.56+dfsg-3
twiggy_0.1025+dfsg-1
inn2_2.6.3+20200601-1
libcrypt-ssleay-perl_0.73.06-1
libnanomsg-raw-perl_0.10-1
libapache2-mod-perl2_2.0.11-2
feersum_1.407-2
libapache-authenhook-perl_2.00-04+pristine-7
libapache-ssllookup-perl_2.00-04-3
libredis-fast-perl_0.26+dfsg-2
remctl_3.16-4
nbdkit_1.20.2-1

-- 
Niko

Bug#944496: marked as done (FTBFS: Assigning non-zero to $[ is no longer possible at tools/hex2bdf)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 15:49:03 +
with message-id 
and subject line Bug#944496: fixed in xfonts-efont-unicode 0.4.2-12
has caused the Debian Bug report #944496,
regarding FTBFS: Assigning non-zero to $[ is no longer possible at tools/hex2bdf
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.)


-- 
944496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfonts-efont-unicode
Version: 0.4.2-11
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi!
I'm afraid that the package fails to build, with a bunch of:
Assigning non-zero to $[ is no longer possible at tools/hex2bdf line 17, <> 
line 7446.

Additionally, there's some binary spew to the terminal.

Full log attached.


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

Kernel: Linux 5.4.0-rc6-00053-g729694c1a413 (SMP w/64 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


xfonts-efont-unicode_amd64.build
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: xfonts-efont-unicode
Source-Version: 0.4.2-12
Done: Hideki Yamane 

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated xfonts-efont-unicode 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 May 2020 21:28:00 +0900
Source: xfonts-efont-unicode
Architecture: source
Version: 0.4.2-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Hideki Yamane 
Closes: 944496
Changes:
 xfonts-efont-unicode (0.4.2-12) unstable; urgency=medium
 .
   * debian/control
 - Move section: fonts
 - We should set Build-Depends: debhelper-compat, instead of
   Build-Depends-Indep
 - Set Standards-Version: 4.5.0
 - Add Rules-Requires-Root: no
 - Set debhelper-compat (= 13)
 - Add "Build-Depends: libarray-base-perl" for below patch
   * Add 0002-deal-with-deprecated-feature-in-Perl5.30.patch (Closes: #944496)
   * Use debian/salsa-ci.yml, instead of debian/.gitlab-ci.yml
   * Trim trailing whitespace.
   * Use correct machine-readable copyright file URI.
Checksums-Sha1:
 0fce1082409d9783d6408c46ad642f1b2dd057e6 2214 xfonts-efont-unicode_0.4.2-12.dsc
 c9234f03686d38f32c4063c606338b02288f898e 5768 
xfonts-efont-unicode_0.4.2-12.debian.tar.xz
 2245a86e172e1999e775c1a1d253cf0cf7d3 6215 
xfonts-efont-unicode_0.4.2-12_amd64.buildinfo
Checksums-Sha256:
 34140deaf2bc1a36feadab05e953d497c9e6380c2fbff8f0398eca0d676e5c2c 2214 
xfonts-efont-unicode_0.4.2-12.dsc
 1ab855ae1d800651fe202acc3777910b6a5207e852cc4d9fc25694dd7a076cd6 5768 
xfonts-efont-unicode_0.4.2-12.debian.tar.xz
 27e5c91b561992e909802c5c520b20ad8cd9c53e24cb3a1b00d1b3c409f492d0 6215 
xfonts-efont-unicode_0.4.2-12_amd64.buildinfo
Files:
 965fc0651fd0471a6b08891f233dc205 2214 fonts optional 
xfonts-efont-unicode_0.4.2-12.dsc
 e11a0c1b051aa5d12ae019378d166b7b 5768 fonts optional 
xfonts-efont-unicode_0.4.2-12.debian.tar.xz
 f783b6ae57c717dd341d5b7741ad7047 6215 fonts optional 
xfonts-efont-unicode_0.4.2-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAl7joDAACgkQXTKNCCqq
sUCI6RAAgLtvZkeywkY+XkI+AnKvhclKbja+NdARSmaJqBfSKzg9Tu87xbZ33CWm
0j8M02yyB+gXGYoxFK0op7lV85P5wsp0uIffRyjMdElm3IX13ncdi+Pduw2kmYTC
0VkP7aSGdYwUNG/DyDu8hvBgwFXKV/RCB3NcI1xPxcJVnu2pQ1UKna4zsmaPS45B
nU3YByuwNei9hyVsPP/Hf3eiPatEFXZQ53fgiO8dobGXmxUxqM0Smwp/cBhUl8k9
v9N2iO3xp1KzGegvKGJC/Zf4uoiG2m95HpP/tJkt9HkvGCFY6QRrwyCPUoaQH4iP
4oqqsgRrPMxUxvkNF2dqW6v3NY6NnSHMUARJ6vJQD97+IpMW3FBwEBgoilFWN7bk
+KkfUCxsjSSXm9vOdvlnIhaBcrKDVR8PnszRx1yvsG3PYA9A7ewQh0vQGZH2MK2a

Processed: Re: libsrt1-openssl: missing Breaks+Replaces

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #962624 [libsrt1-openssl] libsrt1-openssl: missing Breaks+Replaces
Added tag(s) patch.

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

Bug#962624: libsrt1-openssl: missing Breaks+Replaces

[Gianfranco Costamagna]

control: tags -1 patch
(patch uploaded in Ubuntu)

--- srt-1.4.1/debian/changelog  2020-06-10 21:33:17.0 +0200
+++ srt-1.4.1/debian/changelog  2020-06-12 13:10:33.0 +0200
@@ -1,3 +1,9 @@
+srt (1.4.1-3.1) unstable; urgency=medium
+
+  * Add breaks/replaces to ease upgrades (Closes: #962624)
+
+ -- Gianfranco Costamagna   Fri, 12 Jun 2020 
13:10:33 +0200
+
 srt (1.4.1-3) unstable; urgency=medium
 
   [ Jonas Smedegaard ]
diff -Nru srt-1.4.1/debian/control srt-1.4.1/debian/control
--- srt-1.4.1/debian/control2020-06-10 21:33:17.0 +0200
+++ srt-1.4.1/debian/control2020-06-12 13:10:33.0 +0200
@@ -18,9 +18,11 @@
 
 Package: libsrt1-openssl
 Architecture: any
+Breaks: libsrt1 (<< 1.4.1-3)
+Replaces: libsrt1 (<< 1.4.1-3)
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Conflicts: libsrt1-gnutls
+Conflicts: libsrt1-gnutls, libsrt1
 Description: Secure Reliable Transport UDP streaming library (OpenSSL flavour)
  SRT is a latency-aware UDP transport mechanism optimized for video streams.
  It detects and compensates for jitter and bandwidth fluctuations due to
@@ -32,7 +34,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Conflicts: libsrt1-openssl
+Conflicts: libsrt1-openssl, libsrt1
 Description: Secure Reliable Transport UDP streaming library (GnuTLS flavour)
  SRT is a latency-aware UDP transport mechanism optimized for video streams.
  It detects and compensates for jitter and bandwidth fluctuations due to
@@ -42,9 +44,11 @@
 
 Package: libsrt-openssl-dev
 Section: libdevel
+Breaks: libsrt-dev (<< 1.4.1-2)
+Replaces: libsrt-dev (<< 1.4.1-2)
 Architecture: any
 Multi-Arch: same
-Conflicts: libsrt-gnutls-dev
+Conflicts: libsrt-gnutls-dev, libsrt-dev
 Depends: libsrt1-openssl (= ${binary:Version}), ${misc:Depends}
 Suggests: libsrt-doc (= ${binary:Version}), libssl-dev (>= 1.1)
 Description: Secure Reliable Transport UDP streaming library
@@ -57,9 +61,11 @@
 
 Package: libsrt-gnutls-dev
 Section: libdevel
+Breaks: libsrt-dev (<< 1.4.1-2)
+Replaces: libsrt-dev (<< 1.4.1-2)
 Architecture: any
 Multi-Arch: same
-Conflicts: libsrt-openssl-dev
+Conflicts: libsrt-openssl-dev, libsrt-dev
 Depends: libsrt1-gnutls (= ${binary:Version}), ${misc:Depends}
 Suggests: libsrt-doc (= ${binary:Version}), libgnutls28-dev
 Description: Secure Reliable Transport UDP streaming library


Hello, I'm not sure about the fix I did
(libsrt1 and libsrt-dev should have been transitional packages probably, but 
meh, they didn't live
that long to be needed probably).

Forcing their uninstallation, with breaks+replaces did the trick.


No need for the gnutls package to break/replaces the libsrt1 because files are 
called in a different way

G.
On Wed, 10 Jun 2020 22:42:41 +0200 Sebastian Ramacher  
wrote:
> Package: libsrt1-openssl
> Version: 1.4.1-2
> Severity: serious
> 
> When installing libsrt1-openssl if libsrt1 is already installed:
> 
> Preparing to unpack .../libsrt1-openssl_1.4.1-2_amd64.deb ...
> Unpacking libsrt1-openssl:amd64 (1.4.1-2) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libsrt1-openssl_1.4.1-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libsrt.so.1.4.1', which is 
> also in package libsrt1:amd64 1.4.1-1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Selecting previously unselected package libsrt-openssl-dev:amd64.
> Preparing to unpack .../libsrt-openssl-dev_1.4.1-2_amd64.deb ...
> 
> Same issue for libsrt-openssl-dev if libsrt-dev is already installed:
> 
> Unpacking libsrt-openssl-dev:amd64 (1.4.1-2) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libsrt-openssl-dev_1.4.1-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/include/srt/logging_api.h', which is also in 
> package libsrt-dev:amd64 1.4.1-1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/libsrt1-openssl_1.4.1-2_amd64.deb
>  /var/cache/apt/archives/libsrt-openssl-dev_1.4.1-2_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Cheers
> -- 
> Sebastian Ramacher

Processed: Bug#944496 marked as pending in xfonts-efont-unicode

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944496 [src:xfonts-efont-unicode] FTBFS: Assigning non-zero to $[ is no 
longer possible at tools/hex2bdf
Added tag(s) pending.

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

Bug#944496: marked as pending in xfonts-efont-unicode

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #944496 in xfonts-efont-unicode 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/fonts-team/xfonts-efont-unicode/-/commit/4c98de1415c5d8d2009f2f4ef30f50e3c229ffae


add 0002-deal-with-deprecated-feature-in-Perl5.30.patch (Closes: #944496)

use "use Array::Base +1;" and add libarray-base-perl for dependency


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944496

Processed: tagging 962585

[Debian Bug Tracking System]

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

> tags 962585 + fixed-upstream
Bug #962585 [src:schleuder] schleuder: build fails on IPv6-only buildds
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#943450: marked as done (openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 14:49:18 +
with message-id 
and subject line Bug#943450: fixed in openms 2.5.0+cleaned1-3
has caused the Debian Bug report #943450,
regarding openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental
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.)


-- 
943450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openms-doc
Version: 2.4.0-real-1
Severity: normal

Dear Maintainer,

This package failed to build with doxygen 1.8.16-1~exp3 from experimental.

It FTBFS with this error:

[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]pdfTeX warning (ext4): de
stination with the same identifier (name{page.1}) has been already used, duplic
ate ignored

   \relax
l.58
  [1] (./tutorial.tex
Underfull \hbox (badness 1) in paragraph at lines 3--4
...
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [doc/CMakeFiles/doc_tutorials.dir/build.make:65: 
doc/CMakeFiles/doc_tutorials] Error 1
make[4]: Leaving directory '/<>/debian/build'
make[3]: *** [CMakeFiles/Makefile2:34194: doc/CMakeFiles/doc_tutorials.dir/all] 
Error 2
make[3]: Leaving directory '/<>/debian/build'
make[2]: *** [CMakeFiles/Makefile2:34206: 
doc/CMakeFiles/doc_tutorials.dir/rule] Error 2
make[2]: Leaving directory '/<>/debian/build'
make[1]: *** [Makefile:11056: doc_tutorials] Error 2
make[1]: Leaving directory '/<>/debian/build'
make: *** [debian/rules:76: build-arch-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

More details can be found in the file 
debian/build/doc/OpenMS_tutorial/latex_output/refman.log at the end of the 
build.
I attach it.

Paolo

-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openms-doc depends on:
ii  libjs-jquery  3.3.1~dfsg-3

openms-doc recommends no packages.

Versions of packages openms-doc suggests:
pn  libopenms2.4.0  
pn  topp

-- no debconf information
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2019.10.14)  24 OCT 2019 22:10
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**refman.tex
(./refman.tex
LaTeX2e <2018-12-01>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option)
)
\c@part=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\c@figure=\count86
\c@table=\count87
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
)
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
Package: geometry 2018/04/16 v5.8 Page Geometry

(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks14
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty
Package: ifpdf 2018/09/07 v3.3 Provides the ifpdf switch
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty
Package: ifvtex 2016/05/16 v1.6 Detect VTeX and its facilities (HO)
Package ifvtex Info: VTeX not detected.
)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
Package: ifxetex 2010/09/12 v0.6 Provides ifxetex conditional
)
\Gm@cnth=\count88
\Gm@cntv=\count89
\c@Gm@tempcnt=\count90
\Gm@bindingoffset=\dimen103
\Gm@wd@mp=\dimen104
\Gm@odd@mp=\dimen105
\Gm@even@mp=\dimen106
\Gm@layoutwidth=\dimen107
\Gm@layoutheight=\dimen108
\Gm@layouthoffset=\dimen109
\Gm@layoutvoffset=\dimen110
\Gm@dimlist=\toks15
)
(/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty
Package: makeidx 2014/09/29 v1.0m Standard LaTeX package
)
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty
Package: fancyhdr 2019/01/31 v3.10 Extensive control of page headers and footer
s
\f@nch@headwidth=\skip43
\f@nch@O@elh=\skip44
\f@nch@O@erh=\skip45
\f@nch@O@olh=\skip46

Processed: found 962402 in 0.7.0.1-12

[Debian Bug Tracking System]

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

> found 962402 0.7.0.1-12
Bug #962402 [src:haskell-text-icu] haskell-text-icu: FTBFS on ppc64el and 
s390x: toEnum{BlockCode}: tag (302) is outside of enumeration's range (0,280)
Marked as found in versions haskell-text-icu/0.7.0.1-12.
> thanks
Stopping processing here.

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

Bug#949664: libassuan: diff for NMU version 2.5.3-7.1

[Filipi Souza]

Dear maintainer,

I've prepared an NMU for libassuan (versioned as 2.5.3-7.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.


Regards,
Filipi Souza
diff -Nru libassuan-2.5.3/debian/changelog libassuan-2.5.3/debian/changelog
--- libassuan-2.5.3/debian/changelog	2019-07-17 12:09:10.0 -0300
+++ libassuan-2.5.3/debian/changelog	2020-06-10 06:57:10.0 -0300
@@ -1,3 +1,12 @@
+libassuan (2.5.3-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/tests/build-windows: updated to fix testsuite flags being
+  incorrectly passed and to skip a test fail on arch arm64. Thanks
+  Gianfranco Costamagna. (Closes: #949664)
+
+ -- Filipi Souza   Wed, 10 Jun 2020 06:57:10 -0300
+
 libassuan (2.5.3-7) unstable; urgency=medium
 
   * export CPPFLAGS_FOR_BUILD as well
diff -Nru libassuan-2.5.3/debian/tests/build-windows libassuan-2.5.3/debian/tests/build-windows
--- libassuan-2.5.3/debian/tests/build-windows	2019-07-16 14:49:54.0 -0300
+++ libassuan-2.5.3/debian/tests/build-windows	2020-06-10 06:57:10.0 -0300
@@ -2,35 +2,35 @@
 
 set -e
 
-ARCH=$1
+ARCH="$1"
 
 if [ "$ARCH" = x86_64 ]; then
-GCC=x86_64-w64-mingw32-gcc
 WINE=/usr/lib/wine/wine64
 export WINESERVER=/usr/lib/wine/wineserver64
 elif [ "$ARCH" = i686 ]; then
-GCC=i686-w64-mingw32-gcc
 WINE=/usr/lib/wine/wine
 export WINESERVER=/usr/lib/wine/wineserver32
 else
 printf >&2 'Unknown Architecture: %s\n' "$ARCH"
 exit 1
 fi
+GCC="${ARCH}-w64-mingw32-gcc"
 
 # get wine initialized, which normally spews logs to stderr
 # (autopkgtest doesn't want stderr)
 "$WINE" hostname 2>&1
 
-export PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/lib/pkgconfig
+if [ `dpkg --print-architecture` = 'arm64' ] ; then
+  echo "Don't fail testsuite on arm64, this test always failed there"
+  exit 0
+fi
 
-# see https://dev.gnupg.org/T4624 for why this is needed
-extralibs=(-lws2_32)
+export PKG_CONFIG_PATH="/usr/${ARCH}-w64-mingw32/lib/pkgconfig"
 
-"$GCC" -pedantic -Wall -Werror -o test-run.exe \
-   -static \
-   -Wl,--no-as-needed \
-   debian/tests/simple-build.c \
-   $(pkg-config --static --cflags --libs libassuan) "${extralibs[@]}"
+# see https://dev.gnupg.org/T4624 for why this is needed
+extra_libs=(-lws2_32)
 
+# build a static windows binary around libassuan and run it:
+"$GCC" -pedantic -Wall -Werror -static -o test-run.exe debian/tests/simple-build.c $(pkg-config --cflags --static --libs libassuan) "${extra_libs[@]}"
 "$WINE" ./test-run.exe
-rm -f test-run.exe
+rm -f ./test-run.exe

Bug#958958: marked as done (libtorrent-rasterbar must be linked against libatomic on armel/mipsel/m68k/powerpc/sh4)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 13:49:15 +
with message-id 
and subject line Bug#958958: fixed in libtorrent-rasterbar 1.2.5-1.1
has caused the Debian Bug report #958958,
regarding libtorrent-rasterbar must be linked against libatomic on 
armel/mipsel/m68k/powerpc/sh4
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.)


-- 
958958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: btfs
Version: 2.20-1
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

A recent rebuild of btfs against libtorrent-rasterbar10 FTBFS on
release architectures armel and mipsel, among others [1].

I've included what I hope is the relevant part of the log below.

I believe the solution is to link against -latomic, and since linking
is with --as-needed by default now, it should be safe to do this for
all architectures.

Regards
Graham

[1] https://buildd.debian.org/status/package.php?p=btfs


g++ -std=c++11 -Wall -Wextra -Wconversion -Wsign-compare
-Wsign-conversion -Wno-unused-parameter -D_FILE_OFFSET_BITS=64
-I/usr/include/fuse -DTORRENT_USE_OPENSSL -DTORRENT_USE_LIBCRYPTO
-DBOOST_ASIO_HAS_STD_CHRONO=1 -DBOOST_EXCEPTION_DISABLE
-DBOOST_ASIO_ENABLE_CANCELIO -DTORRENT_LINKING_SHARED
-I/usr/include/libtorrent -I/usr/include/arm-linux-gnueabi -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now -o btfs
btfs-btfs.o -lfuse -pthread -ltorrent-rasterbar -lboost_system -lcurl
-lpthread
/usr/bin/ld: 
/usr/lib/gcc/arm-linux-gnueabi/9/../../../arm-linux-gnueabi/libtorrent-rasterbar.so:
undefined reference to `__atomic_fetch_add_8'
/usr/bin/ld: 
/usr/lib/gcc/arm-linux-gnueabi/9/../../../arm-linux-gnueabi/libtorrent-rasterbar.so:
undefined reference to `__atomic_store_8'
/usr/bin/ld: 
/usr/lib/gcc/arm-linux-gnueabi/9/../../../arm-linux-gnueabi/libtorrent-rasterbar.so:
undefined reference to `__atomic_load_8'
/usr/bin/ld: 
/usr/lib/gcc/arm-linux-gnueabi/9/../../../arm-linux-gnueabi/libtorrent-rasterbar.so:
undefined reference to `__atomic_compare_exchange_8'
collect2: error: ld returned 1 exit status
--- End Message ---
--- Begin Message ---
Source: libtorrent-rasterbar
Source-Version: 1.2.5-1.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libtorrent-rasterbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 Jun 2020 17:37:20 +0300
Source: libtorrent-rasterbar
Architecture: source
Version: 1.2.5-1.1
Distribution: unstable
Urgency: high
Maintainer: Cristian Greco 
Changed-By: Adrian Bunk 
Closes: 958958 962090
Changes:
 libtorrent-rasterbar (1.2.5-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Link against libatomic on armel/mipsel/m68k/powerpc/sh4.
 (Closes: #958958)
   * Build depend on python, which reopens #936927 but closes: #962090.
Checksums-Sha1:
 36037d9679c27cd0c0d0ce7c9f643b50ac5ae9f5 2579 
libtorrent-rasterbar_1.2.5-1.1.dsc
 336eae5b60c9078d88307a8145bf60a7b383731a 17632 
libtorrent-rasterbar_1.2.5-1.1.debian.tar.xz
Checksums-Sha256:
 267a1dd8b863e10874259761efdf98e456d11926a925412b6e1480acb18771b4 2579 
libtorrent-rasterbar_1.2.5-1.1.dsc
 99c430804d1d547b4b991424746f726c0fe40b0f1a47823dc5505fbb9281d5e9 17632 
libtorrent-rasterbar_1.2.5-1.1.debian.tar.xz
Files:
 7ec711adff697e02af5f8f3f861270fd 2579 libs optional 
libtorrent-rasterbar_1.2.5-1.1.dsc
 aa918188c5aa50113d824fdcfef67460 17632 libs optional 
libtorrent-rasterbar_1.2.5-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7g/IoACgkQiNJCh6LY
mLHVhQ/8DHIaUBbfdcIBGrzdrsdHRouM+cHrn2iXSn50EOU1TsdEz1owufy5SEYX
FZX9AsKdwI7eVN+kTVGuh9OtLj2gIEawaf4ZayYqIP+X9ZjGAhRh8s0da3ullY2D
yH5QDimam1LoL8qbHrzxRmeZjXjf8E5Y4X2NK0aSwUa52MaCA924yWWWO75JzqyC
PJVS7nuyjSC2MFrxomLoEJVq+JFQO+fG/v6YGDO8URV4EpMqRNBA47U+VWWPjNS0
ksaSN0g3HDIiRxBnCca04QKvFbx3fhss6k+PpKG6g4y5OxgLBpDEnXpdKCOATG8g

Bug#962090: marked as done (libtorrent-rasterbar: Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124.)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 13:49:15 +
with message-id 
and subject line Bug#962090: fixed in libtorrent-rasterbar 1.2.5-1.1
has caused the Debian Bug report #962090,
regarding libtorrent-rasterbar: Can't exec "pyversions": No such file or 
directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm 
line 124.
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.)


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

libtorrent-rasterbar currently fails to build with:
| Can't exec "pyversions": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124.
| dh_auto_clean: error: failed to run pyversions
| make[1]: *** [debian/rules:56: override_dh_auto_clean] Error 25

See
https://buildd.debian.org/status/fetch.php?pkg=libtorrent-rasterbar=amd64=1.2.5-1%2Bb2=1591121318=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libtorrent-rasterbar
Source-Version: 1.2.5-1.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libtorrent-rasterbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 10 Jun 2020 17:37:20 +0300
Source: libtorrent-rasterbar
Architecture: source
Version: 1.2.5-1.1
Distribution: unstable
Urgency: high
Maintainer: Cristian Greco 
Changed-By: Adrian Bunk 
Closes: 958958 962090
Changes:
 libtorrent-rasterbar (1.2.5-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Link against libatomic on armel/mipsel/m68k/powerpc/sh4.
 (Closes: #958958)
   * Build depend on python, which reopens #936927 but closes: #962090.
Checksums-Sha1:
 36037d9679c27cd0c0d0ce7c9f643b50ac5ae9f5 2579 
libtorrent-rasterbar_1.2.5-1.1.dsc
 336eae5b60c9078d88307a8145bf60a7b383731a 17632 
libtorrent-rasterbar_1.2.5-1.1.debian.tar.xz
Checksums-Sha256:
 267a1dd8b863e10874259761efdf98e456d11926a925412b6e1480acb18771b4 2579 
libtorrent-rasterbar_1.2.5-1.1.dsc
 99c430804d1d547b4b991424746f726c0fe40b0f1a47823dc5505fbb9281d5e9 17632 
libtorrent-rasterbar_1.2.5-1.1.debian.tar.xz
Files:
 7ec711adff697e02af5f8f3f861270fd 2579 libs optional 
libtorrent-rasterbar_1.2.5-1.1.dsc
 aa918188c5aa50113d824fdcfef67460 17632 libs optional 
libtorrent-rasterbar_1.2.5-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7g/IoACgkQiNJCh6LY
mLHVhQ/8DHIaUBbfdcIBGrzdrsdHRouM+cHrn2iXSn50EOU1TsdEz1owufy5SEYX
FZX9AsKdwI7eVN+kTVGuh9OtLj2gIEawaf4ZayYqIP+X9ZjGAhRh8s0da3ullY2D
yH5QDimam1LoL8qbHrzxRmeZjXjf8E5Y4X2NK0aSwUa52MaCA924yWWWO75JzqyC
PJVS7nuyjSC2MFrxomLoEJVq+JFQO+fG/v6YGDO8URV4EpMqRNBA47U+VWWPjNS0
ksaSN0g3HDIiRxBnCca04QKvFbx3fhss6k+PpKG6g4y5OxgLBpDEnXpdKCOATG8g
GXk2w1a9lJQ9pd/pfMwc0uS/0UEKVeNmnVD2Qk/uYhOV9sOqpzHYgYTtkx+t3vf5
25S7wCEj9XBpSkrEpbXmwuEOg9kODQCmsHUY68rvr5HJBmEHOhwXKy7N+z5SXBV6
th0yASWrS6D7wYWMX1R8ks+DX1hrnr8o4igAxkzZ3FGLVkRWzus2kxROBSM2FZ+u
KycdwDWs4FmQaL1r4oo5rh0LdeGbTuVglb6j3r+V2ZN/Dy22oWRy4YmgeaEdfHMV
Cqb43Sjfh+cEJwElEHwvHjwGIKWBft/bgeHEQ2trYFjERl0rZqp+repDakG/13lP
LbN7egOEs3d9c5ldXal6WbmdKed/MDsjkSm4OYdq3LLxxGrmNIM=
=ao2n
-END PGP SIGNATURE End Message ---

Bug#962449: marked as done (visp: autopkgtest failure with boost 1.71)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 13:34:26 +
with message-id 
and subject line Bug#962449: fixed in visp 3.3.0-4
has caused the Debian Bug report #962449,
regarding visp: autopkgtest failure with boost 1.71
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.)


-- 
962449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: visp
Version: 3.3.0-3
Severity: serious
Tags: bullseye sid
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

The autopkgtests of visp fail with boost 1.71 [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/v/visp/testing/amd64/


autopkgtest [23:12:29]: test build: [---
g++: error: Boost::thread: No such file or directory
g++: error: Boost::system: No such file or directory
g++: error: Boost::date_time: No such file or directory
autopkgtest [23:12:29]: test build: ---]
autopkgtest [23:12:30]: test build:  - - - - - - - - - - results - - -
- - - - - - -
buildFAIL non-zero exit status 1
autopkgtest [23:12:30]: test build:  - - - - - - - - - - stderr - - -
- - - - - - -
g++: error: Boost::thread: No such file or directory
g++: error: Boost::system: No such file or directory
g++: error: Boost::date_time: No such file or directory
autopkgtest [23:12:30]:  summary
buildFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: visp
Source-Version: 3.3.0-4
Done: Fabien Spindler 

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

Debian distribution maintenance software
pp.
Fabien Spindler  (supplier of updated visp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 12 Jun 2020 12:13:23 +0200
Source: visp
Architecture: source
Version: 3.3.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Fabien Spindler 
Closes: 962449
Changes:
 visp (3.3.0-4) unstable; urgency=medium
 .
   * Add patch to remove boost detection (Closes: #962449)
 - remove boost detection in modules/ar/CMakeLists.txt
 - update cmake tools to generate visp.pc
Checksums-Sha1:
 f9884e475608b0f64acb367fd506958a10dd6762 4558 visp_3.3.0-4.dsc
 dfb0f4e24c4c858acf2c8f0839d4e3c0361f42f3 32380 visp_3.3.0-4.debian.tar.xz
 75b5a580223fcdd5200d181fb9d3d8c67ff97a5a 33628 visp_3.3.0-4_amd64.buildinfo
Checksums-Sha256:
 1073161b7afa6a946d19e4b10b0ae576316bb0c911c33a94a71cb05992b5ab62 4558 
visp_3.3.0-4.dsc
 a8795bda068a65012ad55db71fe02e11ecab7f32e1ec00e3dcfd6f1a7fb2237f 32380 
visp_3.3.0-4.debian.tar.xz
 3d3207e0fb956ceb68d7dbf352f40c6571e15de2cb82f5b99503543a9dbfa70c 33628 
visp_3.3.0-4_amd64.buildinfo
Files:
 a4f94cdeaf4890a2b7d19938a7261fb0 4558 devel optional visp_3.3.0-4.dsc
 ef1a0fcf02006acae379deb5ae57ebbf 32380 devel optional 
visp_3.3.0-4.debian.tar.xz
 ec1802aff43a3588ce8b7c3472dc2a47 33628 devel optional 
visp_3.3.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEX7Rvg9O5UgRjNdJteNxo2zJthDgFAl7jf6ATHG9zYWxsb3VA
ZGViaWFuLm9yZwAKCRB43GjbMm2EOBMeEACU2vyNtcVkczLH/GubZtnQCi5MASVj
Ksp0+nLZmYefwdVUXhltYbWv/s8aqZHKUrM+/sTystXkgFGmMQNqQ6VYR0qLY6Gw
wMwU8JcR5Ub9k4tEY4mfxwlLQ4TlHgqCBATUNWmmnn7sCnDthi273RwNccOekaHD
zhPS3qgs3Ijd6n89iJYCXxj0yGsU1+K8d3RxPjWScArNFJbqE+TTWk3wV88Zmq1E
pFcMacyNhNJtupI+dCGRBcqDvZFkJfUSdZxTZ7vaRPjBM0g1s+zyt88AH6WkUjp5
l+CMeizy/sMIFpFA2WuVs8ASoUjDSiaa0gmwgAlTYCgy7RR796GXva7QR/iyAaNT
fOk9V2KJTmtYoYsT9Uhtr72MlyRPXh9fmBAJ63wAR9grfYyEyW1K9uGcb7p1VDkA
B/+CjkiFALGzH31lDr9JhMQLTVrpAMwVM/Hkk+xqq0A4cjexRMQpDs7likU5UoCE
pVhO9yMMjoLICueteogUdMYZZrpl2zIsoRcBu9igLjvT//vDysmbDwH+iYZLImai
WOvDF3V56TSDYF3DeaYDZruoPa8+xEqft2rGzrKWlz77U1fpr84FJEnwa6+tnx89
Cu8w4q6/kOXoIwOSOYlElRSho/JHDhPt0MF/96VQK7IkPbpkYAqiIbfKcu3pvE/Q
aPMa+BiSpbQ1Ig==
=uc9v
-END PGP SIGNATURE End Message ---

Bug#962390: marked as done (aoflagger FTBFS with boost 1.71)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 12:48:30 +
with message-id 
and subject line Bug#962390: fixed in aoflagger 2.15.0-3
has caused the Debian Bug report #962390,
regarding aoflagger FTBFS with boost 1.71
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.)


-- 
962390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aoflagger
Version: 2.15.0-1
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: 
https://sourceforge.net/p/aoflagger/code/ci/1b8a46d70650bf59320f8a0c9371e619ac40/
Control: block 961995 by -1

After the #960331 fix it failed with:

...
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found suitable 
version "3.8.3", minimum required is "3")
-- Found PythonInterp: /usr/bin/python3.8 (found version "3.8.3")
-- Using python version 3.8.3
CMake Error at 
/usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
  Could NOT find Boost (missing: python3 numpy3) (found suitable version
  "1.71.0", minimum required is "1.55.0")
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.16/Modules/FindBoost.cmake:2179 
(find_package_handle_standard_args)
  CMakeLists.txt:34 (find_package)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: aoflagger
Source-Version: 2.15.0-3
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated aoflagger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 12 Jun 2020 14:02:42 +0200
Source: aoflagger
Architecture: source
Version: 2.15.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 956580 962390
Changes:
 aoflagger (2.15.0-3) unstable; urgency=medium
 .
   * Improve finding of Boost Python (Closes: #962390, #956580)
Checksums-Sha1:
 19663446da61fd84ecaa7a41a64d3d3e04da6397 2449 aoflagger_2.15.0-3.dsc
 9d30b3fea8523cd4c4601d78483d3f6d82d13632 7536 aoflagger_2.15.0-3.debian.tar.xz
Checksums-Sha256:
 e9926a4cce82442cdb5ba3d2e6afeba647153181520b7a22592e1da0135098c1 2449 
aoflagger_2.15.0-3.dsc
 3d66d9b3735e3eee7fabbd983e4fe556ff3da61b949c13ace0382fca368e9665 7536 
aoflagger_2.15.0-3.debian.tar.xz
Files:
 97a1365993933469d96079790a4e3209 2449 science optional aoflagger_2.15.0-3.dsc
 b13e1dc51e9625c0cea6996e28e04376 7536 science optional 
aoflagger_2.15.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl7jdY4ACgkQcRWv0HcQ
3PchIA//aSL5oWIevvdcWsjV5pfFTt1ZddM2yzmhQaNXPFhKo32+D7zsX1ZLmdVg
CtZk7Zpf1Np3+5JuezSFagy1ATC2LH+yGNzO7ScNEhAmPdFgNZhOHoV4PPh+k0Og
gbJjJUlqT7L5PBa+Df6XAEa4AT3IaQpaNRfOxRvdz4eftj/2JL9vjXYQXX8GVmNJ
EkxGddX0KSF4p+TEg+0mdR06rGlILiOlatsH2HVQwcqv/nRf3+SQqXF0+OwwIJEx
cubTh2oh93VxGWPOWBzUhIsRZuWc4/qnRtde6QwL+uXy6IGb4ZnWiin0ElsZOhgz
XCq/UX5z2X9miNYUGHZvZvHXX1Ng1zWIHQLUKvjWinoX6gnhlbLMdm6zJNV6b3zz
CMbxomL7gjpPD4Jm4oDTKLKircgBzoo2pXuSfqGHVHCKcgl7eX0tTZv58luVoSfr
aHUe07vk09ck9QQ+o2s2k/Jb67uvMCc6QuIu1Cl48FViRZU3tXJ3bUPuipHE/hgH
TuS+kbOc3IbhIgRvILQ+tMiESWbDOfVeB1my4e4X9skDN1yqN9gDxlpW9OxldO7w
KlRwfg2eWkwwUp6Qa21rnFffPWe+6huq+rG76tdMpQL/EF3rqzjqtX5eXKGKlkmB
hStMT8SG9h4NT6fouSjcYBdf8695YLsMQzNjCs/pixUp8lzE3Xw=
=FbX6
-END PGP SIGNATURE End Message ---

Bug#954523: marked as pending in alembic

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #954523 in alembic 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/alembic/-/commit/fd94976fd0950e23350216ffa4d6e1831d9440fa


New upstream release (Closes: #954523).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954523

Processed: Bug#954523 marked as pending in alembic

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954523 [src:alembic] alembic: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.7 3.8" returned exit code 13
Added tag(s) pending.

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

Bug#949664: libassuan: diff for NMU version 2.5.3-7.1

[Filipi Souza]

Control: tags 949664 + pending

Dear maintainer,

I've prepared an NMU for libassuan (versioned as 2.5.3-7.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Filipi Souza


diff -Nru libassuan-2.5.3/debian/changelog libassuan-
2.5.3/debian/changelog
--- libassuan-2.5.3/debian/changelog2019-07-17 12:09:10.0
-0300
+++ libassuan-2.5.3/debian/changelog2020-06-10 06:57:10.0
-0300
@@ -1,3 +1,12 @@
+libassuan (2.5.3-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/tests/build-windows: updated to fix testsuite flags being
+  incorrectly passed and to skip a test fail on arch arm64. Thanks
+  Gianfranco Costamagna. (Closes: #949664)
+
+ -- Filipi Souza   Wed, 10 Jun 2020 06:57:10
-0300
+
 libassuan (2.5.3-7) unstable; urgency=medium
 
   * export CPPFLAGS_FOR_BUILD as well
diff -Nru libassuan-2.5.3/debian/tests/build-windows libassuan-
2.5.3/debian/tests/build-windows
--- libassuan-2.5.3/debian/tests/build-windows  2019-07-16
14:49:54.0 -0300
+++ libassuan-2.5.3/debian/tests/build-windows  2020-06-10
06:57:10.0 -0300
@@ -2,35 +2,35 @@
 
 set -e
 
-ARCH=$1
+ARCH="$1"
 
 if [ "$ARCH" = x86_64 ]; then
-GCC=x86_64-w64-mingw32-gcc
 WINE=/usr/lib/wine/wine64
 export WINESERVER=/usr/lib/wine/wineserver64
 elif [ "$ARCH" = i686 ]; then
-GCC=i686-w64-mingw32-gcc
 WINE=/usr/lib/wine/wine
 export WINESERVER=/usr/lib/wine/wineserver32
 else
 printf >&2 'Unknown Architecture: %s\n' "$ARCH"
 exit 1
 fi
+GCC="${ARCH}-w64-mingw32-gcc"
 
 # get wine initialized, which normally spews logs to stderr
 # (autopkgtest doesn't want stderr)
 "$WINE" hostname 2>&1
 
-export PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/lib/pkgconfig
+if [ `dpkg --print-architecture` = 'arm64' ] ; then
+  echo "Don't fail testsuite on arm64, this test always failed there"
+  exit 0
+fi
 
-# see https://dev.gnupg.org/T4624 for why this is needed
-extralibs=(-lws2_32)
+export PKG_CONFIG_PATH="/usr/${ARCH}-w64-mingw32/lib/pkgconfig"
 
-"$GCC" -pedantic -Wall -Werror -o test-run.exe \
-   -static \
-   -Wl,--no-as-needed \
-   debian/tests/simple-build.c \
-   $(pkg-config --static --cflags --libs libassuan)
"${extralibs[@]}"
+# see https://dev.gnupg.org/T4624 for why this is needed
+extra_libs=(-lws2_32)
 
+# build a static windows binary around libassuan and run it:
+"$GCC" -pedantic -Wall -Werror -static -o test-run.exe
debian/tests/simple-build.c $(pkg-config --cflags --static --libs
libassuan) "${extra_libs[@]}"
 "$WINE" ./test-run.exe
-rm -f test-run.exe
+rm -f ./test-run.exe

Processed: libassuan: diff for NMU version 2.5.3-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags 949664 + pending
Bug #949664 [src:libassuan] libassuan: testsuite failure due to wrong flags 
being injected
Added tag(s) pending.

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

Bug#962503: marked as done (libgnustep-gui-dev: NSApplication.h typos lead to FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 12:20:10 +
with message-id 
and subject line Bug#962503: fixed in gnustep-gui 0.28.0-2
has caused the Debian Bug report #962503,
regarding libgnustep-gui-dev: NSApplication.h typos lead to 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.)


-- 
962503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cenon.app
Version: 4.0.6+ds1-2
Severity: important
Tags: sid bullseye
User: pkg-gnustep-maintain...@lists.alioth.debian.org
Usertags: gnustep-gui0.28-transition gnustep-transition

This package fails to build on amd64 with gnustep-gui/0.28.0-1 from
experimental:

gcc DocView.m -c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
-DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
-D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I../../Source/x86_64/linux-gnu -fconstant-string-class=NSConstantString -I. 
-I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \
   -o obj/Cenon.obj/DocView.m.o
In file included from /usr/include/GNUstep/AppKit/AppKit.h:52,
 from DocView.m:70:
DocView.m: In function ‘-[DocView draw:]’:
/usr/include/GNUstep/AppKit/NSApplication.h:131:44: error: expected ‘)’ before 
‘;’ token
  131 | #define NSAppKitVersionNumber10_8  1187;
  |^
DocView.m:1807:45: note: in expansion of macro ‘NSAppKitVersionNumber10_8’
 1807 | if ( floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_8 &&
  | ^
DocView.m:1807:12: note: to match this ‘(’
 1807 | if ( floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_8 &&
  |^
...
make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:515: 
obj/Cenon.obj/DocView.m.o] Error 1
--- End Message ---
--- Begin Message ---
Source: gnustep-gui
Source-Version: 0.28.0-2
Done: Yavor Doganov 

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

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gnustep-gui package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 12 Jun 2020 11:06:34 +0300
Source: gnustep-gui
Architecture: source
Version: 0.28.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Closes: 962503
Changes:
 gnustep-gui (0.28.0-2) unstable; urgency=medium
 .
   * Upload to unstable.
   * debian/gbp.conf: Remove debian-branch.
   * debian/patches/nsappkitversionnumber.patch: New; remove semicolons
 from NSAppKitVersionNumber* definitions (Closes: #962503).
   * debian/patches/gsspeechrecognizer-manpage.patch: Record as applied
 upstream.
   * debian/patches/series: Update.
   * debian/templates/libgnustep-guiN.overrides.m4: Replace
 shlibs-declares-dependency-on-other-package with
 distant-prerequisite-in-shlibs (tag renamed by Lintian).
Checksums-Sha1:
 c322e65c184d0a7ad0bb6dca53dbd59258a72bd8 3019 gnustep-gui_0.28.0-2.dsc
 7e17f6027d3e0ac41ae1b8a01c15015012289cce 19812 
gnustep-gui_0.28.0-2.debian.tar.xz
 f564e493c52eb45c72d94289ad227548b1c4de08 14985 
gnustep-gui_0.28.0-2_amd64.buildinfo
Checksums-Sha256:
 d42b900e37a4b3edaec4ba31e1486a156bbbd02b28bed1defe9afbbb8f330d16 3019 
gnustep-gui_0.28.0-2.dsc
 bb2ba868f5860dd8261a998def9c76691bdc6d249586bf42d73f17e243bbbcbf 19812 
gnustep-gui_0.28.0-2.debian.tar.xz
 38c68a7f8ce6e3ea3aaa306fd23d26162a9b1235381cbad1a409ef55ed898c4f 14985 
gnustep-gui_0.28.0-2_amd64.buildinfo
Files:
 b2b40665a084ad129d5a300e33a90e55 3019 gnustep optional gnustep-gui_0.28.0-2.dsc
 bb12a643b9aa7a058748d5fc20976783 19812 gnustep optional 
gnustep-gui_0.28.0-2.debian.tar.xz
 a796cdbed9cc167df4d80f7419a35931 14985 gnustep optional 

Processed: severity of 961373 is important

[Debian Bug Tracking System]

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

> # builds with boost 1.71 succeeded
> severity 961373 important
Bug #961373 [src:slic3r-prusa] slic3r-prusa FTBFS on armhf: cc1plus: out of 
memory
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)

[Dmitry Shachnev]

Hi!

On Thu, Jun 11, 2020 at 02:57:22PM +0800, pengzon...@uniontech.com wrote:
> Hi!
>
> Sorry for my late reply.
> I tried to exporting QT_XCB_GL_INTEGRATION=xcb_egl  and it still reported
> an error. libglvnd-dev  package was originally installed.

I have never seen this issue, so it's hard to tell anything about it.

I may suggest you to try debugging further and try to find out why Python
and C++ programs behave differently.

Also, you may try to contact upstream PyQt [1] or Qt [2].

[1]: https://www.riverbankcomputing.com/mailman/listinfo/pyqt
[2]: https://bugreports.qt.io/

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: sinntp: diff for NMU version 1.6-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 953908 + patch
Bug #953908 [src:sinntp] sinntp: autopkgtest failure: regular output on stderr
Added tag(s) patch.
> tags 953908 + pending
Bug #953908 [src:sinntp] sinntp: autopkgtest failure: regular output on stderr
Added tag(s) pending.

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

Bug#953908: sinntp: diff for NMU version 1.6-1.1

[Marcelo Mota]

Control: tags 953908 + patch
Control: tags 953908 + pending

Dear maintainer,

I've prepared an NMU for sinntp (versioned as 1.6-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.

Regards,

Marcelo S Mota

diff -Nru sinntp-1.6/debian/changelog sinntp-1.6/debian/changelog
--- sinntp-1.6/debian/changelog 2020-01-12 09:45:54.0 -0300
+++ sinntp-1.6/debian/changelog 2020-06-11 14:29:16.0 -0300
@@ -1,3 +1,11 @@
+sinntp (1.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/tests/control: added restriction to fix CI test. Thanks to
+Paul Gevers . (Closes: #953908)
+
+ -- Marcelo Soares Mota   Thu, 11 Jun 2020 14:29:16 
-0300
+
 sinntp (1.6-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru sinntp-1.6/debian/tests/control sinntp-1.6/debian/tests/control
--- sinntp-1.6/debian/tests/control 2020-01-12 09:42:05.0 -0300
+++ sinntp-1.6/debian/tests/control 2020-06-11 14:29:16.0 -0300
@@ -1 +1,2 @@
 Tests: tests
+Restrictions: allow-stderr

Bug#962703: mailplate: Should we remove this package from Debian?

[Boyuan Yang]

Source: mailplate
Version: 0.2-1
Tags: sid  bullseye
Severity: serious
X-Debbugs-CC: madd...@debian.org

Dear Debian mailplate maintainer,

Thank your for maintaining package mailplate in Debian in the past decades.
However as you can see in https://tracker.debian.org/pkg/mailplate , this
package saw no upload in Debian in the last 12 years. Besides, the registered
homepage is now unavailable (403 Forbidden). Now mailplate is affected by
Debian's ongoing effort in removing all python2-related packages [1].

I'm wondering if you are going to work on this package to have it migrated to
Python3 so that it no longer depends on the now-EOL python2. If that cannot be
achieved in the near future, the best choice of dealing this package might be
having it removed for now and re-introduce it later when the migration is
properly done.

For now I will be preparing for the package removal and submit the removal
request 28 days later (on July 10, 2020). Meanwhile if you have any other
thoughts, please let me know asap so that this package can be properly handled
and maintained.

-- 
Best Regards,
Boyuan Yang


[1] https://wiki.debian.org/Python/2Removal


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

Processed: Re: Bug#959613: range-v3: FTBFS: unique.cpp:58:10: internal compiler error: in dependent_type_p, at cp/pt.c:25610

[Debian Bug Tracking System]

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

> reassign 959613 g++-9
Bug #959613 [src:range-v3] range-v3: FTBFS: unique.cpp:58:10: internal compiler 
error: in dependent_type_p, at cp/pt.c:25610
Bug reassigned from package 'src:range-v3' to 'g++-9'.
No longer marked as found in versions range-v3/0.10.0-1.
Ignoring request to alter fixed versions of bug #959613 to the same values 
previously set
> fixed 959613 9.3.0-10
Bug #959613 [g++-9] range-v3: FTBFS: unique.cpp:58:10: internal compiler error: 
in dependent_type_p, at cp/pt.c:25610
Marked as fixed in versions gcc-9/9.3.0-10.
> found 959613 9.3.0-11
Bug #959613 [g++-9] range-v3: FTBFS: unique.cpp:58:10: internal compiler error: 
in dependent_type_p, at cp/pt.c:25610
Marked as found in versions gcc-9/9.3.0-11.
> found 959613 9.3.0-13
Bug #959613 [g++-9] range-v3: FTBFS: unique.cpp:58:10: internal compiler error: 
in dependent_type_p, at cp/pt.c:25610
Marked as found in versions gcc-9/9.3.0-13.
> severity 959613 important
Bug #959613 [g++-9] range-v3: FTBFS: unique.cpp:58:10: internal compiler error: 
in dependent_type_p, at cp/pt.c:25610
Severity set to 'important' from 'serious'
> affects 959613 src:range-v3
Bug #959613 [g++-9] range-v3: FTBFS: unique.cpp:58:10: internal compiler error: 
in dependent_type_p, at cp/pt.c:25610
Added indication that 959613 affects src:range-v3
> stop
Stopping processing here.

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

Bug#959613: range-v3: FTBFS: unique.cpp:58:10: internal compiler error: in dependent_type_p, at cp/pt.c:25610

[Nicholas Guriev]

reassign 959613 g++-9
fixed 959613 9.3.0-10
found 959613 9.3.0-11
found 959613 9.3.0-13
severity 959613 important
affects 959613 src:range-v3
stop

Dear GCC maintainer, could you please take a little look at this
compiler crash? The regression is appearing since GCC 9.3.0-11 uploaded
on April 24 through 9.3.0-13, while with 9.3.0-10 the ragne-v3 package
is built with no trouble.

Bug#952171: marked as done (yubico-pam: FTBFS: dh_auto_test: error: cd build && make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 10:51:03 +
with message-id 
and subject line Bug#952171: fixed in yubico-pam 2.26-1.1
has caused the Debian Bug report #952171,
regarding yubico-pam: FTBFS: dh_auto_test: error: cd build && make -j4 check 
VERBOSE=1 returned exit code 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.)


-- 
952171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yubico-pam
Version: 2.26-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/build/tests'
> PASS: util_test
> FAIL: pam_test
> ===
>pam_yubico 2.26: tests/test-suite.log
> ===
> 
> # TOTAL: 2
> # PASS:  1
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: pam_test
> ==
> 
> YKVAL mockup started on 30559 at ../../tests/aux/ykval.pl line 52.
> YKVAL mockup started on 17502 at ../../tests/aux/ykval.pl line 52.
> LDAP mockup started at ../../tests/aux/ldap.pl line 101,  line 755.
> in pam_get_user()
> in pam_get_item() 5 for 0
> in conv_func()
> validation for vvincredibletrerdegkkrkkneieultcjdghrejjbckh (on port 17502) 
> at ../../tests/aux/ykval.pl line 62,  line 1.
> in pam_strerror()
> in pam_set_data() yubico_setcred_return
> test 1 failed!
> debug: ../pam_yubico.c:838 (parse_cfg): called.
> debug: ../pam_yubico.c:839 (parse_cfg): flags 0 argc 4
> debug: ../pam_yubico.c:841 (parse_cfg): argv[0]=id=1
> debug: ../pam_yubico.c:841 (parse_cfg): 
> argv[1]=url=http://localhost:17502/wsapi/2/verify?id=%d=%s
> debug: ../pam_yubico.c:841 (parse_cfg): 
> argv[2]=authfile=../../tests/aux/authfile
> debug: ../pam_yubico.c:841 (parse_cfg): argv[3]=debug
> debug: ../pam_yubico.c:842 (parse_cfg): id=1
> debug: ../pam_yubico.c:843 (parse_cfg): key=(null)
> debug: ../pam_yubico.c:844 (parse_cfg): debug=1
> debug: ../pam_yubico.c:845 (parse_cfg): debug_file=1
> debug: ../pam_yubico.c:846 (parse_cfg): alwaysok=0
> debug: ../pam_yubico.c:847 (parse_cfg): verbose_otp=0
> debug: ../pam_yubico.c:848 (parse_cfg): try_first_pass=0
> debug: ../pam_yubico.c:849 (parse_cfg): use_first_pass=0
> debug: ../pam_yubico.c:850 (parse_cfg): nullok=0
> debug: ../pam_yubico.c:851 (parse_cfg): authfile=../../tests/aux/authfile
> debug: ../pam_yubico.c:852 (parse_cfg): ldapserver=(null)
> debug: ../pam_yubico.c:853 (parse_cfg): ldap_uri=(null)
> debug: ../pam_yubico.c:854 (parse_cfg): ldap_bind_user=(null)
> debug: ../pam_yubico.c:855 (parse_cfg): ldap_bind_password=(null)
> debug: ../pam_yubico.c:856 (parse_cfg): ldap_filter=(null)
> debug: ../pam_yubico.c:857 (parse_cfg): ldap_cacertfile=(null)
> debug: ../pam_yubico.c:858 (parse_cfg): ldapdn=(null)
> debug: ../pam_yubico.c:859 (parse_cfg): user_attr=(null)
> debug: ../pam_yubico.c:860 (parse_cfg): yubi_attr=(null)
> debug: ../pam_yubico.c:861 (parse_cfg): yubi_attr_prefix=(null)
> debug: ../pam_yubico.c:862 (parse_cfg): 
> url=http://localhost:17502/wsapi/2/verify?id=%d=%s
> debug: ../pam_yubico.c:863 (parse_cfg): urllist=(null)
> debug: ../pam_yubico.c:864 (parse_cfg): capath=(null)
> debug: ../pam_yubico.c:865 (parse_cfg): cainfo=(null)
> debug: ../pam_yubico.c:866 (parse_cfg): proxy=(null)
> debug: ../pam_yubico.c:867 (parse_cfg): token_id_length=12
> debug: ../pam_yubico.c:868 (parse_cfg): mode=client
> debug: ../pam_yubico.c:869 (parse_cfg): chalresp_path=(null)
> debug: ../pam_yubico.c:899 (pam_sm_authenticate): pam_yubico version: 2.26
> debug: ../pam_yubico.c:914 (pam_sm_authenticate): get user returned: foo
> debug: ../pam_yubico.c:157 (authorize_user_token): Using system-wide 
> auth_file ../../tests/aux/authfile
> debug: ../util.c:154 (check_user_token): Authorization line: foo:vvincredible
> debug: ../util.c:159 (check_user_token): Matched user: foo
> debug: ../util.c:165 (check_user_token): Authorization token: vvincredible
> debug: ../util.c:165 (check_user_token): Authorization token: (null)
> debug: ../util.c:154 (check_user_token): Authorization line: 
> test:cccfhcbe:ccbchvth:
> debug: ../pam_yubico.c:1034 (pam_sm_authenticate): Tokens found for user
> debug: ../pam_yubico.c:1096 (pam_sm_authenticate): conv returned 44 bytes
> debug: ../pam_yubico.c:1110 (pam_sm_authenticate): Skipping first 0 bytes. 
> Length is 44, token_id set to 12 and token OTP 

Bug#959634: marked as done (audtty: FTBFS: audctrl.h:25:10: fatal error: dbus/dbus-glib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 10:48:43 +
with message-id 
and subject line Bug#959634: fixed in audtty 0.1.12-5.1
has caused the Debian Bug report #959634,
regarding audtty: FTBFS: audctrl.h:25:10: fatal error: dbus/dbus-glib.h: No 
such file or directory
to be marked as done.

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

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


-- 
959634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: audtty
Version: 0.1.12-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cc -g -Wall -I/usr/include/dbus-1.0 `pkg-config --cflags glib-2.0` -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -o main.o -c main.c
> In file included from main.c:20:
> /usr/include/audacious/audctrl.h:25:10: fatal error: dbus/dbus-glib.h: No 
> such file or directory
>25 | #include 
>   |  ^~
> compilation terminated.
> make[1]: *** [Makefile:25: main.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/audtty_0.1.12-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: audtty
Source-Version: 0.1.12-5.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated audtty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 May 2020 19:38:24 +0300
Source: audtty
Architecture: source
Version: 0.1.12-5.1
Distribution: unstable
Urgency: low
Maintainer: Chris Taylor 
Changed-By: Adrian Bunk 
Closes: 959634
Changes:
 audtty (0.1.12-5.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Build depend on libdbus-glib-1-dev. (Closes: #959634)
Checksums-Sha1:
 9d81c93d3b731addaa04bc7fb2aad34d4afa42b0 1888 audtty_0.1.12-5.1.dsc
 b1b1ce9955d5cd7aad99363e8d7b7185efe60e82 4212 audtty_0.1.12-5.1.debian.tar.xz
Checksums-Sha256:
 ef50faa20e9b0c850a28b50b1f8de880799415275e976d3d9707c3c6507e508f 1888 
audtty_0.1.12-5.1.dsc
 08b6ccf39dd3083ee8b351a3b6c8a8d36700db13a3b33d5d557354963f6d0129 4212 
audtty_0.1.12-5.1.debian.tar.xz
Files:
 ea5869d9de3cf536bcb57dde0db90c5f 1888 sound optional audtty_0.1.12-5.1.dsc
 55dca0fceb0479316a7bff741b20845c 4212 sound optional 
audtty_0.1.12-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7ROuoACgkQiNJCh6LY
mLGtnxAAo+1w/++1mGYTP25eERTOzHKY2DPqMpgNW3df6stphKfbxhANr2uV7aNb
n8tpOjKlNG2sjLhusFDziwAK9yqJQJ34o1kZR5zWkg4MoBQgRfeeVL0Zz5f8+hm1
rl05CqtvewPyVQizXINvBi3VwUKEBA9ypfMGrJRKeNb045uOC4//iHtJ9zbi2GJ8
uFVaVUxl5lvYfXOo3NTCWOZVDf1RzuOduTjyiKOnixsX/8shpoX6X7aX8DocWgAm
PyLKWcIp2hpETZS2HWldZgiXpf3/gYj4q9sXJqX0+AWeLd9Z7vy2wkAdPmJBVO2A
pY4gWmO0dpBtt3oo0ALvZWrXxEgnJPo7y+SHutgSzGhRTCE358w98hbK8hJhrrJm
48h+1uuNpvrxeQMPVseoGcByKrz/6vp2iIsjtYyg+TtVGNEFKdBlKRyvNXeP9bjg
yUy+Iqw/J84BnOMzxXy7q8TwaqeEqYX1YmTXhCH784OB5IrUWlIVxjOJLuXsnKbQ
TFJ04enORsqLgtatekX9waHjB88ICwvbS5+xX+oHmhgIr9HBu75c4P8OJI6fMoFz
ZwnoZcWEgD97U7XvbI81rMOZ5Dkrn47QzP8uZ6mEao0yuxWjZGepKi2YEJMDT3jK
8OU+BhWRvcCaCRMnebcJMPCc1Sas1aKjH/Lc/NYIS48oNKBWOWk=
=1s2s
-END PGP SIGNATURE End Message ---

Bug#959548: marked as done (eukleides: FTBFS: make[1]: mktexlsr: Command not found)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 10:48:55 +
with message-id 
and subject line Bug#959548: fixed in eukleides 1.5.4-4.2
has caused the Debian Bug report #959548,
regarding eukleides: FTBFS: make[1]: mktexlsr: Command not found
to be marked as done.

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

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


-- 
959548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eukleides
Version: 1.5.4-4.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Installing eukleides
> Installing euktopst
> Installing scripts
> Installing TeX files
> #@mktexlsr 2> /dev/null
> mktexlsr 
> make[1]: mktexlsr: Command not found
> make[1]: *** [Makefile:55: install_tex] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/eukleides_1.5.4-4.1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: eukleides
Source-Version: 1.5.4-4.2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated eukleides package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 May 2020 18:05:05 +0300
Source: eukleides
Architecture: source
Version: 1.5.4-4.2
Distribution: unstable
Urgency: low
Maintainer: Robert Lemmen 
Changed-By: Adrian Bunk 
Closes: 959548
Changes:
 eukleides (1.5.4-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Don't call mktexlsr during the build. (Closes: #959548)
   * Fix building twice in a row.
Checksums-Sha1:
 a17c2e76026fb8edf5333c9e241edda90b69bb67 1756 eukleides_1.5.4-4.2.dsc
 5c34b1e920e789e803870496f24e7e92f19db96b 5408 eukleides_1.5.4-4.2.debian.tar.xz
Checksums-Sha256:
 31681292bc47b593821f9e3b3fc35409a6af3eb37994c3b61047d1c39996c10c 1756 
eukleides_1.5.4-4.2.dsc
 611e99a40fbc9bbc2364ec7889084c5eeaa5e9b0bd8ed3c84726d1419467c524 5408 
eukleides_1.5.4-4.2.debian.tar.xz
Files:
 96620074678fd3e6167277a701fb14e5 1756 math optional eukleides_1.5.4-4.2.dsc
 609f153f387d0f765a47dc87cad7b325 5408 math optional 
eukleides_1.5.4-4.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7RJXEACgkQiNJCh6LY
mLG1Tg/9HlHmrDLWAcS4dr958vbO7f7pE+G3VlXFpHIDcSknsIdI3xDdrLzSPaiV
ByTF5v7ZO5aZ4ue84eXoSKQQRjgwjCKpKohx527xPNmjI8kbsg+OX0RrXuP3MA5K
qTxyNulQ1xlAjgrY+/YuCJfQN1C8cmlAYiTmjJ4JNyLbFsSQUHR68nAhO7Lw9shU
Qf7krJPtolkI4wThS9cuaq2fgDCLu+Mdiw0H5T/k8R/8swr2weS1lxQEed7chg5j
iFUH6Xekg/tMgxY4dQeDLsUwnQxEdFnwvF4fArhNRfgUXe23VaRVvAddz/rJOZA1
LfeDdc1kONxljQ5HoGdtVcbQMvkSDH4+KywQtl27iBuWwjWoHzZsn8TzxRr64hxL
MuvskOuS4/j8iBbq6fFF9GGuCe/OI0WXW5xhMSZ5+uEvhcTj5EO5gedIzGhdj4hK
didNdoITz2DbLs9ooNBcoFJJyFfvGSphzs3C8NIHRK5q6BZdqXOgT1McRD+S8d1/
WDHzLyx6O3bwhE/kqHX/xVLB004o5xIdD0IdjE8fDf+LRZE37+Kde5BqpICF0dKc
NbJ9STfmjXdjhbbPk/tISDfV1OmYryV16OLno0H6hhj4Zsojk4B9gcitpcNZRAK5
7xbgdo/c7P05X0/1xjW2dR6Y2GR+HLC45kGmArUVVR9MiWWXB8Q=
=rLEd
-END PGP SIGNATURE End Message ---

Bug#962368: marked as done (frogatto-data: Source-only upload not automatically built for non-free packages)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 06:19:03 -0400
with message-id 
and subject line Re: Bug#962368: frogatto-data: Source-only upload not 
automatically built for non-free packages
has caused the Debian Bug report #962368,
regarding frogatto-data: Source-only upload not automatically built for 
non-free packages
to be marked as done.

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

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


-- 
962368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frogatto-data
Severity: serious
Version: 1.3.1+dfsg-2
X-Debbugs-CC: mquin...@debian.org

Dear Debian frogatto-data maintainers,

Thanks for updating package frogatto-data in Debian. However, you just
made a source-only upload against a non-free package, which would cause
problems.

By default, Debian's buildd will not build non-free packages due to
licensing concerns. If your package has no licensing concerns, please
follow instructions as written in the Developers Reference [1] to mark
the package as auto-buildable. If not, please make a binary-only upload
(or a source+binary upload) to actually make sure that the deb package
exists in the archive.

-- 
Regards,
Boyuan Yang

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#marking-non-free-packages-as-auto-buildable


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1.3.1+dfsg-3

With recent source+binary upload of frogatto-data, this bug is now solved.

-- 
Regards,
Boyuan Yang


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

Bug#960073: Re: Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)【请注意，邮件由mity...@gmail.com代发】

[pengzon...@uniontech.com]

Hi!

I tried to verify the local opengl/glx, they are normal. It is no problem to 
write QT code directly to call qtwebengine. So I suspect that the problem is 
caused by pyqt.
Looking forward to hearing from you soon.
Thanks.

BRs
//Zongli


testwebengine.cpp
Description: Binary data

Bug#962692: puppet: Crashes due to "missing" facts.d directories

[Wilmer van der Gaast]

Huh https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962320 may in fact be a 
duplicate.

Bug#962692: puppet: Crashes due to "missing" facts.d directories

[Wilmer van der Gaast]

On Fri, 12 Jun 2020, at 09:38, intrigeri wrote:
> > Some stracing uncovered that it was trying to read the following
> > directories:
> >
> > /opt/puppetlabs/facter/facts.d
> > /etc/facter/facts.d
> > /etc/puppetlabs/facter/facts.d
> >
> > through trial and Aborted errors I've created those and now it works again.
> 
> I confirm this workaround fixes the problem for me as well.
> Thanks for figuring it out and sharing this workaround :)
> 
Ha, no worries, glad you discovered this so quickly then!

For others who run into this, let's reduce the above into a oneliner:

mkdir -p /opt/puppetlabs/facter/facts.d /etc/facter/facts.d 
/etc/puppetlabs/facter/facts.d

I just realised that indeed my other testing box had this problem and again it 
was resolved by creating these directories.

Logs show that puppet on this box disappeared on the 7th. (I separately have a 
cronjob that restarts puppet daily due to memory leaks (maybe long gone, the 
cronjob is years old), helping early discovery of this issue) dpkg.log doesn't 
show any ruby or puppet packages being touched then but I do see some libboost 
libraries, I believe at least some of these are (indirect) puppet dependencies?


`//

Bug#962518: cegui-mk2 FTBFS on mipsel/mips64el: symbol differences

[Stephen Kitt]

On Wed, 10 Jun 2020 13:53:58 +0200, Stephen Kitt  wrote:
> On Tue, 9 Jun 2020 21:08:25 +0100, Simon McVittie  wrote:
> > On Tue, 09 Jun 2020 at 15:21:37 -0400, Olek Wojnar wrote:  
> > > On Tue, Jun 9, 2020 at 6:12 AM Adrian Bunk <[1]b...@debian.org>
> > > wrote:
> > > > I wonder if the real fix shouldn't be for cegui-mk2 to stop
> > > > exporting a
> > > pile
> > > > of Boost symbols...
> > > 
> > > 
> > > I would love that. Any advice on a reasonably easy/straightforward way
> > > of doing that?
> > 
> > *If* your upstream is on board with this, my understanding is that
> > the main way to do this is to build with -fvisibility=hidden,
> > and decorate each intentionally-public class/function/thing
> > with a macro that (when building with gcc or clang) expands to
> > __attribute__((__visibility__("hidden"))).
> > 
> > Some upstreams will be doing something similar already, because they are
> > portable to Windows and need to decorate public symbols with
> > __declspec(dllexport) on Windows.  
> 
> See
> https://salsa.debian.org/debian/fcml/-/blob/master/debian/patches/visibility.patch
> for a quick-and-dirty example of both of these approaches (and
> https://salsa.debian.org/debian/fcml/-/commit/22d753b1c820ea339b6b52cbc1cdf6e05229fbf9#34a4bacbb5ecf973fa5f481819228c77da389f43
> for the resulting symbols file simplification).

I’ve looked into the cegui-mk2 situation a bit more. It turns out that the
project itself does define its exported symbols, and that can be used to
built a library with no extraneous symbols:

* add -fvisibility=hidden to the CXXFLAGS (or use the CMake hidden symbol
  support, which I think is available);
* patch the headers define the various export macros, e.g. CEGUIEXPORT in
  cegui/include/CEGUI/Base.h (taking care to match the EXPORTS handling, same
  as the Windows code).

This greatly reduces the number of exported symbols:

 debian/libcegui-mk2-0.8.7.symbols | 7477
 
+++--
 1 file changed, 577 insertions(+), 6900 deletions(-)

However it also breaks dh_dwz.

This still leaves all the bitness variation (armel/armhf/i386 etc. v.
amd64/arm64 etc., which could be better handled with arch-bits), and the
changes from GCC 9 to 10. Those are annoying enough that I suspect it’s
simply not worth dealing with a symbols file, as others have said.

However I do think that controlling the symbols’ visibility would be a good
thing, but that should be dealt with upstream.

Regards,

Stephen


pgp88v71CcYus.pgp
Description: OpenPGP digital signature

Bug#962145: marked as done (nodejs: CVE-2020-11080 CVE-2020-8172 CVE-2020-8174 (June 2020 security release))

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 09:32:09 +
with message-id 
and subject line Bug#962145: fixed in nodejs 10.21.0~dfsg-1~deb10u1
has caused the Debian Bug report #962145,
regarding nodejs: CVE-2020-11080 CVE-2020-8172 CVE-2020-8174 (June 2020 
security release)
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.)


-- 
962145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 10.20.1~dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 10.19.0~dfsg1-1

Hi,

The following vulnerabilities were published for nodejs.

CVE-2020-11080[0]:
HTTP/2 Large Settings Frame DoS

CVE-2020-8172[1]:
TLS session reuse can lead to host certificate verification bypass

CVE-2020-8174[2]:
napi_get_value_string_*() allows various kinds of memory corruption

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-11080
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11080
[1] https://security-tracker.debian.org/tracker/CVE-2020-8172
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8172
[2] https://security-tracker.debian.org/tracker/CVE-2020-8174
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8174
[3] https://nodejs.org/en/blog/vulnerability/june-2020-security-releases

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 10.21.0~dfsg-1~deb10u1
Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= 

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Jun 2020 02:35:16 +0200
Source: nodejs
Architecture: source
Version: 10.21.0~dfsg-1~deb10u1
Distribution: buster-security
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 962145
Changes:
 nodejs (10.21.0~dfsg-1~deb10u1) buster-security; urgency=medium
 .
   * New upstream version 10.21.0~dfsg. Closes: #962145.
   * Security fixes:
 + CVE-2020-11080
 + CVE-2020-8172
 + CVE-2020-8174
Checksums-Sha1:
 30a31a256d4cd50f9ed6695c214769b893656776 3057 nodejs_10.21.0~dfsg-1~deb10u1.dsc
 c95948f590918a4f36de05b61dcc785c8887e7a0 16231704 
nodejs_10.21.0~dfsg.orig.tar.xz
 48f5f4cf8b0139b13d469a56980de45ece54d69a 100040 
nodejs_10.21.0~dfsg-1~deb10u1.debian.tar.xz
 bae499ddb3b314fcd7377f51c674b572c0ac7d4d 7991 
nodejs_10.21.0~dfsg-1~deb10u1_source.buildinfo
Checksums-Sha256:
 7af4de314f97b66f3aca0a5c863feb205d244a1e02177d738c049552f496b7b2 3057 
nodejs_10.21.0~dfsg-1~deb10u1.dsc
 111d0a59a5d0ed8c2f64d46e344e14ea152b0b23f4e892d166a37e5b15c8cb99 16231704 
nodejs_10.21.0~dfsg.orig.tar.xz
 e6328598b1b72cdf9d28f1071214a5f71d6dab8a6c6dc5565d96856c61100d48 100040 
nodejs_10.21.0~dfsg-1~deb10u1.debian.tar.xz
 5b8fdfe5509f9c2a4198bbc272a9cd7b02717a99ead354162720a01c74c45620 7991 
nodejs_10.21.0~dfsg-1~deb10u1_source.buildinfo
Files:
 382f90a5e18e7a37e585384dca624297 3057 javascript optional 
nodejs_10.21.0~dfsg-1~deb10u1.dsc
 3a6dff10c0d58ed9cc7a929aef80da19 16231704 javascript optional 
nodejs_10.21.0~dfsg.orig.tar.xz
 cc0c43957ca629d120e597188b2867e2 100040 javascript optional 
nodejs_10.21.0~dfsg-1~deb10u1.debian.tar.xz
 5e6db70eb65257c4890fd620ad75b3cb 7991 javascript optional 
nodejs_10.21.0~dfsg-1~deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl7aXOwSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN05igQAIsZGfKmoCntQdaGgzTLVZbfsPsefIEB
+a7AOvPVefUteN4HNvOJ4iarvDV4jNDE7EWSjH2NdOEHgLUpvgY0Xbys8khdikqx
cPbnb5vgv4SJPPulT8pVI312in1cTz5lP/XxWooIVoEzv7JbvgC0lJ7Qt6BSsBLt
pP5S0X/dI37Cb7mDpESRRsnWlKXqVtZype8l7GI9Grq9V554bcg083JtoGvlPGwM
sluqtNMpkYdVhvF1uvGiHyiMGo3hIHBG9zPOzZJBtdfGwW3/6pRekXrHr9YmBgI0

Bug#962680: marked as done (janus: CVE-2020-13898 CVE-2020-13899 CVE-2020-13900 CVE-2020-13901)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 08:19:35 +
with message-id 
and subject line Bug#962680: fixed in janus 0.10.1-1
has caused the Debian Bug report #962680,
regarding janus: CVE-2020-13898 CVE-2020-13899 CVE-2020-13900 CVE-2020-13901
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.)


-- 
962680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: janus
Version: 0.10.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/meetecho/janus-gateway/pull/2214

Hi,

The following vulnerabilities were published for janus.

CVE-2020-13898[0]:
| An issue was discovered in janus-gateway (aka Janus WebRTC Server)
| through 0.10.0. janus_sdp_process in sdp.c has a NULL pointer
| dereference.


CVE-2020-13899[1]:
| An issue was discovered in janus-gateway (aka Janus WebRTC Server)
| through 0.10.0. janus_process_incoming_request in janus.c discloses
| information from uninitialized stack memory.


CVE-2020-13900[2]:
| An issue was discovered in janus-gateway (aka Janus WebRTC Server)
| through 0.10.0. janus_sdp_preparse in sdp.c has a NULL pointer
| dereference.


CVE-2020-13901[3]:
| An issue was discovered in janus-gateway (aka Janus WebRTC Server)
| through 0.10.0. janus_sdp_merge in sdp.c has a stack-based buffer
| overflow.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-13898
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13898
[1] https://security-tracker.debian.org/tracker/CVE-2020-13899
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13899
[2] https://security-tracker.debian.org/tracker/CVE-2020-13900
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13900
[3] https://security-tracker.debian.org/tracker/CVE-2020-13901
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13901
[4] https://github.com/meetecho/janus-gateway/pull/2214

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: janus
Source-Version: 0.10.1-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated janus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 12 Jun 2020 10:09:25 +0200
Source: janus
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian VoIP Team 
Changed-By: Jonas Smedegaard 
Closes: 962680
Changes:
 janus (0.10.1-1) unstable; urgency=high
 .
   [ upstream ]
   * new release
 + fixes security issues in SDP code
 closes: bug#962680
 (CVE-2020-13898, CVE-2020-13899, CVE-2020-13900, CVE-2020-13901),
 thanks to Salvatore Bonaccorso
 .
   [ Jonas Smedegaard ]
   * unfuzz patches, and extend to cover e2etest
   * set urgency=high, due to CVE fix
Checksums-Sha1:
 e50a69129f43046a92fd14c46e9c40f4aaee2e5f 2787 janus_0.10.1-1.dsc
 622aeadce32f58d7f2b1180a506bb99d779b4edb 6951415 janus_0.10.1.orig.tar.gz
 224f8ad18edd7c5a08cf99f07185ea57c6ac28e4 19740 janus_0.10.1-1.debian.tar.xz
 b7124c7890a93d72e5d65c41dba7df671a56d055 17198 janus_0.10.1-1_amd64.buildinfo
Checksums-Sha256:
 2df7cf2a33bfec3a0987dbd983b8c6d2dcaca5d2415ca78d9477728aac0cecbb 2787 
janus_0.10.1-1.dsc
 731760e6911908bc523815809487e51320a738f3533f267d4beb83eaa725de85 6951415 
janus_0.10.1.orig.tar.gz
 e4d32282289eb0259cc6af71ccff41e7da4e7a263f9949c2b1de363a9c3c2594 19740 
janus_0.10.1-1.debian.tar.xz
 9c111ff5de33b06f6c21ab257520432f43bac9e407210dc17f4e3703359dc676 17198 
janus_0.10.1-1_amd64.buildinfo
Files:
 a8e79f19a5343ebfa4fa370e7b4ce750 2787 comm optional janus_0.10.1-1.dsc
 fe634b824a41dcb2089d8bed73b57853 6951415 comm optional janus_0.10.1.orig.tar.gz
 88aa11307ce6ccc4fd96aedc16e898da 19740 comm optional 

Bug#962289: marked as done (gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 08:17:32 +
with message-id 
and subject line Bug#962289: fixed in gnutls28 3.6.7-4+deb10u4
has caused the Debian Bug report #962289,
regarding gnutls28: CVE-2020-13777: session resumption works without master key 
allowing MITM
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.)


-- 
962289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnutls28
Version: 3.6.13-4
Severity: grave
Tags: security upstream
Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1011
Control: found -1 3.6.4-1
Control: found -1 3.6.7-4+deb10u3

Hi Andreas,

The following vulnerability was published for gnutsl28, filling it as
RC given the resulting in authentication bypass possibility, but if
you do not agree please downgrade.

CVE-2020-13777[0]:
| GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting
| a session ticket (a loss of confidentiality in TLS 1.2, and an
| authentication bypass in TLS 1.3). The earliest affected version is
| 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until
| the first key rotation, the TLS server always uses wrong data in place
| of an encryption key derived from an application.

If you want I can try to help preparing as well a corresponding
buster-security update.

The issue was introduced in 3.6.4 upstream, so stretch is not
affected.

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-2020-13777
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13777
[1] https://gnutls.org/security-new.html#GNUTLS-SA-2020-06-03
[2] https://gitlab.com/gnutls/gnutls/-/issues/1011

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gnutls28
Source-Version: 3.6.7-4+deb10u4
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated gnutls28 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 Jun 2020 19:32:17 +0200
Source: gnutls28
Architecture: source
Version: 3.6.7-4+deb10u4
Distribution: buster-security
Urgency: high
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 962289
Changes:
 gnutls28 (3.6.7-4+deb10u4) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * GNUTLS-SA-2020-06-03: Flaw in TLS session ticket key construction
 (CVE-2020-13777) (Closes: #962289)
Checksums-Sha1: 
 a6a03560185c91ff0756e4a5a89e64cc216aef6e 3509 gnutls28_3.6.7-4+deb10u4.dsc
 ab70d6845d2efd27986a7af146ffa3192d973838 78712 
gnutls28_3.6.7-4+deb10u4.debian.tar.xz
Checksums-Sha256: 
 0d633cb281152d025b49fa398930c8f5ea2e9af529bc9a2d288813679e75d88f 3509 
gnutls28_3.6.7-4+deb10u4.dsc
 2bf9e2ce3603e46ad2a47762e4e96c2f64729fe5bd784274025aa99f33a11688 78712 
gnutls28_3.6.7-4+deb10u4.debian.tar.xz
Files: 
 4e19564f52ba71851112b45c5e4cfc9f 3509 libs optional 
gnutls28_3.6.7-4+deb10u4.dsc
 f2e6a94c3af7e8346738ee0b339d9790 78712 libs optional 
gnutls28_3.6.7-4+deb10u4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl7bmT5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EygkP/RmssqHIMnJO3RT8Fcyry1YwfoYOCnnI
7cGQALm5OaQvlduqrrfbw75nSO5MoSoCDVxwEtUkqpMHQR6mZacDfSA/7vdWTQ0g
rtRd+LJ2gtUceRdoX0fQV4KH0fCfnYUv/YITjiT4UYqr98RV6n/MZAJyNt1gMOGL
84BPeLqcVfmNOOatoWTpH9H93qqpxPyepqPcx8W21DId8Y9d21OpXNBylo8rc7et
k0iwe5bGeQoQA8h9M23P3HtO9o9Fgap/SeKAvm5LPGXRBCpMCuxBnez0rvVw/I6c
lR+Ze6xVGIO8H03j66PDhy4D/M7V8JbInP1FEwtw0TNAgVXiwPk2b7YrTepCSgQE
ByqF+STaAyccP69NVGwbh7fW2EW/oaJqtUL8w0HH7+3KPcYKKUcyTU/dNvENZlr0
hdqIitX3Ogkr2/A9SGSVhSMR/AonCYodYuZAPjjiicg5BeS+dwauT7kDxvTfCugp

Bug#962692: puppet: Crashes due to "missing" facts.d directories

[intrigeri]

Hi,

Wilmer van der Gaast (2020-06-12):
> wilmer@veer:~/adsb$ sudo puppet agent --waitforcert 60 -t
> /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is
> obsolete
> /usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using
> the last argument as keyword parameters is deprecated
> free(): invalid pointer
> Aborted

On a sid system, I see puppet-master.service failing to start with
the same "free(): invalid pointer" error.

> Some stracing uncovered that it was trying to read the following
> directories:
>
> /opt/puppetlabs/facter/facts.d
> /etc/facter/facts.d
> /etc/puppetlabs/facter/facts.d
>
> through trial and Aborted errors I've created those and now it works again.

I confirm this workaround fixes the problem for me as well.
Thanks for figuring it out and sharing this workaround :)

Cheers!

Bug#961986: marked as done (lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`?)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jun 2020 07:33:35 +
with message-id 
and subject line Bug#961986: fixed in lix 0.9.29-1.1
has caused the Debian Bug report #961986,
regarding lix FTBFS: Error: undefined identifier `FracSec`, did you mean 
function `fracSec`?
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.)


-- 
961986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lix
Version: 0.9.29-1
Severity: serious
Tags: ftbfs

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

...
sdlang-d 0.10.4: building configuration "library"...
.dub/packages/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d(28,21): Error: 
undefined identifier `FracSec`, did you mean function `fracSec`?
.dub/packages/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d(29,18): Error: 
undefined identifier `FracSec`, did you mean function `fracSec`?
.dub/packages/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d(48,21): Error: 
undefined identifier `FracSec`, did you mean function `fracSec`?
.dub/packages/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d(49,18): Error: 
undefined identifier `FracSec`, did you mean function `fracSec`?
ldc2 failed with exit code 1.
make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: lix
Source-Version: 0.9.29-1.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated lix 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Jun 2020 13:11:32 +0200
Source: lix
Binary: lix lix-data
Architecture: source
Version: 0.9.29-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Gianfranco Costamagna 
Description:
 lix- Puzzle game inspired by Lemmings
 lix-data   - Puzzle game inspired by Lemmings
Closes: 961986
Changes:
 lix (0.9.29-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Peter Michael Green  ]
   * Add patch from upstream pull request to fix build with new libphobos
 (Closes: 961986)
Checksums-Sha1:
 306c8c1a216542da1316dac286d2b6cd3e13d555 2027 lix_0.9.29-1.1.dsc
 6a78c8e83471b617c5f7a16b0c680e7b02ee4091 81048 lix_0.9.29-1.1.debian.tar.xz
 e1b1232693bee261535c85e83dc98e03cae682d7 7197 lix_0.9.29-1.1_source.buildinfo
Checksums-Sha256:
 eb5a1232906b6bf258cac9091a0dc422f3c66d097444a73cd5476200634ea8d8 2027 
lix_0.9.29-1.1.dsc
 17580cdc6465327d333da2cbe4a77e61db34edccc8d480a95655ec122c63f2fa 81048 
lix_0.9.29-1.1.debian.tar.xz
 ef1ee08d3485fc826a39de6b3d4db4ecede5c7a76dbefa7bf6f2a7afb9af1d9f 7197 
lix_0.9.29-1.1_source.buildinfo
Files:
 5811a275d2478c8d922789d12fd8b4ea 2027 games optional lix_0.9.29-1.1.dsc
 49a2045d227ca86bcfc545cad1f22c17 81048 games optional 
lix_0.9.29-1.1.debian.tar.xz
 e1fc4b5e756ac40ba107c69575c36b85 7197 games optional 
lix_0.9.29-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl7gwAQACgkQ808JdE6f
XdkCcA/5AZ98W/1uUuaoD23rIcPda3ruPprf8SVRk0AjECOq8a7xgGMBbwNxFHf7
x5AywfJCu+KBf2WLwmA7vtgnYsRz0IrH9AlQsPiMHWk5DVDTbKqq+xIuP+OviiyV
OQbfdHcUP7klSuE7hB9CeIu4Yf5ZJXHF6rQ33FZ2ZglXTgneitk9fmhr/7Y6hf74
1x8y3H0XAKutbF+LTt6XxQ2LmP9ysTW1ckEapuhDtuSetUbj6GAQG8BCH2i04pBf
TLlVxupp8r2RvUlyW78qebHOQZS+8GS27QXZgoJku5x8Rm0/+zP/pDwSvBm0LgJC
AJPiRSr/WBFYxbJjQTy2IzE8BJ1t/3pdk/iJffqYdcLrSGLYpf675y0Y8wnPYXWS
foBSVzA6vJ5tgeEgTNMMUqbqwqSKYTnfU+zML+4VaP5fYkhk13x4Iu5cMMY8AkHr
szLBxpQvI37ehdIAkEVW7g7ttVgv/gcZnUaPmSeubYrlmRcW3umqK23fcAXvE0bm
Sh0AvxNbw8Xiyk4UdK80lfocSpJb5nt2Yq728yaPm7frDihQN+FM/G8zuzk3WGEK
NNpcm1KtmZUKMR6uW7eElxENUGUBnggHT4XoXVSZ3Vx7B7g1TlnM/y/c9ML8OUOv
ChAzYMkd41My2RJKCrrurggqIf5WsFhSnzkMlsTDLR8qcMMgQ6k=
=2kJg
-END PGP SIGNATURE End Message ---

Bug#962692: puppet: Crashes due to "missing" facts.d directories

[Wilmer van der Gaast]

Package: puppet
Version: 5.5.19-1
Severity: grave
Justification: renders package unusable


Since the recent Ruby upgrade, Puppet invocations have been very noisy for a
while already.

But by now it's not even starting. Even after a dpkg -P including most
dependencies (including apt-get remove ruby.*) then reinstalling, all I
get is:

wilmer@veer:~/adsb$ sudo puppet agent --waitforcert 60 -t
/usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is
obsolete
/usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using
the last argument as keyword parameters is deprecated
free(): invalid pointer
Aborted

Some gdb'ing and strace'ing suggests it gets stuck in facter, which indeed
fails individually with the ~same error.

Some stracing uncovered that it was trying to read the following
directories:

/opt/puppetlabs/facter/facts.d
/etc/facter/facts.d
/etc/puppetlabs/facter/facts.d

through trial and Aborted errors I've created those and now it works again.

Really wondering what's special about my system, or are more folks
seeing this?



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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages puppet depends on:
ii  adduser  3.118
ii  facter   3.11.0-4.1
ii  hiera    3.2.0-2
ii  init-system-helpers  1.57
ii  lsb-base 11.1.0
ii  ruby 1:2.7+1
ii  ruby-augeas  1:0.5.0-3+b8
ii  ruby-deep-merge  1.1.1-1
ii  ruby-shadow  2.5.0-1+b3

Versions of packages puppet recommends:
ii  debconf-utils  1.5.74
ii  lsb-release    11.1.0
ii  ruby-selinux   3.0-1+b3

Versions of packages puppet suggests:
pn  ruby-hocon  
pn  ruby-rrd    

-- no debconf information

Processed: bug 960577 is forwarded to https://github.com/tonioo/sievelib/pull/73

[Debian Bug Tracking System]

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

> forwarded 960577 https://github.com/tonioo/sievelib/pull/73
Bug #960577 [src:python-sievelib] python-sievelib FTBFS with python3-pip 20.1
Set Bug forwarded-to-address to 'https://github.com/tonioo/sievelib/pull/73'.
> thanks
Stopping processing here.

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

Bug#962533: mlpack FTBFS on mips64el: relocation truncated to fit

[Adrian Bunk]

On Fri, Jun 12, 2020 at 05:56:39AM +0800, YunQiang Su wrote:
> Adrian Bunk  于 2020年6月9日周二 下午11:18写道：
>...
> just add -mxgot to cxxflags.
> there are 2 type of GOT in mips: one use fewer insn while has a length
> limitaion; another uses more insns while has a big address space support.
>...

That's what I tried:

> > I tried "export DEB_CXXFLAGS_MAINT_APPEND += -mxgot" which gave me:
> >
> > ...
> > /usr/bin/c++  -g -O2 -fdebug-prefix-map=/home/bunk/build/mlpack-3.3.1=.
> > -fstack-protector-strong -Wformat -Werror=format-security -mxgot
> > -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -ftemplate-depth=1000
> > -Wno-unused-function -O3 -fopenmp  -Wl,-z,relro -Wl,-z,now -rdynamic
> > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o  -o ../../../../bin/mlpack_cf
> > -Wl,-rpath,/home/bunk/build/mlpack-3.3.1/obj-mips64el-linux-gnuabi64/lib:
> > ../../../../lib/libmlpack.so.3.3 /usr/lib/libarmadillo.so
> > /usr/lib/mips64el-linux-gnuabi64/libboost_program_options.so
> > /usr/lib/mips64el-linux-gnuabi64/libboost_unit_test_framework.so
> > /usr/lib/mips64el-linux-gnuabi64/libboost_serialization.so -lpthread
> > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function
> > `std::mersenne_twister_engine > 13043109905998158313ul, 29ul, 6148914691236517205ul, 17ul,
> > 8202884508482404352ul, 37ul, 1873444759240704ul, 43ul,
> > 6364136223846793005ul>::seed(unsigned long)':
> > /usr/include/c++/9/bits/random.tcc:329:(.text._ZN6mlpack4math10RandomSeedEm[_ZN6mlpack4math10RandomSeedEm]+0xb8):
> > relocation truncated to fit: R_MIPS_TLS_GOTTPREL against
> > `arma::arma_rng_cxx11_instance'
> > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function
> > `std::mersenne_twister_engine > 13043109905998158313ul, 29ul, 6148914691236517205ul, 17ul,
> > 8202884508482404352ul, 37ul, 1873444759240704ul, 43ul,
> > 6364136223846793005ul>::operator()()':
> > /usr/include/c++/9/bits/random.tcc:458:(.text._ZN4arma8arma_rng5randuIdE4fillEPdy[_ZN4arma8arma_rng5randuIdE4fillEPdy]+0x70):
> > relocation truncated to fit: R_MIPS_TLS_GOTTPREL against
> > `arma::arma_rng_cxx11_instance'
> > /usr/include/c++/9/bits/random.tcc:457:(.text._ZN4arma8arma_rng5randuIdE4fillEPdy[_ZN4arma8arma_rng5randuIdE4fillEPdy]+0x354):
> > relocation truncated to fit: R_MIPS_TLS_GOTTPREL against
> > `arma::arma_rng_cxx11_instance'
> > collect2: error: ld returned 1 exit status
> >
> >
> > debian-mips is Cc'ed, can a mips porter please have a look?

What are these R_MIPS_TLS_GOTTPREL relocations?

cu
Adrian

Bug#962158: lintian: New very problematic --fail-on default value

[Guillem Jover]

Control: tags -1 patch

*Sigh*

On Wed, 2020-06-10 at 08:38:05 -0700, Felix Lechner wrote:
> On Tue, Jun 9, 2020 at 11:15 PM Chris Lamb  wrote:
> >
> > Felix, can you help out? I am not in a position to contribute to this
> > discussion itself.
> 
> Well, I wish I could. Guillem makes many alarmist statements,

This is a funny way to put it I guess. :)

> but fails to explain why the change is an undue burden.

I've done that multiple times now.

> I also do not know
> how to engage productively with visceral and absolute responses such
> as:

Obviously biased, but I don't see anything visceral in any of the
"selected" (out of context) quotes below. They reflect IMO either
astonishment or a reasoned view on the matter. If you disagree you
could have as well rebutted them, which you still have not done…

(Should really not be going over these, because this is yet again
another diversion from the matter at hand but…)

> > Err…

This was in reply to:

  ,---
  As I explained on IRC this statement is probably untrue (and you did
  not have the courtesy to mention that objection here).
  `---

So pretty much astonishment at this, first because I'm not in the
habit of leaking conversations from IRC w/o permission, and second
because of the unsubstantiated truthiness claim veiled in as a
"possibility".

> > it does not make any sense whatsoever
> > does not match reality
> > it does not even make sense within a Debian-centric view

Supported in the context conveniently trimmed out.

> > I'll have to very much disagree
> > you have still not explained what this default change really accomplishes
> > besides inducing tons of work and breakage
> > No, they did not.

These are either substantiated opinion (also conveniently trimmed
out), or facts. If the facts are wrong, you can always challenge them.

> It's amazing how much time and energy Guillem expended on this issue
> here, on IRC, and in #962157 while dpkg has more open bugs than
> Lintian.

Wow, just wow, I'm not sure where to begin here TBH. First, I'm not
even sure how this is in the least relevant to this report, how it
is relevant to you how anyone else spends their time in a volunteer
project, and how that compares to anything else.

But this just feels like a pattern to me, when there are no more
technical arguments to make, you start either the unrelated diversion
and distraction, the personal comments, etc.

And, really, the bug reports have actually been 4 shortish emails. The
"bulk" of the time was on IRC, but that has not been the only and first
instance of endless and repetitive discussions going in circles, with
unrelated tangents all over the place…

> As you know from my past behavior with 'md5sums -z' or the odd
> contributor on Salsa, I am not opposed to compromise when it brings
> peace. In the present case, such a compromise could be a value 'none'
> to disable the default Guillem likes (and which I would like to
> remove).

Again with the personification, this is not something _I_ personally
like. I could personally adapt. This is something I do consider to
be a global bad default for the program and Debian, derivatives, etc
at large.

It's clear you want this behavior change, it's not clear why though.
The reasons I've seen from you are:

  - it has been advertised.
  - ftp-masters have requested it (and they are the only ones that
matter, at which moment I guess I wonder that's the point of any
non-fatal tags in lintian that ftp-masters do not use)
  - a very vague and unsubstantiated "the current solution is simple,
elegant, straightforward and explicit".
  - unrelated claims about the exit status being unreliable.
  - other unrelated stuff from IRC.

The attached (untested, just «perl -cw» checked) patch, applied after
reverting commit 30ae7cab479e64bf58618e17854794112f8cc791 does not
really look complex to me TBH, in addition of fixing a small bug.

> At the same time, the change was widely released two weeks ago. Simon
> Quigley from Ubuntu announced it on debian-devel on May 25 [1], while
> I advertised the change repeatedly on IRC and added a note to DevNews.
> Some users may have already adapted their systems.
> 
> [1] https://lists.debian.org/debian-devel/2020/05/msg00239.html

Yet again, advertising a change does not imply there's a justification
for it, that's not a technical nor even a good social reason. (Not to
mention that not everyone has apt-listchanges installed, so not even a
NEWS might be seen, and as mentioned the problem with that is that it
would go unnoticed given that it is a silent breaking change.)

> It would also give me more time to understand the possibly
> unreasonable burden on Lintian users across Debian and the derivative
> ecosystem. Simon may receive feedback from Ubuntu, a significant
> derivative. If there are real problems, I am happy to discuss a
> solution that reverts the default to Lintian's old setting.

This again shows that all the reasons exposed on IRC and on the reports
are 

Processed: Re: Bug#962158: lintian: New very problematic --fail-on default value

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #962158 [lintian] lintian: Swapped exit statuses and --fail-on default 
value require downstream adjustments
Added tag(s) patch.

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

Bug#925782: mp3check: diff for NMU version 0.8.7-3.1

[David da Silva Polverari]

Control: tags 925782 + pending

Dear maintainer,

I've prepared an NMU for mp3check (versioned as 0.8.7-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.

Regards,

David Polverari.
diff -Nru mp3check-0.8.7/debian/changelog mp3check-0.8.7/debian/changelog
--- mp3check-0.8.7/debian/changelog	2018-12-22 18:33:01.0 -0500
+++ mp3check-0.8.7/debian/changelog	2020-06-11 00:33:53.0 -0500
@@ -1,3 +1,12 @@
+mp3check (0.8.7-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/60_bts925782_ftbfs_with_gcc_9.patch: added to fix FTBFS
+with GCC-9. Thanks to Joachim Reichel . (Closes:
+#925782)
+
+ -- David da Silva Polverari   Thu, 11 Jun 2020 00:33:53 -0500
+
 mp3check (0.8.7-3) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru mp3check-0.8.7/debian/patches/60_bts925782_ftbfs_with_gcc_9.patch mp3check-0.8.7/debian/patches/60_bts925782_ftbfs_with_gcc_9.patch
--- mp3check-0.8.7/debian/patches/60_bts925782_ftbfs_with_gcc_9.patch	1969-12-31 19:00:00.0 -0500
+++ mp3check-0.8.7/debian/patches/60_bts925782_ftbfs_with_gcc_9.patch	2020-06-11 00:33:53.0 -0500
@@ -0,0 +1,50 @@
+Description: fix FTBFS with GCC-9
+Author: Joachim Reichel 
+Bug-Debian: https://bugs.debian.org/925782
+Last-Update: 2019-09-01
+
+--- a/texception.h
 b/texception.h
+@@ -38,10 +38,10 @@
+ 
+ #define TExceptionN(n) public: virtual const char *name()  const { return #n; }
+ #define TExceptionM(m) public: virtual const char *message() const { return m; }
+-#define TExceptionM1(m,a) public: virtual const char *message() const { char *buf; asprintf(, m, a); return buf; }
+-#define TExceptionM2(m,a,b) public: virtual const char *message() const { char *buf; asprintf(, m, a,b); return buf; }
+-#define TExceptionM3(m,a,b,c) public: virtual const char *message() const { char *buf; asprintf(, m, a,b,c); return buf; }
+-#define TExceptionM4(m,a,b,c,d) public: virtual const char *message() const { char *buf; asprintf(, m, a,b,c,d); return buf; }
++#define TExceptionM1(m,a) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a); return result != -1 ? buf : "asprintf failure"; }
++#define TExceptionM2(m,a,b) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a,b); return result != -1 ? buf : "asprintf failure"; }
++#define TExceptionM3(m,a,b,c) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a,b,c); return result != -1 ? buf : "asprintf failure"; }
++#define TExceptionM4(m,a,b,c,d) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a,b,c,d); return result != -1 ? buf : "asprintf failure"; }
+ 
+ // base class of all exceptions 
+ class TException {
+--- a/tstring.cc
 b/tstring.cc
+@@ -111,7 +111,7 @@
+ tstring::Rep *tstring::Rep::create(size_t tmem) {
+size_t m = sizeof(Rep) << 1;
+while((m - 1 - sizeof(Rep)) < tmem) m <<= 1;
+-   Rep *p = new (m - 1 - sizeof(Rep)) Rep;
++   Rep *p = new (/*tag*/ true, m - 1 - sizeof(Rep)) Rep;
+p->mem = m - 1 - sizeof(Rep); p->ref = 1; p->vulnerable = false;
+return p;
+ }
+--- a/tstring.h
 b/tstring.h
+@@ -71,9 +71,12 @@
+   
+   // static methods
+   // operator new for this class
+-  static void * operator new (size_t size, size_t tmem) {
++  // add a tag parameter to ensure that the signature of the delete operator does not collide with the (void*,size_t) overload
++  static void * operator new (size_t size, bool /*tag*/, size_t tmem) {
+ 	 return ::operator new (size + tmem + 1);}
+-  static void operator delete (void *p, size_t) {
++  static void operator delete (void *p, bool /*tag*/, size_t) {
++	 ::operator delete (p); }
++  static void operator delete (void *p) {
+ 	 ::operator delete (p); }
+   
+   // create a new representation
diff -Nru mp3check-0.8.7/debian/patches/series mp3check-0.8.7/debian/patches/series
--- mp3check-0.8.7/debian/patches/series	2018-12-22 18:33:01.0 -0500
+++ mp3check-0.8.7/debian/patches/series	2020-06-11 00:12:11.0 -0500
@@ -4,3 +4,4 @@
 30_hardening.patch
 40_bts726068_remove_truncated_last_frame.patch
 nostrip.patch
+60_bts925782_ftbfs_with_gcc_9.patch

Processed: mp3check: diff for NMU version 0.8.7-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 925782 + pending
Bug #925782 [src:mp3check] mp3check: ftbfs with GCC-9
Added tag(s) pending.

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