Processed: raise severity of python3.10 bugs

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 948018 serious Bug #948018 [src:getfem++] getfem++: b-d on python3-all-dev, but not built for all supported Python3 versions Bug #972349 [src:getfem++] b-d's on python3-all-dev, but only builds for the default python3 Severity set to

Processed: ecflow: silently fails to build python extension if boost is missing

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1000186 [src:ecflow] ecflow: silently fails to build python extension if boost is missing Severity set to 'serious' from 'normal' -- 1000186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000186 Debian Bug Tracking System Contact

Processed: bug 997069 is forwarded to https://jugit.fz-juelich.de/mlz/bornagain/-/commit/3b2a375f50c76a02ae9c41a9f328162350ab3583

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 997069 > https://jugit.fz-juelich.de/mlz/bornagain/-/commit/3b2a375f50c76a02ae9c41a9f328162350ab3583 Bug #997069 [src:bornagain] bornagain: FTBFS: Precomputed.h:29:11: error: ‘size_t’ has not been declared Set Bug forwarded-to-address

Bug#1000315: compreffor: FTBFS with Python 3.10

2021-11-21 Thread Stefano Rivera
Source: compreffor Version: 0.5.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=compreffor=amd64=0.5.1-1%2Bb1=1637495198=0 Tests fail with: ERRORS _ ERROR collecting

Processed: Re: Bug#1000318: docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/moby/moby/pull/43005 Bug #1000318 [src:docker.io] docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile Set Bug forwarded-to-address to 'https://github.com/moby/moby/pull/43005'. -- 1000318:

Bug#998569: marked as done (phosh: FTBFS: ../subprojects/libcall-ui/meson.build:1:0: ERROR: In subproject libcall-ui: Unknown options: "libcall-ui:package_name, libcall-ui:package_version, libcall-ui:

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 14:41:08 + with message-id and subject line Bug#998569: fixed in phosh 0.13.1-2 has caused the Debian Bug report #998569, regarding phosh: FTBFS: ../subprojects/libcall-ui/meson.build:1:0: ERROR: In subproject libcall-ui: Unknown options:

Processed: closing 997491

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 997491 Bug #997491 [src:plyvel] plyvel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#999405: marked as done (python-cytoolz ftbfs with Python 3.10 (test failures))

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 10:50:05 + with message-id and subject line Bug#999405: fixed in python-cytoolz 0.11.0-2 has caused the Debian Bug report #999405, regarding python-cytoolz ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the

Bug#996123: marked as pending in ruby-api-pagination

2021-11-21 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #996123 in ruby-api-pagination 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#996123 marked as pending in ruby-api-pagination

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996123 [src:ruby-api-pagination] ruby-api-pagination: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996123 Debian Bug Tracking System

Processed: Re: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1000146 serious Bug #1000146 [cppcheck] cppcheck: incorrect dependencies: libc6 should be >= 2.32 Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000146:

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-21 Thread Joachim Reichel
severity 1000146 serious thanks Hi Alejandro, I was able to reproduce the problem. It's unclear to me why "${shlibs:Depends}" does not produce a ">= 2.32" constraint and I've asked on the debian-mentors list for comments. Obviously, I could add that constraint manually, but I would first

Bug#984148: marked as done (gcc-avr: ftbfs with GCC-11)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 12:03:56 + with message-id and subject line Bug#984148: fixed in gcc-avr 1:5.4.0+Atmel3.6.2-2 has caused the Debian Bug report #984148, regarding gcc-avr: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt

Bug#1000315: compreffor: diff for NMU version 0.5.1-1.1

2021-11-21 Thread Stefano Rivera
Control: tags 1000315 + patch Control: tags 1000315 + pending Dear maintainer, I've prepared an NMU for compreffor (versioned as 0.5.1-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Also filed as an MR:

Processed: compreffor: diff for NMU version 0.5.1-1.1

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tags 1000315 + patch Bug #1000315 [src:compreffor] compreffor: FTBFS with Python 3.10 Added tag(s) patch. > tags 1000315 + pending Bug #1000315 [src:compreffor] compreffor: FTBFS with Python 3.10 Added tag(s) pending. -- 1000315:

