Bug#963659: pybind11: FTBFS with Sphinx 3.1: File "/usr/lib/python3/dist-packages/sphinx/domains/c.py", line 3093, in object_type / raise NotImplementedError())

Wait for sphinx 3.2.1 I mean.

Processed: Re: Bug#937665: Waiting for Python 2-depending reverse dependencies

Processing control commands: > block 967200 by -1 Bug #967200 [src:python-coverage] python-coverage: Unversioned Python removal in sid/bullseye 967200 was not blocked by any bugs. 967200 was blocking: 937695 938168 Added blocking bug(s) of 967200: 937665 -- 937665:

Bug#937665: Waiting for Python 2-depending reverse dependencies

Control: block 967200 by -1 On 17-Aug-2020, Ben Finney wrote: > The updated package is ready, and waiting for reverse-dependencies (as > described in bug reports blocking this one) to drop Python 2 support. -- \ “I have a map of the United States; it's actual size. It says | `\

Processed: tagging 968413

Processing commands for cont...@bugs.debian.org: > tags 968413 + pending Bug #968413 [src:oss4] failes to build on ppc64el with binutils 2.35 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 968413:

Processed (with 1 error): Bug#937665: Waiting for Python 2-depending reverse dependencies

Processing control commands: > forcemerge -1 967200 Bug #937665 [src:python-coverage] python-coverage: Python2 removal in sid/bullseye Bug #937665 [src:python-coverage] python-coverage: Python2 removal in sid/bullseye Marked as found in versions python-coverage/5.1+dfsg.1-1. Bug #967200

Bug#937665: Waiting for Python 2-depending reverse dependencies

Control: forcemerge -1 967200 Control: block -1 by 933750 Control: outlook -1 0 The updated package is ready, and waiting for reverse-dependencies (as described in bug reports blocking this one) to drop Python 2 support. On 16-Aug-2020, Jann Haber wrote: > It seems like, there are no more rdeps

Bug#968210: statsmodels: arm* test failures/crashes

The TestZeroInflatedModel_probit issue appears to be a failure to converge: as it does trigger warnings of that, and it's already skipped on i386, I intend to ignore it. qemu-arm64: >>> a object at 0x4000d31130> >>> a.res1.params Traceback (most recent call last): File "", line 1, in

Bug#963326: marked as done (seqmagick: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13)

Your message dated Sun, 16 Aug 2020 19:48:47 + with message-id and subject line Bug#963326: fixed in seqmagick 0.8.0-2 has caused the Debian Bug report #963326, regarding seqmagick: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13 to be

Bug#968176: marked as pending in gdcm

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

Processing control commands: > tag -1 pending Bug #968176 [src:gdcm] gdcm: wrong debian/control file (mono archs missing) Added tag(s) pending. -- 968176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 957642

Processing commands for cont...@bugs.debian.org: > tags 957642 + patch Bug #957642 [src:openrc] openrc: ftbfs with GCC-10 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 957642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957642 Debian

Bug#968174: llvm-toolchain-9: Re: Bug#968174: Prevent migration of ocaml-{integers,ctypes} to testing

Hello, I am off and I won't have time to work on it for the next 2 weeks. NMU welcome :) Cheers & sorry! Sylvestre Le 16/08/2020 à 08:01, Stéphane Glondu a écrit : Hello, These bugs are still on topic and prevent ocaml-{integers,ctypes} from migrating to testing. Could you please fix them? Or

Bug#937665: fixed in python-coverage 4.5.2+dfsg.1-2

It seems like, there are no more rdeps of python-coverage now. Not sure about pypy-coverage. Dropping python-coverage would also fix #967200, which currently blocks migration to testing. :) On Mon, 11 Nov 2019 05:48:22 +1100 Ben Finney wrote: > Control: reopen -1 > Control: tags -1 + pending >

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

Le 16/08/2020 à 18:03, Stéphane Glondu a écrit : >>> These bugs are still on topic and prevent ocaml-{integers,ctypes} from >>> migrating to testing. Could you please fix them? Or have the faulty >>> packages removed from testing. >> >> At the moment, llvm-toolchain-8 is a key package [1],

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

Le 16/08/2020 à 17:59, Stéphane Glondu a écrit : >> These bugs are still on topic and prevent ocaml-{integers,ctypes} from >> migrating to testing. Could you please fix them? Or have the faulty >> packages removed from testing. > > At the moment, llvm-toolchain-8 is a key package [1], preventing

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

Le 16/08/2020 à 08:01, Stéphane Glondu a écrit : > These bugs are still on topic and prevent ocaml-{integers,ctypes} from > migrating to testing. Could you please fix them? Or have the faulty > packages removed from testing. At the moment, llvm-toolchain-8 is a key package [1], preventing its

