Bug#976778: Known upstream, fixed with upcoming new version

[Julien Puydt]

Hi,

here is the upstream patch fixing the issue :

https://github.com/fplll/fpylll/commit/ede1e459f0662a0940dca6366aba20d47183a4a0

I tought they'd have already released the new version with this in, but
I should have waited until that was done...

And since this patch needs other changes to apply, I can't just add it.

I'll work on it as soon as upstream will have released the new version.

Sorry,

JP

Bug#976770: marked as done (ranger needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Tue, 08 Dec 2020 06:54:32 +
with message-id 
and subject line Bug#976770: fixed in ranger 1.9.3-3
has caused the Debian Bug report #976770,
regarding ranger needs source upload for Python 3.9 transition
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.)


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

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, do the binaries have to use
the versioned interpreter instead of python3?
Fixing #975451 would be the best solution.
--- End Message ---
--- Begin Message ---
Source: ranger
Source-Version: 1.9.3-3
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated ranger 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, 08 Dec 2020 14:19:45 +0800
Source: ranger
Architecture: source
Version: 1.9.3-3
Distribution: unstable
Urgency: medium
Maintainer: Vern Sun 
Changed-By: Mo Zhou 
Closes: 960184 975451 976770
Changes:
 ranger (1.9.3-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Mo Zhou ]
   * Should not depend on a specific version of Python3 (Closes: #975451)
   * Fix typo in the command binding (Closes: #960184)
   * Upload and rebuild for the python3.9 transition (Closes: #976770)
Checksums-Sha1:
 00c0c1f23f19b3bf2f4438f5beda8739ad561e06 2256 ranger_1.9.3-3.dsc
 df5c34fd85ee191ab08ddf85d6af6c9d817e83ee 11308 ranger_1.9.3-3.debian.tar.xz
 cfda8230157cb4cae9eae93432d4279aea6ac049 6979 ranger_1.9.3-3_source.buildinfo
Checksums-Sha256:
 47e0be73d01321659e0037ae0d929aa71446fea1d60498daf8f983bcf0a38a07 2256 
ranger_1.9.3-3.dsc
 9a4ffcf898c77369a5872ea9aa3836b34730eade0fa1fcc8dbfad3d1f4be58d8 11308 
ranger_1.9.3-3.debian.tar.xz
 472e8f9d7eead1b173eba421c16a2dd8efe54707a2e7105718c38e3a5672aea4 6979 
ranger_1.9.3-3_source.buildinfo
Files:
 08788e49079eb0a6aa1ca17c444ba667 2256 utils optional ranger_1.9.3-3.dsc
 929ce0167a7f820a18af2f54bf5ab26c 11308 utils optional 
ranger_1.9.3-3.debian.tar.xz
 360fd580b54bbfba009d27610899c5a1 6979 utils optional 
ranger_1.9.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl/PG9URHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaorhMg//Zc8BMFP1bmoWc2jT96JtBAfYQz9qb4WN
BQUgVVFwLl/dF1rD5OvDeVObIXXNTGmpWSFMb4sFJT+2dzHGc65nXyCpn0jJqfkn
JrixpFoa4/ijRcsmWxkDS6UiNsm8U2QV23TsBF6sjhTnFOONOkIEmrImWwSmg7fv
sXMm7RqDg+m1CIrS4zL0/HzwzbOTkYzD5NOUTVgIwWBd9IWeltmJx4ggL+kUURV9
/6w+toiLi/0SX8umxU/X3z3OAFR+fWwYw6ktfKtxie2gBDUQ++mBFe+AWBwHhPPE
UHLlqMCkoRuvb2BWnJVDpencK6KVtu9CZUFBL00ijhPXt8lRDMTkcKCGtSmsncEH
GyMnxd+S1QnneXtKKRp5GenCkte62tJqVWW/s1N3ub/75xtkjGExYJTxHhSPAALd
fwFlEKSsmDIUtvA8BnSwr6NR5W15xXgmK8r+jL3yIMm0TiTislNXX3KaJXQxEAZZ
Uzv8QRn5VRewMs4td33N0ST1nm9eP5Khja4eH8dXWH0EtzeyHN7/N7IHHwCFKosS
xss4LEIEHCCh5rzmHesGu43Fc5e83+BL9fsIY1xmgkzFLsnqhGuXBVHON5SaEqsP
J3VpUmvE+2dJr4oVwD75tO73oCZ4kvBySfKiW6iu6IUd1qiwY2ZiI5KtdEkox5jR
wJBJWG4gkDE=
=N7WS
-END PGP SIGNATURE End Message ---

Bug#976803: mrpt uses private binutils shared library

[Matthias Klose]

Package: src:mrpt
Version: 1:2.1.5-1
Severity: serious
Tags: sid bullseye

mrpt uses private binutils shared libraries:

Package: libmrpt-core2.1
Depends: libbinutils (>= 2.35.1), libbinutils (<< 2.35.2), [...]

Please don't do this. Either disable the use of these libraries, or
link these statically and add a Built-Using attribute to the binary package.

Processed: retitle 976778 to fpylll FTBFS with fplll 5.4.0

[Debian Bug Tracking System]

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

> retitle 976778 fpylll FTBFS with fplll 5.4.0
Bug #976778 [src:fpylll] fpylll FTBFS: fatal error: fplll/sieve/sieve_gauss.h: 
No such file or directory
Changed Bug title to 'fpylll FTBFS with fplll 5.4.0' from 'fpylll FTBFS: fatal 
error: fplll/sieve/sieve_gauss.h: No such file or directory'.
> thanks
Stopping processing here.

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

Bug#976802: r-cran-sf build depends on r-cran-s2 that is only available on amd64/ppc64/ppc64el/x32

[Adrian Bunk]

Source: r-cran-sf
Version: 0.9-6+dfsg-1
Severity: serious
Tags: ftbfs

r-cran-sf build depends on r-cran-s2 that is only available
on amd64/ppc64/ppc64el/x32 (see #976473).

Since the new r-cran-sf build dependency seems to be only
required for tests, removing it (also from the autopkgtest?)
might be the easiest short-term solution.

Bug#976218: [Pkg-nagios-devel] Bug#976218: nagios-plugins-contrib: diff for NMU version 27.20200511+1+nmu1

[Jan Wagner]

Hi Christoph,

Am 07.12.20 um 22:05 schrieb Christoph Biedl:
> Okay, I've removed the upload from the queue as I really like to avoid
> disrupting the maintainers' workflow by doing a NMU. However, I'd
> appreciate if you could deal with this pretty soon as it is delaying the
> testing migration of a fairly important package. Perhaps upload a new
> check-ssl only and keep the rest for a later one?

many thanks for helping out. I uploaded a package yesterday in evening.

Cheers, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-@ s+:()>- a+ C$ UL$ P+ L$ !E--- W+++$ N+++ o++ K++
!w---? O M+
!V- PS+ PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y+
--END GEEK CODE BLOCK--



signature.asc
Description: OpenPGP digital signature

Bug#975432: 975...@bugs.debian.org

[Nick Black]

I believe this to be fixed by the 1.2.24 package I uploaded
earlier today. The problem came down to lack of swap support on
the machine(s) on which the tests were running. /proc/swaps
doesn't exist on such a machine, and growlight thus aborted in
startup. Growlight is now resistant to this class of issues. I
expect 1.2.24 to fix this, but won't be sure until it runs.

-- 
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.

Processed: bug 975146 is forwarded to https://github.com/eteran/edb-debugger/commit/1d184460d392daed283ead8e1aaf461c94a87872

[Debian Bug Tracking System]

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

> forwarded 975146 
> https://github.com/eteran/edb-debugger/commit/1d184460d392daed283ead8e1aaf461c94a87872
Bug #975146 [src:edb-debugger] edb-debugger: FTBFS: 
QDisassemblyView.cpp:900:19: error: aggregate ‘QPainterPath path’ has 
incomplete type and cannot be defined
Set Bug forwarded-to-address to 
'https://github.com/eteran/edb-debugger/commit/1d184460d392daed283ead8e1aaf461c94a87872'.
> thanks
Stopping processing here.

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

Processed: Re: anki: Fails with Python3.9 due to use of deprecated unescape() method

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #975395 [anki] anki: Fails with Python3.9 due to use of deprecated 
unescape() method
Severity set to 'serious' from 'normal'

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

Processed: tagging 903413

[Debian Bug Tracking System]

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

> tags 903413 + patch
Bug #903413 [src:debbugs] debbugs: FTBFS in buster/sid (dh_installdocs: Cannot 
find "UPGRADE")
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 976780

[Debian Bug Tracking System]

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

> tags 976780 + ftbfs
Bug #976780 [src:pycuda] pycuda needs a manual upload to drop Python 3.8 support
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 975834 libblosc1
Bug #975834 [src:python-blosc] python-blosc: FTBFS: dh_auto_configure: error: 
pybuild --configure -i python{version} -p "3.8 3.9" returned exit code 13
Bug reassigned from package 'src:python-blosc' to 'libblosc1'.
No longer marked as found in versions python-blosc/1.9.2+ds1-1.
Ignoring request to alter fixed versions of bug #975834 to the same values 
previously set
> forcemerge 976569 975834
Bug #976569 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 
} [libblosc1] numcodecs: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 
13
Bug #975834 [libblosc1] python-blosc: FTBFS: dh_auto_configure: error: pybuild 
--configure -i python{version} -p "3.8 3.9" returned exit code 13
Marked Bug as done
Added indication that 975834 affects numcodecs
Marked as fixed in versions c-blosc/1.20.1+ds1-2.
Marked as found in versions c-blosc/1.20.1+ds1-1.
Merged 975834 976569
> affects 976569 src:numcodecs src:python-blosc
Bug #976569 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 
} [libblosc1] numcodecs: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 
13
Bug #975834 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 
} [libblosc1] python-blosc: FTBFS: dh_auto_configure: 
error: pybuild --configure -i python{version} -p "3.8 3.9" returned exit code 13
Added indication that 976569 affects src:numcodecs and src:python-blosc
Added indication that 975834 affects src:numcodecs and src:python-blosc
> thanks
Stopping processing here.

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

Processed: bug 975479 is forwarded to https://github.com/conradkleinespel/rpassword/issues/55

[Debian Bug Tracking System]

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

> forwarded 975479 https://github.com/conradkleinespel/rpassword/issues/55
Bug #975479 [src:rust-rpassword] rust-rpassword: autopkgtest regression: thread 
'piped_password' panicked
Set Bug forwarded-to-address to 
'https://github.com/conradkleinespel/rpassword/issues/55'.
> thanks
Stopping processing here.

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

Processed: There won't be another python transition before bookworm

[Debian Bug Tracking System]

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

> tags 954812 bookworm
Bug #954812 [src:pythonmagick] pythonmagick: autopkgtest regression: cannot 
import name '_PythonMagick'
Added tag(s) bookworm.
> thanks
Stopping processing here.

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

Bug#976794: Useless in Debian

[David Prévot]

Package: php-doctrine-reflection
Version: 1.2.2-1
Severity: serious
X-Debbugs-Cc: pkg-php-p...@lists.alioth.debian.org

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

I packaged php-doctrine-reflection as used by php-doctrine-persistence,
but php-doctrine-persistence does not use is anymore (well, the version
in experimental does not use it, but it should soon be uploaded to
unstable, before this package gets removed anyway). There is a priori
little point to ship php-doctrine-reflection in the next stable Debian
release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature

Bug#976771: marked as done (python3-semver needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:36:03 +
with message-id 
and subject line Bug#976771: fixed in python-semver 2.10.2-2
has caused the Debian Bug report #976771,
regarding python3-semver needs source upload for Python 3.9 transition
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.)


-- 
976771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-semver
Version: 2.10.2-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/pysemver have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: python-semver
Source-Version: 2.10.2-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-semver 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, 08 Dec 2020 00:09:44 +0100
Source: python-semver
Architecture: source
Version: 2.10.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976771
Changes:
 python-semver (2.10.2-2) unstable; urgency=medium
 .
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976771)
Checksums-Sha1:
 f2844c64026fb5d0ebbd85db5b8a5c4c74988b80 2155 python-semver_2.10.2-2.dsc
 e1c2aa3429fad4be4837feed286c237db0607db6 3052 
python-semver_2.10.2-2.debian.tar.xz
 76967993c51e8f5c4b3f04eaddfc5840684ab138 7498 
python-semver_2.10.2-2_amd64.buildinfo
Checksums-Sha256:
 5c7058be6a33bf4fe2043b434e1f4791444bebd5f9a1d7dc86db9daf1b667492 2155 
python-semver_2.10.2-2.dsc
 5d5ac40039dfd3063f16d3179ac2ca9bb62b3856875c0645ba0db877d54fa2ca 3052 
python-semver_2.10.2-2.debian.tar.xz
 b2430345b72f74e7973e94fe9b3ccb514a1eb020b101c7a163c31749e80148e5 7498 
python-semver_2.10.2-2_amd64.buildinfo
Files:
 25d6d36ea8bd530f95a017e21fd24660 2155 python optional 
python-semver_2.10.2-2.dsc
 1674007d5637edbe37080614815c0623 3052 python optional 
python-semver_2.10.2-2.debian.tar.xz
 258d867102fb3c5691aa7aa36ce40a2b 7498 python optional 
python-semver_2.10.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OtnYACgkQ1BatFaxr
Q/7xUQ//fLXNVJVHdX1x6plSy/Ra9VExH9LanSJP+ZxZ64mTti1OgcM+KzAO3t9c
zRfL/s7AdawRtjkcFJ1WrcpejyU0gxopwWSOgv25F307hx58kwRNluxNn4MD1aMH
LAPWRVTZd4CdFa7oPgmeAcLF4PWUUvlIeC6b9Gxv+KoPL9o9D4otMLCyQlr2rdZI
Ecj+CXhrHBit3NYDjrhJojOyXnrVRHapFcn9L4lVvbvDw6CH/5PZXgV96+Go9YNW
uHmTWeuMEJ5YDLI+gcRNcA7oT5jGJ/WWAqz2TRAgiJjIC9BOvIIyBVe3Vr6LBSh2
ELaB5Hr7jSrkyRD6x0NAnegWOf3zuMaHU/sdCokwwPIGDKmw7InzZlZb6aW1GEFB
dDTiWxlIAozP6cF3S1p9iLhZFe6RsgIp2n8Tn2OU8dBRfW9+sz0kWO7OuB0t9gTM
JlnRXW+ola6Y7k+4dEKXpGggj/D55JC6TAbOkWU16wzT7c59WB7rwoUvwioetRku
oAZisZhJnAVdjwZG/84WHE3z/L899n0j70e3pUd45MDGqdLZ5OVGjSJG/w0xVLjZ
ilcb+5GxVXS55h8JxxyDNfbAUZTN1saBOelcE4dSMu1Xaq48WFqi55xn1D8gpNAI
BF0h7LecVC7TGz/jIanuikHreU6p1tSbbGJYjF5G7KtLr8PEahA=
=ulYK
-END PGP SIGNATURE End Message ---

Bug#976772: marked as done (python3-calmjs needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:35:08 +
with message-id 
and subject line Bug#976772: fixed in python-calmjs 3.4.1-3
has caused the Debian Bug report #976772,
regarding python3-calmjs needs source upload for Python 3.9 transition
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.)