Processed: tagging 998441

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 998441 + fixed-upstream patch Bug #998441 [src:reprozip] reprozip: FTBFS on 2nd reproducible build Added tag(s) patch and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 998441:

Bug#984270: Fix uploaded to salsa

2021-11-21 Thread Gard Spreemann
I believe Salsa commit ba393a45 [1] fixes this bug. However, other build problems relating to the shipped symbols prevent me from uploading the fixed version. [1] https://salsa.debian.org/deeplearning-team/onednn signature.asc Description: PGP signature

Processed: your mail

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 984270 fixed Bug #984270 [src:onednn] onednn: ftbfs with GCC-11 Added tag(s) fixed. > End of message, stopping processing here. Please contact me if you need assistance. -- 984270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984270

Bug#1000318: docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile

2021-11-21 Thread Shengjing Zhu
Control: forwarded -1 https://github.com/moby/moby/pull/43005 On Sun, Nov 21, 2021 at 9:18 PM Reinhard Tartler wrote: > > Source: docker.io > Version: 20.10.5+dfsg1-1 > Severity: serious > Justification: FTBFS - prevents depending packages from migrating > > the docker.io package FTBFS on mipsen

Bug#997609: marked as done (deap: FTBFS: error in deap setup command: use_2to3 is invalid.)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 14:35:38 + with message-id and subject line Bug#997609: fixed in deap 1.3.1-3 has caused the Debian Bug report #997609, regarding deap: FTBFS: error in deap setup command: use_2to3 is invalid. to be marked as done. This means that you claim that the

Bug#990224: [Pkg-pascal-devel] Bug#990224: Bug#990224: Bug#990224: leaves diversion after upgrade from sid to experimental

2021-11-21 Thread Abou Al Montacir
Hi Paul and All, On Wed, 2021-11-03 at 10:15 +0100, Abou Al Montacir wrote: > On Tue, 2021-11-02 at 22:52 +0100, Paul Gevers wrote: > > My point is that even if we replace the mechanism, we still need to > > remove the existing diversions from the version in testing, when > > upgrading to the

Bug#996123: marked as done (ruby-api-pagination: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 11:22:33 + with message-id and subject line Bug#996123: fixed in ruby-api-pagination 4.8.2-2 has caused the Debian Bug report #996123, regarding ruby-api-pagination: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as

Bug#1000317: cyvcf2: diff for NMU version 0.30.11-1.1

2021-11-21 Thread Stefano Rivera
Dear maintainer, I've prepared an NMU for cyvcf2 (versioned as 0.30.11-1.1). The diff is attached to this message. Also filed as https://salsa.debian.org/med-team/cyvcf2/-/merge_requests/1 Regards, SR diff -Nru cyvcf2-0.30.11/debian/changelog cyvcf2-0.30.11/debian/changelog ---

Bug#1000318: docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile

2021-11-21 Thread Reinhard Tartler
Source: docker.io Version: 20.10.5+dfsg1-1 Severity: serious Justification: FTBFS - prevents depending packages from migrating the docker.io package FTBFS on mipsen in the same way: - https://buildd.debian.org/status/fetch.php?pkg=docker.io=mips64el=20.10.10%2Bdfsg1-1=1636015943=0 -

Processed: qutip numpy

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 999517 qutip cannot build against numpy >= 1.20 Bug #999517 [src:qutip] qutip: FTBFS with numpy 1.21 (in experimental): distutils.errors.DistutilsError: Command '['/usr/bin/python3.9', '-m', 'pip', '--disable-pip-version-check',

Bug#997448: marked as done (mlpy: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 15:20:12 + with message-id and subject line Bug#997448: fixed in mlpy 3.5.0+ds-1.3 has caused the Debian Bug report #997448, regarding mlpy: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' to be marked as done. This means that you claim that the

Bug#997324: marked as done (pyliblo: FTBFS: ImportError: cannot import name 'PyClassmember' from 'sphinx.domains.python' (/usr/lib/python3/dist-packages/sphinx/domains/python.py))

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 15:35:24 + with message-id and subject line Bug#997324: fixed in pyliblo 0.10.0-5 has caused the Debian Bug report #997324, regarding pyliblo: FTBFS: ImportError: cannot import name 'PyClassmember' from 'sphinx.domains.python'

