Bug#1000983: marked as pending in ocaml-mm

Control: tag -1 pending Hello, Bug #1000983 in ocaml-mm 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#1000983 marked as pending in ocaml-mm

Processing control commands: > tag -1 pending Bug #1000983 [src:ocaml-mm] ocaml-mm FTBFS on !am64/arm64/riscv64 Added tag(s) pending. -- 1000983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999857: marked as done (mod-wsgi FTBFS with python 3.10 as supported version)

Your message dated Mon, 06 Dec 2021 05:48:52 + with message-id and subject line Bug#999857: fixed in mod-wsgi 4.9.0-1 has caused the Debian Bug report #999857, regarding mod-wsgi FTBFS with python 3.10 as supported version to be marked as done. This means that you claim that the problem has

Bug#999533: marked as done (matplotlib: python3-pil.imagetk should be Depends)

Your message dated Mon, 06 Dec 2021 05:33:50 + with message-id and subject line Bug#999533: fixed in matplotlib 3.5.0-3 has caused the Debian Bug report #999533, regarding matplotlib: python3-pil.imagetk should be Depends to be marked as done. This means that you claim that the problem has

Processed: Bug#999533 marked as pending in matplotlib

Processing control commands: > tag -1 pending Bug #999533 [src:matplotlib] matplotlib: python3-pil.imagetk should be Depends Added tag(s) pending. -- 999533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999533: marked as pending in matplotlib

Control: tag -1 pending Hello, Bug #999533 in matplotlib 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#1000790: marked as done (uhd: FTBFS on ppc64el: c++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’?)

Your message dated Mon, 06 Dec 2021 04:19:53 + with message-id and subject line Bug#1000790: fixed in uhd 4.1.0.4-3 has caused the Debian Bug report #1000790, regarding uhd: FTBFS on ppc64el: c++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’? to be

Processed: reopening 997620

Processing commands for cont...@bugs.debian.org: > reopen 997620 Bug #997620 {Done: Emmanuel Arias } [src:python-dexml] python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid. 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#1001009: Downloads external files on install

On Sun, Dec 5, 2021 at 3:30 PM Tong Sun wrote: > > Hi Andrey, > > Would this fix the problem? > https://salsa.debian.org/debian/dbab/-/commit/40d960d7108051fc7ff07b1b4bbc8580722393c9 W: dbab: unknown-section contrib Maybe not. So what exactly do you mean "moved to contrib", Andrey? > thx > > On

Bug#998161: closed by Debian FTP Masters (reply to Christian Marillat ) (Bug#998161: fixed in gourmand 1.0.0-3)

On 06 déc. 2021 01:16, Itaï BEN YAACOV wrote: > Hi, > > Looks like the same bug persists in gourmand. > > ... > File "/usr/lib/python3/dist-packages/gourmand/backends/db.py", line 759, in > fetch_len > return table.count().execute().fetchone()[0] > AttributeError: 'Table' object has no

Bug#998161: closed by Debian FTP Masters (reply to Christian Marillat ) (Bug#998161: fixed in gourmand 1.0.0-3)

Hi, Looks like the same bug persists in gourmand. ... File "/usr/lib/python3/dist-packages/gourmand/backends/db.py", line 759, in fetch_len return table.count().execute().fetchone()[0] AttributeError: 'Table' object has no attribute 'count' Chhers, Itaï Le dimanche 05 décembre 2021 à 19:03

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

Hi, On Sun, Dec 5, 2021 at 6:57 AM Paul Gevers wrote: > > Hi Andres, > > On 05-12-2021 03:36, Andres Salomon wrote: > > So what's happening with chromium in both sid and stable? I saw on > > d-release that it was removed from testing (#998676 and #998732), with a > > discussion about ending

Bug#984382: marked as done (vdr: ftbfs with GCC-11)

Your message dated Sun, 05 Dec 2021 22:21:27 + with message-id and subject line Bug#984382: fixed in vdr 2.4.7-1 has caused the Debian Bug report #984382, regarding vdr: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#997635: marked as done (flask-openid: FTBFS: error in Flask-OpenID setup command: use_2to3 is invalid.)

Your message dated Sun, 5 Dec 2021 18:58:58 -0300 with message-id and subject line has caused the Debian Bug report #997635, regarding flask-openid: FTBFS: error in Flask-OpenID setup command: use_2to3 is invalid. to be marked as done. This means that you claim that the problem has been dealt

