Processed: valabind: FTBFS

[Debian Bug Tracking System]

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

> tags 952107 + ftbfs
Bug #952107 [src:valabind] valabind: FTBFS: ../gowriter.vala:217.16-217.26: 
error: The name `data_type' does not exist in the context of `Vala.DataType' 
(libvala-0.48)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

[Ansgar]

block 952399 by 924937
thanks

Ansgar writes:
> the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
> than just libpq5: just looking at a small sample of the direct rdeps of
> libssl1.1, one can find the following GPL-licensed programs linking it:
>
>   cryptsetup, wesnoth, mydumper, mupdf, gatling, kopete
>
> Also amanda-client, validns as they contain patches in d/patches
> licensed under the GPL.
>
> There are probably lots more, especially when you start looking at
> libraries (and their whole dependency trees).

Or kmod (GPL-2+).

Ansgar

Processed: Re: Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

[Debian Bug Tracking System]

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

> block 952399 by 924937
Bug #952399 [kmod] OpenSSL linking without license exception
952399 was not blocked by any bugs.
952399 was not blocking any bugs.
Added blocking bug(s) of 952399: 924937
> thanks
Stopping processing here.

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

Bug#952570: tcpcopy: build-depends on removed package iptables-dev

[Juhani Numminen]

Package: tcpcopy
Version: 0.6.3-2.1
Severity: serious
X-debbugs-cc: peter green 

tcpcopy build-depends on removed iptables-dev. Please see Peter's message below
on how to handle the situation (from bug #951090).


On Tue, 11 Feb 2020 01:08:16 + peter green  wrote:
> Package: keepalived
> Version: 1:2.0.19-1
> Severity: serious
> 
> keepalived build-depends on iptables-dev, which is no longer built by the 
> iptables source package. It is still present in unstable as a cruft package, 
> but is completely gone from testing.
> 
> Before it's removal iptables-dev was a transitional dummy package depending 
> on a bunch of other dev packages, please determine which of those dev 
> packages your package needs and adjust your build-dependencies accordingly.

Bug#904657: marked as done (voltron: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 06:20:14 +
with message-id 
and subject line Bug#904657: fixed in voltron 0.1.7+git20200109-1
has caused the Debian Bug report #904657,
regarding voltron: fails to install with Python 3.7
to be marked as done.

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

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


-- 
904657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: voltron
Version: 0.1.4-2
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up voltron (0.1.4-2) ...
File "/usr/lib/python3/dist-packages/voltron/plugins/view/memory.py", line 
14
  async = True
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package voltron (--configure):
   installed voltron package post-installation script subprocess returned error 
exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


voltron=0.1.4-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: voltron
Source-Version: 0.1.7+git20200109-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated voltron 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, 26 Feb 2020 00:57:18 -0500
Source: voltron
Architecture: source
Version: 0.1.7+git20200109-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Boyuan Yang 
Closes: 904657
Changes:
 voltron (0.1.7+git20200109-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ ChangZhuo Chen (陳昌倬) ]
   * debian/control: Update Vcs-* fields to Salsa.
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Boyuan Yang ]
   * New upstream snapshot (2020-01-09).
 + Fix installation failure with Python 3.7.
   (Closes: #904657)
   * debian/control: Bump Standards-Version to 4.5.0.
   * debian/patches: Disable usage of pysigset. Upstream is not
 using this module so the patch should be safe.
Checksums-Sha1:
 864889283523586b8b0a31cb21dccdd0c19792f5 2266 voltron_0.1.7+git20200109-1.dsc
 c6818c43d29a7eec4f8dc272a9dc92fae01591bf 71251 
voltron_0.1.7+git20200109.orig.tar.gz
 28c1e0860fa7999e4c73869532d32e7d3df0b397 3464 
voltron_0.1.7+git20200109-1.debian.tar.xz
 31c836cd2205b473d752cdb280d7ea4455d5dc18 7837 
voltron_0.1.7+git20200109-1_amd64.buildinfo
Checksums-Sha256:
 7be470a249f4bdd9a38580a4520a724e89a5c70e90189404dccc85a2e9dd1182 2266 
voltron_0.1.7+git20200109-1.dsc
 bfb484a432955d39f9f1063d816c6f4e74622995d315d31dbdb06efd3f0ea753 71251 
voltron_0.1.7+git20200109.orig.tar.gz
 b173ce5460a5e27519d22fc871f1f9989ad4bfb0899e0dfa4753bbb6d86e8552 3464 
voltron_0.1.7+git20200109-1.debian.tar.xz
 551954c505acecf2706a484377d4b8a320b5dd841084ea08e5f8b1e7d805ee4c 7837 
voltron_0.1.7+git20200109-1_amd64.buildinfo
Files:
 44d18c3286c16fe96d1d106ebb9fcaa7 2266 devel optional 
voltron_0.1.7+git20200109-1.dsc
 925974c463416e09bfea469d0194c7c5 71251 devel optional 
voltron_0.1.7+git20200109.orig.tar.gz
 f7cb8d5cdfc5c6e3f8552c9264b4eed1 3464 devel optional 
voltron_0.1.7+git20200109-1.debian.tar.xz
 629e59f4d6995fdb059f88f82e424d06 7837 devel optional 
voltron_0.1.7+git20200109-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl5WCu4ACgkQwpPntGGC
Ws7LpxAAueTjSPU0AYdeOnr4DvjEAS2H2CCbn8YI6SgtnhyFvW4cXKIyYZqgwJar
PcLOqca/rVNQwC+FHE2IQkb+BrcXevFNGEuqYZNcheWnXrf9lKE/KLDsLvQPTEO4
KidDAAhCNG1IrDr6/tinGv9G+ryMGRXOnq/msaq13Uy3bh10PANxNj5+Xi5RMBLh

Bug#952312: [Pkg-javascript-devel] Bug#952312: Bug#952312: Bug#952312: node-eslint-scope: FTBFS: tests failed

[Xavier]

Le 25/02/2020 à 22:19, Jonas Smedegaard a écrit :
> Quoting Bastien ROUCARIES (2020-02-25 21:13:48)
>> Le mar. 25 févr. 2020 à 19:48, Jonas Smedegaard  a écrit :
>>
>>> control: reassign -1 node-espree
>>> control: affects -1 node-eslint-scope
>>>
>>> Quoting Xavier (2020-02-25 18:29:35)
 Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit :
> During a rebuild of all packages in sid, your package failed to
> build on amd64.

 Some test are incompatible with node-espree-6. The fix could be
 simply:
>>>
>>> Certainly not a fix to disable tests.
>>>
>>> The package node-espree has exactly one reverse dependency which is
>>> node-eslint-scope, so this is a case of bad coordination.
>>>
>>> (yes, another fix would be to upgrade node-eslint-scope, but that is 
>>> more complex and less urgent, so let's roll back first and work on 
>>> going forward in experimental first
>>
>>
>>
>> Node-espree was upgraded due to not compatible with acorn6...
>>
>> So upgrade is safer
> 
> Please define "safer" in this context.
> 
>  - Jonas

Hi,



 * node-espree is a test dependency of node-eslint-scope in unstable
 * node-espree is a dependency of eslint (new package in experimental)
 * last eslint (6.8.0) depends on espree ≥ 6
 * eslint experimental version is 4.18.2
 * last eslint depends on babel 7
 * node-espree <6 is broken by acorn 6
 * acorn update is part of the difficult Node.js 12 upgrade (with
   rollup-1, gulp 4,...)

I think we should prioritize Node.js upgrade here (needs a transition),
then babel 7, then upgrade eslint to the last version

Bug#952007: marked as done (veyon: FTBFS: ld: final link failed: bad value)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 05:34:44 +
with message-id 
and subject line Bug#951494: fixed in procps 2:3.3.16-2
has caused the Debian Bug report #951494,
regarding veyon: FTBFS: ld: final link failed: bad value
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.)


-- 
951494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: veyon
Version: 4.3.1+repack1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o):
>  relocation R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be 
> used when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: bad value
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/veyon_4.3.1+repack1-2_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: procps
Source-Version: 2:3.3.16-2
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated procps 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, 25 Feb 2020 08:08:40 +1100
Source: procps
Architecture: source
Version: 2:3.3.16-2
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 951335 951494
Changes:
 procps (2:3.3.16-2) unstable; urgency=medium
 .
   * Fix symlink to new soname Closes: #951494
   * top: restore configuration file backward compatibility Closes:
 #951335
   * put remaining binaries in /bin in Linux under /usr/bin
Checksums-Sha1:
 95413f29e17928aa289fdbd5a2c036c92d65ffca 2104 procps_3.3.16-2.dsc
 8630f58c186b6e52752fb7c8754f9fa912f6e383 29044 procps_3.3.16-2.debian.tar.xz
 0976763e739ecd08060b10ddf624793148598eb6 6981 procps_3.3.16-2_amd64.buildinfo
Checksums-Sha256:
 7a5b67f76bc6121e15255753b40ad09ce4c37cc5ec4d80ced88a3dd77269102a 2104 
procps_3.3.16-2.dsc
 187262259daf92e7aeb55888113b83e77636d794c26ca1f4f215fd28347547f8 29044 
procps_3.3.16-2.debian.tar.xz
 1b578eea1a52a879de301c70da4af52f6aecfd58351af091fe1308608fc8142f 6981 
procps_3.3.16-2_amd64.buildinfo
Files:
 04aa94f712a9e27058521994403fa203 2104 admin optional procps_3.3.16-2.dsc
 79d93e3c4de6e58ad0c4c3d340926f38 29044 admin optional 
procps_3.3.16-2.debian.tar.xz
 8b0288b7d51faa4cbebe0127341032c7 6981 admin optional 
procps_3.3.16-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl5UO9UACgkQAiFmwP88
hOOPsw//fmQB9JcXo7/4VjPAJ/iLNP6FWO0KXxjmylXh7fAvUXow4axHeChnhk0W
YdkLQIYf6Meh0KBl9QQMm+xCXmiKaBXQwcGvNJvjBi382yNaTYGiqJ9nEMvCrXAU
GubDKu3l9gIGKUgykYzC2HjMkF4+fGYxadKTup4sspwVEKGl38+i6gkkmY1c8OD0
didRvQWTXqurps11lL3JgakrCSS4UOHVdBCwiZVILkdVCAehmbbQ5SFfSeAem8jv
nKoEO4TLAC3bnNOqeaGJQv9/YHzdC478cT50y5vhJMGbztOptgfnft3mqypUMmS2
MpzzC+ek/najisS7R93Yfbt4SVR8eWI4fExLm+o/+BKoTf9bsT5W7LjymfNqPALH
NuRwWg0dzwvABgDFv7aLgkueJdWFacC9YGzZC9VnAjxaBE6Y2mqNfOmyUzuvfrEW
rcwmf8NJoBjEokDbzFTZDFkXD5bqPqsobWmblcyx4ZNVf+R+EEniegfllMzyBifG
A4I4c7WKkSrjnkfFpiwXQHPXRZ9xtyAw8NYn/DU5eI8ZikaLQS7i7INYFqZbjAgQ
2bs5veQ66vH64JYJFyQbIByKdh//evwuo+LcxaHACacz6kKkSXhVtLyIZDxbvtTM
3my9BLI+FXCgUUefdRngKgWEqXG7liByAg2Jm/u15QGxWHb86jo=
=LCLR
-END PGP SIGNATURE End Message ---

Bug#952271: marked as done (apitrace: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libprocps.so', needed by 'glretrace'. Stop.)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 05:34:44 +
with message-id 
and subject line Bug#951494: fixed in procps 2:3.3.16-2
has caused the Debian Bug report #951494,
regarding apitrace: FTBFS: make[3]: *** No rule to make target 
'/usr/lib/x86_64-linux-gnu/libprocps.so', needed by 'glretrace'.  Stop.
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.)


-- 
951494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apitrace
Version: 9.0+repack-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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libprocps.so', 
> needed by 'glretrace'.  Stop.
> make[3]: *** Waiting for unfinished jobs
> [ 98%] Building CXX object retrace/CMakeFiles/eglretrace.dir/glws_waffle.cpp.o
> cd /<>/obj-x86_64-linux-gnu/retrace && /usr/bin/c++  
> -DGTEST_HAS_TR1_TUPLE=0 -DHAVE_BACKTRACE=1 -DHAVE_READPROC_H -DHAVE_X11 
> -DRETRACE -D_GNU_SOURCE -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
> -I/<>/thirdparty/khronos -I/<>/compat 
> -I/<>/thirdparty/brotli/c/include -I/usr/src/gtest/include 
> -I/<>/lib/trace -I/<>/lib/os 
> -I/<>/retrace -I/<>/lib/highlight 
> -I/<>/helpers -I/<>/obj-x86_64-linux-gnu/dispatch 
> -I/<>/dispatch -I/<>/lib/image 
> -I/<>/lib/ubjson -I/<>/thirdparty/dxerr 
> -I/<>/thirdparty/mhook/mhook-lib -I/usr/include/waffle-1  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -std=gnu++11 -Wall -Wno-sign-compare -fno-strict-aliasing -fno-rtti 
> -fno-exceptions -fmessage-length=0 -fno-omit-frame-pointer   -o 
> CMakeFiles/eglretrace.dir/glws_waffle.cpp.o -c 
> /<>/retrace/glws_waffle.cpp
> [ 98%] Building CXX object retrace/CMakeFiles/glretrace.dir/glws_xlib.cpp.o
> [ 99%] Building CXX object retrace/CMakeFiles/glretrace.dir/glws_glx.cpp.o
> cd /<>/obj-x86_64-linux-gnu/retrace && /usr/bin/c++  
> -DGTEST_HAS_TR1_TUPLE=0 -DHAVE_BACKTRACE=1 -DHAVE_READPROC_H -DHAVE_X11 
> -DRETRACE -D_GNU_SOURCE -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
> -I/<>/thirdparty/khronos -I/<>/compat 
> -I/<>/thirdparty/brotli/c/include -I/usr/src/gtest/include 
> -I/<>/lib/trace -I/<>/lib/os 
> -I/<>/retrace -I/<>/lib/highlight 
> -I/<>/helpers -I/<>/obj-x86_64-linux-gnu/dispatch 
> -I/<>/dispatch -I/<>/lib/image 
> -I/<>/lib/ubjson -I/<>/thirdparty/dxerr 
> -I/<>/thirdparty/mhook/mhook-lib -I/usr/include/waffle-1  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -std=gnu++11 -Wall -Wno-sign-compare -fno-strict-aliasing -fno-rtti 
> -fno-exceptions -fmessage-length=0 -fno-omit-frame-pointer   -o 
> CMakeFiles/glretrace.dir/glws_xlib.cpp.o -c 
> /<>/retrace/glws_xlib.cpp
> cd /<>/obj-x86_64-linux-gnu/retrace && /usr/bin/c++  
> -DGTEST_HAS_TR1_TUPLE=0 -DHAVE_BACKTRACE=1 -DHAVE_READPROC_H -DHAVE_X11 
> -DRETRACE -D_GNU_SOURCE -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
> -I/<>/thirdparty/khronos -I/<>/compat 
> -I/<>/thirdparty/brotli/c/include -I/usr/src/gtest/include 
> -I/<>/lib/trace -I/<>/lib/os 
> -I/<>/retrace -I/<>/lib/highlight 
> -I/<>/helpers -I/<>/obj-x86_64-linux-gnu/dispatch 
> -I/<>/dispatch -I/<>/lib/image 
> -I/<>/lib/ubjson -I/<>/thirdparty/dxerr 
> -I/<>/thirdparty/mhook/mhook-lib -I/usr/include/waffle-1  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -std=gnu++11 -Wall -Wno-sign-compare -fno-strict-aliasing -fno-rtti 
> -fno-exceptions -fmessage-length=0 -fno-omit-frame-pointer   -o 
> CMakeFiles/glretrace.dir/glws_glx.cpp.o -c 
> /<>/retrace/glws_glx.cpp
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> make[2]: *** [CMakeFiles/Makefile2:1075: 
> retrace/CMakeFiles/eglretrace.dir/all] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/apitrace_9.0+repack-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate 

Bug#951494: marked as done (libprocps-dev: dead symlink point to the old soname)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 05:34:44 +
with message-id 
and subject line Bug#951494: fixed in procps 2:3.3.16-2
has caused the Debian Bug report #951494,
regarding libprocps-dev: dead symlink point to the old soname
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.)


-- 
951494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 2:3.3.15-2+b1
Severity: grave
Justification: renders package unusable

The libprocps.so symlink in libprocps-dev points to:
/usr/lib/x86_64-linux-gnu/libprocps.so -> /lib/x86_64-linux-gnu/libprocps.so.7

However libprocps.so.7 is gone and has been replaced by libprocps.so.8.

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: procps
Source-Version: 2:3.3.16-2
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated procps 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, 25 Feb 2020 08:08:40 +1100
Source: procps
Architecture: source
Version: 2:3.3.16-2
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 951335 951494
Changes:
 procps (2:3.3.16-2) unstable; urgency=medium
 .
   * Fix symlink to new soname Closes: #951494
   * top: restore configuration file backward compatibility Closes:
 #951335
   * put remaining binaries in /bin in Linux under /usr/bin
Checksums-Sha1:
 95413f29e17928aa289fdbd5a2c036c92d65ffca 2104 procps_3.3.16-2.dsc
 8630f58c186b6e52752fb7c8754f9fa912f6e383 29044 procps_3.3.16-2.debian.tar.xz
 0976763e739ecd08060b10ddf624793148598eb6 6981 procps_3.3.16-2_amd64.buildinfo
Checksums-Sha256:
 7a5b67f76bc6121e15255753b40ad09ce4c37cc5ec4d80ced88a3dd77269102a 2104 
procps_3.3.16-2.dsc
 187262259daf92e7aeb55888113b83e77636d794c26ca1f4f215fd28347547f8 29044 
procps_3.3.16-2.debian.tar.xz
 1b578eea1a52a879de301c70da4af52f6aecfd58351af091fe1308608fc8142f 6981 
procps_3.3.16-2_amd64.buildinfo
Files:
 04aa94f712a9e27058521994403fa203 2104 admin optional procps_3.3.16-2.dsc
 79d93e3c4de6e58ad0c4c3d340926f38 29044 admin optional 
procps_3.3.16-2.debian.tar.xz
 8b0288b7d51faa4cbebe0127341032c7 6981 admin optional 
procps_3.3.16-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl5UO9UACgkQAiFmwP88
hOOPsw//fmQB9JcXo7/4VjPAJ/iLNP6FWO0KXxjmylXh7fAvUXow4axHeChnhk0W
YdkLQIYf6Meh0KBl9QQMm+xCXmiKaBXQwcGvNJvjBi382yNaTYGiqJ9nEMvCrXAU
GubDKu3l9gIGKUgykYzC2HjMkF4+fGYxadKTup4sspwVEKGl38+i6gkkmY1c8OD0
didRvQWTXqurps11lL3JgakrCSS4UOHVdBCwiZVILkdVCAehmbbQ5SFfSeAem8jv
nKoEO4TLAC3bnNOqeaGJQv9/YHzdC478cT50y5vhJMGbztOptgfnft3mqypUMmS2
MpzzC+ek/najisS7R93Yfbt4SVR8eWI4fExLm+o/+BKoTf9bsT5W7LjymfNqPALH
NuRwWg0dzwvABgDFv7aLgkueJdWFacC9YGzZC9VnAjxaBE6Y2mqNfOmyUzuvfrEW
rcwmf8NJoBjEokDbzFTZDFkXD5bqPqsobWmblcyx4ZNVf+R+EEniegfllMzyBifG
A4I4c7WKkSrjnkfFpiwXQHPXRZ9xtyAw8NYn/DU5eI8ZikaLQS7i7INYFqZbjAgQ
2bs5veQ66vH64JYJFyQbIByKdh//evwuo+LcxaHACacz6kKkSXhVtLyIZDxbvtTM
3my9BLI+FXCgUUefdRngKgWEqXG7liByAg2Jm/u15QGxWHb86jo=
=LCLR
-END PGP SIGNATURE End Message ---

Bug#952169: libmodule-starter-plugin-cgiapp-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 1

[Jaldhar H. Vyas]

On Sun, 23 Feb 2020, Lucas Nussbaum wrote:


Hi,

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



Hi Lucas, because I have been long in responding, I just wanted to drop a 
quick note that I acknowledge your bug report.  I need to do an upstream 
release to fix all the issues and I will try and do this ASAP.


--
Jaldhar H. Vyas 

Bug#952426: marked as done (digikam: digkam experimental not correctly instalable)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 20:12:42 -0600
with message-id <1732700.63rbP3Mbes@riemann>
and subject line Re: Bug#952426: digikam: digkam experimental not correctly 
instalable
has caused the Debian Bug report #952426,
regarding digikam: digkam experimental not correctly instalable
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.)


-- 
952426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:7.0.0~beta2+dfsg-1
Severity: grave
Justification: renders package unusable

 digikam 
digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot 
open shared object file: No such file or directory

Has already been reported.

But in addition,

LANG="C" apt-get -t experimental install  libhdf5-hl-100
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libhdf5-hl-100 : Depends: libhdf5-103-1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
tri-yann4:~#  LANG="C" apt-get -t experimental install  libhdf5-hl-100 
libhdf5-103-1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dvgrab libarmadillo9 libarpack2 libavresample4 libcharls2 libdap25 
libdapclient6v5 libepsilon1 libfyba0
  libgdcm3.0 libgeotiff5 libhdf4-0-alt libkmlbase1 libkmldom1 libkmlengine1 
libmlt-data libmovit8 libodbc1
  libogdi4.1 libqhull7 libqtav1 libqtavwidgets1 librtaudio6 librttr-core0.9.6 
libsocket++1 libsuperlu5 odbcinst
  odbcinst1debian2
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  digikam digikam-private-libs enblend enfuse hugin hugin-tools kdenlive 
libgdal26 libhdf5-103 libmlt++3 libmlt6
  libnetcdf-c++4 libnetcdf15 libopencv-calib3d4.2 libopencv-contrib4.2 
