Bug#972952: [Pkg-javascript-devel] Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

[Xavier]

Le 26/10/2020 à 20:50, Paolo Greppi a écrit :
> Hi Xavier,
> 
> Il 26/10/20 20:24, Xavier ha scritto:
>> Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit :
>>>    ...
>>
>> Hi JS Team,
>>
>> yarnpkg is not in testing due to babel problems. Do you agree to
>> dicrease severity of this bug to allow mkdirp transition (or reassign
>> this bug to node-yarnpkg) ?
>>
>> Cheers,
>> Xavier
>>
> 
> I think this should be reassigned to node-yarnpkg and then escalated to
> upstream
> I volunteer to do the second part.
> 
> Paolo

Done, thanks!

migration from mkdirp 0.53 to 1.0.x is easy but I'm not able to patch
yarnpkg since build already fails for some babel reasons.
How to do migration:

1. replace any

  mkdirp( path <, mode>, function(err) {
if(err) throw err;
/* MAIN FUNCTION *>
  })

by:

  mkdirp( path <, mode> ).then( () => {
/* MAIN FUNCTION */
  }).catch( (err) => {
throw err
  })


2. replace any

  mkdirp( path <, mode>, callback )

by

  mkdirp( path <, mode> ).then( () => {
callback()
  }).catch( (err) => {
callback(err)
  })

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

[Michael Borgelt]

 Zitat von Sebastian Andrzej Siewior :



Could you please tell the permissions for
        /var/log/clamav/
        /var/log/clamav/freshclam.log
?
Sebastian


Hi Sebastian,
the permissions are:

/var/log/clamav
drwxr-xr-x   2 clamav    clamav  4,0K 27. Okt 08:14 clamav

ls -lah /var/log/clamav/
total 8,0K
drwxr-xr-x  2 clamav clamav 4,0K 27. Okt 08:14 .
drwxr-xr-x 26 root   root   4,0K 27. Okt 08:14 ..
-rw-r-  1 clamav adm   0 27. Okt 08:14 clamav.log
-rw-r-  1 clamav adm   0 27. Okt 08:14 freshclam.log

I have tried different permissions for the file and the directory  
without success. The obove permissions are after a clean reinstall off  
clamav package.


--
Michael Borgelt
e-mail: mich...@borgelt.org

Processed: reassign 972952 to yarnpkg, retitle 972952 to yarnpkg isn't compatible with recent node-mkdirp

[Debian Bug Tracking System]

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

> reassign 972952 yarnpkg
Bug #972952 [node-mkdirp] node-mkdirp 1.0 is incompatible with 0.5, breaks 
yarnpkg
Bug reassigned from package 'node-mkdirp' to 'yarnpkg'.
No longer marked as found in versions node-mkdirp/1.0.4-2.
Ignoring request to alter fixed versions of bug #972952 to the same values 
previously set
> retitle 972952 yarnpkg isn't compatible with recent node-mkdirp
Bug #972952 [yarnpkg] node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg
Changed Bug title to 'yarnpkg isn't compatible with recent node-mkdirp' from 
'node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg'.
> thanks
Stopping processing here.

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

Bug#972918: marked as done (virtualbox ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 07:48:41 +
with message-id 
and subject line Bug#972918: fixed in virtualbox 6.1.16-dfsg-3
has caused the Debian Bug report #972918,
regarding virtualbox 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.)


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

virtualbox 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/virtualbox_6.1.16-dfsg-1build1_amd64-2020-10-24T10:20:17Z.build

[...]
Checking for Python support:
  ** Python not found!