Processed: Re: Bug#968511: libgtk-3-0: Segfaults many apps depending on it

Processing control commands: > reassign -1 libpango-1.0-0 1.46.0-1 Bug #968511 [libgtk-3-0] libgtk-3-0: Segfaults many apps depending on it Bug reassigned from package 'libgtk-3-0' to 'libpango-1.0-0'. No longer marked as found in versions gtk+3.0/3.24.22-1. Ignoring request to alter fixed

Bug#963652: Patch to build with current sphinx

Control: tags -1 patch Control: block 964387 by -1 Hi, I believe this issue also affects packages that use python3-m2r as build dependency. In the upstream repo there is a patch, which I have attached here. Kind regards, Benjamin diff --git

Processed: Patch to build with current sphinx

Processing control commands: > tags -1 patch Bug #963652 [src:python-m2r] python-m2r: FTBFS with Sphinx 3.1: TypeError: add_source_parser() takes 2 positional arguments but 3 were given Added tag(s) patch. > block 964387 by -1 Bug #964387 [src:python-aiosqlite] python-aiosqlite: Update the

Bug#968474: marked as done (Please include ocamlvars.mk to avoid FTBFS because of dh_dwz)

Your message dated Sun, 16 Aug 2020 15:22:36 + with message-id and subject line Bug#968474: fixed in pplacer 1.1~alpha19-3 has caused the Debian Bug report #968474, regarding Please include ocamlvars.mk to avoid FTBFS because of dh_dwz to be marked as done. This means that you claim that the

Bug#968509: linux-image-4.19.0-10-amd64: System hangs within a few minutes of booting

Package: src:linux Version: 4.19.132-1 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgraded from 4.19.0-9 to 4.19.0-10. * What exactly did you do

Bug#957858: marked as done (syslinux: ftbfs with GCC-10)

Your message dated Sun, 16 Aug 2020 15:04:29 + with message-id and subject line Bug#957858: fixed in syslinux 3:6.04~git20190206.bf6db5b4+dfsg1-3 has caused the Debian Bug report #957858, regarding syslinux: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem

Bug#968372: marked as done (libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit)

Your message dated Sun, 16 Aug 2020 14:36:08 + with message-id and subject line Bug#968337: fixed in pango1.0 1.46.0-2 has caused the Debian Bug report #968337, regarding libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit to be marked as done. This means that you claim that

Bug#968337: marked as done (libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit)

Your message dated Sun, 16 Aug 2020 14:36:08 + with message-id and subject line Bug#968337: fixed in pango1.0 1.46.0-2 has caused the Debian Bug report #968337, regarding libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit to be marked as done. This means that you claim that

Bug#957858: syslinux GCC-10 patch

I was kindly pointed to https://bugzilla.suse.com/show_bug.cgi?id=1166605#c5 privately (thanks!), which explains that __builtin_strlen is not actually a "builtin" and relying on that without providing a strlen implementation is not correct (and in fact broken with GCC-10). I'm updating the

Bug#968337: marked as pending in pango

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

Processing control commands: > tag -1 pending Bug #968337 [libpango-1.0-0] libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit Bug #968372 [libpango-1.0-0] libpango-1.0-0: ABI break in PangoRenderer, more serious on 32-bit Added tag(s) pending. Added tag(s) pending. -- 968337:

Bug#964908: tomcat9: Catalina fails to load due to missing MbeansDescriptorsIntrospectionSource

I concur that this seems to be fixed in 9.0.37-3. -- Michael Welsh Duggan (m...@md5i.com)

Bug#957496: Please build with llvm-9 (or more recent)