-- 
976772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-calmjs
Version: 3.4.1-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/calmjs have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: python-calmjs
Source-Version: 3.4.1-3
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-calmjs 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, 08 Dec 2020 00:11:24 +0100
Source: python-calmjs
Architecture: source
Version: 3.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976772
Changes:
 python-calmjs (3.4.1-3) unstable; urgency=medium
 .
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976772)
Checksums-Sha1:
 6ad0f5c39c5accc3d979c5e2a42526bf7f4dc315 2092 python-calmjs_3.4.1-3.dsc
 9db10faa971e16cbd7b08d7c4d3ed2e1debf010a 2132 
python-calmjs_3.4.1-3.debian.tar.xz
 136949290401635500b9a7cf558c82216ca36c96 6772 
python-calmjs_3.4.1-3_amd64.buildinfo
Checksums-Sha256:
 184759374c8312b02e71f46c837c9121bdbe67e024cb6c269d00f1475220221a 2092 
python-calmjs_3.4.1-3.dsc
 6b0ffc65f8203f4e960527fcaa35f86b0ac8cfcb3f3bd6859399b2f54178ac0a 2132 
python-calmjs_3.4.1-3.debian.tar.xz
 5893a3dc91fb77ba2cfdce16322d4ff9d230cd20fa1a7595a9369c76ef961347 6772 
python-calmjs_3.4.1-3_amd64.buildinfo
Files:
 384c6ed5f8484c0ef5a71b5845e62217 2092 python optional python-calmjs_3.4.1-3.dsc
 495fb85599d5de271cb49db97f0688a9 2132 python optional 
python-calmjs_3.4.1-3.debian.tar.xz
 7bdeae0c9651fc218957ec486fd3c2fa 6772 python optional 
python-calmjs_3.4.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OttgACgkQ1BatFaxr
Q/76pQ/+JQBgDlV8baPe61XyRKpBaurJvAuST1dXuZ+vSa95eUVfyV3dKfUQzkph
ks9tdvNYStLHqbrD+wai6Lixtd7dU4NdimbV/Xy4J7brjjHVolDbX4EdSs94qXYw
ECY+P0actKr6PmNi5N6FLPXgGSPPzJBhrjxDq6ueXqSc7IzqLYD+6PKSQPTpD6JG
stV5CQ+ha4APAFgIUFoo+E8BqZCnN5TR52F+0PN+Z7DJz80yjuNQxxmtqCqz6v7m
/Y4wGHJ5y71DsqXXYWxIeorgqhZRX/UcDMo4C47n4/t7lSMZigZZGP7eoNrsedzm
QNDVxNZqqvtj2LTLMtXUWYW1OTYGMiyI+bAeSQqQA/Q3Az2DPJfGH1jxtNwWYFs9
RvE3I+rWsaXwTDr2gb58fZJKEu9UQ9dpEFfYBFdI6Ez8KrAJbpU2s2dJuVyJIDWM
MdLexrMeH5lCwE2d8eF60EpltrHN5w7m+F1D2DO1NUHIMgtMvggu8gq/h6SS4zyW
NmZvOuaQ6ASDA6PY3kOLWG0hOecvfeLs+Cjp2QKGctcRt1Ll5n9ItDHfkAz4slXc
9iTx1ZmaXxFhkk5j085vtnEFROvx8MEmA6ZrlvAOxjx+9q0/mtY1NgTq6KtDN1tX
vV/cnIuqO4HDJuMgn77W/OL9OsZ8pMuisChkC6DcsxuMLe8LlJ0=
=aow9
-END PGP SIGNATURE End Message ---

Bug#976781: marked as done (rocketcea FTBFS with Python 3.9 only)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:27:08 +
with message-id 
and subject line Bug#976781: fixed in rocketcea 1.1.18+dfsg-2
has caused the Debian Bug report #976781,
regarding rocketcea FTBFS with Python 3.9 only
to be marked as done.

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

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


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

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

...
   debian/rules execute_after_dh_auto_test
make[1]: Entering directory '/<>'
rm .pybuild/cpython3_3.8_rocketcea/build/separated_Noz.csv
rm: cannot remove '.pybuild/cpython3_3.8_rocketcea/build/separated_Noz.csv': No 
such file or directory
make[1]: *** [debian/rules:10: execute_after_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: rocketcea
Source-Version: 1.1.18+dfsg-2
Done: Bdale Garbee 

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated rocketcea package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Dec 2020 15:34:18 -0700
Source: rocketcea
Architecture: source
Version: 1.1.18+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Bdale Garbee 
Closes: 976781
Changes:
 rocketcea (1.1.18+dfsg-2) unstable; urgency=medium
 .
   * fix version-specific rm in rules file, closes: #976781
Checksums-Sha1:
 0dd7b893d1f434508626c5bb8b701f3461e59cef 2032 rocketcea_1.1.18+dfsg-2.dsc
 759afb43cbd8cd504c4636c3db48174a6b179e69 3252 
rocketcea_1.1.18+dfsg-2.debian.tar.xz
 c70df68b3d59ab8fa74cb4d2c38d096d036da210 8300 
rocketcea_1.1.18+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 cd5c98bcf7f7f9a0dc8f10ce8a1bc9447a113780259e4c84be6d68af68125211 2032 
rocketcea_1.1.18+dfsg-2.dsc
 89e07d8b94808350d688c2fdaa97c60b0152df3b96357cbdf68e75100027b4a1 3252 
rocketcea_1.1.18+dfsg-2.debian.tar.xz
 84b2e3caecb8c8707d9e91c4104371d9ceed43d2d550c0268dceaed54f0681b5 8300 
rocketcea_1.1.18+dfsg-2_amd64.buildinfo
Files:
 f140cf8680ae8f26450d09146c521930 2032 science optional 
rocketcea_1.1.18+dfsg-2.dsc
 1023876924bf606174fd5b17225cdbf5 3252 science optional 
rocketcea_1.1.18+dfsg-2.debian.tar.xz
 6ff7d2965eab983b3158ca81497e170b 8300 science optional 
rocketcea_1.1.18+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAl/OsGQACgkQtwRxBYML
n6EmixAAmeBsj99EvAEyOGqFoOJ5jhrIjVek3VodFAGzrmkV5BelYALUTmg/sNun
cnAgWkMBtsarlLkKKxD9iT/IFMpLKJQ8dvNSZcEYDoLutUqYP72gRI3QKhxlJs1+
F03cn0gN2OZruweKkhsIbXlqO8vWTDY+ainm/HFn1rmZke4g47wbnf7Qo+Sxs3jN
7t1FpIe6ZRno3ovbNkOp5p1JbD1g1fe9Rwe+ye7wIqhXXUFbZIm6WuviA0ooD/gr
jjKK+uw/B0ehNtkI4l4ZuyzgiRfZd3yLz2oBd6kv7vgWpQUT1yzMgrAqDn3BoLlU
mu0ZA7BXZc01EXYNf6DjKbzCtCHC2lP+qntqCpGdwo6vbwA+tDABvNgDoZR1r6i4
pwWDGntKKHXXWk94PEeSsbmutvwao9mqHGUBhPgLEFrplPSClkMpHlUaWzzwC4uC
T/6Xx4x70BdK1xFS5fCYLVzOSAL/GpPOs9gKePatoQpJmkRrVei0/A/T/3o+40X4
fLI5a6tQI2VaB1gf071BPCu1S8TiQ+iBAwxIYP5exfbkg6BIbtg13EUTrsWVl8PD
KLPkj+JZYlW9mP9GvqHWRkOmRfjyKr/tg9Umsw0TNRMx7RyrxsJA9wlhVsqlFa1X
ZVyIvhou+6cIpwSLYwcKz2ozbJnoGfTKuejSeW1eW0MHqKhcbAA=
=TZTS
-END PGP SIGNATURE End Message ---

Bug#976769: marked as done (redfishtool needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:27:01 +
with message-id 
and subject line Bug#976769: fixed in redfishtool 1.1.0-3
has caused the Debian Bug report #976769,
regarding redfishtool needs source upload for Python 3.9 transition
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.)


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

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/redfishtool have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: redfishtool
Source-Version: 1.1.0-3
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated redfishtool 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, 08 Dec 2020 00:08:09 +0100
Source: redfishtool
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976769
Changes:
 redfishtool (1.1.0-3) unstable; urgency=medium
 .
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976769)
Checksums-Sha1:
 fda20535046801a12ea8303608e46e2cb7568edc 2032 redfishtool_1.1.0-3.dsc
 61ffead970b783641e29e743f46cf0bfce9a7ac8 3684 redfishtool_1.1.0-3.debian.tar.xz
 30042f0882fbd9e309a77f5f08cf9cf509569419 6650 
redfishtool_1.1.0-3_amd64.buildinfo
Checksums-Sha256:
 f8aa4c5540909bf980c43a867ab453b8974bd9f02d6101a668e9c789e8e30dc4 2032 
redfishtool_1.1.0-3.dsc
 8d218ffa666c8b353015f15ea65cdb976d3b2907165dee5707489f857162c838 3684 
redfishtool_1.1.0-3.debian.tar.xz
 4d2a2f7ae41bcc16fbc804a50c2ee552a5a15316e22cf49029c78c137004683f 6650 
redfishtool_1.1.0-3_amd64.buildinfo
Files:
 62f1125adfeab20973a818e859d7b1f1 2032 admin optional redfishtool_1.1.0-3.dsc
 fa2d93a89b1f4c58304e50d2c9853d05 3684 admin optional 
redfishtool_1.1.0-3.debian.tar.xz
 a3f8ed9ffc38bff1e50f677d6250b4b3 6650 admin optional 
redfishtool_1.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OthMACgkQ1BatFaxr
Q/7urg/8DBKngpNPCROCbHVnMvF7Bf/RQS39dgmtDz0yPzJJxMyK3iy56k3Malo0
uwu4s1sIMIZKQGwA55QszHWkMmtUofnRvVabSmgwfw9sITzSj8rggobv+mNwYVJf
T6KD16O2cT5XbjO7uLIWLWDkoitK1iXG4haeXvgQkpYJF3O+/E0rMbwPrvpxoSuS
C1wNCbEhyfxFQLLmSwfAUMnh5kU6ppKf3L1VY9j82ZuNWWV51gbzkOkQWZqwOY8G
w7IOcoIWg1Lbk8t+/CfP13M1GP89OzISDjhlDnPiS0feVCPL9RPuo7k44A53nMZW
hkB0TJhRE0C+JPhhOxbYBBM9b8YnxOyxnFII3mgoSRscxPD1kWSFbk/DpGg1icE+
L089lWRPjGACCg8izNrUUAo5SqQh4VPF2M4DePfi2hFRD2mLKOSVgw3/Gkd51C8h
UHK40aSMzthyyfeRxuCX1/3iKZx1dzIUS5+77dcrNZAuY037ZOUYPXpkV9qCivgX
0aSxJC1geEn+mbvnem9NXcJLIPULGLVNOfLeN6Kwm9zhdSvmrHCr6EWWYUbyMUEI
0BjuHMpxJSsAEWTwgAfX1NeRT6jdZuAzv6v33MgC1hFNF30uDo7WqlRAIpZe5OZ3
T+CM/iV2Dr1LL+XIbRMlSkJz4A6XnP1Gf5yT0gVfSDMtNTiak6k=
=t1o+
-END PGP SIGNATURE End Message ---

Bug#976765: marked as done (python3-sushy-cli needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:26:30 +
with message-id 
and subject line Bug#976765: fixed in python-sushy-cli 0.3.1-3
has caused the Debian Bug report #976765,
regarding python3-sushy-cli needs source upload for Python 3.9 transition
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.)


-- 
976765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sushy-cli
Version: 0.3.1-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/sushycli have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: python-sushy-cli
Source-Version: 0.3.1-3
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-sushy-cli 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, 08 Dec 2020 00:04:10 +0100
Source: python-sushy-cli
Architecture: source
Version: 0.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976765
Changes:
 python-sushy-cli (0.3.1-3) unstable; urgency=medium
 .
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976765)
Checksums-Sha1:
 733ad2e2c458008cb88578e797853ec40110c03a 2372 python-sushy-cli_0.3.1-3.dsc
 b20a219f550ae55d3ad61a9b513f18f7a97e2be3 2628 
python-sushy-cli_0.3.1-3.debian.tar.xz
 b69419bece01681dca1b420f401f30c0c1b764b7 10468 
python-sushy-cli_0.3.1-3_amd64.buildinfo
Checksums-Sha256:
 c1b3c63fdeb0d937945470d738dec978b71e24f449b372ba5b1047184453501a 2372 
python-sushy-cli_0.3.1-3.dsc
 0c9041de7293d5bd751b49400382dda9ae56bfc8c2447547f2ad2fc3ccbbf117 2628 
python-sushy-cli_0.3.1-3.debian.tar.xz
 3b31781125ba99e94fe13ca80cd17318c5d2e84340f804db34fc76d5da54574e 10468 
python-sushy-cli_0.3.1-3_amd64.buildinfo
Files:
 9c984d010d6efd2fd2b05ed77757abc6 2372 python optional 
python-sushy-cli_0.3.1-3.dsc
 9d36faeb8e0f77196b7a9097407171ff 2628 python optional 
python-sushy-cli_0.3.1-3.debian.tar.xz
 b5d7361f537eaec1c0e42f077f6dc61f 10468 python optional 
python-sushy-cli_0.3.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OtTsACgkQ1BatFaxr
Q/5kWxAAlngsYV6cW7XN3f+kUNXwQ3n4McYDq+bUlFEVvjaLdyShfHrtQG7GF3/6
iTnTeaRSI5C50ZSdncsz4XZN8RXTl0tpnQ0vjohMOwboQlhA8bl2ffq5hzqi9KrA
E3jAXixB9OzxYlDnEK6ttJ93KxYinZn4XjNmp4ORl6lIKaGx1JpY1xIe3pkSrKLi
Nm+FCXwrIx1GqTb6Ps9SYvbERQNFG+Jz7xZqKj2B0963u9GaFzJIl0gn4XKwBm2+
0ZmCUdAU8AlbaAxrxYKdEJDV5El4YQC20WNRRPdIm2VvU7B7ID8fxFtR4CEb0S6b
sZ8yE9TrtfNaQRbAyn9XV37fkWRQ6sB5GaHk1DMrRhHRaoRkI0FZILtWIOnNbBPS
O2qqK3rCJgLiE4++feO1uCllJbY+zYyZR36UNWZWoPONFd5iOVQJqeoi3sYeML2I
VKIMf7Ldp8T/oDlwfV7dx9IgWPGf+WWCtJFY0idoUIGXPhKnYauMEA6dVkzScn+/
Mp1aiJCmf/uJx+sWj/bkr/yXu/6pYouoRW5JiF2X6uZOWjoYXa3vx24IAggPAyou
I9hYlbuu7/GBlXwYE4p2BfLvd1VTC4SAKsZmvDdmi7SS5hoUQ+CqiPW6nsX6XHbB
bHqCLpS1LZ+8Lh1QCcgBo0w+A8PpjBzbbNCRMiOiWkqce49JGEo=
=LH0X
-END PGP SIGNATURE End Message ---

Bug#976766: marked as done (python3-cyborgclient needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:22:22 +
with message-id 
and subject line Bug#976766: fixed in python-cyborgclient 1.2.1-3
has caused the Debian Bug report #976766,
regarding python3-cyborgclient needs source upload for Python 3.9 transition
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.)


