Bug#973010: [pcp] Bug#973010: pcp is uninstallable on many architectures due to new bpftrace dependency

[Nathan Scott]

On Wed, Oct 28, 2020 at 7:56 AM Martin Pitt  wrote:
>
> Package: pcp
> Version: 5.2.1-1
> [...]
> But the "bpftrace" package only exists on a few architectures [1]. This is 
> what
> makes the package uninstallable and prevents testing migration [2].
>
> Please fix
> that at least by restricting the architectures, like so:

Thanks Martin - we'll tackle this in the next update (pcp-5.2.2,
couple weeks out).

>   Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, 
> libpcp-pmda-perl, python3-pcp, python3, bpftrace (>= 0.9.2) [amd64 arm64 
> ppc64 ppc64el], libpcp-web1
>
> Preferably you would also drop it to Recommends:, as hopefully bpftrace isn't
> an absolute requirement for running PCP? I.e.

It's not an absolute requirement - more of a Suggests: line entry, even.

cheers.

--
Nathan

Bug#973273: python-is-python2 misses Breaks+Replaces: python-minimal

[Helmut Grohne]

Package: python-is-python2
Version: 2.7.18-6
Severity: serious
Justifictaion: fails to install

Upgrading from "python" to "python-is-python" may fail:

| Unpacking python-is-python2 (2.7.18-6) ...
| dpkg: error processing archive 
/var/cache/apt/archives/python-is-python2_2.7.18-6_all.deb (--unpack):
|  trying to overwrite '/usr/bin/python', which is also in package 
python-minimal 2.7.17-2
| Errors were encountered while processing:
|  /var/cache/apt/archives/python-is-python2_2.7.18-6_all.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)

Please add Breaks+Replaces on python-minimal.

Helmut

Processed: FTBFS supysonic

[Debian Bug Tracking System]

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

> block 973034 by 973191
Bug #973034 [src:supysonic] supysonic's autopkg tests are failing with python3.9
973034 was blocked by: 972717
973034 was not blocking any bugs.
Added blocking bug(s) of 973034: 973191
> merge 972717 973191
Bug #972717 [src:supysonic] supysonic fails tests with python3.9
Bug #972717 [src:supysonic] supysonic fails tests with python3.9
Marked as found in versions supysonic/0.6.0+ds-1.
Added tag(s) ftbfs.
Bug #973191 [src:supysonic] supysonic: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.9 3.8" returned exit code 13
Merged 972717 973191
> thanks
Stopping processing here.

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

Bug#971179: marked as done (python-jenkinsapi: FTBFS: Unable to create file /sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats: [Errno 2] No such file or directory: '/sbuild-nonexistent/.pylint.d/j

[Debian Bug Tracking System]

Your message dated Wed, 28 Oct 2020 03:48:47 +
with message-id 
and subject line Bug#971179: fixed in python-jenkinsapi 0.3.11-4
has caused the Debian Bug report #971179,
regarding python-jenkinsapi: FTBFS: Unable to create file 
/sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats: [Errno 2] No such file 
or directory: '/sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats'
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.)


