Processed: Re: [Debian-med-packaging] Bug#1001932: smart-open: FTBFS: ERROR smart_open/tests/test_gcs.py: ModuleNotFoundError: No module named 'google'

Processing control commands: > tags -1 moreinfo Bug #1001932 [src:smart-open] smart-open: FTBFS: ERROR smart_open/tests/test_gcs.py: ModuleNotFoundError: No module named 'google' Added tag(s) moreinfo. > severity -1 important Bug #1001932 [src:smart-open] smart-open: FTBFS: ERROR

Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed

On Sun, 19 Dec 2021 13:03:38 +0800 Paul Wise wrote: > On Sat, 11 Dec 2021 10:15:42 -0800 Noah Meyerhans wrote: > > > On sid we currently see the follow rdeps: > > There are a few more in Build-Depends Also there are a few Recommends and Suggests: $ reverse-depends -s python3-boto

Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed

On Sun, 19 Dec 2021 13:03:38 +0800 Paul Wise wrote: > smart-open: python3-boto This one build-deps on both python3-boto and python3-boto3.  It also has an unrelated failure to build as the test suite cannot import the google.cloud Python module. Filed as #1001932. -- bye, pabs

Bug#1001932: smart-open: FTBFS: ERROR smart_open/tests/test_gcs.py: ModuleNotFoundError: No module named 'google'

Source: smart-open Version: 5.2.1-1 Severity: serious Tags: ftbfs When trying to rebuild smart-open in pbuilder, I get a test failure: $ pdebuild ... = test session starts == platform linux -- Python 3.9.9, pytest-6.2.5,

Bug#978911: marked as done (transmission: ftbfs with autoconf 2.70)

Your message dated Sun, 19 Dec 2021 05:35:03 + with message-id and subject line Bug#978911: fixed in transmission 3.00-2 has caused the Debian Bug report #978911, regarding transmission: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt

Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed

On Sat, 11 Dec 2021 10:15:42 -0800 Noah Meyerhans wrote: > On sid we currently see the follow rdeps: There are a few more in Build-Depends, the totality of them are spread across several different teams and individuals. I would suggest an MBF (mini bug filing) if python-boto is going to be

Processed (with 1 error): bug 978911 is forwarded to https://github.com/transmission/transmission/issues/1573 ...

Processing commands for cont...@bugs.debian.org: > forwarded 978911 https://github.com/transmission/transmission/issues/1573 Bug #978911 [src:transmission] transmission: ftbfs with autoconf 2.70 Changed Bug forwarded-to-address to 'https://github.com/transmission/transmission/issues/1573' from

Processed: bug 1001709 is forwarded to https://github.com/amule-project/amule/issues/309

Processing commands for cont...@bugs.debian.org: > forwarded 1001709 https://github.com/amule-project/amule/issues/309 Bug #1001709 [amule-daemon] amule-daemon: amuled crashes with segmentation fault on startup Set Bug forwarded-to-address to 'https://github.com/amule-project/amule/issues/309'.

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

Your message dated Sun, 19 Dec 2021 03:04:49 + with message-id and subject line Bug#997303: fixed in dulwich 0.20.26-1 has caused the Debian Bug report #997303, regarding xandikos: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 to be marked as

Bug#998031: marked as done (src:breezy: fails to migrate to testing for too long: unresolved RC bug and uploader built arch:all binaries)

Your message dated Sun, 19 Dec 2021 03:04:26 + with message-id and subject line Bug#998031: fixed in breezy 3.2.1+bzr7561-1 has caused the Debian Bug report #998031, regarding src:breezy: fails to migrate to testing for too long: unresolved RC bug and uploader built arch:all binaries to be

Bug#998031: marked as done (src:breezy: fails to migrate to testing for too long: unresolved RC bug and uploader built arch:all binaries)

Your message dated Sun, 19 Dec 2021 03:04:19 + with message-id and subject line Bug#998031: fixed in breezy 3.2.1+bzr7556-1 has caused the Debian Bug report #998031, regarding src:breezy: fails to migrate to testing for too long: unresolved RC bug and uploader built arch:all binaries to be

Bug#995410: marked as done (breezy: FTBFS:)