-- 
976766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-cyborgclient
Version: 1.2.1-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/cyborg have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: python-cyborgclient
Source-Version: 1.2.1-3
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-cyborgclient 
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, 08 Dec 2020 00:06:14 +0100
Source: python-cyborgclient
Architecture: source
Version: 1.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976766
Changes:
 python-cyborgclient (1.2.1-3) unstable; urgency=medium
 .
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976766)
Checksums-Sha1:
 3e83be1671f499f948e5f56030534fa5dc56200a 2685 python-cyborgclient_1.2.1-3.dsc
 d0558d313e25aaf48097964384d23576f76b0f93 3024 
python-cyborgclient_1.2.1-3.debian.tar.xz
 f32e77ad06718f1a7531756e8b6e0aec2a13aeb2 11145 
python-cyborgclient_1.2.1-3_amd64.buildinfo
Checksums-Sha256:
 9f63f5b0e6d23f848f6138bf55a7044c7053aaea03a94c02f691fac106d8be21 2685 
python-cyborgclient_1.2.1-3.dsc
 78e9d1ee9da0c5f61e2c67542422e676adea86d04292df8494ad8c7c7ab0a196 3024 
python-cyborgclient_1.2.1-3.debian.tar.xz
 5299ee9d1e9d67c9c28b802d209cae3546098bfb8cbd2122fddd159a666d345a 11145 
python-cyborgclient_1.2.1-3_amd64.buildinfo
Files:
 3fe695d1a494e059dbbe124ebc13e514 2685 python optional 
python-cyborgclient_1.2.1-3.dsc
 0f4910cb59fcc1c6d23e28df9cea29d4 3024 python optional 
python-cyborgclient_1.2.1-3.debian.tar.xz
 5eeb0903937a99d5329a026d6f1353e1 11145 python optional 
python-cyborgclient_1.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OtbQACgkQ1BatFaxr
Q/7irQ//V0R60tQoSXOwpS3Qn+b43PgpqBYzLIBVGvf5f3ewgNYcWDBf8qjhNUAL
G1Ec5R2XCiTJjlJYVaefOrWXpd38+S/KOn+2Y6yt09LG5n8Rz474bXGNKCNDMmm3
vgCPcg0SQwjP/b/X6wWBzk/CCdP4dYlxWcEsKQCnKvlhDnKOCPbAnZlcnSQ3Zwn2
CFXIz4q5bFa/U2Ws/RLgJzpdll/CtjOriNSHpXN8YSMyXxj0hy+G3UkTSAVLIP9E
9ue0JtobWLszuhwgCqvOmHMysK5gH4hxvalunjd+6aq4n/uNc0tKPUNoYq0jDTNw
LhzVw3FpyINtCU7/7d4OkWbOS11mr4vywkSMWZm1WrcXQHrydwXWLYt2Uzz/eXWl
Uky7CqsIwYOA6oj8CB79IdcnRmxlL+ZDTvs4SSNEccu3PklV0YDsgoJCrYbLTc+D
bmFBekb20qg2fVLRAUrDmMN/Ku/qsgGc6uL8jzXaJ4jSds9fHgLb6Du6riWuhwTX
jXm+0g1WWbwKkdxeIhbIn0RiWXhylWA1aTNrWWAF7bHrbgEr8atVSKoCwr5y9Mhw
14Or7+pZQGx/CY+jIos6ZjsnhHL+nfp/bVloeuy+BuNiSYjl/mce6DZAlYZ+bj+X
bvnKcUUWCZ2qfIEDz4+bJEE0Nx+LpmtfYxZ3wMZIywZ0xpgx79k=
=N6AT
-END PGP SIGNATURE End Message ---

Bug#976762: marked as done (python3-os-collect-config needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:26:03 +
with message-id 
and subject line Bug#976762: fixed in python-os-collect-config 11.0.1-1
has caused the Debian Bug report #976762,
regarding python3-os-collect-config needs source upload for Python 3.9 
transition
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.)


-- 
976762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-os-collect-config
Version: 11.0.0-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/os-collect-config have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: python-os-collect-config
Source-Version: 11.0.1-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-os-collect-config 
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, 07 Dec 2020 23:49:24 +0100
Source: python-os-collect-config
Architecture: source
Version: 11.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976762
Changes:
 python-os-collect-config (11.0.1-1) unstable; urgency=medium
 .
   [ Michal Arbet ]
   * New upstream version
   [ Thomas Goirand ]
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976762)
Checksums-Sha1:
 852674452908553d81f7b961b74b1947850b3d1e 2610 
python-os-collect-config_11.0.1-1.dsc
 d45a61db0b39463d7ce5c29b9e7f9931fc7abe22 43524 
python-os-collect-config_11.0.1.orig.tar.xz
 1732ca34afd6d0d95d3fdfb5183ffdcb2b4a3b94 2656 
python-os-collect-config_11.0.1-1.debian.tar.xz
 f2313d10ef81a25c0c0a6f3b37204c2af0a87093 11455 
python-os-collect-config_11.0.1-1_amd64.buildinfo
Checksums-Sha256:
 bf1b11e716db45b17426715cab2e5f85c199c8282dccacc4cfd2edc8b37f415e 2610 
python-os-collect-config_11.0.1-1.dsc
 036bb1f075afd4a4690e47caced9ac5e5d9d13a61c1f386824ac76de590c75b8 43524 
python-os-collect-config_11.0.1.orig.tar.xz
 52ff9e995f3da60ee9fc35402f0adfbc206a808db4236be80e51530e790ad73c 2656 
python-os-collect-config_11.0.1-1.debian.tar.xz
 5ad815e637fec48fb55547ba3b7be2466836e5d981189984f0f4c8d0afba13ee 11455 
python-os-collect-config_11.0.1-1_amd64.buildinfo
Files:
 b29e5dd7377dc2ddb698cd27bbf19caa 2610 python optional 
python-os-collect-config_11.0.1-1.dsc
 fc6a7d39a71980609157230638df350c 43524 python optional 
python-os-collect-config_11.0.1.orig.tar.xz
 cf201e12d3b085d4fff6b593e5b3076a 2656 python optional 
python-os-collect-config_11.0.1-1.debian.tar.xz
 57ee30655c6a56cf3e44d6b41783dc14 11455 python optional 
python-os-collect-config_11.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OsioACgkQ1BatFaxr
Q/7h9w/+JAndyMkYo2ZopRwRd2cVM06htlsI0TVYbVC5FL9+5lwHm1w+SyjxFc/+
h/etWk5+wroBfKuIdfDgyirXU5TgA3fODQlNM5Pg0HHF5tob7hO/5swK9MDfAVmv
bITZt2RC0zKOYXOh+SEbts17FysI0MbpDseiV7VsbDXi+XJNjj2oBGeDbnpiJfUC
W5Oui7ki8ynRIyxquIC01URUgKyZzx6E5wSJFEmoHSrtRfahVMxgycDsrWsQ77tT
q16tXX0G03RtJ8LG8cCw2t3oXTQwVvmkfxGumDmgIQKKjEy80O7+KHSM/DTfGGXV
yLxi8m7uhe9FBcmM6bYMWcr8+lH6ldB4/WBkP/qASNHEN+ITqMjJO51wviRJzsyn
U6396QCBhAc18GAZwIXvp4Nalo5I0kj/n6InTfL9ioIScbvjYt1Qc4hJ/oLmc1aO
xNUKzjbAF0i00qw75Jjc9Oq20HoDkFUH6i58JKKlZLvprf73B5FyK7EAoiy1sJqA
zFoemOPNOOnuUuUCrZKr9Q2oxX1IbVfxkADEwTRtKu4E/9fB4RILHWwt0/t2tqSB
j0KoR1UJXZkg7/yZBsXBgnjk4P64kcmRv1hi8d3Y9A90DiBBV7znJZIWh2/tIghP
CER2+qh9gH3eEy2s/NBHgf6p/hzQZeVCc9SQ2QYF3YfqEoJWtU8=
=TyAY
-END PGP SIGNATURE End Message ---

Bug#962100: marked as done (python-memprof fails it's autopkg tests both in testing and unstable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:25:14 +
with message-id 
and subject line Bug#962100: fixed in python-memprof 0.3.6-3
has caused the Debian Bug report #962100,
regarding python-memprof fails it's autopkg tests both in testing and unstable
to be marked as done.

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

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


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

python-memprof fails it's autopkg tests both in testing and unstable:

[...]
autopkgtest [05:36:17]: test python3-testsuite: [---
E
==
ERROR: test_demo (test1.Test)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.w_y9am08/downtmp/build.xvE/src/testsuite/test1.py",
line 29, in test_demo
import demo  # noqa
  File "/tmp/autopkgtest-lxc.w_y9am08/downtmp/build.xvE/src/examples/demo.py",
line 19, in 
from memprof import memprof
  File
"/tmp/autopkgtest-lxc.w_y9am08/downtmp/build.xvE/src/memprof/__init__.py", line
17, in 
from .memprof import *
  File "/tmp/autopkgtest-lxc.w_y9am08/downtmp/build.xvE/src/memprof/memprof.py",
line 25, in 
from .getsize import getSize, isInteresting
ModuleNotFoundError: No module named 'memprof.getsize'

--
Ran 1 test in 0.447s

FAILED (errors=1)
--- End Message ---
--- Begin Message ---
Source: python-memprof
Source-Version: 0.3.6-3
Done: Graham Inggs 

We believe that the bug you reported is fixed in the latest version of
python-memprof, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 962...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated python-memprof package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Dec 2020 22:35:14 +
Source: python-memprof
Architecture: source
Version: 0.3.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Graham Inggs 
Closes: 962100
Changes:
 python-memprof (0.3.6-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Graham Inggs ]
   * Fix autopkgtests and run them on all supported
 Python3 versions (Closes: #962100)
   * Add debian/clean to fix FTBFSx2
   * Switch to debhelper 13
   * Set Rules-Requires-Root: no
   * Bump Standards-Version to 4.5.1, no changes
Checksums-Sha1:
 7361d657dd4a3f00cf00af6dc606d89593e30b2c 2106 python-memprof_0.3.6-3.dsc
 225bef77735a8148c8390280e83ca6683931a36b 4056 
python-memprof_0.3.6-3.debian.tar.xz
Checksums-Sha256:
 8921310e782622f047de44889f52b62759234328496b6fa90962a2bc097507e8 2106 
python-memprof_0.3.6-3.dsc
 b0c9b5b212aedd152f8161bec9dd0cf6be9481e6676766f8d5ba20374b53d3a9 4056 
python-memprof_0.3.6-3.debian.tar.xz
Files:
 85924f1e2f7bb1fdf9d5aac4c9ea0132 2106 python optional 
python-memprof_0.3.6-3.dsc
 eb39489d37bcc6b4bea3db5a2149bb77 4056 python optional 
python-memprof_0.3.6-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/OsVIACgkQr8/sjmac
4cJTUBAAhr9CDBLiyk0fLU4r2w18KRPHlJt2vbYN7U3jOblMwuAoWCzxDQzHnu3x
vkSKXg6iiMzBbHs5UZrl2cX3K4aMCJET80MRRcgPVGZRnNpnkEmTfOPoI0bA2EfE
yxC+JJSk0esmPQEGCBcF5+MyaQBb/u9QZnHav0M2tiUxuNMoQKJzUppCcxv92trU
2RV3vv8WEjIw/8lrI51httBUx4AYLqSZsqneVmq9IgMIHM8nuo4PQX8dhVI1/wVm
AAmLYy0VsBzrsWs3wkXRJVdFeZSl9PUIpVh/AFY72Dz4LPInl3Wl44CWvEHvfBDm
FbO/1Ox8veUh/pqXEZY+sVooOuwbd+Yp2LNctyFp/zTfLd4LKvRmHb3P1AS1MbS2
kwBOCeyqPctbj3OgyhKd5PiOSDY4IzReHBIPJ3dnTlhPazoXUvGfpmWJ5p2ud3yn
/j7/lax9k+xcnG9w59gGRP1QeWe+tMMPzes1sLcKUYM7VBlMFP0ZGYgjLVt2SQm1
fDX7GS61uiXmPmbEmQq3rPC7ZqW8n3xqaKWdohT9Ugp2gzQPKnbAqws0Xh5rtYza
fzlCr4+J2OE0xhDQLiqjVtGfQkI4XgtC1r5Sg2KziRYxh3YfjwKCAyjSjqY+cGYJ
o6adajTOeBtgoRVlUg6RyPMJSICurSnIweP4px0t2eSXz/wyy2Q=
=8Fl5
--

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[Russ Allbery]

jim_p  writes:

> First of all, I am really sorry about the annoying logs that spawn under
> every message of mine. I am not putting them there on purpose, this is
> all reportbug's work. I tried setting it to advanced and expert, hoping
> that it will be less spammy, but it isn't. I admit I have no idea on how
> to report a bug outside reportbug.

To add additional information to a bug, you can just send mail directly to
976...@bugs.debian.org with a regular mail client if you want.  (reportbug
is very useful for getting all the right bits in place to open a new bug,
though.)

-- 
Russ Allbery (r...@debian.org)  

Bug#976722: marked as done (python3-freezer-api needs source upload for Python 3.9 transition)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 23:18:54 +
with message-id 
and subject line Bug#976722: fixed in freezer-api 9.0.0-2
has caused the Debian Bug report #976722,
regarding python3-freezer-api needs source upload for Python 3.9 transition
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.)


-- 
976722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-freezer-api
Version: 9.0.0-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, do the scripts have to use
the versioned interpreter instead of python3?
--- End Message ---
--- Begin Message ---
Source: freezer-api
Source-Version: 9.0.0-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated freezer-api 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, 07 Dec 2020 23:43:52 +0100
Source: freezer-api
Architecture: source
Version: 9.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 976722
Changes:
 freezer-api (9.0.0-2) unstable; urgency=medium
 .
   * Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976722)
Checksums-Sha1:
 07050410813ef7eb79325c463afc70f4f2785e92 2843 freezer-api_9.0.0-2.dsc
 2fc6ea20b1377ecf95c6adc621e7b582f51b4756 6304 freezer-api_9.0.0-2.debian.tar.xz
 ee8aafcd4d82e7ff06bbd770a866be448a72ce99 12920 
freezer-api_9.0.0-2_amd64.buildinfo
Checksums-Sha256:
 eac9df140beb3140719b17b9d9588deffdcf55dc2a04f730d0c64e725df705ea 2843 
freezer-api_9.0.0-2.dsc
 26bfd5a5f59e99498823d5d0d770d813afdb99c01b5de8fee3fc1095c5486936 6304 
freezer-api_9.0.0-2.debian.tar.xz
 05d219b1336dd4ff1a970c8264ce20f3842feb64fa1ff37dd68564c345f65e25 12920 
freezer-api_9.0.0-2_amd64.buildinfo
Files:
 d39fb4a6c0770c583018a76a253a47ed 2843 net optional freezer-api_9.0.0-2.dsc
 b54385328800da85b0d7d925f97b68d9 6304 net optional 
freezer-api_9.0.0-2.debian.tar.xz
 c82d3d9d4f1fe572627c81575bd36f5d 12920 net optional 
freezer-api_9.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/OsNgACgkQ1BatFaxr
Q/45tBAAkfUkZcLgeCrEcHkqIMQirEuQdv8+DHESBPmpjuqbLOlvSksND5bEXXcg
cFtzsU3Kaw/rPVkWOVJenh/CS8wjFzluU5iyD6YzDejh5hBhG/BExHbUa8wY8jYP
c4NZN0JhkRyxcqlavWTxuElQ9JCPeT5+UsCq/zih0/MGNVLdXsDzTmJjGC5CIRDC
E4/WmYDbjU6lFQsfGAjTkHXh989BRU8pAKGqLao273VpxIvnd8epztrw+NhSkUgW
iocccL/cPeeTLdr+qyzouRtb9PDLf85t75taYHE1tEC2y/rjNCD9VlT0bSJjlmLc
cKlbjvr2EJVEQmHlALErzfB9s4bWHhyZxYEVhRmYtkwsYJjkhPaYYJnzcEuYYr6Y
J1ktGnPb5ASRu5MZ7ZeVooWdRFvTa0AU5GwCokmUMCs2D/4sRR4Lj3u1AUKAqeBK
CWremE/158qvMm6YxwvcZmVDzgRvOL3VwP9drzvM+7c5VoUn5TG/tXcN2+56hETD
/+qFDOPCwdIEdSZALAsQygsv0Ln6xvtm05UIhQyaLqK94tMPpCsHqzywzSfpViYK
Zag1qwkpHVq51mzpXa4igiNk7Hmc5Mvusy7lsWjc5Xly64rjBFgFW3XvkcR6LneN
DHeCwbM5olEKT/9OL9PXRFSE57DxRXj9CjcVtkYfplU1vz8yEo4=
=7swc
-END PGP SIGNATURE End Message ---

Bug#976769: marked as pending in redfishtool

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/third-party/redfishtool/-/commit/83c4225fb2847780634867d33c879d14f52ba08f


Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976769)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976769

Bug#976771: marked as pending in python-semver

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-semver/-/commit/ee6ec21a7654f46a6f466ad656c2bace456344ee


