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

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

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

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

Bug#976803: mrpt uses private binutils shared library

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

Processed: retitle 976778 to fpylll FTBFS with fplll 5.4.0

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:

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

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

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

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

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

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

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

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

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

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

Processed: tagging 903413

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:

Processed: tagging 976780

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:

Processed: Merge duplicates

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

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

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

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

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:

Bug#976794: Useless in Debian

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Bug#976769: marked as pending in redfishtool

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:

Bug#976771: marked as pending in python-semver

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:

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

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

Processed: Bug#976769 marked as pending in redfishtool

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

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

Bug#975776: marked as pending in billiard

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:

Processed: Bug#975776 marked as pending in billiard

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

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")

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:

Bug#976781: rocketcea FTBFS with Python 3.9 only

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

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

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

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

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

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

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

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

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

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

Bug#976779: mypy FTBFS with only python 3.9

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

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

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. >> >>

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

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" |

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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)

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

Bug#938795: vmtk does not build any more

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

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

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

Bug#938795: vmtk does not build any more

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+

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

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

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

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,

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

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

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'

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

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'

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

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

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.

Bug#975929: Bug in check-manifest, reassigning

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

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

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

Bug#975929: marked as pending in check-manifest

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:

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

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

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

* 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)

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

Processed: forcibly merging 925818 975848

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]

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

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

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

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

Bug#976756: mia: binary-all FTBFS

Source: mia Version: 2.4.7-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mia=all=2.4.7-3=1607360001=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

Processed: affects 973821

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:

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

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

Bug#975165: marked as pending in iannix

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:

Processed: Bug#975165 marked as pending in iannix

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

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

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

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

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.

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

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

Processed: tagging 976687

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:

Processed: tagging 976686

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:

Processed: tagging 975926

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:

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

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

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

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

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

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

Bug#973147: pg-wait-sampling

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

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

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

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

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

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

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

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

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

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:

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

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

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

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

Bug#925818: rocksdb: ftbfs with GCC-9

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#976731: firefox: FTBFS on arm64 (explicit specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’)

Source: firefox Version: 83.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Log: https://buildd.debian.org/status/fetch.php?pkg=firefox=arm64=83.0-1=1606251110=0 Excerpt: > In file included from Unified_cpp_js_src_wasm0.cpp:20: >

  1   2   >