tags 968497 + patch thanks Le 16/08/2020 à 14:04, Stéphane Glondu a écrit : > astra-toolbox is one of the 3 packages (along with qtcreator and > oclgrind) that still depend on llvm-toolchain-8 (which FTBFS on all > architectures, see #957496), and that prevents removing it from > testing. It

Bug#968474: [Help] Re: Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

Le 16/08/2020 à 10:33, Andreas Tille a écrit : > I've fixed this in Git. However, when trying to build I get: > > + ocamlfind ocamlc -c -annot -w Z -package batteries -package csv -package > xmlm -package gsl -package sqlite3 -package zip -package mcl -thread -I > pplacer_src -I json_src -I

Bug#966301: guile oom test fails on ppc64el

Control: found -1 2.2.7+1-5 Adjusting version to the one in testing.

Processed: guile oom test fails on ppc64el

Processing control commands: > found -1 2.2.7+1-5 Bug #966301 [src:guile-2.2] guile oom test fails on ppc64el Marked as found in versions guile-2.2/2.2.7+1-5. -- 966301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966301 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#957496: Please build with llvm-9 (or more recent)

tags 968496 + patch thanks Le 16/08/2020 à 13:57, Stéphane Glondu a écrit : > oclgrind is one of the 3 packages (along with qtcreator and > astra-toolbox) that still depend on llvm-toolchain-8 (which FTBFS on > all architectures, see #957496), and that prevents removing it from > testing. It

Bug#967161: marked as done (libgtkdatabox: Unversioned Python removal in sid/bullseye)

Your message dated Sun, 16 Aug 2020 13:54:31 +0200 with message-id and subject line libgtkdatabox: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967161, regarding libgtkdatabox: Unversioned Python removal in sid/bullseye to be marked as done. This means that you

Bug#963648: closing 963648

close 963648 1.41.0-3 thanks

Processed: closing 963648

Processing commands for cont...@bugs.debian.org: > close 963648 1.41.0-3 Bug #963648 [src:nghttp2] nghttp2: FTBFS with Sphinx 3.1: Could not import extension sphinxcontrib.rubydomain (exception: cannot import name 'l_' from 'sphinx.locale'

Bug#968126: marked as done (mricron: FTBFS with fpc 3.2.0)

Your message dated Sun, 16 Aug 2020 11:18:24 + with message-id and subject line Bug#968126: fixed in mricron 0.20140804.1~dfsg.1-3.1 has caused the Debian Bug report #968126, regarding mricron: FTBFS with fpc 3.2.0 to be marked as done. This means that you claim that the problem has been

Bug#957496: qtcreator: link to library libclang-1.9 (instead libclang-1.8)

tags 966007 + patch thanks Antonio wrote: > I can't remove the old version of clang because it is a dependency of > qtcreator (and only he uses it): is it possible to recompile this package > with the next version of clang library? qtcreator is one of the 3 packages (along with oclgrind and

Bug#968121: marked as done (ddrescueview: FTBFS with fpc 3.2.0)

Your message dated Sun, 16 Aug 2020 11:03:31 + with message-id and subject line Bug#968121: fixed in ddrescueview 0.4~alpha3-4 has caused the Debian Bug report #968121, regarding ddrescueview: FTBFS with fpc 3.2.0 to be marked as done. This means that you claim that the problem has been

Bug#967012: marked as done (vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern)

Your message dated Sun, 16 Aug 2020 10:50:29 + with message-id and subject line Bug#967012: fixed in vmem 1.8-2 has caused the Debian Bug report #967012, regarding vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern to be marked as done. This means that you claim that the

Bug#961444: marked as done (grcompiler FTBFS on architectures where char is unsigned)

Your message dated Sun, 16 Aug 2020 10:03:29 + with message-id and subject line Bug#961444: fixed in grcompiler 5.2-2 has caused the Debian Bug report #961444, regarding grcompiler FTBFS on architectures where char is unsigned to be marked as done. This means that you claim that the problem

Bug#960120: node-yarnpkg: I found an older commit that still builds

Il 15/08/20 14:00, Pirate Praveen ha scritto: >> With this build: >> https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 > >> I get a different error while building: >> [17:58:12] Starting 'build'... >> 2420[17:58:13] Error: [BABEL] >>

Bug#968474: [Help] Re: Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

Control: tags -1 pending Control: tags -1 help On Sun, Aug 16, 2020 at 07:17:13AM +0200, Stéphane Glondu wrote: > As a workaround, an empty dh_dwz override has been added in the > /usr/share/ocaml/ocamlvars.mk snippet in dh-ocaml/1.1.2, which is > included in the debian/rules of most of packages

Processed: [Help] Re: Bug#968474: Please include ocamlvars.mk to avoid FTBFS because of dh_dwz

Processing control commands: > tags -1 pending Bug #968474 [src:pplacer] Please include ocamlvars.mk to avoid FTBFS because of dh_dwz Added tag(s) pending. > tags -1 help Bug #968474 [src:pplacer] Please include ocamlvars.mk to avoid FTBFS because of dh_dwz Added tag(s) help. -- 968474:

Bug#966964: marked as done (libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Sun, 16 Aug 2020 08:23:57 + with message-id and subject line Bug#966654: fixed in libgpiod 1.5.1-2 has caused the Debian Bug report #966654, regarding libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Bug#966964: marked as done (libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Sun, 16 Aug 2020 08:23:57 + with message-id and subject line Bug#966964: fixed in libgpiod 1.5.1-2 has caused the Debian Bug report #966964, regarding libgpiod: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Bug#966654: marked as done (libgpiod: symbol mismatches with gcc-10/O3 optimization)

Your message dated Sun, 16 Aug 2020 08:23:57 + with message-id and subject line Bug#966654: fixed in libgpiod 1.5.1-2 has caused the Debian Bug report #966654, regarding libgpiod: symbol mismatches with gcc-10/O3 optimization to be marked as done. This means that you claim that the problem

Bug#966654: marked as done (libgpiod: symbol mismatches with gcc-10/O3 optimization)

Your message dated Sun, 16 Aug 2020 08:23:57 + with message-id and subject line Bug#966964: fixed in libgpiod 1.5.1-2 has caused the Debian Bug report #966964, regarding libgpiod: symbol mismatches with gcc-10/O3 optimization to be marked as done. This means that you claim that the problem

Processed: bug 968438 is forwarded to https://bugs.kde.org/show_bug.cgi?id=425354

Processing commands for cont...@bugs.debian.org: > forwarded 968438 https://bugs.kde.org/show_bug.cgi?id=425354 Bug #968438 [okular] okular: Annotation menu displayed incorrectly Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=425354'. > thanks Stopping processing here.

Bug#962762: Should monotone-viz be removed from unstable?

reassign 962762 ftp.debian.org retitle 962762 RM: monotone-viz -- RoQA; obsolete, unmaintained thanks Adrian Bunk wrote: > Neither monotone-viz nor monotone are in the current stable, > and monotone was already removed from unstable. > > Should monotone-viz also be removed from unstable? Yes,

Bug#955066: marked as done (mako: FTBFS with Sphinx 2.4: Theme error: no theme named 'zzzeeksphinx' found (missing theme.conf?))

Your message dated Sun, 16 Aug 2020 16:24:44 +0900 with message-id <20200816162444.8f46dd0de6759dc067609...@clear-code.com> and subject line mako: FTBFS with Sphinx 2.4: Theme error: no theme named 'zzzeeksphinx' found (missing theme.conf?) has caused the Debian Bug report #955066, regarding

Processed: Re: Should monotone-viz be removed from unstable?

Processing commands for cont...@bugs.debian.org: > reassign 962762 ftp.debian.org Bug #962762 [monotone-viz] Should monotone-viz be removed from unstable? Bug reassigned from package 'monotone-viz' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #962762 to the same values

Bug#944601: marked as done (FTBFS with OCaml 4.08.1 (safe strings))

Your message dated Sun, 16 Aug 2020 07:33:23 + with message-id and subject line Bug#944601: fixed in ocamlviz 1.01-4 has caused the Debian Bug report #944601, regarding FTBFS with OCaml 4.08.1 (safe strings) to be marked as done. This means that you claim that the problem has been dealt

Bug#959624: marked as done (ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for nil:NilClass)

Your message dated Sun, 16 Aug 2020 16:26:24 +0900 with message-id and subject line Re: ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: has caused the Debian Bug report #959624, regarding ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for

Bug#961444: Fix for grcompiler FTBFS on architectures where char is unsigned

I've reworked the assert to be explicit about checking the integer range could fit in a signed 8 bit value in commit https://github.com/silnrsi/grcompiler/commit/a60a04691c42f3f99543c83f9911c84e44a268fe Hopefully this will fix the issue and it isn't really managing to generate an offset outside

Processed: Bug#944601 marked as pending in ocamlviz

Processing control commands: > tag -1 pending Bug #944601 [src:ocamlviz] FTBFS with OCaml 4.08.1 (safe strings) Added tag(s) pending. -- 944601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944601: marked as pending in ocamlviz

Control: tag -1 pending Hello, Bug #944601 in ocamlviz 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#961445: Fixes in upstream repo commits.

I believe the upstream commits 19c55e0 and 89fa0b3 in the upstream Github repo should fix this bug. I have tested this on

Bug#957496: Prevent migration of ocaml-{integers,ctypes} to testing

Hello, These bugs are still on topic and prevent ocaml-{integers,ctypes} from migrating to testing. Could you please fix them? Or have the faulty packages removed from testing. Cheers, -- Stéphane

Bug#964880: marked as done (npm: test failures in ppc64el and s390x)

Your message dated Sun, 16 Aug 2020 06:03:24 + with message-id and subject line Bug#964854: fixed in npm 6.14.7+ds-2 has caused the Debian Bug report #964854, regarding npm: test failures in ppc64el and s390x to be marked as done. This means that you claim that the problem has been dealt

Bug#964854: marked as done (npm: autopkgtests failures on s390x)

Your message dated Sun, 16 Aug 2020 06:03:24 + with message-id and subject line Bug#964854: fixed in npm 6.14.7+ds-2 has caused the Debian Bug report #964854, regarding npm: autopkgtests failures on s390x to be marked as done. This means that you claim that the problem has been dealt with.