Your message dated Sun, 19 Dec 2021 03:04:26 + with message-id and subject line Bug#995410: fixed in breezy 3.2.1+bzr7561-1 has caused the Debian Bug report #995410, regarding breezy: FTBFS: to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1000502: marked as done (breezy FTBFS: ModuleNotFoundError: No module named 'breezy.testingplugins.plugin')

Your message dated Sun, 19 Dec 2021 03:04:26 + with message-id and subject line Bug#995410: fixed in breezy 3.2.1+bzr7561-1 has caused the Debian Bug report #995410, regarding breezy FTBFS: ModuleNotFoundError: No module named 'breezy.testingplugins.plugin' to be marked as done. This means

Bug#1000502: marked as done (breezy FTBFS: ModuleNotFoundError: No module named 'breezy.testingplugins.plugin')

Your message dated Sun, 19 Dec 2021 03:04:19 + with message-id and subject line Bug#995410: fixed in breezy 3.2.1+bzr7556-1 has caused the Debian Bug report #995410, regarding breezy FTBFS: ModuleNotFoundError: No module named 'breezy.testingplugins.plugin' to be marked as done. This means

Bug#995410: marked as done (breezy: FTBFS:)

Your message dated Sun, 19 Dec 2021 03:04:19 + with message-id and subject line Bug#995410: fixed in breezy 3.2.1+bzr7556-1 has caused the Debian Bug report #995410, regarding breezy: FTBFS: to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#984158: marked as done (grfcodec: ftbfs with GCC-11)

Your message dated Sun, 19 Dec 2021 03:04:55 + with message-id and subject line Bug#984158: fixed in grfcodec 6.0.6-6 has caused the Debian Bug report #984158, regarding grfcodec: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: tagging 998485

Processing commands for cont...@bugs.debian.org: > tags 998485 - pending Bug #998485 [src:gjiten] gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 998485:

Processed: tagging 998478

Processing commands for cont...@bugs.debian.org: > tags 998478 - pending Bug #998478 [src:httest] httest: FTBFS: configure.ac:13: error: AM_INIT_AUTOMAKE expanded multiple times Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 998478:

Processed: tagging 998553

Processing commands for cont...@bugs.debian.org: > tags 998553 + bullseye Bug #998553 [src:libdbi-drivers] libdbi-drivers: FTBFS: 211104 9:49:12 [ERROR] mysqld got signal 11 ; Added tag(s) bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 998553:

Processed: tagging 1001824

Processing commands for cont...@bugs.debian.org: > tags 1001824 + pending Bug #1001824 [xml2rfc] xml2rfc: Incompatible with current weaseyprint Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001824:

Bug#999132: is help needed?

Is help needed in converting debian/rules to use dh? I certainly wouldn't want uqm to fall out of Debian. -- Opinions above are GNU-copylefted.

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

Dear Nicholas, On Fri, 03 Dec 2021 20:11:10 +0300 Nicholas Guriev wrote: Release managers do not happy with huge updates after Debian freeze. And for good reasons (also remember that upgrades only come every two months or so, even longer for oldstable). If telegram-desktop is useless in

Bug#888331: marked as done (vdr-plugin-softhddevice: FTBFS with FFmpeg 4.0)

Your message dated Sat, 18 Dec 2021 21:21:50 + with message-id and subject line Bug#1001906: Removed package(s) from unstable has caused the Debian Bug report #888331, regarding vdr-plugin-softhddevice: FTBFS with FFmpeg 4.0 to be marked as done. This means that you claim that the problem

Bug#972349: marked as done (b-d's on python3-all-dev, but only builds for the default python3)

Your message dated Sat, 18 Dec 2021 21:18:34 + with message-id and subject line Bug#948018: fixed in getfem++ 5.3+dfsg1-4 has caused the Debian Bug report #948018, regarding b-d's on python3-all-dev, but only builds for the default python3 to be marked as done. This means that you claim that

Bug#948018: marked as done (getfem++: b-d on python3-all-dev, but not built for all supported Python3 versions)

Your message dated Sat, 18 Dec 2021 21:18:34 + with message-id and subject line Bug#948018: fixed in getfem++ 5.3+dfsg1-4 has caused the Debian Bug report #948018, regarding getfem++: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This means

Processed: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x