-- 
971179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jenkinsapi
Version: 0.3.11-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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 '/<>'
> pylint jenkinsapi/*.py
> Unable to create directory /sbuild-nonexistent/.pylint.d
> Unable to create file /sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats: 
> [Errno 2] No such file or directory: 
> '/sbuild-nonexistent/.pylint.d/jenkinsapi.views1.stats'
> * Module jenkinsapi.credential
> jenkinsapi/credential.py:86: [R1725(super-with-arguments), 
> UsernamePasswordCredential.__init__] Consider using Python 3 style super() 
> without arguments
> jenkinsapi/credential.py:126: [R1725(super-with-arguments), 
> UsernamePasswordCredential.get_attributes_xml] Consider using Python 3 style 
> super() without arguments
> jenkinsapi/credential.py:149: [R1725(super-with-arguments), 
> SecretTextCredential.__init__] Consider using Python 3 style super() without 
> arguments
> jenkinsapi/credential.py:182: [R1725(super-with-arguments), 
> SecretTextCredential.get_attributes_xml] Consider using Python 3 style 
> super() without arguments
> jenkinsapi/credential.py:217: [R1725(super-with-arguments), 
> SSHKeyCredential.__init__] Consider using Python 3 style super() without 
> arguments
> jenkinsapi/credential.py:294: [R1725(super-with-arguments), 
> SSHKeyCredential.get_attributes_xml] Consider using Python 3 style super() 
> without arguments
> jenkinsapi/credential.py:320: [R1725(super-with-arguments), 
> AmazonWebServicesCredentials.__init__] Consider using Python 3 style super() 
> without arguments
> jenkinsapi/credential.py:363: [R1725(super-with-arguments), 
> AmazonWebServicesCredentials.get_attributes_xml] Consider using Python 3 
> style super() without arguments
> * Module jenkinsapi.credentials
> jenkinsapi/credentials.py:101: [W0707(raise-missing-from), 
> Credentials.__setitem__] Consider explicitly re-raising using the 'from' 
> keyword
> jenkinsapi/credentials.py:118: [W0707(raise-missing-from), 
> Credentials.__setitem__] Consider explicitly re-raising using the 'from' 
> keyword
> jenkinsapi/credentials.py:146: [W0707(raise-missing-from), 
> Credentials.__delitem__] Consider explicitly re-raising using the 'from' 
> keyword
> * Module jenkinsapi.fingerprint
> jenkinsapi/fingerprint.py:100: [W0707(raise-missing-from), 
> Fingerprint.validate] Consider explicitly re-raising using the 'from' keyword
> jenkinsapi/fingerprint.py:104: [W0707(raise-missing-from), 
> Fingerprint.validate] Consider explicitly re-raising using the 'from' keyword
> * Module jenkinsapi.jenkinsbase
> jenkinsapi/jenkinsbase.py:89: [W0707(raise-missing-from), 
> JenkinsBase.get_data] Consider explicitly re-raising using the 'from' keyword
> * Module jenkinsapi.job
> jenkinsapi/job.py:92: [R1725(super-with-arguments), Job.poll] Consider using 
> Python 3 style super() without arguments
> jenkinsapi/job.py:409: [W0707(raise-missing-from), 
> Job.get_buildnumber_for_revision] Consider explicitly re-raising using the 
> 'from' keyword
> jenkinsapi/job.py:417: [W0707(raise-missing-from), Job.get_build] Consider 
> explicitly re-raising using the 'from' keyword
> jenkinsapi/job.py:432: [W0707(raise-missing-from), Job.delete_build] Consider 
> explicitly re-raising using the 'from' keyword
> jenkinsapi/job.py:447: [W0707(raise-missing-from), Job.get_build_metadata] 
> Consider explicitly re-raising using the 'from' keyword
> * Module jenkinsapi.node
> jenkinsapi/node.py:122: [W0707(raise-missing-from), Node.get_node_attributes] 
> Consider explicitly re-raising using the 'from' keyword
> * Module jenkinsapi.nodes
> jenkinsapi/nodes.py:79: [W0707(raise-missing-from), Nodes.iteritems] Consider 
> explicitly re-raising using the 'from' keyword
> jenkinsapi/nodes.py:98: [W0707(raise-missing-from), 

Bug#973136: delve: FTBFS: dh_auto_test: error

[Shengjing Zhu]

Control: severity -1 important
Control: tags -1 unreproducible

On Wed, Oct 28, 2020 at 1:46 AM Lucas Nussbaum  wrote:
>
> Source: delve
> Version: 1.5.0-4
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):

The relevant part is near "FAIL:"

=== RUN   TestIssue1374
   proc_test.go:112: failed assertion at proc_test.go:4211: Call -
could not restore registers: bad address
--- FAIL: TestIssue1374 (0.62s)


However as delve was just built by buildd 11hour ago, and on my
desktop. So this seems a corner case triggered by your environment.
Hence I downgrade the severity.

I guess the difference between buildd, my desktop and your env is real
hardware and VM.
Since delve is a debug tool, like gdb, probably the failed tests are
using some extreme methods which are restricted by VM.

-- 
Shengjing Zhu

Processed: Re: Bug#973136: delve: FTBFS: dh_auto_test: error

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #973136 [src:delve] delve: FTBFS: dh_auto_test: error
Severity set to 'important' from 'serious'
> tags -1 unreproducible
Bug #973136 [src:delve] delve: FTBFS: dh_auto_test: error
Added tag(s) unreproducible.

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

Bug#973094: leiningen-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact commons-io:commons-io:jar:2.6 has not been downloaded from it before.

[Elana Hashman]

Thanks for the report.

Looks like libcommons-io-java has been updated to 2.8.0.[1] We'll need
to patch both the Debian build and send a PR upstream to get it on the
newer version.

- e

[1]: https://packages.debian.org/sid/libcommons-io-java


signature.asc
Description: PGP signature

Bug#947529: marked as done (gnome-chemistry-utils: build-depends on deprecated gnome-doc-utils)

[Debian Bug Tracking System]

Your message dated Wed, 28 Oct 2020 02:33:25 +
with message-id 
and subject line Bug#947529: fixed in gnome-chemistry-utils 0.14.17-4
has caused the Debian Bug report #947529,
regarding gnome-chemistry-utils: build-depends on deprecated gnome-doc-utils
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.)


-- 
947529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-chemistry-utils
Version: 0.14.17-2
Severity: important
Control: block 936625 by -1
Control: block 889019 by -1
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gnome-doc-utils

This package Build-Depends on gnome-doc-utils. gnome-doc-utils is a
deprecated package of documentation utilities. Its most recent upstream
release was in 2012, with most changes in its git repository since then
being translation updates. The GNOME team do not consider gnome-doc-utils
to be suitable for release in Debian 11 'bullseye'.

The supported replacement is yelp.m4 in yelp-tools, as used
in many GNOME 3 packages. A porting guide is available:
https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure

gnome-doc-utils relies on Python 2 code that seems unlikely to be
converted to Python 3, so bug #936625 (part of the effort to remove
Python 2 from Debian for Debian 11 'bullseye') has its severity set to
serious. This means that this bug is highly likely to be elevated to
serious severity at some point in future.

Please convert this package to use yelp-tools, or if necessary remove
the documentation processing entirely.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-chemistry-utils
Source-Version: 0.14.17-4
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated gnome-chemistry-utils 
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, 28 Oct 2020 02:33:10 +0100
Source: gnome-chemistry-utils
Architecture: source
Version: 0.14.17-4
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Daniel Leidert 
Closes: 830039 887117 947529
Changes:
 gnome-chemistry-utils (0.14.17-4) unstable; urgency=medium
 .
   * d/compat: Remove obsolete file.
   * d/control: Add Rules-Requires-Root field.
 (Build-Depends): Replace gnome-doc-utils by yelp-tools. Use
 debhelper-compat 12.
 (Standards-Version): Bump to 4.5.0.
   * d/copyright (Files): Fix redundant-globbing-patterns.
 (Copyright): Update copyright.
   * d/*.install: Fix the help path and remove the scrollkeeper path.
   * d/rules (LDFLAGS): Fix debian-rules-uses-as-needed-linker-flag.
 (override_dh_install): Install scripts for gchem3d and gcrystal to set
 GDK_BACKEND=x11 (closes: #887117).
   * d/patches/gnumeric-ftbfs.patch: Refresh patch and add DEP3 headers.
   * d/patches/openbabel-v3.patch: Dito.
   * d/patches/use-yelp.patch: Add patch (closes: #947529).
 - Rewrite source to use yelp-tools instead of gnome-doc-utils.
   * d/patches/remove-gnome-common.patch: Add patch.
 - Remove remaining references to gnome-common (closes: #830039).
   * d/patches/series: Enable new patch.
   * d/scripts/gchem3d, d/scripts/gcrystal: Add new files.
   * d/tests/control: Add basic tests and run all final executables.
Checksums-Sha1:
 a0cfcede70334ae744e0fe2b28fcd3641ea04cbe 2824 
gnome-chemistry-utils_0.14.17-4.dsc
 eade519591adbde32e5ebd0e8203378079a0b556 67496 
gnome-chemistry-utils_0.14.17-4.debian.tar.xz
 fc808cab331eb00062344859ec9863233ceee4d1 18288 
gnome-chemistry-utils_0.14.17-4_amd64.buildinfo
Checksums-Sha256:
 85a14e981662e3c5f0e23da796fbde7a10b11a5a687e3dbca28b7e42eb0afab8 2824 
gnome-chemistry-utils_0.14.17-4.dsc
 8736f0184977824630c79b2f90c9cc1b16c20e53284527d4c96e7c523fe13bad 67496 
gnome-chemistry-utils_0.14.17-4.debian.tar.xz
 762fe940051df93d6aaa0537efdab1d91bcef19d1a1052983634c7e0ced529a9 18288 

Bug#973170: node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Xavier]

Control: reassign -1 node-fetch
Control: affects -1 node-formidable

Le 27/10/2020 à 18:07, Lucas Nussbaum a écrit :
> Source: node-formidable
> Version: 1.2.1+20200129git8231ea6-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Test works fine using node-fetch installed using npm (same version but
code differs).

Processed: Re: Bug#973170: node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-fetch
Bug #973170 [src:node-formidable] node-formidable: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Bug reassigned from package 'src:node-formidable' to 'node-fetch'.
No longer marked as found in versions 
node-formidable/1.2.1+20200129git8231ea6-1.
Ignoring request to alter fixed versions of bug #973170 to the same values 
previously set
> affects -1 node-formidable
Bug #973170 [node-fetch] node-formidable: FTBFS: dh_auto_test: error: /bin/sh 
-ex debian/tests/pkg-js/test returned exit code 1
Added indication that 973170 affects node-formidable

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

Bug#973081: [Pkg-javascript-devel] Bug#973081: pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined

[Xavier]

Control: reassign -1 webpack
Control: affects -1 src:pdf.js

Le 27/10/2020 à 18:09, Lucas Nussbaum a écrit :
> Source: pdf.js
> Version: 2.6.347+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 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 '/<>'
>> gulp dist-pre
>> [12:18:24] Local gulp not found in /<>
>> [12:18:24] Try running: npm install gulp
>> [12:18:24] Using globally installed gulp
>> [12:18:24] Using gulpfile /<>/gulpfile.js
>> [12:18:24] Starting 'dist-pre'...
>> [12:18:24] Starting 'generic'...
>> [12:18:24] Starting 'buildnumber'...
>>
>> ### Getting extension build number
>> This is not a Git repository; using default build number.
>> Extension build number: 0
>> [12:18:24] Finished 'buildnumber' after 26 ms
>> [12:18:24] Starting 'default_preferences'...
>> [12:18:24] Starting 'default_preferences-pre'...
>>
>> ### Building `default_preferences.json`
>> Since Acorn 8.0.0, options.ecmaVersion is required.
>> Defaulting to 2020, but this will stop working in the future.
>> [12:18:25] Finished 'default_preferences-pre' after 425 ms
>> [12:18:25] Starting ''...
>> [12:18:25] Finished '' after 3.36 ms
>> [12:18:25] Finished 'default_preferences' after 429 ms
>> [12:18:25] Starting 'locale'...
>>
>> ### Building localization files
>> [12:18:25] Finished 'locale' after 145 ms
>> [12:18:25] Starting ''...
>>
>> ### Creating generic viewer
>> (node:27451) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
>> security and usability issues. Please use the Buffer.alloc(), 
>> Buffer.allocUnsafe(), or Buffer.from() methods instead.
>> [12:18:32] '' errored after 7.53 s
>> [12:18:32] TypeError: Cannot read property 'then' of undefined
>> at /usr/share/nodejs/webpack/lib/Compiler.js:493:44
> failed build was retried once to eliminate random failures.

Problem comes from mkdirp-1 patch

Processed: Re: [Pkg-javascript-devel] Bug#973081: pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 webpack
Bug #973081 [src:pdf.js] pdf.js: FTBFS: [12:18:32] TypeError: Cannot read 
property 'then' of undefined
Bug reassigned from package 'src:pdf.js' to 'webpack'.
No longer marked as found in versions pdf.js/2.6.347+dfsg-1.
Ignoring request to alter fixed versions of bug #973081 to the same values 
previously set
> affects -1 src:pdf.js
Bug #973081 [webpack] pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 
'then' of undefined
Added indication that 973081 affects src:pdf.js

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

Bug#973024: feature-check's autopkg tests are failing, blocking python3-defaults

[Peter Pentchev]

On Tue, Oct 27, 2020 at 01:05:32PM +0100, Matthias Klose wrote:
> Package: src:feature-check
> Version: 0.2.2-5
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9

This is the same as #972530, which was already fixed in 0.2.2-6 on
Monday, however the CI system has not run the tests yet.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#973062: Really an issue in cloud-init?

[Thomas Goirand]

Hi,

To me it looks like an issue in python-httpretty. I'll try to fix
httpretty and rebuild cloud-init, then probably close this bug.

Cheers,

Thomas Goirand (zigo)

Bug#973158: marked as done (postgresql-filedump: FTBFS: decode.c:7:10: fatal error: access/tuptoaster.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 18:53:42 +0100
with message-id <20201027175342.ga106...@msg.df7cb.de>
and subject line Re: Bug#973158: postgresql-filedump: FTBFS: decode.c:7:10: 
fatal error: access/tuptoaster.h: No such file or directory
has caused the Debian Bug report #973158,
regarding postgresql-filedump: FTBFS: decode.c:7:10: fatal error: 
access/tuptoaster.h: No such file or directory
to be marked as done.

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

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


-- 
973158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-filedump
Version: 12.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
> -Werror=vla -Wendif-labels -Wmissing-format-attribute 
> -Wimplicit-fallthrough=3 -Wformat-security -fno-strict-aliasing -fwrapv 
> -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation 
> -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-omit-frame-pointer -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -I. -I./ 
> -I/usr/include/postgresql/13/server -I/usr/include/postgresql/internal  
> -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2   -c -o 
> decode.o decode.c
> decode.c:7:10: fatal error: access/tuptoaster.h: No such file or directory
> 7 | #include 
>   |  ^
> compilation terminated.
> make[2]: *** [: decode.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/postgresql-filedump_12.0-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 ---
Version: 13.0-1

> > decode.c:7:10: fatal error: access/tuptoaster.h: No such file or directory

Fixed in unstable.

(There's still a separate test problem on big endian, but that's a
different problem.)

Christoph--- End Message ---

Bug#973051: marked as done (The generic bulseye image is configured without metadata list)

[Debian Bug Tracking System]

Your message dated Wed, 28 Oct 2020 01:21:08 +0100
with message-id 
and subject line Re: Bug#973051: The generic bulseye image is configured 
without metadata list
has caused the Debian Bug report #973051,
regarding The generic bulseye image is configured without metadata list
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.)


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

Hi,

Testing to start the OpenStack image (well, the "genericcloud" image), I
couldn't login into it, because there isn't any metadata service configured
in it.

After adding this:

# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
datasource_list: [ NoCloud, AltCloud, ConfigDrive, OpenStack, CloudStack, 
DigitalOcean, Ec2, MAAS, OVF, GCE, None ]

which is what the legacy OpenStack image does, and rebooting the instance, I
could login without any problem.

After that, it appears that /etc/hosts wasn't configued at all with the
hostname, therefore, the hostname couldn't be resolved even within the VM
itself. I'm not sure if this is related or not, however.

IMO, this is of severity grave, because the image is not usable without a
tweak (ie: impossible to login).

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Hi Bastian,

Thanks for your answer.

On 10/27/20 6:50 PM, Bastian Blank wrote:
> On Tue, Oct 27, 2020 at 04:54:13PM +0100, Thomas Goirand wrote:
>> Testing to start the OpenStack image (well, the "genericcloud" image), I
>> couldn't login into it, because there isn't any metadata service configured
>> in it.
> 
> This is incorrect.  The package uses
> /lib/systemd/system-generators/cloud-init-generator to generate a
> config.  This works in general:
> 
> | $ cat /run/cloud-init/cloud.cfg 
> | datasource_list: [ Azure, None ]
> 
> So, please provide more information.

Hi,

Looking at the logs, I could see the issue was a ConnectTimeoutError
contacting the metadata server on http://169.254.169.254/openstack, so
that probably was a problem in my OpenStack setup, somehow. That's
surprising, because I tried spawning 10 other instances, and none failed.

I'm therefore closing the bug, sorry for the noise. I should have
checked the logs in the first place...

>> After that, it appears that /etc/hosts wasn't configued at all with the
>> hostname, therefore, the hostname couldn't be resolved even within the VM
>> itself. I'm not sure if this is related or not, however.
> 
> Show logs?  /run/cloud-init/cloud-init-generator.log for example.

This still is a problem, even when the metadata are fetched. So this
would deserve a separate bug, I guess. Though I'm not there yet in terms
of thinking how to fix or if we should do anything for it. Let me expand...

In the logs, I can see:

Configuration option 'manage_etc_hosts' is not set, not managing
/etc/hosts in module update_etc_hosts

Adding:
# cat /etc/cloud/cloud.cfg.d/03_zigo.cfg
manage_etc_hosts: true

made it add a 127.0.1.1 entry with the hostname, though this deletes any
other entry I would manually add, as per the cloud-init doc says (and I
tested that fact).

So I wonder how we can fix it, ie that a 127.0.1.1 is added by default,
at least to get the hostname resolvable (and avoid a warning when
sudoing to root).

>> IMO, this is of severity grave, because the image is not usable without a
>> tweak (ie: impossible to login).
> 
> Severities have no real meaning for non-package resources.

Probably you really mean "no real life consequence"? :)
Hopefully, you'll agree that sorting issue by severity can still be
handy at times.

> And the same
> mechanism clearly works on Azure and EC2 without problems, so it would
> be only "important".

So, Azure is more important? :) 

Thomas--- End Message ---

Bug#972992: j4-dmenu-desktop: dmenu and i3-sensible-terminal missing

[Thierry B.]

For the second error, I missed the "--term=" option to chnage the
default terminal, so the issue is only :

running "j4-dmenu-desktop", "dmenu" is missing. So "suckless-tools"
should be a dependency

Bug#972468: marked as done (nvidia-graphics-drivers-legacy-390xx: module build fails for kernel 5.9.0-1-amd64)

[Debian Bug Tracking System]

Your message dated Wed, 28 Oct 2020 00:18:56 +
with message-id 
and subject line Bug#972468: fixed in nvidia-graphics-drivers-legacy-390xx 
390.138-5
has caused the Debian Bug report #972468,
regarding nvidia-graphics-drivers-legacy-390xx: module build fails for kernel 
5.9.0-1-amd64
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.)


-- 
972468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.138-4
Severity: grave
Justification: renders package unusable
Affects: linux-image-5.9.0-1-amd64

The module build fails for kernel 5.9.0-1-amd64.
See attached log "/var/lib/dkms/nvidia-legacy-390xx/390.138/build/make.log".

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
DKMS make.log for nvidia-legacy-390xx-390.138 for kernel 5.9.0-1-amd64 (x86_64)
2020-10-18T22:33:51 CEST
make KBUILD_OUTPUT=/lib/modules/5.9.0-1-amd64/build V=1 -C 
/lib/modules/5.9.0-1-amd64/source 
M=/var/lib/dkms/nvidia-legacy-390xx/390.138/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/5.9.0-1-amd64/source 
NV_KERNEL_OUTPUT=/lib/modules/5.9.0-1-amd64/build NV_KERNEL_MODULES="nvidia 
nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video NV_SPECTRE_V2=0 
modules
make[1]: Entering directory '/usr/src/linux-headers-5.9.0-1-common'
make -C /usr/src/linux-headers-5.9.0-1-amd64 -f 
/usr/src/linux-headers-5.9.0-1-common/Makefile modules
make[2]: Entering directory '/usr/src/linux-headers-5.9.0-1-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
make -f /usr/src/linux-headers-5.9.0-1-common/scripts/Makefile.build 
obj=/var/lib/dkms/nvidia-legacy-390xx/390.138/build \
single-build= \
need-builtin=1 need-modorder=1
scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
NV_CONFTEST_CMD=/bin/sh 
/var/lib/dkms/nvidia-legacy-390xx/390.138/build/conftest.sh " gcc-10" " gcc-10" 
x86_64 /lib/modules/5.9.0-1-amd64/source /lib/modules/5.9.0-1-amd64/build
NV_CONFTEST_CFLAGS=-O2 -D__KERNEL__ -DKBUILD_BASENAME="#conftest2716232" 
-DKBUILD_MODNAME="#conftest2716232" -nostdinc -isystem 
/usr/lib/gcc/x86_64-linux-gnu/10/include 
-I/lib/modules/5.9.0-1-amd64/source/include/asm-x86/mach-default 
-I/lib/modules/5.9.0-1-amd64/source/arch/x86/include/asm/mach-default 
-I/lib/modules/5.9.0-1-amd64/build/include2 
-I/lib/modules/5.9.0-1-amd64/build/include -include 
/lib/modules/5.9.0-1-amd64/build/include/generated/autoconf.h 
-I/lib/modules/5.9.0-1-amd64/source/include 
-I/lib/modules/5.9.0-1-amd64/source/include/uapi 
-I/lib/modules/5.9.0-1-amd64/source/include/xen 
-I/lib/modules/5.9.0-1-amd64/build/include/generated/uapi 
-I/lib/modules/5.9.0-1-amd64/source/arch/x86/include 
-I/lib/modules/5.9.0-1-amd64/source/arch/x86/include/uapi 
-I/lib/modules/5.9.0-1-amd64/build/arch/x86/include/generated 
-I/lib/modules/5.9.0-1-amd64/build/arch/x86/include/generated/uapi -Wall 
-Wundef -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx 
-m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone 
-mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks 
-Wno-frame-address 

Bug#973227: dh-cmake: FTBFS: AttributeError: 'Changelog' object has no attribute 'get_version'

[Kyle Edwards]

Thanks. Looks like I was accidentally using an undocumented method from 
python3-debian that got renamed. I have a working and fix and will ask 
my sponsor to upload it.

Bug#969372: uwsgi-emperor: SysV init script does nothing

[Thomas Goirand]

Hi,

Vlastimil, did you actually try to put some ini file in the relevant
folder, ie: /etc/uwsgi-emperor/vassals/ ? How did you test to tell that
it didn't work?

Cheers,

Thomas Goirand (zigo)

Processed (with 1 error): supysonic FTBFS

[Debian Bug Tracking System]

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

> tags 973034 - fixed pending patch
Bug #973034 [src:supysonic] supysonic's autopkg tests are failing with python3.9
Removed tag(s) fixed.
> merge 972717 973191
Bug #972717 [src:supysonic] supysonic fails tests with python3.9
Unable to merge bugs because:
blocks of #973191 is '' not '973034'
Failed to merge 972717: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#973190: geneweb: FTBFS: ocamlc.opt: OCaml has been configured with -force-safe-string: -unsafe-string is not available.

[Guillaume Brochu]

Dear Lucas,


Thank you for the report!

This is most likely related to the recent migration to OCAML 4.11 in
unstable:
[2020-10-12] Accepted ocaml 4.11.1-3 (source) into unstable

And I think I know what to do to fix it. See the commit messages in :

https://salsa.debian.org/GuillaumeBrochu-guest/geneweb/-/blob/master/debian/patches/0001-Makefile.debian.patch

https://github.com/geneweb/geneweb/commit/5fe0e0bccb33befd56471dd40eaf44ead2f6fb8a

I will try to fix this as soon as possible.

With best regards,


Guillaume

Le mar. 27 oct. 2020 à 13:51, Lucas Nussbaum  a écrit :

> Source: geneweb
> Version: 6.08+git20181019+dfsg-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 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 '/<>/wserver'
> > camlp5r pa_extend.cmo q_MLast.cmo -o pa_macro5.ppo pa_macro5.ml
> > ocamlc -c -I "`camlp5 -where`" -impl pa_macro5.ppo
> > camlp5r ../wserver/pa_macro5.cmo -DUNIX -o wserver.ppi wserver.mli
> > ocamlc.opt -unsafe-string  -I /usr/lib/ocaml/camlp5/ -c -intf wserver.ppi
> > ocamlc.opt: OCaml has been configured with -force-safe-string:
> -unsafe-string is not available.
>


> [...]
>


> The full build log is available from:
>
> http://qa-logs.debian.net/2020/10/27/geneweb_6.08+git20181019+dfsg-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.
>

Bug#973051: The generic bulseye image is configured without metadata list

[Bastian Blank]

On Tue, Oct 27, 2020 at 04:54:13PM +0100, Thomas Goirand wrote:
> Testing to start the OpenStack image (well, the "genericcloud" image), I
> couldn't login into it, because there isn't any metadata service configured
> in it.

This is incorrect.  The package uses
/lib/systemd/system-generators/cloud-init-generator to generate a
config.  This works in general:

| $ cat /run/cloud-init/cloud.cfg 
| datasource_list: [ Azure, None ]

So, please provide more information.

> After that, it appears that /etc/hosts wasn't configued at all with the
> hostname, therefore, the hostname couldn't be resolved even within the VM
> itself. I'm not sure if this is related or not, however.

Show logs?  /run/cloud-init/cloud-init-generator.log for example.

> IMO, this is of severity grave, because the image is not usable without a
> tweak (ie: impossible to login).

Severities have no real meaning for non-package resources.  And the same
mechanism clearly works on Azure and EC2 without problems, so it would
be only "important".

Bastian

-- 
No one wants war.
-- Kirk, "Errand of Mercy", stardate 3201.7

Bug#957814: sma: diff for NMU version 1.4-3.1

[Sudip Mukherjee]

Control: tags 957814 + patch
Control: tags 957814 + pending
--

Dear maintainer,

I've prepared an NMU for sma (versioned as 1.4-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru sma-1.4/debian/changelog sma-1.4/debian/changelog
--- sma-1.4/debian/changelog2014-05-26 02:48:38.0 +0100
+++ sma-1.4/debian/changelog2020-10-27 22:25:23.0 +
@@ -1,3 +1,10 @@
+sma (1.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957814)
+
+ -- Sudip Mukherjee   Tue, 27 Oct 2020 22:25:23 
+
+
 sma (1.4-3) unstable; urgency=low
 
   * debian/control: bumped Standards-Version (no changes)
diff -Nru sma-1.4/debian/patches/fix_gcc-10.patch 
sma-1.4/debian/patches/fix_gcc-10.patch
--- sma-1.4/debian/patches/fix_gcc-10.patch 1970-01-01 01:00:00.0 
+0100
+++ sma-1.4/debian/patches/fix_gcc-10.patch 2020-10-27 22:24:49.0 
+
@@ -0,0 +1,19 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957814
+Forwarded: no
+
+---
+
+--- sma-1.4.orig/Makefile
 sma-1.4/Makefile
+@@ -7,7 +7,7 @@ MANDIR = /usr/man/man8
+ 
+ CC= gcc
+ # XPG3 regular expressions (GNU/BSD/SVR4)
+-CFLAGS= -Wall -O -DUSE_REGEXP
++CFLAGS= -Wall -O -DUSE_REGEXP -fcommon
+ # Others
+ #CFLAGS   = -Wall -O
+ 
diff -Nru sma-1.4/debian/patches/series sma-1.4/debian/patches/series
--- sma-1.4/debian/patches/series   2014-05-26 02:36:51.0 +0100
+++ sma-1.4/debian/patches/series   2020-10-27 21:25:49.0 +
@@ -1,3 +1,4 @@
 fhsify
 fix_manpage
 hardening
+fix_gcc-10.patch

Processed: sma: diff for NMU version 1.4-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957814 + patch
Bug #957814 [src:sma] sma: ftbfs with GCC-10
Added tag(s) patch.
> tags 957814 + pending
Bug #957814 [src:sma] sma: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#972919: marked as done (ycmd ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 22:55:30 +0100
with message-id <20201027215530.qz4p7ky3ejgskvx4@crossbow>
and subject line Re: Bug#972919: ycmd ftbfs with python3.9
has caused the Debian Bug report #972919,
regarding ycmd ftbfs with python3.9
to be marked as done.

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

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


-- 
972919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ycmd
Version: 0+20200810+gita24204e+ds-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ycmd ftbfs with python3.9; to reproduce, you can use the repositories
found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/ycmd_0+20200810+gita24204e+ds-1build1_amd64-2020-10-24T03:08:32Z.build

[...]
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake
(found version "1.71.0") found components: filesystem
-- Using external libclang: /usr/lib/x86_64-linux-gnu/libclang-9.so.1
CMake Warning at /usr/src/googletest/googlemock/CMakeLists.txt:43 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


-- Found PythonInterp: /usr/bin/python3.9 (found version "3.9")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


CMake Error at /usr/src/googletest/googlemock/CMakeLists.txt:103
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


CMake Error at /usr/src/googletest/googlemock/CMakeLists.txt:106
(set_target_properties):
  set_target_properties called with incorrect number of arguments.


-- NOT using clang-tidy for static analysis.
-- Configuring incomplete, errors occurred!
See also
"/<>/ycmd-0+20200810+gita24204e+ds/ycm_build/CMakeFiles/CMakeOutput.log".
See also
"/<>/ycmd-0+20200810+gita24204e+ds/ycm_build/CMakeFiles/CMakeError.log".
cd ycm_build && tail -v -n \+0 CMakeCache.txt
--- End Message ---
--- Begin Message ---
On Mon, Oct 26, 2020 at 10:08:33AM +0100, Matthias Klose wrote:
> deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
> deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

(Shouldn't these be written as https sources given that people does
 redirect anyway?)


> […]
> CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129
> (set_target_properties):
>   set_target_properties called with incorrect number of arguments.
> […]

As identified by others in other builds in this rebuild this
was a regression in googletest, tracked & fixed by now as #972618.


I tried building with "normal" python3.8 and broken googletest and got
these errors as well. Upgrading to the fixed googletest made it build
again. I also tried in a schroot with python3.9 from the mentioned repos
and ycmd builds there as well just fine:
| I: dh_python3 fs:343: renaming ycm_core.so to 
ycm_core.cpython-39-x86_64-linux-gnu.so

I am therefore closing this bugreport as resolved (elsewhere).


Best regards & best of luck with the transition

David Kalnischkies


signature.asc
Description: PGP signature
--- End Message ---

Bug#973173: marked as done (ros-vcstools: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 21:49:30 +
with message-id 
and subject line Bug#973173: fixed in ros-vcstools 0.1.42-3
has caused the Debian Bug report #973173,
regarding ros-vcstools: FTBFS: dh_auto_test: error: pybuild --test --test-nose 
-i python{version} -p "3.9 3.8" returned exit code 13
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.)


-- 
973173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-vcstools
Version: 0.1.42-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package ros-vcstools
> dpkg-buildpackage: info: source version 0.1.42-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jochen Sprickerhof 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from 
> ros-vcstools-0.1.42/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> /<>/setup.py:3: DeprecationWarning: the imp module is deprecated 
> in favour of importlib; see the module's documentation for alternative uses
>   import imp
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8/build' (and everything under 
> it)
> setup.py:3: DeprecationWarning: the imp module is deprecated in favour of 
> importlib; see the module's documentation for alternative uses
>   import imp
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from 
> ros-vcstools-0.1.42/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ros-vcstools using existing 
> ./ros-vcstools_0.1.42.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building ros-vcstools in 
> ros-vcstools_0.1.42-2.debian.tar.xz
> dpkg-source: info: building ros-vcstools in ros-vcstools_0.1.42-2.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> /<>/setup.py:3: DeprecationWarning: the imp module is deprecated 
> in favour of importlib; see the module's documentation for alternative uses
>   import imp
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
> setup.py:3: DeprecationWarning: the imp module is deprecated in favour of 
> importlib; see the module's documentation for alternative uses
>   import imp
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> /<>/setup.py:3: DeprecationWarning: the imp module is deprecated 
> in favour of importlib; see the module's documentation for alternative uses
>   import imp
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/vcstools
> copying src/vcstools/vcs_base.py -> 
> /<>/.pybuild/cpython3_3.9/build/vcstools
> copying src/vcstools/vcs_abstraction.py -> 
> /<>/.pybuild/cpython3_3.9/build/vcstools
> copying src/vcstools/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/vcstools
> copying src/vcstools/hg.py -> 
> /<>/.pybuild/cpython3_3.9/build/vcstools
> copying src/vcstools/__version__.py -> 
> /<>/.pybuild/cpyt

Bug#972920: marked as done (dicomscope: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 21:18:37 +
with message-id 
and subject line Bug#972920: fixed in dicomscope 3.6.0-22
has caused the Debian Bug report #972920,
regarding dicomscope: binary-all FTBFS
to be marked as done.

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

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


-- 
972920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dicomscope
Version: 3.6.0-21
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dicomscope=all=3.6.0-21=1601116491=0

...
   dh_missing -i -O--buildsystem=cmake
dh_missing: warning: usr/lib/libjInterface.so exists in debian/tmp but is not 
installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: dicomscope (4), dicomscope-doc (0), libdicomscope-jni (0)
 * dh_installdocs: dicomscope (0), dicomscope-doc (2), 
libdicomscope-jni (0)
 * dh_installman: dicomscope (1), dicomscope-doc (0), libdicomscope-jni 
(0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:14: binary-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: dicomscope
Source-Version: 3.6.0-22
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dicomscope 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, 27 Oct 2020 22:04:36 +0100
Source: dicomscope
Architecture: source
Version: 3.6.0-22
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 972920
Changes:
 dicomscope (3.6.0-22) unstable; urgency=medium
 .
   * Fix binary-all builds
 Closes: #972920
Checksums-Sha1:
 9ff0f27c6a82a6f0a1d2f9b26675a072f6a6164b 2180 dicomscope_3.6.0-22.dsc
 a104b901cbc41f37d3adb3cfe3fa2a3ac3c08367 11904 
dicomscope_3.6.0-22.debian.tar.xz
 3f3d872477811fcb80541505630182d49790aea9 12287 
dicomscope_3.6.0-22_amd64.buildinfo
Checksums-Sha256:
 3865f31e279a4d7abe465e0465e4335ce70009bf6f11205b7b9bd9ed63e709db 2180 
dicomscope_3.6.0-22.dsc
 3c871982135dfd22462d4ef22ab00363a718e58224463dc52b59dffdeb58 11904 
dicomscope_3.6.0-22.debian.tar.xz
 3251f76215e71318cfa345137693e8a303483ab08b926142f35c934b58cdbaae 12287 
dicomscope_3.6.0-22_amd64.buildinfo
Files:
 93442970431e74b16eec3e553fa49774 2180 graphics optional dicomscope_3.6.0-22.dsc
 7170e663b3859c357d484576a3fde3e7 11904 graphics optional 
dicomscope_3.6.0-22.debian.tar.xz
 f51a4e08dba0198556c911a9b62e4e2f 12287 graphics optional 
dicomscope_3.6.0-22_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+YjB8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE9vhAAhVGHwsvC+i5zqJMd/98hP0RIJrd9FTQM
jTT/QfTZevKy/iJovBpAO8yi/r5khJ6eHJpaRUthXClhje9BMuK+9phTHKKCnHCA
JSVnPTb8sqgQBmXI1mZzS0aD5ACsNFayd/91ajNnRUSOuwWpZuVgH+t2PUe1rl2a
zSIh7r0FUZojSTsE4EMSNvtafxgNHzfF8bh2DUIstiJz+NQAKAi7DQHkCLg2f2ZG
M4YMj3jxSi/7EuD5H0U821bpmaKnMnYZCIX1rkR+S1EbCnODDPs6hWNc0b3H7ptz
24hY8jRF5yrXQ3TbVLw2QiOGo7uC3JyW68sNg0xnXlX4o3gHOkOnPGHTKZdS8YYH
OqIvjfP228hRjgFNo4E1VF4sujP9619gOVn5G4HC7vwjDQSBkd1+vwleJMzTwYza
HljsL3FBZ4EPRb3z0awXMO/yQB2SpbhYfQHgeCqIJGQa+asHyX05ONdDNT6pPOAx
3IioIFutIc79nz9HjRMPZ+QuZM43slMcVED0C0kPPsNnmGt1TFYPO6iIAahkJin0
5m9sGBYCMjHXb7Wqkw3PYP5LNoau1DHUNI7TryNPX7mXvsHrxAv96F9s7K7u8eip

Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unab

[Markus Koschany]

Hi,

This appears to be caused by the recent upgrade of Apache commons-io to
version 2.8.0 (we had 2.6), see also #973135. In version 2.7 they
removed a throws IOException in the method isSymlink()

https://issues.apache.org/jira/browse/IO-610

Could it be related to this change? It is probably necessary to update
the testcase or disable it for a quick workaround.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#972957: marked as done (libudev0-shim FTBFS: cannot find -ludev)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 22:04:05 +
with message-id 
and subject line Bug#972957: fixed in libudev0-shim 1-2
has caused the Debian Bug report #972957,
regarding libudev0-shim FTBFS: cannot find -ludev
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.)


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

https://buildd.debian.org/status/package.php?p=libudev0-shim=sid

...
   dh_auto_build -a
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
cc -Wall -Wextra -g -fvisibility=hidden -shared -fPIC -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-soname,libudev.so.0 -Wl,-z,now -Wl,-z,relro 
-Wl,--no-as-needed -ludev -Wl,--as-needed libudev0.c -o libudev.so.0.0.
/usr/bin/ld: cannot find -ludev
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:11: libudev.so.0.0.] Error 1
--- End Message ---
--- Begin Message ---
Source: libudev0-shim
Source-Version: 1-2
Done: Simon Richter 

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

Debian distribution maintenance software
pp.
Simon Richter  (supplier of updated libudev0-shim 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, 27 Oct 2020 22:32:59 +0100
Source: libudev0-shim
Architecture: source
Version: 1-2
Distribution: unstable
Urgency: medium
Maintainer: Simon Richter 
Changed-By: Simon Richter 
Closes: 972957
Changes:
 libudev0-shim (1-2) unstable; urgency=medium
 .
   * Fix missing build dependency (Closes: #972957)
Checksums-Sha1:
 fdb59b23f9d68f674387fa92980368d6f19b3a18 1390 libudev0-shim_1-2.dsc
 270d6b00c66864fd85c151e9d24fc67909fea938 1976 libudev0-shim_1-2.debian.tar.xz
 b037e610521e5f4e9e1f4ec1c21b94f431945d75 5092 
libudev0-shim_1-2_source.buildinfo
Checksums-Sha256:
 53f1124e46445024974cabfd4a2eebc83b86b71d33d14bdc6817fb0428f59ad1 1390 
libudev0-shim_1-2.dsc
 ce854a2b12a800192ab78c56daa21d4e0b8938cf1950aec837569fd86d2c7226 1976 
libudev0-shim_1-2.debian.tar.xz
 59acda422d209e6ebfcf44096a8f8a6e534b9a5f37037643aee4263c8b5c92b5 5092 
libudev0-shim_1-2_source.buildinfo
Files:
 f76ae61bc667a03d3d06bf3e2dff02f3 1390 oldlibs optional libudev0-shim_1-2.dsc
 4024ba410b7013f444f4501b9d051128 1976 oldlibs optional 
libudev0-shim_1-2.debian.tar.xz
 ee129025abfed6fd44200ddc3105929f 5092 oldlibs optional 
libudev0-shim_1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEtjuqOJSXmNjSiX3Tfr04e7CZCBEFAl+Yk64ACgkQfr04e7CZ
CBEJyQf8DXYwtZXlUaBngWrB+6jjzL4E31eb2hvsnv830CKd70IGXOFeFRi8abMU
jcS+QIlSaF8n5ct2NfUYhg72IMPV4UHixz5SU7w9ZHThcCy1l/GsnfEmFLgUhufs
zRXXsaC4aBigRDcS9OKn49lFE2Dsl0ivSEfxmuh8L0kTClj0L8B1cw4XJhg+3oPZ
fmZpmspgQAcHnPyv7IJF/o0GYXmYE3pepSJmLrUoO3lWzcMT+at9FFVUQwmpQmbv
3kIGIDpEUW2K32wjfJjWoCaWO5FRoGTN9hNyHoFhJv5vqTusPvl2IarhLI+H6Wmv
PYVP7Yl3Ur714G5r+pP2Wugoabpgqw==
=VIxH
-END PGP SIGNATURE End Message ---

Bug#973220: marked as done (node-libnpx: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 123)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 20:48:49 +
with message-id 
and subject line Bug#973220: fixed in node-libnpx 10.2.4-1
has caused the Debian Bug report #973220,
regarding node-libnpx: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 123
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.)


-- 
973220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-libnpx
Version: 10.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> tail -n +2 README.md | marked-man --manual 'User Commands' --version 
> libnpx@$(dpkg-parsechangelog -S version) > libnpx.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/libnpx
>   /bin/sh -ex debian/tests/pkg-js/test
> + export LANG=C
> + export NODE_PATH=node_modules
> + pwd
> + export HOME=/<>
> + ls test/auto-fallback.js test/child.js test/get-prefix.js 
> test/guess-command-name.js test/index.js test/parse-args.js test/util.js
> + grep -v test/auto-fallback.js
> + xargs tap
> TAP version 13
> # Subtest: test/child.js
> # Subtest: escapeArg on *nix
> ok 1 - standard arg left intact
> ok 2 - '-escaped on *nix
> ok 3 - paths escaped as usual
> 1..3
> ok 1 - escapeArg on *nix # time=4.407ms
> 
> # Subtest: escapeArg on win32
> ok 1 - standard arg escaped
> ok 2 - "-escaped on win32
> ok 3 - paths escaped as usual
> 1..3
> ok 2 - escapeArg on win32 # time=1.253ms
> 
> # Subtest: exec
> ok 1 - command string concatenated
> ok 2 - options received!
> ok 3 - unix-style escapes
> ok 4 - win32-style escapes
> ok 5 - got error
> 1..5
> ok 3 - exec # time=11.291ms
> 
> # Subtest: exec (integration)
> ok 1 - node ran successfully
> ok 2 - got the exit code from subproc
> 1..2
> ok 4 - exec (integration) # time=149.221ms
> 
> # Subtest: spawn
> ok 1 - should be equivalent
> ok 2 - got the exit code from
> 1..2
> ok 5 - spawn # time=174.839ms
> 
> # Subtest: runCommand with command arg
> ok 1 - should be equivalent
> ok 2 - got the exit code from subproc
> ok 3 - error message reports ENOENT
> ok 4 - "not found" has code 127
> 1..4
> ok 6 - runCommand with command arg # time=152.75ms
> 
> # Subtest: runCommand with opts.command
> ok 1 - should be equivalent
> 1..1
> ok 7 - runCommand with opts.command # time=85.887ms
> 
> # Subtest: runCommand with opts.call and opts.shell
> ok 1 - should be equivalent
> 1..1
> ok 8 - runCommand with opts.call and opts.shell # time=68.64ms
> 
> 1..8
> # time=657.906ms
> ok 1 - test/child.js # time=828.454ms
> 
> # Subtest: test/get-prefix.js
> /usr/share/nodejs/tap/lib/extra-from-error.js:6
> if (!(k in set) && !/^tapChild/.test(k))
> ^
> 
> TypeError: Cannot use 'in' operator to search for 'name' in uncaughtException
> at /usr/share/nodejs/tap/lib/extra-from-error.js:6:13
> at Array.reduce ()
> at module.exports (/usr/share/nodejs/tap/lib/extra-from-error.js:5:38)
> at TAP.threw (/usr/share/nodejs/tap/lib/test.js:658:15)
> at process.emit (events.js:326:22)
> at process.emit 
> (/usr/share/nodejs/source-map-support/source-map-support.js:495:21)
> at processEmit [as emit] (/usr/share/nodejs/signal-exit/index.js:161:32)
> at process._fatalException (internal/process/execution.js:165:25)
> 1..0 # no tests found
> not ok 2 - test/get-prefix.js # time=190.364ms
>   ---
>   timeout: 3
>   file: test/get-prefix.js
>   command: /usr/bin/node
>   args:
> - test/get-prefix.js
>   stdio:
> - 0
> - pipe
> - 2
>   cwd: /<>
>   exitCode: 7
>   ...
> 
> # Subtest: test/guess-command-name.js
> # Subtest: guesses 

Bug#973220: marked as pending in node-libnpx

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #973220 in node-libnpx 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-libnpx/-/commit/4e8f27730a2e49497e38675e01731d6b19c919ee


Add fix for node-mkdirp ≥ 1

Closes: #973220


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973220

Processed: Bug#973220 marked as pending in node-libnpx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973220 {Done: Xavier Guimard } [src:node-libnpx] 
node-libnpx: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test 
returned exit code 123
Added tag(s) pending.

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

Bug#973112: libcxx-serial: FTBFS: make[5]: *** No rule to make target 'tests/gmock/libgmock.a', needed by 'devel/lib/cxx-serial/cxx-serial-test'. Stop.

[Alec Leamas]

On Tue, 27 Oct 2020 18:06:31 +0100 Lucas Nussbaum  wrote:
> Source: libcxx-serial
> Version: 1.2.1-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Ack, I can reproduce it. This might trigger a major update if I cannot
find a simple solution. Back later

Bug#973065: marked as done (node-zipfile: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 4)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 20:39:00 +
with message-id 
and subject line Bug#973065: fixed in node-zipfile 0.5.12+ds-5
has caused the Debian Bug report #973065,
regarding node-zipfile: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 4
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.)


-- 
973065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-zipfile
Version: 0.5.12+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>/build'
>   CXX(target) Release/obj.target/zipfile/src/node_zipfile.o
> In file included from ../src/node_zipfile.hpp:9,
>  from ../src/node_zipfile.cpp:1:
> ../../../../usr/lib/nodejs/nan/nan.h: In function ‘void 
> Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
> ../../../../usr/lib/nodejs/nan/nan.h:2298:7: warning: cast between 
> incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void 
> (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} 
> [-Wcast-function-type]
>  2298 | , reinterpret_cast(AsyncExecuteComplete)
>   |   ^~~~
> ../src/node_zipfile.cpp: In static member function ‘static void 
> ZipFile::Initialize(v8::Local)’:
> ../src/node_zipfile.cpp:45:94: warning: ‘bool 
> v8::Object::Set(v8::Local, v8::Local)’ is deprecated: 
> Use maybe version [-Wdeprecated-declarations]
>45 | 
> target->Set(Nan::New("ZipFile").ToLocalChecked(),Nan::GetFunction(lcons).ToLocalChecked());
>   |   
>^
> In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
>  from /usr/include/nodejs/deps/v8/include/v8.h:27,
>  from ../src/node_zipfile.hpp:5,
>  from ../src/node_zipfile.cpp:1:
> /usr/include/nodejs/deps/v8/include/v8.h:3499:22: note: declared here
>  3499 | bool Set(Local key, Local value));
>   |  ^~~
> /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of 
> macro ‘V8_DEPRECATED’
>   328 |   declarator __attribute__((deprecated(message)))
>   |   ^~
> ../src/node_zipfile.cpp: In static member function ‘static void 
> ZipFile::get_prop(v8::Local, const 
> Nan::PropertyCallbackInfo&)’:
> ../src/node_zipfile.cpp:112:71: warning: ‘bool v8::Object::Set(uint32_t, 
> v8::Local)’ is deprecated: Use maybe version 
> [-Wdeprecated-declarations]
>   112 | a->Set(i, 
> Nan::New(zf->names_[i].c_str()).ToLocalChecked());
>   |   
> ^
> In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
>  from /usr/include/nodejs/deps/v8/include/v8.h:27,
>  from ../src/node_zipfile.hpp:5,
>  from ../src/node_zipfile.cpp:1:
> /usr/include/nodejs/deps/v8/include/v8.h:3508:22: note: declared here
>  3508 | bool Set(uint32_t index, Local value));
>   |  ^~~
> /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of 
> macro ‘V8_DEPRECATED’
>   328 |   declarator __attribute__((deprecated(message)))
>   |   ^~
> ../src/node_zipfile.cpp: In static member function ‘static void 
> ZipFile::copyFile(const Nan::FunctionCallbackInfo&)’:
> ../src/node_zipfile.cpp:252:72: warning: cast between incompatible function 
> types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to 
> ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
>   252 | uv_queue_work(uv_default_loop(), >request, 
> Work_CopyFile, (uv_after_work_cb)Work_AfterCopyFile);
>   |   
>  ^~~~
> ../src/node_zipfile.cpp: In static member function ‘static void 
> ZipFile::Work_AfterCopyFile(uv_work_t*)’:
> ../src/node_zipfile.cpp:272:93: 

Bug#828781: marked as done (jodreports: FTBFS: error: package freemarker.template does not exist)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 20:41:20 +
with message-id <20201027204120.ynpngietrvfmllp3@debian>
and subject line Re: jodreports: FTBFS: error: package freemarker.template does 
not exist
has caused the Debian Bug report #828781,
regarding jodreports: FTBFS: error: package freemarker.template does not exist
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.)


-- 
828781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jodreports
Version: 2.4.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

jodreports fails to build from source in unstable/amd64:

  [..]

  Adding debian:GeoTrust_Universal_CA.pem
  Adding debian:GeoTrust_Universal_CA_2.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
  Adding debian:GlobalSign_Root_CA.pem
  Adding debian:GlobalSign_Root_CA_-_R2.pem
  Adding debian:GlobalSign_Root_CA_-_R3.pem
  Adding debian:Global_Chambersign_Root_-_2008.pem
  Adding debian:Go_Daddy_Class_2_CA.pem
  Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
  Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem
  Adding debian:Hongkong_Post_Root_CA_1.pem
  Adding debian:IGC_A.pem
  Adding debian:IdenTrust_Commercial_Root_CA_1.pem
  Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
  Adding debian:Izenpe.com.pem
  Adding debian:Juur-SK.pem
  Adding debian:Microsec_e-Szigno_Root_CA.pem
  Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
  Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
  Adding debian:NetLock_Business_=Class_B=_Root.pem
  Adding debian:NetLock_Express_=Class_C=_Root.pem
  Adding debian:NetLock_Notary_=Class_A=_Root.pem
  Adding debian:NetLock_Qualified_=Class_QA=_Root.pem
  Adding debian:Network_Solutions_Certificate_Authority.pem
  Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
  Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem
  Adding debian:PSCProcert.pem
  Adding debian:QuoVadis_Root_CA.pem
  Adding debian:QuoVadis_Root_CA_1_G3.pem
  Adding debian:QuoVadis_Root_CA_2.pem
  Adding debian:QuoVadis_Root_CA_2_G3.pem
  Adding debian:QuoVadis_Root_CA_3.pem
  Adding debian:QuoVadis_Root_CA_3_G3.pem
  Adding debian:RSA_Security_2048_v3.pem
  Adding debian:Root_CA_Generalitat_Valenciana.pem
  Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
  Adding debian:S-TRUST_Universal_Root_CA.pem
  Adding debian:SecureSign_RootCA11.pem
  Adding debian:SecureTrust_CA.pem
  Adding debian:Secure_Global_CA.pem
  Adding debian:Security_Communication_EV_RootCA1.pem
  Adding debian:Security_Communication_RootCA2.pem
  Adding debian:Security_Communication_Root_CA.pem
  Adding debian:Sonera_Class_1_Root_CA.pem
  Adding debian:Sonera_Class_2_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:Starfield_Class_2_CA.pem
  Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
  Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
  Adding debian:StartCom_Certification_Authority.pem
  Adding debian:StartCom_Certification_Authority_2.pem
  Adding debian:StartCom_Certification_Authority_G2.pem
  Adding debian:SwissSign_Gold_CA_-_G2.pem
  Adding debian:SwissSign_Platinum_CA_-_G2.pem
  Adding debian:SwissSign_Silver_CA_-_G2.pem
  Adding debian:Swisscom_Root_CA_1.pem
  Adding debian:Swisscom_Root_CA_2.pem
  Adding debian:Swisscom_Root_EV_CA_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
  Adding debian:TC_TrustCenter_Class_3_CA_II.pem
  Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
  Adding debian:TWCA_Global_Root_CA.pem
  Adding debian:TWCA_Root_Certification_Authority.pem
  Adding debian:Taiwan_GRCA.pem
  Adding debian:TeliaSonera_Root_CA_v1.pem
  Adding debian:Trustis_FPS_Root_CA.pem
  Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
  Adding debian:USERTrust_ECC_Certification_Authority.pem
  Adding debian:USERTrust_RSA_Certification_Authority.pem
  Adding debian:UTN_USERFirst_Email_Root_CA.pem
  Adding 

Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unab

[Thorsten Glaser]

On Tue, 27 Oct 2020, Andreas Tille wrote:

> > > Caused by: java.io.IOException: Unable to delete file: 
> > > targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink
> > >   at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1425)
> > >   at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:338)
> > >   ... 4 more
> > > Caused by: java.nio.file.NoSuchFileException: 
> > > targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink

I read this “cannot delete a dangling link because it does not exist”.

Can you check (add debugging output, best shell out to 'ls -l', because
at this point I don’t trust the JRE!) whether


targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink

indeed exists at this point, and if so, is a symlink, and whether the
symlink target exists?

I saw an issue with symlinks in the Maven Resources Plugin recently
and now wonder whether this is not a JRE bug. Though we could probably
cobble up an MWE…

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

Mit unserem Consulting bieten wir Unternehmen maßgeschneiderte Angebote in
Form von Beratung, Trainings sowie Workshops in den Bereichen
Softwaretechnologie, IT Strategie und Architektur, Innovation und Umsetzung
sowie Agile Organisation.

Besuchen Sie uns auf https://www.tarent.de/consulting .
Wir freuen uns auf Ihren Kontakt.

*

Bug#973207: marked as done (node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 20:38:50 +
with message-id 
and subject line Bug#973207: fixed in node-chokidar 3.4.3-1
has caused the Debian Bug report #973207,
regarding node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex 
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.)


-- 
973207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-chokidar
Version: 3.4.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> # No pkg-js-tools auto build
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/chokidar
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha --exit --reporter spec --timeout 20
> 
> 
>   chokidar
> ✓ should expose public API methods
> fs.watch (non-polling)
>   watch a directory
> ✓ should produce an instance of chokidar.FSWatcher
> ✓ should expose public API methods
> ✓ should emit `add` event when file was added (43ms)
> ✓ should emit nine `add` events when nine files were added in one 
> directory (1294ms)
> ✓ should emit thirtythree `add` events when thirtythree files were 
> added in nine directories (2855ms)
> ✓ should emit `addDir` event when directory was added
> ✓ should emit `change` event when file was changed
> ✓ should emit `unlink` event when file was removed (102ms)
> ✓ should emit `unlinkDir` event when a directory was removed (43ms)
> ✓ should emit two `unlinkDir` event when two nested directories were 
> removed (5024ms)
> ✓ should emit `unlink` and `add` events when a file is renamed (123ms)
> ✓ should emit `add`, not `change`, when previously deleted file is 
> re-added (145ms)
> ✓ should not emit `unlink` for previously moved files (404ms)
> ✓ should survive ENOENT for missing subdirectories
> ✓ should notice when a file appears in a new directory
> ✓ should watch removed and re-added directories (1544ms)
> ✓ should emit `unlinkDir` and `add` when dir is replaced by file 
> (84ms)
> ✓ should emit `unlink` and `addDir` when file is replaced by dir 
> (143ms)
>   watch individual files
> ✓ should detect changes
> ✓ should detect unlinks (121ms)
> ✓ should detect unlink and re-add (164ms)
> ✓ should ignore unwatched siblings (43ms)
> ✓ should detect safe-edit (242ms)
> Skipping gh-682: should detect unlink
>   - should detect unlink while watching a non-existent second file in 
> another directory
>   - should detect unlink and re-add while watching a second file
>   - should detect unlink and re-add while watching a non-existent 
> second file in another directory
>   - should detect unlink and re-add while watching a non-existent 
> second file in the same directory
>   - should detect two unlinks and one re-add
>   - should detect unlink and re-add while watching a second file and 
> a non-existent third file
>   renamed directory
> ✓ should emit `add` for a file in a renamed directory (1026ms)
>   watch non-existent paths
> ✓ should watch non-existent file and detect add (40ms)
> ✓ should watch non-existent dir and detect addDir/add (62ms)
>   watch glob patterns
> ✓ should correctly watch and emit based on glob input (47ms)
> ✓ should respect negated glob patterns (123ms)
> ✓ should traverse subdirs to match globstar patterns (176ms)
> ✓ should resolve relative paths with glob patterns (49ms)
> ✓ should correctly handle conflicting glob patterns (125ms)
> ✓ should correctly handle intersecting glob patterns (43ms)
> ✓ should not confuse glob-like filenames with globs (62ms)
> ✓ should treat glob-like directory names as literal directory names 
> when globbing is disabled (44ms)
> ✓ should treat glob-like filenames as literal filenames when globbing 
> is disabled (42ms)
> ✓ sh

Processed: Bug#973065 marked as pending in node-zipfile

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973065 [src:node-zipfile] node-zipfile: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 4
Added tag(s) pending.

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

Bug#973065: marked as pending in node-zipfile

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #973065 in node-zipfile 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-zipfile/-/commit/c5751443426fdc49c07399bc8d8a102b40f3586f


Add fix for mkdirp ≥ 1

Closes: #973065


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973065

Processed: tags 973034 fixed

[Debian Bug Tracking System]

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

> tags 973034 fixed
Bug #973034 [src:supysonic] supysonic's autopkg tests are failing with python3.9
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Processed: bug 973242 is forwarded to https://github.com/OpenRC/opentmpfiles/issues/4, tagging 973242 ...

[Debian Bug Tracking System]

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

> forwarded 973242 https://github.com/OpenRC/opentmpfiles/issues/4
Bug #973242 [opentmpfiles] CVE-2017-18925
Set Bug forwarded-to-address to 
'https://github.com/OpenRC/opentmpfiles/issues/4'.
> tags 973242 + upstream
Bug #973242 [opentmpfiles] CVE-2017-18925
Added tag(s) upstream.
> found 973242 0.2+2019.05.21.git.44a55796ba-2
Bug #973242 [opentmpfiles] CVE-2017-18925
Marked as found in versions opentmpfiles/0.2+2019.05.21.git.44a55796ba-2.
> thanks
Stopping processing here.

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

Bug#957138: directvnc: diff for NMU version 0.7.7-1.1

[Sudip Mukherjee]

Control: tags 957138 + patch
Control: tags 957138 + pending
--

Dear maintainer,

I've prepared an NMU for directvnc (versioned as 0.7.7-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru directvnc-0.7.7/debian/changelog directvnc-0.7.7/debian/changelog
--- directvnc-0.7.7/debian/changelog2011-07-31 17:20:41.0 +0100
+++ directvnc-0.7.7/debian/changelog2020-10-27 19:25:19.0 +
@@ -1,3 +1,10 @@
+directvnc (0.7.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957138)
+
+ -- Sudip Mukherjee   Tue, 27 Oct 2020 19:25:19 
+
+
 directvnc (0.7.7-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru directvnc-0.7.7/debian/patches/fix_gcc-10.patch 
directvnc-0.7.7/debian/patches/fix_gcc-10.patch
--- directvnc-0.7.7/debian/patches/fix_gcc-10.patch 1970-01-01 
01:00:00.0 +0100
+++ directvnc-0.7.7/debian/patches/fix_gcc-10.patch 2020-10-27 
19:19:25.0 +
@@ -0,0 +1,44 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957138
+Forwarded: no
+
+---
+
+--- directvnc-0.7.7.orig/src/directvnc.h
 directvnc-0.7.7/src/directvnc.h
+@@ -42,7 +42,7 @@
+Tight encoding assumes BUFFER_SIZE is at least 16384 bytes. */
+ 
+ #define BUFFER_SIZE (640*480) 
+-char buffer[BUFFER_SIZE];
++extern char buffer[BUFFER_SIZE];
+ 
+ #define MAX_ENCODINGS 10
+ 
+@@ -64,9 +64,9 @@ struct _mousestate
+unsigned int buttonmask;
+ };
+ 
+-struct _mousestate mousestate;
++extern struct _mousestate mousestate;
+ 
+-int sock;
++extern int sock;
+ 
+ /* rfb.c */
+ int rfb_connect_to_server (char *server, int display);
+--- directvnc-0.7.7.orig/src/main.c
 directvnc-0.7.7/src/main.c
