Processed: Bug#1058449 marked as pending in rally

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058449 [src:rally] rally: FTBFS: KeyError: slice(0, -1, None) Added tag(s) pending. -- 1058449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058449: marked as pending in rally

2024-01-07 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058449 in rally 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#933981: cdrom: USB, KVM create connect/disconnect loop in level1 (repair) install

2024-01-07 Thread Daniel Hedstrom
On Mon, 05 Aug 2019 14:28:47 -0400 Tom Sullivan wrote: > Package: cdrom > Severity: grave > Tags: d-i > Justification: renders package unusable > > Dear Maintainer, > > * What led up to the situation? > > I had another machine that gave kernel panic while upgrading from Stretch to > Buster. Use

Processed: python-ase's autopkg tests fail with Python 3.12

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1056457 [src:python-ase] python-ase's autopkg tests fail with Python 3.12 Severity set to 'important' from 'serious' -- 1056457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056457 Debian Bug Tracking System Contact

Bug#1056457: python-ase's autopkg tests fail with Python 3.12

2024-01-07 Thread Graham Inggs
Control: severity -1 important Hi s3v Thank you for all the links to the upstream commits. I have applied them, and python-ase now builds successfully (closing #1056184). However, since spglib stopped building its extension for all supported Python versions (see #1057858) testing python-ase

Processed: Re: flint-arb: FTBFS: /<>/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1058814 [src:flint-arb] flint-arb: FTBFS: /<>/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration Added tag(s) upstream. > forwarded -1 https://github.com/fredrik-johansson/arb/issues/454 Bug

Bug#1058814: flint-arb: FTBFS: /<>/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration

2024-01-07 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/fredrik-johansson/arb/issues/454 -- http://fam-tille.de

Processed: retitle 1056461 to python3-future: (other packages)'s autopkg tests fail with Python 3.12

2024-01-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1056461 python3-future: (other packages)'s autopkg tests fail with > Python 3.12 Bug #1056461 [python3-future] python-canmatrix's autopkg tests fail with Python 3.12 Changed Bug title to 'python3-future: (other packages)'s autopkg tests

Processed: Re: Bug#1059663 closed by Thomas Goirand (Cloud not reproduce)

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1059663 {Done: Thomas Goirand } [src:python-editor] python-editor: autopkgtest failure with Python 3.12 Bug reopened Ignoring request to alter fixed versions of bug #1059663 to the same values previously set -- 1059663:

Bug#1059663: closed by Thomas Goirand (Cloud not reproduce)

2024-01-07 Thread Graham Inggs
Control: reopen -1 Still failing with python-editor/1.0.3-5. On Sun, 7 Jan 2024 at 15:48, Debian Bug Tracking System wrote: > I couldn't reproduce this. There's no autopkgtest in this package, but > the autopkgtest-pkg-python, which I believe is only doing an import of > the python module,

Bug#1000113: kodi: depends on obsolete pcre3 library

2024-01-07 Thread Vasyl Gello
Hi Yavor, Thanks for the patch! Greatly appreciated!!! Upstream we discussed the pcre PR and there is an old branch porting some stuff to std::regex. I have checked that branch but some problems remained. I can test your patch because I am both the user and the maintainer as you requested.

Processed: Re: Bug#1000113: kodi: depends on obsolete pcre3 library

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1000113 [src:kodi] kodi: depends on obsolete pcre3 library Added tag(s) patch. -- 1000113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000113: kodi: depends on obsolete pcre3 library

2024-01-07 Thread Yavor Doganov
Control: tags -1 + patch Please find attached a patch; I did my best to test it. I believe the changes to the CRegExp class (xbmc/utils/RegExp.*) are sane; they are tested in xbmc/utils/test/TestRegexp.cpp and some other test programs that use CRegExp. I added three more test cases: invalid

Bug#1057056: marked as done (rust-comrak: Unsatisfiable dependency on rust-emojis)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Mon, 8 Jan 2024 03:11:27 + with message-id <9ea89636-5ddc-4244-b904-04e30909d...@debian.org> and subject line rust-comrak: Unsatisfiable dependency on rust-emojis has caused the Debian Bug report #1057056, regarding rust-comrak: Unsatisfiable dependency on rust-emojis to be

Processed: Re: Processed (with 1 error): castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el

2024-01-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1060205 by 1056116 Bug #1060205 [src:castxml] castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el 1060205 was not blocked by any bugs. 1060205 was not blocking any bugs. Added blocking bug(s) of 1060205:

Bug#1060205: castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el

2024-01-07 Thread Étienne Mollier
Control: block -1 by #1056116 Hi Sebastian, > castxml build-depends on missing: > - libclang-17-dev:mips64el Thanks for the heads up, I'm afraid this is a bit out of hands right now. According to bug entries #1059465 and #1056116, llvm-toolchain-16 and -17 fail to build on mips64el at the

Bug#1058007: marked as done (python-wsaccel: runtime dependency on cython)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 18:52:03 + with message-id and subject line Bug#1058007: fixed in python-wsaccel 0.6.3-4 has caused the Debian Bug report #1058007, regarding python-wsaccel: runtime dependency on cython to be marked as done. This means that you claim that the problem has

Bug#1058378: marked as done (python-wsgi-intercept: FTBFS: failed tests)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 18:52:11 + with message-id and subject line Bug#1058378: fixed in python-wsgi-intercept 1.9.3-5 has caused the Debian Bug report #1058378, regarding python-wsgi-intercept: FTBFS: failed tests to be marked as done. This means that you claim that the problem

Bug#1058162: marked as done (manila: FTBFS: KeyError: slice(1, None, None))

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 18:27:10 + with message-id and subject line Bug#1058162: fixed in manila 1:17.1.0-1 has caused the Debian Bug report #1058162, regarding manila: FTBFS: KeyError: slice(1, None, None) to be marked as done. This means that you claim that the problem has been

Bug#1058007: marked as pending in python-wsaccel

2024-01-07 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058007 in python-wsaccel 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#1060005: cifs-utils: Copy file with cp, hangs with a kernel NULL pointer dereference.

2024-01-07 Thread JD Walsh
Package: src:linux Version: 6.1.69-1 Followup-For: Bug #1060005 Dear Maintainer, I'm running Debian 12 6.1.0-17, having recently upgraded from 6.1.0-16. On my machine, running cp on a file on my NAS causes the computer to hang for a few seconds before reporting "Killed". The cifs share becomes

Processed: Bug#1058007 marked as pending in python-wsaccel

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058007 [src:python-wsaccel] python-wsaccel: runtime dependency on cython Added tag(s) pending. -- 1058007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1058378 marked as pending in python-wsgi-intercept

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058378 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: failed tests Ignoring request to alter tags of bug #1058378 to the same tags previously set -- 1058378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058378 Debian Bug

Bug#1058378: marked as pending in python-wsgi-intercept

2024-01-07 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058378 in python-wsgi-intercept 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#1052800: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-07 Thread s3v
Control: forwarded -1 https://github.com/davidhalter/parso/issues/222 thanks Dear Maintainer, After adding:   export PYBUILD_BEFORE_TEST=cp conftest.py {build_dir} in debian/rules, tests pass with Python 3.11 but still fail with Python 3.12. I've opened an issue upstream. ... make[1]:

Processed: bug 1059675 is forwarded to https://github.com/tkaitchuck/aHash/issues/152

2024-01-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1059675 https://github.com/tkaitchuck/aHash/issues/152 Bug #1059675 [rust-ahash] rust-ahash - autopkgtest failure on s390x. Set Bug forwarded-to-address to 'https://github.com/tkaitchuck/aHash/issues/152'. > thanks Stopping processing

Processed: Re: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/davidhalter/parso/issues/222 Bug #1052800 [src:parso] parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Set Bug forwarded-to-address to

Bug#1059648: sip4: autopkgtest failure with Python 3.12

2024-01-07 Thread Dmitry Shachnev
Hi Gregor! On Sun, Jan 07, 2024 at 03:40:49PM +0100, Gregor Riepl wrote: > I can reproduce that, although I should mention that the segfault happens > during teardown, not when the module is loaded: > > >>> import sip > >>> print(sip) >

Bug#1060206: olive-editor: FTBFS: CMake Generate step failed.

2024-01-07 Thread Sebastian Ramacher
Source: olive-editor Version: 20230614+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=olive-editor=amd64=20230614%2Bds-1=1704354645=0 --

Bug#1060205: castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el

2024-01-07 Thread Sebastian Ramacher
Source: castxml Version: 0.6.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=castxml Dependency installability problem for castxml on mips64el:

Bug#1059648: sip4: autopkgtest failure with Python 3.12

2024-01-07 Thread Gregor Riepl
Hi Graham, sip4's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. [1] https://ci.debian.net/packages/s/sip4/testing/amd64/ 22s autopkgtest [20:09:51]: test autodep8-python3: [--- 22s Testing with python3.12: 22s 22s

Bug#1059663: marked as done (python-editor: autopkgtest failure with Python 3.12)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Jan 2024 14:44:56 +0100 with message-id <5a58950b-6048-4298-ad14-1e0062cfe...@debian.org> and subject line Cloud not reproduce has caused the Debian Bug report #1059663, regarding python-editor: autopkgtest failure with Python 3.12 to be marked as done. This means that

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-07 Thread Gregor Riepl
(sorry for the very late response, I only noticed your message just now) I did come to the conclusion that Werkzeug 2.3.x has some bigger changes that will break most of the existing packages in some way. The main differences to Werkzeug 3.x than isn't that big. Ok, that makes sense!

Processed: Bug#1058378 marked as pending in python-wsgi-intercept

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058378 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: failed tests Added tag(s) pending. -- 1058378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058378: marked as pending in python-wsgi-intercept

2024-01-07 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058378 in python-wsgi-intercept 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#1050896: marked as done (packagesearch: Incomplete/Misleading copyright file)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 12:34:10 + with message-id and subject line Bug#1050896: fixed in packagesearch 2.8.1 has caused the Debian Bug report #1050896, regarding packagesearch: Incomplete/Misleading copyright file to be marked as done. This means that you claim that the problem

Processed: Bug#1058248 marked as pending in python-diskimage-builder

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058248 [src:python-diskimage-builder] python-diskimage-builder: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1058248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058248 Debian Bug Tracking System Contact

Bug#1058248: marked as pending in python-diskimage-builder

2024-01-07 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058248 in python-diskimage-builder 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#1058083: Before I try to tackle this bug - can we move the package to DPT

2024-01-07 Thread Ulises Vitulli
Hey Andreas! Feel free to go ahead with my blessing right away! Cheers, \d ps: sorry for the delay, summer holidays in this part of the world! On 1/4/24 03:49, Andreas Tille wrote: Ping? If I do not hear from you in the next couple of days I'll move the package to DPT at beginning of next

Bug#1060174: marked as done (rust-lscolors FTBFS: error[E0560]: struct `nu_ansi_term::Style` has no field named `prefix_with_reset`)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 11:51:03 + with message-id and subject line Bug#1060174: fixed in rust-lscolors 0.16.0-2 has caused the Debian Bug report #1060174, regarding rust-lscolors FTBFS: error[E0560]: struct `nu_ansi_term::Style` has no field named `prefix_with_reset` to be

Bug#1056184: marked as done (python-ase: FTBFS: ERROR: Broken link: :git:`COPYING`: Non-existing path: ../COPYING)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 11:50:54 + with message-id and subject line Bug#1056184: fixed in python-ase 3.22.1-4 has caused the Debian Bug report #1056184, regarding python-ase: FTBFS: ERROR: Broken link: :git:`COPYING`: Non-existing path: ../COPYING to be marked as done. This

Processed: Bug#1058162 marked as pending in manila

2024-01-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058162 [src:manila] manila: FTBFS: KeyError: slice(1, None, None) Added tag(s) pending. -- 1058162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058162: marked as pending in manila

2024-01-07 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058162 in manila 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#1052844: deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-07 Thread s3v
Dear Maintainer, after adding:   export PYBUILD_BEFORE_TEST=cp conftest.py {build_dir} in debian/rules, I was able to build yout package in a sid chroot environment. Kind Regards

Bug#1057595: marked as done (publican: FTBFS: Failed 2/10 test programs)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Jan 2024 12:26:22 +0100 with message-id and subject line Re: Bug#1057595: publican: FTBFS: Failed 2/10 test programs has caused the Debian Bug report #1057595, regarding publican: FTBFS: Failed 2/10 test programs to be marked as done. This means that you claim that the

Processed: upstream patch available

2024-01-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1056440 + patch Bug #1056440 [src:pyopengl] pyopengl's autopkg tests fail with Python 3.12 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056440:

Bug#1058269: marked as done (python-pylxd: FTBFS: failed tests)

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 11:04:36 + with message-id and subject line Bug#1058269: fixed in python-pylxd 2.2.10-3 has caused the Debian Bug report #1058269, regarding python-pylxd: FTBFS: failed tests to be marked as done. This means that you claim that the problem has been dealt

Bug#1058258: marked as done (networking-sfc: FTBFS: KeyError: slice(1, None, None))

2024-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Jan 2024 10:50:38 + with message-id and subject line Bug#1058258: fixed in networking-sfc 17.0.0-2 has caused the Debian Bug report #1058258, regarding networking-sfc: FTBFS: KeyError: slice(1, None, None) to be marked as done. This means that you claim that the

Bug#999989: poco 1.1 uses PCRE3, Mumble 1.5 depends on poco

2024-01-07 Thread Jochen Sprickerhof
* Chris Knadle [2024-01-07 00:29]: The main thing I'd like to understand is how to do coordinate the transition (i.e. the release) with the Release Team. I found some hints about that here: https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#lib-trans The wiki page linked there