Processing control commands: > close -1 0.1.00-5 Bug #1001916 [src:bart-view] src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x Marked as fixed in versions bart-view/0.1.00-5. Bug #1001916 [src:bart-view] src:bart-view: fails to migrate to testing for too long:

Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x

Source: bart-view Version: 0.1.00-4 Severity: serious Control: close -1 0.1.00-5 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Bug#999068: marked as done (libmp3-info-perl: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sat, 18 Dec 2021 20:35:13 + with message-id and subject line Bug#999068: fixed in libmp3-info-perl 1.24-1.4 has caused the Debian Bug report #999068, regarding libmp3-info-perl: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This

Bug#1001657: marked as done (ball: binary-any FTBFS)

Your message dated Sat, 18 Dec 2021 20:34:15 + with message-id and subject line Bug#1001657: fixed in ball 1.5.0+git20180813.37fc53c-10 has caused the Debian Bug report #1001657, regarding ball: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt

Processed: severity of 1000735 is important

Processing commands for cont...@bugs.debian.org: > severity 1000735 important Bug #1000735 [src:linux] iwlwifi: start the wifi, it makes a kernel opps Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000735:

Processed: severity of 1001128 is important

Processing commands for cont...@bugs.debian.org: > severity 1001128 important Bug #1001128 {Done: Salvatore Bonaccorso } [src:linux] linux-image-5.15.0-2-amd64: Kernel crashes my GPU Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need

Processed: closing 1001128

Processing commands for cont...@bugs.debian.org: > close 1001128 5.16~rc4-1~exp1 Bug #1001128 [src:linux] linux-image-5.15.0-2-amd64: Kernel crashes my GPU Marked as fixed in versions linux/5.16~rc4-1~exp1. Bug #1001128 [src:linux] linux-image-5.15.0-2-amd64: Kernel crashes my GPU Marked Bug as

Bug#1001128: Fixed in linux-image-5.16.0-rc5-amd64 5.16~rc5-1~exp1

This bug is not present in linux-image-5.16.0-rc5-amd64 5.16~rc5-1~exp1 I'm not tagging it on the BTS because I'm not sure how the versioning works for the kernel. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/

Bug#998926: marked as done (libaudio-scrobbler-perl: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sat, 18 Dec 2021 19:48:58 + with message-id and subject line Bug#998926: fixed in libaudio-scrobbler-perl 0.01-2.4 has caused the Debian Bug report #998926, regarding libaudio-scrobbler-perl: missing required debian/rules targets build-arch and/or build-indep to be marked

Bug#1001128: linux-image-5.15.0-2-amd64: Kernel crashes my GPU

Package: src:linux Version: 5.15.5-1 Followup-For: Bug #1001128 Forwarded: -1 https://gitlab.freedesktop.org/drm/intel/-/issues/4530#note_1166414 X-Debbugs-Cc: lisan...@debian.org I can reproduce this bug on my machine when I log into Plasma. The cause seems to be detected and fixed according

Bug#1000727: marked as done (joypy: FTBFS with pandas 1.3: ImportError: cannot import name '_subplots' from 'pandas.plotting._matplotlib.tools')

Your message dated Sat, 18 Dec 2021 19:03:50 + with message-id and subject line Bug#1000727: fixed in joypy 0.2.2-3 has caused the Debian Bug report #1000727, regarding joypy: FTBFS with pandas 1.3: ImportError: cannot import name '_subplots' from 'pandas.plotting._matplotlib.tools' to be

Bug#1001891: marked as done (apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion)

Your message dated Sat, 18 Dec 2021 18:18:44 + with message-id and subject line Bug#1001891: fixed in apache-log4j2 2.17.0-1 has caused the Debian Bug report #1001891, regarding apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion to be marked as done. This means that

Processed: Bug#1001429 marked as pending in python-qtpy

Processing control commands: > tag -1 pending Bug #1001429 [src:python-qtpy] python-qtpy: (autopkgtest) needs update for python3.10: deprecation warning on stderr Added tag(s) pending. -- 1001429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001429 Debian Bug Tracking System Contact

Bug#1001429: marked as pending in python-qtpy

Control: tag -1 pending Hello, Bug #1001429 in python-qtpy 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#992535: marked as done (kore: autopkgtest started to time out since the ci.d.n host runs bullseye)