+@@ -24,6 +24,10 @@
+ #include 
+ #include 
+ 
++struct _mousestate mousestate;
++int sock;
++char buffer[BUFFER_SIZE];
++
+ /* little convenience function */
+ static inline double get_time(void);
+ static inline void sig_handler(int foo) { exit(1); }
diff -Nru directvnc-0.7.7/debian/patches/series 
directvnc-0.7.7/debian/patches/series
--- directvnc-0.7.7/debian/patches/series   1970-01-01 01:00:00.0 
+0100
+++ directvnc-0.7.7/debian/patches/series   2020-10-27 18:52:57.0 
+
@@ -0,0 +1 @@
+fix_gcc-10.patch

Processed: directvnc: diff for NMU version 0.7.7-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957138 + patch
Bug #957138 [src:directvnc] directvnc: ftbfs with GCC-10
Added tag(s) patch.
> tags 957138 + pending
Bug #957138 [src:directvnc] directvnc: ftbfs with GCC-10
Added tag(s) pending.

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

Processed: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unabl

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #973070 [src:libsis-base-java] libsis-base-java: FTBFS: Could not delete 
the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests 
because: 1 exceptions: [java.io.IOException: Unable to delete file: 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
Added tag(s) help.

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

Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unab

[Andreas Tille]

Control: tags -1 help

Hi,

I checked out the latest upstream commit and pushed it to Salsa.
Its the same with this.  Any idea why this test has worked before
but is failing now?

Kind regards

  Andreas.

On Tue, Oct 27, 2020 at 06:06:55PM +0100, Lucas Nussbaum wrote:
> Source: libsis-base-java
> Version: 18.09~pre1+git20180827.fe4953e+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 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_auto_test -a
> > mkdir test ; cp -r source/java/ch test ; cp -r sourceTest/java/ch test
> > jh_build sis-base-test.jar test
> > warning: [options] bootstrap class path not set in conjunction with -source 
> > 7
> > 1 warning
> > test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:354: warning - 
> > invalid usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:393: warning - 
> > invalid usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDArray.java:47: warning - invalid usage 
> > of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDArray.java:87: warning - invalid usage 
> > of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/utilities/NativeLibraryUtilities.java:105: 
> > warning - Tag @link: reference not found: System#loadLibrary()
> > 17 warnings
> > LC_ALL=C java -Djava.library.path=source/c/.libs -classpath 
> > sis-base-test.jar ch.systemsx.cisd.base.AllTests
> > Application: base
> > Version: UNKNOWN*
> > Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
> > CPU Architecture: amd64
> > OS: Linux (v4.19.0-6-cloud-amd64)
> > Test class: NativeDataTests
> > 
> > Running testIntToByteToInt
> >  Arguments: [0, 0]
> >  Arguments: [0, 1]
> >  Arguments: [0, 2]
> >  Arguments: [0, 3]
> >  Arguments: [1, 0]
> >  Arguments: [1, 1]
> >  Arguments: [1, 2]
> >  Arguments: [1, 3]
> >  Arguments: [2, 0]
> >  Arguments: [2, 1]
> >  Arguments: [2, 2]
> >  Arguments: [2, 3]
> >  Arguments: [3, 0]
> >  Arguments: [3, 1]
> >  Arguments: [3, 2]
> >  Arguments: [3, 3]
> > Running testIntChangeByteOrderAndBack
> > Running testShortChangeByteOrderAndBack
> > Running testCharChangeByteOrderAndBack
> > Running testLongChangeByteOrderAndBack
> > Running testFloatChangeByteOrderAndBack
> > Running testDoubleChangeByteOrderAndBack
> > Running testLongToByteToLong
> >  Arguments: [0, 0]
> >  Arguments: [0, 1]
> >  Arguments: [0, 2]
> >  Arguments: [0, 3]
> >  Arguments: [1, 0]
> >  Arguments: [1, 1]
> >  Arguments: [1, 2]
> >  Arguments: [1, 3]
> >  Arguments: [2, 0]
> >  Arguments: [2, 1]
> >  Arguments: [2, 2]
> >  Arguments: [2, 3]
> >  Arguments: [3, 0]
> >  Arguments: [3, 1]
> >  Arguments: [3, 2]
> >  Arguments: [3, 3]
> > Running testShortToByteToShort
> >  Arguments: [0, 0]
> >  Arguments: [0, 1]
> >  Arguments: [0, 2]
> >  Arguments: [0, 3]
> >  Arguments: [1, 0]
> >  Arguments: [1, 1]
> >  Arguments: [1, 2]
> >  Arguments: [1, 3]
> >  Arguments: [2, 0]
> >  Arguments: [2, 1]
> >  Arguments: [2,

Bug#973207: marked as pending in node-chokidar

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #973207 in node-chokidar 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-chokidar/-/commit/87de610caea7ae537811571de1d7d24a72439550


Disable test during build (autopkgtest only)

Closes: #973207


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973207

Bug#973231: marked as done (pypng: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 19:48:52 +
with message-id 
and subject line Bug#973231: fixed in pypng 0.0.20+ds-3
has caused the Debian Bug report #973231,
regarding pypng: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p "3.9 3.8" returned exit code 13
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.)


-- 
973231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pypng
Version: 0.0.20+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> copying code/png.py -> /<>/.pybuild/cpython3_3.9_png/build
> copying code/test_png.py -> /<>/.pybuild/cpython3_3.9_png/build
> copying code/pngsuite.py -> /<>/.pybuild/cpython3_3.9_png/build
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying code/png.py -> /<>/.pybuild/cpython3_3.8_png/build
> copying code/test_png.py -> /<>/.pybuild/cpython3_3.8_png/build
> copying code/pngsuite.py -> /<>/.pybuild/cpython3_3.8_png/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_png/build; 
> python3.9 -m unittest discover -v 
> test_L12 (test_png.Test)
> Test L12. ... ok
> test_L16_to_RGB (test_png.Test)
> asRGB() on 16-bit grey source. ... ok
> test_L2 (test_png.Test)
> Test L2 (and asRGB8). ... ok
> test_L3 (test_png.Test)
> Test L3. ... ok
> test_L4 (test_png.Test)
> Test L4. ... ok
> test_L7 (test_png.Test)
> Test L7. ... ok
> test_L8 (test_png.Test)
> Test L8. ... ok
> test_L9 (test_png.Test)
> Test L9. ... ok
> test_LA4 (test_png.Test)
> Create an LA image with bitdepth 4. ... ok
> test_LA_to_RGBA (test_png.Test)
> asRGBA() on LA source. ... ok
> test_L_to_RGB (test_png.Test)
> asRGB() on grey source. ... ok
> test_L_to_RGBA (test_png.Test)
> asRGBA() on grey source. ... ok
> test_L_trns_0 (test_png.Test)
> Create greyscale image with tRNS chunk. ... ok
> test_L_trns_tuple (test_png.Test)
> Using 1-tuple for transparent arg. ... ok
> test_P2 (test_png.Test)
> 2-bit palette. ... ok
> test_RGB_to_RGBA (test_png.Test)
> asRGBA8() on colour type 2 source. ... ok
> test_RGB_trns (test_png.Test)
> Test colour type 2 and tRNS chunk. ... ok
> test_alpha_trns (test_png.Test)
> alpha and transparent don't mix. ... ok
> test_background_bad (test_png.Test)
> Wrong background in constructor. ... ok
> test_background_rgb_unnatural (test_png.Test)
> non-integer background in constructor. ... ok
> test_background_unnatural (test_png.Test)
> non-integer background in constructor. ... ok
> test_bad_filter (test_png.Test)
> Test file that contains impossible filter type. ... ok
> test_bitdepth_bad (test_png.Test) ... ok
> test_cannot_length_check (test_png.Test)
> The length check cannot be used on an itertools.chain object. ... ok
> test_checksum_bad (test_png.Test)
> Chunk has bad checksum. ... ok
> test_chunk_after_idat (test_png.Test)
> Test with a PNG that has an ancillary chunk after IDAT chunks. ... ok
> test_chunk_short (test_png.Test)
> Chunk that is too short. ... ok
> test_chunk_truncated (test_png.Test)
> Chunk doesn't have length and type. ... ok
> test_deepen_palette (test_png.Test)
> Test that palette bitdepth can be increased, ... ok
> test_empty (test_png.Test)
> Test empty file. ... ok
> test_extra_pixels (test_png.Test)
> Test file that contains too many pixels. ... ok
> test_flat (test_png.Test)
> Test read_flat. ... ok
> test_from_array_L (test_png.Test) ... ok
> test_from_array_L16 (test_png.Test) ... ok
> test_from_array_L2 (test_png.Test) ... ok
> test_from_array_LA (test_p

Bug#971180: marked as done (ipython: FTBFS: Could not import extension IPython.sphinxext.ipython_console_highlighting (exception: No module named 'decorator'))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 19:33:29 +
with message-id 
and subject line Bug#971180: fixed in ipython 7.18.1-2
has caused the Debian Bug report #971180,
regarding ipython: FTBFS: Could not import extension 
IPython.sphinxext.ipython_console_highlighting (exception: No module named 
'decorator')
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.)


-- 
971180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipython
Version: 7.18.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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 '/<>'
> http_proxy=127.0.0.1:9 https_proxy=127.0.0.1:9 PYTHONPATH=. python3 -m sphinx 
> -b html docs/source 
> debian/python-ipython-doc/usr/share/doc/python-ipython-doc/html
> Running Sphinx v3.2.1
> 
> Extension error:
> Could not import extension IPython.sphinxext.ipython_console_highlighting 
> (exception: No module named 'decorator')
> Adding Tag: ipystable
> make[1]: *** [debian/rules:22: override_dh_sphinxdoc] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/ipython_7.18.1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated ipython 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, 27 Oct 2020 19:07:53 +
Source: ipython
Architecture: source
Version: 7.18.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 971180
Changes:
 ipython (7.18.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Gordon Ball ]
   * Add missing build-dependency: python3-decorator (Closes: #971180)
   * Rename the git repository from ipython4 -> ipython, and update Vcs-*
 fields accordingly.
Checksums-Sha1:
 4b635bfec5f5d995b3cde11b630e53d674468a8e 2411 ipython_7.18.1-2.dsc
 6e4125a858f65827c1a5c4c2026313202762812d 7252 ipython_7.18.1-2.debian.tar.xz
 697d3212bb17022361192de89a4b7b2312bcf00f 6774 ipython_7.18.1-2_source.buildinfo
Checksums-Sha256:
 b6890ef63fb5252693942e69193fbda173db496280bc8ab4253bd122b02eca05 2411 
ipython_7.18.1-2.dsc
 66a2660e230493468ae97eb3c8b3fdf57d66454c0997063bbdadb614edc2c42b 7252 
ipython_7.18.1-2.debian.tar.xz
 cb7572b69f22f7584948825a550836b4bbb57be4d185c74733a22a895834e1f8 6774 
ipython_7.18.1-2_source.buildinfo
Files:
 2cfea6694dad1dee2b2a5cb1bc6b8557 2411 python optional ipython_7.18.1-2.dsc
 7ff02837f534ca7149c5126dad288113 7252 python optional 
ipython_7.18.1-2.debian.tar.xz
 2f9dcdac8fc08371a97640a4901d021d 6774 python optional 
ipython_7.18.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl+Ycm0ACgkQo12v+60p
6N7pNg/9Gp26Olb+WM3PqnXHLaWvF1fzpiPwuLvQD2dVIo3wEXu3Rja/iqT/Ul9q
7Tjsubd69SC/tJE4byNunYuvK/qV22NDLqI4OTdGVeAiEWsWzDJl2oh4vT7cirM8
e7vffKk8U8k5bzm52kqpLPNEBvS/KFnBpLUe3izIonLsZPpCbBDqYPeA4b+N9NDN
/g3C/5qzO6RK7/k0VTsX5niFUOCVKshZAqo+4Tb+tav+NEwvWWFUTAVjGKoEbCs6
Sicck1cFUSYlK4kBbjHOriCJgoJHPSlpQFyIi2t/Vqn0unNCr+ljwgbRAE30bPjB
kxLkm1R0lKrDp5nT/tkESKw8mGoOMWu0hHcQu0ykYfqg7hjRNbUKYa1f4GctYjKd
931YxiC1HcD3B9TtQ9N/CM/yBDh/Xyz4JrWlWhXeh468sTYxAFNji0FCIAPeKs7Z

Processed: Bug#973207 marked as pending in node-chokidar

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973207 [src:node-chokidar] node-chokidar: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.

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

Processed: Re: Bug#973177: python-geojson: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream pending
Bug #973177 {Done: Bas Couwenberg } [src:python-geojson] 
python-geojson: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p "3.9 3.8" returned exit code 13
Added tag(s) upstream and pending.

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

Bug#973177: python-geojson: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Sebastiaan Couwenberg]

Control: tags -1 upstream pending

This is fixed upstream, the commit in question will be included as a patch.

Kind Regards,

Bas

Bug#973117: marked as done (node-parse-json: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 19:33:41 +
with message-id 
and subject line Bug#973117: fixed in node-parse-json 5.1.0+~1.1.6-2
has caused the Debian Bug report #973117,
regarding node-parse-json: FTBFS: tests failed
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.)


-- 
973117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-parse-json
Version: 5.1.0+~1.1.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-parse-json
> dpkg-buildpackage: info: source version 5.1.0+~1.1.6-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>   rm -rf lines-and-columns/node_modules/.cache
> Use of uninitialized value $package in concatenation (.) or string at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/nodejs.pm line 943.
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-parse-json using existing 
> ./node-parse-json_5.1.0+~1.1.6.orig-lines-and-columns.tar.gz
> dpkg-source: info: building node-parse-json using existing 
> ./node-parse-json_5.1.0+~1.1.6.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-parse-json in 
> node-parse-json_5.1.0+~1.1.6-1.debian.tar.xz
> dpkg-source: info: building node-parse-json in 
> node-parse-json_5.1.0+~1.1.6-1.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>   mkdir node_modules
>   mkdir -p lines-and-columns/node_modules
>   ln -s /usr/share/nodejs/assert lines-and-columns/node_modules/
> internal/modules/cjs/loader.js:834
>   throw err;
>   ^
> 
> Error: Cannot find module '@types/mocha'
> Require stack:
> - /<>/[eval]
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:831:15)
> at Function.resolve (internal/modules/cjs/helpers.js:80:19)
> at [eval]:1:21
> at Script.runInThisContext (vm.js:120:18)
> at Object.runInThisContext (vm.js:309:38)
> at Object. ([eval]-wrapper:10:26)
> at Module._compile (internal/modules/cjs/loader.js:1015:30)
> at evalScript (internal/process/execution.js:94:25)
> at internal/main/eval_string.js:23:3 {
>   code: 'MODULE_NOT_FOUND',
>   requireStack: [
> '/<>/[eval]'
>   ]
> }
> ### @types/mocha NOT FOUND
>   ln -s ../lines-and-columns node_modules/lines-and-columns
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/lines-and-columns/build
>   cd ./lines-and-columns && sh -ex 
> ../debian/nodejs/lines-and-columns/build
> + TSC=tsc ./script/build
> Building ES module version.
> test/test.ts(4,1): error TS2582: Cannot find name 'describe'. Do you need to 
> install type definitions for a test runner? Try `npm i @types/jest` or `npm i 
> @types/mocha`.
> test/test.ts(5,3): error TS2582: Cannot find name 'it'. Do you need to 
> install type definitions for a test runner? Try `npm i @types/jest` or `npm i 
> @types/mocha`.
> test/test.ts(10,3): error TS2582: Cannot find name 'it'. Do you need to 
> install type definitions for a test runner? Try `npm i @types/jest` or `npm i 
> @types/mocha`.
> test/test.ts(15,3): error TS2582: Cannot find name 'it'. Do you need to 
> install type definitions for a test runner? Try `npm i @types/jest` or `npm i 
> @types/mocha`.
> test/test.ts(21,3): error TS2582: Cannot find name 'it'. Do you need to 
> install type definitions for a test runner? Try `npm i @types/jest` or `npm i 
> @types/mocha`.
> test/test.ts(26,3): error TS2582: Cannot find name 'it'. Do you need to 
> install type definitions for a test runner? Try `npm i @types/jest` or `npm i 
> @t

Processed (with 1 error): Merge supysonic FTBFS bis

[Debian Bug Tracking System]

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

> block 973191 by 972484
Bug #973191 [src:supysonic] supysonic: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.9 3.8" returned exit code 13
973191 was not blocked by any bugs.
973191 was not blocking any bugs.
Added blocking bug(s) of 973191: 972484
> merge 972717 973191
Bug #972717 [src:supysonic] supysonic fails tests with python3.9
Unable to merge bugs because:
blocks of #973191 is '' not '973034'
Failed to merge 972717: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#938351: marked as pending in renpy

[Markus Koschany]

Am 27.10.20 um 20:10 schrieb Gregor Riepl:
>> https://salsa.debian.org/games-team/renpy/commit/fc29ebfe106238b590a7896450a5d1ad1f94f84e
>>
>> 
>> Switch to python3.
>>
>> Closes: #938351
>> 
> 
> I'm confused.
> Does that mean upstream has completed the port to Python 3?

No.

> Last I checked, the bug was still wide open:
> https://github.com/renpy/renpy/issues/1098

Just the dependencies were switched to Python 3 and the Git hook sent an
automatic email to the BTS.



signature.asc
Description: OpenPGP digital signature

Bug#973034: supysonic's autopkg tests are failing with python3.9

[Louis-Philippe Véronneau]

tags -1 fixed
block 973034 by 972717
thanks

This has been fixed in the VCS already [1], but a new revision can't be
uploaded since this package FTBFS with python3.9

[1]:
https://salsa.debian.org/python-team/packages/supysonic/-/commit/e187fd03c2c22939778f870f07fbfada50b9ada7

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#938351: marked as pending in renpy

[Gregor Riepl]

> https://salsa.debian.org/games-team/renpy/commit/fc29ebfe106238b590a7896450a5d1ad1f94f84e
> 
> 
> Switch to python3.
> 
> Closes: #938351
> 

I'm confused.
Does that mean upstream has completed the port to Python 3?

Last I checked, the bug was still wide open:
https://github.com/renpy/renpy/issues/1098

Processed (with 1 error): Re: supysonic's autopkg tests are failing with python3.9

[Debian Bug Tracking System]

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

> tags -1 fixed
Failed to alter tags of Bug -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_tag did not pass regex check
.

> block 973034 by 972717
Bug #973034 [src:supysonic] supysonic's autopkg tests are failing with python3.9
973034 was not blocked by any bugs.
973034 was not blocking any bugs.
Added blocking bug(s) of 973034: 972717
> thanks
Stopping processing here.

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

Bug#973213: marked as done (gqrx-sdr: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 19:03:29 +
with message-id 
and subject line Bug#973213: fixed in gnuradio 3.8.2.0-8
has caused the Debian Bug report #973213,
regarding gqrx-sdr: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
 undefined reference to `pthread_create'
to be marked as done.

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

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


-- 
973213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gqrx-sdr
Version: 2.13.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_d5388.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
>  undefined reference to `pthread_create'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12:
>  undefined reference to `pthread_detach'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13:
>  undefined reference to `pthread_cancel'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14:
>  undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/gqrx-sdr_2.13.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gnuradio
Source-Version: 3.8.2.0-8
Done: bott...@debian.org (A. Maitland Bottoms)

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gnuradio 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, 27 Oct 2020 06:14:45 -0400
Source: gnuradio
Architecture: source
Version: 3.8.2.0-8
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 973007 973008 973213
Changes:
 gnuradio (3.8.2.0-8) unstable; urgency=medium
 .
   * add thrift-compiler to gnuradio-dev dependencies
 (Closes: #973008, #973007, #973213)
   * Restore thrift on armel
Checksums-Sha1:
 01da0abb5ed03ae2467ac496a0c85e485b0ba941 4639 gnuradio_3.8.2.0-8.dsc
 cfcce949ba2e0cf6e876a9a41c42d1d753f2ca2b 1532380 
gnuradio_3.8.2.0-8.debian.tar.xz
 157d7e1c154b1ab80a445aee5b600228d5918e8f 33924 
gnuradio_3.8.2.0-8_amd64.buildinfo
Checksums-Sha256:
 5fb159794c7ac008a6acda231798efc9c37d38e4e00045ec1c97d3ac2dc3f218 4639 
gnuradio_3.8.2.0-8.dsc
 7a95baf92aef96924f852e350056338d2b34c47ec28ac90d4624f83f5f825d94 1532380 
gnuradio_3.8.2.0-8.debian.tar.xz
 6ea950af4eac1da390096f06b84664f725347e90092673f9c289b49d141527d4 33924 
gnuradio_3.8.2.0-8_amd64.buildinfo
Files:
 3f228383ec0ba16481ef459d84925711 4639 comm optional gnuradio_3.8.2.0-8.dsc
 cb2a63f057d48d08f7ffe18e201fbc9f 1532380 comm optional 
gnuradio_3.8.2.0-8.debian.tar.xz
 8d8611fb94f19b347829d65ac119ad8c 33924 comm optional 
gnuradio_3.8.2.0-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl+Ya2EACgkQUEHxiR9E
4JAcfA/+LbE/S+1iGUAaqh0ifXsfd/GlVhh3bu9kzbl9mQvmCmqyn6SHy5cX+sO8
nuoNo65yKObprwE8LkwqYopktDlh7EEwIzMQTqonWz4q/oeiBSYcqIY6kzrVWbpe
8lsIJLsTTdWAo2rZA0eGIeCFQ2auMJ3bD5u46KD1cDqT+2RISUGw8UbyoXwzavoo
/6X3IGuQgestyu3s0Prk8ZWd4zg10JTgbqL7OccoV5Ak6lUblAJ+kUEYscxaOUWv
D/7uCfLXPdp1H/U9Sl5Ia4hKA6j73tpfHBxSjGXS5yWBCBre

Bug#973008: marked as done (gr-gsm: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 19:03:29 +
with message-id 
and subject line Bug#973008: fixed in gnuradio 3.8.2.0-8
has caused the Debian Bug report #973008,
regarding gr-gsm: FTBFS in unstable
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.)


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

Hi Maintainer

As per reproducible builds [1], gr-gsm recently started failing to
build in unstable.

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

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gr-gsm.html


CMake Error at CMakeLists.txt:88 (find_package):
  Found package configuration file:

/usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake

  but it set Gnuradio_FOUND to FALSE so package "Gnuradio" is considered to
  be NOT FOUND.  Reason given by package:

  The following imported targets are referenced, but are missing:
  gnuradio::gnuradio-runtime



-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: gnuradio
Source-Version: 3.8.2.0-8
Done: bott...@debian.org (A. Maitland Bottoms)

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gnuradio 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, 27 Oct 2020 06:14:45 -0400
Source: gnuradio
Architecture: source
Version: 3.8.2.0-8
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 973007 973008 973213
Changes:
 gnuradio (3.8.2.0-8) unstable; urgency=medium
 .
   * add thrift-compiler to gnuradio-dev dependencies
 (Closes: #973008, #973007, #973213)
   * Restore thrift on armel
Checksums-Sha1:
 01da0abb5ed03ae2467ac496a0c85e485b0ba941 4639 gnuradio_3.8.2.0-8.dsc
 cfcce949ba2e0cf6e876a9a41c42d1d753f2ca2b 1532380 
gnuradio_3.8.2.0-8.debian.tar.xz
 157d7e1c154b1ab80a445aee5b600228d5918e8f 33924 
gnuradio_3.8.2.0-8_amd64.buildinfo
Checksums-Sha256:
 5fb159794c7ac008a6acda231798efc9c37d38e4e00045ec1c97d3ac2dc3f218 4639 
gnuradio_3.8.2.0-8.dsc
 7a95baf92aef96924f852e350056338d2b34c47ec28ac90d4624f83f5f825d94 1532380 
gnuradio_3.8.2.0-8.debian.tar.xz
 6ea950af4eac1da390096f06b84664f725347e90092673f9c289b49d141527d4 33924 
gnuradio_3.8.2.0-8_amd64.buildinfo
Files:
 3f228383ec0ba16481ef459d84925711 4639 comm optional gnuradio_3.8.2.0-8.dsc
 cb2a63f057d48d08f7ffe18e201fbc9f 1532380 comm optional 
gnuradio_3.8.2.0-8.debian.tar.xz
 8d8611fb94f19b347829d65ac119ad8c 33924 comm optional 
gnuradio_3.8.2.0-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl+Ya2EACgkQUEHxiR9E
4JAcfA/+LbE/S+1iGUAaqh0ifXsfd/GlVhh3bu9kzbl9mQvmCmqyn6SHy5cX+sO8
nuoNo65yKObprwE8LkwqYopktDlh7EEwIzMQTqonWz4q/oeiBSYcqIY6kzrVWbpe
8lsIJLsTTdWAo2rZA0eGIeCFQ2auMJ3bD5u46KD1cDqT+2RISUGw8UbyoXwzavoo
/6X3IGuQgestyu3s0Prk8ZWd4zg10JTgbqL7OccoV5Ak6lUblAJ+kUEYscxaOUWv
D/7uCfLXPdp1H/U9Sl5Ia4hKA6j73tpfHBxSjGXS5yWBCBre1anxrD/4RRGlymGR
28/HQLkqJWYqBM5WQkNO1L+UZGBYXKFlkhHp+I1mryGaU7RCqYRxBMYll3D/GPl1
80o/U7ysXee4f3F/U7flkoRd7ZxjiaL3n9I25nuzTN6CXngAd/8Ni27VLIa4WVd0
JHl3fCgG1eudpEqhjRlAP3Nf3w215/ptK2tWGLcFQxSLkjdMDKSg6pzy1U6aDAGv
9rYjdGrxxEaXg0Y6KxMSWEJmxA0bHp7CIthTUcZefgnZLykbVH5cw/AoHKsuX89f
A1Z63J3C7HmiKMZs5Lz+jzbN+I/LTr3VWTyjGfK/ArbGhCmtyiUBR9IzTZB7XVao
3Uadxc//buwqiXL0U5ljZBe+pCjGY1gyx844Dj37a2FA1taX7Tk=
=cWFI
-END PGP SIGNATURE End Message ---

Bug#973007: marked as done (gr-air-modes: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 19:03:29 +
with message-id 
and subject line Bug#973007: fixed in gnuradio 3.8.2.0-8
has caused the Debian Bug report #973007,
regarding gr-air-modes: FTBFS in unstable
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.)


-- 
973007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-air-modes
Version: 0.0.20190917-2
Severity: serious
Tags: ftbfs

Hi Maintainer

As per reproducible builds [1], gr-air-modes recently started failing
to build in unstable.

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

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gr-air-modes.html


CMake Error at CMakeLists.txt:90 (find_package):
  Found package configuration file:

/usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake

  but it set Gnuradio_FOUND to FALSE so package "Gnuradio" is considered to
  be NOT FOUND.  Reason given by package:

  The following imported targets are referenced, but are missing:
  gnuradio::gnuradio-runtime



-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: gnuradio
Source-Version: 3.8.2.0-8
Done: bott...@debian.org (A. Maitland Bottoms)

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gnuradio 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, 27 Oct 2020 06:14:45 -0400
Source: gnuradio
Architecture: source
Version: 3.8.2.0-8
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 973007 973008 973213
Changes:
 gnuradio (3.8.2.0-8) unstable; urgency=medium
 .
   * add thrift-compiler to gnuradio-dev dependencies
 (Closes: #973008, #973007, #973213)
   * Restore thrift on armel
Checksums-Sha1:
 01da0abb5ed03ae2467ac496a0c85e485b0ba941 4639 gnuradio_3.8.2.0-8.dsc
 cfcce949ba2e0cf6e876a9a41c42d1d753f2ca2b 1532380 
gnuradio_3.8.2.0-8.debian.tar.xz
 157d7e1c154b1ab80a445aee5b600228d5918e8f 33924 
gnuradio_3.8.2.0-8_amd64.buildinfo
Checksums-Sha256:
 5fb159794c7ac008a6acda231798efc9c37d38e4e00045ec1c97d3ac2dc3f218 4639 
gnuradio_3.8.2.0-8.dsc
 7a95baf92aef96924f852e350056338d2b34c47ec28ac90d4624f83f5f825d94 1532380 
gnuradio_3.8.2.0-8.debian.tar.xz
 6ea950af4eac1da390096f06b84664f725347e90092673f9c289b49d141527d4 33924 
gnuradio_3.8.2.0-8_amd64.buildinfo
Files:
 3f228383ec0ba16481ef459d84925711 4639 comm optional gnuradio_3.8.2.0-8.dsc
 cb2a63f057d48d08f7ffe18e201fbc9f 1532380 comm optional 
gnuradio_3.8.2.0-8.debian.tar.xz
 8d8611fb94f19b347829d65ac119ad8c 33924 comm optional 
gnuradio_3.8.2.0-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl+Ya2EACgkQUEHxiR9E
4JAcfA/+LbE/S+1iGUAaqh0ifXsfd/GlVhh3bu9kzbl9mQvmCmqyn6SHy5cX+sO8
nuoNo65yKObprwE8LkwqYopktDlh7EEwIzMQTqonWz4q/oeiBSYcqIY6kzrVWbpe
8lsIJLsTTdWAo2rZA0eGIeCFQ2auMJ3bD5u46KD1cDqT+2RISUGw8UbyoXwzavoo
/6X3IGuQgestyu3s0Prk8ZWd4zg10JTgbqL7OccoV5Ak6lUblAJ+kUEYscxaOUWv
D/7uCfLXPdp1H/U9Sl5Ia4hKA6j73tpfHBxSjGXS5yWBCBre1anxrD/4RRGlymGR
28/HQLkqJWYqBM5WQkNO1L+UZGBYXKFlkhHp+I1mryGaU7RCqYRxBMYll3D/GPl1
80o/U7ysXee4f3F/U7flkoRd7ZxjiaL3n9I25nuzTN6CXngAd/8Ni27VLIa4WVd0
JHl3fCgG1eudpEqhjRlAP3Nf3w215/ptK2tWGLcFQxSLkjdMDKSg6pzy1U6aDAGv
9rYjdGrxxEaXg0Y6KxMSWEJmxA0bHp7CIthTUcZefgnZLykbVH5cw/AoHKsuX89f
A1Z63J3C7HmiKMZs5Lz+jzbN+I/LTr3VWTyjGfK/ArbGhCmtyiUBR9IzTZB7XVao
3Uadxc//buwqiXL0U5ljZBe+pCjGY1gyx844Dj37a2FA1taX7Tk=
=cWFI
-END PGP SIGNATURE End Message ---

Bug#973109: marked as done (node-react: FTBFS: TypeError: invalid options argument)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 18:49:08 +
with message-id 
and subject line Bug#973109: fixed in node-react 17.0.1+dfsg+~cs32.23.54-2
has caused the Debian Bug report #973109,
regarding node-react: FTBFS: TypeError: invalid options argument
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.)


-- 
973109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-react
Version: 17.0.1+dfsg+~cs32.23.54-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> node scripts/rollup/build.js
>  BUILDING  react.development.js (umd_dev)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  react.development.js (umd_dev)
> 
>  BUILDING  react.production.min.js (umd_prod)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  react.production.min.js (umd_prod)
> 
>  BUILDING  react.profiling.min.js (umd_profiling)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  react.profiling.min.js (umd_profiling)
> 
>  BUILDING  react.development.js (node_dev)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  react.development.js (node_dev)
> 
>  BUILDING  react.production.min.js (node_prod)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  react.production.min.js (node_prod)
> 
>  BUILDING  React-dev.js (fb_www_dev)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  React-dev.js (fb_www_dev)
> 
>  BUILDING  React-prod.js (fb_www_prod)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  React-prod.js (fb_www_prod)
> 
>  BUILDING  React-profiling.js (fb_www_profiling)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  React-profiling.js (fb_www_profiling)
> 
>  BUILDING  React-dev.js (rn_fb_dev)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects" option should be used instead. 
> "treeshake.pureExternalModules: true" is equivalent to 
> "treeshake.moduleSideEffects: 'no-external'"
> 
>  COMPLETE  React-dev.js (rn_fb_dev)
> 
>  BUILDING  React-prod.js (rn_fb_prod)
> 
> The "treeshake.pureExternalModules" option is deprecated. The 
> "treeshake.moduleSideEffects&quo

Bug#973109: marked as pending in node-react

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #973109 in node-react 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-react/-/commit/074c9aa2c0d69834981c6ffa944b1404ffdfa007


Add fix for node-mkdirp ≥ 1

Closes: #973109


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973109

Bug#973164: marked as done (python-deprecated: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 18:49:19 +
with message-id 
and subject line Bug#973164: fixed in python-deprecated 1.2.10-2
has caused the Debian Bug report #973164,
regarding python-deprecated: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build \
>   --buildsystem=pybuild \
>   --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_deprecated/build/deprecated
> copying deprecated/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_deprecated/build/deprecated
> copying deprecated/sphinx.py -> 
> /<>/.pybuild/cpython3_3.9_deprecated/build/deprecated
> copying deprecated/classic.py -> 
> /<>/.pybuild/cpython3_3.9_deprecated/build/deprecated
> running egg_info
> creating Deprecated.egg-info
> writing Deprecated.egg-info/PKG-INFO
> writing dependency_links to Deprecated.egg-info/dependency_links.txt
> writing requirements to Deprecated.egg-info/requires.txt
> writing top-level names to Deprecated.egg-info/top_level.txt
> writing manifest file 'Deprecated.egg-info/SOURCES.txt'
> reading manifest file 'Deprecated.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '.coveragerc'
> warning: no files found matching '*.yaml'
> warning: no previously-included files matching '*.py[cod]' found anywhere in 
> distribution
> warning: no previously-included files matching '__pycache__' found anywhere 
> in distribution
> warning: no previously-included files matching '*.so' found anywhere in 
> distribution
> warning: no previously-included files matching '*.dylib' found anywhere in 
> distribution
> warning: no previously-included files matching '.DS_Store' found anywhere in 
> distribution
> writing manifest file 'Deprecated.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_deprecated/build/deprecated
> copying deprecated/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_deprecated/build/deprecated
> copying deprecated/sphinx.py -> 
> /<>/.pybuild/cpython3_3.8_deprecated/build/deprecated
> copying deprecated/classic.py -> 
> /<>/.pybuild/cpython3_3.8_deprecated/build/deprecated
> running egg_info
> writing Deprecated.egg-info/PKG-INFO
> writing dependency_links to Deprecated.egg-info/dependency_links.txt
> writing requirements to Deprecated.egg-info/requires.txt
> writing top-level names to Deprecated.egg-info/top_level.txt
> reading manifest file 'Deprecated.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '.coveragerc'
> warning: no files found matching '*.yaml'
> warning: no previously-included files matching '*.py[cod]' found anywhere in 
> distribution
> warning: no previously-included files matching '__pycache__' found anywhere 
> in distribution
> warning: no previously-included files matching '*.so' found anywhere in 
> distribution
> warning: no previously-included files matching '*.dylib' found anywhere in 
> distribution
> warning: no previously-included files matching '.DS_Store' found anywhere in 
> distribution
> writing manifest file 'Deprecated.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_deprecated/build; python3.9 -m pytest 
> tests
> = t

Processed: Bug#973109 marked as pending in node-react

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973109 {Done: Xavier Guimard } [src:node-react] 
node-react: FTBFS: TypeError: invalid options argument
Added tag(s) pending.

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

Bug#973177: marked as done (python-geojson: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 18:49:24 +
with message-id 
and subject line Bug#973177: fixed in python-geojson 2.5.0-3
has caused the Debian Bug report #973177,
regarding python-geojson: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.9 3.8" returned exit code 13
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.)


-- 
973177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-geojson
Version: 2.5.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh  build --with python3 --buildsystem pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/geometry.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/mapping.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/feature.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/factory.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/codec.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/_version.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/examples.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/base.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> copying geojson/utils.py -> 
> /<>/.pybuild/cpython3_3.9_geojson/build/geojson
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/geometry.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/mapping.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/feature.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/factory.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/codec.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/_version.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/examples.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/base.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
> copying geojson/utils.py -> 
> /<>/.pybuild/cpython3_3.8_geojson/build/geojson
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:217: python3.9 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating geojson.egg-info
> writing geojson.egg-info/PKG-INFO
> writing dependency_links to geojson.egg-info/dependency_links.txt
> writing top-level names to geojson.egg-info/top_level.txt
> writing manifest file 'geojson.egg-info/SOURCES.txt'
> reading manifest file 'geojson.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.txt' under directory 'tests'
> writi

Bug#973242: CVE-2017-18925

[Moritz Muehlenhoff]

Package: opentmpfiles
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2017-18925:
https://github.com/OpenRC/opentmpfiles/issues/4

Cheers,
Moritz

Bug#973222: python-smoke-zephyr: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: python-smoke-zephyr
Version: 2.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-smoke-zephyr
> dpkg-buildpackage: info: source version 2.0.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Samuel Henrique 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_smoke-zephyr/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_smoke-zephyr/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-smoke-zephyr using existing 
> ./python-smoke-zephyr_2.0.0.orig.tar.gz
> dpkg-source: info: building python-smoke-zephyr in 
> python-smoke-zephyr_2.0.0-1.debian.tar.xz
> dpkg-source: info: building python-smoke-zephyr in 
> python-smoke-zephyr_2.0.0-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/configuration.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/utilities.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/argparse_types.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/job.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/requirements.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/configuration.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/utilities.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/argparse_types.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/job.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/requirements.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build; python3.9 -m 
> unittest discover -v -s /<>/tests -p "[a-z]*.py"
> test_bin_b64_type (argparse_types.ArgparseTypeTests) ... ok
> test_bin_hex_type (argparse_types.ArgparseTypeTests) ... ok
> test_dir_type (argparse_types.ArgparseTypeTests) ... ok
> test_log_level_type (argparse_types.ArgparseTypeTests) ... ok
> test_port_type (argparse_types.ArgparseTypeTests) ... ok
> test_timespan_type (argparse_types.ArgparseTypeTests) ... ok
> test_job_add (job.JobManagerTests) ... ok
> test_job_delete (job.JobManagerTests) ... ok
> test_job_disable (job.JobManagerTests) ... ok
> test_job_init (job.JobManagerTests) ... ok
> test_job_request_delete (job.JobManagerTests) ... ok
> test_job_run (job.JobManagerTest

Bug#973223: ktorrent: FTBFS: ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153: undefined reference to `TagLib::String::~String()'

[Lucas Nussbaum]

Source: ktorrent
Version: 5.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/ktorrent_mediaplayer.dir/playlist.cpp.o: in function 
> `kt::PlayList::data(QModelIndex const&, int) const':
> ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153:
>  undefined reference to `TagLib::String::~String()'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:122:
>  undefined reference to `TagLib::String::~String()'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:154:
>  undefined reference to `TagLib::String::~String()'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/ktorrent_5.2.0-1_unstable.log

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

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

Bug#973216: kio-extras: FTBFS: ld: CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10): undefined reference to `typein

[Lucas Nussbaum]

Source: kio-extras
Version: 4:19.12.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:/usr/include/c++/10/bits/stl_function.h:386:
>  more undefined references to 
> `TagLib::ByteVector::operator<(TagLib::ByteVector const&) const' follow
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10):
>  undefined reference to `typeinfo for TagLib::RIFF::AIFF::File'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x20):
>  undefined reference to `TagLib::RIFF::AIFF::File::tag() const'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x28):
>  undefined reference to `TagLib::RIFF::AIFF::File::audioProperties() const'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x30):
>  undefined reference to `TagLib::RIFF::AIFF::File::save()'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/kio-extras_19.12.3-1_unstable.log

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

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

Bug#973236: neo: FTBFS: AttributeError: 'NoneType' object has no attribute 'supported_objects'

[Lucas Nussbaum]

Source: neo
Version: 0.7.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e; for PY in python3.9 python3.8; do \
> [ ${PY#*.} -ge 7 ] || { echo "Skipping $PY - absent support in neo's 
> tests"; continue; }; \
> echo "I: Running Neo unittests using $PY"; \
> NOSETESTS_NO_NETWORK=1 $PY -m nose -s -v neo ;\
> done
> I: Running Neo unittests using python3.9
> /<>/neo/rawio/tdtrawio.py:117: SyntaxWarning: "is not" with a 
> literal. Did you mean "!="?
>   if self.sortname is not '':
> test_read_all (neo.rawio.tests.test_axographrawio.TestAxographRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_axonrawio.TestAxonRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_raw_protocol (neo.rawio.tests.test_axonrawio.TestAxonRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_bci2000rawio.TestBCI2000RawIO) ... SKIP: 
> Requires download of data from the web
> This test compares the output of ReachGraspIO.read_block() with the ... SKIP: 
> requires scipy
> This test compares the output of ReachGraspIO.read_block() with the ... SKIP: 
> requires scipy
> test_read_all (neo.rawio.tests.test_blackrockrawio.TestBlackrockRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_brainvisionrawio.TestBrainVisionRawIO) 
> ... SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_elanrawio.TestElanRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_examplerawio.TestExampleRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_intanrawio.TestIntanRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_micromedrawio.TestMicromedRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_neuralynxrawio.TestNeuralynxRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all 
> (neo.rawio.tests.test_neuroexplorerrawio.TestNeuroExplorerRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_neuroscoperawio.TestNeuroScopeRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_nixrawio.TestNixRawIO) ... SKIP: Requires 
> download of data from the web
> test_raise_error_if_discontinuous_files 
> (neo.rawio.tests.test_openephysrawio.TestOpenEphysRawIO) ... SKIP: Requires 
> download of data from the web
> test_raise_error_if_strange_timestamps 
> (neo.rawio.tests.test_openephysrawio.TestOpenEphysRawIO) ... SKIP: Requires 
> download of data from the web
> test_read_all (neo.rawio.tests.test_openephysrawio.TestOpenEphysRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_plexonrawio.TestPlexonRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all 
> (neo.rawio.tests.test_rawbinarysignalrawio.TestRawBinarySignalRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_rawmcsrawio.TestRawMCSRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_spike2rawio.TestSpike2RawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_tdtrawio.TestTdtRawIO) ... SKIP: Requires 
> download of data from the web
> test_read_all (neo.rawio.tests.test_winedrrawio.TestWinEdrRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_winwcprawio.TestWinWcpRawIO) ... SKIP: 
> Requires download of data from the web
> test_assert_readed_neo_object_is_compliant 
> (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... SKIP: Requires 
> download of data from the web
> test_load_lazy_objects (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) 
> ... SKIP: Requires download of data from the web
> test_read_then_write (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... 
> SKIP: Requires download of data from the web
> test_readed_with_lazy_is_compliant 
> (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... SKIP: Requires 
> download of data from the web
> test_write_then_read (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... 
> SKIP: Requires download of data from the web
> test_assert_

Bug#973217: python-fedora: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: python-fedora
Version: 0.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> file flask_fas.py (for module flask_fas) not found
> copying flask_fas_openid.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build
> creating /<>/.pybuild/cpython3_3.9_fedora/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests
> copying tests/test_urlutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/iterutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/urlutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/textutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/release.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> creating /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/test_openidbaseclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/functional_test_utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> copying fedora/tg2/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> copying fedora/tg2/utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidproxyclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/baseclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidbaseclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/proxyclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/bodhi.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/fas2.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/fasproxy.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/wiki.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidcclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/tg1utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/controllers.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/tg2utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/widgets.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/json.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/util.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/client.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> copying fedora/wsgi/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> copying fedora/wsgi/csrf.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/django
> copying fedora/django/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/django
> creating 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2/templates
> copying fedora/tg2/templates/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2/templates
> creating 
> /<>/.pybuild/cpython3_3.9

Bug#973227: dh-cmake: FTBFS: AttributeError: 'Changelog' object has no attribute 'get_version'

[Lucas Nussbaum]

Source: dh-cmake
Version: 0.6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package dh-cmake
> dpkg-buildpackage: info: source version 0.6
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Alastair McKinstry 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean  --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 28, in 
> version=debian_version_to_python_version(get_current_version()),
>   File "/<>/setup.py", line 17, in get_current_version
> return str(changelog.get_version())
> AttributeError: 'Changelog' object has no attribute 'get_version'
> E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.8" 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/dh-cmake_0.6_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.

Bug#973234: weechat-el: FTBFS: Symbol’s function definition is void: rx-form

[Lucas Nussbaum]

Source: weechat-el
Version: 0.5.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> sed -e s/@VERSION@/0.5.0/ weechat-pkg.el.in > weechat-pkg.el
> Creating documentation: README.html
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Package cl is deprecated
> Creating package tarball weechat-0.5.0.tar
> weechat Version: 0.5.0
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -l weechat-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Symbol’s function definition is void: rx-form
> dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval 
> "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -l 
> weechat-test.el --eval \(ert-run-tests-batch-and-exit\) returned exit code 255
> make: *** [debian/rules:5: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/weechat-el_0.5.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.

Bug#973232: minexpert2: FTBFS: ProgramWindow.cpp:2318:58: error: no matching function for call to ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, pappso::DataKind, std::size_t, std:

[Lucas Nussbaum]

Source: minexpert2
Version: 7.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/debian/build/src && /usr/bin/c++ 
> -DQCUSTOMPLOT_USE_LIBRARY -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
> -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src 
> -I/<>/debian/build/src/minexpert2_autogen/include 
> -I/<>/debian/build -I/<> -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -O3 -DNDEBUG   -Wno-unknown-pragmas -Wall 
> -pedantic -Wextra -fPIC -std=gnu++17 -o 
> CMakeFiles/minexpert2.dir/gui/ProgramWindow.cpp.o -c 
> /<>/src/gui/ProgramWindow.cpp
> /<>/src/gui/ProgramWindow.cpp: In member function ‘void 
> msxps::minexpert::ProgramWindow::finishedIntegratingQualifiedMassSpectrumVectorToDtRtMz(msxps::minexpert::QualifiedMassSpectrumVectorMassDataIntegrator*)’:
> /<>/src/gui/ProgramWindow.cpp:2318:58: error: no matching 
> function for call to 
> ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, 
> pappso::DataKind, std::size_t, std::size_t, double, double, double, double)’
>  2318 | qualified_mass_spectra_integrator->getColorMapMaxMz());
>   |  ^
> In file included from /<>/src/gui/BaseColorMapPlotWnd.hpp:44,
>  from 
> /<>/src/gui/DriftSpecMassSpecColorMapWnd.hpp:46,
>  from /<>/src/gui/ProgramWindow.hpp:71,
>  from /<>/src/gui/ProgramWindow.cpp:63:
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:42:3: note: 
> candidate: ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind, 
> pappso::DataKind, pappso::AxisScale, pappso::AxisScale, pappso::AxisScale, 
> std::size_t, std::size_t, double, double, double, double)’
>42 |   ColorMapPlotConfig(DataKind x_axis_data_kind,
>   |   ^~
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:42:3: note:   
> candidate expects 11 arguments, 8 provided
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:40:3: note: 
> candidate: ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig()’
>40 |   ColorMapPlotConfig();
>   |   ^~
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:40:3: note:   
> candidate expects 0 arguments, 8 provided
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: 
> candidate: ‘constexpr pappso::ColorMapPlotConfig::ColorMapPlotConfig(const 
> pappso::ColorMapPlotConfig&)’
>22 | struct PMSPP_LIB_DECL ColorMapPlotConfig
>   |   ^~
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note:   
> candidate expects 1 argument, 8 provided
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: 
> candidate: ‘constexpr 
> pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::ColorMapPlotConfig&&)’
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note:   
> candidate expects 1 argument, 8 provided
> /<>/src/gui/ProgramWindow.cpp: In member function ‘void 
> msxps::minexpert::ProgramWindow::finishedIntegratingQualifiedMassSpectrumVectorToRtDt(msxps::minexpert::QualifiedMassSpectrumVectorMassDataIntegrator*)’:
> /<>/src/gui/ProgramWindow.cpp:2571:58: error: no matching 
> function for call to 
> ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, 
> pappso::DataKind, std::size_t, std::size_t, double, double, double, double)’
>  2571 | qualified_mass_spectra_integrator->getColorMapMaxMz());
>   |  ^
> In file included from /<>/src/gui/BaseColorMapPlotWnd.hpp:44,
>  from 
> /<>/src/gui/DriftSpecMassSpecColorMapWnd.hpp:46,
>  from /<>/src/gui/ProgramWindow.hpp:71,
>  from /<>/src/gui/Progr

Processed (with 1 error): Merge supysonic FTBFS bugs

[Debian Bug Tracking System]

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

> severity 972717 serious
Bug #972717 [src:supysonic] supysonic fails tests with python3.9
Severity set to 'serious' from 'important'
> merge 972717 973191 973034
Bug #972717 [src:supysonic] supysonic fails tests with python3.9
Unable to merge bugs because:
blockedby of #973191 is '' not '972484'
blockedby of #973034 is '' not '972484'
Failed to merge 972717: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#973228: websploit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: websploit
Version: 4.0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package websploit
> dpkg-buildpackage: info: source version 4.0.4-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by SZ Lin (林上智) 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_websploit/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_websploit/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building websploit using existing 
> ./websploit_4.0.4.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building websploit in websploit_4.0.4-1.debian.tar.xz
> dpkg-source: info: building websploit in websploit_4.0.4-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_websploit/build/websploit
> copying websploit/websploit.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit
> copying websploit/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/ezcolor
> copying websploit/ezcolor/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/ezcolor
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/wifi_fap.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/wifi_fap_spam.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/http_sniffer.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/scan_network.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/wifi_deauth.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/scan_wifi.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/arp_spoof.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> creating /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core
> copying websploit/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/base
> copying websploit/core/base/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/base
> copying websploit/core/base/Base.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/base
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/output.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/about.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/version.py -

Bug#973219: python-murano-pkg-check: FTBFS: make[1]: pyversions: No such file or directory

[Lucas Nussbaum]

Source: python-murano-pkg-check
Version: 0.3.0-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + PKGOS_USE_PY2=no
> + shift
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.9 3.8
> + [ yes = no ]
> + [ no = yes ]
> + [ disabled = disabled ]
> + continue
> + [ 3.9 = disabled ]
> + echo 3.9
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + [ 3 = 3 ]
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -e .testr.conf ]
> + [ -x /usr/bin/testr-python3 ]
> + TESTR=testr
> + rm -rf .testrepository
> + testr init
> + mktemp -t
> + TEMP_REZ=/tmp/tmp.SLqI2h7pqi
> + PYTHON=python3.9 testr run --parallel --subunit
> + tee /tmp/tmp.SLqI2h7pqi
> + subunit2pyunit
> /<>/muranopkgcheck/tests/functional/test_cases.py:79: 
> YAMLLoadWarning: calling yaml.load_all() without Loader=... is deprecated, as 
> the default Loader is unsafe. Please read https://msg.pyyaml.org/load for 
> full details.
>   cases.extend(list(yaml.load_all(f)))
> Non-zero exit code (2) from test listing.
> running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
> OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
> OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
> ${PYTHON:-python} -m subunit.run discover -t ./ . --list 
> --- import errors ---
> Failed to import test module: muranopkgcheck.tests.test_error
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_error.py", line 15, in 
> 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_log
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_log.py", line 15, in 
> 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_manager
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_manager.py", line 15, in 
> 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_manifest_validator
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_manifest_validator.py", 
> line 16, in 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_muranopl_validator
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_muranopl_validator.py", 
> line 16, in 
> import mock
> ModuleNotFoundError: No modu

Bug#973230: cura: FTBFS: plugins/Toolbox/src/AuthorsModel.py:71: error: Argument "key" to "sort" of "list" has incompatible type "Callable[[Dict[str, Union[str, List[str], int, None]]], Union[str, Lis

[Lucas Nussbaum]

Source: cura
Version: 4.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j4
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: invalid-imports
>   Start  2: pytest-main
>   Start  3: pytest-FirmwareUpdateChecker
>   Start  4: pytest-LegacyProfileReader
>  1/14 Test  #1: invalid-imports ..   Passed0.13 sec
>   Start  5: pytest-PostProcessingPlugin
>  2/14 Test  #3: pytest-FirmwareUpdateChecker .   Passed0.69 sec
>   Start  6: pytest-VersionUpgrade25to26
>  3/14 Test  #4: pytest-LegacyProfileReader ...   Passed0.73 sec
>   Start  7: pytest-VersionUpgrade26to27
>  4/14 Test  #6: pytest-VersionUpgrade25to26 ..   Passed0.29 sec
>   Start  8: pytest-VersionUpgrade27to30
>  5/14 Test  #7: pytest-VersionUpgrade26to27 ..   Passed0.27 sec
>   Start  9: pytest-VersionUpgrade34to35
>  6/14 Test  #8: pytest-VersionUpgrade27to30 ..   Passed0.29 sec
>   Start 10: pytest-VersionUpgrade43to44
>  7/14 Test  #9: pytest-VersionUpgrade34to35 ..   Passed0.26 sec
>   Start 11: pytest-VersionUpgrade44to45
>  8/14 Test  #5: pytest-PostProcessingPlugin ..   Passed1.17 sec
>   Start 12: pytest-XmlMaterialProfile
>  9/14 Test #10: pytest-VersionUpgrade43to44 ..   Passed0.26 sec
>   Start 13: code-style
> 10/14 Test #11: pytest-VersionUpgrade44to45 ..   Passed0.28 sec
>   Start 14: shortcut-keys
> 11/14 Test #14: shortcut-keys    Passed0.26 sec
> 12/14 Test #12: pytest-XmlMaterialProfile    Passed1.18 sec
> 13/14 Test #13: code-style ...***Failed   21.02 sec
> Success: no issues found in 4 source files
> Success: no issues found in 162 source files
> Success: no issues found in 2 source files
> Success: no issues found in 3 source files
> Success: no issues found in 7 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 7 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 3 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 3 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 6 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> plugins/Toolbox/src/AuthorsModel.py:71: error: Argument "key" to "sort" of 
> "list" has incompatible type "Callable[[Dict[str, Union[str, List[str], int, 
> None]]], Union[str, List[str], int, None]]"; expected "Callable[[Dict[str, 
> Union[str, List[str], int, None]]], _SupportsLessThan]"
> plugins/Toolbox/src/AuthorsModel.py:71: error: Incompatible return value type 
> (got "Union[str, List[str], int, None]", expected "_SupportsLessThan")
> Success: no issues found in 2 source files
> Found 2 errors in 1 file (checked 17 source files)
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 53 source files
> Success: no issues found in 10 source files
> Success: no issues found in 3 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no is

Bug#973226: python-django-celery-beat: FTBFS: ModuleNotFoundError: No module named 'celery.five'

[Lucas Nussbaum]

Source: python-django-celery-beat
Version: 1.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/apps.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/models.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/schedulers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/managers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/admin.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0003_auto_20161209_0049.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0004_auto_20170221_.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying 
> django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0001_initial.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/apps.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/models.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/schedulers.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/managers.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/admin.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/utils.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> creating 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0003_auto_20161209_0049.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0004_auto_20170221_.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying 
> django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_c

Bug#973221: soundkonverter: FTBFS: MetaReplayGain.h:25:10: fatal error: fileref.h: No such file or directory

[Lucas Nussbaum]

Source: soundkonverter
Version: 3.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame && 
> /usr/bin/c++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB -DQT_CONCURRENT_LIB 
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -DSOUNDKONVERTER_KF5_BUILD -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -Dsoundkonverter_codec_lame_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame 
> -I/<>/src/plugins/soundkonverter_codec_lame 
> -I/<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame/soundkonverter_codec_lame_autogen/include
>  -I/<>/obj-x86_64-linux-gnu -I/<>/src -isystem 
> /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem 
> /usr/include/KF5/KIOGui -isystem /usr/include/KF5/KIOCore -isystem 
> /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem 
> /usr/include/KF5/KConfigCore -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KJobWidgets -isystem 
> /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KBookmarks -isystem 
> /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KXmlGui -isystem 
> /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
> /usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem 
> /usr/include/KF5/Solid -isystem /usr/include/KF5/KDELibs4Support -isystem 
> /usr/include/KF5/KDELibs4Support/KDE -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/KF5/KCrash -isystem /usr/include/KF5/KI18n -isystem 
> /usr/include/KF5/KNotifications -isystem /usr/include/KF5/KIconThemes 
> -isystem /usr/include/KF5/KGuiAddons -isystem 
> /usr/include/KF5/KUnitConversion -isystem /usr/include/KF5/KTextWidgets 
> -isystem /usr/include/KF5/SonnetUi -isystem /usr/include/KF5/KParts -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -Wno-deprecated-declarations -fno-operator-names -fno-exceptions -Wall 
> -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
> -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
> -Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fPIC 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o 
> CMakeFiles/soundkonverter_codec_lame.dir/lameconversionoptions.cpp.o -c 
> /<>/src/plugins/soundkonverter_codec_lame/lameconversionoptions.cpp
> In file included from /<>/src/configdialog/../pluginloader.h:15,
>  from /<>/src/configdialog/../config.h:10,
>  from 
> /<>/src/configdialog/configcoverartpage.cpp:4:
> /<>/src/configdialog/../core/codecplugin.h:36:21: warning: 
> ‘virtual QString CodecPlugin::type() const’ can be marked override 
> [-Wsuggest-override]
>36 | virtual QString type() const;
>   | ^~~~
> In file included from /<>/src/configdialog/../pluginloader.h:16,
>  from /<>/src/configdialog/../config.h:10,
>  from 
> /<>/src/configdialog/configcoverartpage.cpp:4:
> /<>/src/configdialog/../core/filterplugin.h:42:21: warning: 
> ‘virtual QString FilterPlugin::type() const’ can be marked override 
> [-Wsuggest-override]
>42 | virtual QString type() const;
>   | ^~~~
> In file included from /<>/src/configdialog/../pluginloader.h:17,
>  from /<>/src/configdialog/../config.h:10,
>  from 
> /<>/src/configdialog/configcoverartpage.cpp:4:
> /<>/src/configdialog/../core/replaygainplugin.h:57:21: warning: 
> ‘virtual QString ReplayGainPlugin::type() const’ can be marked override 
> [-Wsuggest-override]
>57 | virtual QString type() const;
>   | ^~~~
&

Bug#973238: typedload: FTBFS: typedload/datadumper.py:159: error: NotImplemented? not callable

[Lucas Nussbaum]

Source: typedload
Version: 2.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> mypy --config-file mypy.conf typedload
> typedload/datadumper.py:159: error: NotImplemented? not callable
> Found 1 error in 1 file (checked 5 source files)
> make[2]: *** [Makefile:9: mypy] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/typedload_2.2-1_unstable.log

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

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

Bug#973229: golang-gopkg-alecthomas-kingpin.v3: FTBFS: src/gopkg.in/alecthomas/kingpin.v3/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n"

[Lucas Nussbaum]

Source: golang-gopkg-alecthomas-kingpin.v3
Version: 3.0~git20180227.b8d601d-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> gopkg.in/alecthomas/kingpin.v3
> src/gopkg.in/alecthomas/kingpin.v3/i18n_init.go:13:2: cannot find package 
> "github.com/nicksnyder/go-i18n/i18n" in any of:
>   /usr/lib/go-1.15/src/github.com/nicksnyder/go-i18n/i18n (from $GOROOT)
>   
> /<>/obj-x86_64-linux-gnu/src/github.com/nicksnyder/go-i18n/i18n 
> (from $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> gopkg.in/alecthomas/kingpin.v3 returned exit code 1
> make: *** [debian/rules:7: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/golang-gopkg-alecthomas-kingpin.v3_3.0~git20180227.b8d601d-1_unstable.log

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

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

Bug#973231: pypng: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: pypng
Version: 0.0.20+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> copying code/png.py -> /<>/.pybuild/cpython3_3.9_png/build
> copying code/test_png.py -> /<>/.pybuild/cpython3_3.9_png/build
> copying code/pngsuite.py -> /<>/.pybuild/cpython3_3.9_png/build
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying code/png.py -> /<>/.pybuild/cpython3_3.8_png/build
> copying code/test_png.py -> /<>/.pybuild/cpython3_3.8_png/build
> copying code/pngsuite.py -> /<>/.pybuild/cpython3_3.8_png/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_png/build; 
> python3.9 -m unittest discover -v 
> test_L12 (test_png.Test)
> Test L12. ... ok
> test_L16_to_RGB (test_png.Test)
> asRGB() on 16-bit grey source. ... ok
> test_L2 (test_png.Test)
> Test L2 (and asRGB8). ... ok
> test_L3 (test_png.Test)
> Test L3. ... ok
> test_L4 (test_png.Test)
> Test L4. ... ok
> test_L7 (test_png.Test)
> Test L7. ... ok
> test_L8 (test_png.Test)
> Test L8. ... ok
> test_L9 (test_png.Test)
> Test L9. ... ok
> test_LA4 (test_png.Test)
> Create an LA image with bitdepth 4. ... ok
> test_LA_to_RGBA (test_png.Test)
> asRGBA() on LA source. ... ok
> test_L_to_RGB (test_png.Test)
> asRGB() on grey source. ... ok
> test_L_to_RGBA (test_png.Test)
> asRGBA() on grey source. ... ok
> test_L_trns_0 (test_png.Test)
> Create greyscale image with tRNS chunk. ... ok
> test_L_trns_tuple (test_png.Test)
> Using 1-tuple for transparent arg. ... ok
> test_P2 (test_png.Test)
> 2-bit palette. ... ok
> test_RGB_to_RGBA (test_png.Test)
> asRGBA8() on colour type 2 source. ... ok
> test_RGB_trns (test_png.Test)
> Test colour type 2 and tRNS chunk. ... ok
> test_alpha_trns (test_png.Test)
> alpha and transparent don't mix. ... ok
> test_background_bad (test_png.Test)
> Wrong background in constructor. ... ok
> test_background_rgb_unnatural (test_png.Test)
> non-integer background in constructor. ... ok
> test_background_unnatural (test_png.Test)
> non-integer background in constructor. ... ok
> test_bad_filter (test_png.Test)
> Test file that contains impossible filter type. ... ok
> test_bitdepth_bad (test_png.Test) ... ok
> test_cannot_length_check (test_png.Test)
> The length check cannot be used on an itertools.chain object. ... ok
> test_checksum_bad (test_png.Test)
> Chunk has bad checksum. ... ok
> test_chunk_after_idat (test_png.Test)
> Test with a PNG that has an ancillary chunk after IDAT chunks. ... ok
> test_chunk_short (test_png.Test)
> Chunk that is too short. ... ok
> test_chunk_truncated (test_png.Test)
> Chunk doesn't have length and type. ... ok
> test_deepen_palette (test_png.Test)
> Test that palette bitdepth can be increased, ... ok
> test_empty (test_png.Test)
> Test empty file. ... ok
> test_extra_pixels (test_png.Test)
> Test file that contains too many pixels. ... ok
> test_flat (test_png.Test)
> Test read_flat. ... ok
> test_from_array_L (test_png.Test) ... ok
> test_from_array_L16 (test_png.Test) ... ok
> test_from_array_L2 (test_png.Test) ... ok
> test_from_array_LA (test_png.Test) ... ok
> test_from_array_LA_alpha_bad (test_png.Test) ... ok
> test_from_array_LA_bitdepth_bad (test_png.Test) ... ok
> test_from_array_LA_grey_bad (test_png.Test) ... ok
> test_from_array_RGB (test_png.Test) ... ok
> test_from_array_bad (test_png.Test)
> Invoke from_array incorrectly to provoke Error. ... ok
> test_from_array_iterator (test_png.Test) ... ok
> test_from_array_iterator_height (test_png.Test)
> Row iterator without height raises Error. ... ok
> test_from_array_width (test_png.Test)
> Test width argument. ... ok
> test_height_bad (test_png.Test)
> Wrong height in constructor. ... ok
> test_iend_missing (test_png.Test)
> Test file with missing IEND chunk. ... ok
> test_ihdr_compression (test_png.Test)
> Test file that has invalid compression IHDR value. ... ok
> test_ihdr_filter (te

Bug#973220: node-libnpx: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 123

[Lucas Nussbaum]

Source: node-libnpx
Version: 10.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> tail -n +2 README.md | marked-man --manual 'User Commands' --version 
> libnpx@$(dpkg-parsechangelog -S version) > libnpx.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/libnpx
>   /bin/sh -ex debian/tests/pkg-js/test
> + export LANG=C
> + export NODE_PATH=node_modules
> + pwd
> + export HOME=/<>
> + ls test/auto-fallback.js test/child.js test/get-prefix.js 
> test/guess-command-name.js test/index.js test/parse-args.js test/util.js
> + grep -v test/auto-fallback.js
> + xargs tap
> TAP version 13
> # Subtest: test/child.js
> # Subtest: escapeArg on *nix
> ok 1 - standard arg left intact
> ok 2 - '-escaped on *nix
> ok 3 - paths escaped as usual
> 1..3
> ok 1 - escapeArg on *nix # time=4.407ms
> 
> # Subtest: escapeArg on win32
> ok 1 - standard arg escaped
> ok 2 - "-escaped on win32
> ok 3 - paths escaped as usual
> 1..3
> ok 2 - escapeArg on win32 # time=1.253ms
> 
> # Subtest: exec
> ok 1 - command string concatenated
> ok 2 - options received!
> ok 3 - unix-style escapes
> ok 4 - win32-style escapes
> ok 5 - got error
> 1..5
> ok 3 - exec # time=11.291ms
> 
> # Subtest: exec (integration)
> ok 1 - node ran successfully
> ok 2 - got the exit code from subproc
> 1..2
> ok 4 - exec (integration) # time=149.221ms
> 
> # Subtest: spawn
> ok 1 - should be equivalent
> ok 2 - got the exit code from
> 1..2
> ok 5 - spawn # time=174.839ms
> 
> # Subtest: runCommand with command arg
> ok 1 - should be equivalent
> ok 2 - got the exit code from subproc
> ok 3 - error message reports ENOENT
> ok 4 - "not found" has code 127
> 1..4
> ok 6 - runCommand with command arg # time=152.75ms
> 
> # Subtest: runCommand with opts.command
> ok 1 - should be equivalent
> 1..1
> ok 7 - runCommand with opts.command # time=85.887ms
> 
> # Subtest: runCommand with opts.call and opts.shell
> ok 1 - should be equivalent
> 1..1
> ok 8 - runCommand with opts.call and opts.shell # time=68.64ms
> 
> 1..8
> # time=657.906ms
> ok 1 - test/child.js # time=828.454ms
> 
> # Subtest: test/get-prefix.js
> /usr/share/nodejs/tap/lib/extra-from-error.js:6
> if (!(k in set) && !/^tapChild/.test(k))
> ^
> 
> TypeError: Cannot use 'in' operator to search for 'name' in uncaughtException
> at /usr/share/nodejs/tap/lib/extra-from-error.js:6:13
> at Array.reduce ()
> at module.exports (/usr/share/nodejs/tap/lib/extra-from-error.js:5:38)
> at TAP.threw (/usr/share/nodejs/tap/lib/test.js:658:15)
> at process.emit (events.js:326:22)
> at process.emit 
> (/usr/share/nodejs/source-map-support/source-map-support.js:495:21)
> at processEmit [as emit] (/usr/share/nodejs/signal-exit/index.js:161:32)
> at process._fatalException (internal/process/execution.js:165:25)
> 1..0 # no tests found
> not ok 2 - test/get-prefix.js # time=190.364ms
>   ---
>   timeout: 3
>   file: test/get-prefix.js
>   command: /usr/bin/node
>   args:
> - test/get-prefix.js
>   stdio:
> - 0
> - pipe
> - 2
>   cwd: /<>
>   exitCode: 7
>   ...
> 
> # Subtest: test/guess-command-name.js
> # Subtest: guesses unscoped registry binaries
> ok 1 - should be equal
> 1..1
> ok 1 - guesses unscoped registry binaries # time=24.712ms
> 
> # Subtest: guesses scoped registry binaries
> ok 1 - should be equal
> 1..1
> ok 2 - guesses scoped registry binaries # time=0.911ms
> 
> # Subtest: guesses hosted git binaries
> ok 1 - should be equal
> ok 2 - should be equal
> 1..2
> ok 3 - guesses hosted git binaries # time=5.405ms
> 
> # Subtest: guesses git binaries
> ok 1 - should be equal
> ok 2 - should be equal
> 1..2
> ok 4 - guesses git binaries # time=1.544ms
> 
> # Subtest: leaves local directory/file commands intact
> ok 1 - should be equal
> ok 2 - should be

Bug#973233: tinc: FTBFS: configure: error: VDE plug header files not found.

[Lucas Nussbaum]

Source: tinc
Version: 1.0.36-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking libvdeplug_dyn.h usability... no
> checking libvdeplug_dyn.h presence... no
> checking for libvdeplug_dyn.h... no
> configure: error: VDE plug header files not found.
>   tail -v -n \+0 config.log

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/tinc_1.0.36-1_unstable.log

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

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

Bug#973218: localslackirc: FTBFS: rocket.py:213: error: NotImplemented? not callable

[Lucas Nussbaum]

Source: localslackirc
Version: 1.10-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> MYPYPATH=stubs mypy --config-file mypy.conf irc.py
> rocket.py:213: error: NotImplemented? not callable
> rocket.py:216: error: NotImplemented? not callable
> rocket.py:219: error: NotImplemented? not callable
> rocket.py:222: error: NotImplemented? not callable
> rocket.py:225: error: NotImplemented? not callable
> rocket.py:257: error: NotImplemented? not callable
> rocket.py:278: error: NotImplemented? not callable
> rocket.py:281: error: NotImplemented? not callable
> Found 8 errors in 1 file (checked 1 source file)
> make[1]: *** [Makefile:6: lint] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/localslackirc_1.10-1_unstable.log

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

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

Bug#973239: python-fixtures: FTBFS: ValueError: not enough values to unpack (expected 2, got 1)

[Lucas Nussbaum]

Source: python-fixtures
Version: 3.0.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -x ; set -e ; for i in 3.9 3.8 ; do \
>   python$i -m testtools.run fixtures.test_suite ; \
> done
> + set -e
> + python3.9 -m testtools.run fixtures.test_suite
> /usr/lib/python3.9/runpy.py:127: RuntimeWarning: 'testtools.run' found in 
> sys.modules after import of package 'testtools', but prior to execution of 
> 'testtools.run'; this may result in unpredictable behaviour
>   warn(RuntimeWarning(msg))
> Tests running...
> ==
> ERROR: 
> fixtures.tests._fixtures.test_monkeypatch.TestMonkeyPatch.test_patch_classmethod_with_boundmethod
> --
> Traceback (most recent call last):
>   File "/<>/fixtures/tests/_fixtures/test_monkeypatch.py", line 
> 223, in test_patch_classmethod_with_boundmethod
> slf, cls = C.foo_cls()
> TypeError: bar_two_args() missing 1 required positional argument: 'arg'
> ==
> ERROR: 
> fixtures.tests._fixtures.test_monkeypatch.TestMonkeyPatch.test_patch_classmethod_with_classmethod
> --
> Traceback (most recent call last):
>   File "/<>/fixtures/tests/_fixtures/test_monkeypatch.py", line 
> 191, in test_patch_classmethod_with_classmethod
> cls, target_class = C.foo_cls()
> ValueError: not enough values to unpack (expected 2, got 1)
> 
> Ran 128 tests in 2.017s
> FAILED (failures=2)
> make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/python-fixtures_3.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.

Bug#973224: uwsgi-apparmor: FTBFS: make[1]: pyversions: No such file or directory

[Lucas Nussbaum]

Source: uwsgi-apparmor
Version: 0.0.0+git.2014.09.15.7d6d7bd7eb-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> make: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> dh build
>dh_update_autotools_config
>dh_autoreconf
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e && for pyvers in 3.9 3.8; do \
>   PYTHON=python$pyvers uwsgi --build-plugin . ;\
> done
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-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.

Bug#973235: golang-github-c-bata-go-prompt: FTBFS: src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find package "golang.org/x/sys/unix"

[Lucas Nussbaum]

Source: golang-github-c-bata-go-prompt
Version: 0.2.3+git20181109.b6d2b43-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer
> src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find package 
> "golang.org/x/sys/unix" in any of:
>   /usr/lib/go-1.15/src/golang.org/x/sys/unix (from $GOROOT)
>   /<>/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix (from 
> $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer returned 
> exit code 1
> make: *** [debian/rules:4: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/golang-github-c-bata-go-prompt_0.2.3+git20181109.b6d2b43-1_unstable.log

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

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

Bug#973237: ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, :httponly, :defer, :renew, :sidbits, :secure_random, :redis_s

[Lucas Nussbaum]

Source: ruby-redis-rack
Version: 2.1.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, 
> :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
> /usr/share/rubygems-integration/all/gems/redis-4.2.2/lib/redis.rb:836:in 
> `set'
> /usr/lib/ruby/vendor_ruby/redis/store/interface.rb:9:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/ttl.rb:8:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `block in set'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:39:in `_marshal'
> /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `set'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `block in set'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:84:in `namespace'
> /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `set'
> /<>/lib/rack/session/redis.rb:49:in `block (2 levels) in 
> write_session'
> /<>/lib/redis/rack/connection.rb:22:in `with'
> /<>/lib/rack/session/redis.rb:82:in `with'
> /<>/lib/rack/session/redis.rb:49:in `block in write_session'
> /<>/lib/rack/session/redis.rb:70:in `with_lock'
> /<>/lib/rack/session/redis.rb:48:in `write_session'
> /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:399:in 
> `commit_session'
> /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:279:in `context'
> /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:271:in `call'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:77:in `request'
> /usr/lib/ruby/vendor_ruby/rack/mock.rb:59:in `get'
> /<>/test/rack/session/redis_test.rb:165:in `block (3 levels) 
> in '
> /<>/test/rack/session/redis_test.rb:396:in 
> `with_pool_management'
> /<>/test/rack/session/redis_test.rb:163:in `block (2 levels) 
> in '
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
> 34 runs, 78 assertions, 0 failures, 10 errors, 0 skips
> pkill redis-server
> rake aborted!
> Tests failed
> /<>/debian/ruby-tests.rake:12:in `block in '
> /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in ` (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/ruby-redis-rack_2.1.2-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.

Processed: Bug#947529 marked as pending in gnome-chemistry-utils

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #947529 [src:gnome-chemistry-utils] gnome-chemistry-utils: build-depends on 
deprecated gnome-doc-utils
Added tag(s) pending.

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

Bug#972728: marked as done (python-latexcodec: ftbfs with python 3.9 as supported version)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 18:34:34 +
with message-id 
and subject line Bug#972728: fixed in python-latexcodec 2.0.1-1
has caused the Debian Bug report #972728,
regarding python-latexcodec: ftbfs with python 3.9 as supported version
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.)