libopencv-features2d4.2
  libopencv-highgui4.2 libopencv-imgcodecs4.2 libopencv-objdetect4.2 
libopencv-shape4.2 libopencv-stitching4.2
  libopencv-superres4.2 libopencv-video4.2 libopencv-videoio4.2 
libopencv-videostab4.2 libopencv-viz4.2
  libvigraimpex11 libvtk6.3 melt showfoto
The following NEW packages will be installed:
  libhdf5-103-1 libhdf5-hl-100
0 upgraded, 2 newly installed, 30 to remove and 67 not upgraded.
Need to get 1265 kB of archives.
After this operation, 212 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.



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

Kernel: Linux 5.4.21 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages digikam depends on:
ii  digikam-data  4:7.0.0~beta2+dfsg-1
ii  digikam-private-libs  4:7.0.0~beta2+dfsg-1
ii  libc6 2.30-0experimental2
ii  libgcc-s1 10-20200222-1
ii  libkf5configcore5 5.62.0-1+b1
ii  libkf5coreaddons5 5.62.0-1
ii  libkf5i18n5   5.62.0-1
ii  libmagick++-6.q16-8   8:6.9.10.23+dfsg-2.1+b2
ii  libqt5core5a  5.12.5+dfsg-8
ii  libqt5gui55.12.5+dfsg-8
ii  libqt5sql55.12.5+dfsg-8
ii  libqt5sql5-mysql  5.12.5+dfsg-8
ii  libqt5sql5-sqlite 5.12.5+dfsg-8
ii  libqt5widgets55.12.5+dfsg-8
ii  libstdc++610-20200222-1
ii  perl  5.30.1~rc1-1

Versions of packages digikam recommends:
ii  ffmpegthumbs4:19.12.2-1
ii  firefox-esr [www-browser]   68.5.0esr-1+b1
ii  google-chrome-stable [www-browser]  80.0.3987.116-1
ii  links2 [www-browser]2.20.2-1+b1
ii  lynx [www-browser]  2.9.0dev.4-1
ii  w3m [www-browser]   0.5.3-37+b1

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:5.17.5-2

-- no debconf information
--- End Message ---
--- Begin Message ---
On Tuesday, February 25, 2020 2:35:30 A.M. CST Eric Valette wrote:
> On 25/02/2020 02:37, Steven Robbins 

Bug#951302: timeshift: /mnt is used programmatically

[Steve Meliza]

The Timeshift author has informed me that he will fix this bug in an
upstream release before the end of March.

Bug#888675: nudging...

[Jonas Smedegaard]

Nudging this closed bug (again) to avoid auto-kicking from testing

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

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

signature.asc
Description: signature

Bug#952033: marked as done (ruby-fog-aliyun: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 01:10:00 +
with message-id 
and subject line Bug#952033: fixed in ruby-fog-aliyun 0.3.2-4
has caused the Debian Bug report #952033,
regarding ruby-fog-aliyun: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:
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.)


-- 
952033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fog-aliyun
Version: 0.3.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  NoMethodError:
>undefined method `expect' for 
> #
>Did you mean?  exec
>  # ./spec/fog/aliyun_spec.rb:11:in `block (2 levels) in '
> 
> Finished in 0.00111 seconds (files took 0.22475 seconds to load)
> 2 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/fog/aliyun_spec.rb:6 # Fog::Aliyun has a version number
> rspec ./spec/fog/aliyun_spec.rb:10 # Fog::Aliyun does something useful
> 
> /usr/bin/ruby2.5 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.5" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-fog-aliyun_0.3.2-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-fog-aliyun
Source-Version: 0.3.2-4
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-fog-aliyun 
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, 26 Feb 2020 00:07:37 +0100
Source: ruby-fog-aliyun
Architecture: source
Version: 0.3.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 952033
Changes:
 ruby-fog-aliyun (0.3.2-4) unstable; urgency=medium
 .
   * Team upload.
   * d/compat: Remove obsolete file.
   * d/control: Add Rules-Requires-Root field.
 (Build-Depends): Use debhelper-compat version 12, depend on ruby-rspec to
 fix the FTBFS (closes: #952033), and remove useless version information.
 (Standards-Version): Bump to 4.5.0.
 (Depends): Use ${ruby:Depends} and remove interpreter.
   * d/ruby-tests.rake: Minor update.
   * d/upstream/metadata: Add metadata.
Checksums-Sha1:
 d5c1cfd26ef0bb79f5399761ae3ac8d6b5157938 2190 ruby-fog-aliyun_0.3.2-4.dsc
 5231b916efee310851834a7ee431b42e1f036020 3008 
ruby-fog-aliyun_0.3.2-4.debian.tar.xz
 2a34aabd6cbd7ec57f12a15a44aa66333c8c3973 9406 
ruby-fog-aliyun_0.3.2-4_amd64.buildinfo
Checksums-Sha256:
 2ef7aff5eaebb990016b4d7fefb0e8d8bc9eb7d483335132525e694b34db2060 2190 
ruby-fog-aliyun_0.3.2-4.dsc
 04a6756ca3b33d4997f81b23b6a1a62fa9e69dcd4c73c7b6e6e122b2bbfda877 3008 
ruby-fog-aliyun_0.3.2-4.debian.tar.xz
 a788f37129b78dd6635a9b76e439977c39d3fc21bbe49ec5c21345584af31e8d 9406 
ruby-fog-aliyun_0.3.2-4_amd64.buildinfo
Files:
 fc3a322586ffb8321b5dd084e4ccb088 2190 ruby optional ruby-fog-aliyun_0.3.2-4.dsc
 2812e032ffc5e364a9d64f7389cc24fa 3008 ruby optional 
ruby-fog-aliyun_0.3.2-4.debian.tar.xz
 cc26a3026dc3dc0dd14be7fb34f72a6c 9406 ruby optional 
ruby-fog-aliyun_0.3.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5VvS4ACgkQS80FZ8KW
0F3SkRAAn0W7WOlfRVwO9RbtgI2mZyqeRs6TznxqA63cEC/RxQJO+nMLevuL/aW6

Bug#952028: marked as done (gist: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: subject.filename.should be filename)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 01:08:43 +
with message-id 
and subject line Bug#952028: fixed in gist 5.0.0-4
has caused the Debian Bug report #952028,
regarding gist: FTBFS: ERROR: Test "ruby2.7" failed:  Failure/Error: 
subject.filename.should be filename
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.)


-- 
952028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gist
Version: 5.0.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  Failure/Error: subject.filename.should be filename
> 
>  NameError:
>uninitialized constant RSpec::Support::Differ
>  # ./spec/auth_token_file_spec.rb:26:in `block (4 levels) in  (required)>'
> 
> Finished in 0.06116 seconds (files took 0.78733 seconds to load)
> 25 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/auth_token_file_spec.rb:12 # Gist::AuthTokenFile::filename with 
> default GITHUB_URL is ~/.gist
> rspec ./spec/auth_token_file_spec.rb:24 # Gist::AuthTokenFile::filename with 
> custom GITHUB_URL is ~/.gist.{custom_github_url}
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/gist_5.0.0-3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated gist 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, 26 Feb 2020 01:35:35 +0100
Source: gist
Architecture: source
Version: 5.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 952028
Changes:
 gist (5.0.0-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Repository, Repository-
 Browse, Bug-Submit.
 .
   [ Daniel Leidert ]
   * d/control: Add Rules-Requires-Root field.
 (Standards-Version): Bump to 4.5.0.
 (Depends): Add ${ruby:Depends} and remove interpreter.
   * d/patches/mochafix: Add patch.
 - Fix tests mocks (closes: #952028).
   * d/patches/series: Add new patch.
Checksums-Sha1:
 7e8d2e1ad8746d5fdc1f8fd5e83b4819ea581037 1976 gist_5.0.0-4.dsc
 c53ed7fc6fb55b7bd3677b565f315c5353f553c8 6676 gist_5.0.0-4.debian.tar.xz
 5d74aaf9d6a0fda9f56e257f415c980b02c48dbc 10087 gist_5.0.0-4_amd64.buildinfo
Checksums-Sha256:
 65a856ca5e56b4016d9518a1d826bd6472e9bbbd0c8d504f6248377ec096ede4 1976 
gist_5.0.0-4.dsc
 966229fb27c360dac2a8a7d54ae66a5e36873d94e7ab28d29ef20719e6807bbd 6676 
gist_5.0.0-4.debian.tar.xz
 37b67fdb076542655e79c6ab69cbe9247a0ff6a26ec1e85f254c8e799301bf47 10087 
gist_5.0.0-4_amd64.buildinfo
Files:
 001388e1400b6fcde078745f33c7d289 1976 net optional gist_5.0.0-4.dsc
 fa5028fab65b3653edc4598d0ce1f716 6676 net optional gist_5.0.0-4.debian.tar.xz
 1117b4fcb9eda0270b2efe2184c64747 10087 net optional 
gist_5.0.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5Vv1QACgkQS80FZ8KW
0F27WhAAyvyOzhGXet34Tm84C4I7b0KZ1pVyvmrtYWUPJevixhDrnSfvRKGMGvST

Bug#950092: marked as done (node-base64url FTBFS: error TS2688: Cannot find type definition file for 'node')

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 01:09:15 +
with message-id 
and subject line Bug#950092: fixed in node-base64url 3.0.1-3
has caused the Debian Bug report #950092,
regarding node-base64url FTBFS: error TS2688: Cannot find type definition file 
for 'node'
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.)


-- 
950092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-base64url
Version: 3.0.1-2
Severity: serious
Tags: ftbfs bullseye sid

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-base64url-3.0.1'
pandoc --from gfm-raw_html --to html --standalone --output readme.html readme.md
[WARNING] This document format requires a nonempty  element.
  Please specify either 'title' or 'pagetitle' in the metadata,
  e.g. by using --metadata pagetitle="..." on the command line.
  Falling back to 'readme'
pandoc --from gfm-raw_html --to plain --output readme.txt readme.md
tsc
error TS2688: Cannot find type definition file for 'node'.
src/base64url.ts(35,22): error TS4067: Parameter 'input' of call signature from 
exported interface has or is using private name 'Buffer'.
src/base64url.ts(36,28): error TS4075: Parameter 'input' of method from 
exported interface has or is using private name 'Buffer'.
src/base64url.ts(38,34): error TS4075: Parameter 'base64url' of method from 
exported interface has or is using private name 'Buffer'.
src/base64url.ts(40,34): error TS4057: Return type of method from exported 
interface has or is using private name 'Buffer'.
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: node-base64url
Source-Version: 3.0.1-3
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-base64url 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, 26 Feb 2020 02:02:00 +0100
Source: node-base64url
Architecture: source
Version: 3.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 950092
Changes:
 node-base64url (3.0.1-3) unstable; urgency=medium
 .
   * update watch file:
 + rewrite usage comment
 + simplify regular expressions
   * mark binary package as Multi-Arch: foreign
   * declare compliance with Debian Policy 4.5.0
   * update debhelper;
 build-depend on debhelper-compat (not debhelper)
   * extend patch 2001 to cover types below /usr/share;
 closes: bug#950092, thanks to Xavier
   * mark autopkgtest as superficial
   * add patch 1001 to fix adjust type string -> BufferEncoding;
 tighten build-dependency on node-typescript-types
   * install below /usr/share
Checksums-Sha1:
 f3efbe7e33a699a5bbf91d0c73c7e60ae76c4daa 2105 node-base64url_3.0.1-3.dsc
 53371c2e7b27b378ae291b30714334059aa7f9d8 4196 
node-base64url_3.0.1-3.debian.tar.xz
 4bf3fc82bfbfffc8db91a5d430890e9bbb46924a 7361 
node-base64url_3.0.1-3_amd64.buildinfo
Checksums-Sha256:
 5c18dfe28f76af74130f96adaa7f2661336fa23233dcd3ecfb40aa13fd0f4546 2105 
node-base64url_3.0.1-3.dsc
 a0a87e5e49834ac8ab1926a89ed9ed0aa12a3db2c686c70b60629512d4575d9d 4196 
node-base64url_3.0.1-3.debian.tar.xz
 d3a97dbf1569b94a62751fd172865e5ed1ccb23a087707f0096dcd1637475ff5 7361 
node-base64url_3.0.1-3_amd64.buildinfo
Files:
 2268fc007b4d75ade562aad30847cec5 2105 javascript optional 
node-base64url_3.0.1-3.dsc
 3fd603ad54d4ecc87b5a9d0d98edf923 4196 javascript optional 
node-base64url_3.0.1-3.debian.tar.xz
 d44a2ed5f31706e178cf0e9607445c46 7361 javascript optional 
node-base64url_3.0.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl5Vw/AACgkQLHwxRsGg
ASH1rw//UN/vW70mkaPBBpcayc25nMNQqz5t1XUXy8P60TWHYHJaOPdyWuoCjUDe

Bug#952311: marked as done (docker.io: FTBFS: dh_auto_build: error: cd .gopath && go install -trimpath -v -p 4 [...] returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 01:08:13 +
with message-id 
and subject line Bug#952311: fixed in docker.io 19.03.6+dfsg1-2
has caused the Debian Bug report #952311,
regarding docker.io: FTBFS: dh_auto_build: error: cd .gopath && go install 
-trimpath -v -p 4 [...] 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.)


-- 
952311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docker.io
Version: 19.03.6+dfsg1-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[1]: Entering directory '/<>'
> DH_GOLANG_BUILDPKG="github.com/docker/distribution"dh_auto_build -v
>   cd .gopath && go version
> go version go1.13.8 linux/amd64
>   cd .gopath && go env
> GO111MODULE="off"
> GOARCH="amd64"
> GOBIN=""
> GOCACHE="/<>/.gopath/go-build"
> GOENV="/<>/debian/tmp/.config/go/env"
> GOEXE=""
> GOFLAGS=""
> GOHOSTARCH="amd64"
> GOHOSTOS="linux"
> GONOPROXY=""
> GONOSUMDB=""
> GOOS="linux"
> GOPATH="/<>/.gopath"
> GOPRIVATE=""
> GOPROXY="off"
> GOROOT="/usr/lib/go-1.13"
> GOSUMDB="sum.golang.org"
> GOTMPDIR=""
> GOTOOLDIR="/usr/lib/go-1.13/pkg/tool/linux_amd64"
> GCCGO="gccgo"
> AR="ar"
> CC="gcc"
> CXX="g++"
> CGO_ENABLED="1"
> GOMOD=""
> CGO_CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security"
> CGO_CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2"
> CGO_CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security"
> CGO_FFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong"
> CGO_LDFLAGS="-Wl,-z,relro"
> PKG_CONFIG="pkg-config"
> GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 
> -fdebug-prefix-map=/tmp/go-build702919615=/tmp/go-build 
> -gno-record-gcc-switches"
>   cd .gopath && go generate -v github.com/docker/distribution
> src/github.com/docker/distribution/blobs.go
> src/github.com/docker/distribution/doc.go
> src/github.com/docker/distribution/errors.go
> src/github.com/docker/distribution/manifests.go
> src/github.com/docker/distribution/registry.go
> src/github.com/docker/distribution/tags.go
>   cd .gopath && go install -trimpath -v -p 4 
> github.com/docker/distribution
> runtime/internal/sys
> internal/race
> internal/cpu
> runtime/internal/atomic
> runtime/internal/math
> sync/atomic
> math/bits
> internal/bytealg
> unicode/utf8
> math
> unicode
> internal/testlog
> container/list
> crypto/internal/subtle
> runtime
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> runtime/cgo
> vendor/golang.org/x/crypto/internal/subtle
> vendor/golang.org/x/crypto/curve25519
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> internal/oserror
> strconv
> io
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> hash
> bytes
> reflect
> crypto
> strings
> bufio
> regexp/syntax
> path
> time
> internal/syscall/unix
> hash/crc32
> crypto/internal/randutil
> regexp
> crypto/hmac
> context
> internal/poll
> crypto/rc4
> internal/fmtsort
> encoding/binary
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> os
> encoding/base64
> crypto/cipher
> crypto/sha512
> crypto/ed25519/internal/edwards25519
> crypto/aes
> crypto/des
> fmt
> crypto/md5
> crypto/sha1
> crypto/sha256
> encoding/pem
> path/filepath
> net
> github.com/opencontainers/go-digest
> github.com/opencontainers/image-spec/specs-go
> mime
> compress/flate
> github.com/docker/distribution/digestset
> github.com/docker/distribution/reference
> github.com/opencontainers/image-spec/specs-go/v1
> compress/gzip
> math/big
> encoding/hex
> io/ioutil
> net/url
> vendor/golang.org/x/crypto/internal/chacha20
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/sys/cpu
> log
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/text/unicode/bidi
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> crypto/x509/pkix
> crypto/ecdsa
> vendor/golang.org/x/crypto/cryptobyte
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> mime/quotedprintable
> net/http/internal
> vendor/golang.org/x/net/idna
> vendor/golang.org/x/net/http/httpproxy
> net/textproto
> crypto/x509
> vendor/golang.org/x/net/http/httpguts
> mime/multipart
> crypto/tls
> net/http/httptrace
> net/http
> 

Processed: your mail

[Debian Bug Tracking System]

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

> block 944496 by 952542
Bug #944496 [src:xfonts-efont-unicode] FTBFS: Assigning non-zero to $[ is no 
longer possible at tools/hex2bdf
944496 was not blocked by any bugs.
944496 was not blocking any bugs.
Added blocking bug(s) of 944496: 952542
> thanks
Stopping processing here.

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

Bug#951951: marked as done (gzip: FTBFS: stdio.h:366: undefined reference to `__chk_fail')

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 00:35:02 +
with message-id 
and subject line Bug#951951: fixed in gzip 1.10-1
has caused the Debian Bug report #951951,
regarding gzip: FTBFS: stdio.h:366: undefined reference to `__chk_fail'
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.)


-- 
951951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gzip
Version: 1.9-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/builddir-indep'
>   CC   bits.o
>   CC   deflate.o
>   CC   gzip.o
>   CC   inflate.o
>   CC   lzw.o
>   CC   trees.o
>   CC   unlzh.o
>   CC   unlzw.o
>   CC   unpack.o
>   CC   unzip.o
>   CC   util.o
>   CC   zip.o
>   CC   version.o
>   AR   libver.a
>   CCLD gzip.exe
> /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcpy':
> /usr/share/mingw-w64/include/string.h:228: undefined reference to 
> `__memcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: 
> undefined reference to `__strcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: 
> undefined reference to `__memcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: 
> undefined reference to `__stpcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcat':
> /usr/share/mingw-w64/include/string.h:234: undefined reference to 
> `__memcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcpy':
> /usr/share/mingw-w64/include/string.h:228: undefined reference to 
> `__strcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:228: 
> undefined reference to `__stpcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcat':
> /usr/share/mingw-w64/include/string.h:234: undefined reference to 
> `__strcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: /usr/share/mingw-w64/include/string.h:234: 
> undefined reference to `__strcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: gzip.o: in function `strcpy':
> /usr/share/mingw-w64/include/string.h:228: undefined reference to 
> `__memcpy_chk'
> /usr/bin/i686-w64-mingw32-ld: lib/libgzip.a(openat-proc.o): in function 
> `sprintf':
> /usr/share/mingw-w64/include/stdio.h:366: undefined reference to `__chk_fail'
> /usr/bin/i686-w64-mingw32-ld: lib/libgzip.a(vasnprintf.o): in function 
> `sprintf':
> /usr/share/mingw-w64/include/stdio.h:366: undefined reference to `__chk_fail'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/gzip_1.9-3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated gzip 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, 25 Feb 2020 14:56:28 -0700
Source: gzip
Architecture: source
Version: 1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Bdale Garbee 
Closes: 881895 925554 951951
Changes:
 gzip (1.10-1) unstable; urgency=medium
 .
   * new upstream version, closes: #925554
   * explicitly link -lssp when building with mingw, closes: #951951
   * apply suggestions from lintian and Nicolas Boulenguez, closes: #881895
Checksums-Sha1:
 ff054414fbd37820ed3a6656ebff3b1eee80a1b4 1967 gzip_1.10-1.dsc
 

Bug#952028: marked as pending in gist

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #952028 in gist 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/ruby-team/gist/-/commit/59c171a27b92bf72edc7f57548fbcbb5544cf6f9


Update packaging files and fix tests to prevent FTBFS

  * d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.5.0.
(Depends): Add ${ruby:Depends} and remove interpreter
  * d/copyright: Minor update.
  * d/patches/mochafix: Add patch.