Your message dated Sat, 18 Dec 2021 17:49:46 + with message-id and subject line Bug#992535: fixed in kore 4.1.0-5 has caused the Debian Bug report #992535, regarding kore: autopkgtest started to time out since the ci.d.n host runs bullseye to be marked as done. This means that you claim

Bug#1001312: marked as done (kore: FTBFS with postgresql 14, with openssl 3)

Your message dated Sat, 18 Dec 2021 17:49:46 + with message-id and subject line Bug#1001312: fixed in kore 4.1.0-5 has caused the Debian Bug report #1001312, regarding kore: FTBFS with postgresql 14, with openssl 3 to be marked as done. This means that you claim that the problem has been

Bug#998455: marked as done (regina-normal: b-d on python3-all-dev, but not built for all supported Python3 versions)

Your message dated Sat, 18 Dec 2021 17:21:27 + with message-id and subject line Bug#998455: fixed in regina-normal 7.0-1 has caused the Debian Bug report #998455, regarding regina-normal: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This

Bug#1001891: apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion

Hi! On Sat, Dec 18, 2021 at 03:30:16PM +0100, Markus Koschany wrote: > Control: owner -1 ! > > Am Samstag, dem 18.12.2021 um 14:37 +0100 schrieb Salvatore Bonaccorso: > > Source: apache-log4j2 > > Version: 2.16.0-1 > > Severity: grave > > Tags: security upstream > > Forwarded:

Bug#993578: marked as done (90gpg-agent generator: `gpgconf --check-programs` can hang)

Your message dated Sat, 18 Dec 2021 16:48:33 + with message-id and subject line Bug#993578: fixed in gnupg2 2.2.27-3 has caused the Debian Bug report #993578, regarding 90gpg-agent generator: `gpgconf --check-programs` can hang to be marked as done. This means that you claim that the problem

Bug#999323: marked as done (libapache-mod-encoding: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sat, 18 Dec 2021 16:33:28 + with message-id and subject line Bug#999323: fixed in libapache-mod-encoding 0.0.20021209-12 has caused the Debian Bug report #999323, regarding libapache-mod-encoding: missing required debian/rules targets build-arch and/or build-indep to be

Bug#971325: marked as done (renpy: uses deprecated libavresample)

Your message dated Sat, 18 Dec 2021 15:48:33 + with message-id and subject line Bug#971325: fixed in renpy 7.3.5+dfsg-2 has caused the Debian Bug report #971325, regarding renpy: uses deprecated libavresample to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#971325 marked as pending in renpy

Processing control commands: > tag -1 pending Bug #971325 [src:renpy] renpy: uses deprecated libavresample Added tag(s) pending. -- 971325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#971325: marked as pending in renpy

Control: tag -1 pending Hello, Bug #971325 in renpy 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 (with 1 error): uhd: FTBFS on mipsel:

Processing commands for cont...@bugs.debian.org: > package src:uhd Limiting to bugs with field 'package' containing at least one of 'src:uhd' Limit currently set to 'package':'src:uhd' > nofixed 1000791 src:uhd/4.1.0.4-7 Unknown command or malformed arguments to command. > fixed 1000791

Processed: uhd: FTBFS on ppc64el:

Processing commands for cont...@bugs.debian.org: > package src:uhd Limiting to bugs with field 'package' containing at least one of 'src:uhd' Limit currently set to 'package':'src:uhd' > notfixed 1000790 uhd/4.1.0.4-3 Bug #1000790 {Done: A. Maitland Bottoms } [src:uhd] uhd: FTBFS on ppc64el:

Bug#938351: marked as pending in renpy

Renpy still has not been ported to Python 3 yet. The status of renpy and other Python 2 games was previously discussed on debian-devel-games. https://lists.debian.org/debian-devel-games/2020/12/msg00013.html A removal request was filed: https://bugs.debian.org/1001888 I don't think a removal

Processed: Re: Bug#1001891: apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion

Processing control commands: > owner -1 ! Bug #1001891 [src:apache-log4j2] apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion Owner recorded as Markus Koschany . -- 1001891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001891 Debian Bug Tracking System Contact

Bug#1001891: apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion

Control: owner -1 ! Am Samstag, dem 18.12.2021 um 14:37 +0100 schrieb Salvatore Bonaccorso: > Source: apache-log4j2 > Version: 2.16.0-1 > Severity: grave > Tags: security upstream > Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3230 > X-Debbugs-Cc: car...@debian.org, Debian Security

Bug#1001789: marked as done (r-cran-gplots: package 'gplots' was installed before R 4.0.0: please re-install it)

Your message dated Sat, 18 Dec 2021 13:48:32 + with message-id and subject line Bug#1001789: fixed in gplots 3.1.1-2 has caused the Debian Bug report #1001789, regarding r-cran-gplots: package 'gplots' was installed before R 4.0.0: please re-install it to be marked as done. This means that

Bug#1001785: texlive-extra affected by log4j CVEs

Am 16.12.2021 um 09:38 teilte Sven Mueller mit: Hi Sven, hi Norbert, texlive-extra-utils contains arara (https://github.com/islandoftex/arara) which was updated two days ago via TeX Live (https://www.tug.org/texlive/) which was updated slightly after that. Please update to the newest TeX Live

Bug#1001891: apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion

Source: apache-log4j2 Version: 2.16.0-1 Severity: grave Tags: security upstream Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3230 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.16.0-1~deb11u1 Control: found -1 2.16.0-1~deb10u1 Hi, The following

Processed: apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion

Processing control commands: > found -1 2.16.0-1~deb11u1 Bug #1001891 [src:apache-log4j2] apache-log4j2: CVE-2021-45105: Certain strings can cause infinite recursion Marked as found in versions apache-log4j2/2.16.0-1~deb11u1. > found -1 2.16.0-1~deb10u1 Bug #1001891 [src:apache-log4j2]

Bug#1001785: marked as done (texlive-extra affected by log4j CVEs)

Your message dated Sat, 18 Dec 2021 13:23:53 + with message-id and subject line Bug#1001785: fixed in texlive-extra 2021.20211217-1 has caused the Debian Bug report #1001785, regarding texlive-extra affected by log4j CVEs to be marked as done. This means that you claim that the problem has

Bug#1001667: flam3: flaky autopkgtest on ppc64el

I've discovered there is a 2nd seed, so have modified the little test script. Also, the 'echo' was superfluous with set -x === #!/bin/bash # set -e set -x # while :     do env seed=$RANDOM issac_seed=$RANDOM flam3-genome > /dev/null done # genome.sh

Bug#999006: marked as done (sgrep: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sat, 18 Dec 2021 12:49:23 + with message-id and subject line Bug#999006: fixed in sgrep 1.94a-5 has caused the Debian Bug report #999006, regarding sgrep: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#998613: marked as done (retro-gtk: FTBFS: ../retro-gtk/meson.build:188:4: ERROR: Got unknown keyword arguments "export_packages", "namespace")

Your message dated Sat, 18 Dec 2021 12:18:51 + with message-id and subject line Bug#998613: fixed in retro-gtk 1.0.2-2.1 has caused the Debian Bug report #998613, regarding retro-gtk: FTBFS: ../retro-gtk/meson.build:188:4: ERROR: Got unknown keyword arguments "export_packages", "namespace"

Bug#1001882: 0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU

On Sat, 18 Dec 2021 at 17:22:49 +0800, Shengjing Zhu wrote: > process didn't exit successfully: > `/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/debug/build/mozglue-static-db2fd9029278a596/build-script-build` > (exit status: 1) ... > cargo:warning=cc1plus: error:

Bug#1001382: marked as done (liferea: stopped showing xkcd picture in the reader)

Your message dated Sat, 18 Dec 2021 12:03:47 + with message-id and subject line Bug#1001382: fixed in liferea 1.13.7-2 has caused the Debian Bug report #1001382, regarding liferea: stopped showing xkcd picture in the reader to be marked as done. This means that you claim that the problem has

Bug#1001882: 0ad: FTBFS on armhf: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU

Source: 0ad Version: 0.0.25b-1 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/fetch.php?pkg=0ad=armhf=0.0.25b-1%2Bb1=1639777042=0 error: failed to run custom build command for `mozglue-static v0.1.0