Bug#1000184: marked as done (sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes network access despite proxy setting)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Nov 2021 07:52:22 + with message-id <20211122075222.41673ce6@felix.codehelp> and subject line Needs a fix in the package has caused the Debian Bug report #1000184, regarding sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes network access despite

Processed: Needs a fix in the package

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1000184 4.2.0-5 Bug #1000184 [sphinx-common] sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes network access despite proxy setting No longer marked as found in versions sphinx/4.2.0-5. > thanks Stopping processing

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

2021-11-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Nov 2021 07:48:55 + with message-id and subject line Bug#999539: fixed in python-quantities 0.12.4-2 has caused the Debian Bug report #999539, regarding python-quantities: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test -i

Bug#1000365: Current pyzmq not playing well with Python 3.10 ?

2021-11-21 Thread Julien Puydt
Package: python3-zmq Version: 22.3.0-1 Severity: grave I have issues updating packages nbconvert and jupyterlab-server, both of which because of autopkgtest failures, with the similar-looking backtrace: autopkgtest [08:13:59]: test autodep8-python3: [--- Testing with

Processed: raise severity of python3.10 bugs

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

Processed: closing 984283

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 984283 5.10.0~rc1-1 Bug #984283 [src:paraview] paraview: ftbfs with GCC-11 Marked as fixed in versions paraview/5.10.0~rc1-1. Bug #984283 [src:paraview] paraview: ftbfs with GCC-11 Marked Bug as done > thanks Stopping processing here.

Bug#984248: mygui: ftbfs with GCC-11

2021-11-21 Thread Steve Langasek
Package: mygui Followup-For: Bug #984248 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Control: tags -1 patch Attached please find a small patch to fix this build failure with gcc-11. -- Steve Langasek Give me a lever long enough and a Free OS

Processed: Re: mygui: ftbfs with GCC-11

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

Processed: tagging 988028

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 988028 + buster Bug #988028 [src:ruby-riddle] ruby-riddle FTBFS in buster: Mysql2::Error: Load data local infile forbidden Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 988028:

Bug#996212: Fix require dalli 3.x

2021-11-21 Thread Daniel Leidert
After having a look at the issue, the 2.x series is not compatible with Rails 6.1. We need to upload dalli 3.x instead. https://github.com/petergoldstein/dalli/issues/771 I checked and the 3.x series builds fine (except for one test which requires network access and must be disabled). Regards,

Processed: segyio: diff for NMU version 1.8.3-1.1

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tags 1000360 + pending Bug #1000360 [src:segyio] segyio: FTBFS with Python 3.10 Added tag(s) pending. -- 1000360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000360: segyio: diff for NMU version 1.8.3-1.1

2021-11-21 Thread Stefano Rivera
Control: tags 1000360 + pending Dear maintainer, I've prepared an NMU for segyio (versioned as 1.8.3-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Also filed as: https://salsa.debian.org/science-team/segyio/-/merge_requests/1 I'd really suggest a

Bug#996301: marked as done (ruby-jbuilder: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Nov 2021 02:38:50 + with message-id and subject line Bug#996301: fixed in ruby-jbuilder 2.10.0-2 has caused the Debian Bug report #996301, regarding ruby-jbuilder: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim

Bug#1000360: segyio: FTBFS with Python 3.10

2021-11-21 Thread Stefano Rivera
Source: segyio Version: 1.8.3-1 Severity: serious Tags: upstream patch Justification: FTBFS FTBFS with Python 3.10: Tests fail with: E AttributeError: module 'collections' has no attribute 'Mapping' See: https://buildd.debian.org/status/fetch.php?pkg=segyio=amd64=1.8.3-1%2Bb5=1637491602=0

Bug#984122: closing 984122

2021-11-21 Thread Joe Nahmias
close 984122 2.5.0+dfsg1-1 thanks Forgot to mark it closed in the changelog

Processed: closing 984122

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 984122 2.5.0+dfsg1-1 Bug #984122 [src:fceux] fceux: ftbfs with GCC-11 The source 'fceux' and version '2.5.0+dfsg1-1' do not appear to match any binary packages Marked as fixed in versions fceux/2.5.0+dfsg1-1. Bug #984122 [src:fceux] fceux:

Bug#996301: marked as pending in ruby-jbuilder

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

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

Processed: FTBFS: test failure: External MBEDTLS version mismatch

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > block -1 with 1000358 Bug #1000359 [src:python-biopython] FTBFS: test failure: External MBEDTLS version mismatch 1000359 was not blocked by any bugs. 1000359 was not blocking any bugs. Added blocking bug(s) of 1000359: 1000358 -- 1000359:

Bug#1000359: FTBFS: test failure: External MBEDTLS version mismatch

2021-11-21 Thread Stefano Rivera
Source: python-biopython Version: 1.79+dfsg-1 Severity: serious Justification: FTBFS Control: block -1 with 1000358 python-biopython FTBFS with tests failing like so: == FAIL: test_tblastx

Bug#1000357: ddcci-dkms: install and module build failure with Linux 5.15: error: initialization of 'void (*)(struct device *)' from incompatible pointer type 'int (*)(struct device *)' [-Werror=incom

2021-11-21 Thread Paul Wise
Package: ddcci-dkms Version: 0.4.1-1 Severity: serious When I try to install ddcci-dkms with linux-headers-amd64 5.15.3-1 installed, the installation fails because the build of the ddcci module fails because of an incompatible pointer type in the source code: $ sudo apt install

Bug#996304: marked as done (ruby-json-schema: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @ rb_sysopen - http://foo.bar/)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Nov 2021 01:51:20 + with message-id and subject line Bug#996304: fixed in ruby-json-schema 2.8.1-3 has caused the Debian Bug report #996304, regarding ruby-json-schema: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @

Processed: Bug#996304 marked as pending in ruby-json-schema

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996304 [src:ruby-json-schema] ruby-json-schema: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @ rb_sysopen - http://foo.bar/ Added tag(s) pending. -- 996304:

Bug#996304: marked as pending in ruby-json-schema

2021-11-21 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996304 in ruby-json-schema 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#996229: marked as done (ruby-flexmock: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 1, expected 0))

2021-11-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Nov 2021 01:04:28 + with message-id and subject line Bug#996229: fixed in ruby-flexmock 2.3.6-7 has caused the Debian Bug report #996229, regarding ruby-flexmock: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 1,

Bug#996229: marked as pending in ruby-flexmock

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

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996229 [src:ruby-flexmock] ruby-flexmock: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 1, expected 0) Added tag(s) pending. -- 996229:

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: 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#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

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