- Fix tests mocks (closes: #952028).
  * d/patches/series: Add new patch.
  * d/patches/*: Refresh. Add DEP3 headers.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952028

Bug#950092: marked as pending in node-base64url

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #950092 in node-base64url 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/js-team/node-base64url/-/commit/374d05af5ae25b9dc65fbde72397064854a5c551


extend patch 2001 to cover types below /usr/share; closes: bug#950092, thanks 
to Xavier


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950092

Processed: Bug#952028 marked as pending in gist

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952028 [src:gist] gist: FTBFS: ERROR: Test "ruby2.7" failed:  
Failure/Error: subject.filename.should be filename
Added tag(s) pending.

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

Processed: Bug#950092 marked as pending in node-base64url

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950092 [src:node-base64url] node-base64url FTBFS: error TS2688: Cannot 
find type definition file for 'node'
Added tag(s) pending.

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

Processed: Bug#952311 marked as pending in docker.io

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952311 [src:docker.io] docker.io: FTBFS: dh_auto_build: error: cd .gopath 
&& go install -trimpath -v -p 4 [...] returned exit code 2
Added tag(s) pending.

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

Bug#952311: marked as pending in docker.io

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #952311 in docker.io 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/docker-team/docker/-/commit/e0897f72b2a60528b8fcf5f3347e746d81db3574


New upstream patch to fix FTBFS in "libnetwork" (Closes: #952311).

  * Build-Depends:
= golang-github-miekg-dns-dev (>= 1.1.26~)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952311

Bug#952244: marked as done (qtcurve: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 26 Feb 2020 00:19:47 +
with message-id 
and subject line Bug#952244: fixed in qtcurve 1.9-5
has caused the Debian Bug report #952244,
regarding qtcurve: 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.)


-- 
952244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtcurve
Version: 1.9-4
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):
>  fakeroot debian/rules binary
> dh binary --with=kf5
>dh_testroot
>dh_prep
>dh_auto_install --buildsystem=kf5
>dh_install
> dh_install: warning: Cannot find (any matches for) "usr/lib/*/gtk-2.0/*" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: gtk2-engines-qtcurve missing files: usr/lib/*/gtk-2.0/*
> dh_install: warning: Cannot find (any matches for) 
> "usr/lib/*/libqtcurve-cairo.so.*" (tried in ., debian/tmp)
> 
> dh_install: warning: gtk2-engines-qtcurve missing files: 
> usr/lib/*/libqtcurve-cairo.so.*
> dh_install: warning: Cannot find (any matches for) 
> "usr/share/themes/QtCurve/gtk-2.0/*" (tried in ., debian/tmp)
> 
> dh_install: warning: gtk2-engines-qtcurve missing files: 
> usr/share/themes/QtCurve/gtk-2.0/*
> dh_install: warning: Cannot find (any matches for) 
> "usr/share/themes/QtCurve/mozilla/*" (tried in ., debian/tmp)
> 
> dh_install: warning: gtk2-engines-qtcurve missing files: 
> usr/share/themes/QtCurve/mozilla/*
> dh_install: warning: Cannot find (any matches for) "usr/lib/*/qt5/*" (tried 
> in ., debian/tmp)
> 
> dh_install: warning: kde-style-qtcurve-qt5 missing files: usr/lib/*/qt5/*
> dh_install: warning: Cannot find (any matches for) "usr/share/kstyle/*" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: kde-style-qtcurve-qt5 missing files: usr/share/kstyle/*
> dh_install: warning: Cannot find (any matches for) "usr/share/locale/*" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: qtcurve-l10n missing files: usr/share/locale/*
> dh_install: warning: Cannot find (any matches for) 
> "usr/lib/*/libqtcurve-utils.so.*" (tried in ., debian/tmp)
> 
> dh_install: warning: libqtcurve-utils2 missing files: 
> usr/lib/*/libqtcurve-utils.so.*
> dh_install: error: missing files, aborting
> make: *** [debian/rules:16: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/qtcurve_1.9-4_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: qtcurve
Source-Version: 1.9-5
Done: Boris Pek 

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

Debian distribution maintenance software
pp.
Boris Pek  (supplier of updated qtcurve 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, 26 Feb 2020 02:56:14 +0300
Source: qtcurve
Architecture: source
Version: 1.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Boris Pek 
Closes: 952244
Changes:
 qtcurve (1.9-5) unstable; urgency=medium
 .
   [ Sven Mueller ]
   * Add build dependency on libx11-xcb-dev. (Closes: #952244)
 .
   [ Boris Pek ]
   * Update debian/control:
 - bump Standards-Version to 4.5.0 (was 4.4.1): no changes required
 - replace build dependency from debhelper (>= 12~) to
   debhelper-compat (= 12)
 - add "Rules-Requires-Root: no"
   * Update years in debian/copyright.
   * Delete debian/compat.
Checksums-Sha1:
 3e8fe9a80382cff9ca0795727b2def56d4ac7913 2567 qtcurve_1.9-5.dsc
 5543d7b622fedc98e3999d2d9e649db71f380572 

Bug#952545: marked as done (irssi-scripts: Duplicate usercount.pl conflict with irssi)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 23:35:19 +
with message-id 
and subject line Bug#952545: fixed in irssi-scripts 20200223
has caused the Debian Bug report #952545,
regarding irssi-scripts: Duplicate usercount.pl conflict with irssi
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.)


-- 
952545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: irssi-scripts
Version: 20200222
Severity: important

Dear Maintainer,

On upgrading fails and collides with irssi package:

Preparing to unpack .../irssi-scripts_20200222_all.deb ...
Unpacking irssi-scripts (20200222) over (20181120) ...
dpkg: error processing archive 
/var/cache/apt/archives/irssi-scripts_20200222_all.deb (--unpack):
 trying to overwrite '/usr/share/irssi/scripts/usercount.pl', which is also in 
package irssi 1.2.2-1+b1
Errors were encountered while processing:
 /var/cache/apt/archives/irssi-scripts_20200222_all.deb

Greetings,
Haegar

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

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

Versions of packages irssi-scripts depends on:
ii  irssi  1.2.2-1+b1
ii  perl   5.30.0-9

Versions of packages irssi-scripts recommends:
ii  libwww-perl 6.43-1
ii  sensible-utils  0.0.12+nmu1

Versions of packages irssi-scripts suggests:
ii  chromium [www-browser]80.0.3987.116-1
ii  firefox-esr [www-browser] 68.5.0esr-1+b1
ii  google-chrome-beta [www-browser]  81.0.4044.26-1
ii  konqueror [www-browser]   4:19.08.2-2+b1
ii  libdbi-perl   1.643-1
ii  lynx [www-browser]2.9.0dev.4-1
ii  net-tools 1.60+git20180626.aebd88e-1
ii  uzbl [www-browser]0.0.0~git.20120514-1.2
ii  w3m [www-browser] 0.5.3-37+b1

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: irssi-scripts
Source-Version: 20200223
Done: Daniel Echeverry 

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

Debian distribution maintenance software
pp.
Daniel Echeverry  (supplier of updated irssi-scripts 
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, 25 Feb 2020 17:58:35 -0500
Source: irssi-scripts
Architecture: source
Version: 20200223
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry 
Changed-By: Daniel Echeverry 
Closes: 952545
Changes:
 irssi-scripts (20200223) unstable; urgency=medium
 .
   * New upstream release.
+ Remove usercount.pl script. (Closes: #952545)
Checksums-Sha1:
 5ffaaed7ef9554e9eb982a29c5339fc94fd94263 1686 irssi-scripts_20200223.dsc
 7060510d69b4f6ce86e957ceb550390faad02cc3 647812 irssi-scripts_20200223.tar.xz
 d42da0da7c60ba4815cc64fb59dad4efa880cf05 6045 
irssi-scripts_20200223_source.buildinfo
Checksums-Sha256:
 ec61428af75c0499e7ea87ccc0d0bbc51ba2aa0a35e64ff4b20e2a395e41e4c9 1686 
irssi-scripts_20200223.dsc
 35e2563dff3116c83fc5d9e59d40bbce6ddf40242ac5cc9e8eac30f24bb5338c 647812 
irssi-scripts_20200223.tar.xz
 bdc404dc3de305dce1ca1d1873e60d9b67ed722dc985381bd89309e641b67d11 6045 
irssi-scripts_20200223_source.buildinfo
Files:
 e4b93a3cb68982d8b1a6290de2acdc76 1686 net optional irssi-scripts_20200223.dsc
 d5d8efd0f6c03d627c8578a018010b6c 647812 net optional 
irssi-scripts_20200223.tar.xz
 6f42e7ffda2e118a3736238dff889140 6045 net optional 
irssi-scripts_20200223_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAl5Vq8QTHGVwc2lsb25A
ZGViaWFuLm9yZwAKCRAh/ClQS1Iw258lD/9cbI3Fihl1Yx1On0dIav1YBgLoSG1k

Bug#952399: OpenSSL linking without license exception

[Bastian Germann]

Am 25.02.20 um 23:38 schrieb Marco d'Itri:
> Control: found 26+20191223-1
>
> On Feb 23, Bastian Germann  wrote:
>
>> All of the GPL-2+ licensed executables contained in the kmod
>> binary package link to libcrypto even though they do not have any
>> OpenSSL license exception. ftp-master considers this a serious
>> issue. So please remove this optional dependency or ask upstream
>> for a license exception.
> The large number of contributors to kmod obviously makes impossible
>  getting a license exception, also considering that only Debian
> cares about linking GPL'ed software with OpenSSL.
>
> Since only libkmod (which is LGPL'ed), and not the actual commands,
> is linked with OpenSSL, and the libkmod symbols do not change
> depending if OpenSSL support is enabled or not, and the patches
> which introduced OpenSSL support did not touch the commands, then I
> think that the commands are obviously not a derivative work of
> OpenSSL. You can also easily verify that the commands are not
> linked with OpenSSL by looking at the build logs of the package.

$ ldd /bin/*mod /sbin/*mod*

/bin/kmod:
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/bin/lsmod:
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/sbin/depmod
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/sbin/insmod:
libcrypto.so.1.1 =>
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1/sbin/lsmod:
libcrypto.so.1.1 =>
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1/sbin/modinfo:
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/sbin/modprobe:
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/sbin/rmmod:
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1

buster's amd64 binaries are actually directly linked with libcrypto;
readelf says "(NEEDED)  Shared library: [libcrypto.so.1.1]"

Even if they were linked with libcrypto via libkmod it would not make
any difference.

> Also, the next major release of OpenSSL will be relicensed with the
>  ASLv2 anyway, which is compatible with the GPLv3.

That will help for bullseye+ but not for buster.

> For these reasons I have no interest and no plans to do anything
> about this, and I am quite annoyed that I had to spend my time
> researching these details and then explaining them to you.

You don't care and I am fine with that since I am not the maintainer
of the package. But I wanted to report the issue anyway since the
legal team's comments on that matter are unanimous.

Bug#952546: marked as done (pydoctor: d/copyright & DFSG issues)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 23:19:02 +
with message-id 
and subject line Bug#952546: fixed in pydoctor 19.11.0+git20200114.c74016b-2
has caused the Debian Bug report #952546,
regarding pydoctor: d/copyright & DFSG issues
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.)


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

Hello,

There is an embedded copy of (some of?) epydoc with copyright holders
not mentioned in d/copyright.

There does not seem to be source code for templates/bootstrap.min.css.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pydoctor
Source-Version: 19.11.0+git20200114.c74016b-2
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated pydoctor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Feb 2020 16:00:02 -0700
Source: pydoctor
Architecture: source
Version: 19.11.0+git20200114.c74016b-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Anthony Fok 
Closes: 952546
Changes:
 pydoctor (19.11.0+git20200114.c74016b-2) unstable; urgency=medium
 .
   * Remove empty debian/patches/series file
   * Add missing embedded epydoc and Bootstrap copyright info
 as well as non-minified source for bootstrap.min.css (Bootstrap v3.3.4)
 for DFSG compliance.  Special thanks to Sean Whitton for the report.
 (Closes: #952546)
   * Also expand pydoctor copyright info:
  - Update Michael Hudson’s name to Michael Hudson-Doyle
  - Add Maarten ter Huurne
   * Fix empty package by adding debian/pydoctor.install
   * Symlink to bootstrap.min.css from libjs-bootstrap instead of shipping
 pydoctor included bootstrap.min.css v3.3.4 from 2015
   * Add debian/clean to remove pydoctor.egg-info/
   * Add myself to the list of Uploaders and to debian/copyright
Checksums-Sha1:
 d4822b1c817aa0da6d354295ae7a169e3f31fe53 2261 
pydoctor_19.11.0+git20200114.c74016b-2.dsc
 0c9426bcfd9e2c12504d2dd38482dc394f3ca4a1 24656 
pydoctor_19.11.0+git20200114.c74016b-2.debian.tar.xz
 2b6a2e5565cee259b48fd3f6945342eee3068a86 6972 
pydoctor_19.11.0+git20200114.c74016b-2_amd64.buildinfo
Checksums-Sha256:
 646164d29037c8883c5107fd3e5ab515a43f6bfc6554a44b8a815e63695f2890 2261 
pydoctor_19.11.0+git20200114.c74016b-2.dsc
 2c18bb458cdc1973af31429ac000c112ee679d406fb15398efb92c3f35571f9e 24656 
pydoctor_19.11.0+git20200114.c74016b-2.debian.tar.xz
 40196415d76a3df4eca25bd4bd7c1981d85c30173ff2b0dee8a33dfbb2fa187c 6972 
pydoctor_19.11.0+git20200114.c74016b-2_amd64.buildinfo
Files:
 52af5dd56db36c8a8e3c21957d18816e 2261 python optional 
pydoctor_19.11.0+git20200114.c74016b-2.dsc
 c6e93b3cdad010403fafa2b1081cf7d8 24656 python optional 
pydoctor_19.11.0+git20200114.c74016b-2.debian.tar.xz
 860085a022079a08ec7e4f79b9179e59 6972 python optional 
pydoctor_19.11.0+git20200114.c74016b-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl5VqDMACgkQ6iUAtBLF
ms9ymxAArWa4Vu2oZEMQpwwuxOTeda6JZiUl3UKgyXevfDkzDYOnuCZMQJBtp2Bc
E3HbC0FaT9tV+5SsQcXuJS6icCNe+D6UDTSpFCiTTiXJanzx48bfDiErx7hlUDEM
yLG5jKnrM0f2M+aeibSIYhCg8ccRLhLxQtpOPevu2bqF+X/ig36pC8CcotKWr9qq
XJqhmukYTupGqYg57FcgcJYinIwRW5u1/XuqtmgWlt65sHWumBPW0cGADRKmS/PZ
rXC5TVGfAVAYiSNh3eG8nY7Mofyfih7Si85RVrnqxyALpYuqchCs+SIcssgitRT0
nVEL726ginRtH5Chd2dfyCNBlA7kBd1OC0WrH71p9fTaMYNsq6l+1vFXJW/n+tGE
y8v7v8HvTwzgTpEW4KlXWyQ+0Xgg/aF8t1H8mk/C8TY4OEpeHpG0z2YhYAXpoL/N
rHbEdCoNnnBq/mnidx0ZG3iPA5e8bDXiVNFrKeUSpRvvPV1tBWsdAtozsYmAbTaw
u6RZPJk491sua15fEECSZZOPogoBoe75nMR7aPlZdns7dOD5OpXtuuUZrglsOkpw
jRQV+F2zuZ/SviTjQNEB7Tw+lm60vJrqAfiUhLxdAI7TCKf30KhZaR68dbubuCrZ
/JttZoue+Dwa8wkNzwjfIty4oMrOp+slhYPvAcxFyL7WyCw67AU=
=OxUg
-END PGP SIGNATURE End Message ---

Bug#952018: marked as done (ruby-http-accept-language: FTBFS: ERROR: Test "ruby2.5" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 23:10:49 +
with message-id 
and subject line Bug#952018: fixed in ruby-http-accept-language 2.1.1-3
has caused the Debian Bug report #952018,
regarding ruby-http-accept-language: FTBFS: ERROR: Test "ruby2.5" failed: 
NoMethodError:
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.)


-- 
952018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-http-accept-language
Version: 2.1.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>   NoMethodError:
> undefined method `expect' for 
> #
> Did you mean?  exec
>   # ./spec/parser_spec.rb:62:in `block (2 levels) in '
> 
> Finished in 0.01261 seconds (files took 0.12149 seconds to load)
> 18 examples, 18 failures
> 
> Failed examples:
> 
> rspec ./spec/auto_locale_spec.rb:37 # HttpAcceptLanguage::AutoLocale 
> available languages includes accept_languages take a suitable locale
> rspec ./spec/auto_locale_spec.rb:50 # HttpAcceptLanguage::AutoLocale 
> available languages do not include accept_languages set the locale to default
> rspec ./spec/auto_locale_spec.rb:65 # HttpAcceptLanguage::AutoLocale default 
> locale is ja set the locale to default
> rspec ./spec/middleware_spec.rb:31 # Rack integration handles reuse of the 
> env instance
> rspec ./spec/middleware_spec.rb:42 # Rack integration decodes the 
> HTTP_ACCEPT_LANGUAGE header
> rspec ./spec/middleware_spec.rb:47 # Rack integration finds the first 
> available language
> rspec ./spec/parser_spec.rb:9 # HttpAcceptLanguage::Parser should return 
> empty array
> rspec ./spec/parser_spec.rb:14 # HttpAcceptLanguage::Parser should properly 
> split
> rspec ./spec/parser_spec.rb:18 # HttpAcceptLanguage::Parser should ignore 
> jambled header
> rspec ./spec/parser_spec.rb:23 # HttpAcceptLanguage::Parser should properly 
> respect whitespace
> rspec ./spec/parser_spec.rb:28 # HttpAcceptLanguage::Parser should find first 
> available language
> rspec ./spec/parser_spec.rb:32 # HttpAcceptLanguage::Parser should find first 
> compatible language
> rspec ./spec/parser_spec.rb:37 # HttpAcceptLanguage::Parser should find first 
> compatible from user preferred
> rspec ./spec/parser_spec.rb:42 # HttpAcceptLanguage::Parser should accept 
> symbols as available languages
> rspec ./spec/parser_spec.rb:47 # HttpAcceptLanguage::Parser should accept and 
> ignore wildcards
> rspec ./spec/parser_spec.rb:52 # HttpAcceptLanguage::Parser should sanitize 
> available language names
> rspec ./spec/parser_spec.rb:56 # HttpAcceptLanguage::Parser should accept 
> available language names as symbols and return them as strings
> rspec ./spec/parser_spec.rb:60 # HttpAcceptLanguage::Parser should find most 
> compatible language from user preferred
> 
> /usr/bin/ruby2.5 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.5" failed: 

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/ruby-http-accept-language_2.1.1-2_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: ruby-http-accept-language
Source-Version: 2.1.1-3
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated 
ruby-http-accept-language 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 

Processed: Bug#952033 marked as pending in ruby-fog-aliyun

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952033 [src:ruby-fog-aliyun] ruby-fog-aliyun: FTBFS: ERROR: Test "ruby2.5" 
failed: NoMethodError:
Added tag(s) pending.

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

Bug#952033: marked as pending in ruby-fog-aliyun

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #952033 in ruby-fog-aliyun 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/ruby-team/ruby-fog-aliyun/-/commit/df3066b2d72a3d638b1f7bad6994f570e73b07e3


Update packaging files and fix FTBFS

  * d/compat: Remove obsolete file.
  * d/control: Add Rules-Requires-Root field.
(Build-Depends): Use debhelper-compat version 12, depend on ruby-rspec to
fix the FTBFS (closes: #952033), and remove useless version information.
(Standards-Version): Bump to 4.5.0.
(Depends): Use ${ruby:Depends} and remove interpreter.
  * d/ruby-tests.rake: Minor update.
  * d/upstream/metadata: Add metadata.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952033

Processed: Bug#952018 marked as pending in ruby-http-accept-language

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952018 [src:ruby-http-accept-language] ruby-http-accept-language: FTBFS: 
ERROR: Test "ruby2.5" failed: NoMethodError:
Added tag(s) pending.

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

Processed: found 952399 in 26+20191223-1

[Debian Bug Tracking System]

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

> found 952399 26+20191223-1
Bug #952399 [kmod] OpenSSL linking without license exception
Marked as found in versions kmod/26+20191223-1.
> thanks
Stopping processing here.

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

Bug#952018: marked as pending in ruby-http-accept-language

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #952018 in ruby-http-accept-language 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/ruby-team/ruby-http-accept-language/-/commit/298cc0e9f6c29995b3ae21009cd504c11f2913ca


Update packaging files and fix FTBFS

  * d/compat: Remove obsolete file.
  * d/control: Add Rules-Requires-Root field.
(Build-Depends): Use debhelper-compat version 12 and depend on ruby-rspec
to fix the FTBFS (closes: #952018).
(Standards-Version): Bump to 4.5.0.
(Depends): Remove interpreter.
  * d/ruby-tests.rake: Minor update.
  * d/upstream/metadata: Add metadata.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952018

Bug#952399: OpenSSL linking without license exception

[Marco d'Itri]

Control: found 26+20191223-1

On Feb 23, Bastian Germann  wrote:

> All of the GPL-2+ licensed executables contained in the kmod binary
> package link to libcrypto even though they do not have any OpenSSL
> license exception. ftp-master considers this a serious issue. So please
> remove this optional dependency or ask upstream for a license exception.
The large number of contributors to kmod obviously makes impossible 
getting a license exception, also considering that only Debian cares 
about linking GPL'ed software with OpenSSL.

Since only libkmod (which is LGPL'ed), and not the actual commands, is
linked with OpenSSL, and the libkmod symbols do not change depending if 
OpenSSL support is enabled or not, and the patches which introduced 
OpenSSL support did not touch the commands, then I think that the 
commands are obviously not a derivative work of OpenSSL.
You can also easily verify that the commands are not linked with OpenSSL 
by looking at the build logs of the package.

Also, the next major release of OpenSSL will be relicensed with the 
ASLv2 anyway, which is compatible with the GPLv3.

For these reasons I have no interest and no plans to do anything about 
this, and I am quite annoyed that I had to spend my time researching 
these details and then explaining them to you.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#952029: marked as done (ruby-mathml: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: e.rest << @scanner.rest.to_s)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 22:35:34 +
with message-id 
and subject line Bug#952029: fixed in ruby-mathml 0.14-5
has caused the Debian Bug report #952029,
regarding ruby-mathml: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: 
e.rest << @scanner.rest.to_s
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.)


-- 
952029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mathml
Version: 0.14-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>   Failure/Error: e.rest << @scanner.rest.to_s
> 
>   FrozenError:
> can't modify frozen String: ""
>   # ./lib/math_ml/latex.rb:459:in `rescue in parse_into'
>   # ./lib/math_ml/latex.rb:450:in `parse_into'
>   # ./lib/math_ml/latex.rb:392:in `parse'
>   # ./lib/math_ml/util.rb:331:in `parse_eqnarray'
>   # ./spec/math_ml/util_spec.rb:639:in `block (3 levels) in  (required)>'
>   # ./lib/math_ml/util.rb:170:in `encode'
>   # ./spec/math_ml/util_spec.rb:638:in `block (2 levels) in  (required)>'
>   # --
>   # --- Caused by: ---
>   # MathML::LaTeX::ParseError:
>   #   Need more column.
>   #   ./lib/math_ml/latex.rb:1045:in `env_array_row'
> 
> Deprecation Warnings:
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/math_ml/element_spec.rb:5:in `block (2 levels) in  (required)>'.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 1 deprecation warning total
> 
> Finished in 0.48445 seconds (files took 0.13909 seconds to load)
> 105 examples, 14 failures
> 
> Failed examples:
> 
> rspec ./spec/math_ml/latex/macro_spec.rb:27 # MathML::LaTeX::Macro #parse
> rspec ./spec/math_ml/latex/macro_spec.rb:63 # MathML::LaTeX::Macro #commands
> rspec ./spec/math_ml/latex/macro_spec.rb:69 # MathML::LaTeX::Macro 
> #expand_command
> rspec ./spec/math_ml/latex/macro_spec.rb:80 # MathML::LaTeX::Macro 
> #environments
> rspec ./spec/math_ml/latex/macro_spec.rb:87 # MathML::LaTeX::Macro 
> #expand_environment
> rspec ./spec/math_ml/latex/macro_spec.rb:99 # MathML::LaTeX::Macro 
> #expand_with_options
> rspec ./spec/math_ml/latex/parser_spec.rb:135 # MathML::LaTeX::Parser#parse 
> should process sqrt
> rspec ./spec/math_ml/latex/parser_spec.rb:214 # MathML::LaTeX::Parser#parse 
> should process array
> rspec ./spec/math_ml/latex/parser_spec.rb:380 # MathML::LaTeX::Parser#parse 
> can be used with macro
> rspec ./spec/math_ml/latex/parser_spec.rb:446 # MathML::LaTeX::Parser#parse 
> can be used with macro with option
> rspec ./spec/math_ml/latex/parser_spec.rb:484 # MathML::LaTeX::Parser#parse 
> can be used in safe mode
> rspec ./spec/math_ml/latex/scanner_spec.rb:159 # MathML::LaTeX::Scanner 
> #scan_option
> rspec ./spec/math_ml/latex/scanner_spec.rb:181 # MathML::LaTeX::Scanner 
> #check_option
> rspec ./spec/math_ml/util_spec.rb:618 # MathML::Util::SimpleLaTeX parse 
> eqnarray
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-mathml_0.14-4_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: ruby-mathml
Source-Version: 0.14-5
Done: =?utf-8?q?C=C3=A9dric_Boutillier?= 

We believe that the bug you reported is fixed in the latest version of
ruby-mathml, which is due to be installed in the Debian FTP 

Bug#950020: marked as done (meson autopkg tests failing on arm64)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 22:23:18 +
with message-id 
and subject line Bug#950020: fixed in meson 0.53.2-1
has caused the Debian Bug report #950020,
regarding meson autopkg tests failing on arm64
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.)


-- 
950020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:meson
Version: 0.53.0-1
Severity: serious
Tags: sid bullseye

meson autopkg tests failing on arm64:

https://ci.debian.net/data/autopkgtest/testing/arm64/m/meson/4117906/log.gz

==
ERROR: test_ld_environment_variable_rust (__main__.LinuxlikeTests)
--
Traceback (most recent call last):
  File "run_unittests.py", line 5897, in test_ld_environment_variable_rust
self._check_ld('ld.gold', 'gold', 'rust', 'GNU ld.gold')
  File "run_unittests.py", line 5881, in _check_ld
comp = getattr(env, 'detect_{}_compiler'.format(lang))(MachineChoice.HOST)
  File
"/tmp/autopkgtest-lxc.o9fv_b8h/downtmp/build.N45/src/mesonbuild/environment.py",
line 1411, in detect_rust_compiler
self._handle_exceptions(popen_exceptions, compilers)
  File
"/tmp/autopkgtest-lxc.o9fv_b8h/downtmp/build.N45/src/mesonbuild/environment.py",
line 733, in _handle_exceptions
raise EnvironmentException(errmsg)
mesonbuild.mesonlib.EnvironmentException: Unknown compiler(s): ['rustc']
The follow exceptions were encountered:
Running "rustc --version" gave "[Errno 2] No such file or directory: 'rustc':
'rustc'"

--
Ran 301 tests in 357.825s

FAILED (errors=1, skipped=50)
pytest-xdist not found, using unittest instead
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.53.2-1
Done: Jussi Pakkanen 

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Feb 2020 18:02:37 +0200
Source: meson
Architecture: source
Version: 0.53.2-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Closes: 950020 951487
Changes:
 meson (0.53.2-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #950020, #951487
Checksums-Sha1:
 216c31d93508ff3d791c449b8122cac31b2bbf8e 3396 meson_0.53.2-1.dsc
 ef933d8b0fd858befe35257b30c73fdef62c9e08 1557955 meson_0.53.2.orig.tar.gz
 c48e4a91fa937a4624828f9f33421993f177eb11 13240 meson_0.53.2-1.debian.tar.xz
 6ad77fbf26f927ccc550e04e5bdecb0fb176496c 5997 meson_0.53.2-1_source.buildinfo
Checksums-Sha256:
 bc2ec4ec1d496b3cf30dd6441dbd714f3c89dfec691a9e600ddc368b8b2a8ef8 3396 
meson_0.53.2-1.dsc
 3e8f830f33184397c2eb0b651ec502adb63decb28978bdc84b3558d71284c21f 1557955 
meson_0.53.2.orig.tar.gz
 27b2e5373206eef3943926f5af12206b53741a1a74bd6c03ec2fc6f1309e5072 13240 
meson_0.53.2-1.debian.tar.xz
 b0ead16dde44e36d8fea35c06839fbc4fb0e501ddca139c3aab76ecd1e0c0a4b 5997 
meson_0.53.2-1_source.buildinfo
Files:
 c5b5b33da2442ce138449d85032b22b1 3396 devel optional meson_0.53.2-1.dsc
 80303535995fcae72bdb887df102b421 1557955 devel optional 
meson_0.53.2.orig.tar.gz
 325446dfc4de09f7ac597255fa7b3ce6 13240 devel optional 
meson_0.53.2-1.debian.tar.xz
 1b689dc4ad9acb130122e5eedc6f90e2 5997 devel optional 
meson_0.53.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPbRrVe+lnUDmIyFI0U7xXa/hE0cFAl5Vk+0ACgkQ0U7xXa/h
E0c9Yw/+P4wmsqsMA4pljkuBSQaUSwTNzWiTOAhive23tL3Htjgs1oGiVk6Gl0BT
6xUHSFlZDU1N9v24GHe7Z+Ah6LQHlDiD5oLBuX+JyieiOdg1PpJ+31ifjifUBSI6
bixaeAndvLBzgLafeBILo3kepR2ootUhM6wNKE2MbOWbN6s/MIvdx1p58VrTYv+j
KANj46b+eBTl56DFHidOPW3lw32CcXyukDOIfiMwwyhu/hK114dHxgFcylwzskQl
qQau3uSBA5To25f1yoiiAQc4kRe12TKYLCnkKyk3Fi2P8tatflkty0dYc6aFc8nE
cDX51BgQUXlSawpzfeS3l+ja9iZlUywLp0Tf1EalL4fHhg2FZvU5ieC4dkGRFVdd

Processed: Re: Bug#952545: irssi-scripts: Duplicate usercount.pl conflict with irssi

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #952545 [irssi-scripts] irssi-scripts: Duplicate usercount.pl conflict with 
irssi
Severity set to 'grave' from 'important'

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

Processed: Bug#952029 marked as pending in ruby-mathml

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952029 [src:ruby-mathml] ruby-mathml: FTBFS: ERROR: Test "ruby2.7" failed: 
Failure/Error: e.rest << @scanner.rest.to_s
Added tag(s) pending.

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

Bug#952029: marked as pending in ruby-mathml

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #952029 in ruby-mathml 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/ruby-team/ruby-mathml/-/commit/ec836f39b73d10e6a30c340ad5abb8151175d041


Add patches to fix tests with ruby2.7 (Closes: #952029)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952029

Bug#902241: (no subject)

[Santiago Vila]

fixed 902241 2.6.0-2
thanks

(Marking the bug as fixed in buster)

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 902241 2.6.0-2
Bug #902241 [src:python-proliantutils] python-proliantutils: FTBFS in stretch 
(AssertionError: IloConnectionError not raised)
Marked as fixed in versions python-proliantutils/2.6.0-2.
> thanks
Stopping processing here.

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

Bug#952546: bootstrap.min.js in pydoctor

[Jonas Smedegaard]

Quoting Anthony Fok (2020-02-25 22:35:03)
> A fix to this bug is almost ready: I have expanded d/copyright to 
> include the missing epydoc and bootstrap.min.css copyright info, and 
> added debian/missing-sources/bootstrap.css (vanilla Bootstrap v3.3.4, 
> equivalent to the embedded minified version, from Bootstrap CDN).

If the package ships copy of bootstrap.min.css then I suggest to also 
strip that and symlink to the css in the libjs-bootstrap package.

 - Jonas

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

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

signature.asc
Description: signature

Bug#902241: [PKG-Openstack-devel] Bug#902241: python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not raised)

[Santiago Vila]

On Fri, 29 Jun 2018, Thomas Goirand wrote:

> Replacing the IP by 198.51.100.1, which is reserved by IETF for
> documentation (according to
> https://en.wikipedia.org/wiki/Reserved_IP_addresses) fixes the issue.

Maybe I misread Debian Policy, but I believe packages are not allowed
to even *try* Internet during build, and that's why I propose
disabling the test entirely, that should be simple and effective.

Thanks.

Bug#932197: Request to join the Neurodebian group

[Andreas Tille]

Hi,

here is some update I'm also forwarding to NeuroDebian Team list to have
some public record of the current status.

On Thu, Feb 20, 2020 at 01:36:35AM +1100, Stuart Prescott wrote:
> 
> I also looked at nipype (but its source is very odd and I can't build what is 
> in the repo; I think that was .gitattributes related but end up fixing it)

I have updated nipype in the Git repository I moved to Debian Med team[1]
The latest upstream version needs a new dependency python3-etelemetry
which I packaged and uploaded to new (see #952558)
 
I've also tried to build heudiconv in Git[2].  It builds so far but tests
accessing remote locations to download data need to be disabled.  That's
where I'm stoping for now.

Kind regards

   Andreas.

[1] https://salsa.debian.org/med-team/nipype
[2] https://salsa.debian.org/med-team/heudiconv 

-- 
http://fam-tille.de

Bug#902241: python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not raised)

[Santiago Vila]

reopen 902241
tags 902241 + patch
thanks

This bug was already diagnosed by you here:

https://bugs.launchpad.net/proliantutils/+bug/1779342

I suggest applying the patch below. I can take care of filing the bug
against release.debian.org if it helps.

(Remember that packages in stretch *must* build in stretch. Closing
bugs like this one does not help at all to comply with such promise).

Thanks.

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-proliantutils (2.1.11-2+deb9u1) stretch; urgency=medium
+
+  * Disable test which fails when there is Internet connectivity.
+Closes: #902241.
+
+ -- Thomas Goirand   Tue, 25 Feb 2020 22:20:10 +0100
+
 python-proliantutils (2.1.11-2) unstable; urgency=medium
 
   * d/s/options: extend-diff-ignore of .gitreview
--- a/proliantutils/tests/ilo/test_firmware_controller.py
+++ b/proliantutils/tests/ilo/test_firmware_controller.py
@@ -554,6 +554,7 @@ class FirmwareImageUploaderTestCase(unittest.TestCase):
   ('1.1.1.1', exception.IloConnectionError),
   ('any_kind_of_address', exception.IloConnectionError),)
 @ddt.unpack
+@unittest.skip("Test fails when there is Internet connectivity")
 def test__get_socket_throws_exception_in_case_of_failed_connection(
 self, input_hostname, expected_exception_type):
 # | GIVEN |

Processed: Re: bootstrap.min.js in pydoctor

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #952546 [src:pydoctor] pydoctor: d/copyright & DFSG issues
Added tag(s) pending.

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

Bug#952546: bootstrap.min.js in pydoctor

[Anthony Fok]

Control: tags -1 + pending

On Tue, Feb 25, 2020 at 12:06 PM Colin Watson  wrote:
>
> On Tue, Feb 25, 2020 at 05:40:47PM +, Ian Jackson wrote:
> > (The d/copyright problem with epydoc should be easy if tedious to fix;
> > I don't understand why it wants epydoc which I thought was obsolete
> > but this is far from my field of expertise.)
>
> epydoc has been unmaintained for a long time, but the API documentation
> of various projects (notably Twisted) still relies on its docstring
> format for automatically-generated HTML documentation in a way that
> would be extremely tedious to replace with something else.  As a result,
> the approach that the Twisted developers ended up taking for pydoctor
> was to take a copy of the bits of epydoc that they needed and port those
> bits to Python 3 themselves.
>
> (This is second-hand; I'm not on the Twisted team, but I contribute a
> fair bit there and generally keep an eye on what they're doing since we
> rely on Twisted at work.)

Thank you Sean for the heads-up, and thank you Ian, Jonas and Colin
for your valuable and helpful comments.

A fix to this bug is almost ready: I have expanded d/copyright to
include the missing epydoc and bootstrap.min.css copyright info, and
added debian/missing-sources/bootstrap.css (vanilla Bootstrap v3.3.4,
equivalent to the embedded minified version, from Bootstrap CDN).

... though I discovered I foolishly uploaded an essentially empty
pydoctor binary package, and I may end up renaming it
python3-pydoctor, similar to how it was named python-pydoctor for the
Python2 version.  That's most likely why Lintian did not pick up on
the "bootstrap.min.css" missing source issue.  Jonas, thanks for
letting me know about linking to bootstrap.min.css in libjs-bootstrap;
I'll do that.

Cheers,
Anthony

Processed: python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not raised)

[Debian Bug Tracking System]

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

> reopen 902241
Bug #902241 {Done: Thomas Goirand } [src:python-proliantutils] 
python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not 
raised)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-proliantutils/2.6.0-2.
> tags 902241 + patch
Bug #902241 [src:python-proliantutils] python-proliantutils: FTBFS in stretch 
(AssertionError: IloConnectionError not raised)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: py2removal bugs severity updates - 2020-02-25 21:35:15.383242+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-nevow is a module and has 0 external rdeps or not in testing
> severity 937132 serious
Bug #937132 [src:nevow] nevow: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-appdirs is a module and has 0 external rdeps or not in testing
> severity 936127 serious
Bug #936127 [src:appdirs] appdirs: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#952312: [Pkg-javascript-devel] Bug#952312: Bug#952312: Bug#952312: node-eslint-scope: FTBFS: tests failed

[Jonas Smedegaard]

Quoting Bastien ROUCARIES (2020-02-25 21:13:48)
> Le mar. 25 févr. 2020 à 19:48, Jonas Smedegaard  a écrit :
> 
> > control: reassign -1 node-espree
> > control: affects -1 node-eslint-scope
> >
> > Quoting Xavier (2020-02-25 18:29:35)
> > > Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit :
> > > > During a rebuild of all packages in sid, your package failed to
> > > > build on amd64.
> > >
> > > Some test are incompatible with node-espree-6. The fix could be
> > > simply:
> >
> > Certainly not a fix to disable tests.
> >
> > The package node-espree has exactly one reverse dependency which is
> > node-eslint-scope, so this is a case of bad coordination.
> >
> > (yes, another fix would be to upgrade node-eslint-scope, but that is 
> > more complex and less urgent, so let's roll back first and work on 
> > going forward in experimental first
> 
> 
> 
> Node-espree was upgraded due to not compatible with acorn6...
> 
> So upgrade is safer

Please define "safer" in this context.


 - Jonas

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

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

signature.asc
Description: signature

Bug#952335: [Pkg-javascript-devel] Bug#952335: uglify-js: FTBFS: ERROR: `m` is not a supported option

[Xavier]

Le 25/02/2020 à 19:15, Jonas Smedegaard a écrit :
> control: reassign -1 node-commander
> control: affects -1 uglify-js
> 
> Quoting Xavier (2020-02-25 18:43:53)
>> Le 23/02/2020 à 14:31, Lucas Nussbaum a écrit :
>>> During a rebuild of all packages in sid, your package failed to 
>>> build on amd64.
>>
>> At least uglify-js (https://salsa.debian.org/js-team/uglifyjs) is 
>> incompatible with node-commander 4
> 
> Then it seems node-commander upgrade (done by you, Xavier) was badly 
> coordinated and should be reverted.
> 
>  - Jonas

debci did not report this because package was already broken. Rolling
back does not fix all (that's why I wrote "at least").
Reverting node-commander update may break a lot of packages:

node-commander
Reverse Depends:
  mocha
  uglifyjs
  yarnpkg
  node-ws
  uglifyjs.terser
  node-d3-dsv
  node-jade
  node-express-generator
  node-babel-cli
  cleancss
mocha
Reverse Depends:
  node-type-check
uglifyjs
Reverse Depends:
  node-constantinople
node-uglify
yarnpkg
Reverse Depends:
  gitlab
node-ws
Reverse Depends:
  node-websocket-stream
  node-flashproxy
uglifyjs.terser
Reverse Depends:
node-d3-dsv
Reverse Depends:
  node-d3
  node-d3-request
  node-d3-fetch
node-jade
Reverse Depends:
node-express-generator
Reverse Depends:
node-babel-cli
Reverse Depends:
  node-grunt-babel
cleancss
Reverse Depends:
node-type-check
Reverse Depends:
  node-levn
  node-optionator
node-constantinople
Reverse Depends:
  node-jade
node-uglify
Reverse Depends:
  node-dryice
  lava-dev
  emscripten
  node-with
  node-transformers
gitlab
Reverse Depends:
node-websocket-stream
Reverse Depends:
node-flashproxy
Reverse Depends:
node-d3
Reverse Depends:
  node-dagre-d3-renderer
node-d3-request
Reverse Depends:
  node-d3
node-d3-fetch
Reverse Depends:
node-grunt-babel
Reverse Depends:
node-levn
Reverse Depends:
  node-optionator
node-optionator
Reverse Depends:
  livescript
  node-escodegen
node-dryice
Reverse Depends:
lava-dev
Reverse Depends:
  lava
emscripten
Reverse Depends:
node-with
Reverse Depends:
  node-jade
node-transformers
Reverse Depends:
  node-jade
node-dagre-d3-renderer
Reverse Depends:
livescript
Reverse Depends:
  node-type-check
node-escodegen
Reverse Depends:
  node-static-eval
  node-static-module
  jison
  node-istanbul
lava
Reverse Depends:
node-static-eval
Reverse Depends:
  node-static-module
node-static-module
Reverse Depends:
  node-brfs
jison
Reverse Depends:
node-istanbul
Reverse Depends:
  node-opencv
node-brfs
Reverse Depends:
node-opencv

Bug#952275: marked as done (ipxe: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 21:09:59 +
with message-id 
and subject line Bug#952275: fixed in ipxe 1.0.0+git-20190125.36a4c85-5
has caused the Debian Bug report #952275,
regarding ipxe: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 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.)


-- 
952275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipxe
Version: 1.0.0+git-20190125.36a4c85-4
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[2]: Entering directory '/<>/src'
> rm -f bin{,-*}/*.* bin{,-*}/.certificate.* bin{,-*}/.certificates.* 
> bin{,-*}/.private_key.* bin{,-*}/errors bin{,-*}/NIC ./util/zbin 
> ./util/elf2efi32 ./util/elf2efi64 ./util/efirom ./util/efifatbin 
> ./util/iccfix ./util/einfo TAGS bin{,-*}/symtab
> rm -f -r .echocheck bin{,-*}/.fnrec.state bin{,-*}/.embedded.list 
> bin{,-*}/.trusted.list bin{,-*}/.certificate.list bin{,-*}/.private_key.list 
> bin{,-*}/.config.list bin{,-*}/.assert.list bin{,-*}/.profile.list 
> bin{,-*}/.dbgcol.list bin{,-*}/deps bin{,-*}/rules bin{,-*}/.rom.list 
> bin{,-*}/.rom.defs bin{,-*}/.blib.list bin{,-*}/doc
> make[2]: Leaving directory '/<>/src'
> rm -fr src/bin-*
> rm -f src/config/local/*
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ipxe using existing 
> ./ipxe_1.0.0+git-20190125.36a4c85.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.assert.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.blib.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.certificate.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.config.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.dbgcol.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.embedded.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.fnrec.state
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.private_key.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.profile.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.rom.list
>  ipxe-1.0.0+git-20190125.36a4c85/src/bin/.trusted.list
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/ipxe_1.0.0+git-20190125.36a4c85-4.diff.SdDrsp
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-02-23T02:27:31Z

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/ipxe_1.0.0+git-20190125.36a4c85-4_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: ipxe
Source-Version: 1.0.0+git-20190125.36a4c85-5
Done: Bastian Blank 

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

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated ipxe 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, 25 Feb 2020 21:44:34 +0100
Source: ipxe
Architecture: source
Version: 1.0.0+git-20190125.36a4c85-5
Distribution: unstable
Urgency: medium
Maintainer: Bastian Blank 
Changed-By: Bastian Blank 
Closes: 952275
Changes:
 ipxe (1.0.0+git-20190125.36a4c85-5) unstable; urgency=medium
 .
   * Cleanup src/bin correctly. (closes: #952275)

Processed: Bug#951927 marked as pending in murano

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #951927 [src:murano] murano: FTBFS: FileNotFoundError: [Errno 2] No such 
file or directory: '/tmp/tmp1ojzxlld'
Added tag(s) pending.

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

Bug#951927: marked as pending in murano

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #951927 in murano 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/openstack-team/services/murano/-/commit/f447ddec47318b2ad65f0d50b22a1cba6541b0d6


* Blacklist failing tests (failing because of wrong order in result):
- test_XML_Dict_Serializer_create_link_nodes()
- test_export_fixation_table()
(Closes: #951927).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/951927

Bug#902241: marked as done (python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not raised))

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 21:20:19 +0100
with message-id <9eca9499-865e-440f-8f0b-1ad332754...@debian.org>
and subject line Closing this bug
has caused the Debian Bug report #902241,
regarding python-proliantutils: FTBFS in stretch (AssertionError: 
IloConnectionError not raised)
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.)


-- 
902241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-proliantutils
Version: 2.1.11-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch and it failed:


[...]
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_not_to_upload_firmware_file
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_not_to_upload_firmware_file
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_to_upload_firmware_file
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_to_upload_firmware_file
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_calls_extract_of_fw_extractor_object
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_calls_extract_of_fw_extractor_object
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_failed_extraction
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_failed_extraction
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_unknown_firmware_file_format
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_unknown_firmware_file_format
 ... ok

==
FAIL: 
proliantutils.tests.ilo.test_firmware_controller.FirmwareImageUploaderTestCase.test__get_socket_throws_exception_in_case_of_failed_connection_2
proliantutils.tests.ilo.test_firmware_controller.FirmwareImageUploaderTestCase.test__get_socket_throws_exception_in_case_of_failed_connection_2
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/ddt.py", line 129, in wrapper
return func(self, *args, **kwargs)
  File "proliantutils/tests/ilo/test_firmware_controller.py", line 566, in 
test__get_socket_throws_exception_in_case_of_failed_connection
self.assertRaises(expected_exception_type, fw_img_uploader._get_socket)
  File "/usr/lib/python2.7/unittest/case.py", line 473, in assertRaises
callableObj(*args, **kwargs)
  File "/usr/lib/python2.7/unittest/case.py", line 116, in __exit__
"{0} not raised".format(exc_name))
AssertionError: IloConnectionError not raised


--
Ran 473 tests in 5.071s

FAILED (failures=1)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I admit this is strange because it seems to build ok in the
reproducible builds autobuilders.

However, I've decided to report it anyway because I've tried to build
it 55 times and it failed 55 times, on 23 different autobuilders:

https://people.debian.org/~sanvila/build-logs/python-proliantutils/

I can even reproduce it with plain dpkg-buildpackage (i.e. without sbuild)
on a brand new machine from Digital Ocean, so if you could not reproduce
this, please contact me privately. As a last resort, I could give you
access to one of such machines.

Thanks.
--- End Message ---
--- Begin Message ---
As it's been open for 2 months, it's highly unlikely anyone will work on
that bug in Stretch, so I'm closing the bug.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#952312: [Pkg-javascript-devel] Bug#952312: Bug#952312: Bug#952312: node-eslint-scope: FTBFS: tests failed

[Bastien ROUCARIES]

Le mar. 25 févr. 2020 à 19:48, Jonas Smedegaard  a écrit :

> control: reassign -1 node-espree
> control: affects -1 node-eslint-scope
>
> Quoting Xavier (2020-02-25 18:29:35)
> > Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit :
> > > During a rebuild of all packages in sid, your package failed to
> > > build on amd64.
> >
> > Some test are incompatible with node-espree-6. The fix could be
> > simply:
>
> Certainly not a fix to disable tests.
>
> The package node-espree has exactly one reverse dependency which is
> node-eslint-scope, so this is a case of bad coordination.
>
> (yes, another fix would be to upgrade node-eslint-scope, but that is
> more complex and less urgent, so let's roll back first and work on going
> forward in experimental first



Node-espree was upgraded due to not compatible with acorn6...

So upgrade is safer

> )
>
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private--
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#950581: marked as done (python-django: CVE-2020-7471: Potential SQL injection via StringAgg(delimiter))

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 19:47:34 +
with message-id 
and subject line Bug#950581: fixed in python-django 1:1.11.28-1~deb10u1
has caused the Debian Bug report #950581,
regarding python-django: CVE-2020-7471: Potential SQL injection via 
StringAgg(delimiter)
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.)


-- 
950581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 2:2.2.9-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1:1.11.27-1~deb10u1

Hi,

The following vulnerability was published for python-django.

CVE-2020-7471[0]:
| Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3
| allows SQL Injection if untrusted data is used as a StringAgg
| delimiter (e.g., in Django applications that offer downloads of data
| as a series of rows with a user-specified column delimiter). By
| passing a suitably crafted delimiter to a
| contrib.postgres.aggregates.StringAgg instance, it was possible to
| break escaping and inject malicious SQL.


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-7471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7471
[1] https://www.djangoproject.com/weblog/2020/feb/03/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.11.28-1~deb10u1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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, 14 Feb 2020 10:00:33 +
Source: python-django
Binary: python-django python-django-common python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 1:1.11.28-1~deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 950581
Changes:
 python-django (1:1.11.28-1~deb10u1) buster-security; urgency=high
 .
   * New upstream security release. (Closes: #950581)
 
 .
 - CVE-2020-7471: Potential SQL injection via StringAgg(delimiter)
 .
   Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3
   allows SQL Injection if untrusted data is used as a StringAgg delimiter
   (e.g., in Django applications that offer downloads of data as a series of
   rows with a user-specified column delimiter). By passing a suitably
   crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it
   was possible to break escaping and inject malicious SQL.
Checksums-Sha1:
 68aff58b16ac698d772f1d208ff3b7e4d8ccebfd 3267 
python-django_1.11.28-1~deb10u1.dsc
 1537a67692f9f724d005631cc035d9a58648934a 7852525 
python-django_1.11.28.orig.tar.gz
 0aaf74684fec34304800795dfce4c38c4c2fa9e2 27456 
python-django_1.11.28-1~deb10u1.debian.tar.xz
 76770ff673fe837ec2bb661baf1190d8ef5685aa 1538384 
python-django-common_1.11.28-1~deb10u1_all.deb
 4d2baa4d8c66f3a35628c60344789c4d47894199 2645532 
python-django-doc_1.11.28-1~deb10u1_all.deb
 bc275075c3758ed659057adae9f1bb83ddc3dffe 917656 
python-django_1.11.28-1~deb10u1_all.deb
 c9307b5a4d69d3f31c860c2cea6a11a0a8b36860 8678 
python-django_1.11.28-1~deb10u1_amd64.buildinfo
 8d9554ac05abc114dcd6a60b6f667ed0ee42d609 917484 

Bug#949227: marked as done (python-pysaml2: FTBFS in buster because of expired certificate)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 19:47:34 +
with message-id 
and subject line Bug#949227: fixed in python-pysaml2 4.5.0-4+deb10u1
has caused the Debian Bug report #949227,
regarding python-pysaml2: FTBFS in buster because of expired certificate
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.)


-- 
949227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysaml2
Version: 4.5.0-4
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/python-pysaml2.html

...
= test session starts ==
platform linux2 -- Python 2.7.16, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/python-pysaml2-4.5.0, inifile:
plugins: betamax-0.8.1
collected 570 items / 1 errors

 ERRORS 
___ ERROR collecting tests/test_82_pefim.py 
tests/test_82_pefim.py:17: in 
conf.load_file("server_conf")
src/saml2/config.py:377: in load_file
return self.load(copy.deepcopy(mod.CONFIG), metadata_construction)
src/saml2/config.py:356: in load
self.load_complex(cnf, metadata_construction=metadata_construction)
src/saml2/config.py:296: in load_complex
self.load_metadata(cnf["metadata"]))
src/saml2/config.py:400: in load_metadata
mds.imp(metadata_conf)
src/saml2/mdstore.py:968: in imp
_md.load()
src/saml2/mdstore.py:672: in load
return self.parse_and_check_signature(_txt)
src/saml2/mdstore.py:635: in parse_and_check_signature
self.parse(txt)
src/saml2/mdstore.py:541: in parse
self.entities_descr.valid_until,))
E   ToOld: Metadata not valid anymore, it's only valid until 
2020-11-28T09:10:09Z
!!! Interrupted: 1 errors during collection 
=== 1 error in 7.98 seconds 
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: python-pysaml2
Source-Version: 4.5.0-4+deb10u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-pysaml2 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, 07 Feb 2020 09:27:20 +0100
Source: python-pysaml2
Binary: python-pysaml2 python-pysaml2-doc python3-pysaml2
Architecture: source all
Version: 4.5.0-4+deb10u1
Distribution: buster-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-pysaml2 - SAML Version 2 to be used in a WSGI environment - Python 2.x
 python-pysaml2-doc - SAML Version 2 to be used in a WSGI environment - doc
 python3-pysaml2 - SAML Version 2 to be used in a WSGI environment - Python 3.x
Closes: 949227 949322
Changes:
 python-pysaml2 (4.5.0-4+deb10u1) buster-security; urgency=medium
 .
   * CVE-2020-5390: does not check that the signature in a SAML document is
 enveloped and thus signature wrapping is effective, i.e., it is affected by
 XML Signature Wrapping (XSW). Applied upstream patch: Fix XML Signature
 Wrapping (XSW) vulnerabilities (Closes: #949322).
   * Remove a test file that will fail past 2020-11-28 (Closes: #949227).
   * Add fix-importing-mock-in-py2.7.patch.
   * Add remove-test_switch_1.patch.
Checksums-Sha1:
 bf1dd67d1c7c58a83ffb7835258201b98e5c0e87 2933 
python-pysaml2_4.5.0-4+deb10u1.dsc
 37d0cb194b322f858836282130ddea2e7fd352de 2694552 
python-pysaml2_4.5.0.orig.tar.xz
 fc4f63c29f46e62f2a34c4c6d8c435bcdc845a60 15212 
python-pysaml2_4.5.0-4+deb10u1.debian.tar.xz
 2f871221e72dfd08a755a75f50cbe434e292fab0 51268 
python-pysaml2-doc_4.5.0-4+deb10u1_all.deb
 34a8dcd2aab907e2b75010803d59b2fed9682dd1 202024 
python-pysaml2_4.5.0-4+deb10u1_all.deb
 ba1a64ece07f657d9862ce77fee5978693439988 11002 
python-pysaml2_4.5.0-4+deb10u1_amd64.buildinfo
 

Bug#950581: marked as done (python-django: CVE-2020-7471: Potential SQL injection via StringAgg(delimiter))

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 19:49:33 +
with message-id 
and subject line Bug#950581: fixed in python-django 1:1.10.7-2+deb9u8
has caused the Debian Bug report #950581,
regarding python-django: CVE-2020-7471: Potential SQL injection via 
StringAgg(delimiter)
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.)


-- 
950581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 2:2.2.9-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1:1.11.27-1~deb10u1

Hi,

The following vulnerability was published for python-django.

CVE-2020-7471[0]:
| Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3
| allows SQL Injection if untrusted data is used as a StringAgg
| delimiter (e.g., in Django applications that offer downloads of data
| as a series of rows with a user-specified column delimiter). By
| passing a suitably crafted delimiter to a
| contrib.postgres.aggregates.StringAgg instance, it was possible to
| break escaping and inject malicious SQL.


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-7471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7471
[1] https://www.djangoproject.com/weblog/2020/feb/03/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.10.7-2+deb9u8
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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, 15 Feb 2020 10:25:11 +
Source: python-django
Binary: python-django python3-django python-django-common python-django-doc
Built-For-Profiles: nocheck
Architecture: source all
Version: 1:1.10.7-2+deb9u8
Distribution: stretch-security
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 950581
Changes:
 python-django (1:1.10.7-2+deb9u8) stretch-security; urgency=high
 .
   * CVE-2020-7471: Prevent a Potential SQL injection via StringAgg(delimiter).
 (Closes: #950581)
 .
 Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows
 SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in
 Django applications that offer downloads of data as a series of rows with a
 user-specified column delimiter). By passing a suitably crafted delimiter
 to a contrib.postgres.aggregates.StringAgg instance, it was possible to
 break escaping and inject malicious SQL.
Checksums-Sha1:
 00bec81e5c3ecfbfbe2f3a73ec54a18cdacf6b29 2804 python-django_1.10.7-2+deb9u8.dsc
 5edd13a642460c33cdaf8e8166eccf6b2a2555df 7737654 
python-django_1.10.7.orig.tar.gz
 863b6c87e2d2232eb1352a4e5ce73ee0bd5d7f7e 44688 
python-django_1.10.7-2+deb9u8.debian.tar.xz
 f5310b0f95fc877f7bf092f5eeb4fa89dc42c228 1515062 
python-django-common_1.10.7-2+deb9u8_all.deb
 dc07d0e62143cc54c4cd4f03cdf4e259cc65b0b3 2536942 
python-django-doc_1.10.7-2+deb9u8_all.deb
 145a80c1d0452c8986532eac529db0e20ad75ea0 905372 
python-django_1.10.7-2+deb9u8_all.deb
 4387ce6c4adb3850bf7ebc3a92aadbcb0215c8cc 9409 
python-django_1.10.7-2+deb9u8_amd64.buildinfo
 24ddd2907c9b4d4911aecdf105336c96302bf51e 886958 
python3-django_1.10.7-2+deb9u8_all.deb
Checksums-Sha256:
 818d23d52146c8ca4584a8f9c7d5082278c0843c0c681195a3165e7a3cef41d1 2804 

Bug#949322: marked as done (python-pysaml2: CVE-2020-5390)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 19:47:35 +
with message-id 
and subject line Bug#949322: fixed in python-pysaml2 4.5.0-4+deb10u1
has caused the Debian Bug report #949322,
regarding python-pysaml2: CVE-2020-5390
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.)


-- 
949322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysaml2
Version: 4.5.0-5
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 4.5.0-4

Hi,

The following vulnerability was published for python-pysaml2.

CVE-2020-5390[0]:
| PySAML2 before 5.0.0 does not check that the signature in a SAML
| document is enveloped and thus signature wrapping is effective, i.e.,
| it is affected by XML Signature Wrapping (XSW). The signature
| information and the node/object that is signed can be in different
| places and thus the signature verification will succeed, but the wrong
| data will be used. This specifically affects the verification of
| assertion that have been signed.


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-5390
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5390
[1] 
https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-pysaml2
Source-Version: 4.5.0-4+deb10u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-pysaml2 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, 07 Feb 2020 09:27:20 +0100
Source: python-pysaml2
Binary: python-pysaml2 python-pysaml2-doc python3-pysaml2
Architecture: source all
Version: 4.5.0-4+deb10u1
Distribution: buster-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-pysaml2 - SAML Version 2 to be used in a WSGI environment - Python 2.x
 python-pysaml2-doc - SAML Version 2 to be used in a WSGI environment - doc
 python3-pysaml2 - SAML Version 2 to be used in a WSGI environment - Python 3.x
Closes: 949227 949322
Changes:
 python-pysaml2 (4.5.0-4+deb10u1) buster-security; urgency=medium
 .
   * CVE-2020-5390: does not check that the signature in a SAML document is
 enveloped and thus signature wrapping is effective, i.e., it is affected by
 XML Signature Wrapping (XSW). Applied upstream patch: Fix XML Signature
 Wrapping (XSW) vulnerabilities (Closes: #949322).
   * Remove a test file that will fail past 2020-11-28 (Closes: #949227).
   * Add fix-importing-mock-in-py2.7.patch.
   * Add remove-test_switch_1.patch.
Checksums-Sha1:
 bf1dd67d1c7c58a83ffb7835258201b98e5c0e87 2933 
python-pysaml2_4.5.0-4+deb10u1.dsc
 37d0cb194b322f858836282130ddea2e7fd352de 2694552 
python-pysaml2_4.5.0.orig.tar.xz
 fc4f63c29f46e62f2a34c4c6d8c435bcdc845a60 15212 
python-pysaml2_4.5.0-4+deb10u1.debian.tar.xz
 2f871221e72dfd08a755a75f50cbe434e292fab0 51268 
python-pysaml2-doc_4.5.0-4+deb10u1_all.deb
 34a8dcd2aab907e2b75010803d59b2fed9682dd1 202024 
python-pysaml2_4.5.0-4+deb10u1_all.deb
 ba1a64ece07f657d9862ce77fee5978693439988 11002 
python-pysaml2_4.5.0-4+deb10u1_amd64.buildinfo
 8866cceded75a98643850790fea817a576cca55d 202048 
python3-pysaml2_4.5.0-4+deb10u1_all.deb
Checksums-Sha256:
 7666259a25a9a905927bd07e3770bc51a2b11a354fc88eb144caa5060ef197ce 2933 
python-pysaml2_4.5.0-4+deb10u1.dsc
 3e1a807fc82998883d8648624fabcda57a446a198e297c36a14e7969c4c2ddc1 2694552 
python-pysaml2_4.5.0.orig.tar.xz
 c09d116988a6af9273c4f2a8a7b59b07d619ae0144e822f50b0900049a187b19 15212 
python-pysaml2_4.5.0-4+deb10u1.debian.tar.xz
 e2ba9e52d314a0467ecea1aa788071bd25f59fcd55e1c4d218df5dc3b915d131 51268 

Processed: Re: Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

[Debian Bug Tracking System]

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

> severity 952464 important
Bug #952464 [src:clazy] clazy: flaky arm64 autopkgtest: unable to execute 
command: Segmentation fault
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

[Pino Toscano]

severity 952464 important
thanks

In data lunedì 24 febbraio 2020 21:10:53 CET, Paul Gevers ha scritto:
> Source: clazy
> Version: 1.6-2
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky

The test is not flaky.

> Dear maintainer(s),
> 
> With a recent upload of gcc-10 to unstable, the autopkgtest of clazy
> failed on arm64 in testing when that autopkgtest was run with the binary
> packages of gcc-10 from unstable.

The failures have nothing to do with gcc-10.

> I looked into the history of your autopkgtest and it fails very often.

Err, not really, no need to exagerate things that are not like that.

The situation is more complex than that, and it needs a longer
explanation. No TL;DR is provided.

clazy is a clang plugin to detect more issues in Qt-based software,
and because of that it uses (and links to) the LLVM/clang libraries.
What is shipped is the following:

(1) /usr/bin/clazy
(2) /usr/bin/clazy-standalone
(3) /usr/lib/MULTI-ARCH/ClazyPlugin.so

(3) is the actual plugin, which is used like:
  $ clang -Xclang -load -Xclang ClazyPlugin.so -Xclang \
  -add-plugin -Xclang clazy [etc...]
This is links to the LLVM and clang libraries.

(2) is a similar version of (1), made as standalone executable rather
than a compiler plugin. It is used as compiler, so e.g.:
  $ clazy [...]

(1) is a shells script that wraps the usage of (3), with extra
parameters for version/help, and list the actual checks available.

clazy supports various LLVM versions (clazy 1.6 requires LLVM >= 5),
and it is generally updated whenever a new LLVM version is released.
For this reason, I let it built with the default LLVM version (that is
src:llvm-defaults), so using the unversioned llvm/clang -dev packages.
OTOH, (1) as shipped upstream calls the unversioned "clang++"
executable: because of this, we have local changes that record the path
to the clang++ tool of the clang version used during the built (i.e.
the Debian default one). It is easy to check this:

  $ dpkg -l | grep clazy
  ii  clazy   1.6-2+b1  amd64Clang 
plugin for additional warnings
  $ grep CLANGXX /usr/bin/clazy
  ${CLANGXX:-/usr/lib/llvm-9/bin/clang++} --version | head -1 | awk 
'{printf("clang version: %s\n",$3)}'
${CLANGXX:-/usr/lib/llvm-9/bin/clang++} -Qunused-arguments -Xclang -load 
-Xclang $ClazyPluginLib -Xclang -add-plugin -Xclang clazy $ExtraClangOptions 
"$@"

In addition to that, the clang-X package used is recorded as dependency:

  $ apt-cache show clazy | grep Depends
  Depends: libc6 (>= 2.14), libllvm9 (>= 1:9~svn298832-1~), libstdc++6 (>= 9), 
clang-9

So clazy pulls whichever version of clang it was built with, and thus
(1) works OOTB.

Now let's take a look at the autopkgtest structure:

  $ cat debian/tests/control 
  Tests: run-tests
  Depends: @, clang, clang-tools, python3, qtbase5-dev, qtdeclarative5-dev
  Restrictions: rw-build-tree, allow-stderr

  $ cat debian/tests/run-tests 
  #!/bin/sh
  
  set -e
  
  # show some facts about clang/clang++, so it is easier to debug issues
  clang -E -x c - -v < /dev/null
  clang++ -E -x c++ - -v < /dev/null
  
  cd tests
  ./run_tests.py --verbose

The upstream tests/run_tests.py executable executes the tests twice:
with (2) and (3). We can understand easily that the tests with (2) work
fine in all the cases, and indeed they pass flawlessy. The tests with
(3) use "clang++" as compiler name by default, and as such it is the
Debian default.

Putting all the pieces together: why the autopkgtest can fail?
The answer is simple: the version of src:llvm-defaults in the
environment of the test is different than the one used to build clazy.

In this particular case: clazy was rebuilt when src:llvm-defaults was
switched from 8 to 9, and because LLVM 9 was already in testing, the
binNMU migrated instantly to testing. However, src:llvm-defaults took
its 5 days to migrate to testing, so "clang" was still 8.
I see src:llvm-defaults migrated to testing today: this means that the
failures "disappear", since in both suites the versions of
(a) src:llvm-defaults used when building clazy
(b) src:llvm-defaults present
are the same.

What I will not do: switch away from the unversioned llvm version.
This means manually changing the used llvm version, which is a PITA,
and generally not needed for what clazy needs.

It seems like run_tests.py allows changing the "clang" executable used
with the CLANGXX environment variable. This seems a promising move,
however detecting what was the clang version used to build clazy only
by looking at the installed clazy seems hard. I will try to come up
with something in the next days to allow testing with the right
version. Although, as I said, the issue "fixed itself" until the next
src:llvm-defaults switch, this is slightly less problematic.

In the meanwhile: because of what I said above, I'm demoting the
severity of this bug to important. Also, 

Bug#945567: new network-manager-strongswan package [and 1 more messages]

[Harald Dunkel]

Hi Ian,

On 2/24/20 5:14 PM, Ian Jackson wrote:


Fixed I think.  I have created this:
   https://salsa.debian.org/debian/network-manager-strongswan
and made you ("harri-guest") a maintainer of it.

I think you can do all the rest of the setup yourself.  Let me know if
you want anything else doing.



I have pushed n-m-s 1.4.5-1 to salsa, without touching the label.
Worked very well.

Next I created version 1.4.5-2 (no tag yet) to fix the issues you
mentioned (Vcs-git, git format-patch). Hopefully I didn't miss
anything. lintian is still happy. Pushed.

Maybe you could take a look?


Thanx in advance
Harri

Bug#952494: marked as done (Can not manage wired interface)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 20:36:05 +0100
with message-id <96c56008-3223-4d47-ddef-72e4f2dd0...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#952494: Can not manage wired 
interface
has caused the Debian Bug report #952494,
regarding Can not manage wired interface
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.)


-- 
952494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 1.22.6-1
Severity: grave


Hi, I found the network-manage can not manage the wired net interface now. 
Message "Wired Unmanaged" was showed, and I have set "managed=true" in 
NetworkManager.conf.

How to resolve this problem?


Thank you!

Gulfstream



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

Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.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 network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.16-2
ii  init-system-helpers1.57
ii  libaudit1  1:2.8.5-2+b1
ii  libbluetooth3  5.50-1+b1
ii  libc6  2.29-10
ii  libcurl3-gnutls7.67.0-2
ii  libglib2.0-0   2.62.4-2
ii  libgnutls303.6.12-2
ii  libjansson42.12-1
ii  libmm-glib01.10.4-0.1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.21-4
ii  libnm0 1.22.6-1
ii  libpam-systemd 244.3-1
ii  libpolkit-agent-1-00.105-26
ii  libpolkit-gobject-1-0  0.105-26
ii  libpsl50.20.2-2
ii  libreadline8   8.0-3
ii  libselinux13.0-1+b1
ii  libsystemd0244.3-1
ii  libteamdctl0   1.30-1
ii  libudev1   244.3-1
ii  libuuid1   2.34-0.1
ii  policykit-10.105-26
ii  udev   244.3-1
ii  wpasupplicant  2:2.9+git20200213+877d9a0-1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1.1
ii  iptables 1.8.4-3
ii  modemmanager 1.10.4-0.1
ii  ppp  2.4.7-2+4.1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1
pn  libteam-utils

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true


-- no debconf information
--- End Message ---
--- Begin Message ---
Am 25.02.20 um 01:51 schrieb gulfstream:
> Package: network-manager
> Version: 1.22.6-1
> Severity: grave
> 
> 
> Hi, I found the network-manage can not manage the wired net interface now. 
> Message "Wired Unmanaged" was showed, and I have set "managed=true" in 
> NetworkManager.conf.
> 
If you are using /etc/network/interfaces and managed=true mode
(something which I do *not* recommend), then you bind the network
configuration to an interface name.

Since you appear to be the same person that filed #952506, this appears
to be your real problem and not NetworkManager misbehaving. So I'm going
to close this bug report.

I would also recommend that you drop any configurations from
/etc/network/interfaces, use managed=false and use the native
NetworkManager configuration via settings files in
/etc/NetworkManager/system-connections.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#952497: marked as done (Wired network interface can not be managed by Network-Manager)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 20:36:05 +0100
with message-id <96c56008-3223-4d47-ddef-72e4f2dd0...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#952494: Can not manage wired 
interface
has caused the Debian Bug report #952494,
regarding Wired network interface can not be managed by Network-Manager
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.)


-- 
952494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 1.22.8-1
Severity: grave


Hi, I found that the network-manage can not manage the wired net interface now. 
Message "Wired Unmanaged" was showed, and I have set "managed=true" in 
NetworkManager.conf.

I have upgrade the network-manager to 1.22.8-1, but the problem did not be 
resolved.

How to resolve this problem?

Thank you!


Gulfstream


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

Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.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 network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.16-2
ii  init-system-helpers1.57
ii  libaudit1  1:2.8.5-2+b1
ii  libbluetooth3  5.50-1+b1
ii  libc6  2.29-10
ii  libcurl3-gnutls7.67.0-2
ii  libglib2.0-0   2.62.4-2
ii  libgnutls303.6.12-2
ii  libjansson42.12-1
ii  libmm-glib01.10.4-0.1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.21-4
ii  libnm0 1.22.8-1
ii  libpam-systemd 244.3-1
ii  libpolkit-agent-1-00.105-26
ii  libpolkit-gobject-1-0  0.105-26
ii  libpsl50.20.2-2
ii  libreadline8   8.0-3
ii  libselinux13.0-1+b1
ii  libsystemd0244.3-1
ii  libteamdctl0   1.30-1
ii  libudev1   244.3-1
ii  libuuid1   2.34-0.1
ii  policykit-10.105-26
ii  udev   244.3-1
ii  wpasupplicant  2:2.9+git20200213+877d9a0-1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1.1
ii  iptables 1.8.4-3
ii  modemmanager 1.10.4-0.1
ii  ppp  2.4.7-2+4.1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1
pn  libteam-utils

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true


-- no debconf information
--- End Message ---
--- Begin Message ---
Am 25.02.20 um 01:51 schrieb gulfstream:
> Package: network-manager
> Version: 1.22.6-1
> Severity: grave
> 
> 
> Hi, I found the network-manage can not manage the wired net interface now. 
> Message "Wired Unmanaged" was showed, and I have set "managed=true" in 
> NetworkManager.conf.
> 
If you are using /etc/network/interfaces and managed=true mode
(something which I do *not* recommend), then you bind the network
configuration to an interface name.

Since you appear to be the same person that filed #952506, this appears
to be your real problem and not NetworkManager misbehaving. So I'm going
to close this bug report.

I would also recommend that you drop any configurations from
/etc/network/interfaces, use managed=false and use the native
NetworkManager configuration via settings files in
/etc/NetworkManager/system-connections.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#905877: marked as done (regression in 1.4: upgrades random packages from testing to experimental (doesn't respect pinning?))

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 19:21:58 +
with message-id 
and subject line Bug#905877: fixed in unattended-upgrades 1.18
has caused the Debian Bug report #905877,
regarding regression in 1.4: upgrades random packages from testing to 
experimental (doesn't respect pinning?)
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.)


-- 
905877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 1.4
Severity: serious

Recently I have had unattended-upgrades upgrade random packages from
testing to experimental. If I downgrade the packages upgraded, I won't
get the same packages upgraded the next day. I run apt-show-versions
daily and save the output to my mail store. Using my mail store I found
that the first instance of this happening was on 2018-07-06, there were
earlier instances but they were from me manually installing packages
from experimental and u-u doing subsequent upgrades. I noticed that I
upgraded unattended-upgrades on that date from 1.3 to 1.4. I'm not
sure, but the changelog indicates some package candidate changes,
perhaps this caused the issue? I think this bug should be fixed before Debian 
releases buster, this could break some setups.

$ notmuch search --output files --format text0 subject:apt-show-versions AND 
experimental | xargs -0 grep -Zl ^+.*/experimental | xargs -0 grep ^Date:
grep: /home/pabs/mail/cur/1533911695.H364727P6217.chianamo:2,: No such file or 
directory
/home/pabs/mail/.archives.chianamo/cur/1533738479.H931450P19950.chianamo:2,S:Date:
 Wed, 08 Aug 2018 22:27:59 +0800
/home/pabs/mail/.archives.chianamo/cur/1533452480.H469089P20113.chianamo:2,S:Date:
 Sun, 05 Aug 2018 15:01:20 +0800
/home/pabs/mail/.archives.chianamo/cur/1532469048.H39195P10262.chianamo:2,S:Date:
 Wed, 25 Jul 2018 05:50:47 +0800
/home/pabs/mail/.archives.chianamo/cur/1532009473.H904807P26370.chianamo:2,S:Date:
 Thu, 19 Jul 2018 22:11:13 +0800
/home/pabs/mail/.archives.chianamo/cur/1531406466.H36620P31910.chianamo:2,S:Date:
 Thu, 12 Jul 2018 22:41:05 +0800
/home/pabs/mail/.archives.chianamo/cur/1531318643.H907159P2397.chianamo:2,S:Date:
 Wed, 11 Jul 2018 22:17:23 +0800
/home/pabs/mail/.archives.chianamo/cur/1531231937.H239897P6579.chianamo:2,S:Date:
 Tue, 10 Jul 2018 22:12:17 +0800
/home/pabs/mail/.archives.chianamo/cur/1531145728.H178673P15461.chianamo:2,S:Date:
 Mon, 09 Jul 2018 22:15:28 +0800
/home/pabs/mail/.archives.chianamo/cur/1530973747.H830435P12225.chianamo:2,S:Date:
 Sat, 07 Jul 2018 22:29:07 +0800
/home/pabs/mail/.archives.chianamo/cur/1530887497.H217865P26358.chianamo:2,S:Date:
 Fri, 06 Jul 2018 22:31:36 +0800
/home/pabs/mail/.archives.chianamo/cur/1528812402.H467547P3507.chianamo:2,S:Date:
 Tue, 12 Jun 2018 22:06:42 +0800
/home/pabs/mail/.archives.chianamo/cur/1528121929.H964004P25155.chianamo:2,S:Date:
 Mon, 04 Jun 2018 22:18:49 +0800
/home/pabs/mail/.archives.chianamo/cur/1527948341.H185749P9358.chianamo:2,S:Date:
 Sat, 02 Jun 2018 22:05:41 +0800
/home/pabs/mail/.archives.chianamo/cur/1527863815.H640051P20918.chianamo:2,S:Date:
 Fri, 01 Jun 2018 22:36:55 +0800
...

$ which-pkg-broke unattended-upgrades | grep -C3 'Jul *6'
libpython3.6-stdlib:amd64  Sun Jul  1 13:07:11 2018
python3.6-minimal  Sun Jul  1 13:07:14 2018
libpython3.6-minimal:amd64 Sun Jul  1 13:07:19 2018
unattended-upgradesFri Jul  6 21:03:10 2018
install-info   Sat Jul  7 12:22:43 2018
libapt-pkg5.0:amd64Mon Jul 16 15:38:37 2018
libapt-inst2.0:amd64   Mon Jul 16 15:38:43 2018

$ zgrep -B2 -A1 unattended-upgrades /var/log/apt/history.log.1.gz 
Start-Date: 2018-07-06  21:03:00
Requested-By: pabs (1000)
Upgrade: unattended-upgrades:amd64 (1.3, 1.4)
End-Date: 2018-07-06  21:03:21

unattended-upgrades (1.4) unstable; urgency=medium
...
  * Adjust candidates only for packages to be possibly installed
(Closes: #892028, #899366) (LP: #1396787)

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU.utf8 

Processed: retitle 951907 to python-bleach: CVE-2020-6802: mutation XSS vulnerability

[Debian Bug Tracking System]

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

> retitle 951907 python-bleach: CVE-2020-6802: mutation XSS vulnerability
Bug #951907 {Done: Scott Kitterman } [src:python-bleach] 
src:python-bleach: Security issue: mutation XSS vulnerability
Changed Bug title to 'python-bleach: CVE-2020-6802: mutation XSS vulnerability' 
from 'src:python-bleach: Security issue: mutation XSS vulnerability'.
> thanks
Stopping processing here.

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

Bug#952546: bootstrap.min.js in pydoctor

[Colin Watson]

On Tue, Feb 25, 2020 at 05:40:47PM +, Ian Jackson wrote:
> (The d/copyright problem with epydoc should be easy if tedious to fix;
> I don't understand why it wants epydoc which I thought was obsolete
> but this is far from my field of expertise.)

epydoc has been unmaintained for a long time, but the API documentation
of various projects (notably Twisted) still relies on its docstring
format for automatically-generated HTML documentation in a way that
would be extremely tedious to replace with something else.  As a result,
the approach that the Twisted developers ended up taking for pydoctor
was to take a copy of the bits of epydoc that they needed and port those
bits to Python 3 themselves.

(This is second-hand; I'm not on the Twisted team, but I contribute a
fair bit there and generally keep an eye on what they're doing since we
rely on Twisted at work.)

-- 
Colin Watson   [cjwat...@debian.org]

Bug#952543: marked as done (Using old libfmt breaks sopt and purify)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 18:50:13 +
with message-id 
and subject line Bug#952543: fixed in spdlog 1:1.5.0+ds-1
has caused the Debian Bug report #952543,
regarding Using old libfmt breaks sopt and purify
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.)


-- 
952543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libspdlog-dev
Version: 1:1.5.0-1
Severity: serious
Affects: src:purify, src:sopt
Control: reassign 951995 libspdlog-dev
Control: reassign 951960 libspdlog-dev
Control: forcemerge -1 951995 951960

Since spdlog uses the old (included) libfmt, the builds of purify and
sopt fail with linker errors like:

undefined reference to `fmt::v6::internal::assert_fail(char const*, int,
char const*)

See the merged bugs for the reports. Could you revert this change? Or
somehow make it work (I guess, the library itself would need to be
included).

Thank you!

Best

Ole
--- End Message ---
--- Begin Message ---
Source: spdlog
Source-Version: 1:1.5.0+ds-1
Done: michael.cru...@gmail.com (Michael R. Crusoe)

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated spdlog 
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, 25 Feb 2020 19:22:37 +0100
Source: spdlog
Architecture: source
Version: 1:1.5.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 952543
Changes:
 spdlog (1:1.5.0+ds-1) unstable; urgency=medium
 .
   * Mark libspdlog1 as Multi-Arch: same
   * Repack source to remove newer libfmt (Closes: #952543)
Checksums-Sha1:
 703c3c860f44f6cf76abfd1a6e7f7a12b48108dd 2107 spdlog_1.5.0+ds-1.dsc
 fce2b1c481f91734cc62710729db1feed84923d3 147904 spdlog_1.5.0+ds.orig.tar.xz
 c350419de6091e91ba18df4ba8a81ac43d967410 13416 spdlog_1.5.0+ds-1.debian.tar.xz
 350468cb2aa079c598109616087cf90cd12b08cd 7125 
spdlog_1.5.0+ds-1_source.buildinfo
Checksums-Sha256:
 f9de691f01e2d7586655900e3af492aad8902d3a9ca0f9242d9f4a5ee1bb8b8a 2107 
spdlog_1.5.0+ds-1.dsc
 b7aab59d0978bad5c140f881ca7882d7c11edf1f463a0b0c8d002d6187f36244 147904 
spdlog_1.5.0+ds.orig.tar.xz
 f4af5af5a9f818a31c52299ffa46566ce9fb40520c94dd68b8ec2671d9064684 13416 
spdlog_1.5.0+ds-1.debian.tar.xz
 c0223ac6b01a18481e6d158fe31727d5ad1e98e4c9c03f8d6fd8fb711f7e15e0 7125 
spdlog_1.5.0+ds-1_source.buildinfo
Files:
 4267a6f6f474c606b16b4751d35aace2 2107 libdevel optional spdlog_1.5.0+ds-1.dsc
 1fba151f9f88ff08691c21bea8adb04b 147904 libdevel optional 
spdlog_1.5.0+ds.orig.tar.xz
 e2ff1aeee7039e17d29227b777313c96 13416 libdevel optional 
spdlog_1.5.0+ds-1.debian.tar.xz
 25b450996d7e4eb0ff80dccfbd8398cd 7125 libdevel optional 
spdlog_1.5.0+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl5VZlsACgkQPCZ2P2xn
5uIwsBAAqqTRDV3e0Vd/fjCLjIE0J0IoO9dlufoV9NZWvMxuuqWxRxIJnqFcSEfZ
nSEvgGPNicsgVSqhZOEH9TTDz2qhmGB1RVn4VA+eMRxmgjyKDiS6gtHbndTqGRss
NFjnumDJ3hxS2XLmRa6uw/aAlXKm1JZDEaL+ARGJYuyZ/4KdXkzP1mpSIyraDmv7
OVGYZT4iMUYf65p7vlFefgObegSXfVlVy8GtuwrLXzhCfXOUNjljo3WAkbmhTzet
ieJOsSLkEwO0Gh7dYaq0Nwzkam3Hz2kS0YSbZeAcugiiDvp02eSx+7w4q3PDxLtY
6UIZmwrFm3TNNxDQLAtvyge4//lsm71zW3m7OGNmEvUAw0HkQXinFLzdKIi9yd+9
tVmxIy7Jc2XeJQZIF4c9YdlCOCPjnWg4dxcte8QI+tI2Z2B5wO7PwLAbf1n11yJY
ZMussg2lxSM5joTv8IYCDVaA+w4VNrBbeXQzHGqPu22Dd31gabuQKMDDkcxgDgSa
KhiHGh+9t6TZCzN2vYvtUpfLXvFCMqW8eFzlOpA2CZWLHq9Pg0ogiwDC2sThR6PN
2su1umbcic7L3ucFrqRzpbB0AaXAKXgdxHOxMDNDlRXvUq5qOy3bDbUhJ+Td4ryJ
f3LPCaKuiJIOCd37xUi3enbqpKkLbU6yFI4gfJcrYFaxMg6YtkA=
=Dpgi
-END PGP SIGNATURE End Message ---

Bug#951995: marked as done (sopt: FTBFS: core.h:266: undefined reference to `fmt::v6::internal::assert_fail(char const*, int, char const*)')

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 18:50:13 +
with message-id 
and subject line Bug#952543: fixed in spdlog 1:1.5.0+ds-1
has caused the Debian Bug report #952543,
regarding sopt: FTBFS: core.h:266: undefined reference to 
`fmt::v6::internal::assert_fail(char const*, int, char const*)'
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.)


-- 
952543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sopt
Version: 3.0.1-10
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/common_catch_main_object.dir/common_catch_main.cc.o: 
> in function `std::make_unsigned::type 
> fmt::v6::internal::to_unsigned(long)':
> /usr/include/spdlog/fmt/bundled/core.h:266: undefined reference to 
> `fmt::v6::internal::assert_fail(char const*, int, char const*)'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/sopt_3.0.1-10_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: spdlog
Source-Version: 1:1.5.0+ds-1
Done: michael.cru...@gmail.com (Michael R. Crusoe)

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated spdlog 
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, 25 Feb 2020 19:22:37 +0100
Source: spdlog
Architecture: source
Version: 1:1.5.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 952543
Changes:
 spdlog (1:1.5.0+ds-1) unstable; urgency=medium
 .
   * Mark libspdlog1 as Multi-Arch: same
   * Repack source to remove newer libfmt (Closes: #952543)
Checksums-Sha1:
 703c3c860f44f6cf76abfd1a6e7f7a12b48108dd 2107 spdlog_1.5.0+ds-1.dsc
 fce2b1c481f91734cc62710729db1feed84923d3 147904 spdlog_1.5.0+ds.orig.tar.xz
 c350419de6091e91ba18df4ba8a81ac43d967410 13416 spdlog_1.5.0+ds-1.debian.tar.xz
 350468cb2aa079c598109616087cf90cd12b08cd 7125 
spdlog_1.5.0+ds-1_source.buildinfo
Checksums-Sha256:
 f9de691f01e2d7586655900e3af492aad8902d3a9ca0f9242d9f4a5ee1bb8b8a 2107 
spdlog_1.5.0+ds-1.dsc
 b7aab59d0978bad5c140f881ca7882d7c11edf1f463a0b0c8d002d6187f36244 147904 
spdlog_1.5.0+ds.orig.tar.xz
 f4af5af5a9f818a31c52299ffa46566ce9fb40520c94dd68b8ec2671d9064684 13416 
spdlog_1.5.0+ds-1.debian.tar.xz
 c0223ac6b01a18481e6d158fe31727d5ad1e98e4c9c03f8d6fd8fb711f7e15e0 7125 
spdlog_1.5.0+ds-1_source.buildinfo
Files:
 4267a6f6f474c606b16b4751d35aace2 2107 libdevel optional spdlog_1.5.0+ds-1.dsc
 1fba151f9f88ff08691c21bea8adb04b 147904 libdevel optional 
spdlog_1.5.0+ds.orig.tar.xz
 e2ff1aeee7039e17d29227b777313c96 13416 libdevel optional 
spdlog_1.5.0+ds-1.debian.tar.xz
 25b450996d7e4eb0ff80dccfbd8398cd 7125 libdevel optional 
spdlog_1.5.0+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl5VZlsACgkQPCZ2P2xn
5uIwsBAAqqTRDV3e0Vd/fjCLjIE0J0IoO9dlufoV9NZWvMxuuqWxRxIJnqFcSEfZ
nSEvgGPNicsgVSqhZOEH9TTDz2qhmGB1RVn4VA+eMRxmgjyKDiS6gtHbndTqGRss
NFjnumDJ3hxS2XLmRa6uw/aAlXKm1JZDEaL+ARGJYuyZ/4KdXkzP1mpSIyraDmv7
OVGYZT4iMUYf65p7vlFefgObegSXfVlVy8GtuwrLXzhCfXOUNjljo3WAkbmhTzet
ieJOsSLkEwO0Gh7dYaq0Nwzkam3Hz2kS0YSbZeAcugiiDvp02eSx+7w4q3PDxLtY
6UIZmwrFm3TNNxDQLAtvyge4//lsm71zW3m7OGNmEvUAw0HkQXinFLzdKIi9yd+9
tVmxIy7Jc2XeJQZIF4c9YdlCOCPjnWg4dxcte8QI+tI2Z2B5wO7PwLAbf1n11yJY
ZMussg2lxSM5joTv8IYCDVaA+w4VNrBbeXQzHGqPu22Dd31gabuQKMDDkcxgDgSa

Bug#952428: marked as done (sympa: CVE-2020-9369: Security flaws in CSRF prevention)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 18:50:26 +
with message-id 
and subject line Bug#952428: fixed in sympa 6.2.40~dfsg-4
has caused the Debian Bug report #952428,
regarding sympa: CVE-2020-9369: Security flaws in CSRF prevention
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.)


-- 
952428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: sympa
severity: critical
version: 6.2.40~dfsg-3
tags: patch

A vulnerability has been discovered in Sympa web interface that can
cause denial of service (DoS) attack.

By submitting requests with malformed parameters, this flaw allows to
create junk files in Sympa's directory for temporary files.  And
particularly by tampering token to prevent CSRF, it allows to originate
excessive notification messages to listmasters.

Full advisory:

https://sympa-community.github.io/security/2020-001.html

Regards
   Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
From 9b86fb3f0337d70221d63392db7d1a52b439dc8f Mon Sep 17 00:00:00 2001
From: IKEDA Soji 
Date: Tue, 11 Feb 2020 17:52:22 +0900
Subject: [PATCH] Sympa SA 2020-001 (candidate).  Denial of service caused by
 malformed CSRF token.

---
 src/cgi/wwsympa.fcgi.in | 25 +++--
 1 file changed, 3 insertions(+), 22 deletions(-)

diff --git a/src/cgi/wwsympa.fcgi.in b/src/cgi/wwsympa.fcgi.in
index 2eb8aec..c7b5195 100644
--- a/src/cgi/wwsympa.fcgi.in
+++ b/src/cgi/wwsympa.fcgi.in
@@ -992,9 +992,6 @@ our %in_regexp = (
 
 # Role
 'role' => 'member|editor|owner',
-
-## CSRF token is a lower case MD5 hash
-'csrftoken' => '^[0-9a-f]{32}$',
 );
 
 ## Regexp applied on incoming parameters (%in)
@@ -1262,8 +1259,6 @@ while ($query = CGI::Fast->new) {
 # affected to another anonymous session.
 undef $ENV{'HTTP_COOKIE'};
 unless (defined $session) {
-Sympa::send_notify_to_listmaster($robot,
-'failed_to_create_web_session', {});
 wwslog('info', 'Failed to create session');
 $session = Sympa::WWW::Session->new($robot, {});
 }
@@ -2149,32 +2144,18 @@ sub get_parameters {
 if ($one_p !~ /^$regexp$/s
 || (defined $negative_regexp && $one_p =~ /$negative_regexp/s)
 ) {
-## Dump parameters in a tmp file for later analysis
-my $dump_file =
-  Conf::get_robot_conf($robot, 'tmpdir')
-. '/sympa_dump.'
-. time . '.'
-. $PID;
-unless (open DUMP, ">$dump_file") {
-wwslog('err', 'Failed to create %s: %s',
-$dump_file, $ERRNO);
-}
-Sympa::Tools::Data::dump_var(\%in, 0, \*DUMP);
-close DUMP;
-
 Sympa::WWW::Report::reject_report_web('user', 'syntax_errors',
 {p_name => $p},
 '', '');
 wwslog(
 'err',
-'Syntax error for parameter %s value "%s" not conform to regexp:%s; dumped vars in %s',
+'Syntax error for parameter %s value "%s" not conform to regexp:%s',
 $pname,
 $one_p,
-$regexp,
-$dump_file
+$regexp
 );
 $in{$p} = '';
-next;
+last;
 }
 }
 }
-- 
1.8.3.1



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sympa
Source-Version: 6.2.40~dfsg-4
Done: Stefan Hornburg (Racke) 

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

Debian distribution maintenance software
pp.
Stefan Hornburg (Racke)  (supplier of updated sympa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Feb 2020 19:22:52 

Bug#951924: marked as done (diodon: FTBFS: testcase.vala:32.5-32.19: error: Creation method of abstract class cannot be public.)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 18:49:43 +
with message-id 
and subject line Bug#951924: fixed in diodon 1.9.0-1
has caused the Debian Bug report #951924,
regarding diodon: FTBFS: testcase.vala:32.5-32.19: error: Creation method of 
abstract class cannot be public.
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./waf build --nocache --prefix=/usr
> Waf: Entering directory `/<>/_build_'
> [ 1/70] po: po/bg.po -> _build_/po/bg.mo
> [ 2/70] po: po/ca.po -> _build_/po/ca.mo
> [ 3/70] po: po/cs.po -> _build_/po/cs.mo
> [ 4/70] po: po/de.po -> _build_/po/de.mo
> [ 5/70] po: po/en_GB.po -> _build_/po/en_GB.mo
> [ 6/70] po: po/es.po -> _build_/po/es.mo
> [ 7/70] po: po/et.po -> _build_/po/et.mo
> [ 8/70] po: po/fi.po -> _build_/po/fi.mo
> [ 9/70] po: po/fr.po -> _build_/po/fr.mo
> [10/70] po: po/gl.po -> _build_/po/gl.mo
> [11/70] po: po/hu.po -> _build_/po/hu.mo
> [12/70] po: po/it.po -> _build_/po/it.mo
> [13/70] po: po/ja.po -> _build_/po/ja.mo
> [14/70] po: po/lt.po -> _build_/po/lt.mo
> [15/70] po: po/nb.po -> _build_/po/nb.mo
> [16/70] po: po/nl.po -> _build_/po/nl.mo
> [17/70] po: po/pl.po -> _build_/po/pl.mo
> [18/70] po: po/pt.po -> _build_/po/pt.mo
> [19/70] po: po/pt_BR.po -> _build_/po/pt_BR.mo
> [20/70] po: po/ro.po -> _build_/po/ro.mo
> [21/70] po: po/ru.po -> _build_/po/ru.mo
> [22/70] po: po/se.po -> _build_/po/se.mo
> [23/70] po: po/sk.po -> _build_/po/sk.mo
> [24/70] po: po/sv.po -> _build_/po/sv.mo
> [25/70] po: po/tr.po -> _build_/po/tr.mo
> [26/70] po: po/uk.po -> _build_/po/uk.mo
> [27/70] po: po/zh_CN.po -> _build_/po/zh_CN.mo
> [28/70] subst: data/net.launchpad.Diodon.gschema.xml.in.in -> 
> _build_/data/net.launchpad.Diodon.gschema.xml.in
> [29/70] intltool: data/diodon.desktop.in -> _build_/data/diodon.desktop
> [30/70] intltool: data/diodon-autostart.desktop.in -> 
> _build_/data/diodon-autostart.desktop
> [31/70] subst_pc: data/diodon.pc.in -> _build_/data/diodon.pc
> [32/70] valac: libdiodon/clipboard-configuration.vala 
> libdiodon/clipboard-item.vala libdiodon/clipboard-manager.vala 
> libdiodon/clipboard-menu-item.vala libdiodon/clipboard-menu.vala 
> libdiodon/clipboard-type.vala libdiodon/controller.vala 
> libdiodon/file-clipboard-item.vala libdiodon/image-clipboard-item.vala 
> libdiodon/preferences-view.vala libdiodon/primary-clipboard-manager.vala 
> libdiodon/text-clipboard-item.vala libdiodon/utility.vala 
> libdiodon/zeitgeist-clipboard-storage.vala -> _build_/libdiodon/diodon.h 
> _build_/libdiodon/diodon.vapi _build_/libdiodon/Diodon-1.0.gir 
> _build_/libdiodon/diodon.deps _build_/libdiodon/clipboard-configuration.c 
> _build_/libdiodon/clipboard-item.c _build_/libdiodon/clipboard-manager.c 
> _build_/libdiodon/clipboard-menu-item.c _build_/libdiodon/clipboard-menu.c 
> _build_/libdiodon/clipboard-type.c _build_/libdiodon/controller.c 
> _build_/libdiodon/file-clipboard-item.c 
> _build_/libdiodon/image-clipboard-item.c _build_/libdiodon/preferences-view.c 
> _build_/libdiodon/primary-clipboard-manager.c 
> _build_/libdiodon/text-clipboard-item.c _build_/libdiodon/utility.c 
> _build_/libdiodon/zeitgeist-clipboard-storage.c
> [33/70] intltool: plugins/indicator/indicator.plugin.in -> 
> _build_/plugins/indicator/indicator.plugin
> [34/70] intltool: _build_/data/net.launchpad.Diodon.gschema.xml.in -> 
> _build_/data/net.launchpad.Diodon.gschema.xml
> [35/70] glib_validate_schema: _build_/data/net.launchpad.Diodon.gschema.xml 
> -> _build_/data/net.launchpad.Diodon.gschema.xml.valid
> /<>/libdiodon/utility.vala:151.40-151.63: warning: 
> Gdk.Screen.get_active_window has been deprecated since 3.22
> /<>/libdiodon/utility.vala:153.43-153.55: warning: Gdk.X11Window 
> has been deprecated since vala-0.24. Use Gdk.X11.Window
> /<>/libdiodon/zeitgeist-clipboard-storage.vala:33.6-33.42: 
> warning: DBus methods are recommended to throw at least `GLib.Error' or 
> `GLib.DBusError, GLib.IOError'
> /<>/libdiodon/zeitgeist-clipboard-storage.vala:528.40-528.64: 
> warning: GLib.DateTime.from_timeval_utc has been deprecated since 2.62
> /<>/libdiodon/zeitgeist-clipboard-storage.vala:371.36-371.42: 
> warning: GLib.TimeVal has been deprecated since 2.62
> 

Bug#951960: marked as done (purify: FTBFS: ld: ../purify/libpurify.so.2.0.0: undefined reference to `fmt::v6::internal::basic_data::signs')

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 18:50:13 +
with message-id 
and subject line Bug#952543: fixed in spdlog 1:1.5.0+ds-1
has caused the Debian Bug report #952543,
regarding purify: FTBFS: ld: ../purify/libpurify.so.2.0.0: undefined reference 
to `fmt::v6::internal::basic_data::signs'
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.)


-- 
952543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: purify
Version: 2.0.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -std=gnu++11  -Wl,-z,relro -rdynamic 
> CMakeFiles/test_purify_fitsio.dir/purify_fitsio.cc.o 
> CMakeFiles/common_catch_main_object.dir/__/__/common_catch_main.cc.o  -o 
> test_purify_fitsio  
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu/cpp/purify:/usr/lib/x86_64-linux-gnu/openmpi/lib
>  ../purify/libpurify.so.2.0.0 /usr/lib/x86_64-linux-gnu/libfftw3_omp.so 
> /usr/lib/x86_64-linux-gnu/libfftw3.so -lCCfits -lcfitsio 
> /usr/lib/x86_64-linux-gnu/libsopt.so.3.0.1 -ltiff 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
> /usr/lib/x86_64-linux-gnu/libcasa_ms.so 
> /usr/lib/x86_64-linux-gnu/libcasa_measures.so 
> /usr/lib/x86_64-linux-gnu/libcasa_tables.so 
> /usr/lib/x86_64-linux-gnu/libcasa_scimath.so 
> /usr/lib/x86_64-linux-gnu/libcasa_scimath_f.so 
> /usr/lib/x86_64-linux-gnu/libcasa_casa.so -fopenmp 
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::basic_data::signs'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `vtable for 
> fmt::v6::format_error'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int 
> fmt::v6::internal::snprintf_float(double, int, 
> fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::assert_fail(char const*, int, char const*)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::error_handler::on_error(char const*)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `char 
> fmt::v6::internal::decimal_point_impl(fmt::v6::internal::locale_ref)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::basic_data::zero_or_powers_of_10_32'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `char 
> fmt::v6::internal::thousands_sep_impl(fmt::v6::internal::locale_ref)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `typeinfo 
> for fmt::v6::format_error'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `std::__cxx11::basic_string, 
> std::allocator > 
> fmt::v6::internal::grouping_impl(fmt::v6::internal::locale_ref)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int 
> fmt::v6::internal::format_float(long double, int, 
> fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int 
> fmt::v6::internal::snprintf_float(long double, int, 
> fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::format_error::~format_error()'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::basic_data::hex_digits'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::basic_data::digits'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to `int 
> fmt::v6::internal::format_float(double, int, 
> fmt::v6::internal::float_specs, fmt::v6::internal::buffer&)'
> /usr/bin/ld: ../purify/libpurify.so.2.0.0: undefined reference to 
> `fmt::v6::internal::basic_data::zero_or_powers_of_10_64'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/purify_2.0.0-4_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. 

Bug#952543: Using old libfmt breaks sopt and purify

[Michael R. Crusoe]

On Tue, 25 Feb 2020 19:01:02 +0100 "Michael R. Crusoe" 
 wrote:
> On Tue, 25 Feb 2020 15:22:10 +0100 Ole Streicher  
wrote:

>
> > Since spdlog uses the old (included) libfmt, the builds of purify and
> > sopt fail with linker errors like:
> >
> > undefined reference to `fmt::v6::internal::assert_fail(char const*, 
int,

> > char const*)
> >
> > See the merged bugs for the reports. Could you revert this change? Or
> > somehow make it work (I guess, the library itself would need to be
> > included).
>
> Thanks for the report. spdlog 1.5 requires a newer libfmt, otherwise the
> tests don't pass

Sorry, was a local issue with the tests not passing. A repacked spdlog 
has been made without its copy of libfmt and it is on its way to the archive

Processed: Re: [Pkg-javascript-devel] Bug#952312: Bug#952312: node-eslint-scope: FTBFS: tests failed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-espree
Bug #952312 [src:node-eslint-scope] node-eslint-scope: FTBFS: tests failed
Bug reassigned from package 'src:node-eslint-scope' to 'node-espree'.
No longer marked as found in versions node-eslint-scope/4.0.3-4.
Ignoring request to alter fixed versions of bug #952312 to the same values 
previously set
> affects -1 node-eslint-scope
Bug #952312 [node-espree] node-eslint-scope: FTBFS: tests failed
Added indication that 952312 affects node-eslint-scope

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

Bug#952312: [Pkg-javascript-devel] Bug#952312: Bug#952312: node-eslint-scope: FTBFS: tests failed

[Jonas Smedegaard]

control: reassign -1 node-espree
control: affects -1 node-eslint-scope

Quoting Xavier (2020-02-25 18:29:35)
> Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit :
> > During a rebuild of all packages in sid, your package failed to 
> > build on amd64.
> 
> Some test are incompatible with node-espree-6. The fix could be 
> simply:

Certainly not a fix to disable tests.

The package node-espree has exactly one reverse dependency which is 
node-eslint-scope, so this is a case of bad coordination.

(yes, another fix would be to upgrade node-eslint-scope, but that is 
more complex and less urgent, so let's roll back first and work on going 
forward in experimental first)


 - Jonas

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

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

signature.asc
Description: signature

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

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 18:34:45 +
with message-id 
and subject line Bug#943423: fixed in ccfits 2.5+dfsg-2
has caused the Debian Bug report #943423,
regarding libccfits-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.)


-- 
943423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libccfits-doc
Version: 2.5+dfsg-1
Severity: normal

Dear Maintainer,

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

It FTBFS with this error:

/usr/bin/make -C latex
make[2]: Entering directory '/<>/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>

make[2]: *** [Makefile:8: refman.pdf] Error 1
make[2]: Leaving directory '/<>/latex'
make[1]: *** [debian/rules:15: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build] Error 2

More details can be found in the file latex/refman.log at the end of the build.
I attach it.

This had been notified already for doxygen 1.8.15 but the bug was closed:
https://bugs.debian.org/921296

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

-- 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 18:50
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**refman
(./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/base/ifthen.sty
Package: ifthen 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
) (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty
Rollback for package 'array' requested -> date 2016-10-06.
 Best approximation is the release introduced on 2016-10-06.
(/usr/share/texlive/texmf-dist/tex/latex/tools/array-2016-10-06.sty
Package: array 2016/10/06 v2.4d Tabular extension package (FMi)
\col@sep=\dimen103
\extrarowheight=\dimen104
\NC@list=\toks14
\extratabsurround=\skip43
\backup@length=\skip44
)) (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty
Package: fixltx2e 2016/12/29 v2.1a fixes to LaTeX (obsolete)
Applying: [2015/01/01] Old fixltx2e package on input line 46.

Package fixltx2e Warning: fixltx2e is not required with releases after 2015
(fixltx2e)All fixes are now in the LaTeX kernel.
(fixltx2e)See the latexrelease package for details.

Already applied: [/00/00] Old fixltx2e package on input line 53.
) (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty
Package: calc 2017/05/25 v4.3 Infix arithmetic (KKT,FJ)
\calc@Acount=\count88
\calc@Bcount=\count89
\calc@Adimen=\dimen105
\calc@Bdimen=\dimen106
\calc@Askip=\skip45
\calc@Bskip=\skip46
LaTeX Info: Redefining \setlength on input line 80.
LaTeX Info: Redefining \addtolength on input line 81.
\calc@Ccount=\count90
\calc@Cskip=\skip47
) (./doxygen.sty
Package: doxygen 
(/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty
Package: alltt 1997/06/16 v2.0g defines alltt environment
) (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty
Package: float 2001/11/08 v1.3d Float enhancements (AL)
\c@float@type=\count91
\float@exts=\toks15
\float@box=\box27
\@float@everytoks=\toks16
\@floatcapt=\box28
) (/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty
Package: verbatim 2014/10/28 v1.5q LaTeX2e package for 

Bug#943423: troubles generating refman.pdf

[Aurelien Jarno]

Hi,

On 2020-02-05 15:04, Gordon, Craig A. (GSFC-660.1)[INNOVIM] wrote:
> Hi Paolo,
> 
> It was never intended for end users to have to generate the CCfits manual 
> themselves (nor is it intended to be compatible with all versions of 
> Doxygen).  That's why CCfits-2.5.pdf is included with the stand-alone 
> distribution.  Is there a special reason you're trying to run "make docs"?  
> Because otherwise I wouldn't recommend doing that.

In Debian we have a rule requiring that everything, including
documentation, is rebuild from sources.

I have finally been able to build the documentation with the attached
patch. It fixes two issues:
- Newer versions of doxygen now interpret "" in "KeyData" as an
  the underline HTML command. The patch escapes it so that it is not
  interpreted anymore.
- Newer versions of doxygen have markdown support enabled by default,
  causing indented lines to be interpreted as the verbatim code.

Best regards,
Aurelien Jarno

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- a/Doxyfile.in
+++ b/Doxyfile.in
@@ -1758,3 +1758,13 @@ GENERATE_LEGEND= YES
 # the various graphs.
 
 DOT_CLEANUP= YES
+
+# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
+# according to the Markdown format, which allows for more readable
+# documentation. See https://daringfireball.net/projects/markdown/ for details.
+# The output of markdown processing is further processed by doxygen, so you can
+# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
+# case of backward compatibilities issues.
+
+MARKDOWN_SUPPORT   = NO
+
--- a/Keyword.h
+++ b/Keyword.h
@@ -155,7 +155,7 @@ namespace CCfits {
\param val (T) Will be filled with the keyword value, and is also the function return value.
 
Allowed T types: CCfits stores keyword values of type U in a templated subclass of
-   Keyword, KeyData.  Normally U is set when reading the Keyword in from the file, 
+   Keyword, KeyData\.  Normally U is set when reading the Keyword in from the file, 
and is limited to types int, double, string, bool, and complex.
(The exception is when the user has created and added a new Keyword using an
HDU::addKey function, in which case they might have specified other types for U.)  
@@ -180,7 +180,7 @@ namespace CCfits {
\param newValue (T) New value for the Keyword
 
Allowed T types: This must copy newValue to a data member of type U in the
-   Keyword subclass KeyData (see description for Keyword::value (T& val) for more
+   Keyword subclass KeyData\ (see description for Keyword::value (T& val) for more
details).  To avoid compilation errors, it is generally best to provide a newValue
of type T = type U, though the following type conversions will also be handled:
 


signature.asc
Description: PGP signature

Bug#952543: Using old libfmt breaks sopt and purify

[Michael R. Crusoe]

On Tue, 25 Feb 2020 15:22:10 +0100 Ole Streicher  wrote:

> Since spdlog uses the old (included) libfmt, the builds of purify and
> sopt fail with linker errors like:
>
> undefined reference to `fmt::v6::internal::assert_fail(char const*, int,
> char const*)
>
> See the merged bugs for the reports. Could you revert this change? Or
> somehow make it work (I guess, the library itself would need to be
> included).

Thanks for the report. spdlog 1.5 requires a newer libfmt, otherwise the 
tests don't pass


libfmt 6.1.2 has been uploaded to experimental: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950857 and I just 
confirmed that it allows the spdlog tests to pass


So libfmt-dev >= 6.1.2 reaches sid we can rebuild its downstream packages.

Processed: Re: Bug#952335: [Pkg-javascript-devel] Bug#952335: uglify-js: FTBFS: ERROR: `m` is not a supported option

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-commander
Bug #952335 [src:uglify-js] uglify-js: FTBFS: ERROR: `m` is not a supported 
option
Bug reassigned from package 'src:uglify-js' to 'node-commander'.
No longer marked as found in versions uglify-js/3.6.3-1.
Ignoring request to alter fixed versions of bug #952335 to the same values 
previously set
> affects -1 uglify-js
Bug #952335 [node-commander] uglify-js: FTBFS: ERROR: `m` is not a supported 
option
Added indication that 952335 affects uglify-js

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

Bug#952335: [Pkg-javascript-devel] Bug#952335: uglify-js: FTBFS: ERROR: `m` is not a supported option

[Jonas Smedegaard]

control: reassign -1 node-commander
control: affects -1 uglify-js

Quoting Xavier (2020-02-25 18:43:53)
> Le 23/02/2020 à 14:31, Lucas Nussbaum a écrit :
> > During a rebuild of all packages in sid, your package failed to 
> > build on amd64.
> 
> At least uglify-js (https://salsa.debian.org/js-team/uglifyjs) is 
> incompatible with node-commander 4

Then it seems node-commander upgrade (done by you, Xavier) was badly 
coordinated and should be reverted.


 - Jonas

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

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

signature.asc
Description: signature

Bug#952546: bootstrap.min.js in pydoctor

[Jonas Smedegaard]

Quoting Ian Jackson (2020-02-25 18:40:47)
> For -devel, context is that Anthony Fok just uploaded a new upstream 
> version of pydoctor (a tool for extracting API docs for python 
> modules) in order to fix a couple of upstream bugs.  Anthony, thank 
> you very much for your work to help fix one of our (mutual) indirect 
> dependencies.
> 
> Unfortunately the new pydoctor has some DFSG issues (#952546, CC'd).
> 
> I am hoping that -devel can advise what the conventional approach is 
> to the package containing a sourceless copy of bootstrap.min.js.
> 
> I'm guessing that the answer is to strip the sourceless file from the 
> package, and have the binary package contain a symlink into the file 
> tree of some other package which contains an appropriate bootstrap 
> file ?  But is this right, and if so which package ?
> 
> I vaguely remembered this having been discussed before but I couldn't 
> find the conclusions written down anywhere.  I looked in quite a few 
> places for answers to this: I searched the lintian tags for missing 
> source, but they all seemed quite generic.  I tried to search -devel 
> archives for "bootstrap" (too many hits) and "bootstrap.min.js" 
> (nothing relevant).  I tried various wiki searches too.

If you need Bootstrap 3.x, then add symlink to path 
/usr/share/javascript/bootstrap/js/bootstrap.min.js and depend on 
package libjs-bootstrap.

If instead you need Bootstrap 4.x, then you should do something similar 
but for some path below /usr/share/javascript/bootstrap4 and package 
libjs-bootstrap4 (I am vague here because that package apparently use a 
symlink internally requiring actually installing the package to know for 
certain which exact path it is - no, you should *not* link below 
/usr/share/nodejs as that path is not reliable).

 - Jonas

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

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

signature.asc
Description: signature

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

[Lisandro Damián Nicanor Pérez Meyer]

On 20/02/25 01:46, Lisandro Damián Nicanor Pérez Meyer wrote:
> On 20/02/24 09:10, Paul Gevers wrote:
> > Source: clazy
> > Version: 1.6-2
> > Severity: serious
> > Tags: sid bullseye
> > X-Debbugs-CC: debian...@lists.debian.org
> > User: debian...@lists.debian.org
> > Usertags: flaky
> > 
> > Dear maintainer(s),
> 
> Hi Paul, thanks for the bug report.
>  
> > With a recent upload of gcc-10 to unstable, the autopkgtest of clazy
> > failed on arm64 in testing when that autopkgtest was run with the binary
> > packages of gcc-10 from unstable. I looked into the history of your
> > autopkgtest and it fails very often.
> 
> I'm not the direct uploader of this package, but I'll try to fix this.
> This seems to be a failure in llvm/clang though.
> 
> Team members: I'm currently looming at 
> 

I *think* the bug is related to the clang/llvm version used, as I think they
mismatched in the autopkgtests. Maybe both debian/control and
debian/test/control should depend upon a specific clang version, and we should
try to rebuild clazy with each new version as possible, as we do with
qt creator.

Bug#952335: [Pkg-javascript-devel] Bug#952335: uglify-js: FTBFS: ERROR: `m` is not a supported option

[Xavier]

Le 23/02/2020 à 14:31, Lucas Nussbaum a écrit :
> Source: uglify-js
> Version: 3.6.3-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.

At least uglify-js (https://salsa.debian.org/js-team/uglifyjs) is
incompatible with node-commander 4

Bug#952546: bootstrap.min.js in pydoctor

[Ian Jackson]

For -devel, context is that Anthony Fok just uploaded a new upstream
version of pydoctor (a tool for extracting API docs for python
modules) in order to fix a couple of upstream bugs.  Anthony, thank
you very much for your work to help fix one of our (mutual) indirect
dependencies.

Unfortunately the new pydoctor has some DFSG issues (#952546, CC'd).

I am hoping that -devel can advise what the conventional approach is
to the package containing a sourceless copy of bootstrap.min.js.

I'm guessing that the answer is to strip the sourceless file from the
package, and have the binary package contain a symlink into the file
tree of some other package which contains an appropriate bootstrap
file ?  But is this right, and if so which package ?

I vaguely remembered this having been discussed before but I couldn't
find the conclusions written down anywhere.  I looked in quite a few
places for answers to this: I searched the lintian tags for missing
source, but they all seemed quite generic.  I tried to search -devel
archives for "bootstrap" (too many hits) and "bootstrap.min.js"
(nothing relevant).  I tried various wiki searches too.

(The d/copyright problem with epydoc should be easy if tedious to fix;
I don't understand why it wants epydoc which I thought was obsolete
but this is far from my field of expertise.)

Regards,
Ian.

Bug#948940: Merge requests for FTBFS in Qt/KDE packages

[John Scott]

I have now prepared merge requests for fixing ktp-common-internals, 
ktp-accounts-kcm,
and kaccounts-providers respectively [1] [2] [3]. These issues are all fixed in
new upstream releases, but I am not comfortable with such an undertaking and
hope these fixes will suffice in the meantime.

[1] 
https://salsa.debian.org/qt-kde-team/kde/ktp-common-internals/-/merge_requests/1
[2] 
https://salsa.debian.org/qt-kde-team/kde/kaccounts-providers/-/merge_requests/2
[3] https://salsa.debian.org/qt-kde-team/kde/ktp-accounts-kcm/-/merge_requests/1

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

Bug#952312: [Pkg-javascript-devel] Bug#952312: node-eslint-scope: FTBFS: tests failed

[Xavier]

Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit :
> Source: node-eslint-scope
> Version: 4.0.3-4
> 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.

MR not allowed to this project. Some test are incompatible with
node-espree-6. The fix could be simply:


--- a/debian/rules
+++ b/debian/rules
@@ -15,6 +15,8 @@ endif

 # Work around missing node module "typescript-eslint-parser"
 TEST_EXCLUDES += tests/typescript.js
+TEST_EXCLUDES += tests/es6-export.js
+TEST_EXCLUDES += tests/es6-super.js

 override_dh_auto_build: $(DOCS) $(CHANGELOGS)

Bug#950926: ember: Using packages to install "snap" packages is not a correct use of the packaging system

[Simon McVittie]

On Tue, 25 Feb 2020 at 15:02:21 +, Jonathan Dowland wrote:
> It would be interesting to see whether game-data-packager could consume
> data from snaps, and avoid all these pitfalls.

That would remove the sandboxing and known-runtime-libraries properties
of the snap packaging system. I wouldn't recommend that. The apt/dpkg
packaging system is set up for a single, system-wide dependency
tree. That's great for binaries that were built within the scope of
that dependency tree, but unsuitable for binaries that were built with
different assumptions (unless the binaries were deliberately built to
have minimal dependencies, like the few proprietary binary-only games
supported by game-data-packager, or with no assumptions at all, like the
data for Free game engines that is the majority of what game-data-packager
deals with).

If what you want is to install Snap packages, then I would suggest
installing Snap packages (perhaps through something like GNOME Software,
which knows about multiple ways to install software). Not every piece
of software has to be delivered as a .deb.

If ember is no longer feasible to package as a .deb in Debian, then only
releasing new versions of it as Snap packages (or Flatpak or AppImage
or whatever) is perfectly reasonable; but in that case, I don't think
a .deb package that installs those other-packaging-system packages from
third-party repositories is a great upgrade path.

> I believe smcv was
> interested in something similar for flatpaks (that might have been
> installing into flatpaks, rather than consuming from them)

Off-topic for Ember:

Yes, this is the other way round. I wanted to be able to turn games
(particularly proprietary games like Unreal 1) into Flatpak packages as
an alternative to .deb (and .rpm and Arch Linux packages, which should
now mostly work too). Some of the same reasoning would apply equally to
turning those games into Snap packages, although I think Flatpak is a
better fit, so I don't plan to work on that myself.

Why I wanted to do that:

- Flatpak apps are, or can be configured to be, sandboxed (placed in a
  limited container without access to, for example, ~/.ssh). Snap has the
  same idea, although the details are different (Flatpak is likely to be
  a lot better-confined on systems that don't have Ubuntu's non-upstream
  kernel patches for better AppArmor).

- Flatpak apps run on a set of libraries that don't have to match the ones
  on the host system, so we can run proprietary games from the distant past
  in (for example) a Debian-10-based container that has SDL 1, GTK 2, etc.
  without having to keep those libraries in the development branch of Debian
  forever. I think Snap can do the same thing, but the details of how it
  achieves it are rather different.

- Flatpak apps can be installed "for just me" (in ~/.local/share)
  unprivileged, or system-wide (into /var/lib) with appropriate privileges.
  I don't think Snap apps can be installed per-user without exercising
  privileges.

- Identical files in Flatpak apps are automatically deduplicated by
  content (this is relevant if you have overlapping games installed,
  like Unreal, Unreal Gold and Unreal Tournament). I don't think Snap
  does this.

smcv

Bug#952234: marked as done (liblog4ada: FTBFS: ! LaTeX Error: File `letltxmacro.sty' not found.)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 17:11:10 +
with message-id 
and subject line Bug#952234: fixed in liblog4ada 1.3.1.b6dafb49-2
has caused the Debian Bug report #952234,
regarding liblog4ada: FTBFS: ! LaTeX Error: File `letltxmacro.sty' 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.)


-- 
952234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblog4ada
Version: 1.3-5
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[2]: Entering directory '/<>/doc'
> pdflatex -draftmode log4Ada.tex
> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./log4Ada.tex
> LaTeX2e <2020-02-02> patch level 2
> L3 programming layer <2020-02-14>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2019/12/20 v1.4l Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/pdftexcmds/pdftexcmds.sty
> (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty)
> 
> ! LaTeX Error: File `letltxmacro.sty' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
> 
> Enter file name: 
> ! Emergency stop.
>  
>  
> l.132 \RequirePackage{letltxmacro}[2008/06/13]
>   ^^M
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on log4Ada.log.
> make[2]: *** [GNUmakefile:4: log4Ada.aux] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/liblog4ada_1.3-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: liblog4ada
Source-Version: 1.3.1.b6dafb49-2
Done: Nicolas Boulenguez 

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated liblog4ada package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Feb 2020 17:11:38 +0100
Source: liblog4ada
Architecture: source
Version: 1.3.1.b6dafb49-2
Distribution: unstable
Urgency: medium
Maintainer: Xavier Grave 
Changed-By: Nicolas Boulenguez 
Closes: 952234
Changes:
 liblog4ada (1.3.1.b6dafb49-2) unstable; urgency=medium
 .
   * Reupload to unstable for gnat-9 transition.
   * Build-Depend texlive-latex-extra. Closes: #952234.
   * Debhelper 12 dh-sequence syntax.
   * Standards-Version: 4.5.0.
   * Drop redundant branch from Vcs-Git.
Checksums-Sha1:
 

Bug#952288: [Pkg-javascript-devel] Bug#952288: jssip: FTBFS: Error: module debug in /<>/lib not found

[Xavier]

Le 23/02/2020 à 14:44, Lucas Nussbaum a écrit :
> Source: jssip
> Version: 0.6.34-5
> 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.

I asked a ROM-RM for this useless & unmaintained package

Bug#952216: marked as done (node-prelude-ls: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 16:50:40 +
with message-id 
and subject line Bug#952216: fixed in node-prelude-ls 1.1.2+dfsg-5
has caused the Debian Bug report #952216,
regarding node-prelude-ls: FTBFS: dh_auto_test: error: /bin/sh -e 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
952216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-prelude-ls
Version: 1.1.2+dfsg-4
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[2]: Entering directory '/<>'
> mkdir -p lib/
> /usr/bin/lsc --compile package.json.ls
> /usr/bin/lsc --output lib --bare --compile "src/Func.ls"
> /usr/bin/lsc --output lib --bare --compile "src/List.ls"
> /usr/bin/lsc --output lib --bare --compile "src/Num.ls"
> /usr/bin/lsc --output lib --bare --compile "src/Obj.ls"
> /usr/bin/lsc --output lib --bare --compile "src/Str.ls"
> /usr/bin/lsc --output lib --bare --compile "src/index.ls"
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
> 
> Run tests with Mocha
> 
> Rules & Behavior
>   --allow-uncaught   Allow uncaught errors to propagate
> [boolean]
>   --async-only, -A   Require all tests to use a callback (async) or
>  return a Promise  
> [boolean]
>   --bail, -b Abort ("bail") after first test failure   
> [boolean]
>   --check-leaks  Check for global variable leaks   
> [boolean]
>   --delayDelay initial execution of root suite 
> [boolean]
>   --exit Force Mocha to quit after tests complete  
> [boolean]
>   --forbid-only  Fail if exclusive test(s) encountered 
> [boolean]
>   --forbid-pending   Fail if pending test(s) encountered   
> [boolean]
>   --global, --globalsList of allowed global variables
> [array]
>   --retries  Retry failed tests this many times 
> [number]
>   --slow, -s Specify "slow" test threshold (in milliseconds)
>   [string] [default: 
> 75]
>   --timeout, -t, --timeouts  Specify test timeout threshold (in milliseconds)
> [string] [default: 
> 2000]
>   --ui, -u   Specify user interface[string] [default: 
> "bdd"]
> 
> Reporting & Output
>   --color, -c, --colors Force-enable color output  
> [boolean]
>   --diffShow diff on failure
>[boolean] [default: 
> true]
>   --full-trace  Display full stack traces  
> [boolean]
>   --growl, -G   Enable Growl notifications 
> [boolean]
>   --inline-diffsDisplay actual/expected 
> differences
> inline within each string  
> [boolean]
>   --reporter, -RSpecify reporter to use
>   [string] [default: 
> "spec"]
>   --reporter-option, --reporter-options,Reporter-specific options
>   -O()   
> [array]
> 
> Configuration
>   --config   Path to config file   [string] [default: (nearest rc 
> file)]
>   --opts Path to `mocha.opts` (DEPRECATED)
>  [string] [default: 
> "./test/mocha.opts"]
>   --package  Path to package.json for config
> [string]
> 
> File Handling
>   --extension  File extension(s) to load   [array] [default: 
> js]
>   --file   Specify file(s) to be loaded prior to root suite
>execution   [array] [default: 
> (none)]
>   --ignore, --exclude  Ignore file(s) or glob pattern(s)
>[array] [default: 
> (none)]
>   --recursive  Look for tests in subdirectories
> [boolean]
>   --require, -rRequire module  [array] [default: 
> (none)]
>   

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

[Lisandro Damián Nicanor Pérez Meyer]

On 20/02/24 09:10, Paul Gevers wrote:
> Source: clazy
> Version: 1.6-2
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
> 
> Dear maintainer(s),

Hi Paul, thanks for the bug report.
 
> With a recent upload of gcc-10 to unstable, the autopkgtest of clazy
> failed on arm64 in testing when that autopkgtest was run with the binary
> packages of gcc-10 from unstable. I looked into the history of your
> autopkgtest and it fails very often.

I'm not the direct uploader of this package, but I'll try to fix this.
This seems to be a failure in llvm/clang though.

Team members: I'm currently looming at 


Cheers, Lisandro.

Bug#952170: libconfig-model-dpkg-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255

[Dominique Dumont]

On dimanche 23 février 2020 14:09:03 CET you wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

The failed test depend on licensecheck behavior. A bug in this package was 
recently fixed, which led to this test failure.

I'll fix this test.

All the best

Dod

Bug#951983: marked as done (git-buildpackage: FTBFS: ImportError: No module named cachecontrol)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 16:00:13 +
with message-id 
and subject line Bug#948831: fixed in pydoctor 19.11.0+git20200114.c74016b-1
has caused the Debian Bug report #948831,
regarding git-buildpackage: FTBFS: ImportError: No module named cachecontrol
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.)


-- 
948831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-buildpackage
Version: 0.9.18
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> mkdir -p build
> pydoctor -v --config=.pydoctor.cfg
> Traceback (most recent call last):
>   File "/usr/bin/pydoctor", line 10, in 
> from pydoctor.driver import main
>   File "/usr/lib/python2.7/dist-packages/pydoctor/driver.py", line 5, in 
> 
> from pydoctor import model, zopeinterface
>   File "/usr/lib/python2.7/dist-packages/pydoctor/model.py", line 19, in 
> 
> from pydoctor.sphinx import SphinxInventory
>   File "/usr/lib/python2.7/dist-packages/pydoctor/sphinx.py", line 10, in 
> 
> from cachecontrol import CacheControl
> ImportError: No module named cachecontrol
> make[3]: *** [Makefile:29: apidocs] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/git-buildpackage_0.9.18_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: pydoctor
Source-Version: 19.11.0+git20200114.c74016b-1
Done: Anthony Fok 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 23 Feb 2020 07:34:00 -0700
Source: pydoctor
Binary: pydoctor python-pydoctor
Architecture: source all
Version: 19.11.0+git20200114.c74016b-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Anthony Fok 
Description:
 pydoctor   - Python API document generator
 python-pydoctor - transitional package
Closes: 937421 948831 949232
Changes:
 pydoctor (19.11.0+git20200114.c74016b-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 19.11.0+git20200114.c74016b
   * debian/watch: Track HEAD on GitHub for now for python3 compatibility.
   * Apply "cme fix dpkg" fixes:
 - Bump Standards-Version to 4.5.0 (no change)
 - Reformat debian/control for easier human reading
 - Change license shortname "MIT" to "Expat" in debian/copyright
   * Remove dependency on python-nevow which upstream has stopped using
 since 2013.
   * Switch to Python 3, and rename binary package to pydoctor
 because it is a Python application and not used as a module.
 Also add explicit dependency on python3-lockfile as recommended
 by Andrej Shadura. (Closes: #937421, #948831, #949232)
   * debian/rules: Change "dh $*" to "dh $@" (Lintian I: no-dh-sequencer)
Checksums-Sha1:
 42af049de89771b9887c441d1c64ec258b2c1949 2227 
pydoctor_19.11.0+git20200114.c74016b-1.dsc
 82c18bbe797032da55a614aa636be73330724d18 90952 
pydoctor_19.11.0+git20200114.c74016b.orig.tar.xz
 49d494f7872091dd3196912062e7bb9ab4884895 6344 
pydoctor_19.11.0+git20200114.c74016b-1.debian.tar.xz
 488c860ded8db30a94295d5f63c94a943471ec1d 8456 
pydoctor_19.11.0+git20200114.c74016b-1_all.deb
 a346cc428ecadc2806b4bb4bb4157f06982fbe21 6969 
pydoctor_19.11.0+git20200114.c74016b-1_amd64.buildinfo
 8e1a43623b277f65fa61134d8cd2229079a76971 4448 

Bug#948831: marked as done (git-buildpackage: FTBFS: ImportError: No module named cachecontrol)

[Debian Bug Tracking System]

Your message dated Tue, 25 Feb 2020 16:00:13 +
with message-id 
and subject line Bug#948831: fixed in pydoctor 19.11.0+git20200114.c74016b-1
has caused the Debian Bug report #948831,
regarding git-buildpackage: FTBFS: ImportError: No module named cachecontrol
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.)


-- 
948831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-buildpackage
Version: 0.9.17
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in standard sid chroot:

make[3]: Entering directory '/build/1st/git-buildpackage-0.9.17'
mkdir -p build
pydoctor -v --config=.pydoctor.cfg
Traceback (most recent call last):
  File "/usr/bin/pydoctor", line 10, in 
from pydoctor.driver import main
  File "/usr/lib/python2.7/dist-packages/pydoctor/driver.py", line 5, in 

from pydoctor import model, zopeinterface
  File "/usr/lib/python2.7/dist-packages/pydoctor/model.py", line 19, in 

from pydoctor.sphinx import SphinxInventory
  File "/usr/lib/python2.7/dist-packages/pydoctor/sphinx.py", line 10, in 

from cachecontrol import CacheControl
ImportError: No module named cachecontrol
make[3]: *** [Makefile:29: apidocs] Error 1
make[3]: Leaving directory '/build/1st/git-buildpackage-0.9.17'
make[2]: *** [Makefile:25: docs] Error 2
make[2]: Leaving directory '/build/1st/git-buildpackage-0.9.17'
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/1st/git-buildpackage-0.9.17'
make: *** [debian/rules:18: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pydoctor
Source-Version: 19.11.0+git20200114.c74016b-1
Done: Anthony Fok 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 23 Feb 2020 07:34:00 -0700
Source: pydoctor
Binary: pydoctor python-pydoctor
Architecture: source all
Version: 19.11.0+git20200114.c74016b-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Anthony Fok 
Description:
 pydoctor   - Python API document generator
 python-pydoctor - transitional package
Closes: 937421 948831 949232
Changes:
 pydoctor (19.11.0+git20200114.c74016b-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 19.11.0+git20200114.c74016b
   * debian/watch: Track HEAD on GitHub for now for python3 compatibility.
   * Apply "cme fix dpkg" fixes:
 - Bump Standards-Version to 4.5.0 (no change)
 - Reformat debian/control for easier human reading
 - Change license shortname "MIT" to "Expat" in debian/copyright
   * Remove dependency on python-nevow which upstream has stopped using
 since 2013.
   * Switch to Python 3, and rename binary package to pydoctor
 because it is a Python application and not used as a module.
 Also add explicit dependency on python3-lockfile as recommended
 by Andrej Shadura. (Closes: #937421, #948831, #949232)
   * debian/rules: Change "dh $*" to "dh $@" (Lintian I: no-dh-sequencer)
Checksums-Sha1:
 42af049de89771b9887c441d1c64ec258b2c1949 2227 
pydoctor_19.11.0+git20200114.c74016b-1.dsc
 82c18bbe797032da55a614aa636be73330724d18 90952 
pydoctor_19.11.0+git20200114.c74016b.orig.tar.xz
 49d494f7872091dd3196912062e7bb9ab4884895 6344 
pydoctor_19.11.0+git20200114.c74016b-1.debian.tar.xz
 488c860ded8db30a94295d5f63c94a943471ec1d 8456 

Bug#950926: ember: Using packages to install "snap" packages is not a correct use of the packaging system

[Jonathan Dowland]

On Sun, Feb 09, 2020 at 11:12:48PM +0100, Manuel A. Fernandez Montecelo wrote:

2) These kind of methods are done for special packages like firmware,
very popular apps like flash (at the time), etc, or *data* packages
from games.


We have game-data-packager (gdp, which I originally wrote) for
situations like this. When you generate a .deb (as gdb does) containing
the data and install that, you get an Installed-Size which reflects the
actual disk usage of the package; you know that data is removed again
when you remove the package; you can express package inter-dependencies
properly, etc.

The ember package, at present

• claims to have an Installed-Size of 35.8 kB but will install
  177+MiB in pre-inst
• Does not clean that up again on package removal
• Doesn't handle "snap install" failing, silently completes package
  installation
• Supplies a .desktop file referencing Exec=ember but does not provide
  any ember binary (even as a route into the snap) in $PATH

It would be interesting to see whether game-data-packager could consume
data from snaps, and avoid all these pitfalls. I believe smcv was
interested in something similar for flatpaks (that might have been
installing into flatpaks, rather than consuming from them)


--
  Jonathan Dowland
   https://jmtd.net

Processed: Bug#951956 marked as pending in manila

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #951956 [src:manila] manila: FTBFS: testtools.matchers._impl.MismatchError: 
[(4, 21, 'M310')] != [(4, 20, 'M310')]
Added tag(s) pending.

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

Processed: py2removal bugs severity updates - 2020-02-25 15:35:19.203816+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-parsley is a module and has 0 external rdeps or not in testing
> severity 937241 serious
Bug #937241 [src:parsley] parsley: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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