Bug#995448: marked as done (ruby-httpclient: uses stale copy of CA certificates)

Your message dated Sun, 05 Dec 2021 21:03:39 + with message-id and subject line Bug#995448: fixed in ruby-httpclient 2.8.3-3+deb11u1 has caused the Debian Bug report #995448, regarding ruby-httpclient: uses stale copy of CA certificates to be marked as done. This means that you claim that

Bug#995875: marked as done (SSL error when trying to retrieve bug reports)

Your message dated Sun, 05 Dec 2021 21:03:39 + with message-id and subject line Bug#995448: fixed in ruby-httpclient 2.8.3-3+deb11u1 has caused the Debian Bug report #995448, regarding SSL error when trying to retrieve bug reports to be marked as done. This means that you claim that the

Bug#946412: janus-gateway: upstream does not support stable releases

Quoting Jonas Smedegaard (2021-04-22 14:45:08) > Quoting Jonas Smedegaard (2019-12-08 14:09:10) > > Upstream releases are to be considered draft snapshots, > > and this package is therefore unsuitable for inclusion > > in long-term distributions like Debian stable. > > > > This bug should be

Bug#997774: tensorpipe: FTBFS: dh_missing: error: missing files, aborting

Hi, Obviously the debian/not-installed file should be updated to further exclude new files generated by Googletest, and the fix should be trivial. Thanks, Boyuan Yang On Sun, 24 Oct 2021 14:27:37 +0200 Lucas Nussbaum wrote: > Source: tensorpipe > Version: 0.0~git20210304.369e855-2 > Severity:

Processed: docbook-mathml should switch from w3-dtd-mathml to w3c-sgml-lib

Processing control commands: > block 994795 by -1 Bug #994795 [w3-dtd-mathml] w3-dtd-mathml: invalid redeclaration of predefined entities amp and lt yields failures with libxml2 2.9.12 994795 was not blocked by any bugs. 994795 was not blocking any bugs. Added blocking bug(s) of 994795: 1001181

Bug#1001181: docbook-mathml should switch from w3-dtd-mathml to w3c-sgml-lib

Package: docbook-mathml Version: 1.1CR1-2.1 Severity: serious Tags: bookworm sid Control: block 994795 by -1 w3-dtd-mathml contains an older version of mathml2.dtd that no longer works with libxml2 2.9.12, see #994795 for background.

Bug#1001009: Downloads external files on install

Hi Andrey, Would this fix the problem? https://salsa.debian.org/debian/dbab/-/commit/40d960d7108051fc7ff07b1b4bbc8580722393c9 thx On Sun, Dec 5, 2021 at 9:56 AM Tong Sun wrote: > > Thanks Andrey, > > Two questions, > > By "moved to contrib", did you meant to change > > Section: net > > to > >

Bug#999760: opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5

Hi On Tue, 30 Nov 2021 12:32:25 +0100 Andreas Beckmann wrote: there is still an unhandled file conflict: Preparing to unpack .../14-libopencv4.5d-jni_4.5.4+dfsg-7+b1_amd64.deb ... Unpacking libopencv4.5d-jni (4.5.4+dfsg-7+b1) ... dpkg: error processing archive

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

Paul Gevers wrote: > On 05-12-2021 03:36, Andres Salomon wrote: >> So what's happening with chromium in both sid and stable? I saw on d-release >> that it was removed from testing (#998676 and #998732), with a discussion >> about ending security support for it in stable. > > The problem really

Bug#998161: marked as done (gourmet: Fails to run with sqlalchemy 1.4.23, due to removal of FromClause.count())

Your message dated Sun, 05 Dec 2021 19:00:12 + with message-id and subject line Bug#998161: fixed in gourmand 1.0.0-3 has caused the Debian Bug report #998161, regarding gourmet: Fails to run with sqlalchemy 1.4.23, due to removal of FromClause.count() to be marked as done. This means that

Bug#995387: marked as done (dpkg: remove-on-upgrade deletes symlink targets owned by another package)

Your message dated Sun, 05 Dec 2021 18:18:47 + with message-id and subject line Bug#995387: fixed in dpkg 1.21.0 has caused the Debian Bug report #995387, regarding dpkg: remove-on-upgrade deletes symlink targets owned by another package to be marked as done. This means that you claim that