Add dh_python3 --shebang=/usr/bin/python3 (Closes: #976771)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976771

Processed: Bug#976771 marked as pending in python-semver

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976771 [python3-semver] python3-semver needs source upload for Python 3.9 
transition
Added tag(s) pending.

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

Processed: Bug#976769 marked as pending in redfishtool

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976769 [redfishtool] redfishtool needs source upload for Python 3.9 
transition
Added tag(s) pending.

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

Bug#976790: powerline: Missing package relation with python3-i3ipc

[Axel Beckert]

Package: powerline
Version: 2.8.1-3
Severity: serious
File: /usr/share/powerline/bindings/i3/powerline-i3.py

Hi,

using /usr/share/powerline/bindings/i3/powerline-i3.py bails out for me
as follows:

$ python3 /usr/share/powerline/bindings/i3/powerline-i3.py
{"version": 1}
[
[]
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/powerline/bindings/wm/__init__.py", line 
61, in get_i3_connection
import i3ipc
ModuleNotFoundError: No module named 'i3ipc'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/powerline/bindings/i3/powerline-i3.py", line 46, in 
i3 = get_i3_connection()
  File "/usr/lib/python3/dist-packages/powerline/bindings/wm/__init__.py", line 
63, in get_i3_connection
import i3 as conn
ModuleNotFoundError: No module named 'i3'
$

Installing python3-i3ipc fixes this. So please add python3-i3ipc to the
Suggests header (and i3 or i3-wm to the Enhances header).

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

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages powerline depends on:
ii  cdebconf [debconf-2.0]  0.255
ii  debconf [debconf-2.0]   1.5.74
ii  init-system-helpers 1.59
ii  libc6   2.31-5
ii  python3 3.9.0-4
ii  python3-powerline   2.8.1-3

Versions of packages powerline recommends:
ii  fonts-powerline  2.8.1-3

Versions of packages powerline suggests:
ii  powerline-doc  2.8.1-3
pn  vim-addon-manager  

-- debconf information:
* powerline/enable: false
  powerline/title:

Bug#975776: marked as pending in billiard

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #975776 in billiard 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/billiard/-/commit/b055742549e51dcf0bd80014476c0917b52d77bb


Add upstream patch to fix Python 3.9 FTBFS (Closes: #975776).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975776

Processed: Bug#975776 marked as pending in billiard

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#976522: marked as done (golang-gopkg-libgit2-git2go.v28: FTBFS: src/gopkg.in/libgit2/git2go.v28/git_dynamic.go:10:3: error: #error "Invalid libgit2 version; this git2go supports libgit2 v0.28")

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 22:00:09 +
with message-id 
and subject line Bug#976522: fixed in golang-gopkg-libgit2-git2go.v30 30.3.2-1
has caused the Debian Bug report #976522,
regarding golang-gopkg-libgit2-git2go.v28: FTBFS: 
src/gopkg.in/libgit2/git2go.v28/git_dynamic.go:10:3: error: #error "Invalid 
libgit2 version; this git2go supports libgit2 v0.28"
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.)


-- 
976522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gopkg-libgit2-git2go.v28
Version: 0.28.5-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> DC-Build-Header: golang-gopkg-libgit2-git2go.v28 0.28.5-1 / 2020-12-05 
> 01:42:16 +
> DC-Task: type:rebuild-full-arm64 source:golang-gopkg-libgit2-git2go.v28 
> version:0.28.5-1 chroot:unstable esttime:63 
> logfile:/tmp/golang-gopkg-libgit2-git2go.v28_0.28.5-1_unstable.log modes:
> DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source 
> --apt-update -d unstable -v --no-run-lintian 
> golang-gopkg-libgit2-git2go.v28_0.28.5-1'
> sbuild (Debian sbuild) 0.78.1 (09 February 2019) on 
> ip-172-31-3-36.eu-central-1.compute.internal
> 
> +==+
> | golang-gopkg-libgit2-git2go.v28 0.28.5-1 (arm64) Sat, 05 Dec 2020 01:42:16 
> + |
> +==+
> 
> Package: golang-gopkg-libgit2-git2go.v28
> Version: 0.28.5-1
> Source Version: 0.28.5-1
> Distribution: unstable
> Machine Architecture: arm64
> Host Architecture: arm64
> Build Architecture: arm64
> Build Type: full
> 
> I: NOTICE: Log filtering will replace 
> 'var/run/schroot/mount/sid-arm64-sbuild-d348add8-9665-49ef-b0fe-71779951b804' 
> with '<>'
> I: NOTICE: Log filtering will replace 
> 'build/golang-gopkg-libgit2-git2go.v28-s3gBm5/resolver-1iVat2' with 
> '<>'
> 
> +--+
> | Update chroot   
>  |
> +--+
> 
> Get:1 http://127.0.0.1:12990/debian sid InRelease [150 kB]
> Get:2 http://127.0.0.1:12990/debian sid/main Sources.diff/Index [37.0 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main arm64 Packages.diff/Index [37.0 
> kB]
> Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-12-04-2017.12.pdiff 
> [19.3 kB]
> Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-12-04-2017.12.pdiff 
> [19.3 kB]
> Get:5 http://127.0.0.1:12990/debian sid/main arm64 Packages 
> 2020-12-04-2017.12.pdiff [19.0 kB]
> Get:5 http://127.0.0.1:12990/debian sid/main arm64 Packages 
> 2020-12-04-2017.12.pdiff [19.0 kB]
> Fetched 263 kB in 1s (332 kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Calculating upgrade...
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 
> +--+
> | Fetch source files  
>  |
> +--+
> 
> 
> Check APT
> -
> 
> Checking available source versions...
> 
> Download source files with APT
> --
> 
> Reading package lists...
> NOTICE: 'golang-gopkg-libgit2-git2go.v28' packaging is maintained in the 
> 'Git' version control system at:
> https://salsa.debian.org/go-team/packages/golang-gopkg-libgit2-git2go
> Please use:
> git clone 
> https://salsa.debian.org/go-team/packages/golang-gopkg-libgit2-git2go
> to retrieve the latest (possibly unreleased) updates to the package.
> Need to get 81.9 kB of source archives.
> Get:1 http://127.0.0.1:12990/debian sid/main golang-gopkg-libgit2-git2go.v28 
> 0.28.5-1 (dsc) [2442 B]
> Get:2 http://127.0.0.1:12990/debian sid/main golang-gopkg-libgit2-git2go.v28 
> 0.28.5-1 (tar) [75.5 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main golang-gopkg-libgit2-git2go.v28 
> 0.28.5-1 (diff) [3952 B]
> Fetched 81.9 kB in 0s (1060 kB/s)
> Download complete and in download only mode
> I: NOTICE: Log filtering will replace 
> 'build/golang-gopkg-libgit2-git2go.v28-s3gBm5/golang-gopkg-libgit2-git2go.

Bug#976781: rocketcea FTBFS with Python 3.9 only

[Adrian Bunk]

Source: rocketcea
Version: 1.1.18+dfsg-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules execute_after_dh_auto_test
make[1]: Entering directory '/<>'
rm .pybuild/cpython3_3.8_rocketcea/build/separated_Noz.csv
rm: cannot remove '.pybuild/cpython3_3.8_rocketcea/build/separated_Noz.csv': No 
such file or directory
make[1]: *** [debian/rules:10: execute_after_dh_auto_test] Error 1

Bug#976782: python-jpype FTBFS with Python 3.9 only

[Adrian Bunk]

Source: python-jpype
Version: 1.1.2-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_python3
make[1]: Entering directory '/<>'
dh_python3
mv 
/<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar
 /<>/debian/python3-jpype/usr/share/java
mv: cannot stat 
'/<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar':
 No such file or directory
make[1]: *** [debian/rules:13: override_dh_python3] Error 1

Processed: bug 976731 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1677690

[Debian Bug Tracking System]

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

> forwarded 976731 https://bugzilla.mozilla.org/show_bug.cgi?id=1677690
Bug #976731 [src:firefox] firefox: FTBFS on arm64 (explicit specialization in 
non-namespace scope ‘class js::wasm::BaseRegAlloc’)
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1677690'.
> thanks
Stopping processing here.

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

Bug#976780: pycuda needs a manual upload to drop Python 3.8 support

[Adrian Bunk]

Source: pycuda
Version: 2019.1.2-1
Severity: serious

Sources+binaries might be easier than a manual binNMU.

Bug#972645: gnome-builder does not start without flatpak package installed

[Simon McVittie]

Control: severity -1 normal
Control: tags -1 + unreproducible

On Mon, 07 Dec 2020 at 21:01:38 +, Simon McVittie wrote:
> On Wed, 21 Oct 2020 at 18:01:33 +, nodiscc wrote:
> > gnome-builder does not start at all when the flatpak package is not
> > installed, and returns code 255.
> 
> I was unable to reproduce this on either buster or bullseye by removing the
> flatpak package from a fairly complete GNOME installation.

I also can't reproduce this on the following system:

- standard Debian installation (no GUI)
- add xorg, openbox, xdm (with Recommends)
- add gnome-builder (without Recommends)

when starting from either buster or bullseye.

If you create a new user account on the same system (so your home
directory and personal configuration are not in use), can you run
gnome-builder successfully as that user?

> > ptrace: Operation not permitted.
> > No threads.
> > No shared libraries loaded at this time.

I don't see any of those messages, only warnings about the python3-lxml
and python3-jedi packages not being available.

Those look like messages from gdb? I tried installing gdb, but
gnome-builder still launches successfully, and can clone one of the
suggested GNOME projects and edit files.

gnome-builder can't install flatpak-builder without the Recommends, but
degraded functionality is to be expected if you don't install Recommends.

smcv

Processed: Re: Bug#972645: gnome-builder does not start without flatpak package installed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #972645 [gnome-builder] gnome-builder does not start without flatpak 
package installed
Severity set to 'normal' from 'grave'
> tags -1 + unreproducible
Bug #972645 [gnome-builder] gnome-builder does not start without flatpak 
package installed
Added tag(s) unreproducible.

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

Bug#976779: mypy FTBFS with only python 3.9

[Adrian Bunk]

Source: mypy
Version: 0.790-2
Severity: serious
Tags: ftbfs

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

...
#set -e; for v in 3.9; do
set -e; for v in 3.8; do \
PATH=$PATH:/<>/debian/mypy/usr/bin/ python$v -m pytest -n 
auto \
-o testpaths=mypy/test -o python_files=test*.py \
-k "not StubtestMiscUnit" \
-o python_classes= -o python_functions=; \
done
bash: line 2: python3.8: command not found
make[1]: *** [debian/rules:77: override_dh_auto_test] Error 127

Bug#974011: xmille: Incorrect license/copyright for xmille

[Keith Packard]

Adrian Bunk  writes:

> On Sun, Nov 08, 2020 at 07:06:52PM -0500, Ryan Armstrong wrote:
>>...
>> I have been researching old terminal and X games recently, and realized
>> that much of the code from 'xmille' orignated from the terminal game
>> 'mille', which is part of bsdgames.
>> 
>> Specifically, the following files are notably similar between the two
>> games:
>> comp.c
>> end.c
>> extern.c
>> init.c
>> mille.c & mille.h
>> misc.c
>> move.c
>> types.h
>> varpush.c
>> 
>> Many of these even contain telltale BSD version/date comments, even a
>> few not listed above that are common but extensively re-written.
>> However, all of the original source files contain the 3-term BSD
>> license, as follows:
>>...
>> This has been stripped out of all code in the xmille distribution.
>> Also, none of the included materials give credit to the original author,
>> Ken Arnold.
>> 
>> I'm not sure what the best solution is, exactly. Extensively patch the
>> source until it complies with the BSD license again?
>> 
>> Presumably, the copyright file needs to change at the very least.
>>...
>
> Keith, do you remember the copyright history of this code?

I may have copied the underlying mille sources *before* copyrights were
added to each file; I started work on the X10 version of xmille around
1985 or 1986. I guess I could have mistakenly removed them? Thanks for
discovering this error; I can fix these "upstream" and publish a new
version?

-- 
-keith


signature.asc
Description: PGP signature

Bug#976778: fpylll FTBFS: fatal error: fplll/sieve/sieve_gauss.h: No such file or directory

[Adrian Bunk]

Source: fpylll
Version: 0.5.2+ds1-2
Severity: serious
Tags: ftbfs

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

...
build/src/fpylll/fplll/integer_matrix.cpp:729:10: fatal error: 
fplll/sieve/sieve_gauss.h: No such file or directory
  729 | #include "fplll/sieve/sieve_gauss.h"
  |  ^~~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:353: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build --test-pytest -i python{version} -p 3.9 
returned exit code 13
make: *** [debian/rules:11: binary-arch] Error 25

Bug#975415: marked as done (git-revise: autopkgtest failure on armhf & ppc64el showing the package downloads code from internet)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 21:19:02 +
with message-id 
and subject line Bug#975415: fixed in git-revise 0.6.0-2
has caused the Debian Bug report #975415,
regarding git-revise: autopkgtest failure on armhf & ppc64el showing the 
package downloads code from internet
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.)


-- 
975415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-revise
Version: 0.6.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package git-revise, great.
However, it fails on armhf and ppc64el. Currently this failure is
blocking the migration to testing [1]. Can you please investigate the
situation and fix it? (I have manually retriggered the failing runs as
in case they are flaky; new autopkgtests are not automatically retried).

I copied some of the output at the bottom of this report. I noticed that
the test uses pip to download packages from the internet. The
ftp-masters have ruled that this is forbidden:
https://ftp-master.debian.org/REJECT-FAQ.html [Non-Main II].

Paul

[1] https://qa.debian.org/excuses.php?package=git-revise

https://ci.debian.net/data/autopkgtest/testing/armhf/g/git-revise/7988961/log.gz

ERROR: invocation failed (exit code 1), logfile:
/tmp/autopkgtest-lxc.f5o8xggd/downtmp/build.GgD/src/.tox/format/log/format-1.log
== log start
===
Collecting black
  Downloading black-20.8b1.tar.gz (1.1 MB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Collecting click>=7.1.2
  Downloading click-7.1.2-py2.py3-none-any.whl (82 kB)
Collecting regex>=2020.1.8
  Downloading regex-2020.10.28.tar.gz (694 kB)
Collecting typed-ast>=1.4.0
  Using cached typed_ast-1.4.1.tar.gz (208 kB)
Collecting mypy-extensions>=0.4.3
  Using cached mypy_extensions-0.4.3-py2.py3-none-any.whl (4.5 kB)
Collecting toml>=0.10.1
  Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Collecting pathspec<1,>=0.6
  Downloading pathspec-0.8.0-py2.py3-none-any.whl (28 kB)
Collecting appdirs
  Downloading appdirs-1.4.4-py2.py3-none-any.whl (9.6 kB)
Collecting typing-extensions>=3.7.4
  Using cached typing_extensions-3.7.4.3-py3-none-any.whl (22 kB)
Building wheels for collected packages: black, regex, typed-ast
  Building wheel for black (PEP 517): started
  Building wheel for black (PEP 517): finished with status 'done'
  Created wheel for black: filename=black-20.8b1-py3-none-any.whl
size=124186
sha256=9f3176da50d383ad44ceec1128cd60d00cd2b4ee5acd3b67a5bbdbf44f78682a
  Stored in directory:
/home/debci/.cache/pip/wheels/95/a4/59/10cd5378d52f92cdb45025f040e4686e10ae5217961c25fd66
  Building wheel for regex (setup.py): started
  Building wheel for regex (setup.py): finished with status 'error'
  ERROR: Command errored out with exit status 1:





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: git-revise
Source-Version: 0.6.0-2
Done: Nicolas Schier 

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

Debian distribution maintenance software
pp.
Nicolas Schier  (supplier of updated git-revise package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Dec 2020 15:15:05 +0100
Source: git-revise
Architecture: source
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Schier 
Changed-By: Nicolas Schier 
Closes: 975415
Changes:
 git-revise (0.6.0-2) unstable; urgency=medium
 .
   * debian/tests: switch from tox to pytest (Closes: #975415)
Checksums-Sha1:
 32e626f475758f0389745581ec3e6c5a3d559ef7 2015 git-revise_0.6.0-2.dsc

Bug#976218: [Pkg-nagios-devel] Bug#976218: nagios-plugins-contrib: diff for NMU version 27.20200511+1+nmu1

[Christoph Biedl]

Jan Wagner wrote...

> Hi Chirstoph,
>
> thanks for taking care.

You're welcome.

> 1.124.0 is already integrated into VCS
> (https://salsa.debian.org/nagios-team/pkg-nagios-plugins-contrib/-/commit/6827b67108fcaafb5c73de8d7b44d71b2a7e6cf3),
> so you can delay this a bit more. Actually I'm working hard to get the
> latest VCS into unstable but I have to work on some other issues as well.

Okay, I've removed the upload from the queue as I really like to avoid
disrupting the maintainers' workflow by doing a NMU. However, I'd
appreciate if you could deal with this pretty soon as it is delaying the
testing migration of a fairly important package. Perhaps upload a new
check-ssl only and keep the rest for a later one?

Christoph, as well with a long list of chores


signature.asc
Description: PGP signature

Bug#972645: gnome-builder does not start without flatpak package installed

[Simon McVittie]

On Wed, 21 Oct 2020 at 18:01:33 +, nodiscc wrote:
> gnome-builder does not start at all when the flatpak package is not
> installed, and returns code 255.

I was unable to reproduce this on either buster or bullseye by removing the
flatpak package from a fairly complete GNOME installation.

This might mean that gnome-builder has an undeclared dependency on
something else that is depended on by flatpak.

(gnome-builder does correctly have an indirect Recommends on Flatpak,
because its design encourages a Flatpak-based workflow.)

smcv

Bug#972623: marked as done (Security fixes from the October 2020 CPU)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 20:53:29 +
with message-id 
and subject line Bug#972623: fixed in mysql-8.0 8.0.22-1
has caused the Debian Bug report #972623,
regarding Security fixes from the October 2020 CPU
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.)


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

Source: mysql-8.0
Version: 8.0.21
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2020 lists CVEs affecting 
MySQL 8.0

that are fixed in 8.0.22

CVE list:

    - CVE-2020-14672 CVE-2020-14765 CVE-2020-14769 CVE-2020-14771
    - CVE-2020-14773 CVE-2020-14775 CVE-2020-14776 CVE-2020-14777
    - CVE-2020-14785 CVE-2020-14786 CVE-2020-14789 CVE-2020-14790
    - CVE-2020-14791 CVE-2020-14793 CVE-2020-14794 CVE-2020-14799
    - CVE-2020-14800 CVE-2020-14804 CVE-2020-14809 CVE-2020-14812
    - CVE-2020-14814 CVE-2020-14821 CVE-2020-14827 CVE-2020-14828
    - CVE-2020-14829 CVE-2020-14830 CVE-2020-14836 CVE-2020-14837
    - CVE-2020-14838 CVE-2020-14839 CVE-2020-14844 CVE-2020-14845
    - CVE-2020-14846 CVE-2020-14848 CVE-2020-14852 CVE-2020-14860
    - CVE-2020-14861 CVE-2020-14866 CVE-2020-14867 CVE-2020-14868
    - CVE-2020-14869 CVE-2020-14870 CVE-2020-14873 CVE-2020-14878
    - CVE-2020-14888 CVE-2020-14891 CVE-2020-14893

Ref: https://www.oracle.com/security-alerts/cpuoct2020.html#AppendixMSQL

Regards,

Lars Tangvald
--- End Message ---
--- Begin Message ---
Source: mysql-8.0
Source-Version: 8.0.22-1
Done: Lars Tangvald 

We believe that the bug you reported is fixed in the latest version of
mysql-8.0, 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.
Lars Tangvald  (supplier of updated mysql-8.0 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, 20 Oct 2020 09:37:54 +
Source: mysql-8.0
Architecture: source
Version: 8.0.22-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Lars Tangvald 
Closes: 972623
Launchpad-Bugs-Fixed: 1882527
Changes:
 mysql-8.0 (8.0.22-1) unstable; urgency=medium
 .
   * Imported upstream version 8.0.22 to fix security issues:
 - https://www.oracle.com/security-alerts/cpuoct2020.html#AppendixMSQL
 - CVE-2020-14672 CVE-2020-14765 CVE-2020-14769 CVE-2020-14771
 - CVE-2020-14773 CVE-2020-14775 CVE-2020-14776 CVE-2020-14777
 - CVE-2020-14785 CVE-2020-14786 CVE-2020-14789 CVE-2020-14790
 - CVE-2020-14791 CVE-2020-14793 CVE-2020-14794 CVE-2020-14799
 - CVE-2020-14800 CVE-2020-14804 CVE-2020-14809 CVE-2020-14812
 - CVE-2020-14814 CVE-2020-14821 CVE-2020-14827 CVE-2020-14828
 - CVE-2020-14829 CVE-2020-14830 CVE-2020-14836 CVE-2020-14837
 - CVE-2020-14838 CVE-2020-14839 CVE-2020-14844 CVE-2020-14845
 - CVE-2020-14846 CVE-2020-14848 CVE-2020-14852 CVE-2020-14860
 - CVE-2020-14861 CVE-2020-14866 CVE-2020-14867 CVE-2020-14868
 - CVE-2020-14869 CVE-2020-14870 CVE-2020-14873 CVE-2020-14878
 - CVE-2020-14888 CVE-2020-14891 CVE-2020-14893
 (Closes: #972623)
   * d/patches: Dropped patches for issues fixed upstream
 fix_expired_test_certs.patch and fix_mariadb_charset_segfault.patch
   * d/rules: Link system libs by default
 Ensures that if new dependencies are added we use system instead
 of bundled versions, where possible.
   * d/install: Added new upstream plugins for MySQL Router
   * d/systemd: Disable service timeout
 For large databases, the service could timeout on stop, possibly
 leading to data corruption during a system shutdown.
 (LP: #1882527)
Checksums-Sha1:
 9a1534d840cb8c031cb8b1e675ac43d0ee93c693 3646 mysql-8.0_8.0.22-1.dsc
 0bf6f95fa5cf925e9cee1edab765c694cb7571bd 285934450 mysql-8.0_8.0.22.orig.tar.gz
 310b6d873b72520e647521218ada95e8ab1e5339 232 mysql-8.0_8.0.22.orig.tar.gz.asc
 37bfc4199cbd383a9b67b8c528dab64b6934e28a 157412 
mysql-8.0_8.0.22-1.debian.tar.xz
 8f96fc06cf12186dffbd90c43e2ad261cfd7c068 9510 
mysql-8.0_8.0.22-1_source.buildinfo
Checksums-Sha256:
 0a41

Bug#976774: python3-fparser needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-fparser
Version: 0.0.11-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/fparser2 have to use
the versioned interpreter instead of python3?

Bug#976773: pympress needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: pympress
Version: 1.5.1+dfsg-4
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/pympress have to use
the versioned interpreter instead of python3?

Bug#976772: python3-calmjs needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-calmjs
Version: 3.4.1-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/calmjs have to use
the versioned interpreter instead of python3?

Bug#976770: ranger needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: ranger
Version: 1.9.3-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, do the binaries have to use
the versioned interpreter instead of python3?
Fixing #975451 would be the best solution.

Bug#976624: marked as done (python3-xcbgen: not compatible with python 3.9)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 20:32:09 +
with message-id 
and subject line Bug#976624: fixed in xcb-proto 1.14.1-1
has caused the Debian Bug report #976624,
regarding python3-xcbgen: not compatible with python 3.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.)


-- 
976624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xcb-proto
Severity: serious
Tags: patch upstream

Hello Maintainer,

Python 3.9 deprecated fractions.gcd in favor of math.gcd, this causes a
FTBFS in polybar #975795[0]. I believe this issue can cause FTBFS in other
packages and thus I picked the serious severity (same one applied to the
polybar bug report caused by this).

I have tried to find the correct place to send patches upstream and gave up
along the way when I couldn't find the project on freedesktop's gitlab
instance[1] and the homepage pointed to an empty bugzilla (which I assume
is not used anymore).

I proposed a solution on salsa[2], which I'm also attaching to this email.

I'm also willing to NMU the fix in case the maintainers don't have
available time.

Thanks,

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975795
[1] https://gitlab.freedesktop.org
[2] https://salsa.debian.org/xorg-team/proto/xcb-proto/-/merge_requests/2

-- 
Samuel Henrique 
From 0cb3fba7b33aae669d47ea5f30a5a2bc5f21e465 Mon Sep 17 00:00:00 2001
From: Samuel Henrique 
Date: Sat, 5 Dec 2020 20:07:58 +
Subject: [PATCH] d/p/python39-compat.patch: Add patch for python 3.9
 compatibility

---
 debian/patches/python39-compat.patch | 21 +
 debian/patches/series|  1 +
 2 files changed, 22 insertions(+)
 create mode 100644 debian/patches/python39-compat.patch
 create mode 100644 debian/patches/series

diff --git a/debian/patches/python39-compat.patch b/debian/patches/python39-compat.patch
new file mode 100644
index 000..924ed40
--- /dev/null
+++ b/debian/patches/python39-compat.patch
@@ -0,0 +1,21 @@
+Description: Fix import of deprecated fractions.gcd function (for python >= 3.9)
+Author: Samuel Henrique 
+Index: xcb-proto/xcbgen/align.py
+===
+--- xcb-proto.orig/xcbgen/align.py
 xcb-proto/xcbgen/align.py
+@@ -2,7 +2,13 @@
+ This module contains helper classes for alignment arithmetic and checks
+ '''
+ 
+-from fractions import gcd
++# python >= 3.9 compatibility
++# fractions.gcd is deprecated since python 3.9
++# math.gcd is available since python 3.5
++try:
++from fractions import gcd
++except ImportError:
++from math import gcd
+ 
+ class Alignment(object):
+ 
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..5703b40
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+python39-compat.patch
-- 
2.29.2

--- End Message ---
--- Begin Message ---
Source: xcb-proto
Source-Version: 1.14.1-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated xcb-proto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Dec 2020 22:01:27 +0200
Source: xcb-proto
Architecture: source
Version: 1.14.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 976624
Changes:
 xcb-proto (1.14.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #976624)
   * watch: Updated.
Checksums-Sha1:
 359f1a6a05c4b8f6ebb7d5194fb37452186a8a89 1988 xcb-proto_1.14.1-1.dsc
 1bb307b09c25c42058cc36e565a29ec86d7a4b91 194674 xcb-proto_1.14.1.orig.tar.gz
 55a62241a89e84613935f4d06f3515ccd5a06a81 4846 xcb-proto_1.14.1-1.diff.gz
 d9fbfad649fc257848ccb452ac147e4bd3f29baf 7572 
xcb-proto_1.14.1-1_source.buildinfo
Checksums-Sha256:
 a03c91002643ef867c52511d51f4cfb7d1fe139aa614574c020b8bb329c2f50b 1988 
xcb-proto_1.14.1-1.dsc
 85cd21e9d9fbc341d0dbf11eace98d55d7db89fda724b0e598855fcddf0944fd 194674 

Bug#976771: python3-semver needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-semver
Version: 2.10.2-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/pysemver have to use
the versioned interpreter instead of python3?

Bug#976769: redfishtool needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: redfishtool
Version: 1.1.0-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/redfishtool have to use
the versioned interpreter instead of python3?

Bug#976767: python3-mako needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-mako
Version: 1.1.3+ds1-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/mako-render have to use
the versioned interpreter instead of python3?

Bug#976766: python3-cyborgclient needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-cyborgclient
Version: 1.2.1-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/cyborg have to use
the versioned interpreter instead of python3?

Bug#976764: geophar needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: geophar
Version: 18.08.6+dfsg1-5
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

Bug#976765: python3-sushy-cli needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-sushy-cli
Version: 0.3.1-2
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/sushycli have to use
the versioned interpreter instead of python3?

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

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 20:21:23 +
with message-id 
and subject line Bug#976569: fixed in c-blosc 1.20.1+ds1-2
has caused the Debian Bug report #976569,
regarding numcodecs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.8 3.9" returned exit code 13
to be marked as done.

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

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


-- 
976569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numcodecs
Version: 0.7.2+ds-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3.8 setup.py build 
> [numcodecs] setting up Blosc extension
> [numcodecs] compiling Blosc extension without SSE2 support
> [numcodecs] compiling Blosc extension without AVX2 support
> [numcodecs] setting up Zstandard extension
> [numcodecs] setting up LZ4 extension
> [numcodecs] setting up compat extension
> [numcodecs] setting up vlen extension
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/astype.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/bz2.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/lzma.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/msgpacks.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/base64.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/version.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/json.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/categorize.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/fixedscaleoffset.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/abc.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/pickles.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/quantize.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/packbits.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/registry.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/checksum32.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/delta.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/gzip.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/compat.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> copying ./numcodecs/zlib.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs
> creating 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_vlen_utf8.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_zstd.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_fixedscaleoffset.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_categorize.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_compat.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_lz4.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_quantize.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_gzip.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_registry.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_bz2.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_pickles.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_vlen_array.py -> 
> /<>/.pybuild/cpython3_3.8_numcodecs/build/numcodecs/tests
> copying ./numcodecs/tests/test_lzma.py -> 
> /<>/.pybuild/cpython3_3.8_numc

Bug#938795: vmtk does not build any more

[Drew Parsons]

On 2020-12-08 04:07, Andreas Tille wrote:

Hi,

vmtk is using Python3 in Git[1], but there are build issues with vtk7:



First thing to try would be building against vtk9, which Anton recently 
released for us.


Upstream authors in other packages have commented that vtk7 is quite 
old. Builds might be more reliable with vtk9, although it does have 
issues with the 32-bit systems.


Drew

Bug#976762: python3-os-collect-config needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: python3-os-collect-config
Version: 11.0.0-1
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/os-collect-config have to use
the versioned interpreter instead of python3?

Bug#938795: vmtk does not build any more

[Andreas Tille]

Hi,

vmtk is using Python3 in Git[1], but there are build issues with vtk7:

...
cd /build/vmtk-1.4.0+dfsg/obj-x86_64-linux-gnu/vtkVmtk/ComputationalGeometry && 
/usr/bin/c++ -DITK_IO_FACTORY_REGISTER_MANAGER 
-DvtkvmtkComputationalGeometry_EXPORTS -I/build/vmtk-1.4.0+   
dfsg/obj-x86_64-linux-gnu/ITKFactoryRegistration -I/usr/include/hdf5/serial 
-I/usr/include/nifti -I/usr/include/gdcm-3.0 -I/usr/include/ITK-4.13 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk -I/build/  vmtk-1.4.0+dfsg/vtkVmtk/Common 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk/ComputationalGeometry 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk/DifferentialGeometry 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk/IO -I/build/vmtk-1.4.0+dfsg/vtkVmtk/Misc 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk/Segmentation 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk/Contrib 
-I/build/vmtk-1.4.0+dfsg/vtkVmtk/Utilities/vtkvmtkITK -I/build/vmtk-1.4. 
0+dfsg/obj-x86_64-linux-gnu/vtkVmtk -I/usr/include/vtk-7.1 
-I/usr/include/python3.9 -g -O2 -fdebug-prefix-map=/build/vmtk-1.4.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format- security -Wdate-time 
-D_FORTIFY_SOURCE=2   -O2 -g -DNDEBUG -fPIC -fPIC -o 
CMakeFiles/vtkvmtkComputationalGeometry.dir/vtkvmtkCenterlineBranchExtractor.cxx.o
 -c /build/vmtk-1.4.0+dfsg/  
vtkVmtk/ComputationalGeometry/vtkvmtkCenterlineBranchExtractor.cxx
In file included from 
/build/vmtk-1.4.0+dfsg/vtkVmtk/ComputationalGeometry/vtkvmtkCenterlineBranchExtractor.cxx:24:
/build/vmtk-1.4.0+dfsg/vtkVmtk/ComputationalGeometry/vtkvmtkPolyBallLine.h:45:10:
 error: 'double vtkvmtkPolyBallLine::EvaluateFunction(double, double, double)' 
marked 'override', but does  not override
   45 |   double EvaluateFunction(double x, double y, double z) VTK_OVERRIDE
  |  ^~~~
[  4%] Building CXX object 
vtkVmtk/IO/CMakeFiles/vtkvmtkIO.dir/vtkvmtkXdaReader.cxx.o


Any help is welcome.

Kind regards

   Andreas.

[1] https://salsa.debian.org/science-team/vmtk

-- 
http://fam-tille.de

Bug#976761: drop-seq: autopkgtest regression on armhf and i386: Invalid maximum heap size: -Xmx16384m

[Paul Gevers]

Source: drop-seq
Version: 2.4.0+dfsg-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of drop-seq the autopkgtest fails on armhf and i386
in testing when that autopkgtest is run with the binary packages of
drop-seq from unstable. It passes (well, it's skipped) when run with
only packages from testing. In tabular form:

   passfail
drop-seq   from testing2.4.0+dfsg-3
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/d/drop-seq/8688759/log.gz

autopkgtest [10:24:35]: test run-unit-test: [---
Test 1
Invalid maximum heap size: -Xmx16384m
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
autopkgtest [10:24:36]: test run-unit-test: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976624: python3-xcbgen: not compatible with python 3.9

[Samuel Henrique]

Hello Timo,

Hi, upstream is at https://gitlab.freedesktop.org/xorg/proto/xcbproto


Oh no, I was searching for "xcb-proto" trusting it would find it if it was
there :(
Thank you for pointing out the correct place, it might be handy in the
future.


> and this issue is fixed in the latest release, so I'll just release that.
>

Awesome, thank you!

Regards,


-- 
Samuel Henrique 

Bug#976624: python3-xcbgen: not compatible with python 3.9

[Timo Aaltonen]

On 6.12.2020 3.49, Samuel Henrique wrote:

Package: xcb-proto
Severity: serious
Tags: patch upstream

Hello Maintainer,

Python 3.9 deprecated fractions.gcd in favor of math.gcd, this causes a 
FTBFS in polybar #975795[0]. I believe this issue can cause FTBFS in 
other packages and thus I picked the serious severity (same one applied 
to the polybar bug report caused by this).


I have tried to find the correct place to send patches upstream and gave 
up along the way when I couldn't find the project on freedesktop's 
gitlab instance[1] and the homepage pointed to an empty bugzilla (which 
I assume is not used anymore).


I proposed a solution on salsa[2], which I'm also attaching to this email.

I'm also willing to NMU the fix in case the maintainers don't have 
available time.


Thanks,

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975795 


[1] https://gitlab.freedesktop.org 
[2] 
https://salsa.debian.org/xorg-team/proto/xcb-proto/-/merge_requests/2 



--
Samuel Henrique 


Hi, upstream is at https://gitlab.freedesktop.org/xorg/proto/xcbproto

and this issue is fixed in the latest release, so I'll just release that.


--
t

Processed: Re: Bug#975470: python-meshplex: autopkgtest regression on 32 bit archs: TypeError: Cannot cast array data from dtype('int64') to dtype('int32') according to the rule 'safe'

[Debian Bug Tracking System]

Processing control commands:

> reopen 975470
Bug #975470 {Done: Drew Parsons } [src:python-meshplex] 
python-meshplex: autopkgtest regression on 32 bit archs: TypeError: Cannot cast 
array data from dtype('int64') to dtype('int32') according to the rule 'safe'
Bug reopened
Ignoring request to alter fixed versions of bug #975470 to the same values 
previously set
> notfound 975470 0.15.3-2
Bug #975470 [src:python-meshplex] python-meshplex: autopkgtest regression on 32 
bit archs: TypeError: Cannot cast array data from dtype('int64') to 
dtype('int32') according to the rule 'safe'
Ignoring request to alter found versions of bug #975470 to the same values 
previously set
> found 975470 0.15.4-1
Bug #975470 [src:python-meshplex] python-meshplex: autopkgtest regression on 32 
bit archs: TypeError: Cannot cast array data from dtype('int64') to 
dtype('int32') according to the rule 'safe'
Marked as found in versions python-meshplex/0.15.4-1.

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

Bug#975470: python-meshplex: autopkgtest regression on 32 bit archs: TypeError: Cannot cast array data from dtype('int64') to dtype('int32') according to the rule 'safe'

[Paul Gevers]

Control: reopen 975470
Control: notfound 975470 0.15.3-2
Control: found 975470 0.15.4-1

Hi Drew,

On Mon, 23 Nov 2020 21:04:55 +0800 Drew Parsons  wrote:
> Control: fixed 975470 0.15.3-2

^^^ is processed when sent to -done, that expects a "Version:
<>" there. However, version 0.15.4-1 fails again on i386.

> Patched in 0.15.3-2 to run tests with int32 instead of int64 on 32-bit 
> systems.

https://ci.debian.net/data/autopkgtest/testing/i386/p/python-meshplex/8703677/log.gz

E   TypeError: Cannot cast array data from dtype('uint32') to
dtype('int32') according to the rule 'safe'

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#975929: marked as done (python-logfury: autopkgtest tries to use pip to download and install code from the internet)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 19:33:36 +
with message-id 
and subject line Bug#975929: fixed in check-manifest 0.45-2
has caused the Debian Bug report #975929,
regarding python-logfury: autopkgtest tries to use pip to download and install 
code from the internet
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.)


-- 
975929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-logfury
Version: 0.1.2-4
Severity: serious
Justification: ftp-master autoreject ruling

Hi,

Your package has an autopkgtest, awesome. However, I noticed that it
tries to install Python code using pip. Running downloaded code from
internet is not allowed in the Debian archive; see the ftp-masters
autoreject list [1], so this must be prevented. Note that the download
is only tried with the latest upload of check-manifest, so this seems to
be a fallback mechanism which should be turned off.

Downloading data seems to be allowed, but please add a needs-internet
restriction in that case.

Your autopkgtest seems to need an update for check-manifest, that's how
I discovered this issue. If this is an issue with check-manifest, please
clone this issue and reassign one of the two.

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-logfury/8443183/log.gz

autopkgtest [11:55:16]: test command1: [---
[*] testing on python3.8:
running nosetests
running egg_info
creating src/logfury.egg-info
writing src/logfury.egg-info/PKG-INFO
writing dependency_links to src/logfury.egg-info/dependency_links.txt
writing requirements to src/logfury.egg-info/requires.txt
writing top-level names to src/logfury.egg-info/top_level.txt
writing manifest file 'src/logfury.egg-info/SOURCES.txt'
reading manifest file 'src/logfury.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'src/logfury.egg-info/SOURCES.txt'
WARNING: The pip package is not available, falling back to EasyInstall
for handling setup_requires/test_requires; this is deprecated and will
be removed in a future version.
Searching for build>=0.1
Reading https://pypi.org/simple/build/
Download error on https://pypi.org/simple/build/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1124) -- Some packages may not be found!
Couldn't find index page for 'build' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.org/simple/
Download error on https://pypi.org/simple/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1124) -- Some packages may not be found!
No local packages or working download links found for build>=0.1
error: Could not find suitable distribution for
Requirement.parse('build>=0.1')
autopkgtest [11:55:17]: test command1: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: check-manifest
Source-Version: 0.45-2
Done: Sergio Durigan Junior 

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

Debian distribution maintenance software
pp.
Sergio Durigan Junior  (supplier of updated check-manifest 
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, 06 Dec 2020 18:12:47 -0500
Source: check-manifest
Architecture: source
Version: 0.45-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sergio Durigan Junior 
Closes: 975929
Changes:
 check-manifest (0.45-2) unstable; urgency=medium
 .
   * d/control: Add python3-build as a B-D. (Closes: #975929)
   * d/control: Bump Standards-Version to 4.5.1.
Checksums-Sha1:
 93a4274a86573deeadafa5f7775787ba3a05e34e 2381 check-manifest_0.45-2.dsc
 4fc8f5938eabaeffc9af689e1e009473d27c9316 5080 
check-manifest_0.45-2.debian.tar.xz
 facf100ba6a3c2076190504f616a7687ffcd818b 7835 
check-manifest_0.45-2_

Bug#975929: Bug in check-manifest, reassigning

[Paul Gevers]

Dear Ondrej,

On Mon, 30 Nov 2020 08:59:11 +0100 Ondrej Novy  wrote:
> check-manifest have in setup.py:
> install_requires=[
> 'build>=0.1',
> 
> and doesn't have python3-build (which is not in archive) in B-D. Thus
> reassigning to check-manifest.

Am I correct in saying that this will *not* prevent future
python-logfury autopkgtests from ever using pip? Obviously, this solves
the current problem, but unless you say to the answer "no, you're not
correct", python-logfury needs to prevent pip from running at all times
during its autopkgtest.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976559: python-x2go: FTBFS: NameError: name 'AF_INET' is not defined

[Mike Gabriel]

Control: reassign -1 src:python-gevent
Control: forcemerge #975782 -1

Hi Lucas,

On  Sa 05 Dez 2020 21:07:34 CET, Lucas Nussbaum wrote:


On 05/12/20 at 13:49 +0100, Lucas Nussbaum wrote:

Source: python-x2go
Version: 0.6.1.3-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).


It also fails on amd64. You can find a build log in
http://qa-logs.debian.net/2020/12/05/amd64/

Lucas


This is a duplicate of #975782. Please retry by building  
src:python-x2go against python3-gevent 20.9.0-0.1 (just uploaded to  
unstable by doko).


Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpcUYDPOzUFW.pgp
Description: Digitale PGP-Signatur

Bug#975929: marked as pending in check-manifest

[Sergio Durigan Junior]

Control: tag -1 pending

Hello,

Bug #975929 in check-manifest 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/check-manifest/-/commit/5ac87a48352f3255f6c6777bc8bf5c3332d025ec


d/control: Add python3-build as a B-D.

Closes: #975929


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975929

Processed: Bug#975929 marked as pending in check-manifest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975929 [check-manifest] python-logfury: autopkgtest tries to use pip to 
download and install code from the internet
Added tag(s) pending.

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

Bug#976325: [ans...@debian.org: Bug#976325: src:libgdf: invalid maintainer address]

[Rafael Laboissière]

* Yaroslav Halchenko  [2020-12-07 11:06]:


mail server is back online so we are back to enjoying all the mail ;-)


Thanks !

Rafael

Bug#976218: marked as done (nagios-plugins-contrib needs update of check_ssl_cert)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 18:22:09 +
with message-id 
and subject line Bug#976218: fixed in nagios-plugins-contrib 28.20201207
has caused the Debian Bug report #976218,
regarding nagios-plugins-contrib needs update of check_ssl_cert
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.)


-- 
976218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: file, nagios-plugins-contrib
Control: found -1 file/1:5.39-3
Control: found -1 nagios-plugins-contrib/27.20200511+1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
file   from testing1:5.39-3
nagios-plugins-contrib from testing27.20200511+1
all others from testingfrom testing

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

Currently this regression is blocking the migration of file to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

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

Paul

[1] https://qa.debian.org/excuses.php?package=file

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/8542183/log.gz

autopkgtest [14:13:17]: test command7:
/usr/lib/nagios/plugins/check_ssl_cert -H www.debian.org
autopkgtest [14:13:17]: test command7: [---
SSL_CERT UNKNOWN www.debian.org: Unable to fetch a valid certificate
issuer certificate.
autopkgtest [14:13:18]: test command7: ---]



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nagios-plugins-contrib
Source-Version: 28.20201207
Done: Jan Wagner 

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

Debian distribution maintenance software
pp.
Jan Wagner  (supplier of updated nagios-plugins-contrib 
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, 07 Dec 2020 17:40:28 +0100
Source: nagios-plugins-contrib
Architecture: source
Version: 28.20201207
Distribution: unstable
Urgency: high
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Jan Wagner 
Closes: 821207 855416 861814 865021 878233 955378 960923 976218
Changes:
 nagios-plugins-contrib (28.20201207) unstable; urgency=high
 .
   [ Jan Wagner ]
   * [d42a7cb] Update check_multipath to 0.4.8
   * [f4bc15c] Update check_rbl to 1.5.3
   * [e9aaf9b] Update check_ssl_cert to 1.109.0
   * [4a7c176] Removing dnsbl.inps.de from d/patches/check_rbl/additional_rbls
   * [8c8a770] Update check_ssl_cert to 1.113.0
   * [713e713] Update check_zone_auth to 1.14
   * [3a81549] Update check-multipath to 0.4.9
   * [f268738] Update check_rbl to 1.5.4
   * [1b75778] Update check_ssl_cert to 1.118.0
   * [7474d54] Update check_ssl_cert to 1.120.0 (Closes: #976218)
   * [e391368] Adding d/p/check_raid/sort_megacli_numerical
   * [9c92bb0] Adding d/p/check_raid/hpacucli_cache_fail
   * [1e9f7cc] Adding d/p/check_raid/fix_unparsed_error_cciss
   * [2569d5b] check_ssl_cert: Update to 1.122.0
 .
   [ Bas Couwenberg ]
   * [da04a15] Update gbp.conf to use --source-only-changes by default.
 .
   [ Jan Wagner ]
   * [ddaed0a] Update check-cert-expire, check-entropy and check-running-kernel
 from upstream
   * [ad756f4] Remove obsolete patch d/p/dsa/python2to3
   * [5965683] Adding '-maxdepth 1' to
 d/p/dsa/check_running_kernel_jessie_centos_fix. (Closes: #878233, #855416),
 Thanks Felix Geyer
   * [a28a09b] d/c

Processed: forcibly merging 925818 975848

[Debian Bug Tracking System]

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

> forcemerge 925818 975848
Bug #925818 {Done: Laszlo Boszormenyi (GCS) } [src:rocksdb] 
rocksdb: ftbfs with GCC-9
Bug #925818 {Done: Laszlo Boszormenyi (GCS) } [src:rocksdb] 
rocksdb: ftbfs with GCC-9
Added tag(s) ftbfs.
Bug #975848 [src:rocksdb] rocksdb: FTBFS: ./db/version_edit.h:178:33: error: 
implicitly-declared ‘constexpr rocksdb::FileDescriptor::FileDescriptor(const 
rocksdb::FileDescriptor&)’ is deprecated [-Werror=deprecated-copy]
Marked Bug as done
Marked as fixed in versions rocksdb/6.1.2-1.
Merged 925818 975848
> thanks
Stopping processing here.

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

Bug#976641: marked as done (icu's autopkg tests fail)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 17:49:21 +
with message-id 
and subject line Bug#976641: fixed in icu 67.1-5
has caused the Debian Bug report #976641,
regarding icu's autopkg tests fail
to be marked as done.

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

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


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

icu's autopkg tests fail both in testing and unstable:

autopkgtest [11:26:11]: test smoke: [---
+ uconv -f utf8 -t latin1 /etc/hostname
ci-341-76ae504c+ icu-config --unicode-version
/tmp/autopkgtest-lxc.60n88ynl/downtmp/build.EAD/src/debian/tests/smoke: 8:
icu-config: not found
autopkgtest [11:26:11]: test smoke: ---]
autopkgtest [11:26:11]: test smoke:  - - - - - - - - - - results - - - - - - - 
- - -
smokeFAIL non-zero exit status 127

[...]

autopkgtest [11:26:50]: test build-test: [---
g++  debian/tests/ustring.cpp -licuio -licui18n -licuuc -licudata
make: g++: No such file or directory
make: ***
[/tmp/autopkgtest-lxc.60n88ynl/downtmp/build.EAD/src/debian/tests/build-test:7:
a.out] Error 127
autopkgtest [11:26:51]: test build-test: ---]
--- End Message ---
--- Begin Message ---
Source: icu
Source-Version: 67.1-5
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated icu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Dec 2020 15:57:21 +0100
Source: icu
Architecture: source
Version: 67.1-5
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 973279 976641
Changes:
 icu (67.1-5) unstable; urgency=medium
 .
   * Fix autopkg tests (closes: #973279, #976641).
Checksums-Sha1:
 5f1697b4f69779e5881217571f782cec80b18139 2236 icu_67.1-5.dsc
 bd0a9dcd50e916c2a5c1b9ed61de153605e52c4a 29712 icu_67.1-5.debian.tar.xz
Checksums-Sha256:
 9f8a9fb50b17b38e93c1b851a4e37742d9fa698045bc93881dbd0c98710450e0 2236 
icu_67.1-5.dsc
 92181fec8ce8bf2d8454446578afa8540d32ed19d2c9f0c95919fea5578ba29d 29712 
icu_67.1-5.debian.tar.xz
Files:
 30e30bb96b4f3d3d4764d722006b 2236 libs optional icu_67.1-5.dsc
 b3642edc41f743e3d1fc49c47fabb6f7 29712 libs optional icu_67.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl/OZuUACgkQ3OMQ54ZM
yL/lXRAArJQj8s258/PV3EJjgSLCS/eUavXpuIHJJbcCeEqNYtEt5DIK88s5WdHC
FKn3vB6fCsY6SqnKyTw+weCbd8vXJlcFnToOs4UatLTHLALs7gUwJFx0KhAPOT9F
BfooNSm+pFE1LStPAMfgzCEVYAsbjZb52DKs1dfgse9bgKgqKmBxrtvaaAtoPf5D
RZgMR/EYM20f4/Y9OVFHxUirASKej3WNgzRunXI+Rly2Ew0L/jtr77VtuDXE4Bqy
fWhaQoM+RT6QP1VC4fOtIBIkdQsFZa8H4t5ub4+UBQ0OiXiJwaGrgrvdPVSRgnsF
lo9fk+Gm/ZhZxN/WxR8FbYkrq8Ec9QbWQLp+fOMu47YLbrQ8JAUp/n3vKl7tKF6P
X028l0JEFoxTgeC+7tuprYJEsDOBWU3hrJkzpClVNc7eZ4CznGb4IvdNDMbOuBcm
IEEfrSZ7v47uyxJ2xHepdFgfYiJ/zVg347GwUPuCjgUQ3bZjBdn7XPa0/qqgMKpM
JOFj//v6WJhHCKfPe6ytWfK7TEXnf8lJdkV8qMfkq7Zj0q+VM4roCM1SK8WGTrUl
ib0udiRKUww43FQrGFOpBdCFCrSWtvbZNWXFlFOhWMKzdAVfYIFUMpGijRxosIib
Ftftxa6KIoULtoNJEiSdajcoV8WLcDsH73xIitqIc2r8wakA2fs=
=zMVO
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package src:ufonormalizer

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ufonormalizer
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #973167 (http://bugs.debian.org/973167)
> # Bug title: ufonormalizer: FTBFS: dh_auto_test: error: pybuild --test -i 
> python{version} -p "3.9 3.8" returned exit code 13
> #  * https://github.com/unified-font-object/ufoNormalizer/issues/73
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 973167 + fixed-upstream
Bug #973167 [src:ufonormalizer] ufonormalizer: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) fixed-upstream.
> usertags 973167 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 973167 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#976756: mia: binary-all FTBFS

[Adrian Bunk]

Source: mia
Version: 2.4.7-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=mia&arch=all&ver=2.4.7-3&stamp=1607360001&raw=0

...
CMake Error at mia/3d/cmake_install.cmake:110 (file):
  file INSTALL cannot find
  "/<>/obj-x86_64-linux-gnu/mia/3d/libmia3dtest-2.4.so.6.0.1":
  No such file or directory.
Call Stack (most recent call first):
  mia/cmake_install.cmake:65 (include)
  cmake_install.cmake:130 (include)


make[1]: *** [Makefile:96: install] Error 1

Processed: affects 973821

[Debian Bug Tracking System]

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

> affects 973821 src:cfgrib
Bug #973821 [python3-pandas] cfgrib: FTBFS: tests failed
Added indication that 973821 affects src:cfgrib
> thanks
Stopping processing here.

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

Bug#974011: xmille: Incorrect license/copyright for xmille

[Adrian Bunk]

On Sun, Nov 08, 2020 at 07:06:52PM -0500, Ryan Armstrong wrote:
>...
> I have been researching old terminal and X games recently, and realized
> that much of the code from 'xmille' orignated from the terminal game
> 'mille', which is part of bsdgames.
> 
> Specifically, the following files are notably similar between the two
> games:
> comp.c
> end.c
> extern.c
> init.c
> mille.c & mille.h
> misc.c
> move.c
> types.h
> varpush.c
> 
> Many of these even contain telltale BSD version/date comments, even a
> few not listed above that are common but extensively re-written.
> However, all of the original source files contain the 3-term BSD
> license, as follows:
>...
> This has been stripped out of all code in the xmille distribution.
> Also, none of the included materials give credit to the original author,
> Ken Arnold.
> 
> I'm not sure what the best solution is, exactly. Extensively patch the
> source until it complies with the BSD license again?
> 
> Presumably, the copyright file needs to change at the very least.
>...

Keith, do you remember the copyright history of this code?

Thanks
Adrian

Bug#975165: marked as pending in iannix

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

Bug #975165 in iannix 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/multimedia-team/iannix/-/commit/f61f3adb9fe1536e356325adde034925cd9a2652


Patch to fix FTBFS with Qt5.15+

Closes: #975165


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975165

Processed: Bug#975165 marked as pending in iannix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975165 [src:iannix] iannix: FTBFS: objects/nxcurve.cpp:546:18: error: 
variable ‘QPainterPath pathTmp’ has initializer but incomplete type
Added tag(s) pending.

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

Bug#976329: marked as done (src:psychtoolbox-3: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2020 11:04:48 -0500
with message-id <20201207160448.gq1090...@lena.dartmouth.edu>
and subject line Re: Bug#976329: src:psychtoolbox-3: invalid maintainer address
has caused the Debian Bug report #976329,
regarding src:psychtoolbox-3: invalid maintainer address
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.)


-- 
976329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psychtoolbox-3
Version: 3.0.17.3.dfsg1-1
Severity: serious
X-Debbugs-Cc: Yaroslav Halchenko 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 27 Nov 2020 16:50:50 +

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   t...@neuro.debian.net
>     all hosts for 'neuro.debian.net' have been failing for a long
> time and were last tried after this message arrived

Reporting-MTA: dns; muffat.debian.org

Action: failed
Final-Recipient: rfc822;team@neuro.debian.net
Status: 5.0.0

--- End Message ---
--- Begin Message ---
mail server is back online so we are back to enjoying all the mail ;-)

On Thu, 03 Dec 2020, Ansgar wrote:

> Source: psychtoolbox-3
> Version: 3.0.17.3.dfsg1-1
> Severity: serious
> X-Debbugs-Cc: Yaroslav Halchenko 

> The maintainer address is invalid, see below.

> Ansgar

>  Forwarded Message 
> Subject: Mail delivery failed: returning message to sender
> Date: Fri, 27 Nov 2020 16:50:50 +

> > This message was created automatically by mail delivery software.

> > A message that you sent could not be delivered to one or more of its
> > recipients. This is a permanent error. The following address(es)
> > failed:

> >   t...@neuro.debian.net
> >     all hosts for 'neuro.debian.net' have been failing for a long
> > time and were last tried after this message arrived


> Reporting-MTA: dns; muffat.debian.org

> Action: failed
> Final-Recipient: rfc822;t...@neuro.debian.net
> Status: 5.0.0


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Bug#976326: marked as done (src:datalad: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2020 11:05:55 -0500
with message-id <20201207160555.gr1090...@lena.dartmouth.edu>
and subject line Re: Bug#976326: src:datalad: invalid maintainer address
has caused the Debian Bug report #976326,
regarding src:datalad: invalid maintainer address
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.)


-- 
976326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: datalad
Version: 0.13.5-1
Severity: serious
X-Debbugs-Cc: Yaroslav Halchenko 

The maintainer address is invalid, see below.

Ansgar

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
> its recipients. This is a permanent error. The following
> address(es) failed:

  t...@datalad.org
    all hosts for 'datalad.org' have been failing for a long time 
> and were last tried after this message arrived

Reporting-MTA: dns; muffat.debian.org

Action: failed
Final-Recipient: rfc822;team@datalad.org
Status: 5.0.0

--- End Message ---
--- Begin Message ---
mail server is back online so we are back to enjoying all the mail ;-)


On Thu, 03 Dec 2020, Ansgar wrote:

> Source: datalad
> Version: 0.13.5-1
> Severity: serious
> X-Debbugs-Cc: Yaroslav Halchenko 

> The maintainer address is invalid, see below.

> Ansgar

> This message was created automatically by mail delivery software.

> A message that you sent could not be delivered to one or more of
> > its recipients. This is a permanent error. The following
> > address(es) failed:

>   t...@datalad.org
>     all hosts for 'datalad.org' have been failing for a long time 
> > and were last tried after this message arrived


> Reporting-MTA: dns; muffat.debian.org

> Action: failed
> Final-Recipient: rfc822;t...@datalad.org
> Status: 5.0.0


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Bug#976325: marked as done (src:libgdf: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2020 11:06:47 -0500
with message-id <20201207160647.gs1090...@lena.dartmouth.edu>
and subject line Re: [ans...@debian.org: Bug#976325: src:libgdf: invalid 
maintainer address]
has caused the Debian Bug report #976325,
regarding src:libgdf: invalid maintainer address
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.)


-- 
976325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgdf
Version: 0.1.3-5
Severity: serious
X-Debbugs-Cc: Rafael Laboissière 

The maintainer address is invalid, see below.

Ansgar

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   t...@neuro.debian.net
>     retry timeout exceeded

Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;team@neuro.debian.net
Status: 5.0.0

--- End Message ---
--- Begin Message ---
mail server is back online so we are back to enjoying all the mail ;-)


On Thu, 03 Dec 2020, Rafael Laboissière wrote:

> Dear Yaroslav and Michael,

> Are you aware of the problem related in Bug#976325, regarding the email
> address t...@neuro.debian.net?

> Best,

> Rafael Laboissière
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik



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

Processed: tagging 976687

[Debian Bug Tracking System]

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

> tags 976687 - sid
Bug #976687 [src:python-escript] python3-escript: mixing incompatible libpython 
and libboost_python
Removed tag(s) sid.
> thanks
Stopping processing here.

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

Processed: tagging 976686

[Debian Bug Tracking System]

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

> tags 976686 - sid
Bug #976686 [src:glom] glom: mixing incompatible libpython and libboost_python
Removed tag(s) sid.
> thanks
Stopping processing here.

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

Processed: tagging 975926

[Debian Bug Tracking System]

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

> tags 975926 - sid
Bug #975926 [enigmail] enigmail should not be shipped in bookworm
Removed tag(s) sid.
> thanks
Stopping processing here.

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

Bug#973147: marked as done (pg-wait-sampling: FTBFS: diff in generated debian/control)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2020 17:20:22 +0100
with message-id <20201207162022.ga25...@xanadu.blop.info>
and subject line Re: Bug#973147: pg-wait-sampling
has caused the Debian Bug report #973147,
regarding pg-wait-sampling: FTBFS: diff in generated debian/control
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.)


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2020-06-17 12:26:59.0 +
> +++ debian/control.Y4C6pb 2020-10-27 12:17:58.659154225 +
> @@ -8,8 +8,8 @@
>  Vcs-Browser: https://github.com/postgrespro/pg_wait-sampling
>  Vcs-Git: https://github.com/postgrespro/pg_wait-sampling.git
>  
> -Package: postgresql-12-pg-wait-sampling
> +Package: postgresql-13-pg-wait-sampling
>  Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-12,
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13,
>  Description: pg_wait-sampling provides functions for detailed per backend
>   and per query statistics about PostgreSQL wait events
> 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/pg-wait-sampling_1.1.1-1_unstable.log

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

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

On 07/12/20 at 16:41 +0100, Adrien Nayrat wrote:
> On 11/13/20 3:53 PM, Krüg...@buxtehude.debian.org, Sebastian wrote:
> > The new release 1.1.2 should fix the bug:
> > 
> >  
> > 
> > https://github.com/postgrespro/pg_wait_sampling/releases
> > 
> > 
> >  
> > 
> 
> Hello,
> New version has been released and is available:
> https://tracker.debian.org/pkg/pg-wait-sampling
> 
> I am not familiar with Debian bug tracking system, I do not know if I can 
> close
> this bug or if Lucas Nussbaum has to do?

You can, but I'm closing it

Lucas--- End Message ---

Bug#975415: git-revise: autopkgtest failure on armhf & ppc64el showing the package downloads code from internet

[Nicolas Schier]

Source: git-revise
Tags: pending

Thanks for the verbose explanation!

I uploaded a new version of git-revise that uses pytest to run the 
tests (and no more tox with its automatically downloaded dependencies).
As soon as I have found a sponsor, this RC bug should be fixed.

Kind regards,
Nicolas


signature.asc
Description: PGP signature

Bug#976218: [Pkg-nagios-devel] Bug#976218: nagios-plugins-contrib: diff for NMU version 27.20200511+1+nmu1 (was: Bug#976218: file breaks nagios-plugins-contrib autopkgtest: SSL_CERT UNKNOWN www.debian

[Jan Wagner]

Hi Chirstoph,

thanks for taking care.

Am 07.12.20 um 08:09 schrieb Christoph Biedl:
> to resolve this issue, I've prepared a NMU for nagios-plugins-contrib
> (versioned as 27.20200511+1+nmu1), and uploaded it to DELAYED/5. Please
> feel free to tell me if I should delay it longer.

1.124.0 is already integrated into VCS
(https://salsa.debian.org/nagios-team/pkg-nagios-plugins-contrib/-/commit/6827b67108fcaafb5c73de8d7b44d71b2a7e6cf3),
so you can delay this a bit more. Actually I'm working hard to get the
latest VCS into unstable but I have to work on some other issues as well.

Thanks, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS
PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y
--END GEEK CODE BLOCK--

Bug#973147: pg-wait-sampling

[Adrien Nayrat]

On 11/13/20 3:53 PM, Krüg...@buxtehude.debian.org, Sebastian wrote:
> The new release 1.1.2 should fix the bug:
> 
>  
> 
> https://github.com/postgrespro/pg_wait_sampling/releases
> 
> 
>  
> 

Hello,
New version has been released and is available:
https://tracker.debian.org/pkg/pg-wait-sampling

I am not familiar with Debian bug tracking system, I do not know if I can close
this bug or if Lucas Nussbaum has to do?

Regards,

-- 
Adrien NAYRAT

Bug#976735: spyder needs source upload for Python 3.9 transition

[Adrian Bunk]

Package: spyder
Version: 3.3.6+dfsg1-5
Severity: serious

Since binNMUs are not possible for binary-all packages,
a source upload is needed for the Python 3.9 transition.

In a more general note, does /usr/bin/spyder3 have to use
the versioned interpreter instead of python3?

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com

First of all, I am really sorry about the annoying logs that spawn under every
message of mine. I am not putting them there on purpose, this is all
reportbug's work. I tried setting it to advanced and expert, hoping that it
will be less spammy, but it isn't. I admit I have no idea on how to report a
bug outside reportbug.

About the "nvidia-blacklists-nouveau.conf". I had to use nouveau some months
ago too (for like 1 hour at most, thankfully) and that file was removed when I
purged some nvidia package. I have no idea why it is not removed anymore. A
file with the same name but under a different path exists in nvidia-
legacy-340xx-kernel-support.

As for the rest. I accept that the bug is not related to the driver directly
but to the kernel. But from my point of view, because it showed up when I
upgraded to 5.9.11 from sid, it remains a bug in the driver and the patch I
posted above IS for the driver!

However, the patch does not work, probably because it conflicts with another
patch. It does work with no issues on another distro that uses the same kernel
version and the has the same kernel parameter disabled. It also works when it
is applied to the "source" of the driver (tested on a virtual machine by a
friend of mine).

Last but not least, although I can not say I am "mad" at debian for this, I
think that it non-free is a part of debian and should receive equal support.
Besides, for ~2 years now (since 5.2 if I recall correctly), I do my best to
keep this driver in the repo. I am (usually) the first to open the bug report
and to find the needed patches.

My last hope is 5.10. It will stay in the repos for the entire first half of
2021, since debian will be on a freeze for 11. I will do my best to make nvidia
legacy 340 work with it, but if if I get no help, I will move to another distro
(arch) before the release of debian 11.
At least I will enjoy an up to date chromium there...



-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux

/proc/version:
Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 10.2.0 (Debian 10.2.0-19) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.152130] Console: colour VGA+ 80x25
[0.588297] pci :01:00.0: vgaarb: setting as boot VGA device
[0.588297] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.588297] pci :01:00.0: vgaarb: bridge control possible
[0.588297] vgaarb: loaded
[0.774547] Linux agpgart interface v0.103
[3.185919] nvidia: loading out-of-tree module taints kernel.
[3.185930] nvidia: module license 'NVIDIA' taints kernel.
[3.220590] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.250196] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.250623] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.250636] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.834283] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.923444] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9
[3.923538] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[3.923959] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[3.924154] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[8.576505] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Dec  7 15:17 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Dec  7 15:19 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Dec  7 15:19 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Dec  7 15:17 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jun  8 11:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root 

Processed: Re: Bug#976559: python-x2go: FTBFS: NameError: name 'AF_INET' is not defined

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:python-gevent
Bug #976559 [src:python-x2go] python-x2go: FTBFS: NameError: name 'AF_INET' is 
not defined
Bug reassigned from package 'src:python-x2go' to 'src:python-gevent'.
No longer marked as found in versions python-x2go/0.6.1.3-2.
Ignoring request to alter fixed versions of bug #976559 to the same values 
previously set
> forcemerge #975782 -1
Bug #975782 {Done: Adrian Bunk } [src:python-gevent] 
python-x2go: FTBFS: NameError: name 'AF_INET' is not defined
Bug #976559 [src:python-gevent] python-x2go: FTBFS: NameError: name 'AF_INET' 
is not defined
Marked Bug as done
Added indication that 976559 affects src:python-x2go
Marked as fixed in versions python-gevent/20.9.0-0.1.
Merged 975782 976559

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

Processed: Bug#964496 marked as pending in libjson-validator-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964496 [libjson-validator-perl] libjson-validator-perl: License known for 
cache files
Added tag(s) pending.

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

Bug#964496: marked as pending in libjson-validator-perl

[Andrius Merkys]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libjson-validator-perl/-/commit/7c7f1f7b624946c895a7eb9139fde36b5d4659b7


Adding cache links for OpenAPI schemas (Closes: #964496).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964496

Bug#972921: marked as done (shasta: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 14:50:15 +
with message-id 
and subject line Bug#972921: fixed in shasta 0.6.0-2
has caused the Debian Bug report #972921,
regarding shasta: binary-all FTBFS
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=shasta&arch=all&ver=0.6.0-1&stamp=1603461248&raw=0

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# Rename shastaDynamic to shasta for ease
mv debian/shasta/usr/bin/shastaDynamic debian/shasta/usr/bin/shasta
mv: cannot stat 'debian/shasta/usr/bin/shastaDynamic': No such file or directory
make[1]: *** [debian/rules:30: override_dh_install] Error 1
--- End Message ---
--- Begin Message ---
Source: shasta
Source-Version: 0.6.0-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
shasta, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated shasta 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, 07 Dec 2020 14:37:49 +0100
Source: shasta
Architecture: source
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 972921 972922 973427
Changes:
 shasta (0.6.0-2) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Enable binary-all build
 Closes: #972921
   * Architecture: any-amd64 arm64
 Closes: #972922
   * Do not override dh_missing, try to install the files from debian/tmp
 or remove them before dh_missing is called
   * Make sure shared library will fit default Python3 version
   * dh_missing --fail-missing
   * Standards-Version: 5.4.1
 .
   [ Shayan Doust ]
   * build depends python3-dev instead of python3-all-dev
 Closes: #973427
Checksums-Sha1:
 a30681c24556187a0942d533045f61f0810598e8 2256 shasta_0.6.0-2.dsc
 eb5ef92ff1d7d92c32febefe3bed04c3ab927f1d 9480 shasta_0.6.0-2.debian.tar.xz
 bacb680ef09105aee48e04a302a08497f6578a83 15322 shasta_0.6.0-2_amd64.buildinfo
Checksums-Sha256:
 ee0750862d9811ae91c8bea2288eca251fb78e5fa784c954feac171763a12359 2256 
shasta_0.6.0-2.dsc
 500a73c38c68689bb4e140c8652125dc7fd111f21785da6baccd288236667a69 9480 
shasta_0.6.0-2.debian.tar.xz
 ed0c24d63575ddfdfe33e4bd61f8c89fe182ad807b0b75b7cfe6cc84fae75ef1 15322 
shasta_0.6.0-2_amd64.buildinfo
Files:
 b0cf230e935d64e0c40112d85d763bb1 2256 science optional shasta_0.6.0-2.dsc
 4e5bc4d635e480c65835c69dea584f20 9480 science optional 
shasta_0.6.0-2.debian.tar.xz
 0c1e6710683119e00de341cbcf7bb372 15322 science optional 
shasta_0.6.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl/ONJkRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHYNA/9G3h6xqOyaENlweLgD4v7JYSTh6sENVpY
IsHIs9oGoARPSs8NMLdYplDtFTrdT0r7mceJgbUpN1kKh8OVjif+hu4qAkkFRy1+
s7s6eqgkh0oYsNBhL6HV0D/RdhYIvEVgGU+H0Cfn77TLHtM0LnN9cE1VgZU3KyDb
PwN8qwlU4CKvd+T/PvfCFNVKnbj78mgqWJbODPQcnSZI/q4/vDnX5XpmoYvG23Hd
zSwv/CL2e7QzOnHgDN3MqJEqvx3hFa4h61xJNRcmzFh1TIOLV9tcFq4aoRNYZ6bn
yrc7CG1pL3KkUd9uI5mHnoFx8rwp3QpksFoOugSN/vimZTIMqoAf0LLaI9wptVzX
hby0J/wg0vY9mmkGaSd6jHlSHzmVZkPaLi5eqfoHcITAXVWd/4y/mZHX/DI/1A1c
q40PrO0xEC7Q8I3rmzkNEt0qnq3NxbTdWh/rmUulEkUy2PXkBe+wDuAocf7s/ehY
LzD02ml9LlPeGtXjpNhlt41wDYXrYAaFyeL3Mmp8y/s/h+oQPCO4xP+qvbm/V2R8
69BD3kNIISDDPOR7vgI6PsgCZ068S94a74QmvGsfEJNS5UAfV/KCYn/pEYZkVuuK
ucM25beFs2aj7KRCTustUDMM1VSOen3QnidVCN+0vsmSimqbNCV9amMnyJHjv9vT
hOK2WNisAVI=
=pEro
-END PGP SIGNATURE End Message ---

Bug#971166: marked as done (libgovirt: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2020 14:41:51 +
with message-id 
and subject line Bug#971166: fixed in libgovirt 0.3.7-2
has caused the Debian Bug report #971166,
regarding libgovirt: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/tests'
> ../build-aux/test-driver: line 107: 17674 Trace/breakpoint trap   "$@" > 
> $log_file 2>&1
> FAIL: test-govirt
> ===
>libgovirt 0.3.7: tests/test-suite.log
> ===
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-govirt
> =
> 
> # random seed: R02S2c214f45fe23607ab25f7fa1cae83bc8
> 1..6
> # Start of govirt tests
> # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
> after threads are created
> # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation 
> gnutls (GTlsBackendGnutls) for ?gio-tls-backend?
> 
> (/<>/tests/.libs/test-govirt:17674): GLib-CRITICAL **: 
> 11:26:26.668: Did not see expected message libgovirt-WARNING **: Disabling 
> strict checking of SSL certificates
> Bail out! libsoup-FATAL-WARNING: Could not set SSL credentials from 
> '/etc/ssl/certs/ca-certificates.crt': Failed to populate trust list from 
> /etc/ssl/certs/ca-certificates.crt: Error while reading file.
> 
> (/<>/tests/.libs/test-govirt:17674): libsoup-WARNING **: 
> 11:26:26.668: Could not set SSL credentials from 
> '/etc/ssl/certs/ca-certificates.crt': Failed to populate trust list from 
> /etc/ssl/certs/ca-certificates.crt: Error while reading file.
> # DEBUG: Listening on https://127.0.0.1:8088/
> 
> # DEBUG: Listening on https://[::1]:8088/
> 
> # DEBUG: 
> Waiting for requests...
> 
> FAIL test-govirt (exit status: 133)
> 
> 
> Testsuite summary for libgovirt 0.3.7
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> 
> make[5]: *** [Makefile:753: test-suite.log] Error 1
> make[5]: Leaving directory '/<>/tests'
> make[4]: *** [Makefile:861: check-TESTS] Error 2
> make[4]: Leaving directory '/<>/tests'
> make[3]: *** [Makefile:934: check-am] Error 2
> make[3]: Leaving directory '/<>/tests'
> make[2]: *** [Makefile:476: check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

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

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

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

We believe that the bug you reported is fixed in the latest version of
libgovirt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libgovirt 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, 07 De

Bug#925818: rocksdb: ftbfs with GCC-9

[GCS]

On Mon, Dec 7, 2020 at 1:00 PM Paul Gevers  wrote:
> On 07-12-2020 08:11, László Böszörményi (GCS) wrote:
> >  Yeah, it's a bit confusing why someone tagged this as affecting
> > experimental.
>
> That's because you fixed this bug in experimental. So the BTS apparently
> that's part of where the bug is relevant. The version in experimental is
> marked as fixed, so everything's fine.
 Ah, got where the misunderstanding is between us. I talk about
#975848 [1] while you are not.

> > I could _not_ confirm that the FTBFS happens there.
>
> Neither did the person that set that tag. Otherwise he would have also
> used "reopen" too. Take a look at the top right version plot in the BTS.
 As noted, there are two GCC FTBFS bugs and the latter set as
affecting experimental for no known reason.

Regards,
Laszlo/GCS
[1] https://bugs.debian.org/975848

Bug#976730: firefox: FTBFS on armhf (unresolved imports `core::arch::arm::float32x4_t`, `core::arch::arm::int32x4_t`, `core::arch::arm::vaddq_f32`)

[Julien Cristau]

Source: firefox
Version: 83.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1680495

The log at
https://buildd.debian.org/status/fetch.php?pkg=firefox&arch=armhf&ver=83.0-1&stamp=1605661388&raw=0
seems to match the error reported upstream by SUSE, with qcms relying on
nightly rustc features.

Cheers,
Julien