Check /<>/out/configure.log for details
make[1]: *** [debian/rules:44: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:39: build] Error 2
--- End Message ---
--- Begin Message ---
Source: virtualbox
Source-Version: 6.1.16-dfsg-3
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
virtualbox, 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.
Gianfranco Costamagna  (supplier of updated 
virtualbox 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 08:28:19 +0100
Source: virtualbox
Architecture: source
Version: 6.1.16-dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Virtualbox Team 
Changed-By: Gianfranco Costamagna 
Closes: 972918
Changes:
 virtualbox (6.1.16-dfsg-3) unstable; urgency=medium
 .
   * Add patch to support python3.9 (Closes: #972918)
Checksums-Sha1:
 eb06dae46923ca2f5c574b1626c8a3f27161e6bf 3625 virtualbox_6.1.16-dfsg-3.dsc
 d0f17c40b25f5a1feef45c9f3588097cabfe58cc 86048 
virtualbox_6.1.16-dfsg-3.debian.tar.xz
 ea0a4512a729cd94645569ce4670392368084d1c 25038 
virtualbox_6.1.16-dfsg-3_source.buildinfo
Checksums-Sha256:
 65f7ae16543c18dba942930514cbc3216156cdab5b04c53632b57e17f4fdd4ea 3625 
virtualbox_6.1.16-dfsg-3.dsc
 505668de2f728cc634b00f0e4e319a77d326606c0c01b13a43fcddec3c994bec 86048 
virtualbox_6.1.16-dfsg-3.debian.tar.xz
 e8e764db35b5471e8ecb121d80a8b796e6d62900c876f53e4be2f4e634ed407a 25038 
virtualbox_6.1.16-dfsg-3_source.buildinfo
Files:
 9efcda131755a460ea9a6e3920299afe 3625 contrib/misc optional 
virtualbox_6.1.16-dfsg-3.dsc
 3e93886a0427dc4cf4299d5ce81539bd 86048 contrib/misc optional 
virtualbox_6.1.16-dfsg-3.debian.tar.xz
 7223becc92ec0a7d235e2c41c468491b 25038 contrib/misc optional 
virtualbox_6.1.16-dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl+XzJoACgkQ808JdE6f
XdlMFhAApkQkoWt0N9z7hn8b78q5e5aU01ks4XKR2ZkC6+8hChu6xekhjjpPP5D9
jKrVlraNNDYbLQsqGxRsC83xVKFfjF+f6Zv8SEqR7M9d0yJy6dPjunv8MrcWgFUS
+yzOaHeXrsH7zvUpxz1U0Pu4zeKOrTKaxCHI4uYyZIwTpzIBRX2htyi/2cBhKe20
Vm0OH3yNR1hMw563lQMb3+22ueOWyaMOV5DCNyjWqDhCwNug+J+9i8/nJuJ9Ma5g
s/V4zh/gUHkM7HhpIp9ekYc4EMsv0FwU/cFvUOdm721Rn/EEeCdzVkhmh3RDpF87
CaxjHZeAmsyj6ZLBPgfkhr0PTZtV94WPDP9RRXtMGvyWndsYBbafLy0qsQjd39F9
GnDcZjK0zCMjq8c7grKQxd/YZh8jFW8/qxr43xw/OS8yEAP9ShTJa4iVTuxCMidM
udD9gpiH0mVZSPfp5Phq59a7bWJlBwPOtZDKez4InPCdGJzA/NtyifN7FD75Ebfi
EumUxiLsgZlAVp+42cZcn3S5IXJdlWP1HbvH+rw0K6RpF7/Rr+1ecN3w0QVGHN8p
1RMD+8Bt6ys0d1hNujgD3x0xDbn1oX7sXMz6Khn25zb9g+jCCxNMOp/mq3WaxLfp
pFYol5dhPhzEnkDQ50/+eSn2tEwOUEQ7a7zAMFMTxFH12yriIVI=
=5WFx
-END PGP SIGNATURE End Message ---

Processed: severity of 972952 is grave

[Debian Bug Tracking System]

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

> severity 972952 grave
Bug #972952 [yarnpkg] yarnpkg isn't compatible with recent node-mkdirp
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.

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

Bug#973007: gr-air-modes: FTBFS in unstable

[Graham Inggs]

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!

Bug#973008: gr-gsm: FTBFS in unstable

[Graham Inggs]

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!

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

[Martin Pitt]

Package: pcp
Version: 5.2.1-1
Severity: serious
Tags: patch

The recent 5.2.1-1 upload made a dependency change to pcp:

 Package: pcp 
-Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, libpcp-web1
+Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, bpftrace (>= 0.9.2), libpcp-web1

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:

  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.

  Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl, 
python3-pcp, python3, libpcp-web1
  Recommends: bpftrace (>= 0.9.2)

Thanks!

Martin

[1] https://packages.debian.org/sid/bpftrace
[2] https://tracker.debian.org/pkg/pcp


signature.asc
Description: PGP signature

Processed: Bug#972153 marked as pending in python-fakeredis

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #972153 [src:python-fakeredis] python-fakeredis autopkg test fails
Added tag(s) pending.

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

Bug#972153: marked as pending in python-fakeredis

[Ondřej Nový]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-fakeredis/-/commit/5e1edc4cddc3409f242b41bc6de1b63d1695456d


Add python3-pytest-mock to autopkgtests requirement (Closes: #972153).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/972153

Processed (with 1 error): forcibly merging 972153 972095

[Debian Bug Tracking System]

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

> forcemerge 972153 972095
Bug #972153 [src:python-fakeredis] python-fakeredis autopkg test fails
Unable to merge bugs because:
package of #972095 is 'python-fakeredis' not 'src:python-fakeredis'
Failed to forcibly merge 972153: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#972153: marked as done (python-fakeredis autopkg test fails)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 08:48:37 +
with message-id 
and subject line Bug#972153: fixed in python-fakeredis 1.4.4-1
has caused the Debian Bug report #972153,
regarding python-fakeredis autopkg test fails
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.)


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

python-fakeredis autopkg test fails. missing test dependency?


[...]
test/test_fakeredis.py::test_lastsave[FakeStrictRedis] PASSED[ 67%]
test/test_fakeredis.py::test_time[FakeStrictRedis] ERROR [ 67%]

 ERRORS 
_ ERROR at setup of test_time[FakeStrictRedis] _
file /tmp/autopkgtest-lxc.tksev830/downtmp/build.Tqp/src/test/test_fakeredis.py,
line 3361
  @fake_only
  def test_time(r, mocker):
E   fixture 'mocker' not found
>   available fixtures: cache, capfd, capfdbinary, caplog, capsys,
capsysbinary, cov, create_redis, doctest_namespace, fake_server,
is_redis_running, monkeypatch, no_cover, pytestconfig, r, record_property,
record_testsuite_property, record_xml_attribute, recwarn, tmp_path,
tmp_path_factory, tmpdir, tmpdir_factory
>   use 'pytest --fixtures [testpath]' for help on them.

/tmp/autopkgtest-lxc.tksev830/downtmp/build.Tqp/src/test/test_fakeredis.py:3361
=== 760 passed, 26 skipped, 1 error in 23.98 seconds ===
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:9:
DeprecationWarning: the imp module is deprecated in favour of importlib; see the
module's documentation for alternative uses
  import imp
autopkgtest [20:17:10]: test command1: ---]
autopkgtest [20:17:10]: test command1:  - - - - - - - - - - results - - - - - -
- - - -
command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: python-fakeredis
Source-Version: 1.4.4-1
Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= 

We believe that the bug you reported is fixed in the latest version of
python-fakeredis, 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.
Ondřej Nový  (supplier of updated python-fakeredis 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 09:29:34 +0100
Source: python-fakeredis
Architecture: source
Version: 1.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Ondřej Nový 
Closes: 972153
Changes:
 python-fakeredis (1.4.4-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
   * Add python3-pytest-mock to autopkgtests requirement (Closes: #972153).
Checksums-Sha1:
 4364ad914e34d25a23e6751d624c465d613af3da 2652 python-fakeredis_1.4.4-1.dsc
 9aa671ae7c010a87a7c112d3d1a00048e16cd000 65483 
python-fakeredis_1.4.4.orig.tar.gz
 ec1c1325fa5b4ea8e8a4d7f576ad8b2301a51d84 4124 
python-fakeredis_1.4.4-1.debian.tar.xz
 be75dd499209ef8fdd4dee2fd68e13a2a2303ec3 7901 
python-fakeredis_1.4.4-1_amd64.buildinfo
Checksums-Sha256:
 36c13022d4511926e56698345fdd15cb382e2ecbabf12a5ef3d46b5b9402d026 2652 
python-fakeredis_1.4.4-1.dsc
 db1642edb7bc35dcc6d4e7d017416a325b79986d59cad01d35c5274964362a92 65483 
python-fakeredis_1.4.4.orig.tar.gz
 f1ef73b3e3cb8375332bb6ef9cf3816e4068928f6abb957a02abb55e6ef69cef 4124 
python-fakeredis_1.4.4-1.debian.tar.xz
 66599d5cf4dbc8a64b92d23ed5dff034e9eb85295e50e42049887c5c0d3d35f6 7901 
python-fakeredis_1.4.4-1_amd64.buildinfo
Files:
 183728ef83f0e07de494d15085571025 2652 python optional 
python-fakeredis_1.4.4-1.dsc
 6439cee55e360949050101a02aba0d90 65483 python optional 
python-fakeredis_1.4.4.orig.tar.gz
 607b4800140d4dddc2362bc61331337d 4124 python optional 
python-fakeredis_1.4.4-1.debian.tar.xz
 bf273cd31267691923be4d7b392f55c0 7901 python

Processed: forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 972952 https://github.com/yarnpkg/yarn/issues/8417
Bug #972952 [yarnpkg] yarnpkg isn't compatible with recent node-mkdirp
Set Bug forwarded-to-address to 'https://github.com/yarnpkg/yarn/issues/8417'.
>
End of message, stopping processing here.

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

Bug#972974: clamav-freshclam start faild.

[jean-christophe manciot]

I confirm this issue on bullseye.
There is also a similar one with clamav-daemon:

# systemctl status clamav-daemon
● clamav-daemon.service - Clam AntiVirus userspace daemon
 Loaded: loaded (/lib/systemd/system/clamav-daemon.service;
enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/clamav-daemon.service.d
 └─extend.conf
 Active: failed (Result: exit-code) since Tue 2020-10-27 09:15:31
CET; 1s ago
   Docs: man:clamd(8)
 man:clamd.conf(5)
 https://www.clamav.net/documents/
Process: 1452534 ExecStartPre=/bin/mkdir -p /run/clamav
(code=exited, status=0/SUCCESS)
Process: 1452542 ExecStartPre=/bin/chown clamav /run/clamav
(code=exited, status=0/SUCCESS)
Process: 1452550 ExecStart=/usr/sbin/clamd --foreground=true
(code=exited, status=1/FAILURE)
   Main PID: 1452550 (code=exited, status=1/FAILURE)

Oct 27 09:15:31 hostname systemd[1]: Starting Clam AntiVirus userspace daemon...
Oct 27 09:15:31 hostname systemd[1]: Started Clam AntiVirus userspace daemon.
Oct 27 09:15:31 hostname clamd[1452550]: ERROR: lchown to user
'clamav' failed on
Oct 27 09:15:31 hostname clamd[1452550]: log file '/var/log/clamav/clamav.log'.
Oct 27 09:15:31 hostname clamd[1452550]: Error was 'Operation not permitted'
Oct 27 09:15:31 hostname clamd[1452550]: Tue Oct 27 09:15:31 2020 ->
^lchown to user 'clamav' failed on log file
'/var/log/clamav/clamav.log'.  Error >
Oct 27 09:15:31 hostname systemd[1]: clamav-daemon.service: Main
process exited, code=exited, status=1/FAILURE
Oct 27 09:15:31 hostname systemd[1]: clamav-daemon.service: Failed
with result 'exit-code'.

-- 
Jean-Christophe

Bug#972659: marked as done (libtss2-esys0: bumps SONAME without changing package name)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 10:00:13 +
with message-id 
and subject line Bug#972659: fixed in tpm2-tss 3.0.1-2
has caused the Debian Bug report #972659,
regarding libtss2-esys0: bumps SONAME without changing package name
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.)


-- 
972659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal

Hello,

libtpm2-tss bump the soname of its lib. Make the package
tpm2-abrmd needs to build against the latest libtpm2-tss.
Please see #972118

  nmu tpm2-abrmd:2.3.3-1 . ANY . -m 'Rebuild against the new
libtpm2-tss, see #972118.'

Thanks.|

Yours,
Paul
--- End Message ---
--- Begin Message ---
Source: tpm2-tss
Source-Version: 3.0.1-2
Done: Ying-Chun Liu (PaulLiu) 

We believe that the bug you reported is fixed in the latest version of
tpm2-tss, 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.
Ying-Chun Liu (PaulLiu)  (supplier of updated tpm2-tss 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Oct 2020 22:59:41 +0800
Source: tpm2-tss
Binary: libtss2-dev libtss2-esys0 libtss2-esys0-dbgsym libtss2-fapi1 
libtss2-fapi1-dbgsym libtss2-mu0 libtss2-mu0-dbgsym libtss2-rc0 
libtss2-rc0-dbgsym libtss2-sys1 libtss2-sys1-dbgsym libtss2-tcti-cmd0 
libtss2-tcti-cmd0-dbgsym libtss2-tcti-device0 libtss2-tcti-device0-dbgsym 
libtss2-tcti-mssim0 libtss2-tcti-mssim0-dbgsym libtss2-tcti-swtpm0 
libtss2-tcti-swtpm0-dbgsym libtss2-tctildr0 libtss2-tctildr0-dbgsym
Architecture: source amd64
Version: 3.0.1-2
Distribution: unstable
Urgency: low
Maintainer: Mathieu Trudel-Lapierre 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 libtss2-dev - TPM2 Software stack library - development files
 libtss2-esys0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-fapi1 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-mu0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-rc0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-sys1 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-tcti-cmd0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-tcti-device0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-tcti-mssim0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-tcti-swtpm0 - TPM2 Software stack library - TSS and TCTI libraries
 libtss2-tctildr0 - TPM2 Software stack library - TSS and TCTI libraries
Closes: 972659
Changes:
 tpm2-tss (3.0.1-2) unstable; urgency=low
 .
   * Splitting package based on library SONAME. (Closes: #972659)
Checksums-Sha1:
 eac58d8acccec6f2ef68f15778a1a253589d797e 2806 tpm2-tss_3.0.1-2.dsc
 27583045cbc18e0b5f69ea3a0605e51eff217514 13584 tpm2-tss_3.0.1-2.debian.tar.xz
 3229c4e1be2ed16df1d492c79ea1c6e6c4df96e6 66040 libtss2-dev_3.0.1-2_amd64.deb
 41c127c0a5b18fc5b385eefdecad587afb948d90 395188 
libtss2-esys0-dbgsym_3.0.1-2_amd64.deb
 ba6386f96b6acb5632404991760892d08497bebb 155060 libtss2-esys0_3.0.1-2_amd64.deb
 b9d34f78e35e2fc7ed9ebed0eed2d4e1f29193da 910892 
libtss2-fapi1-dbgsym_3.0.1-2_amd64.deb
 33dae7420eb46dae72519307c392d7209aff2f99 294340 libtss2-fapi1_3.0.1-2_amd64.deb
 f1d9251663bce0f26b7365e5afb2e2262f959b02 160044 
libtss2-mu0-dbgsym_3.0.1-2_amd64.deb
 ef16f76b575b398935d9d00cc6510e267a552231 75312 libtss2-mu0_3.0.1-2_amd64.deb
 3f96749b7e713c151b49031a99330af94271154e 7836 
libtss2-rc0-dbgsym_3.0.1-2_amd64.deb
 46b9f1470f000ba1698d0f7a24fbb7339a1038c5 26600 libtss2-rc0_3.0.1-2_amd64.deb
 be6d48584254faec21b3038d9860b35dc9ba84e9 199244 
libtss2-sys1-dbgsym_3.0.1-2_amd64.deb
 b35c1aaf82d62f713be412e31c5b9688a8504bdc 53412 libtss2-sys1_3.0.1-2_amd64.deb
 18ca20aa88e7d6ad39ff72c644240e23cfe1c474 25944 
libtss2-tcti-cmd0-dbgsym_3.0.1-2_amd64.deb
 14ec5ec7d7e5929be272a23b3f07a6084e008943 31576 
libtss2-tcti-cmd0_3.0.1-2_amd64.deb
 c76fa88b247ba4d7ea59c07a26b4811e8af70961 25168 
libtss2-tcti-device0-dbgsym_3.0.1-2_amd64.deb
 d0d5516

Bug#894789: marked as done (tightvnc-java: FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2020 10:00:11 +
with message-id 
and subject line Bug#894789: fixed in tightvnc-java 1.3.10-1
has caused the Debian Bug report #894789,
regarding tightvnc-java: FTBFS with openjdk-9
to be marked as done.

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

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


-- 
894789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tightvnc-java
Version: 1.2.7-9
Severity: serious
Tags: sid buster
Justification: fails to build from source

Hi,

tightvnc-java FTBFS with openjdk-9 as the default jdk:

 debian/rules build
dh build
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/tightvnc-java-1.2.7'
# Add here commands to compile the package.
/usr/bin/make
make[2]: Entering directory '/build/tightvnc-java-1.2.7'
javac -target 1.1 -source 1.3 -O VncViewer.java RfbProto.java AuthPanel.java 
VncCanvas.java OptionsFrame.java ClipboardFrame.java ButtonPanel.java 
DesCipher.java RecordingFrame.java SessionRecorder.java SocketFactory.java 
HTTPConnectSocketFactory.java HTTPConnectSocket.java ReloginPanel.java
warning: [options] bootstrap class path not set in conjunction with -source 1.3
error: Source option 1.3 is no longer supported. Use 1.6 or later.
error: Target option 1.1 is no longer supported. Use 1.6 or later.
Makefile:30: recipe for target 'VncViewer.class' failed
make[2]: *** [VncViewer.class] Error 2
make[2]: Leaving directory '/build/tightvnc-java-1.2.7'
debian/rules:16: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/tightvnc-java-1.2.7'
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


tightvnc-java_1.2.7-9.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tightvnc-java
Source-Version: 1.3.10-1
Done: Sven Geuer 

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

Debian distribution maintenance software
pp.
Sven Geuer  (supplier of updated tightvnc-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Oct 2020 09:35:03 +0200
Source: tightvnc-java
Binary: tightvnc-java
Architecture: source all
Version: 1.3.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Sven Geuer 
Description:
 tightvnc-java - TightVNC java applet and command line program
Closes: 533130 586415 894789 968001
Changes:
 tightvnc-java (1.3.10-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #533130).
   * New maintainer (Closes: #586415).
   * Add myself as uploader.
   * Fix FTBFS, set the java compiler's -target and -source options to the
 lowest values supported by OpenJDK 11 (Closes: #894789).
   * Update to packaging format "3.0 (quilt)".
 - Add d/source/format.
 - Add d/patches/series.
 - Add d/patches/fix-makefile.patch.
   * Patch the sources to build a named java package (Closes: #968001).
 - Add d/patches/make-it-a-named-package.patch.
 - Update d/jtightvncviewer.sh.
   * Switch to DH compat format and raise level.
 - Replace Build-Depends debhelper (>> 9) by debhelper-compat (= 13)
   in d/control.
 - Remove file d/compat.
   * Introduce watch file.
   * Revise d/rules.
   * Fix d/tightvnc-java.dirs.
   * More updates to d/control.
 - Change Section from contrib/web to web, there are no non-free
   dependencies nowadays.
 - Replace Build-Depends-indep by Build-Depends-Indep.
 - Add missing stanzas Root-Requires-Root, Vcs-Browser, Vcs-Git, Homepage.
   * In maintainer scripts call 'set -e' explicitly to make lintian happy.
   * Drop installation of class files from Makefile.
 - Update d/patches/fix-makefile.patch.
 - Update d/rules.
   * Revise d/copyright to comply with DEP-5.
   * Introduce d/upstream/metadata.
   * Introduce d/source/lintian-overrides.
   * Bump Standards-Version to 4.5.0.
   * Add d/gbp.conf.
 

Bug#972468: nvidia-driver 450.66-1

[Vincent Lefevre]

On 2020-10-27 10:34:13 +0100, Felix Stupp wrote:
> Can someone please mark the bug in a way that also the nvidia-driver
> package is affected / causing this bug so apt-listbugs can show this
> bug to users before upgrading the kernel / installing the
> nvidia-driver?

I had already marked linux-image-5.9.0-1-amd64 as being affected,
so that users who want to upgrade from 5.8 to this package should
be warned. BTW, as expected, this bug appears on

https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=linux-image-5.9.0-1-amd64

Also note that this bug is against
src:nvidia-graphics-drivers-legacy-390xx, while nvidia-driver is from
the nvidia-graphics-drivers source package. I don't know whether this
bug should be assigned to both source packages or a second bug is
needed.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#972156: closed by Debian FTP Masters (reply to handsome_feng ) (Bug#972156: fixed in kylin-video 2.1.1.1-1)

[Dmitry Shachnev]

On Tue, Oct 27, 2020 at 07:51:04AM +, Debian Bug Tracking System wrote:
>  kylin-video (2.1.1.1-1) unstable; urgency=medium
>  .
>[ Dmitry Shachnev ]
>* Fix build with Qt 5.15 again. (Closes: #972156)

This version works fine, thank you!

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

[Matthias Klose]

Control: severity -1 important

On 10/26/20 1:04 PM, Adrian Bunk wrote:
> Package: libgcc-s1
> Version: 10.2.0-15
> Severity: grave
> 
> On a buster system, with unstable pinned to low priority:

Lowering the severity. Feel free to correct me if this specific configuration
deserves RC severity.

Processed: Re: Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #972936 [libgcc-s1] libgcc-s1 needs Breaks: libgcc1 (<< 1:10)
Severity set to 'important' from 'grave'

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

Bug#973012: pybind11's autopkg tests are failing, blocking python3-defaults

[Matthias Klose]

Package: src:pybind11
Version: 2.5.0-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [19:02:38]: test command4: set -e ; cp -r tests ${AUTOPKGTEST_TMP} ;
cd ${AUTOPKGTEST_TMP}/tests ; cmake . ; make ; pytest-3
autopkgtest [19:02:38]: test command4: [---
-- The CXX compiler identification is GNU 10.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /usr/bin/python3.9 (found version "3.9")
-- Found PythonLibs: python3.9
-- Performing Test HAS_CPP14_FLAG
-- Performing Test HAS_CPP14_FLAG - Success
-- Setting tests build type to MinSizeRel as none was specified
-- Building tests with Eigen v3.3.8
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake
(found suitable version "1.71.0", minimum required is "1.56")
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- LTO enabled
-- Configuring done
-- Generating done
-- Build files have been written to:
/tmp/autopkgtest-lxc.adcars4k/downtmp/autopkgtest_tmp/tests
Scanning dependencies of target cross_module_gil_utils
[  2%] Building CXX object
CMakeFiles/cross_module_gil_utils.dir/cross_module_gil_utils.cpp.o
In file included from /usr/include/pybind11/pytypes.h:12,
 from /usr/include/pybind11/cast.h:13,
 from /usr/include/pybind11/attr.h:13,
 from /usr/include/pybind11/pybind11.h:44,
 from
/tmp/autopkgtest-lxc.adcars4k/downtmp/autopkgtest_tmp/tests/cross_module_gil_utils.cpp:9:
/usr/include/pybind11/detail/common.h:112:10: fatal error: Python.h: No such
file or directory
  112 | #include 
  |  ^~
compilation terminated.
make[2]: *** [CMakeFiles/cross_module_gil_utils.dir/build.make:82:
CMakeFiles/cross_module_gil_utils.dir/cross_module_gil_utils.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:157:
CMakeFiles/cross_module_gil_utils.dir/all] Error 2
make: *** [Makefile:103: all] Error 2
autopkgtest [19:02:39]: test command4: ---]
autopkgtest [19:02:39]: test command4:  - - - - - - - - - - results - - - - - -
- - - -
command4 FAIL non-zero exit status 2
autopkgtest [19:02:39]: test command4:  - - - - - - - - - - stderr - - - - - - -
- - -
In file included from /usr/include/pybind11/pytypes.h:12,
 from /usr/include/pybind11/cast.h:13,
 from /usr/include/pybind11/attr.h:13,
 from /usr/include/pybind11/pybind11.h:44,
 from
/tmp/autopkgtest-lxc.adcars4k/downtmp/autopkgtest_tmp/tests/cross_module_gil_utils.cpp:9:
/usr/include/pybind11/detail/common.h:112:10: fatal error: Python.h: No such
file or directory
  112 | #include 
  |  ^~
compilation terminated.
make[2]: *** [CMakeFiles/cross_module_gil_utils.dir/build.make:82:
CMakeFiles/cross_module_gil_utils.dir/cross_module_gil_utils.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:157:
CMakeFiles/cross_module_gil_utils.dir/all] Error 2
make: *** [Makefile:103: all] Error 2
autopkgtest [19:02:39]:  summary
command1 PASS
command2 PASS
command3 PASS
command4 FAIL non-zero exit status 2

Bug#972175: closed by Debian FTP Masters (reply to Thomas Pierson ) (Bug#972175: fixed in clementine 1.4.0~rc1+git346-g4e3e9c8d1+dfsg-1)

[Thomas Pierson]

Hi Dmitry,

I just uploaded a new version of clementine disabling projectm for now 
because I have also others issues related to its integration. I need a 
bit of time to work on this.


So for now the new version of clementine I uploaded include a new 
upstream version (small, 1 bugfix), a change of the repacking method 
and no depend on projectm so it should be ok to build on all arch.


And I will keep an eye on it for the migration to testing.
--
Thomas

Bug#973014: genshi's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:genshi
Version: 0.7.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9


ERROR: test_extract_i18n_msg_with_other_directives_nested
(genshi.filters.tests.i18n.MsgDirectiveTestCase)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/filters/tests/i18n.py",
line 792, in test_extract_i18n_msg_with_other_directives_nested
messages = list(translator.extract(tmpl.stream))
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/base.py",
line 454, in stream
self._prepare_self()
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/base.py",
line 473, in _prepare_self
self._stream = list(self._prepare(self._stream, inlined))
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/base.py",
line 490, in _prepare
directive, substream = cls.attach(self, substream, value,
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/directives.py",
line 718, in attach
return super(WithDirective, cls).attach(template, stream, value,
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/directives.py",
line 82, in attach
return cls(value, template, namespaces, *pos[1:]), stream
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/directives.py",
line 706, in __init__
Expression(node.value, template.filepath,
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/eval.py",
line 93, in __init__
self.code = _compile(node, self.source, mode=self.mode,
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/eval.py",
line 451, in _compile
tree = xform().visit(node)
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/astutil.py",
line 798, in visit
return visitor(node)
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/astutil.py",
line 820, in _clone
value = self.visit(value)
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/astutil.py",
line 798, in visit
return visitor(node)
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/astutil.py",
line 816, in _clone
value = [self.visit(x) for x in value]
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/astutil.py",
line 816, in 
value = [self.visit(x) for x in value]
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/astutil.py",
line 798, in visit
return visitor(node)
  File
"/tmp/autopkgtest-lxc.zz1p467h/downtmp/build.oV9/src/build/lib/genshi/template/eval.py",
line 640, in visit_Subscript
not isinstance(node.slice, _ast.Index):
AttributeError: module '_ast' has no attribute 'Index'

Bug#973015: python-adal's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-adal
Version: 1.2.2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

/usr/lib/python3.9/http/client.py:245:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = , mode = 'rb'
bufsize = -1

def makefile(self, mode='r', bufsize=-1):
"""Returns this fake socket's own tempfile buffer.

If there is an entry associated with the socket, the file
descriptor gets filled in with the entry data before being
returned.
"""
self._mode = mode
self._bufsize = bufsize

if self._entry:
t = threading.Thread(
target=self._entry.fill_filekind, args=(self.fd,)
)
t.start()
if self.timeout == socket._GLOBAL_DEFAULT_TIMEOUT:
timeout = None
else:
timeout = self.timeout
t.join(timeout)
>   if t.isAlive():
E   AttributeError: 'Thread' object has no attribute 'isAlive'

Bug#973016: python-cobra's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-cobra
Version: 0.18.1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

python-cobra assumes that all it's dependencies are packaged for all supported
python3 versions, but libsbml is not packaged that way.

Either package libsbml for all supported python3 versions, or don't assume in
python-cobra that packaging.

Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/cobra/__init__.py", line 40, in 
from cobra import io
  File "/usr/lib/python3/dist-packages/cobra/io/__init__.py", line 8, in 

from cobra.io.sbml import read_sbml_model, write_sbml_model, \
  File "/usr/lib/python3/dist-packages/cobra/io/sbml.py", line 41, in 
import libsbml
  File "/usr/lib/python3/dist-packages/libsbml/libsbml.py", line 22, in 
import _libsbml
ModuleNotFoundError: No module named '_libsbml'

Bug#973017: python-django-import-export 's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-django-import-export
Version: 2.4.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [19:11:54]: test command1: set -e ; for py in $(py3versions -r
2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c
"import import_export; print(import_export)" ; done
autopkgtest [19:11:54]: test command1: [---
Testing with python3.9:
bash: line 1: python3.9: command not found

Bug#973019: python-boto's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-boto
Version: 2.49.0-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ERROR: test_cloudsearch_erroneous_sdf
(tests.unit.cloudsearch.test_document.CloudSearchBadSDFTesting)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.dvcvqgv_/downtmp/autopkgtest_tmp/tests/unit/cloudsearch/test_document.py",
line 269, in test_cloudsearch_erroneous_sdf
document.commit()
  File "/usr/lib/python3/dist-packages/boto/cloudsearch/document.py", line 199,
in commit
r = session.post(url, data=sdf, headers={'Content-Type': 
'application/json'})
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 578, in post
return self.request('POST', url, data=data, json=json, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 530, in 
request
resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 643, in send
r = adapter.send(request, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 670, in
urlopen
httplib_response = self._make_request(
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 426, in
_make_request
six.raise_from(e, None)
  File "", line 3, in raise_from
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 421, in
_make_request
httplib_response = conn.getresponse()
  File "/usr/lib/python3.9/http/client.py", line 1343, in getresponse
response = self.response_class(self.sock, method=self._method)
  File "/usr/lib/python3.9/http/client.py", line 245, in __init__
self.fp = sock.makefile("rb")
  File "/usr/lib/python3/dist-packages/httpretty/core.py", line 438, in makefile
if t.isAlive():
AttributeError: 'Thread' object has no attribute 'isAlive'
 >> begin captured logging << 
urllib3.util.retry: DEBUG: Converted retries value: 5 -> Retry(total=5,
connect=None, read=None, redirect=None, status=None)
urllib3.connectionpool: DEBUG: Starting new HTTP connection (1):
doc-demo-userdomain.us-east-1.cloudsearch.amazonaws.com:80
- >> end captured logging << -

Bug#973020: python-azure's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-azure
Version: 20200927+git-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = , mode = 'rb'
bufsize = -1

def makefile(self, mode='r', bufsize=-1):
"""Returns this fake socket's own tempfile buffer.

If there is an entry associated with the socket, the file
descriptor gets filled in with the entry data before being
returned.
"""
self._mode = mode
self._bufsize = bufsize

if self._entry:
t = threading.Thread(
target=self._entry.fill_filekind, args=(self.fd,)
)
t.start()
if self.timeout == socket._GLOBAL_DEFAULT_TIMEOUT:
timeout = None
else:
timeout = self.timeout
t.join(timeout)
>   if t.isAlive():
E   AttributeError: 'Thread' object has no attribute 'isAlive'

/usr/lib/python3/dist-packages/httpretty/core.py:438: AttributeError

Bug#973018: python-etelemetry's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-etelemetry
Version: 0.2.0-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

=== FAILURES ===
___ test_get_project ___

def test_get_project():
repo = "invalidrepo"
with pytest.raises(ValueError):
get_project(repo)
repo = "github/hub"
>   res = get_project(repo)

test_client.py:24:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../client.py:59: in get_project
return res.json(encoding="utf-8")
/usr/lib/python3/dist-packages/requests/models.py:889: in json
return complexjson.loads(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

s = '{"version":"2.14.2"}', cls = 
object_hook = None, parse_float = None, parse_int = None, parse_constant = None
object_pairs_hook = None, kw = {'encoding': 'utf-8'}

def loads(s, *, cls=None, object_hook=None, parse_float=None,
parse_int=None, parse_constant=None, object_pairs_hook=None, **kw):
"""Deserialize ``s`` (a ``str``, ``bytes`` or ``bytearray`` instance
containing a JSON document) to a Python object.

``object_hook`` is an optional function that will be called with the
result of any object literal decode (a ``dict``). The return value of
``object_hook`` will be used instead of the ``dict``. This feature
can be used to implement custom decoders (e.g. JSON-RPC class hinting).

``object_pairs_hook`` is an optional function that will be called with 
the
result of any object literal decoded with an ordered list of pairs.  The
return value of ``object_pairs_hook`` will be used instead of the 
``dict``.
This feature can be used to implement custom decoders.  If 
``object_hook``
is also defined, the ``object_pairs_hook`` takes priority.

``parse_float``, if specified, will be called with the string
of every JSON float to be decoded. By default this is equivalent to
float(num_str). This can be used to use another datatype or parser
for JSON floats (e.g. decimal.Decimal).

``parse_int``, if specified, will be called with the string
of every JSON int to be decoded. By default this is equivalent to
int(num_str). This can be used to use another datatype or parser
for JSON integers (e.g. float).

``parse_constant``, if specified, will be called with one of the
following strings: -Infinity, Infinity, NaN.
This can be used to raise an exception if invalid JSON numbers
are encountered.

To use a custom ``JSONDecoder`` subclass, specify it with the ``cls``
kwarg; otherwise ``JSONDecoder`` is used.
"""
if isinstance(s, str):
if s.startswith('\ufeff'):
raise JSONDecodeError("Unexpected UTF-8 BOM (decode using
utf-8-sig)",
  s, 0)
else:
if not isinstance(s, (bytes, bytearray)):
raise TypeError(f'the JSON object must be str, bytes or 
bytearray, '
f'not {s.__class__.__name__}')
s = s.decode(detect_encoding(s), 'surrogatepass')

if (cls is None and object_hook is None and
parse_int is None and parse_float is None and
parse_constant is None and object_pairs_hook is None and not 
kw):
return _default_decoder.decode(s)
if cls is None:
cls = JSONDecoder
if object_hook is not None:
kw['object_hook'] = object_hook
if object_pairs_hook is not None:
kw['object_pairs_hook'] = object_pairs_hook
if parse_float is not None:
kw['parse_float'] = parse_float
if parse_int is not None:
kw['parse_int'] = parse_int
if parse_constant is not None:
kw['parse_constant'] = parse_constant
>   return cls(**kw).decode(s)
E   TypeError: __init__() got an unexpected keyword argument 'encoding'

/usr/lib/python3.9/json/__init__.py:359: TypeError
_ test_check_available _

def test_check_available():
repo = "invalidrepo"
res = check_available_version(repo, "0.1.0")
assert res is None
repo = "github/hub"
res = check_available_version(repo, "0.1.0")
>   assert "version" in res
E   TypeError: argument of type 'NoneType' is not iterable

test_client.py:49: TypeError
== 2 failed, 2 passed in 1.42 seconds ==

Bug#973022: python-blosc's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-blosc
Version: 1.8.1+ds1-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

==
FAIL: compress (blosc.toplevel)
Doctest: blosc.toplevel.compress
--
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 2204, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for blosc.toplevel.compress
  File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 396, in compress

--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 440, in
blosc.toplevel.compress
Failed example:
a_bytesobj = a.tostring()
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
a_bytesobj = a.tostring()
AttributeError: 'array.array' object has no attribute 'tostring'
--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 441, in
blosc.toplevel.compress
Failed example:
c_bytesobj = blosc.compress(a_bytesobj, typesize=4)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
c_bytesobj = blosc.compress(a_bytesobj, typesize=4)
NameError: name 'a_bytesobj' is not defined
--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 442, in
blosc.toplevel.compress
Failed example:
len(c_bytesobj) < len(a_bytesobj)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
len(c_bytesobj) < len(a_bytesobj)
NameError: name 'c_bytesobj' is not defined


==
FAIL: decompress (blosc.toplevel)
Doctest: blosc.toplevel.decompress
--
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 2204, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for blosc.toplevel.decompress
  File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 549, in 
decompress

--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 579, in
blosc.toplevel.decompress
Failed example:
a_bytesobj = a.tostring()
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
a_bytesobj = a.tostring()
AttributeError: 'array.array' object has no attribute 'tostring'
--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 580, in
blosc.toplevel.decompress
Failed example:
c_bytesobj = blosc.compress(a_bytesobj, typesize=4)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
c_bytesobj = blosc.compress(a_bytesobj, typesize=4)
NameError: name 'a_bytesobj' is not defined
--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 581, in
blosc.toplevel.decompress
Failed example:
a_bytesobj2 = blosc.decompress(c_bytesobj)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
a_bytesobj2 = blosc.decompress(c_bytesobj)
NameError: name 'c_bytesobj' is not defined
--
File "/usr/lib/python3/dist-packages/blosc/toplevel.py", line 582, in
blosc.toplevel.decompress
Failed example:
a_bytesobj == a_bytesobj2
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.9/doctest.py", line 1336, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
a_bytesobj == a_bytesobj2
NameError: name 'a_bytesobj' is not defined


--
Ran 37 tests in 4.209s

FAILED (failures=2)

Bug#973021: python-bitstring's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-bitstring
Version: 3.1.5-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

==
ERROR: testDouble (test_bits.InitFromArray)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.0phu_6mf/downtmp/autopkgtest_tmp/test/test_bits.py", line
420, in testDouble
b = Bits(a)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 796, in __new__
x._initialise(auto, length, offset, **kwargs)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 805, in _initialise
self._initialise_from_auto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 836, in
_initialise_from_auto
self._setauto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 1282, in _setauto
b = s.tostring()
AttributeError: 'array.array' object has no attribute 'tostring'

==
ERROR: testEmptyArray (test_bits.InitFromArray)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.0phu_6mf/downtmp/autopkgtest_tmp/test/test_bits.py", line
401, in testEmptyArray
b = Bits(a)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 796, in __new__
x._initialise(auto, length, offset, **kwargs)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 805, in _initialise
self._initialise_from_auto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 836, in
_initialise_from_auto
self._setauto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 1282, in _setauto
b = s.tostring()
AttributeError: 'array.array' object has no attribute 'tostring'

==
ERROR: testSignedShort (test_bits.InitFromArray)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.0phu_6mf/downtmp/autopkgtest_tmp/test/test_bits.py", line
414, in testSignedShort
b = Bits(a)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 796, in __new__
x._initialise(auto, length, offset, **kwargs)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 805, in _initialise
self._initialise_from_auto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 836, in
_initialise_from_auto
self._setauto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 1282, in _setauto
b = s.tostring()
AttributeError: 'array.array' object has no attribute 'tostring'

==
ERROR: testSingleByte (test_bits.InitFromArray)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.0phu_6mf/downtmp/autopkgtest_tmp/test/test_bits.py", line
406, in testSingleByte
b = Bits(a)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 796, in __new__
x._initialise(auto, length, offset, **kwargs)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 805, in _initialise
self._initialise_from_auto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 836, in
_initialise_from_auto
self._setauto(auto, length, offset)
  File "/usr/lib/python3/dist-packages/bitstring.py", line 1282, in _setauto
b = s.tostring()
AttributeError: 'array.array' object has no attribute 'tostring'

--
Ran 483 tests in 0.248s

FAILED (errors=4)

Bug#973026: python-executing's autopkg tests fail with python3.9

[Matthias Klose]

Package: src:python-executing
Version: 0.4.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [22:01:06]: test unittest: [---
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.0jbyozrd/downtmp/build.4ij/src/tests/test_main.py",
line 522, in 
assert tester[1 + 2] is tester
  File "/tmp/autopkgtest-lxc.0jbyozrd/downtmp/build.4ij/src/tests/utils.py",
line 45, in __getitem__
self.check(node.slice.value, item)
AttributeError: 'BinOp' object has no attribute 'value'
autopkgtest [22:01:07]: test unittest: ---]

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

[Matthias Klose]

Package: src:feature-check
Version: 0.2.2-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [18:46:41]: test tap-python.sh: [---


 Testing python3.9

'python3.9' -m feature_check "$@"

#   Failed test '-V succeeded'
#   at t/01-options.t line 47.
#  got: 127
# expected: 0

#   Failed test '-V did not output any errors'
#   at t/01-options.t line 48.
#  got: 'test-python/python/python_fcheck.sh: 1: python3.9: not 
found
# '
# expected: ''
Bailout called.  Further testing stopped:  Unexpected number of lines in the -V
output
FAILED--Further testing stopped: Unexpected number of lines in the -V output
autopkgtest [18:46:41]: test tap-python.sh: ---]
autopkgtest [18:46:41]: test tap-python.sh:  - - - - - - - - - - results - - - -
- - - - - -
tap-python.shFAIL non-zero exit status 253
autopkgtest [18:46:42]: test tap-python.sh:  - - - - - - - - - - stderr - - - -
- - - - - -

#   Failed test '-V succeeded'
#   at t/01-options.t line 47.
#  got: 127
# expected: 0

#   Failed test '-V did not output any errors'
#   at t/01-options.t line 48.
#  got: 'test-python/python/python_fcheck.sh: 1: python3.9: not 
found
# '
# expected: ''
FAILED--Further testing stopped: Unexpected number of lines in the -V output

Bug#973027: rdkit: FTBFS in unstable with postgresql 13

[Andrius Merkys]

Source: rdkit
Version: 202003.4-2
Severity: serious
Tags: ftbfs sid

Hello,

rdkit FTBFS in unstable with postgresql 13. From [1]:

dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control  2020-09-22 08:32:21.0 -1200
+++ debian/control.cexQZ6   2021-11-25 14:26:59.459300200 -1200
@@ -159,10 +159,10 @@
  .
  This package contains the header files.

-Package: postgresql-12-rdkit
+Package: postgresql-13-rdkit
 Architecture: any
 Section: database
-Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-12
+Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
 Suggests:
 Description: Cheminformatics and machine-learning software (PostgreSQL
Cartridge)
  RDKit is a Python/C++ based cheminformatics and machine-learning software
Error: debian/control needs updating from debian/control.in. Run
'pg_buildext updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is
required.
make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
debian/control] Error 1

However, replacing s/postgresql-12/postgresql-13/ does not fix the issue
as rdkit seemingly uses no longer present postgresql header file:

gcc -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Werror=vla -Wendif-labels
-Wmissing-format-attribute -Wimplicit-fallthrough=3 -W
format-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard
-Wno-format-truncation -Wno-stringop-truncation -g -g -O2
-fstack-protector-strong -W
format -Werror=format-security -fno-omit-frame-pointer -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/local/include
-I/<>/Code -DRDKITVER='"007300"'   -I.
-I/<>/Code/PgSQL/rdkit -I/usr/incl
ude/postgresql/13/server -I/usr/include/postgresql/internal  -Wdate-time
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  -fPIC -c -o
rdkit_gist.o /<
>/Code/PgSQL/rdkit/rdkit_gist.c
/<>/Code/PgSQL/rdkit/rdkit_gist.c:35:10: fatal error:
access/tuptoaster.h: No such file or directory
   35 | #include 
  |  ^
compilation terminated.
make[2]: *** [/<>/Code/PgSQL/rdkit/Makefile:109:
rdkit_gist.o] Error 1

Andrius

[1]
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/rdkit_202003.4-2.rbuild.log.gz

Bug#973023: invalid syntax in ecf.py

[Matthias Klose]

Package: src:ecflow
Version: 5.5.3-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

[...]
Setting up python3-ecflow (5.5.3-3) ...
/usr/lib/python3/dist-packages/ecflow/ecf.py:561: SyntaxWarning: "is" with a
literal. Did you mean "=="?
  if name is "":
Setting up autopkgtest-satdep (0) ...
Processing triggers for libc-bin (2.31-4) ...
(Reading database ... 13712 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...

Bug#973028: python-fabio's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-fabio
Version: 0.10.2+dfsg-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fabio/7758092/log.gz

Bug#973030: python-icecream's autopkg tests ar failing with python3.9

[Matthias Klose]

Package: src:python-icecream
Version: 2.0.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [23:11:12]: test unittest: [---
..EEE.
==
ERROR: testArgToStringFunction (tests.test_icecream.TestIceCream)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/tests/test_icecream.py",
line 361, in testArgToStringFunction
ic(eins)
  File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
172, in __call__
out = self._format(callFrame, *args)
  File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
206, in _format
out = self._formatArgs(
  File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
213, in _formatArgs
sanitizedArgStrs = [
  File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
214, in 
source.get_text_with_indentation(arg)
  File
"/tmp/autopkgtest-lxc.cpj9es1s/downtmp/build.Ibp/src/icecream/icecream.py", line
110, in get_text_with_indentation
result = self.asttokens().get_text(node)
  File "/usr/lib/python3/dist-packages/executing.py", line 340, in asttokens
return ASTTokens(
  File "/usr/lib/python3/dist-packages/asttokens/asttokens.py", line 65, in 
__init__
self.mark_tokens(self._tree)
  File "/usr/lib/python3/dist-packages/asttokens/asttokens.py", line 76, in
mark_tokens
MarkTokens(self).visit_tree(root_node)
  File "/usr/lib/python3/dist-packages/asttokens/mark_tokens.py", line 49, in
visit_tree
util.visit_tree(node, self._visit_before_children, 
self._visit_after_children)
  File "/usr/lib/python3/dist-packages/asttokens/util.py", line 186, in 
visit_tree
ret = postvisit(current, par_value, value)
  File "/usr/lib/python3/dist-packages/asttokens/mark_tokens.py", line 92, in
_visit_after_children
nfirst, nlast = self._methods.get(self, node.__class__)(node, first, last)
  File "/usr/lib/python3/dist-packages/asttokens/mark_tokens.py", line 330, in
visit_keyword
util.expect_token(name, token.NAME, node.arg)
  File "/usr/lib/python3/dist-packages/asttokens/util.py", line 56, in 
expect_token
raise ValueError("Expected token %s, got %s on line %s col %s" % (
ValueError: Expected token NAME:'outputFunction', got
NAME:'originalOutputFunction' on line 55 col 5

Bug#973032: python-latexcodec's autopkg tests are failing with python3.9

[Matthias Klose]

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

Bug#973033: python-molotov's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-molotov
Version: 1.6-7
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/7759352/log.gz

Bug#973013: ctdopts autopkg tests are failing, blocking python3-defaults

[Matthias Klose]

Package: src:ctdopts
Version: 1.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [07:37:47]: test run-example: [---
+ py3versions -r
+ echo Testing with python3.9:
+ python3.9 -c import CTDopts; print(CTDopts)
Testing with python3.9:

+ python3.9 /usr/share/doc/python3-ctdopts/examples/example.py
Model being written to exampleTool.ctd...

Model loaded from exampleTool.ctd...

For debugging purposes we can output a human readable representation of
Parameter objects. Here's the first one:
PARAMETER positive_int
  type: int
  default: 5
  tags: advanced, magic
  restrictions on numeric range: 0 to None
  description: A positive integer parameter

The following parameters were registered in the model:
['positive_int', 'input_files', 'output', 'this_that', 'param_1', 'param_2',
'param_3']

The same parameters with subgroup information, if they were registered under
parameter groups:
['positive_int', 'input_files', 'output', 'this_that', 'subparams:param_1',
'subparams:param_2', 'subparams:subsubparam:param_3']

A dictionary of parameters with default values, returned by 
CTDModel.get_defaults():
{   'positive_int': 5,
'subparams': {   'param_1': 5.5,
 'param_2': [0.0, 2.5, 5.0],
 'subsubparam': {'param_3': 2}},
'this_that': 'this'}

As you can see, parameter values are usually stored in nested dictionaries. If
you want a flat dictionary, you canget that using CTDopts.flatten_dict(). Flat
keys can be either tuples of tree node (subgroup) names down to the parameter...
{   ('positive_int',): 5,
('subparams', 'param_1'): 5.5,
('subparams', 'param_2'): [0.0, 2.5, 5.0],
('subparams', 'subsubparam', 'param_3'): 2,
('this_that',): 'this'}

...or they can be strings where nesing levels are separated by colons:
{   'positive_int': 5,
'subparams:param_1': 5.5,
'subparams:param_2': [0.0, 2.5, 5.0],
'subparams:subsubparam:param_3': 2,
'this_that': 'this'}

We can create dictionaries of arguments on our own that we want to validate
against the model.CTDopts can read them from argument-storing CTD files or from
the command line, but we can just define them in a nested dictionary on our own
as well. We start with defining them explicitly.
{   'input_files': ['file1.fastq', 'file2.fastq', 'file3.fastq'],
'positive_int': 111,
'subparams': {'param_1': '999.0'}}

We can validate these arguments against the model, and get a dictionary with
parameter types correctly casted and defaults set. Note that subparams:param_1
was casted from string to a floating point number because that's how it was
defined in the model.
{   'input_files': ['file1.fastq', 'file2.fastq', 'file3.fastq'],
'positive_int': 111,
'subparams': {   'param_1': 999.0,
 'param_2': [0.0, 2.5, 5.0],
 'subsubparam': {'param_3': 2}},
'this_that': 'this'}

We can write a CTD file containing these validated argument values. Just call
CTDModel.write_ctd() with an extra parameter: the nested argument dictionary
containing the actual values.

As mentioned earlier, CTDopts can load argument values from CTD files. Feel free
to change some values in exampleTool_preset_params.ctd you've just written, and
load it back.
Traceback (most recent call last):
  File "/usr/share/doc/python3-ctdopts/examples/example.py", line 165, in 

args_from_ctd = args_from_file('exampleTool_preset_params.ctd')
  File "/usr/lib/python3/dist-packages/CTDopts/CTDopts.py", line 1230, in
args_from_file
return get_args(parameters, base=None)
  File "/usr/lib/python3/dist-packages/CTDopts/CTDopts.py", line 1211, in 
get_args
get_args(child, current_group)
  File "/usr/lib/python3/dist-packages/CTDopts/CTDopts.py", line 1224, in 
get_args
if element.getchildren():
AttributeError: 'xml.etree.ElementTree.Element' object has no attribute
'getchildren'
autopkgtest [07:37:47]: test run-example: ---]
autopkgtest [07:37:47]: test run-example:  - - - - - - - - - - results - - - - -
- - - - -
run-example  FAIL non-zero exit status 1
autopkgtest [07:37:48]:  summary
run-example  FAIL non-zero exit status 1

Bug#973036: python-msrestazure's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-msrestazure
Version: 0.6.2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

self = , mode = 'rb'
bufsize = -1

def makefile(self, mode='r', bufsize=-1):
"""Returns this fake socket's own tempfile buffer.

If there is an entry associated with the socket, the file
descriptor gets filled in with the entry data before being
returned.
"""
self._mode = mode
self._bufsize = bufsize

if self._entry:
t = threading.Thread(
target=self._entry.fill_filekind, args=(self.fd,)
)
t.start()
if self.timeout == socket._GLOBAL_DEFAULT_TIMEOUT:
timeout = None
else:
timeout = self.timeout
t.join(timeout)
>   if t.isAlive():
E   AttributeError: 'Thread' object has no attribute 'isAlive'

/usr/lib/python3/dist-packages/httpretty/core.py:438: AttributeError

Bug#973035: python-msrest's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:python-msrest
Version: 0.6.18-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9


self = , mode = 'rb'
bufsize = -1

def makefile(self, mode='r', bufsize=-1):
"""Returns this fake socket's own tempfile buffer.

If there is an entry associated with the socket, the file
descriptor gets filled in with the entry data before being
returned.
"""
self._mode = mode
self._bufsize = bufsize

if self._entry:
t = threading.Thread(
target=self._entry.fill_filekind, args=(self.fd,)
)
t.start()
if self.timeout == socket._GLOBAL_DEFAULT_TIMEOUT:
timeout = None
else:
timeout = self.timeout
t.join(timeout)
>   if t.isAlive():
E   AttributeError: 'Thread' object has no attribute 'isAlive'

/usr/lib/python3/dist-packages/httpretty/core.py:438: AttributeError

Bug#973037: sphinxcontrib-bibtex's autopkg tests are failing with python3.9

[Matthias Klose]

Package: src:sphinxcontrib-bibtex
Version: 1.0.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9


==
ERROR: test_issue4.test_encoding
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line 171, in
decorator
return func(*(args + (app, status, warning)), **kwargs)
  File
"/tmp/autopkgtest-lxc.__y4ypab/downtmp/autopkgtest_tmp/test/test_issue4.py",
line 22, in test_encoding
app.builder.build_all()
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 260,
in build_all
self.build(None, summary=__('all source files'), method='all')
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 311,
in build
updated_docnames = set(self.read())
  File "/usr/lib/python3.9/contextlib.py", line 124, in __exit__
next(self.gen)
  File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 213, in
pending_warnings
memhandler.flushTo(logger)
  File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 178, in 
flushTo
logger.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1587, in handle
self.callHandlers(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1649, in callHandlers
hdlr.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 944, in handle
rv = self.filter(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 802, in filter
result = f.filter(record)
  File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 421, in 
filter
raise exc
sphinx.errors.SphinxWarning:
/tmp/autopkgtest-lxc.__y4ypab/downtmp/autopkgtest_tmp/test/issue4/index.rst:3:Error
in "bibliography" directive:
invalid option value: (option: "encoding"; value: 'latex+utf')
unknown encoding: "latex+utf".

.. bibliography:: test.bib
   :all:
   :encoding: latex+utf

--
Ran 29 tests in 8.494s

FAILED (errors=1)

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

[Matthias Klose]

Package: src:supysonic
Version: 0.6.0+ds-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

autopkgtest [19:10:55]: test unittests: [---
=== python3.9 ===
/tmp/autopkgtest-lxc.m7pc_az_/downtmp/build.Kqd/src/debian/tests/unittests: 13:
python3.9: not found
autopkgtest [19:10:56]: test unittests: ---]

Processed: seqan3: autopackage tests need updating for new googletest

[Debian Bug Tracking System]

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

> severity 973001 serious
Bug #973001 [src:seqan3] seqan3: autopackage tests need updating for new 
googletest
Severity set to 'serious' from 'normal'
> tag 973001 + ftbfs
Bug #973001 [src:seqan3] seqan3: autopackage tests need updating for new 
googletest
Added tag(s) ftbfs.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was gin...@debian.org).
> usertag 973001 needs-update
There were no usertags set.
Usertags are now: needs-update.
> thanks
Stopping processing here.

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

Processed: Re: Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #972936 [libgcc-s1] libgcc-s1 needs Breaks: libgcc1 (<< 1:10)
Severity set to 'grave' from 'important'

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

Processed: Re: Bug#973019: python-boto's autopkg tests are failing with python3.9

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 972721
Bug #973019 [src:python-boto] python-boto's autopkg tests are failing with 
python3.9
973019 was not blocked by any bugs.
973019 was not blocking any bugs.
Added blocking bug(s) of 973019: 972721

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

Processed: 973027 is forwarded

[Debian Bug Tracking System]

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

> forwarded 973027 https://github.com/rdkit/rdkit/issues/3521
Bug #973027 [src:rdkit] rdkit: FTBFS in unstable with postgresql 13
Set Bug forwarded-to-address to 'https://github.com/rdkit/rdkit/issues/3521'.
> tags 973027 + confirmed upstream patch
Bug #973027 [src:rdkit] rdkit: FTBFS in unstable with postgresql 13
Added tag(s) upstream, patch, and confirmed.
> thanks
Stopping processing here.

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

Bug#973019: python-boto's autopkg tests are failing with python3.9

[Noah Meyerhans]

Control: block -1 by 972721

>   File "/usr/lib/python3/dist-packages/httpretty/core.py", line 438, in 
> makefile
> if t.isAlive():
> AttributeError: 'Thread' object has no attribute 'isAlive'

This looks like #972721

I don't think we need to do anything in python-boto to fix this.

Processed: seqan3: autopackage tests need updating for new googletest

[Debian Bug Tracking System]

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

> severity 973001 serious
Bug #973001 [src:seqan3] seqan3: autopackage tests need updating for new 
googletest
Ignoring request to change severity of Bug 973001 to the same value.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was gin...@debian.org).
> usertag 973001 needs-update
Usertags were: needs-update.
Usertags are now: needs-update.
> thanks
Stopping processing here.

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

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

[Thomas Goirand]

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)

Processed: notfound 933091 in 0.8.1-1, found 933091 in 1.0.0-1

[Debian Bug Tracking System]

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

> notfound 933091 0.8.1-1
Bug #933091 {Done: Pirate Praveen } 
[node-rollup-plugin-typescript] node-rollup-plugin-typescript seems 
incompatible with rollup/typescript
No longer marked as found in versions node-rollup-plugin-typescript/0.8.1-1.
> found 933091 1.0.0-1
Bug #933091 {Done: Pirate Praveen } 
[node-rollup-plugin-typescript] node-rollup-plugin-typescript seems 
incompatible with rollup/typescript
Marked as found in versions node-rollup-plugin-typescript/1.0.0-1; no longer 
marked as fixed in versions node-rollup-plugin-typescript/1.0.0-1 and reopened.
> thanks
Stopping processing here.

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

Processed: found 933091 in 0.8.1-1

[Debian Bug Tracking System]

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

> found 933091 0.8.1-1
Bug #933091 [node-rollup-plugin-typescript] node-rollup-plugin-typescript seems 
incompatible with rollup/typescript
Marked as found in versions node-rollup-plugin-typescript/0.8.1-1.
> thanks
Stopping processing here.

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

Processed: tagging 933091

[Debian Bug Tracking System]

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

> tags 933091 + buster-ignore
Bug #933091 [node-rollup-plugin-typescript] node-rollup-plugin-typescript seems 
incompatible with rollup/typescript
Added tag(s) buster-ignore.
> thanks
Stopping processing here.

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

Processed: fixed 933091 in 1.0.0-1

[Debian Bug Tracking System]

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

> fixed 933091 1.0.0-1
Bug #933091 [node-rollup-plugin-typescript] node-rollup-plugin-typescript seems 
incompatible with rollup/typescript
Marked as fixed in versions node-rollup-plugin-typescript/1.0.0-1.
> thanks
Stopping processing here.

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

Bug#972926: celery: autopkgtest failures

[s3v]

Hi,

I tried to build Celery 5.0.0-2 in a pbuilder chroot:


 # pbuilder build --basetgz /home/pbuilder-sid.tgz --use-network yes
--buildplace ./cache --aptcache ./ cache celery_5.0.0-2.dsc


and it succeed.

Kind Regards

Bug#973058: kineticstools: FTBFS: mv: cannot move 'debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools/resources' to 'debian/kineticstools-data/usr/share/kineticstools/resources

[Lucas Nussbaum]

Source: kineticstools
Version: 0.6.1+git20200325.3558942+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_install
> I: pybuild base:217: /usr/bin/python3.9 setup.py install --root 
> /<>/debian/python3-kineticstools 
> running install
> running build
> running build_py
> running egg_info
> writing kineticsTools.egg-info/PKG-INFO
> writing dependency_links to kineticsTools.egg-info/dependency_links.txt
> writing entry points to kineticsTools.egg-info/entry_points.txt
> writing requirements to kineticsTools.egg-info/requires.txt
> writing top-level names to kineticsTools.egg-info/top_level.txt
> reading manifest file 'kineticsTools.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'kineticsTools.egg-info/SOURCES.txt'
> running build_ext
> running install_lib
> creating /<>/debian/python3-kineticstools
> creating /<>/debian/python3-kineticstools/usr
> creating /<>/debian/python3-kineticstools/usr/lib
> creating /<>/debian/python3-kineticstools/usr/lib/python3.9
> creating 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages
> creating 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/summarizeModifications.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/BasicLdaEnricher.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/__init__.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/pipelineTools.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/MultiSiteCommon.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/MultiSiteDetection.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/PositiveControlEnricher.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/sharedArray.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/WorkerProcess.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/loader.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/KineticWorker.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools
> creating 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools/tasks
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/tasks/gather_bigwig.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools/tasks
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/tasks/__init__.py
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools/tasks
> creating 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools/tasks/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/tasks/__pycache__/gather_bigwig.cpython-39.pyc
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTools/tasks/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_kineticstools/build/kineticsTools/tasks/__pycache__/__init__.cpython-39.pyc
>  -> 
> /<>/debian/python3-kineticstools/usr/lib/python3.9/dist-packages/kineticsTool

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

[Lucas Nussbaum]

Source: python-py
Version: 1.9.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):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
>   PYBUILD_TEST_ARGS="{interpreter} -m pytest testing 
> --ignore={dir}/testing/log/test_warning.py" \
>   LC_ALL=C.UTF-8 \
>   dh_auto_test
> I: pybuild base:217: python3.9 -m pytest testing 
> --ignore=/<>/testing/log/test_warning.py
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: tox.ini, testpaths: testing
> collected 855 items
> 
> testing/code/test_assertion.py x..ss.x.  [  
> 2%]
> testing/code/test_code.py .. [  
> 4%]
> testing/code/test_excinfo.py ...ss...xx..x.. [  
> 9%]
> xx   [ 
> 12%]
> testing/code/test_source.py .xF. [ 
> 18%]
>  [ 
> 20%]
> testing/io_/test_capture.py .ss.s... [ 
> 25%]
> ..s...ss...s.[ 
> 30%]
> testing/io_/test_saferepr.py [ 
> 31%]
> testing/io_/test_terminalwriter.py . [ 
> 35%]
> ...  [ 
> 36%]
> testing/io_/test_terminalwriter_linewidth.py s.. [ 
> 37%]
> testing/log/test_log.py .[ 
> 39%]
> testing/path/test_cacheutil.py . [ 
> 41%]
> testing/path/test_local.py . [ 
> 46%]
> ss..s..sx..s [ 
> 54%]
> .sssx... [ 
> 62%]
> testing/path/test_svnauth.py sss [ 
> 67%]
> testing/path/test_svnurl.py  [ 
> 72%]
> ..ssx... [ 
> 76%]
> testing/path/test_svnwc.py . [ 
> 82%]
> .ss..x.  [ 
> 89%]
> testing/process/test_cmdexec.py .[ 
> 90%]
> testing/process/test_forkedfunc.py ..[ 
> 92%]
> testing/process/test_killproc.py .   [ 
> 92%]
> testing/root/test_builtin.py ... [ 
> 94%]
> testing/root/test_error.py   [ 
> 95%]
> testing/root/test_py_imports.py .[ 
> 97%]
> testing/root/test_std.py ... [ 
> 97%]
> testing/root/test_xmlgen.py ...  
> [100%]
> 
> === FAILURES 
> ===
> ___ test_getfslineno 
> ___
> 
> def test_getfslineno():
> from py.code import getfslineno
> 
> def f(x):
> pass
> 
> fspath, lineno = getfslineno(f)
> 
> assert fspath.basename == "test_source.py"
> assert lineno == py.code.getrawcode(f).co_firstlineno-1 # see 
> findsource
> 
> class A(object):
> pass
> 
> fspath, lineno = getfslineno(A)
> 
> _, A_lineno = inspect.findsource(A)
> assert fspath.basename == "test_source.py"
> assert lineno == A_lineno
> 
> assert getfslineno(3) == ("", -1)
> class B:
> pass
> B.__name__ = "B2"
> >   assert getfslineno(B)[1] == -1
> E   assert 455 == -1
> 
> testing/code/test_source.py:459: AssertionError
> === warnings summary 
> ===
> /usr/lib/python3/dist-packages/_pytest/mark/structures.py:331
>   /usr/lib/python3/dist-packages/_pytest/mark/structures.py:331: 

Bug#973056: sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: sphinx-tabs
Version: 1.2.1+ds-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 '/<>'
> python3 -m sphinx -b html -d docs/.build/.doctrees -N docs docs/.build/html
> Running Sphinx v3.2.1
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
> 
> generating indices...  genindexdone
> writing additional pages...  searchdone
> copying static files... ... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
> 
> The HTML pages are in docs/.build/html.
> Copying tabs assets
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> running egg_info
> writing sphinx_tabs.egg-info/PKG-INFO
> writing dependency_links to sphinx_tabs.egg-info/dependency_links.txt
> writing requirements to sphinx_tabs.egg-info/requires.txt
> writing top-level names to sphinx_tabs.egg-info/top_level.txt
> reading manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'docs'
> warning: no previously-included files matching '*' found under directory 
> 'docs'
> warning: no previously-included files found matching 'test'
> warning: no previously-included files found matching 'images'
> warning: no previously-included files matching '*' found under directory 
> 'images'
> warning: no previously-included files found matching '.pre-commit-config.yaml'
> warning: no previously-included files found matching '.readthedocs.yml'
> warning: no previously-included files found matching 'pylint.cfg'
> warning: no previously-included files found matching 'tox.ini'
> warning: no previously-included files found matching 'codecov.yml'
> writing manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> copying sphinx_tabs/tabs.css -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.js -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> creating 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/LICENSE.md -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/menu.min.css -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/segment.min.css -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/tab.min.css -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/tab.min.js -> 
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.py -> 
> /<>/.pybuild/cpython3_3.8_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_sphinx-tabs/build/sphinx_tabs
> running egg_info
> writing sphinx_tabs.egg-info/PKG-INFO
> writing dependency_links to sphinx_tabs.egg-info/dependency_links.txt
> writing requirements to sphinx_tabs.egg-info/requires.txt
> writing top-level names to sphinx_tabs.egg-info/top_level.txt
> reading manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'docs'
> warning: no previously-included files matching '*&

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

[Lucas Nussbaum]

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(), &closure->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: warning: ‘v8::Local 
> Nan::MakeCallback(v8::Local, v8::Local, int, 
> v8::Local*)’ is deprecated [-Wdeprecated-declarations]
>   272 | Nan::MakeCallback(Nan::GetCurrentContext()->Global(), 
> Nan::New(closure->cb), 1, argv);
>   |   
>   ^
> In file included from ../src/node_zipfile.hpp:9,
>  from ../src/node_zipfile.cpp:1:
> ../../../../usr/lib/nodejs/nan/nan.h:1024:46: note: declared here
>  1024 |   NAN_DEPRECATED inline v8::Local MakeCallback(
>   |  ^~~~
> ../src/node_zipfile.cpp:275:93: warning: ‘v8::Local 
> Nan::MakeCallback(v8::Local, v8::Local, int, 
> v8::Local*)’ is deprecated [-Wdeprecated-declarations]
>   275 | Nan::MakeCallback(Nan::GetCurrentContext()->Gl

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

[Lucas Nussbaum]

Source: bumpversion
Version: 1.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 bumpversion
> dpkg-buildpackage: info: source version 1.0.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Michael Fladischer 
> 
>  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/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)
> '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 bumpversion using existing 
> ./bumpversion_1.0.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building bumpversion in bumpversion_1.0.0-1.debian.tar.xz
> dpkg-source: info: building bumpversion in bumpversion_1.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/build/bumpversion
> copying bumpversion/cli.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/__main__.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/version_part.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/vcs.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/functions.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> copying bumpversion/utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/bumpversion
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/cli.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/__main__.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/version_part.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/vcs.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/exceptions.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/functions.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
> copying bumpversion/utils.py -> 
> /<>/.pybuild/cpython3_3.8/build/bumpversion
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:284: cp -r /<>/tests 
> /<>/.pybuild/cpython3_3.9/build
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9/build; 
> python3.9 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: tox.ini
> collected 148 items
> 
> tests/test_cli.py FxxFxx.... [ 
> 36%]
> xxXX...xx[ 
> 75%]
> tests/test_function

Bug#973067: ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :pool_size, :pool_timeout

[Lucas Nussbaum]

Source: ruby-redis-activesupport
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):
> ArgumentError: unknown keywords: :pool_size, :pool_timeout
> /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/active_support/cache/redis_store.rb:282:in `block (2 
> levels) in write_entry'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:65:in `block (2 levels) in 
> with'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:64:in `handle_interrupt'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:64:in `block in with'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:61:in `handle_interrupt'
> /usr/lib/ruby/vendor_ruby/connection_pool.rb:61:in `with'
> /<>/lib/active_support/cache/redis_store.rb:268:in `with'
> /<>/lib/active_support/cache/redis_store.rb:282:in `block in 
> write_entry'
> /<>/lib/active_support/cache/redis_store.rb:340:in `failsafe'
> /<>/lib/active_support/cache/redis_store.rb:280:in 
> `write_entry'
> /<>/lib/active_support/cache/redis_store.rb:86:in `block in 
> write'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/cache.rb:686:in
>  `block in instrument'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/notifications.rb:182:in
>  `instrument'
> 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/cache.rb:686:in
>  `instrument'
> /<>/lib/active_support/cache/redis_store.rb:81:in `write'
> /<>/test/active_support/cache/redis_store_test.rb:22:in 
> `block in setup'
> /<>/test/active_support/cache/redis_store_test.rb:762:in 
> `with_store_management'
> /<>/test/active_support/cache/redis_store_test.rb:21:in 
> `setup'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:96: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'
> 
> 81 runs, 288 assertions, 0 failures, 69 errors, 0 skips
> pkill redis-server
> rake aborted!
> Tests failed
> /<>/debian/ruby-tests.rake:13: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-activesupport_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#973059: logging-tree: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: logging-tree
Version: 1.8.1-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):
>  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
>   pybuild --configure -i python{version} -p "3.9 3.8"
> 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
>   pybuild --build -i python{version} -p "3.9 3.8"
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> copying logging_tree/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> copying logging_tree/nodes.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> copying logging_tree/format.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree
> creating 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/case.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_format.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_node.py -> 
> /<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> copying logging_tree/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> copying logging_tree/nodes.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> copying logging_tree/format.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree
> creating 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/case.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_format.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
> copying logging_tree/tests/test_node.py -> 
> /<>/.pybuild/cpython3_3.8_logging_tree/build/logging_tree/tests
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test -i python{version} -p "3.9 3.8"
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_logging_tree/build; python3.9 -m 
> unittest discover -v 
> test_2_dot_5_handlers (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_2_dot_6_handlers (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_fancy_tree (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_formatter_that_is_not_a_Formatter_instance 
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_formatter_with_no_fmt_attributes 
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_handler_with_parent_attribute_that_is_none 
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_handler_with_wrong_parent_attribute 
> (logging_tree.tests.test_format.FormatTests) ... ok
> test_most_handlers (logging_tree.tests.test_format.FormatTests) ... ERROR
> test_nested_handlers (logging_tree.tests.test_format.FormatTests) ... ok
> test_printout (logging_tree.tests.test_format.FormatTests) ... ok
> test_simple_tree (logging_tree.tests.test_format.FormatTests) ... ok
> test_default_tree (logging_tree.tests.test_node.NodeTests) ... ok
> test_one_level_tree (logging_tree.tests.test_node.NodeTests) ... ok
> test_two_level_tree (logging_tree.tests.test_node.NodeTests) ... ok
> test_two_level_tree_with_placeholder (logging_tree.tests.test_node.NodeTests) 
> ... ok
> 
> ==
> ERROR: test_2_dot_5_handlers (logging_tree.tests.test_format.FormatTests)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.9_logging_tree/build/logging_tree/tests/test_format.py",
&

Bug#973061: nototools: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

[Lucas Nussbaum]

Source: nototools
Version: 0.2.13-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_clean
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_nototools/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_nototools/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
> rm -rf nototools.egg-info
> make[1]: Leaving directory '/<>'
>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 nototools using existing 
> ./nototools_0.2.13.orig.tar.xz
> dpkg-source: info: local changes detected, the modified files are:
>  nototools-0.2.13/nototools/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/nototools_0.2.13-1.diff.EHwupO
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-10-27T12:29:37Z

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/nototools_0.2.13-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#973068: undercover-el: FTBFS: tests failed

[Lucas Nussbaum]

Source: undercover-el
Version: 0.7.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 undercover-el
> dpkg-buildpackage: info: source version 0.7.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Lev Lamberov 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with elpa
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building undercover-el using existing 
> ./undercover-el_0.7.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building undercover-el in 
> undercover-el_0.7.0-1.debian.tar.xz
> dpkg-source: info: building undercover-el in undercover-el_0.7.0-1.dsc
>  debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>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 test --eval "(load \"undercover.el\")" -l 
> test/first-example-library-test.el --eval \(ert-run-tests-batch-and-exit\)
> Loading /<>/undercover.el (source)...
> Package cl is deprecated
> Running 10 tests (2020-10-27 12:25:27+, selector ‘t’)
> Test test-001/edebug-handlers-are-setted backtrace:
>   signal(ert-test-failed (((should (eq 'undercover--stop-point-before 
>   ert-fail(((should (eq 'undercover--stop-point-before (symbol-functio
>   (if (unwind-protect (setq value-2 (apply fn-0 args-1)) (setq form-de
>   (let (form-description-4) (if (unwind-protect (setq value-2 (apply f
>   (let ((value-2 'ert-form-evaluation-aborted-3)) (let (form-descripti
>   (let* ((fn-0 #'eq) (args-1 (condition-case err (let ((signal-hook-fu
>   (closure (t) nil (let* ((fn-0 #'eq) (args-1 (condition-case err (let
>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>   ert-run-test(#s(ert-test :name test-001/edebug-handlers-are-setted :
>   ert-run-or-rerun-test(#s(ert--stats :selector t :tests [#s(ert-test 
>   ert-run-tests(t #f(compiled-function (event-type &rest event-args) #
>   ert-run-tests-batch(nil)
>   ert-run-tests-batch-and-exit()
>   eval((ert-run-tests-batch-and-exit) t)
>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>   command-line()
>   normal-top-level()
> Test test-001/edebug-handlers-are-setted condition:
> (ert-test-failed
>  ((should
>(eq 'undercover--stop-point-before
>   (symbol-function ...)))
>   :form
>   (eq undercover--stop-point-before nil)
>   :value nil))
>FAILED   1/10  test-001/edebug-handlers-are-setted (0.000124 sec)
>passed   2/10  test-002/result-is-correct (0.001455 sec)
>passed   3/10  test-003/functions-are-covered (0.54 sec)
>passed   4/10  test-004/check-distance-stop-points-number-of-covers 
> (0.000121 sec)
>passed   5/10  test-005/check-coverage-statistics (0.001180 sec)
>passed   6/10  test-006/check-environment-variables (0.68 sec)
>passed   7/10  test-008/should-error (0.000867 sec)
>passed   8/10  test-009/check-simplecov-report (0.003059 sec)
>passed   9/10  test-010/check-text-report (0.001166 sec)
>passed  10/10  test-011/check-text-report-file (0.001415 sec)
> 
> Ran 10 tests, 9 results as expected, 1 unexpected (2020-10-27 12:25:27+, 
> 0.107047 sec)
> 
> 1 unexpected results:
>FAILED  test-001/edebug-handlers-are-setted
> 
> Error: (error "Unsupported report-format")
> 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 test 
> --eval "(load \"undercover.el\")" -l test/first-example-library-test.el 
> --eval \(ert-run-tests-batch-and-exit\) returned exit code 1
> make: *** [debian/rules:4: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/undercover-el_0.7.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#972916: sagemath ftbfs with python3.9

[Graham Inggs]

Control: reopen -1

Hi

The new upload of sagemath/9.2-1 still FTBFS [1] with Python 3.9 as
default.  I've copied what I hope is the relevant part of the log
below.

Regards
Graham


[1] 
https://people.debian.org/~ginggs/python3.9-default/sagemath_9.2-1+build1_amd64-2020-10-27T15:56:32Z.build


make[2]: Entering directory '/<>'
mkdir -p debian/tmp
mv sage/local debian/tmp/usr
mv debian/tmp/usr/lib/python3.8 debian/tmp/usr/lib/python3
mv: cannot stat 'debian/tmp/usr/lib/python3.8': No such file or directory
make[2]: *** [debian/rules:83: override_dh_auto_install] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:40: install] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:40: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Bug#973074: python-apptools: 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-apptools
Version: 4.5.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):
> make[1]: Entering directory '/<>'
> xvfb-run -a dh_auto_test
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_apptools/build; python3.9 -m nose -v 
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user42'
> apptools.io.h5.tests.test_dict_node.test_create ... ok
> apptools.io.h5.tests.test_dict_node.test_is_dict_node ... ok
> apptools.io.h5.tests.test_dict_node.test_is_not_dict_node ... ok
> apptools.io.h5.tests.test_dict_node.test_create_with_data ... ok
> apptools.io.h5.tests.test_dict_node.test_create_with_array_data ... ok
> apptools.io.h5.tests.test_dict_node.test_load_saved_dict_node ... ok
> apptools.io.h5.tests.test_dict_node.test_load_saved_dict_node_with_array ... 
> ok
> apptools.io.h5.tests.test_dict_node.test_keys ... ok
> apptools.io.h5.tests.test_dict_node.test_delete_item ... ok
> apptools.io.h5.tests.test_dict_node.test_delete_array ... ok
> apptools.io.h5.tests.test_dict_node.test_auto_flush ... ok
> apptools.io.h5.tests.test_dict_node.test_auto_flush_off ... ok
> apptools.io.h5.tests.test_dict_node.test_undefined_key ... ok
> apptools.io.h5.tests.test_dict_node.test_basic_dtypes ... ok
> apptools.io.h5.tests.test_dict_node.test_mixed_type_list ... ok
> apptools.io.h5.tests.test_dict_node.test_dict ... ok
> apptools.io.h5.tests.test_dict_node.test_wrap_self_raises_error ... ok
> apptools.io.h5.tests.test_file.test_reopen ... ok
> apptools.io.h5.tests.test_file.test_open_from_pytables_object ... ok
> apptools.io.h5.tests.test_file.test_open_from_closed_pytables_object ... ok
> apptools.io.h5.tests.test_file.test_create_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_getitem_failure ... ok
> apptools.io.h5.tests.test_file.test_iteritems ... ok
> apptools.io.h5.tests.test_file.test_create_plain_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_plain_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_create_chunked_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_chunked_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_create_extendable_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_extendable_array_with_H5Group ... 
> ok
> apptools.io.h5.tests.test_file.test_str_and_repr ... ok
> apptools.io.h5.tests.test_file.test_shape_and_dtype ... ok
> apptools.io.h5.tests.test_file.test_shape_only_raises ... ok
> apptools.io.h5.tests.test_file.test_create_duplicate_array_raises ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_dict_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_dict_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_table_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_table_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_group_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_group_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_remove_group_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_remove_group_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_remove_group_with_remove_node ... ok
> apptools.io.h5.tests.test_file.test_remove_node_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_remove_node_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_read_mode_raises_on_nonexistent_file ... 
> ok
> apptools.io.h5.tests.test_file.test_cleanup ... ok
> apptools.io.h5.tests.test_file.test_create_group_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_group_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_split_path ... ok
> apptools.io.h5.tests.test_file.test_join_path ... ok
> apptools.io.h5.tests.test_file.test_auto_groups ... ok
> apptools.io.h5.tests.test_file.test_auto_groups_deep ... ok
> apptools.io.h5.tests.test_file.test_groups ... ok
> apptools.io.h5.tests.test_file.test_group_attributes ... ok
> apptools.io.h5.tests.test_file.test_group_properties ... ok
> apptools.io.h5.tests.test_file.test_iter_groups ... ok
> apptools.io.h5.tests.test_file.test_mapping_interface_for_file ... ok
> apptools.io.h5.tests.test_file.test_mapping_interface_for_group ... ok
> apptools.io.h5.tests.test_file.test_group_str_and_repr ... ok
> appt

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

[Lucas Nussbaum]

Source: commonmark-bkrs
Version: 0.5.4+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[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} 
> CommonMark/test/test-CommonMark.py" dh_auto_test
> I: pybuild base:217: python3.9 CommonMark/test/test-CommonMark.py
> Traceback (most recent call last):
>   File "/<>/CommonMark/test/test-CommonMark.py", line 5, in 
> 
> from CommonMark_bkrs import CommonMark
>   File 
> "/<>/.pybuild/cpython3_3.9/build/CommonMark_bkrs/__init__.py", 
> line 3, in 
> from CommonMark_bkrs.CommonMark import HTMLRenderer
>   File 
> "/<>/.pybuild/cpython3_3.9/build/CommonMark_bkrs/CommonMark.py", 
> line 18, in 
> HTMLunescape = html.parser.HTMLParser().unescape
> AttributeError: 'HTMLParser' object has no attribute 'unescape'
> E: pybuild pybuild:352: test: plugin custom failed with: exit code=1: 
> python3.9 CommonMark/test/test-CommonMark.py
> dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned 
> exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/commonmark-bkrs_0.5.4+ds-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.

Bug#973064: ruby-rails-controller-testing: FTBFS: ERROR: Test "ruby2.7" failed.

[Lucas Nussbaum]

Source: ruby-rails-controller-testing
Version: 1.0.5-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/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-rails-controller-testing/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"rails-controller-testing\"
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-rails-controller-testing/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.7 -w -I"test"  
> "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb"
>  "test/controllers/assigns_test.rb" 
> "test/controllers/template_assertions_test.rb" 
> "test/helpers/template_assertions_test.rb" 
> "test/integration/template_assertions_test.rb" "test/test_helper.rb" -v
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:313:in
>  `block in verify_gemfile_dependencies_are_found!': Could not find gem 
> 'sqlite3' in any of the gem sources listed in your Gemfile. 
> (Bundler::GemNotFound)
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in
>  `each'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in
>  `verify_gemfile_dependencies_are_found!'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:49:in
>  `start'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:22:in
>  `resolve'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:264:in
>  `resolve'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:175:in
>  `specs'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:243:in
>  `specs_for'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:231:in
>  `requested_specs'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:91:in
>  `block in definition_method'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:20:in
>  `setup'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in
>  `setup'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in
>  `block in '
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:136:in
>  `with_level'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:88:in
>  `silence'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in
>  `'
>   from 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in `require'
>   from 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in `require'
>   from /<>/test/dummy/config/boot.rb:4:in `'
>   from 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in `require'
>   from 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in `require'
>   from /<>/test/dummy/config/application.rb:1:in ` (required)&g

Bug#973066: esup-el: FTBFS: tests failed

[Lucas Nussbaum]

Source: esup-el
Version: 0.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[1]: Entering directory '/<>'
> skipping upstream build
> 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 test -l test/esup-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Redundant pcase pattern: _
> Running 24 tests (2020-10-27 12:17:52+, selector ‘t’)
> Test esup-child-run__advises_load backtrace:
>   (time-since t1)
>   (float-time (time-since t1))
>   (let (t1) (setq t1 (current-time)) (eval sexp) (float-time (time-sin
>   (list (let (t1) (setq t1 (current-time)) (eval sexp) (float-time (ti
>   (let ((gc gc-elapsed) (gcs gcs-done)) (list (let (t1) (setq t1 (curr
>   (setq benchmark (let ((gc gc-elapsed) (gcs gcs-done)) (list (let (t1
>   (let ((sexp (if (string-equal sexp-string "") "" (car-safe (read-fro
>   esup-child-profile-string("(defun my-load (file) (load file))" "/fak
>   (setq esup--profile-results (esup-child-profile-string sexp-string f
>   (cond ((string-equal sexp-string "") 'nil) (t (setq esup--profile-re
>   (progn (setq sexp (if (string-equal sexp-string "") "" (car-safe (re
>   (condition-case error-message (progn (setq sexp (if (string-equal se
>   (let* ((sexp-string (esup-child-chomp (buffer-substring start end)))
>   esup-child-profile-sexp(1 35)
>   (append results (esup-child-profile-sexp start end))
>   (setq results (append results (esup-child-profile-sexp start end)))
>   (while (> start last-start) (setq results (append results (esup-chil
>   (let ((buffer-read-only t) (last-start -1) (end (progn (forward-sexp
>   (save-current-buffer (set-buffer buffer) (goto-char (point-min)) (fo
>   (condition-case error-message (save-current-buffer (set-buffer buffe
>   esup-child-profile-buffer(#)
>   (progn (esup-child-send-log "loading %s" abs-file-path) (esup-child-
>   (if abs-file-path (progn (esup-child-send-log "loading %s" abs-file-
>   (let* ((clean-file (esup-child-chomp file-name)) (abs-file-path (loc
>   esup-child-profile-file("qux.el")
>   (prog1 (esup-child-profile-file init-file) (advice-remove 'require '
>   esup-child-run("qux.el" -1)
>   (list '(:gc-time :exec-time) (esup-child-run "qux.el" esup-test/fake
>   (let ((signal-hook-function #'ert--should-signal-hook)) (list '(:gc-
>   (condition-case err (let ((signal-hook-function #'ert--should-signal
>   (let* ((fn-55 #'esup-results-equal-p) (args-56 (condition-case err (
>   (progn (progn (fset 'find-file-noselect (cl-function (lambda (filena
>   (unwind-protect (progn (progn (fset 'find-file-noselect (cl-function
>   (let ((saved-func-find-file-noselect (condition-case err (symbol-fun
>   (noflet ((find-file-noselect (filename &optional nowarn rawfile wild
>   (let* ((load-path (plist-get '(:load-path ("/fake14") :files (("/fak
>   (with-esup-mock '(:load-path ("/fake14") :files (("/fake14/qux.el" .
>   (closure (t) nil (with-esup-mock '(:load-path ("/fake14") :files (("
>   ert--run-test-internal(#s(ert--test-execution-info :test ... :result
>   ert-run-test(#s(ert-test :name esup-child-run__advises_load :documen
>   ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
>   ert-run-tests(t #f(compiled-function (event-type &rest event-args) #
>   ert-run-tests-batch(nil)
>   ert-run-tests-batch-and-exit()
>   eval((ert-run-tests-batch-and-exit) t)
>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>   command-line()
>   normal-top-level()
> Test esup-child-run__advises_load condition:
> (file-missing "Cannot open load file" "No such file or directory" 
> "time-date")
>FAILED   1/24  esup-child-run__advises_load (0.000547 sec)
> Test esup-child-run__advises_require backtrace:
>   (time-since t1)
>   (float-time (time-since t1))
>   (let (t1) (setq t1 (current-time)) (eval sexp) (float-time (time-sin
>   (list (let (t1) (setq t1 (current-time)) (eval sexp) (float-time (ti
>   (let ((gc gc-elapsed) (gcs gcs-done)) (list (let (t1) (setq t1 (curr
>   (setq benchmark (le

Bug#973078: lomiri-download-manager: FTBFS: make[3]: *** No rule to make target 'tests/gmock/libgmock.a', needed by 'tests/downloads/client/test_download_manager_watch_client'. Stop.

[Lucas Nussbaum]

Source: lomiri-download-manager
Version: 0.1.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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 67%] Building CXX object 
> tests/downloads/client/CMakeFiles/test_download_manager_watch_client.dir/test_download_manager_watch_client_autogen/mocs_compilation.cpp.o
> cd /<>/obj-x86_64-linux-gnu/tests/downloads/client && 
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
> -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
> -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_LOG_DYN_LINK 
> -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_REGEX_DYN_LINK 
> -DBOOST_THREAD_DYN_LINK -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=8 
> -DGTEST_VERSION_PATCH=0 -DGTEST_VERSION_UNKNOWN 
> -DI18N_DOMAIN=\"lomiri-download-manager\" -DNDEBUG -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB 
> -DQT_TESTCASE_BUILDDIR=\"/<>/obj-x86_64-linux-gnu\" 
> -DQT_TESTLIB_LIB 
> -I/<>/obj-x86_64-linux-gnu/tests/downloads/client/test_download_manager_watch_client_autogen/include
>  -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/src/googletest/googletest/include 
> -I/usr/src/googletest/googlemock/include 
> -I/<>/tests/downloads/client 
> -I/<>/obj-x86_64-linux-gnu/tests/downloads/client 
> -I/<>/src/common/public -I/<>/src/common/priv 
> -I/<>/src/downloads/common 
> -I/<>/src/downloads/client -I/<>/src/downloads/priv 
> -I/<>/tests/common -isystem /usr/include/x86_64-linux-gnu/qt5 
> -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/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtTest -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fPIC 
> -pthread -pipe -std=c++11 -Werror -O2 -Wall -W -D_REENTRANT -fPIC -pedantic 
> -Wextra -fPIC -o 
> CMakeFiles/test_download_manager_watch_client.dir/test_download_manager_watch_client_autogen/mocs_compilation.cpp.o
>  -c 
> /<>/obj-x86_64-linux-gnu/tests/downloads/client/test_download_manager_watch_client_autogen/mocs_compilation.cpp
> make[3]: *** No rule to make target 'tests/gmock/libgmock.a', needed by 
> 'tests/downloads/client/test_client_manager_client'.  Stop.
> make[3]: *** Waiting for unfinished jobs
> [ 67%] Building CXX object 
> tests/downloads/client/CMakeFiles/test_client_manager_client.dir/test_client_manager.cpp.o
> cd /<>/obj-x86_64-linux-gnu/tests/downloads/client && 
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
> -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
> -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_LOG_DYN_LINK 
> -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_REGEX_DYN_LINK 
> -DBOOST_THREAD_DYN_LINK -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=8 
> -DGTEST_VERSION_PATCH=0 -DGTEST_VERSION_UNKNOWN 
> -DI18N_DOMAIN=\"lomiri-download-manager\" -DNDEBUG -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB 
> -DQT_TESTCASE_BUILDDIR=\"/<>/obj-x86_64-linux-gnu\" 
> -DQT_TESTLIB_LIB 
> -I/<>/obj-x86_64-linux-gnu/tests/downloads/client/test_client_manager_client_autogen/include
>  -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/src/googletest/googletest/include 
> -I/usr/src/googletest/googlemock/include 
> -I/<>/tests/downloads/client 
> -I/<>/obj-x86_64-linux-gnu/tests/downloads/client 
> -I/<>/src/common/public -I/<>/src/common/priv 
> -I/<>/src/downloads/common 
> -I/<>/src/downloads/client -I/<>/src/downloads/priv 
> -I/<>/tests/common -isystem /usr/include/x86_64-linux-gnu/qt5 
> -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/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtTest -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fPIC 
> -pthread -pipe -std=c++11 -Werror -O2 -Wall -W -D_REENTRANT -fPIC -pedantic 
> -Wextra -fPIC -o 
> CMakeFiles/test_client_manag

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

[Lucas Nussbaum]

Source: python-msrestazure
Version: 0.6.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):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-msrestazure
> dpkg-buildpackage: info: source version 0.6.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Nicolas Dandrimont 
> 
>  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_msrestazure/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_msrestazure/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-msrestazure using existing 
> ./python-msrestazure_0.6.2.orig.tar.gz
> dpkg-source: info: building python-msrestazure in 
> python-msrestazure_0.6.2-1.debian.tar.xz
> dpkg-source: info: building python-msrestazure in 
> python-msrestazure_0.6.2-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_msrestazure/build/msrestazure
> copying msrestazure/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/azure_operation.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/azure_cloud.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/version.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/azure_exceptions.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/azure_active_directory.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/tools.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> copying msrestazure/azure_configuration.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure
> creating 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure/polling
> copying msrestazure/polling/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure/polling
> copying msrestazure/polling/async_arm_polling.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure/polling
> copying msrestazure/polling/arm_polling.py -> 
> /<>/.pybuild/cpython3_3.9_msrestazure/build/msrestazure/polling
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/azure_operation.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/azure_cloud.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/version.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/azure_exceptions.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/azure_active_directory.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> copying msrestazure/tools.py -> 
> /<>/.pybuild/cpython3_3.8_msrestazure/build/msrestazure
> cop

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

[Lucas Nussbaum]

Source: pybtex
Version: 0.22.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 '/<>/docs'
> sphinx-build -b html -d build/doctrees   source build/html
> Running Sphinx v3.2.1
> loading translations [en]... done
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 9 source files that are out of date
> updating environment: [new config] 9 added, 0 changed, 0 removed
> reading sources... [ 11%] api/formatting
> reading sources... [ 22%] api/index
> reading sources... [ 33%] api/parsing
> reading sources... [ 44%] api/plugins
> reading sources... [ 55%] api/styles
> reading sources... [ 66%] cmdline
> reading sources... [ 77%] formats
> reading sources... [ 88%] history
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 11%] api/formatting
> writing output... [ 22%] api/index
> writing output... [ 33%] api/parsing
> writing output... [ 44%] api/plugins
> writing output... [ 55%] api/styles
> writing output... [ 66%] cmdline
> writing output... [ 77%] formats
> writing output... [ 88%] history
> writing output... [100%] index
> 
> /<>/docs/source/api/formatting.rst:126: WARNING: unknown option: 
> -l python
> /<>/docs/source/cmdline.rst:61: WARNING: unknown option: --format
> /<>/docs/source/cmdline.rst:87: WARNING: unknown option: 
> --style-language
> /<>/docs/source/cmdline.rst:94: WARNING: unknown option: 
> --output-backend
> /<>/docs/source/cmdline.rst:109: WARNING: unknown option: 
> --name-style
> /<>/docs/source/cmdline.rst:109: WARNING: unknown option: 
> --abbreviate-names
> /<>/docs/source/cmdline.rst:149: WARNING: unknown option: --style
> generating indices...  genindexdone
> writing additional pages...  searchdone
> copying static files... ... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 7 warnings.
> 
> The HTML pages are in build/html.
> 
> build finished. the html pages are in build/html.
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:284: cp -r /<>/*.egg-info 
> /<>/.pybuild/cpython3_3.9_pybtex/build
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_pybtex/build; 
> python3.9 -m nose -v tests
> test_parser (tests.bibtex_parser_test.AtCharacterInUnwantedEntryTest) ... ok
> test_parser (tests.bibtex_parser_test.AtCharacterTest) ... ok
> test_parser (tests.bibtex_parser_test.AtTest) ... ok
> test_parser (tests.bibtex_parser_test.BracesAndQuotesTest) ... ok
> test_parser (tests.bibtex_parser_test.BracesTest) ... ok
> test_parser (tests.bibtex_parser_test.CaseSensitivityTest) ... ok
> test_parser (tests.bibtex_parser_test.CrossFileMacrosTest) ... ok
> test_parser (tests.bibtex_parser_test.CrossrefTest) ... ok
> test_parser (tests.bibtex_parser_test.CrossrefWantedTest) ... ok
> test_parser (tests.bibtex_parser_test.DuplicateFieldTest) ... ok
> test_parser (tests.bibtex_parser_test.EmptyDataTest) ... ok
> test_parser (tests.bibtex_parser_test.EntryInCommentTest) ... ok
> test_parser (tests.bibtex_parser_test.EntryInStringTest) ... ok
> test_parser (tests.bibtex_parser_test.EntryTypesTest) ... ok
> test_parser (tests.bibtex_parser_test.FieldNamesTest) ... ok
> test_parser (tests.bibtex_parser_test.InlineCommentTest) ... ok
> test_parser (tests.bibtex_parser_test.KeyParsingTest) ... ok
> test_parser (tests.bibtex_parser_test.KeylessEntriesTest) ... ok
> test_parser (tests.bibtex_parser_test.MacrosTest) ... ok
> test_parser (tests.bibtex_parser_test.SimpleEntryTest) ... ok
> test_parser (tests.bibtex_parser_test.UnusedEntryTest) ... ok
> test_parser (tests.bibtex_parser_test.WantedEntriesTest) ... ok
> test_parser (tests.bibtex_parser_test.WindowsNewlineTest) ... ok
> tests.bst_parser_test.bst_parser_test.test_bst_parser('plain',) ... ok
> tests.bst_parser_test.bst_parser_test.test_bst_parser('apacite',) ... ok
> tests.bst_parser_test.bst_parser_test.test_bst_parser('jurabib',) ... ok
> tests.database_test.database_test.test_database_parsing_and_writing(PybtexStreamIO('bibtex'),)
>  ... ERROR
> tests.database_test.database_test.test_database_parsing_and_writing(PybtexStreamIO(&#

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: Unable to delete file: target

[Lucas Nussbaum]

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, 2]
>  Arguments: [2, 3]
>  Arguments: [3, 0]
>  Arguments: [3, 1]
>  Arguments: [3, 2]
>  Arguments: [3, 3]
> Running testNPE
> Running testCharToByteToChar
>  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 testFloatToByteToFloat
>  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#973063: amazon-ecr-credential-helper: FTBFS: dh_auto_test: error

[Lucas Nussbaum]

Source: amazon-ecr-credential-helper
Version: 0.3.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 -- -ldflags "-X 
> "github.com/awslabs/amazon-ecr-credential-helper/ecr-login"/version.Version=0.3.1
>  -X 
> "github.com/awslabs/amazon-ecr-credential-helper/ecr-login"/version.GitCommitSHA=b4a1707"
>   cd obj-x86_64-linux-gnu && go version
> go version go1.15.2 linux/amd64
>   cd obj-x86_64-linux-gnu && go env
> GO111MODULE="off"
> GOARCH="amd64"
> GOBIN=""
> GOCACHE="/<>/obj-x86_64-linux-gnu/go-build"
> GOENV="/sbuild-nonexistent/.config/go/env"
> GOEXE=""
> GOFLAGS=""
> GOHOSTARCH="amd64"
> GOHOSTOS="linux"
> GOINSECURE=""
> GOMODCACHE="/<>/obj-x86_64-linux-gnu/pkg/mod"
> GONOPROXY=""
> GONOSUMDB=""
> GOOS="linux"
> GOPATH="/<>/obj-x86_64-linux-gnu"
> GOPRIVATE=""
> GOPROXY="off"
> GOROOT="/usr/lib/go-1.15"
> GOSUMDB="sum.golang.org"
> GOTMPDIR=""
> GOTOOLDIR="/usr/lib/go-1.15/pkg/tool/linux_amd64"
> GCCGO="gccgo"
> AR="ar"
> CC="gcc"
> CXX="g++"
> CGO_ENABLED="1"
> GOMOD=""
> CGO_CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security"
> CGO_CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2"
> CGO_CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security"
> CGO_FFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong"
> CGO_LDFLAGS="-Wl,-z,relro"
> PKG_CONFIG="pkg-config"
> GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 
> -fdebug-prefix-map=/tmp/go-build325308206=/tmp/go-build 
> -gno-record-gcc-switches"
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 -ldflags "-X 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/version.Version=0.3.1
>  -X 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/version.GitCommitSHA=b4a1707"
>  github.com/awslabs/amazon-ecr-credential-helper/ecr-login 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/api 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/api/mocks 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cache 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cache/mocks 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login
>  github.com/awslabs/amazon-ecr-credential-helper/ecr-login/config 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/mocks 
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/version
> internal/unsafeheader
> runtime/internal/sys
> runtime/internal/atomic
> internal/cpu
> math/bits
> runtime/internal/math
> unicode/utf8
> internal/race
> sync/atomic
> unicode
> internal/bytealg
> math
> internal/testlog
> encoding
> unicode/utf16
> runtime
> container/list
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> runtime/cgo
> github.com/aws/aws-sdk-go/aws/client/metadata
> golang.org/x/sys/internal/unsafeheader
> github.com/aws/aws-sdk-go/internal/sdkmath
> github.com/awslabs/amazon-ecr-credential-helper/ecr-login/version
> internal/reflectlite
> sync
> github.com/aws/aws-sdk-go/internal/sync/singleflight
> math/rand
> internal/singleflight
> errors
> sort
> strconv
> io
> internal/oserror
> vendor/golang.org/x/net/dns/dnsmessage
> syscall
> strings
> reflect
> bytes
> regexp/syntax
> github.com/aws/aws-sdk-go/internal/sdkio
> bufio
> internal/syscall/unix
> time
> internal/syscall/execenv
> regexp
> hash
> hash/crc32
> crypto
> crypto/internal/randutil
> crypto/hmac
> internal/poll
> context
> internal/fmtsort
> encoding/binary
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> path
> os
> encoding/base64
> crypto/cipher
> crypto/sha512
> crypto/ed25519/internal/edwards25519
> crypto/aes
> crypto/des
> fmt
> path/filepath
> crypto/md5
> crypto/sha1
> io/ioutil
> github.com/aws/aws-sdk-go/internal/sh

Processed: sagemath ftbfs with python3.9

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #972916 {Done: Tobias Hansen } [src:sagemath] sagemath 
ftbfs with python3.9
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sagemath/9.2-1.

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

Bug#973069: mgba: FTBFS: CheckFunctionExists.c:17: undefined reference to `snprintf_l'

[Lucas Nussbaum]

Source: mgba
Version: 0.8.3+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):
> /usr/bin/ld: CMakeFiles/cmTC_33e3c.dir/CheckFunctionExists.c.o: in function 
> `main':
> /usr/share/cmake-3.18/Modules/CheckFunctionExists.c:17: undefined reference 
> to `snprintf_l'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/mgba_0.8.3+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#973073: tycho: FTBFS: constructor EquinoxContainer in class org.eclipse.osgi.internal.framework.EquinoxContainer cannot be applied to given types

[Lucas Nussbaum]

Source: tycho
Version: 1.6.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):
> make[1]: Entering directory '/<>'
> dh_auto_build -- package -Dmaven.test.skip=true
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -Dmaven.test.skip=true -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [WARNING] The project org.eclipse.tycho:tycho:pom:1.6.0 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Tycho  
> [pom]
> [INFO] Tycho OSGi Bundles Parent  
> [pom]
> [INFO] Tycho Embedder API Maven/OSGi Shared Classes   
> [jar]
> [INFO] Tycho Core Maven/OSGi Shared Classes   
> [jar]
> [INFO] Tycho p2 Resolver Maven/OSGi Shared Classes
> [jar]
> [INFO] Tycho p2 Tools Maven/OSGi Shared Classes   
> [jar]
> [INFO] Tycho Maven/p2 Repository Integration  
> [jar]
> [INFO] Tycho p2 Resolver Bundle   
> [jar]
> [INFO] Tycho p2 Tools Bundle  
> [jar]
> [INFO] Tycho OSGi Runtime External Bundles
> [jar]
> [INFO] Sisu Equinox/Plexus bridge 
> [pom]
> [INFO] Sisu Equinox Services API  
> [jar]
> [INFO] Sisu Equinox Embedder  
> [jar]
> [INFO] Tycho Eclipse Project Metadata Model   
> [jar]
> [INFO] Tycho Embedder API 
> [jar]
> [INFO] Tycho Core 
> [jar]
> [INFO] Sisu Equinox Launching 
> [jar]
> [INFO] Tycho JVM Library Detector 
> [jar]
> [INFO] Tycho JDT Compiler Component   
> [jar]
> [INFO] Tycho OSGi Compiler Plugin
> [maven-plugin]
> [INFO] Tycho OSGi Packaging Plugin   
> [maven-plugin]
> [INFO] Tycho Target Platform Configuration Plugin
> [maven-plugin]
> [INFO] Tycho p2 Tools Parent  
> [pom]
> [INFO] Tycho p2 Resolver Component
> [jar]
> [INFO] Tycho Maven Build Extension   
> [maven-plugin]
> [INFO] Tycho Artifactor Comparator Plugin 
> [jar]
> [INFO] Tycho p2 Metadata Plugin  
> [maven-plugin]
> [INFO] Tycho p2 Publisher Plugin 
> [maven-plugin]
> [INFO] Tycho p2 Repository Plugin
> [maven-plugin]
> [INFO] 
> [INFO] --< org.eclipse.tycho:tycho 
> >---
> [INFO] Building Tycho 1.6.0  
> [1/29]
> [INFO] [ pom 
> ]-
> [INFO] 
> [I

Bug#973080: cool-retro-term: FTBFS: Error setting permissions on /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/DarkPicture.schema: No such file or d

[Lucas Nussbaum]

Source: cool-retro-term
Version: 1.1.1+git20200723-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 '/<>/qmltermwidget'
> /usr/lib/qt5/bin/qmake -install qinstall -exe 
> QMLTermWidget/libqmltermwidget.so 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/libqmltermwidget.so
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/src/qmldir 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/qmldir
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/src/QMLTermScrollbar.qml 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/QMLTermScrollbar.qml
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes/BlackOnLightYellow.schema 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/BlackOnLightYellow.schema
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/kb-layouts 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes/BlackOnRandomLight.colorscheme
>  
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/BlackOnRandomLight.colorscheme
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes/historic/BlackOnLightColor.schema
>  
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/BlackOnLightColor.schema
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes/BlackOnWhite.schema 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/BlackOnWhite.schema
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes/historic/DarkPicture.schema 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/DarkPicture.schema
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/qmltermwidget/lib/color-schemes/BreezeModified.colorscheme 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/BreezeModified.colorscheme
> Error setting permissions on 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/DarkPicture.schema:
>  No such file or directory
> make[2]: *** [Makefile:937: install_colorschemes2] Error 3

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/cool-retro-term_1.1.1+git20200723-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#973076: natsort: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: natsort
Version: 7.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):
>  debian/rules build
> dh build --with python3,sphinxdoc --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_natsort/build/natsort
> copying natsort/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> copying natsort/__main__.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> copying natsort/ns_enum.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> copying natsort/unicode_numbers.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> copying natsort/unicode_numeric_hex.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> copying natsort/natsort.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> copying natsort/utils.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort
> creating /<>/.pybuild/cpython3_3.9_natsort/build/natsort/compat
> copying natsort/compat/fake_fastnumbers.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort/compat
> copying natsort/compat/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort/compat
> copying natsort/compat/locale.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort/compat
> copying natsort/compat/fastnumbers.py -> 
> /<>/.pybuild/cpython3_3.9_natsort/build/natsort/compat
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/__main__.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/ns_enum.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/unicode_numbers.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/unicode_numeric_hex.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/natsort.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> copying natsort/utils.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort
> creating /<>/.pybuild/cpython3_3.8_natsort/build/natsort/compat
> copying natsort/compat/fake_fastnumbers.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort/compat
> copying natsort/compat/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort/compat
> copying natsort/compat/locale.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort/compat
> copying natsort/compat/fastnumbers.py -> 
> /<>/.pybuild/cpython3_3.8_natsort/build/natsort/compat
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_natsort/build; 
> python3.9 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> plugins: hypothesis-5.32.1, mock-1.10.4
> collected 274 items
> 
> tests/test_fake_fastnumbers.py ...   [  
> 5%]
> tests/test_final_data_transform_factory.py   [  
> 8%]
> tests/test_input_string_transform_factory.py .   [ 
> 14%]
> tests/test_main.py ..[ 
> 22%]
> tests/test_natsort_key.py .  [ 
> 24%]
> tests/test_natsort_keygen.py .   [ 
> 32%]
> tests/test_natsorted.py ...  [ 
> 49%]
> tests/test_natsorted_convenience.py  [ 
> 53%]
> tests/test_ns_enum.py .  [ 
> 54%]
> tests/test_parse_bytes_function.py   [ 
> 55%]
> tests/test_parse_number_function.py ...  [ 
> 58%]
> tests/test_parse_string_function

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

[Lucas Nussbaum]

Source: pyrandom2
Version: 1.0.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):
>  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 src/random2.py -> /<>/.pybuild/cpython3_3.9_random2/build
> running egg_info
> creating src/random2.egg-info
> writing src/random2.egg-info/PKG-INFO
> writing dependency_links to src/random2.egg-info/dependency_links.txt
> writing top-level names to src/random2.egg-info/top_level.txt
> writing manifest file 'src/random2.egg-info/SOURCES.txt'
> reading manifest file 'src/random2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.rst'
> warning: no files found matching 'buildout.cfg'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> writing manifest file 'src/random2.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying src/random2.py -> /<>/.pybuild/cpython3_3.8_random2/build
> running egg_info
> writing src/random2.egg-info/PKG-INFO
> writing dependency_links to src/random2.egg-info/dependency_links.txt
> writing top-level names to src/random2.egg-info/top_level.txt
> reading manifest file 'src/random2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.rst'
> warning: no files found matching 'buildout.cfg'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> writing manifest file 'src/random2.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> 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
> writing src/random2.egg-info/PKG-INFO
> writing dependency_links to src/random2.egg-info/dependency_links.txt
> writing top-level names to src/random2.egg-info/top_level.txt
> reading manifest file 'src/random2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.rst'
> warning: no files found matching 'buildout.cfg'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> writing manifest file 'src/random2.egg-info/SOURCES.txt'
> running build_ext
> test_autoseed (tests.WichmannHill_TestBasicOps) ... ok
> test_bigrand (tests.WichmannHill_TestBasicOps) ... ok
> test_gauss (tests.WichmannHill_TestBasicOps) ... ok
> test_gauss_with_whseed (tests.WichmannHill_TestBasicOps) ... ok
> test_jumpahead (tests.WichmannHill_TestBasicOps) ... ok
> test_pickling (tests.WichmannHill_TestBasicOps) ... ok
> test_sample (tests.WichmannHill_TestBasicOps) ... ok
> test_sample_distribution (tests.WichmannHill_TestBasicOps) ... ok
> test_sample_inputs (tests.WichmannHill_TestBasicOps) ... ok
> test_sample_on_dicts (tests.WichmannHill_TestBasicOps) ... ok
> test_saverestore (tests.WichmannHill_TestBasicOps) ... ok
> test_seedargs (tests.WichmannHill_TestBasicOps) ... ok
> test_setstate_first_arg (tests.WichmannHill_TestBasicOps) ... ok
> test_strong_jumpahead (tests.WichmannHill_TestBasicOps) ... ok
> test_53_bits_per_float (tests.MersenneTwister_TestBasicOps) ... ok
> test_autoseed (tests.MersenneTwister_TestBasicOps) ... ok
> test_bigrand (tests.MersenneTwister_TestBasicOps) ... ok
> test_bigrand_ranges (tests.MersenneTwister_TestBasicOps) ... ok
> test_gauss (tests.MersenneTwister_TestBasicOps) ... ok
> test_genrandbits (tests.MersenneTwister_TestBasicOps) ... FAIL
> test_jumpahead (tests.MersenneTwister_TestBasicOps) ... ok
> test_long_seed (tests.MersenneTwister_TestBasicOps) ... ok
> test_pickling (tests.MersenneTwister_TestBasicOps) ... ok
> test_randbelow_logic (tests.MersenneTwister_TestBasicOps) ... ok
> test_randrange_bug_159089

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

[Lucas Nussbaum]

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
> at AsyncSeriesHook.eval [as callAsync] (eval at create 
> (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), :4:1)
> at AsyncSeriesHook.lazyCompileHook [as _callAsync] 
> (/usr/share/nodejs/tapable/lib/Hook.js:35:21)
> at Compiler.emitAssets (/usr/share/nodejs/webpack/lib/Compiler.js:490:19)
> at onCompiled (/usr/share/nodejs/webpack/lib/Compiler.js:278:9)
> at /usr/share/nodejs/webpack/lib/Compiler.js:681:15
> at AsyncSeriesHook.eval [as callAsync] (eval at create 
> (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), :4:1)
> at AsyncSeriesHook.lazyCompileHook [as _callAsync] 
> (/usr/share/nodejs/tapable/lib/Hook.js:35:21)
> at /usr/share/nodejs/webpack/lib/Compiler.js:678:31
> at AsyncSeriesHook.eval [as callAsync] (eval at create 
> (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), :4:1)
> [12:18:32] 'generic' errored after 8.13 s
> [12:18:32] 'dist-pre' errored after 8.14 s
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/pdf.js_2.6.347+dfsg-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#973090: python3-antlr3: FTBFS: make[1]: pyversions: No such file or directory

[Lucas Nussbaum]

Source: python3-antlr3
Version: 3.5.2-7
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 -e; set -x ; for i in 3.9 3.8 ; do \
>   PYTHONPATH=/<>/debian/usr/lib/python3/dist-packages 
> PYTHON=python$i python$i setup.py unittest ; \
> done
> + PYTHONPATH=/<>/debian/usr/lib/python3/dist-packages 
> PYTHON=python3.9 python3.9 setup.py unittest
> running unittest
> /<>/setup.py:94: DeprecationWarning: the imp module is 
> deprecated in favour of importlib; see the module's documentation for 
> alternative uses
>   import imp
> testInit (testdfa.TestDFA)
> DFA.__init__() ... ok
> testUnpack (testdfa.TestDFA)
> DFA.unpack() ... ok
> testInitNone (testexceptions.TestEarlyExitException)
> EarlyExitException.__init__() ... ok
> testInitNone (testexceptions.TestFailedPredicateException)
> FailedPredicateException.__init__() ... Segmentation fault
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 139

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/python3-antlr3_3.5.2-7_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#973083: ponyorm: FTBFS: Sorry, but pony 0.7.13 requires Python of one of the following versions: 2.7, 3.3-3.8. You have version 3.9.0+

[Lucas Nussbaum]

Source: ponyorm
Version: 0.7.13-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 ponyorm
> dpkg-buildpackage: info: source version 0.7.13-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jelmer Vernooij 
>  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 
> Sorry, but pony 0.7.13 requires Python of one of the following versions: 2.7, 
> 3.3-3.8. You have version 3.9.0+
> 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:4: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/ponyorm_0.7.13-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#973082: python-biplist: 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-biplist
Version: 1.0.3-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_biplist/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_biplist/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_biplist/build/biplist
> copying biplist/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_biplist/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_biplist/build; 
> python3.9 -m nose -v tests
> testCurrentOffsetOutOfRange (test_fuzz_results.TestFuzzResults) ... ok
> testExcessivelyLongAsciiString (test_fuzz_results.TestFuzzResults) ... ok
> testIntegerWithZeroByteLength (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidArrayObjectCount (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidDictionaryObjectCount (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidMarkerByteUnpack (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidObjectOffset (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidOffsetEnding (test_fuzz_results.TestFuzzResults) ... ok
> testInvalidRealLength (test_fuzz_results.TestFuzzResults) ... ok
> testNaNDateSeconds (test_fuzz_results.TestFuzzResults) ... ok
> testNegativelyLongAsciiString (test_fuzz_results.TestFuzzResults) ... ok
> testRecursiveObjectOffset (test_fuzz_results.TestFuzzResults) ... ok
> testEmptyFile (test_invalid.TestInvalidPlistFile) ... ok
> testInvalid (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidObjectRefOverflow (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidObjectRefSize (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidOffsestTableOffset (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidOffsetOverflow (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidOffsetSize (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidTemplate (test_invalid.TestInvalidPlistFile) ... ok
> testInvalidTopObjectNumber (test_invalid.TestInvalidPlistFile) ... ok
> testTooShort (test_invalid.TestInvalidPlistFile) ... ok
> testBoolOnly (test_valid.TestValidPlistFile) ... ok
> testEmptyUnicodeRoot (test_valid.TestValidPlistFile) ... ok
> testFileRead (test_valid.TestValidPlistFile) ... ok
> Archive is created with class like this: ... ok
> testLargeDates (test_valid.TestValidPlistFile) ... ok
> testLargeIntegers (test_valid.TestValidPlistFile) ... ok
> testSmallDates (test_valid.TestValidPlistFile) ... ok
> testSmallReal (test_valid.TestValidPlistFile) ... ok
> testUidComparisons (test_valid.TestValidPlistFile) ... ok
> testUnicodeRoot (test_valid.TestValidPlistFile) ... ok
> Primarily testint that an empty unicode and bytes are not mixed up ... ok
> testBadKeys (test_write.TestWritePlist) ... ok
> testBoolRoot (test_write.TestWritePlist) ... ok
> testBools (test_write.TestWritePlist) ... ok
> testBoolsAndIntegersMixed (test_write.TestWritePlist) ... ok
> testBytes (test_

Bug#973091: fcitx5: FTBFS: make[3]: *** No rule to make target '/unstable/input-method/input-method-unstable-v1.xml', needed by 'src/lib/fcitx-wayland/input-method/wayland-input-method-unstable-v1-cli

[Lucas Nussbaum]

Source: fcitx5
Version: 0.0~git20200626.2e9821a-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 '/<>/obj-x86_64-linux-gnu'
> [ 49%] Generating en_dict.fscd
> cd "/<>/obj-x86_64-linux-gnu/src/modules/spell/dict" && 
> ./comp-spell-dict --comp-dict /<>/debian/data/en_dict.txt 
> /<>/obj-x86_64-linux-gnu/src/modules/spell/dict/en_dict.fscd
> [ 49%] Linking CXX executable teststringutils
> cd "/<>/obj-x86_64-linux-gnu/test" && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/teststringutils.dir/link.txt --verbose=1
> /usr/bin/c++ -Wall -Wextra -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
> CMakeFiles/teststringutils.dir/teststringutils.cpp.o -o teststringutils  
> -Wl,-rpath,"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-utils" 
> ../src/lib/fcitx-utils/libFcitx5Utils.so.1.0 
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 49%] Built target teststringutils
> [ 50%] Building CXX object 
> src/lib/fcitx/CMakeFiles/Fcitx5Core.dir/instance.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/src/lib/fcitx" && /usr/bin/c++ 
> -DFCITX_GETTEXT_DOMAIN=\"fcitx5\" -DFMT_LOCALE -DFcitx5Core_EXPORTS 
> -I"/<>/obj-x86_64-linux-gnu" 
> -I"/<>/src/lib/fcitx/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx" 
> -I"/<>/src/lib/fcitx-config/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-config" 
> -I"/<>/src/lib/fcitx-utils/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-utils" -isystem 
> /usr/include/uuid -Wall -Wextra -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
> -std=c++17 -o CMakeFiles/Fcitx5Core.dir/instance.cpp.o -c 
> "/<>/src/lib/fcitx/instance.cpp"
> [ 50%] Building CXX object 
> src/lib/fcitx-wayland/core/CMakeFiles/Fcitx5WaylandCore.dir/wl_pointer.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/src/lib/fcitx-wayland/core" && 
> /usr/bin/c++ -DFCITX_GETTEXT_DOMAIN=\"fcitx5\" 
> -I"/<>/obj-x86_64-linux-gnu" 
> -I"/<>/src/lib/fcitx-wayland/core" 
> -I"/<>/src/lib/fcitx-wayland/core/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-wayland/core" 
> -I"/<>/src/lib/fcitx-utils/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-utils" -Wall -Wextra 
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=c++17 -o 
> CMakeFiles/Fcitx5WaylandCore.dir/wl_pointer.cpp.o -c 
> "/<>/src/lib/fcitx-wayland/core/wl_pointer.cpp"
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 50%] Built target spell_en_dict
> [ 50%] Building CXX object 
> src/lib/fcitx-wayland/core/CMakeFiles/Fcitx5WaylandCore.dir/wl_region.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/src/lib/fcitx-wayland/core" && 
> /usr/bin/c++ -DFCITX_GETTEXT_DOMAIN=\"fcitx5\" 
> -I"/<>/obj-x86_64-linux-gnu" 
> -I"/<>/src/lib/fcitx-wayland/core" 
> -I"/<>/src/lib/fcitx-wayland/core/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-wayland/core" 
> -I"/<>/src/lib/fcitx-utils/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fcitx-utils" -Wall -Wextra 
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=c++17 -o 
> CMakeFiles/Fcitx5WaylandCore.dir/wl_region.cpp.o -c 
> "/<>/src/lib/fcitx-wayland/core/wl_region.cpp"
> [ 51%] Building CXX object 
> src/lib/fcitx-wayland/core/CMakeFiles/Fcitx5WaylandCore.dir/wl_registry.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/src/lib/fcitx-wayland/core" && 
> /usr/bin/c++ -DFCITX_GETTEXT_DOMAIN=\"fcitx5\" 
> -I"/<>/obj-x86_64-linux-gnu" 
> -I"/<>/src/lib/fcitx-wayland/core" 
> -I"/<>/src/lib/fcitx-wayland/core/.." 
> -I"/<>/obj-x86_64-linux-gnu/src/lib/fc

Bug#973084: docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package "github.com/cpuguy83/go-md2man/md2man"

[Lucas Nussbaum]

Source: docker.io
Version: 19.03.13+dfsg1-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 
> '/<>/.gopath/src/github.com/docker/cli'
> ./scripts/build/dynbinary
> Building dynamically linked build/docker-linux-amd64
> scripts/docs/generate-man.sh
> vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package 
> "github.com/cpuguy83/go-md2man/md2man" in any of:
>   
> /<>/.gopath/src/github.com/docker/cli/vendor/github.com/cpuguy83/go-md2man/md2man
>  (vendor tree)
>   /usr/lib/go-1.15/src/github.com/cpuguy83/go-md2man/md2man (from $GOROOT)
>   /<>/.gopath/src/github.com/cpuguy83/go-md2man/md2man (from 
> $GOPATH)
> make[2]: *** [Makefile:76: manpages] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/docker.io_19.03.13+dfsg1-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#973098: twms: FTBFS: error: Error: setup script specifies an absolute path:

[Lucas Nussbaum]

Source: twms
Version: 0.07z+git20200829+cb7d39a-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 --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 
> /usr/lib/python3/dist-packages/setuptools/dist.py:466: UserWarning: The 
> version specified ('0.06y') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
> /usr/lib/python3/dist-packages/setuptools/dist.py:466: UserWarning: The 
> version specified ('0.06y') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:466: UserWarning: The 
> version specified ('0.06y') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/daemon.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/fetchers.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/correctify.py -> 
> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/overview.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/__init__.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/bbox.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/gpxparse.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/twms.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/projections.py -> 
> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/drawing.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/canvas.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/capabilities.py -> 
> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/reproject.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/sketch.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/filter.py -> /<>/.pybuild/cpython3_3.9/build/twms
> running egg_info
> creating twms.egg-info
> writing twms.egg-info/PKG-INFO
> writing dependency_links to twms.egg-info/dependency_links.txt
> writing entry points to twms.egg-info/entry_points.txt
> writing requirements to twms.egg-info/requires.txt
> writing top-level names to twms.egg-info/top_level.txt
> writing manifest file 'twms.egg-info/SOURCES.txt'
> reading manifest file 'twms.egg-info/SOURCES.txt'
> writing manifest file 'twms.egg-info/SOURCES.txt'
> error: Error: setup script specifies an absolute path:
> 
> /<>/README.md
> 
> setup() arguments must *always* be /-separated paths relative to the
> setup.py directory, *never* absolute paths.
> 
> E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.9 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p "3.9 3.8" 
> returned exit code 13
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/twms_0.07z+git20200829+cb7d39a-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#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.

[Lucas Nussbaum]

Source: leiningen-clojure
Version: 2.9.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 '/<>'
> cd leiningen-core && lein bootstrap
> Leiningen's classpath: :/usr/share/java/leiningen-2.9.1.jar
> Applying task [with-profile base do install, classpath .lein-bootstrap] to []
> Applying task do to (install, classpath .lein-bootstrap)
> Applying task install to []
> Applying task javac to nil
> Running javac with [@/tmp/.leiningen-cmdline1737550926085786113.tmp]
> Applying task compile to nil
> All namespaces already AOT compiled.
> Created /<>/leiningen-core/target/leiningen-core-2.9.1.jar
> Wrote /<>/leiningen-core/pom.xml
> Installed jar and pom into ../debian/maven-repo.
> Applying task classpath to [.lein-bootstrap]
> chmod a+x bin/lein
> bin/lein uberjar
> Recalculating Leiningen's classpath.
> Leiningen's classpath: 
> /<>/leiningen-core/src/:/<>/leiningen-core/resources/:/<>/test:/<>/target/classes:/<>/src::/<>/resources:/<>/leiningen-core/test:/<>/leiningen-core/src:/<>/leiningen-core/dev-resources:/<>/leiningen-core/resources:/<>/leiningen-core/target/classes:/<>/leiningen-core/../debian/maven-repo/nrepl/nrepl/0.6.0/nrepl-0.6.0.jar:/<>/leiningen-core/../debian/maven-repo/org/clojure/core.specs.alpha/debian/core.specs.alpha-debian.jar:/<>/leiningen-core/../debian/maven-repo/clojure-complete/clojure-complete/0.2.5/clojure-complete-0.2.5.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/resolver/maven-resolver-transport-wagon/debian/maven-resolver-transport-wagon-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/clojure/tools.macro/0.1.5/tools.macro-0.1.5.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/maven-resolver-provider/3.x/maven-resolver-provider-3.x.jar:/<>/leiningen-core/../debian/maven-repo/javax/inject/javax.inject/debian/javax.inject-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/codehaus/plexus/plexus-interpolation/debian/plexus-interpolation-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/commons/commons-lang3/debian/commons-lang3-debian.jar:/<>/leiningen-core/../debian/maven-repo/timofreiberg/bultitude/0.3.0/bultitude-0.3.0.jar:/<>/leiningen-core/../debian/maven-repo/com/hypirion/io/0.3.1/io-0.3.1.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/wagon/wagon-provider-api/debian/wagon-provider-api-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/clojure/spec.alpha/debian/spec.alpha-debian.jar:/<>/leiningen-core/../debian/maven-repo/robert/hooke/1.3.0/hooke-1.3.0.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/resolver/maven-resolver-impl/debian/maven-resolver-impl-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/slf4j/slf4j-api/debian/slf4j-api-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/tcrawley/dynapath/debian/dynapath-debian.jar:/<>/leiningen-core/../debian/maven-repo/com/google/inject/guice/debian/guice-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/jsoup/jsoup/debian/jsoup-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/httpcomponents/httpcore/debian/httpcore-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/slf4j/slf4j-nop/1.7.25/slf4j-nop-1.7.25.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/resolver/maven-resolver-api/debian/maven-resolver-api-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/maven-repository-metadata/3.x/maven-repository-metadata-3.x.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/resolver/maven-resolver-transport-file/debian/maven-resolver-transport-file-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/maven-builder-support/3.x/maven-builder-support-3.x.jar:/<>/leiningen-core/../debian/maven-repo/commons-logging/commons-logging/debian/commons-logging-debian.jar:/<>/leiningen-core/../debian/maven-repo/com/google/guava/guava/debian/guava-debian.jar:/<>/leiningen-core/../debian/maven-repo/commons-io/commons-io/debian/commons-io-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/jsr-305/jsr305/0.x/jsr305-0.x.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/maven/wagon/wagon-http/debian/wagon-http-debian.jar:/<>/leiningen-core/../debian/maven-repo/aopalliance/aopalliance/debian/aopalliance-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/eclipse/sisu/org.eclipse.sisu.inject/debian/org.eclipse.sisu.inject-debian.jar:/<>/leiningen-core/../debian/maven-repo/org/apache/geronimo/specs/geron

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

[Lucas Nussbaum]

Source: python-aiosmtpd
Version: 1.2-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 '/<>'
> mkdir -p /tmp/new
> mkdir -p /tmp/old
> openssl req -x509 -newkey rsa:4096 \
> -keyout '/tmp/new/server.key' \
> -out '/tmp/new/server.crt' \
> -days 365 -nodes -subj '/CN=localhost'
> Generating a RSA private key
> 
> ...
> writing new private key to '/tmp/new/server.key'
> -
> dh_auto_test
>   pybuild --test -i python{version} -p "3.9 3.8"
> I: pybuild pybuild:284: cp -a 
> '/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/tests/certs/server.key'
>  
> '/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/tests/certs/server.crt'
>  '/tmp/old' && cp -f /tmp/new/server.key /tmp/new/server.crt 
> '/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/tests/certs'
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_aiosmtpd/build; python3.9 -m unittest 
> discover -v 
> test_message (aiosmtpd.tests.test_handlers.TestAsyncMessage) ... Exception in 
> callback Controller._stop()
> handle: 
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/asyncio/events.py", line 80, in _run
> self._context.run(self._callback, *self._args)
>   File 
> "/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/controller.py",
>  line 64, in _stop
> for task in asyncio.Task.all_tasks(self.loop):
> AttributeError: type object '_asyncio.Task' has no attribute 'all_tasks'
> ok
> test_message_decoded (aiosmtpd.tests.test_handlers.TestAsyncMessage) ... 
> Exception in callback Controller._stop()
> handle: 
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/asyncio/events.py", line 80, in _run
> self._context.run(self._callback, *self._args)
>   File 
> "/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/controller.py",
>  line 64, in _stop
> for task in asyncio.Task.all_tasks(self.loop):
> AttributeError: type object '_asyncio.Task' has no attribute 'all_tasks'
> ok
> test_debugging_cli_bad_argument (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_debugging_cli_no_args (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_debugging_cli_stderr (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_debugging_cli_stdout (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_debugging_cli_two_args (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_mailbox_cli (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_mailbox_cli_no_args (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_mailbox_cli_too_many_args (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_sink_cli_any_args (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_sink_cli_no_args (aiosmtpd.tests.test_handlers.TestCLI) ... ok
> test_debugging (aiosmtpd.tests.test_handlers.TestDebugging) ... Exception in 
> callback Controller._stop()
> handle: 
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/asyncio/events.py", line 80, in _run
> self._context.run(self._callback, *self._args)
>   File 
> "/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/controller.py",
>  line 64, in _stop
> for task in asyncio.Task.all_tasks(self.loop):
> AttributeError: type object '_asyncio.Task' has no attribute 'all_tasks'
> ok
> test_debugging (aiosmtpd.tests.test_handlers.TestDebuggingBytes) ... 
> Exception in callback Controller._stop()
> handle: 
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/asyncio/events.py", line 80, in _run
> self._context.run(self._callback, *self._args)
>   File 
> "/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/controller.py",
>  line 64, in _stop
> for task in asyncio.Task.all_tasks(self.loop):
> AttributeError: type object '_asyncio.Task' has no attribute 'all_tasks'
> ok
> test_debugging_with_options 
> (aiosmtpd.tests.test_handlers.TestDebuggingOptions) ... Exception in callback 
> Controller._stop()
> handle: 
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/asyncio/events.py", line 80, in _run
> self._context.run(self._callback, *self._args)
>   File 
> "/<>/.pybuild/cpython3_3.9_aiosmtpd/build/aiosmtpd/controller.py",
>  line 64, in _stop
> for task in asyncio.T

Bug#973089: qiskit-ibmq-provider: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: qiskit-ibmq-provider
Version: 0.4.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 qiskit-ibmq-provider
> dpkg-buildpackage: info: source version 0.4.6-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Diego M. Rodriguez 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from 
> qiskit-ibmq-provider-0.4.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_qiskit-ibmq-provider/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_qiskit-ibmq-provider/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 
> qiskit-ibmq-provider-0.4.6/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building qiskit-ibmq-provider using existing 
> ./qiskit-ibmq-provider_0.4.6.orig.tar.gz
> dpkg-source: info: building qiskit-ibmq-provider in 
> qiskit-ibmq-provider_0.4.6-2.debian.tar.xz
> dpkg-source: info: building qiskit-ibmq-provider in 
> qiskit-ibmq-provider_0.4.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_qiskit-ibmq-provider/build/qiskit
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/ibmqbackend.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/ibmqfactory.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/backendjoblimit.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/accountprovider.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/version.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/apiconstants.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/ibmqbackendservice.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq/api
> copying qiskit/providers/ibmq/api/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq/api
> copying qiskit/providers/ibmq/api/session.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq/api
> copying qiskit/providers/ibmq/api/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq/api
> creating 
> /&

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

[Lucas Nussbaum]

Source: celery-haystack
Version: 0.10-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[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. HAYSTACK=v2 python3 
> /usr/bin/django-admin test --settings=celery_haystack.test_settings" 
> dh_auto_test
> I: pybuild base:217: PYTHONPATH=. HAYSTACK=v2 python3 /usr/bin/django-admin 
> test --settings=celery_haystack.test_settings
> Creating test database for alias 'default'...
> EEE
> ==
> ERROR: test_complex (celery_haystack.tests.tests.QueuedSearchIndexTestCase)
> --
> Traceback (most recent call last):
>   File "/<>/celery_haystack/utils.py", line 17, in 
> get_update_task
> mod = import_module(module)
>   File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1014, in _gcd_import
>   File "", line 991, in _find_and_load
>   File "", line 975, in _find_and_load_unlocked
>   File "", line 671, in _load_unlocked
>   File "", line 783, in exec_module
>   File "", line 219, in _call_with_frames_removed
>   File "/<>/celery_haystack/tasks.py", line 11, in 
> from celery.task import Task  # noqa
> ModuleNotFoundError: No module named 'celery.task'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/<>/celery_haystack/tests/tests.py", line 58, in 
> test_complex
> note1 = Note.objects.create(content='Because everyone loves test.')
>   File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, 
> in manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 422, 
> in create
> obj.save(force_insert=True, using=self.db)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, 
> in save
> self.save_base(using=using, force_insert=force_insert,
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 791, 
> in save_base
> post_save.send(
>   File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line 
> 173, in send
> return [
>   File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py", line 
> 174, in 
> (receiver, receiver(signal=self, sender=sender, **named))
>   File "/<>/celery_haystack/signals.py", line 21, in enqueue_save
> return self.enqueue('update', instance, sender, **kwargs)
>   File "/<>/celery_haystack/signals.py", line 44, in enqueue
> enqueue_task(action, instance)
>   File "/<>/celery_haystack/utils.py", line 41, in enqueue_task
> task = get_update_task()
>   File "/<>/celery_haystack/utils.py", line 19, in 
> get_update_task
> raise ImproperlyConfigured('Error importing module %s: "%s"' %
> django.core.exceptions.ImproperlyConfigured: Error importing module 
> celery_haystack.tasks: "No module named 'celery.task'"
> 
> ==
> ERROR: test_delete (celery_haystack.tests.tests.QueuedSearchIndexTestCase)
> --
> Traceback (most recent call last):
>   File "/<>/celery_haystack/utils.py", line 17, in 
> get_update_task
> mod = import_module(module)
>   File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1014, in _gcd_import
>   File "", line 991, in _find_and_load
>   File "", line 975, in _find_and_load_unlocked
>   File "", line 671, in _load_unlocked
>   File "", line 783, in exec_module
>   File "", line 219, in _call_with_frames_removed
>   File "/<>/celery_haystack/tasks.py", line 11, in 
> from celery.task import Task  # noqa
> ModuleNotFoundError: No module named 'celery.task'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback

Bug#973095: ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.

[Lucas Nussbaum]

Source: ros-angles
Version: 1.9.13-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[5]: Entering directory '/<>/build'
> [ 90%] Building CXX object test/CMakeFiles/utest.dir/utest.cpp.o
> cd /<>/build/test && /usr/bin/c++ -DGTEST_VERSION_MAJOR=1 
> -DGTEST_VERSION_MINOR=8 -DGTEST_VERSION_PATCH=0 -DGTEST_VERSION_UNKNOWN 
> -DROS_BUILD_SHARED_LIBS=1 -I/<>/angles/include 
> -I/usr/src/googletest/googlemock/include 
> -I/usr/src/googletest/googletest/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> CMakeFiles/utest.dir/utest.cpp.o -c /<>/angles/test/utest.cpp
> make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 
> 'devel/lib/angles/utest'.  Stop.
> make[5]: Leaving directory '/<>/build'
> make[4]: *** [CMakeFiles/Makefile2:324: test/CMakeFiles/utest.dir/all] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/ros-angles_1.9.13-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#973093: pgaudit: FTBFS: diff in generated debian/control

[Lucas Nussbaum]

Source: pgaudit
Version: 1.4.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):
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2019-11-07 20:19:43.0 +
> +++ debian/control.BQsJsA 2020-10-27 12:30:12.131808295 +
> @@ -13,9 +13,9 @@
>  Vcs-Git: https://salsa.debian.org/postgresql/pgaudit.git
>  Homepage: http://pgaudit.org/
>  
> -Package: postgresql-12-pgaudit
> +Package: postgresql-13-pgaudit
>  Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-12
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
>  Suggests:
>  Description: PostgreSQL Audit Extension
>   The pgAudit extension provides detailed session and/or object audit logging
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9: 
> debian/control] Error 1

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

Bug#973088: mir: FTBFS: egl_extensions.h:105:9: error: ‘PFNEGLBINDWAYLANDDISPLAYWL’ does not name a type

[Lucas Nussbaum]

Source: mir
Version: 1.8.0+dfsg1-10
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 /<>/build-amd64/src/platforms/mesa/server/kms && /usr/bin/c++ 
> -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION 
> -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE 
> -DMIR_LOG_COMPONENT_FALLBACK=\"mesa-kms\" 
> -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API 
> -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT 
> -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" 
> -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=2 -DMIR_VERSION_MINOR=7 
> -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__GBM__ 
> -I/<>/include/core -I/<>/include/common 
> -I/<>/include/cookie -I/<>/include/platforms/mesa 
> -I/<>/src/platforms/mesa/include 
> -I/<>/include/platform -I/<>/include/renderers/gl 
> -I/<>/include/renderers/sw 
> -I/<>/src/platforms/common/server 
> -I/<>/src/include/platform -I/<>/include/client 
> -I/<>/src/platforms/mesa/server/kms/.. -I/usr/include/libdrm -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g 
> -std=c++14 -Wall -fno-strict-aliasing  -Wnon-virtual-dtor -Wextra -fPIC 
> -Wno-mismatched-tags -Wno-psabi -flto -ffat-lto-objects -std=c++14 -o 
> CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/real_kms_output.cpp.o -c 
> /<>/src/platforms/mesa/server/kms/real_kms_output.cpp
> In file included from 
> /<>/src/platforms/eglstream-kms/server/buffer_allocator.h:25,
>  from 
> /<>/src/platforms/eglstream-kms/server/platform.cpp:22:
> /<>/include/platform/mir/graphics/egl_extensions.h:105:9: error: 
> ‘PFNEGLBINDWAYLANDDISPLAYWL’ does not name a type
>   105 | PFNEGLBINDWAYLANDDISPLAYWL const eglBindWaylandDisplayWL;
>   | ^~
> [ 12%] Linking CXX static library libmirplatformwayland-input.a
> cd /<>/build-amd64/src/platforms/wayland && /usr/bin/cmake -P 
> CMakeFiles/mirplatformwayland-input.dir/cmake_clean_target.cmake
> cd /<>/build-amd64/src/platforms/wayland && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/mirplatformwayland-input.dir/link.txt --verbose=1
> gcc-ar qc libmirplatformwayland-input.a 
> CMakeFiles/mirplatformwayland-input.dir/input_platform.cpp.o 
> CMakeFiles/mirplatformwayland-input.dir/input_device.cpp.o
> gcc-ranlib libmirplatformwayland-input.a
> make[4]: Leaving directory '/<>/build-amd64'
> [ 12%] Built target mirplatformwayland-input
> make  -f 
> src/platforms/evdev/CMakeFiles/mirplatforminputevdevobjects.dir/build.make 
> src/platforms/evdev/CMakeFiles/mirplatforminputevdevobjects.dir/depend
> make[4]: Entering directory '/<>/build-amd64'
> cd /<>/build-amd64 && /usr/bin/cmake -E cmake_depends "Unix 
> Makefiles" /<> /<>/src/platforms/evdev 
> /<>/build-amd64 /<>/build-amd64/src/platforms/evdev 
> /<>/build-amd64/src/platforms/evdev/CMakeFiles/mirplatforminputevdevobjects.dir/DependInfo.cmake
>  --color=
> Scanning dependencies of target mirplatforminputevdevobjects
> make[4]: Leaving directory '/<>/build-amd64'
> make  -f 
> src/platforms/evdev/CMakeFiles/mirplatforminputevdevobjects.dir/build.make 
> src/platforms/evdev/CMakeFiles/mirplatforminputevdevobjects.dir/build
> make[4]: Entering directory '/<>/build-amd64'
> [ 12%] Building CXX object 
> src/platforms/evdev/CMakeFiles/mirplatforminputevdevobjects.dir/libinput_device.cpp.o
> cd /<>/build-amd64/src/platforms/evdev && /usr/bin/c++ 
> -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION 
> -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE 
> -DMIR_LIBINPUT_HAS_ACCEL_PROFILE=1 
> -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API 
> -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT 
> -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" 
> -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=2 -DMIR_VERSION_MINOR=7 
> -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/<>/include/core 
> -I/<>/include/common -I/<>/include/cookie 
> -I/<>/include/platform -I/<>/src/include/platform 
> -I/<>/src/include/common -I/<>/include/client -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g 
> -std=c++14 -Wall -fno-strict-aliasing -pedantic -Wnon-virtua

Bug#973087: python-fs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" --test-pytest "--test-args=--ignore tests/test_ftpfs.py" returned exit code 13

[Lucas Nussbaum]

Source: python-fs
Version: 2.4.11-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 '/<>'
> # skip tests that is not runnable with python3-pyftpdlib due to missing
> # test moudles
> dh_auto_test -- --test-pytest --test-args="--ignore tests/test_ftpfs.py"
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9/build; 
> python3.9 -m pytest --ignore tests/test_ftpfs.py
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> collected 1525 items
> 
> tests/test_appfs.py .s   [  
> 0%]
> tests/test_base.py . [  
> 0%]
> tests/test_bulk.py . [  
> 0%]
> tests/test_copy.py ...   [  
> 1%]
> tests/test_encoding.py ...   [  
> 1%]
> tests/test_enums.py .[  
> 1%]
> tests/test_errors.py [  
> 1%]
> tests/test_filesize.py   [  
> 2%]
> tests/test_fscompat.py ...   [  
> 2%]
> tests/test_ftp_parse.py .[  
> 2%]
> tests/test_glob.py ..[  
> 3%]
> tests/test_imports.py .  [  
> 3%]
> tests/test_info.py . [  
> 3%]
> tests/test_iotools.py    [  
> 4%]
> tests/test_lrucache.py . [  
> 4%]
> tests/test_memoryfs.py . [  
> 7%]
> ..   [  
> 9%]
> tests/test_mirror.py [ 
> 12%]
> tests/test_mode.py ..[ 
> 12%]
> tests/test_mountfs.py .. [ 
> 15%]
>  [ 
> 20%]
> .[ 
> 22%]
> tests/test_move.py ..[ 
> 22%]
> tests/test_multifs.py .. [ 
> 26%]
> s[ 
> 28%]
> tests/test_new_name.py . [ 
> 28%]
> tests/test_opener.py .   [ 
> 30%]
> tests/test_osfs.py F [ 
> 34%]
> .s...[ 
> 36%]
> tests/test_path.py . [ 
> 37%]
> tests/test_permissions.py .. [ 
> 38%]
> tests/test_subfs.py F... [ 
> 42%]
> ..s...F. [ 
> 46%]
> s[ 
> 50%]
> tests/test_tarfs.py  [ 
> 53%]
> s... [ 
> 58%]
> ..s. [ 
> 63%]
> s... [ 
> 67%]
> ..s. [ 
> 72%]
> s... [ 
> 77%]
> ...  [ 
> 78%]
> tests/test_tempfs.py F.. [ 
> 81%]
> ...s.F.. [ 
> 86%]
> ...s...  [ 
> 89%]
> tests/test_time.py ..[ 
> 89%]
> tests/test_tool

Bug#973092: python-smstrade: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" --system=custom returned exit code 13

[Lucas Nussbaum]

Source: python-smstrade
Version: 0.2.4-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 '/<>'
> dh_auto_test -- --system=custom
> I: pybuild pybuild:284: cp -r /<>/tests 
> /<>/.pybuild/cpython3_3.9_smstrade/build
> I: pybuild base:217: unset http_proxy ; unset https_proxy ; cd 
> /<>/.pybuild/cpython3_3.9_smstrade/build ; python3.9 -m pytest
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> collected 22 items
> 
> tests/test_smstrade.py ....FF
> [100%]
> 
> === FAILURES 
> ===
> __ TestSMSTradeAPI.test__send_normal_message 
> ___
> 
> self = 
> api = 
> 
> def test__send_normal_message(self, api):
> httpretty.enable()
> httpretty.register_uri(httpretty.POST, api.url, body='100')
> >   assert api._send_message('01717654321', 'Test') == {
> 'status': smstrade.STATUS_OK}
> 
> /<>/.pybuild/cpython3_3.9_smstrade/build/tests/test_smstrade.py:202:
>  
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /<>/.pybuild/cpython3_3.9_smstrade/build/smstrade/__init__.py:374:
>  in _send_message
> return self._send_normal_message(recipient, text)
> /<>/.pybuild/cpython3_3.9_smstrade/build/smstrade/__init__.py:304:
>  in _send_normal_message
> response = requests.post(self.url, data=request_params)
> /usr/lib/python3/dist-packages/requests/api.py:119: in post
> return request('post', url, data=data, json=json, **kwargs)
> /usr/lib/python3/dist-packages/requests/api.py:61: in request
> return session.request(method=method, url=url, **kwargs)
> /usr/lib/python3/dist-packages/requests/sessions.py:530: in request
> resp = self.send(prep, **send_kwargs)
> /usr/lib/python3/dist-packages/requests/sessions.py:643: in send
> r = adapter.send(request, **kwargs)
> /usr/lib/python3/dist-packages/requests/adapters.py:439: in send
> resp = conn.urlopen(
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:670: in urlopen
> httplib_response = self._make_request(
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:426: in _make_request
> six.raise_from(e, None)
> :3: in raise_from
> ???
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:421: in _make_request
> httplib_response = conn.getresponse()
> /usr/lib/python3.9/http/client.py:1343: in getresponse
> response = self.response_class(self.sock, method=self._method)
> /usr/lib/python3.9/http/client.py:245: in __init__
> self.fp = sock.makefile("rb")
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = , mode = 'rb'
> bufsize = -1
> 
> def makefile(self, mode='r', bufsize=-1):
> """Returns this fake socket's own tempfile buffer.
> 
> If there is an entry associated with the socket, the file
> descriptor gets filled in with the entry data before being
> returned.
> """
> self._mode = mode
> self._bufsize = bufsize
> 
> if self._entry:
> t = threading.Thread(
> target=self._entry.fill_filekind, args=(self.fd,)
> )
> t.start()
> if self.timeout == socket._GLOBAL_DEFAULT_TIMEOUT:
> timeout = None
> else:
> timeout = self.timeout
> t.join(timeout)
> >   if t.isAlive():
> E   AttributeError: 'Thread' object has no attribute 'isAlive'
> 
> /usr/lib/python3/dist-packages/httpretty/core.py:438: AttributeError
> __ TestSMSTradeAPI.test__send_binary_message 
> ___
> 
> self = 
> api = 
> 
> def test__send_binary_message(self, api):
> httpretty.enable()
> httpretty.register_uri(httpretty.POST, api.url, body='100')
> api.messagetype = smstrade.MESSAGE_TYPE_BINARY
> api.udh = '040b02000820de'
> >   assert api._send_message('01717654321', u'48656c6c6f') == {
> 'status': smstrade.STATUS_OK}
> 
&g

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

[Lucas Nussbaum]

Source: python-bleach
Version: 3.2.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 -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/callbacks.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/html5lib_shim.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/linkifier.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/sanitizer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> copying bleach/utils.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach
> creating /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor
> copying bleach/_vendor/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_inputstream.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_utils.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_tokenizer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/constants.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/html5parser.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/serializer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> copying bleach/_vendor/html5lib/_ihatexml.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/lint.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/alphabeticalattributes.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/whitespace.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/inject_meta_charset.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/optionaltags.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/base.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> copying bleach/_vendor/html5lib/filters/sanitizer.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/filters
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/etree.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/genshi.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/etree_lxml.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/dom.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> copying bleach/_vendor/html5lib/treewalkers/base.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/treewalkers
> creating 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/_trie
> copying bleach/_vendor/html5lib/_trie/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_bleach/build/bleach/_vendor/html5lib/_trie
>

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

[Lucas Nussbaum]

Source: python-boltons
Version: 19.1.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_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_boltons/build/boltons
> copying boltons/funcutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/ecoutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/iterutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/strutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/timeutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/setutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/mboxutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/namedutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/tableutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/formatutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/ioutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/queueutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/easterutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/statsutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/debugutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/mathutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/dictutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/listutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/gcutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/urlutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/deprutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/jsonutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/tbutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/socketutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/cacheutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/excutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/typeutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> copying boltons/fileutils.py -> 
> /<>/.pybuild/cpython3_3.9_boltons/build/boltons
> running egg_info
> creating boltons.egg-info
> writing boltons.egg-info/PKG-INFO
> writing dependency_links to boltons.egg-info/dependency_links.txt
> writing top-level names to boltons.egg-info/top_level.txt
> writing manifest file 'boltons.egg-info/SOURCES.txt'
> reading manifest file 'boltons.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: manifest_maker: MANIFEST.in, line 7: 'recursive-include' expects 
>...
> 
> warning: manifest_maker: MANIFEST.in, line 8: 'recursive-include' expects 
>...
> 
> writing manifest file 'boltons.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_boltons/build/boltons
> copying boltons/funcutils.py -> 
> /<>/.pybuild/cpython3_3.8_boltons/build/boltons
> copying boltons/ecoutils.py -> 
> /<>/.pybuild/cpython3_3.8_boltons/build/boltons
> copying boltons/iterutils.py -> 
> /<>/.pybuild/cpython3_3.8_boltons/build/boltons
> copying boltons/strutils.py -> 
> /<>/.py

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

[Lucas Nussbaum]

Source: python-argcomplete
Version: 1.8.1-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.

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
> creating /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete
> copying argcomplete/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete
> copying argcomplete/my_argparse.py -> 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete
> copying argcomplete/completers.py -> 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete
> copying argcomplete/compat.py -> 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete
> copying argcomplete/my_shlex.py -> 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete
> running egg_info
> writing argcomplete.egg-info/PKG-INFO
> writing dependency_links to argcomplete.egg-info/dependency_links.txt
> writing requirements to argcomplete.egg-info/requires.txt
> writing top-level names to argcomplete.egg-info/top_level.txt
> reading manifest file 'argcomplete.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'argcomplete.egg-info/SOURCES.txt'
> creating 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete/bash_completion.d
> copying argcomplete/bash_completion.d/python-argcomplete.sh -> 
> /<>/.pybuild/cpython3_3.9_argcomplete/build/argcomplete/bash_completion.d
> running build_scripts
> creating build
> creating build/scripts-3.9
> copying and adjusting scripts/activate-global-python-argcomplete -> 
> build/scripts-3.9
> copying scripts/python-argcomplete-tcsh -> build/scripts-3.9
> copying and adjusting scripts/register-python-argcomplete -> build/scripts-3.9
> copying and adjusting scripts/python-argcomplete-check-easy-install-script -> 
> build/scripts-3.9
> changing mode of build/scripts-3.9/activate-global-python-argcomplete from 
> 644 to 755
> changing mode of build/scripts-3.9/register-python-argcomplete from 644 to 755
> changing mode of 
> build/scripts-3.9/python-argcomplete-check-easy-install-script from 644 to 755
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete
> copying argcomplete/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete
> copying argcomplete/my_argparse.py -> 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete
> copying argcomplete/completers.py -> 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete
> copying argcomplete/compat.py -> 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete
> copying argcomplete/my_shlex.py -> 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete
> running egg_info
> writing argcomplete.egg-info/PKG-INFO
> writing dependency_links to argcomplete.egg-info/dependency_links.txt
> writing requirements to argcomplete.egg-info/requires.txt
> writing top-level names to argcomplete.egg-info/top_level.txt
> reading manifest file 'argcomplete.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'argcomplete.egg-info/SOURCES.txt'
> creating 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete/bash_completion.d
> copying argcomplete/bash_completion.d/python-argcomplete.sh -> 
> /<>/.pybuild/cpython3_3.8_argcomplete/build/argcomplete/bash_completion.d
> running build_scripts
> creating build/scripts-3.8
> copying and adjusting scripts/activate-global-python-argcomplete -> 
> build/scripts-3.8
> copying scripts/python-argcomplete-tcsh -> build/scripts-3.8
> copying and adjusting scripts/register-python-argcomplete -> build/scripts-3.8
> copying and adjusting scripts/python-argcomplete-check-easy-install-script -> 
> build/scripts-3.8
> changing mode of build/scripts-3.8/activate-global-python-argcomplete from 
> 644 to 755
> changing mode of build/scripts-3.8/register-python-argcomplete from 644 to 755
> changing mode of 
> build/