-- 
972728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-latexcodec
Version: 1.0.7-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
User: debian-pyt...@lists.debian.org
Usertags: python3.9

Dear Maintainer,

I think an upstream update will fix this.

Cheers,
mwh

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-51-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: python-latexcodec
Source-Version: 2.0.1-1
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated python-latexcodec 
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, 27 Oct 2020 21:12:56 +0300
Source: python-latexcodec
Architecture: source
Version: 2.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Dmitry Shachnev 
Closes: 972728 973032
Changes:
 python-latexcodec (2.0.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Dmitry Shachnev ]
   * New upstream release.
 - Compatible with Python 3.9 (closes: #972728, #973032).
   * Add GitLab CI configuration.
   * Switch from nose to pytest for testing.
Checksums-Sha1:
 cc703f953e5c30e882f55c0372724f384426e64f 2361 python-latexcodec_2.0.1-1.dsc
 ffe1124614cebac89635687d4a5b4d1e26c8f847 30131 
python-latexcodec_2.0.1.orig.tar.gz
 ebc89c013221f71d9f5c3ef163de837b336a3906 4080 
python-latexcodec_2.0.1-1.debian.tar.xz
 724b2319e86b0023242465867df2deaebb9f0458 7925 
python-latexcodec_2.0.1-1_source.buildinfo
Checksums-Sha256:
 117b13ede547f36d88aa1ea563a8ca037175f5d2cf677a2c3f034a62997e8c25 2361 
python-latexcodec_2.0.1-1.dsc
 2aa2551c373261cefe2ad3a8953a6d6533e68238d180eb4bb91d7964adb3fe9a 30131 
python-latexcodec_2.0.1.orig.tar.gz
 5916b670c572ebf1ff2c694b715d788bf69753964951cebb11d3f1fb5506b1b7 4080 
python-latexcodec_2.0.1-1.debian.tar.xz
 22e2db8aa4a1281bf86a9b6d92ff6dd2d1f50d98893f11c15d16fc2a0fec9d4b 7925 
python-latexcodec_2.0.1-1_source.buildinfo
Files:
 82e1312b63673fafbc51b3db4c5c56a0 2361 python optional 
python-latexcodec_2.0.1-1.dsc
 49c379bbdd1d924941c155f3d4dd5a92 30131 python optional 
python-latexcodec_2.0.1.orig.tar.gz
 97e3f174d61522ecd5890d8e764cfec5 4080 python optional 
python-latexcodec_2.0.1-1.debian.tar.xz
 c720a0c90a660bf43aa9ef62175ecd72 7925 python optional 
python-latexcodec_2.0.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl+YZGMTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy7T5D/9Q/fUrbHOXGbEhobvHNV6TFotWjy8/
w2ZmozHFGtNAqdH+63lhVdOsXNzGt6AqdWrqzHOTJxemDEfMZu1wO+tEykJzojY8
XvNSZeLbaZYNVzl/L6c0l5v7GUSoO9SKIoVMP9HvZ5hqDxNrKamvBxwYWo9NmBUw
6aaF1TiREVcrqdQiac6JYnRZiPnzZkwlo2506u4wV8ha7hloYYnoCuYwzS/zDY6c

Bug#973032: marked as done (python-latexcodec's autopkg tests are failing with python3.9)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 18:34:34 +
with message-id 
and subject line Bug#973032: fixed in python-latexcodec 2.0.1-1
has caused the Debian Bug report #973032,
regarding python-latexcodec's autopkg tests are failing with python3.9
to be marked as done.

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

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


-- 
973032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-latexcodec
Version: 1.0.7-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

==
ERROR: test_install_example.test_install_example_3
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File
"/tmp/autopkgtest-lxc.mp1w7t9_/downtmp/autopkgtest_tmp/test/test_install_example.py",
line 24, in test_install_example_3
assert text_latex.decode("latex+latin1") == u"þ"
LookupError: unknown encoding: latex+latin1

==
ERROR: test_install_example.test_install_example_4
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File
"/tmp/autopkgtest-lxc.mp1w7t9_/downtmp/autopkgtest_tmp/test/test_install_example.py",
line 37, in test_install_example_4
codecs.encode(text_unicode, "ulatex+ascii")
LookupError: unknown encoding: ulatex+ascii

==
ERROR: test_double_quotes_unicode (test_latex_codec.TestDecoder)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.mp1w7t9_/downtmp/autopkgtest_tmp/test/test_latex_codec.py",
line 222, in test_double_quotes_unicode
self.decode(u"“á”", u"``á''".encode("utf8"), "utf8")
  File
"/tmp/autopkgtest-lxc.mp1w7t9_/downtmp/autopkgtest_tmp/test/test_latex_codec.py",
line 57, in decode
decoded, n = codecs.getdecoder(encoding)(text_latex)
  File "/usr/lib/python3.9/codecs.py", line 975, in getdecoder
return lookup(encoding).decode
LookupError: unknown encoding: latex+utf8
--- End Message ---
--- Begin Message ---
Source: python-latexcodec
Source-Version: 2.0.1-1
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated python-latexcodec 
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, 27 Oct 2020 21:12:56 +0300
Source: python-latexcodec
Architecture: source
Version: 2.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Dmitry Shachnev 
Closes: 972728 973032
Changes:
 python-latexcodec (2.0.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Dmitry Shachnev ]
   * New upstream release.
 - Compatible with Python 3.9 (closes: #972728, #973032).
   * Add GitLab CI configuration.
   * Switch from nose to pytest for testing.
Checksums-Sha1:
 cc703f953e5c30e882f55c0372724f384426e64f 2361 python-latexcodec_2.0.1-1.dsc
 ffe1124614cebac89635687d4a5b4d1e26c8f847 30131 
python-latexcodec_2.0.1.orig.tar.gz
 ebc89c013221f71d9f5c3ef163de837b336a3906 4080 
python-latexcodec_2.0.1-1.debian.tar.xz
 724b2319e86b0023242465867df2deaebb9f0458 7925 
python-latexcodec_2.0.1-1_source.buildinfo
Checksums-Sha256:
 

Bug#947529: marked as pending in gnome-chemistry-utils

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #947529 in gnome-chemistry-utils 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/debichem-team/gnome-chemistry-utils/-/commit/4bbcaec102cbf34c6ea0e3951234e978178ad155


Replace gnome-doc-utils by yelp-tools

  * d/control (Build-Depends): Replace gnome-doc-utils by yelp-tools.
  * d/*.install: Fix the help path and remove the scrollkeeper path.
  * d/patches/use-yelp.patch: Add patch (closes: #947529).
- Rewrite source to use yelp-tools instead of gnome-doc-utils.
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947529

Bug#973117: marked as pending in node-parse-json

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #973117 in node-parse-json 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-parse-json/-/commit/aa1db8000f87e737b22897938e56fe1e3a40ff72


Add build dependency to mocha (@types/mocha)

Closes: #973117


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973117

Processed: Bug#973117 marked as pending in node-parse-json

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973117 [src:node-parse-json] node-parse-json: FTBFS: tests failed
Added tag(s) pending.

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

Bug#943396: FTBFS on armhf: testsuite segfault

[Bernhard Übelacker]

Dear Maintainer,
a short addition.
The backtrace that I received building with CC=gcc-10 seems
to be the same as in #972665, therefore they might be related?

Kind regards,
Bernhard

Bug#973215: python-fluent-logger: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: python-fluent-logger
Version: 0.9.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-fluent-logger
> dpkg-buildpackage: info: source version 0.9.6-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Michal Arbet 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from 
> python-fluent-logger-0.9.6/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_fluent/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_fluent/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from 
> python-fluent-logger-0.9.6/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-fluent-logger using existing 
> ./python-fluent-logger_0.9.6.orig.tar.xz
> dpkg-source: info: building python-fluent-logger in 
> python-fluent-logger_0.9.6-2.debian.tar.xz
> dpkg-source: info: building python-fluent-logger in 
> python-fluent-logger_0.9.6-2.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> copying fluent/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> copying fluent/asyncsender.py -> 
> /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> copying fluent/asynchandler.py -> 
> /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> copying fluent/sender.py -> 
> /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> copying fluent/handler.py -> 
> /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> copying fluent/event.py -> 
> /<>/.pybuild/cpython3_3.9_fluent/build/fluent
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_fluent/build/fluent
> copying fluent/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_fluent/build/fluent
> copying fluent/asyncsender.py -> 
> /<>/.pybuild/cpython3_3.8_fluent/build/fluent
> copying fluent/asynchandler.py -> 
> /<>/.pybuild/cpython3_3.8_fluent/build/fluent
> copying fluent/sender.py -> 
> /<>/.pybuild/cpython3_3.8_fluent/build/fluent
> copying fluent/handler.py -> 
> /<>/.pybuild/cpython3_3.8_fluent/build/fluent
> copying fluent/event.py -> 
> /<>/.pybuild/cpython3_3.8_fluent/build/fluent
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_fluent/build; 
> python3.9 -m nose -v tests
> test_custom_field_fill_missing_fmt_key_is_true 
> (tests.test_asynchandler.TestHandler) ... ERROR
> test_custom_field_raise_exception (tests.test_asynchandler.TestHandler) ... ok
> test_custom_fmt (tests.test_asynchandler.TestHandler) ... ERROR
> test_custom_fmt_with_format_style (tests.test_asynchandler.TestHandler) ... 
> ERROR
> test_custom_fmt_with_template_style (tests.test_asynchandler.TestHandler) ... 
> ERROR
> test_exception_message (tests.test_asynchandler.TestHandler) ... ERROR
> test_json_encoded_message (tests.test_asynchandler.TestHandler) ... ERROR
> test_non_string_dict_message (tests.test_asynchandler.TestHandler) ... ERROR
> test_non_string_simple_message (test

Bug#973213: gqrx-sdr: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

[Lucas Nussbaum]

Source: gqrx-sdr
Version: 2.13.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_d5388.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
>  undefined reference to `pthread_create'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12:
>  undefined reference to `pthread_detach'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13:
>  undefined reference to `pthread_cancel'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14:
>  undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/gqrx-sdr_2.13.1-1_unstable.log

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

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