Processed: Bug#998607 marked as pending in gnome-logs

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998607 [src:gnome-logs] gnome-logs: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "tests" Added tag(s) pending. -- 998607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998607 Debian Bug Tracking System Contact ow...@bugs.debian.org

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:

Bug#997382: marked as done (theano: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 23:22:45 + with message-id and subject line Bug#997382: fixed in theano 1.0.5+dfsg-4 has caused the Debian Bug report #997382, regarding theano: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' to be marked as done. This means that

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

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#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:

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#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#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#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#996569: marked as done (getmail6 naming issues)

2021-11-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 22:34:14 + with message-id and subject line Bug#996569: fixed in getmail6 6.18.4-2 has caused the Debian Bug report #996569, regarding getmail6 naming issues to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: Bug#993616: gnome-software: cannot resolve http://ftp.us/debian.org

2021-11-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #993616 [gnome-software] gnome-software: cannot resolve http://ftp.us/debian.org Severity set to 'normal' from 'grave' > tags -1 moreinfo Bug #993616 [gnome-software] gnome-software: cannot resolve http://ftp.us/debian.org Added tag(s)

Bug#993616: gnome-software: cannot resolve http://ftp.us/debian.org

2021-11-21 Thread Gunnar Hjalmarsson
Control: severity -1 normal Control: tags -1 moreinfo Thanks for your report. To me it sounds as a temporary network issue. Can you please let us know whether it has worked as expected later? -- Regards, Gunnar Hjalmarsson

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

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

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

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

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

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

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

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#996222: marked as done (ruby-factory-bot: 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 18:39:06 + with message-id and subject line Bug#996222: fixed in ruby-factory-bot 6.2.0-1 has caused the Debian Bug report #996222, regarding ruby-factory-bot: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done.

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

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

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

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

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#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#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#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: 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:

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

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:

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

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#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: > > - >

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#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:

  1   2   >