Bug#1000421: marked as done (dpkg-shlibdeps: Wrong minimum version requirement on libc6)

Your message dated Sun, 05 Dec 2021 18:18:47 + with message-id and subject line Bug#1000421: fixed in dpkg 1.21.0 has caused the Debian Bug report #1000421, regarding dpkg-shlibdeps: Wrong minimum version requirement on libc6 to be marked as done. This means that you claim that the problem

Bug#994237: marked as done (fix ftbfs with GCC 11)

Your message dated Sun, 05 Dec 2021 17:48:31 + with message-id and subject line Bug#994237: fixed in criterion 2.3.3git1-2 has caused the Debian Bug report #994237, regarding fix ftbfs with GCC 11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#984025: marked as done (criterion: ftbfs with GCC-11)

Your message dated Sun, 05 Dec 2021 17:48:31 + with message-id and subject line Bug#984025: fixed in criterion 2.3.3git1-2 has caused the Debian Bug report #984025, regarding criterion: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: tagging 998772

Processing commands for cont...@bugs.debian.org: > tags 998772 - experimental Bug #998772 {Done: Paul Gevers } [src:ruby-omniauth-openid-connect] src:ruby-omniauth-openid-connect: fails to migrate to testing for too long: unresolved RC bug Removed tag(s) experimental. > thanks Stopping

Bug#1001170: gnudatalanguage: FTBFS on mipsel: relocation truncated to fit: R_MIPS_GOT16 against `CpuTPOOL_MAX_ELTS'

Source: gnudatalanguage Version: 1.0.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) | [ 97%] Linking CXX shared library libgnudatalanguage.so | cd /<>/obj-mipsel-linux-gnu/src && /usr/bin/cmake -E cmake_link_script

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

Source: hkl Version: 5.0.0.2816-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) | ../../config/test-driver: line 112: 746832 Segmentation fault "$@" >> "$log_file" 2>&1 | FAIL: trajectory.py |

Processed: found 999721 in 0.3.5-1

Processing commands for cont...@bugs.debian.org: > found 999721 0.3.5-1 Bug #999721 [src:ruby-omniauth-openid-connect] ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in

Bug#1000756: freedv: FTBFS: varicode.h: No such file or directory

This appears to be fixed by version 1.6.1-1 in experimental? is there any blocker for uploading it to unstable?

Bug#998008: marked as done (libc-bin: postinst makes a working NIS system not to work anymore at every point release)

Your message dated Sun, 05 Dec 2021 16:04:41 + with message-id and subject line Bug#998008: fixed in glibc 2.32-5 has caused the Debian Bug report #998008, regarding libc-bin: postinst makes a working NIS system not to work anymore at every point release to be marked as done. This means

Bug#1000413: marked as done (discosnp: autopkgtest regression: Segmentation fault)

Your message dated Sun, 05 Dec 2021 16:04:30 + with message-id and subject line Bug#1000413: fixed in discosnp 1:2.6.1-1 has caused the Debian Bug report #1000413, regarding discosnp: autopkgtest regression: Segmentation fault to be marked as done. This means that you claim that the problem

Processed: tagging 996640

Processing commands for cont...@bugs.debian.org: > tags 996640 + pending Bug #996640 [src:powertop] powertop FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#998498: pfstools: FTBFS: stl_algobase.h:278:56: error: macro "min" passed 3 arguments, but takes just 2

X-Debbugs-Cc: libnetpbm10-...@packages.debian.org On 2021-11-04 Lucas Nussbaum wrote: > Source: pfstools > Version: 2.2.0-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211104 ftbfs-bookworm > Hi, > During a rebuild of all

Bug#1001009: Downloads external files on install

Thanks Andrey, Two questions, By "moved to contrib", did you meant to change Section: net to Section: contrib in d/control? Now, let's define what "package cannot function" actually means. If functions normally without this or similar unpackaged file, but the program is completely data

Bug#992673: marked as done (libgpuarray: *gemv broken on libclblast)

Your message dated Sun, 5 Dec 2021 14:30:07 + with message-id <47cbdd19-9686-fc47-3c38-fc9671823...@debian.org> and subject line re: libgpuarray: autopkgtest depends on libclblas-dev which is not in testing *and* has skip-not-installable has caused the Debian Bug report #992673, regarding

Bug#998494: marked as done (ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so)