Bug#1000308: pycuda: FTBFS with Python 3.10

2021-11-21 Thread Graham Inggs
Source: pycuda Version: 2021.1~dfsg-1 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer I tried to do a manual binNMU of pycuda to add Python 3.10 as a supported version (#996584), but it failed. I've copied what I hope is the relevant part of

Bug#1000307: FTBFS: autopkgtest fails sue to missing socket.io module

2021-11-21 Thread Yadd
Package: node-http-proxy Severity: serious Tags: ftbfs socket.io module is missing in autopkgtest dependencies and unavailable in Debian

Processed: tagging 994304

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 994304 + ftbfs Bug #994304 [src:libgpuarray] libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 994304:

Bug#999535: marked as done (python-ltfatpy: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 10:35:48 + with message-id and subject line Bug#999535: fixed in python-ltfatpy 1.0.16-6 has caused the Debian Bug report #999535, regarding python-ltfatpy: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i

Bug#999516: marked as done (python-ltfatpy: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 10:35:48 + with message-id and subject line Bug#999516: fixed in python-ltfatpy 1.0.16-6 has caused the Debian Bug report #999516, regarding python-ltfatpy: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i

Processed: closing 996559

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 996559 2.22+dfsg-2 Bug #996559 [src:minimap2] minimap2 FTBFS on !x86 Marked as fixed in versions minimap2/2.22+dfsg-2. Bug #996559 [src:minimap2] minimap2 FTBFS on !x86 Marked Bug as done > thanks Stopping processing here. Please contact

Bug#1000317: cyvcf2: FTBFS with Python 3.10

2021-11-21 Thread Stefano Rivera
Source: cyvcf2 Version: 0.30.11-1 Severity: serious Tags: ftbfs patch Justification: FTBFS https://buildd.debian.org/status/fetch.php?pkg=cyvcf2=amd64=0.30.11-1%2Bb1=1637483151=0 Tests fail with: == ERROR:

Processed: notfound 1000318 in 20.10.5+dfsg1-1, found 1000318 in 20.10.10+dfsg1-1

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1000318 20.10.5+dfsg1-1 Bug #1000318 [src:docker.io] docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile No longer marked as found in versions docker.io/20.10.5+dfsg1-1. > found 1000318 20.10.10+dfsg1-1 Bug

Bug#997324: marked as pending in pyliblo

2021-11-21 Thread Sebastian Ramacher
Control: tag -1 pending Hello, Bug #997324 in pyliblo 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#997324 marked as pending in pyliblo

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997324 [src:pyliblo] pyliblo: FTBFS: ImportError: cannot import name 'PyClassmember' from 'sphinx.domains.python' (/usr/lib/python3/dist-packages/sphinx/domains/python.py) Added tag(s) pending. -- 997324:

Processed: update the bts with the right meta info

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 997878 src:python-softlayer 5.8.5-2 Bug #997878 {Done: Sandro Tosi } [src:python-click, src:python-softlayer] python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable Bug reassigned from package

Bug#983993: marked as done (binutils-avr: ftbfs with GCC-11)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 09:48:52 + with message-id and subject line Bug#983993: fixed in binutils-avr 2.26.20160125+Atmel3.6.2-3 has caused the Debian Bug report #983993, regarding binutils-avr: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem

Bug#993125: src:pcp: fails to migrate to testing for too long: RC bug

2021-11-21 Thread Petter Reinholdtsen
[Paul Gevers] > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. According to https://tracker.debian.org/pkg/pcp >, the auto-removal is not cancelled when this issue is fixed in unstable: * Migration

Bug#999410: marked as done (python-rocksdb ftbfs with Python 3.10)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 10:21:39 + with message-id and subject line Bug#999410: fixed in python-rocksdb 0.8.0~rc3-2 has caused the Debian Bug report #999410, regarding python-rocksdb ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been

Bug#997609: marked as pending in deap

2021-11-21 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #997609 in deap 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#997609 marked as pending in deap

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997609 [src:deap] deap: FTBFS: error in deap setup command: use_2to3 is invalid. Added tag(s) pending. -- 997609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000318: docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile

2021-11-21 Thread Reinhard Tartler
On 11/21/21 8:14 AM, Reinhard Tartler wrote: > Source: docker.io > Version: 20.10.5+dfsg1-1 > Severity: serious > Justification: FTBFS - prevents depending packages from migrating > > the docker.io package FTBFS on mipsen in the same way: > > - >

Bug#998569: marked as pending in phosh

2021-11-21 Thread Guido Günther
Control: tag -1 pending Hello, Bug #998569 in phosh 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#998569 marked as pending in phosh

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998569 [src:phosh] phosh: FTBFS: ../subprojects/libcall-ui/meson.build:1:0: ERROR: In subproject libcall-ui: Unknown options: "libcall-ui:package_name, libcall-ui:package_version, libcall-ui:pkgdatadir, libcall-ui:pkglibdir" Added tag(s)

Bug#997448: mlpy: diff for NMU version 3.5.0+ds-1.3

2021-11-21 Thread Stefano Rivera
Control: tags 997448 + patch Dear maintainer, I've prepared an NMU for mlpy (versioned as 3.5.0+ds-1.3). The diff is attached to this message. Also forwarded as https://salsa.debian.org/science-team/mlpy/-/merge_requests/3 Regards, SR diff -Nru mlpy-3.5.0+ds/debian/changelog

Processed: mlpy: diff for NMU version 3.5.0+ds-1.3

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tags 997448 + patch Bug #997448 [src:mlpy] mlpy: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' Added tag(s) patch. -- 997448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997448 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1000322: locking issues can lead to complete mail spool destruction

2021-11-21 Thread Antoine Beaupre
Package: syncmaildir Version: 1.3.0-1 Severity: grave Tags: upstream Forwarded: https://github.com/gares/syncmaildir/issues/18 I have experienced, twice, a situation in which SMD has attempted to destroy my entire mail spool. In both cases I noticed before it managed to delete it all, but it did

Bug#997260: marked as done (rstatd: FTBFS: rup.c:30:10: fatal error: rpc/rpc.h: No such file or directory)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 09:36:56 + with message-id and subject line Bug#997260: fixed in rstatd 4.0.1-11 has caused the Debian Bug report #997260, regarding rstatd: FTBFS: rup.c:30:10: fatal error: rpc/rpc.h: No such file or directory to be marked as done. This means that you

Bug#997069: marked as done (bornagain: FTBFS: Precomputed.h:29:11: error: ‘size_t’ has not been declared)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 13:03:54 + with message-id and subject line Bug#997069: fixed in bornagain 1.19.0-3 has caused the Debian Bug report #997069, regarding bornagain: FTBFS: Precomputed.h:29:11: error: ‘size_t’ has not been declared to be marked as done. This means that you

Bug#1000317: marked as done (cyvcf2: FTBFS with Python 3.10)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 13:04:08 + with message-id and subject line Bug#1000317: fixed in cyvcf2 0.30.11-1.1 has caused the Debian Bug report #1000317, regarding cyvcf2: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#999361: mypy ftbfs with python3.10 as supported (test failures)

2021-11-21 Thread Andrey Rahmatullin
On Wed, Nov 10, 2021 at 03:20:52PM +0100, Matthias Klose wrote: > mypy ftbfs with python3.10 as supported (test failures): > https://launchpadlibrarian.net/567976006/buildlog_ubuntu-jammy-amd64.mypy_0.910-3_BUILDING.txt.gz This just says "The typed_ast package is not installed." which sounds like

Bug#996487: marked as done (nbd-client: connects to localhost instead of the requested server)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 16:19:10 + with message-id and subject line Bug#996487: fixed in nbd 1:3.23-1 has caused the Debian Bug report #996487, regarding nbd-client: connects to localhost instead of the requested server to be marked as done. This means that you claim that the

Processed: Re: Bug#1000255: mpv: autopkgtest failures

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1000255 [src:mpv] mpv: autopkgtest failures Added tag(s) help. -- 1000255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000255: mpv: autopkgtest failures

2021-11-21 Thread Sebastian Ramacher
Control: tags -1 help On 2021-11-20 09:34:37 +0100, Gianfranco Costamagna wrote: > Source: mpv > Version: 0.34.0-1 > Severity: serious > > > Hello, the last version 0.34.0 is regressed on arm64 armhf and probably other > architectures. > > Look, e.g. >

Bug#996140: marked as pending in ruby-bogus

2021-11-21 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996140 in ruby-bogus 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#996140 marked as pending in ruby-bogus

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996140 [src:ruby-bogus] ruby-bogus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: # ArgumentError: Added tag(s) pending. -- 996140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996140 Debian Bug Tracking System Contact

Bug#999538: pytables: diff for NMU version 3.6.1-5.1

2021-11-21 Thread Antonio Valentino
Il 21/11/21 04:50, Stefano Rivera ha scritto: Control: tags 999538 + patch Control: tags 999538 + pending Dear maintainer, I've prepared an NMU for pytables (versioned as 3.6.1-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Also available as an MR:

Bug#1000268: marked as done (ros-ros-comm FTBFS on IPV6-only buildds)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 20:52:59 + with message-id and subject line Bug#1000268: fixed in ros-ros-comm 1.15.13+ds1-6 has caused the Debian Bug report #1000268, regarding ros-ros-comm FTBFS on IPV6-only buildds to be marked as done. This means that you claim that the problem has

Bug#1000184: Can dh_sphinxdoc disable intersphinx_mapping support?

2021-11-21 Thread Dmitry Shachnev
Hi Neil! On Fri, Nov 19, 2021 at 09:48:56AM +, Neil Williams wrote: > tag 1000184 - pending > thanks > > Does dh_sphinxdoc need to also disable https: or does > intersphinx_mapping have to be patched out of every package using Sphinx? dh_sphinxdoc is a packaging helper that is called *after*

Bug#998398: marked as done (FTBFS: very wrong python dependency)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 19:22:16 + with message-id and subject line Bug#998398: fixed in python-imgviz 1.4.1+ds-1 has caused the Debian Bug report #998398, regarding FTBFS: very wrong python dependency to be marked as done. This means that you claim that the problem has been

Processed: Bug#997459 marked as pending in hamradio-maintguide

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997459 [src:hamradio-maintguide] hamradio-maintguide: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' Added tag(s) pending. -- 997459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997459 Debian Bug Tracking System Contact

Bug#997459: marked as pending in hamradio-maintguide

2021-11-21 Thread Tony Mancill
Control: tag -1 pending Hello, Bug #997459 in hamradio-maintguide 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#1000336: numba: FTBFS with Python 3.10

2021-11-21 Thread Stefano Rivera
Source: numba Version: 0.52.0-5 Severity: serious Tags: ftbfs upstream Justification: FTBFS Forwarded: https://github.com/numba/numba/issues/7562 numba isn't compatible with Python 3.10, yet. Upstream is working on it, see https://github.com/numba/numba/issues/7562 setup.py immediately fails

Bug#1000337: pairtools: diff for NMU version 0.3.0-3.1

2021-11-21 Thread Stefano Rivera
Dear maintainer, I've prepared an NMU for pairtools (versioned as 0.3.0-3.1). The diff is attached to this message. Also filed as https://salsa.debian.org/med-team/pairtools/-/merge_requests/1 Regards, SR diff -Nru pairtools-0.3.0/debian/changelog pairtools-0.3.0/debian/changelog ---

Bug#1000340: bibtexconv: autopkgtest failure: "Tests" field is empty

2021-11-21 Thread Paul Gevers
Source: bibtexconv Version: 1.3.1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package bibtexconv, great. However, it fails. Currently this failure is blocking

Bug#1000350: macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring sing2)) -- SIGSEGV

2021-11-21 Thread Torrance, Douglas
Control: forwarded -1 https://github.com/Macaulay2/M2/issues/2318 Control: tags -1 pending On Sun 21 Nov 2021 05:37:27 PM EST, Sebastian Ramacher wrote: Source: macaulay2 Version: 1.19+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the

Bug#996297: Ruby 3 freezes Ranges by default

2021-11-21 Thread Daniel Leidert
The problem is caused by Ruby 3 freezing Ranges by default [1,2]. Thus the tests try to handle already frozen objects and some code is not working as well. I've forwarded the problem to upstream, but they have been inactive for some time. [1] https://bugs.ruby-lang.org/issues/15504 [2]

Processed: Re: Bug#1000350: macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring sing2)) -- SIGSEGV

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/Macaulay2/M2/issues/2318 Bug #1000350 [src:macaulay2] macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring sing2)) -- SIGSEGV Set Bug forwarded-to-address to 'https://github.com/Macaulay2/M2/issues/2318'. > tags -1

Processed: bug 996297 is forwarded to https://github.com/dkubb/ice_nine/issues/36, tagging 996297

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 996297 https://github.com/dkubb/ice_nine/issues/36 Bug #996297 [src:ruby-ice-nine] ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen Set Bug forwarded-to-address to

Bug#1000315: marked as pending in compreffor

2021-11-21 Thread Boyuan Yang
Control: tag -1 pending Hello, Bug #1000315 in compreffor 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#1000315 marked as pending in compreffor

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000315 [src:compreffor] compreffor: FTBFS with Python 3.10 Ignoring request to alter tags of bug #1000315 to the same tags previously set -- 1000315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000315 Debian Bug Tracking System Contact

Bug#993125: src:pcp: fails to migrate to testing for too long: RC bug

2021-11-21 Thread Paul Gevers
Hi Petter, Thanks for reaching out. On 21-11-2021 11:11, Petter Reinholdtsen wrote: This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. According to https://tracker.debian.org/pkg/pcp >, the

Bug#1000337: pairtools: FTBFS with Python 3.10

2021-11-21 Thread Stefano Rivera
Source: pairtools Version: 0.3.0-3 Severity: serious Tags: upstream patch Justification: FTBFS Forwarded: https://github.com/open2c/pairtools/pull/108 pairtools FTBFS with Python 3.10: == ERROR: pairtools

Bug#1000308: pycuda: FTBFS with Python 3.10

2021-11-21 Thread Andreas Beckmann
Control: forwarded -1 https://github.com/inducer/pycuda/issues/320 On 21/11/2021 09.24, Graham Inggs wrote: I tried to do a manual binNMU of pycuda to add Python 3.10 as a I believe that should be '-lboost_python310'. I ran into this yesterday trying to build everything with CUDA 11.5 ...

Processed: Re: Bug#1000308: pycuda: FTBFS with Python 3.10

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/inducer/pycuda/issues/320 Bug #1000308 [src:pycuda] pycuda: FTBFS with Python 3.10 Set Bug forwarded-to-address to 'https://github.com/inducer/pycuda/issues/320'. -- 1000308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000308

Bug#1000293: jackd2: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

2021-11-21 Thread Joenio Marques da Costa
Package: jackd2 Version: 1.9.19~dfsg-2 Severity: important The same error here in my Desktop environment. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux

Bug#1000336: numba: FTBFS with Python 3.10

2021-11-21 Thread Diane Trout
Thanks for the bug report and the forward, I'd managed to spot the build failures last night but only read the log files about why today. I subscribed to the upstream bug report. Diane On Sun, 2021-11-21 at 15:55 -0400, Stefano Rivera wrote: > Source: numba > Version: 0.52.0-5 > Severity:

Bug#1000350: macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring sing2)) -- SIGSEGV

2021-11-21 Thread Sebastian Ramacher
Source: macaulay2 Version: 1.19+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | -- making example results for "multiplicity" -- 0.516413 seconds elapsed | --

Bug#996382: marked as pending in ruby-seamless-database-pool

2021-11-21 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996382 in ruby-seamless-database-pool 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#996382 marked as pending in ruby-seamless-database-pool

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996382 [src:ruby-seamless-database-pool] ruby-seamless-database-pool: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996382 Debian Bug

Bug#1000348: macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i -> M(offset,n,1)), (10000,294)) < 1.5) -- timing test

2021-11-21 Thread Sebastian Ramacher
Source: macaulay2 Version: 1.19+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | testing: methods.m2 | | oo50 : FunctionClosure | | ii51 : assert(timer(M, (offset,296,1)) < 0.1) -- recursion test

Bug#996382: marked as done (ruby-seamless-database-pool: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:08:05 + with message-id and subject line Bug#996382: fixed in ruby-seamless-database-pool 1.0.20-2 has caused the Debian Bug report #996382, regarding ruby-seamless-database-pool: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to

Bug#996140: marked as done (ruby-bogus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: # ArgumentError:)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:35:54 + with message-id and subject line Bug#996140: fixed in ruby-bogus 0.1.6-3 has caused the Debian Bug report #996140, regarding ruby-bogus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: # ArgumentError: to be marked as done. This means

Bug#1000348: macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i -> M(offset,n,1)), (10000,294)) < 1.5) -- timing test

2021-11-21 Thread Torrance, Douglas
Control: forwarded -1 https://github.com/Macaulay2/M2/issues/2206 Control: tags -1 pending On Sun 21 Nov 2021 05:36:05 PM EST, Sebastian Ramacher wrote: Source: macaulay2 Version: 1.19+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the

Processed: Re: Bug#1000348: macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i -> M(offset,n,1)), (10000,294)) < 1.5) -- timing test

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/Macaulay2/M2/issues/2206 Bug #1000348 [src:macaulay2] macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i -> M(offset,n,1)), (1,294)) < 1.5) -- timing test Set Bug forwarded-to-address to

Processed: owner 997459, owner 916478, owner 986960

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 997459 tmanc...@debian.org Bug #997459 [src:hamradio-maintguide] hamradio-maintguide: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' Owner recorded as tmanc...@debian.org. > owner 916478 tmanc...@debian.org Bug #916478

Bug#997459: marked as done (hamradio-maintguide: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 20:46:09 + with message-id and subject line Bug#997459: fixed in hamradio-maintguide 0.7 has caused the Debian Bug report #997459, regarding hamradio-maintguide: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' to be marked as done. This means

Bug#1000337: marked as done (pairtools: FTBFS with Python 3.10)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 20:46:42 + with message-id and subject line Bug#1000337: fixed in pairtools 0.3.0-3.1 has caused the Debian Bug report #1000337, regarding pairtools: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt

Bug#997026: marked as done (libgpuarray: FTBFS with sphinx 4.2.0)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:20:06 + with message-id and subject line Bug#997026: fixed in libgpuarray 0.7.6-7 has caused the Debian Bug report #997026, regarding libgpuarray: FTBFS with sphinx 4.2.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#994304: marked as done (libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:20:06 + with message-id and subject line Bug#994304: fixed in libgpuarray 0.7.6-7 has caused the Debian Bug report #994304, regarding libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim that

Bug#998607: marked as done (gnome-logs: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "tests")

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:48:41 + with message-id and subject line Bug#998607: fixed in gnome-logs 3.36.0-3 has caused the Debian Bug report #998607, regarding gnome-logs: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "tests" to be marked as done. This means that you claim

Bug#998528: marked as done (file-roller: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "magic")

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:48:35 + with message-id and subject line Bug#998528: fixed in file-roller 3.40.0-3 has caused the Debian Bug report #998528, regarding file-roller: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "magic" to be marked as done. This means that you

Bug#997104: marked as done (ascd: FTBFS: ar: libdeps specified more than once)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 19:29:17 +0100 with message-id and subject line has caused the Debian Bug report #997104, regarding ascd: FTBFS: ar: libdeps specified more than once to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: Re: Bug#999543: devscripts: uscan crash with cmus package

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 1000210 -1 Bug #1000210 [devscripts] [regression] uscan die: filenamemangle failed Bug #999543 [devscripts] devscripts: uscan crash with cmus package Severity set to 'serious' from 'important' Bug #1000210 [devscripts] [regression] uscan die:

Bug#1000315: marked as done (compreffor: FTBFS with Python 3.10)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 19:34:18 + with message-id and subject line Bug#1000315: fixed in compreffor 0.5.1-2 has caused the Debian Bug report #1000315, regarding compreffor: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt

Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

2021-11-21 Thread Paul Gevers
Source: r-cran-raster, r-cran-satellite Control: found -1 r-cran-raster/3.5-2-1 Control: found -1 r-cran-satellite/1.0.4-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a

Processed: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > found -1 r-cran-raster/3.5-2-1 Bug #1000339 [src:r-cran-raster, src:r-cran-satellite] r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend' Marked as found in versions r-cran-raster/3.5-2-1. > found -1

Bug#998607: marked as pending in gnome-logs

2021-11-21 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #998607 in gnome-logs 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:

  1   2   >