Your message dated Sun, 05 Dec 2021 14:12:48 +0100 with message-id <60f88dd3c044a978fc7a5b1be4a4abda10808c0a.ca...@debian.org> and subject line Closing this report - not applicable anymore has caused the Debian Bug report #998494, regarding ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby3.0"

Bug#998506: marked as done (ruby-rspec-puppet-facts: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so)

Your message dated Sun, 05 Dec 2021 14:03:01 +0100 with message-id and subject line Closing this report - not applicable anymore has caused the Debian Bug report #998506, regarding ruby-rspec-puppet-facts: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so to be marked as

Bug#1000780: eigen3 breaks pybind11 autopkgtest on ppc64el: inlining failed in call to ‘always_inline’

Source: pybind11 Version: 2.7.1-1 Followup-For: Bug #1000780 Sounds like some change was made in eigen3 3.4.0 which now breaks pybind11 (pybind11 3.8.1 also fails the same way). Not clear at this point if it's a regression in eigen3 that needs to be fixed in eigen3, or an API change that

Processed: pybind11 eigen3

Processing commands for cont...@bugs.debian.org: > forwarded 1000780 https://github.com/pybind/pybind11/issues/3528 Bug #1000780 [src:eigen3, src:pybind11] eigen3 breaks pybind11 autopkgtest on ppc64el: inlining failed in call to ‘always_inline’ Set Bug forwarded-to-address to

Bug#998509: marked as done (ruby-rspec-puppet: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so)

Your message dated Sun, 05 Dec 2021 12:03:45 + with message-id and subject line Bug#998509: fixed in ruby-rspec-puppet 2.8.0-2 has caused the Debian Bug report #998509, regarding ruby-rspec-puppet: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so to be marked as

Bug#995909: python3-fava: Fails to start with jinja2 3.0.1

Hi, intrigeri (2021-12-05): >> I understand this is upstream bug >> https://github.com/beancount/fava/issues/1266, >> that's been fixed in the 1.19 release. > > Upgrading fava requires python3-flask-babel (>= 1). > > I'll try to update it. I've uploaded python3-flask-babel 2.0.0. Here's a

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

> Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers: > > The problem really is lack of maintenance. In my opinion, chromium deserves > > an active *team* to support it in Debian. [..] > > We'll not ship it in bookworm unless we see steady uploads > > in unstable and we see security

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers: > Hi Andres, > > On 05-12-2021 03:36, Andres Salomon wrote: > > So what's happening with chromium in both sid and stable? I saw on > > d-release that it was removed from testing (#998676 and #998732), with a > > discussion about ending

Bug#995909: Acknowledgement (python3-fava: Fails to start with jinja2 3.0.1)

Hi, > I understand this is upstream bug > https://github.com/beancount/fava/issues/1266, > that's been fixed in the 1.19 release. Upgrading fava requires python3-flask-babel (>= 1). I'll try to update it.

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

Hi Andres, On 05-12-2021 03:36, Andres Salomon wrote: So what's happening with chromium in both sid and stable? I saw on d-release that it was removed from testing (#998676 and #998732), with a discussion about ending security support for it in stable. I'm willing to help out with chromium

Processed: Re: Bug#997707: fava: FTBFS: help2man: can't get `--help' info from PYTHONPATH="/<>/src" python3 -m fava.cli

Processing control commands: > tag 995909 + ftbfs Bug #995909 [python3-fava] python3-fava: Fails to start with jinja2 3.0.1 Added tag(s) ftbfs. > tag 995909 + bookworm Bug #995909 [python3-fava] python3-fava: Fails to start with jinja2 3.0.1 Added tag(s) bookworm. > tag 995909 + sid Bug #995909

Bug#997707: fava: FTBFS: help2man: can't get `--help' info from PYTHONPATH="/<>/src" python3 -m fava.cli

Control: tag 995909 + ftbfs Control: tag 995909 + bookworm Control: tag 995909 + sid Control: severity 995909 serious Control: reassign 995909 src:fava Control: merge -1 995909 Hi, Lucas Nussbaum (2021-10-24): >> help2man: can't get `--help' info from PYTHONPATH="/<>/src" >> python3 -m fava.cli

Processed: affects 994391

Processing commands for cont...@bugs.debian.org: > affects 994391 + todoman Bug #994391 [python3-click] vdirsyncer is unusable Added indication that 994391 affects todoman > thanks Stopping processing here. Please contact me if you need assistance. -- 994391: