Bug#1060138: marked as done (vlc-plugin-bittorrent: track vlc plugin ABI)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 07:50:03 + with message-id and subject line Bug#1060138: fixed in vlc-plugin-bittorrent 2.15-1 has caused the Debian Bug report #1060138, regarding vlc-plugin-bittorrent: track vlc plugin ABI to be marked as done. This means that you claim that the problem

Processed: bug 1056522 is forwarded to https://github.com/Textualize/rich/pull/2968 ...

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1056522 https://github.com/Textualize/rich/pull/2968 Bug #1056522 [src:rich] rich's autopkg tests fail with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/Textualize/rich/pull/2968'. > forwarded 1058314

Processed: unblock 1055955 with 1042845 1040396

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # only in sid > unblock 1055955 with 1042845 1040396 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1060653 1042844 1060323 1042845 1057318 1060456 1026046 1057424 1042853 1040396 1060458 1042521 1054793 1042525

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

2024-01-11 Thread Antonio Valentino
On Fri, 12 Jan 2024 08:07:41 +0100 s3v wrote: Dear Maintainer, > E   If you are not working on Numba development, the original error was: 'cannot import name '_typeconv' from 'numba.core.typeconv' (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > E   For help, please

Processed: block 1055955 with 1060653

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1055955 with 1060653 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1057270 1050451 1042844 1042521 1060458 1042525 1054793 1042845 1057424 1026046 1060456 1042853 1040396 1057318 1060323 1054776 1055955

Bug#1060653: os-autoinst: FTBFS on i386: t/01-test_needle.t failure

2024-01-11 Thread Niko Tyni
Source: os-autoinst Version: 4.6.1699947509.970d0609-1 Severity: serious Tags: ftbfs This package failed to build against Perl 5.38 in sid on i386 with three retries so far. The issue is currently a blocker for the ongoing Perl 5.38 transition. Latest log is at

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

2024-01-11 Thread s3v
Dear Maintainer, > E   If you are not working on Numba development, the original error was: > 'cannot import name '_typeconv' from 'numba.core.typeconv' > (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > E   For help, please visit: > E    > E   >

Processed: [mutagen] Bug #1042647: forward to upstream fix

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1042647 > https://github.com/quodlibet/mutagen/commit/37b4e6bddc03e1f71542 Bug #1042647 [src:mutagen] mutagen: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting Set Bug

Bug#1059040: libxml2: ABI change? (undefined references)

2024-01-11 Thread Rafael Laboissière
Rafael * Rene Engelhard [2023-12-25 23:48]: Hi, Am 25.12.23 um 22:57 schrieb Rene Engelhard: I didn't file it for the plain build issue. Nevertheless, if it broke so many projects you probably should do a full-fledged rebuild and send Well, mitigated by 2.12.3, but still. But again,

Processed: bug 1058340 is forwarded to https://github.com/mkdocstrings/python/issues/121

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1058340 https://github.com/mkdocstrings/python/issues/121 Bug #1058340 [src:mkdocstrings-python-handlers] mkdocstrings-python-handlers: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Bug#1060323: marked as done (libosp-dev: missing dependency on libosp5)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 04:35:14 + with message-id and subject line Bug#1060323: fixed in opensp 1.5.2-15 has caused the Debian Bug report #1060323, regarding libosp-dev: missing dependency on libosp5 to be marked as done. This means that you claim that the problem has been dealt

Bug#1059634: marked as done (pythran: autopkgtest failure with Python 3.12)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 03:21:07 + with message-id and subject line Bug#1059634: fixed in pythran 0.14.0+ds-5 has caused the Debian Bug report #1059634, regarding pythran: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem has

Processed: Bug#1059634 marked as pending in pythran

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1059634 [src:pythran] pythran: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1059634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1059634: marked as pending in pythran

2024-01-11 Thread Drew Parsons
Control: tag -1 pending Hello, Bug #1059634 in pythran 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: Re: nautilus: tracker build test failure

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1050733 normal Bug #1050733 [src:nautilus] nautilus: tracker build test failure Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1050733:

Bug#1026046: marked as done (libdevel-mat-perl: FTBFS: test failures on some architectures)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jan 2024 00:25:16 + with message-id and subject line Bug#1026046: fixed in libdevel-mat-perl 0.51-2 has caused the Debian Bug report #1026046, regarding libdevel-mat-perl: FTBFS: test failures on some architectures to be marked as done. This means that you claim

Bug#1059978: rosegarden: team uploading and git committed changes

2024-01-11 Thread Stuart Prescott
Hi Gianfranco On 08/01/2024 23:01, Gianfranco Costamagna wrote: I've prepared an Team upload for rosegarden (versioned as 1:22.12.1-2) and uploaded it to DELAYED/15. Please feel free to tell me if I should delay it longer. Excellent - many thanks for the patch, commit to git, and upload!

Bug#1033258: marked as done (upx-ucl: CVE-2023-23456)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 23:20:23 + with message-id and subject line Bug#1033258: fixed in upx-ucl 4.2.2-1 has caused the Debian Bug report #1033258, regarding upx-ucl: CVE-2023-23456 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1058517: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2

2024-01-11 Thread Bastian Germann
Control: forwarded -1 https://hg.jcea.es/dvdisaster/rev/03a51becc4c8 Please import this upstream patch to fix this.

Processed: Re: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://hg.jcea.es/dvdisaster/rev/03a51becc4c8 Bug #1058517 [src:dvdisaster] dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2 Set Bug forwarded-to-address to 'https://hg.jcea.es/dvdisaster/rev/03a51becc4c8'. -- 1058517:

Bug#1059869: autopkgtest fails

2024-01-11 Thread Bastian Germann
Ping. It is now 1 week until this will auto-remove several packages. Please consider releasing and packaging the new release.

Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf

2024-01-11 Thread Emanuele Rocca
Hi Julian, On 2024-01-11 05:46, Julian Andres Klode wrote: > And there aren't any hard errors. We could zero initialize > those or add supressions to make things look nicer I suppose. Mmmh no, they are all actual errors as far as valgrind is concerned. The thing is, you're running valgrind

Bug#1060458: perl-tk: FTBFS with Perl 5.38 on big-endian 64-bit: test failures

2024-01-11 Thread gregor herrmann
On Thu, 11 Jan 2024 21:29:50 +0200, Niko Tyni wrote: > This is currently a hard blocker for the ongoing Perl 5.38 transition as > perl-tk has quite a few reverse dependencies that are now uninstallable > on s390x. Georges, in case you don't find the time to upload a fixed package, I'm happy to

Bug#1052844: marked as done (deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 20:50:29 + with message-id and subject line Bug#1052844: fixed in deepdiff 6.7.1-1 has caused the Debian Bug report #1052844, regarding deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to

Bug#1026046: FTBFS: test failures on some architectures

2024-01-11 Thread gregor herrmann
On Thu, 11 Jan 2024 21:50:33 +0200, Niko Tyni wrote: > Either it's gotten worse or it's just bad luck, but previously built > archs (armhf and armel) are now failing, making this release critical > and blocking the Perl 5.38 transition. I also noticed that the new failures are slightly different

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

2024-01-11 Thread s3v
Dear Maintainer, I've successfully built your package locally after commenting these lines [1]. I guess is safe to stop treating warning as errors for downstream users. Kind Regards [1] https://sources.debian.org/src/python-itsdangerous/2.1.2-3/setup.cfg/#L40-L41

Processed: Bug#1052849 marked as pending in python-pkginfo

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1052849 [src:python-pkginfo] python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Added tag(s) pending. -- 1052849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052849

Bug#1052849: marked as pending in python-pkginfo

2024-01-11 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1052849 in python-pkginfo 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#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-11 Thread Stefano Rivera
Hi Andreas (2024.01.11_17:48:43_+) > I've fixed the two other bugs in python-pkginfo and upgraded to latest > upstream. Unfortunately I have no clue about this issue. The test is expecting the module to be installed in the test environment. Either we could try harder to emulate that, or skip

Processed: Re: importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdat

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #1052903 [src:importlib-resources] importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdata01/ziptestdata.zip' Added

Bug#1052903: importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdata0

2024-01-11 Thread Andreas Tille
Control: tags -1 moreinfo Control: tags -1 unreproducible Control: severity -1 important Hi, I've tried to reproduce the issue but failed in my local pbuilder. May be that issue vanished somehow? Kind regards Andreas. -- http://fam-tille.de

Processed: Re: Bug#1026046: FTBFS: test failures on some architectures

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.51-1 Bug #1026046 [src:libdevel-mat-perl] libdevel-mat-perl: FTBFS: test failures on some architectures Marked as found in versions libdevel-mat-perl/0.51-1. > severity -1 serious Bug #1026046 [src:libdevel-mat-perl] libdevel-mat-perl: FTBFS: test

Bug#1037883: vimix: ftbfs with GCC-13

2024-01-11 Thread Bastian Germann
This should be resolved with the current upstream release.

Bug#1060459: scalpel: Scalpel not working on Apple Silicon

2024-01-11 Thread Golden G. Richard III
Package: scalpel Version: 1.60-10 Severity: grave Tags: patch Justification: renders package unusable X-Debbugs-Cc: goldenrich...@gmail.com Dear Maintainer, * What led up to the situation? I am the author of Scalpel. Execution of Scalpel 1.60 (the version that is currently in the scalpel

Processed: block 1055955 with 1060458

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1055955 with 1060458 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1042844 1054776 1050451 1057318 1060323 1042845 1057270 1040396 1042853 1057424 1042525 1042521 1054793 1055955 was not blocking any bugs.

Bug#1060458: perl-tk: FTBFS with Perl 5.38 on big-endian 64-bit: test failures

2024-01-11 Thread Niko Tyni
Source: perl-tk Version: 1:804.036+dfsg1-1 Severity: serious Tags: ftbfs patch User: debian-p...@lists.debian.org Usertags: perl-5.38-transition This package failed to build against Perl 5.38 on s390x, ppc64, sparc64, and alpha. This is because Perl upstream changed the implementation of SvPV()

Processed: Re: awscli: Please drop python-cryptography upper limit or increase it

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Added tag(s) patch. -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1060455: awscli: Please drop python-cryptography upper limit or increase it

2024-01-11 Thread Jeremy Bícha
Control: tags -1 + patch There is a diff at https://launchpad.net/ubuntu/+source/awscli/2.14.6-1ubuntu1 for this issue. You can ignore the build failure since that doesn't seem to currently affect Debian Unstable. Thank you, Jeremy Bícha

Bug#1060266: python3-ykman: Package uninstallable

2024-01-11 Thread Jeremy Bícha
Florian, I see you have a newer version of yubikey-manager staged in Salsa that would fix this RC bug. Could you either upload that version or upload a targeted fix for this issue? Thank you, Jeremy Bícha

Processed: [python-bottle] Bug #1058087: forward to upstream fix

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1058087 https://github.com/bottlepy/bottle/issues/1378 Bug #1058087 [src:python-bottle] python-bottle: FTBFS: ImportError: cannot import name 'test' from 'bottle.ext' (/<>/bottle.py) Set Bug forwarded-to-address to

Bug#1055707: marked as done (python-acora fbfs with Python 3.12)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 19:05:57 + with message-id and subject line Bug#1055707: fixed in python-acora 2.4-0.1 has caused the Debian Bug report #1055707, regarding python-acora fbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Bug#1056849: marked as done (python-acora: ftbfs with cython 3.0.x)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 19:05:57 + with message-id and subject line Bug#1056849: fixed in python-acora 2.4-0.1 has caused the Debian Bug report #1056849, regarding python-acora: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been

Processed: Re: python3-ykman: Package uninstallable

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch upstream fixed-upstream Bug #1060266 [python3-ykman] python3-ykman: Package uninstallable Added tag(s) upstream, patch, and fixed-upstream. -- 1060266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060266 Debian Bug Tracking System Contact

Bug#1060266: python3-ykman: Package uninstallable

2024-01-11 Thread Jeremy Bícha
Control: tags -1 patch upstream fixed-upstream Please adapt this upstream commit to fix this issue: https://github.com/Yubico/yubikey-manager/commit/4990bc2bc Thank you, Jeremy Bícha

Processed: awscli: Please drop python-cryptography upper limit or increase it

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/aws/aws-cli/issues/5943 Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Set Bug forwarded-to-address to 'https://github.com/aws/aws-cli/issues/5943'. -- 1060455:

Bug#1060455: awscli: Please drop python-cryptography upper limit or increase it

2024-01-11 Thread Jeremy Bícha
Source: awscli Version: 2.14.6-1 Severity: serious Control: forwarded -1 https://github.com/aws/aws-cli/issues/5943 awscli is not installable in Debian Unstable because python-cryptography has been updated to a newer version than permitted in awscli's dependencies. I recommend dropping the upper

Bug#1055707: python-acora fbfs with Python 3.12

2024-01-11 Thread Bastian Germann
I am sponsoring a NMU that fixes this issue. The changes can be found in git.

Bug#1042663: marked as done (pygtkspellcheck: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 18:04:48 + with message-id and subject line Bug#1042663: fixed in pygtkspellcheck 5.0.3-1 has caused the Debian Bug report #1042663, regarding pygtkspellcheck: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as

Bug#1060449: completely wrong version number reported

2024-01-11 Thread ahs3
Package: imapfilter Version: 1:2.8.2-1 Severity: serious The imapfilter package is listed as 2.8.2. However, the version reported is: $ /usr/bin/imapfilter -V IMAPFilter 2.7.1 Copyright (c) 2001-2020 Eleftherios Chatzimparmpas While this is mostly annoying, I've run into the following problem

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

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1052849 [src:python-pkginfo] python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Added tag(s) help. -- 1052849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052849

Bug#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-11 Thread Andreas Tille
Control: tags -1 help Hi, I've fixed the two other bugs in python-pkginfo and upgraded to latest upstream. Unfortunately I have no clue about this issue. Any idea what might be wrong here? Kind regards Andreas. -- http://fam-tille.de

Processed: Re: python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1042599 [src:python-pkginfo] python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) pending. > block -1 by 1052849 Bug #1042599 [src:python-pkginfo] python-pkginfo: FTBFS with Sphinx 7.1,

Bug#1042599: python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'

2024-01-11 Thread Andreas Tille
Control: tags -1 pending Control: block -1 by 1052849 -- http://fam-tille.de

Processed: [bts-link] source package src:numpydoc

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:numpydoc > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#1057935: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.3

2024-01-11 Thread Sudip Mukherjee
Control: tags 1057935 + pending -- Dear maintainer, I've prepared an NMU for ncurses-hexedit (versioned as 0.9.7+orig-7.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. -- Regards Sudip diff -Nru ncurses-hexedit-0.9.7+orig/debian/changelog

Processed: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.3

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags 1057935 + pending Bug #1057935 [src:ncurses-hexedit] ncurses-hexedit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’} Added tag(s) pending. -- 1057935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057935 Debian Bug Tracking

Bug#1058296: marked as done (ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 17:05:03 + with message-id and subject line Bug#1058296: fixed in ostree-push 1.0.1-4 has caused the Debian Bug report #1058296, regarding ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1060377: marked as done (nut-modbus has an undeclared file conflict on /lib/nut/apc_modbus)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 16:50:08 + with message-id and subject line Bug#1060377: fixed in nut 2.8.1-3 has caused the Debian Bug report #1060377, regarding nut-modbus has an undeclared file conflict on /lib/nut/apc_modbus to be marked as done. This means that you claim that the

Bug#1058296: marked as done (ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 16:50:16 + with message-id and subject line Bug#1058296: fixed in ostree-push 1.0.1-3 has caused the Debian Bug report #1058296, regarding ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf

2024-01-11 Thread Julian Andres Klode
On Thu, Jan 11, 2024 at 03:53:17PM +0100, Emanuele Rocca wrote: > Hi Julian, > > On 2024-01-08 10:28, Julian Andres Klode wrote: > > (in Ubuntu we have partially recovered by disabling stack clash > > protection but it crashes on invalid writes there, I suppose we need > > to rebuild some more

Bug#1057930: cunit: diff for NMU version 2.1-3-dfsg-2.7

2024-01-11 Thread Sudip Mukherjee
Control: tags 1057930 + pending -- Dear maintainer, I've prepared an NMU for cunit (versioned as 2.1-3-dfsg-2.7) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. -- Regards Sudip diff -Nru cunit-2.1-3-dfsg/debian/changelog

Processed: cunit: diff for NMU version 2.1-3-dfsg-2.7

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags 1057930 + pending Bug #1057930 [src:cunit] cunit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’} Added tag(s) pending. -- 1057930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057930 Debian Bug Tracking System Contact

Bug#1060072: marked as done (RM: fheroes2-pkg -- RoQA; Replaced by DFSG-free fheroes2)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 17:11:58 +0100 with message-id and subject line duplicate RM request has caused the Debian Bug report #1060072, regarding RM: fheroes2-pkg -- RoQA; Replaced by DFSG-free fheroes2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1058329: ipxe: FTBFS: arch/x86/core/patch_cf.S:26: Error: 64bit mode not supported on `i386'.

2024-01-11 Thread Ciaran Anscomb
I was able to `make bin-x86_64-efi/ipxe.efi` by commenting out ".arch i386" (and sometimes i486 or i586) lines in various .S files under arch/x86/ The result netbooted fine and did the job. I assume something changed in the compiler or assembler at some point, so this is only a pointer in that

Bug#1060440: marked as done (llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 16:03:43 + with message-id and subject line Bug#1060440: fixed in llvm-toolchain-17 1:17.0.6-5 has caused the Debian Bug report #1060440, regarding llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel to be marked as done. This means that you claim that the

Bug#1058099: pyro4: FTBFS: AttributeError: 'CoreTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? debdiff for NMU

2024-01-11 Thread GCS
Hi Thomas, On Thu, Jan 11, 2024 at 4:57 PM Thomas Goirand wrote: > Please see attached diff to fix the issue. It's kind of trivial to fix, > as you may see... Could you please upload it to unstable ASAP, or allow > me to NMU this fix? I'll upload it ASAP. But what's your intention with keeping

Bug#1060440: llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel

2024-01-11 Thread Faidon Liambotis
On Thu, Jan 11, 2024 at 01:02:47PM +, Simon McVittie wrote: > It looks as though these are already known and already fixed in the > packaging git repo. Correct. I introduced these breakages with a couple of recent MRs, and hopefully fixed them with #130. I asked Sylvestre to hold off until we

Bug#1058099: pyro4: FTBFS: AttributeError: 'CoreTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? debdiff for NMU

2024-01-11 Thread Thomas Goirand
Hi Laszlo, Please see attached diff to fix the issue. It's kind of trivial to fix, as you may see... Could you please upload it to unstable ASAP, or allow me to NMU this fix? Cheers, Thomas Goirand (zigo)diff -Nru pyro4-4.82/debian/changelog pyro4-4.82/debian/changelog ---

Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf

2024-01-11 Thread Emanuele Rocca
Hi Julian, On 2024-01-08 10:28, Julian Andres Klode wrote: > (in Ubuntu we have partially recovered by disabling stack clash > protection but it crashes on invalid writes there, I suppose we need > to rebuild some more apt dependencies without the flag...). The 'invalid writes' issue seems

Bug#1042700: marked as done (python-padme: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 14:37:13 + with message-id and subject line Bug#1042700: fixed in python-padme 1.1.1-5 has caused the Debian Bug report #1042700, regarding python-padme: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done.

Bug#1053328: marked as done (pycryptodome: Baseline violation on i386 and test FTBFS on !x86)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 13:51:37 + with message-id and subject line Bug#1053328: fixed in pycryptodome 3.20.0+dfsg-1 has caused the Debian Bug report #1053328, regarding pycryptodome: Baseline violation on i386 and test FTBFS on !x86 to be marked as done. This means that you

Bug#1056436: marked as done (pycryptodome's autopkg tests fail with Python 3.12)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 13:51:37 + with message-id and subject line Bug#1056436: fixed in pycryptodome 3.20.0+dfsg-1 has caused the Debian Bug report #1056436, regarding pycryptodome's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Bug#1042650: marked as done (python-whoosh: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 13:51:46 + with message-id and subject line Bug#1042650: fixed in python-whoosh 2.7.4+git6-g9134ad92-8 has caused the Debian Bug report #1042650, regarding python-whoosh: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be

Bug#1059875: RM: rJava [i386] -- RoM: FTBFS as i386 builds no longer maintained upstream

2024-01-11 Thread Dirk Eddelbuettel
( Resending to now correctly-typed package r-cran-rcdklibs -- Dirk ) On 11 January 2024 at 07:09, Dirk Eddelbuettel wrote: | | Package: ftp.debian.org | Severity: normal | | The rJava package (source package 'rjava', binary package r-cran-rjava) no | longer builds on i386 as most of the

Bug#1059875: RM: rJava [i386] -- RoM: FTBFS as i386 builds no longer maintained upstream

2024-01-11 Thread Dirk Eddelbuettel
Package: ftp.debian.org Severity: normal The rJava package (source package 'rjava', binary package r-cran-rjava) no longer builds on i386 as most of the world, including R and its CRAN network, have moved on from i386. So I am requesting the removal of the i386 builds from testing so that the

Bug#1060440: llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel

2024-01-11 Thread Simon McVittie
Source: llvm-toolchain-17 Version: 1:17.0.6-4 Severity: serious Tags: ftbfs pending Justification: fails to build from source (but built successfully in the past) Forwarded: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/130 llvm-toolchain-17_1:17.0.6-4 has a FTBFS issue

Processed: found 1060429 in 2.1.0-1

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1060429 2.1.0-1 Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py There is no source info for the package 'python-django-solo' at version '2.1.0-1' with

Processed: add patch

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1058365 [python-jedi] python-lsp-server: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) patch. -- 1058365:

Bug#1058365: add patch

2024-01-11 Thread Matthias Klose
Control: tags -1 + patch patch at https://launchpadlibrarian.net/708712831/python-jedi_0.18.2-1_0.18.2-1ubuntu1.diff.gz

Processed: bug 1058296 is forwarded to https://github.com/dbnicholson/ostree-push/issues/16

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1058296 https://github.com/dbnicholson/ostree-push/issues/16 Bug #1058296 [src:ostree-push] ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Set Bug

Bug#1058290: Kafka vs Six

2024-01-11 Thread Alexandre Detiste
This one line is a no-op under Python3 and can be removed > from kafka.vendor.six.moves import range I ll have a more torough look at home and use CodeSearch to locate vendored copies of six.py Greetings

Bug#1037852: Bug#1056886: May be new upstream version fixes this issue

2024-01-11 Thread Andreas Tille
Hi Emmanuel, Am Thu, Jan 11, 2024 at 05:57:03AM -0300 schrieb Emmanuel Arias: > Thanks for your work. Yes, two new dependency must be added to Debian. I > postponed all this work, until finish with python-cassandra-driver. I hope > take scalene in the next week. Just take your time. I simply

Bug#1060434: ftbfs: usr/share/java/jansi1.jar is a symlink of a non-exist file jansi1-1.18.jar

2024-01-11 Thread Tianyu Chen
Source: jansi1 Version: 1.18-3 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sweetyf...@deepin.org Hi, During a rebuild of jansi1, your package built successfully but contains a broken symlink. The symlink usr/share/java/jansi1.jar points to

Bug#1060432: rpds-py ftbfs in unstable

2024-01-11 Thread Matthias Klose
Package: src:rpds-py Version: 0.12.0-2 Severity: serious Tags: sid trixie ftbfs rpds-py ftbfs in unstable, because of missing build dependencies: Issues preventing migration: ∙ ∙ rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-archery-dev ∙ ∙ rpds-py unsatisfiable

Processed: found 1055494 in 1.2.1+dfsg-2, found 1056054 in 5.0.1-1, tagging 1022957 ...

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1055494 1.2.1+dfsg-2 Bug #1055494 [clamav-doc] clamav-doc: missing Breaks+Replaces: clamav (<< 1.2) Marked as found in versions clamav/1.2.1+dfsg-2. > found 1056054 5.0.1-1 Bug #1056054 [openmpi-doc] openmpi-doc:

Processed: lowering severity, ignoring the problem for now

2024-01-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1058031 [src:pygame] pygame: FTBFS with Python 3.12 Severity set to 'important' from 'serious' -- 1058031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058031: lowering severity, ignoring the problem for now

2024-01-11 Thread Matthias Klose
Control: severity -1 important lowering the severity, ignoring the problem for now. The package is now built for 3.12.

Bug#1060149: src:extrepo: fails to migrate to testing for too long: autopkgtest regression

2024-01-11 Thread Wouter Verhelst
On Sun, Jan 07, 2024 at 08:19:40AM +0100, Paul Gevers wrote: > Hi Wouter, > > On 06-01-2024 20:51, Wouter Verhelst wrote: > > > The Release Team considers packages that are out-of-sync between testing > > > and > > > unstable for more than 30 days as having a Release Critical bug in testing > >

Bug#1037852: Bug#1056886: May be new upstream version fixes this issue

2024-01-11 Thread Emmanuel Arias
Hi Andreas, Thanks for your work. Yes, two new dependency must be added to Debian. I postponed all this work, until finish with python-cassandra-driver. I hope take scalene in the next week. Thanks again, you make some steps for me :) Cheers, Emmanuel El jue, 11 de ene de 2024, 05:33, Andreas

Bug#1056877: marked as done (pyyaml: ftbfs with cython 3.0.x)

2024-01-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jan 2024 08:36:38 + with message-id and subject line Bug#1056877: fixed in pyyaml 6.0.1-2 has caused the Debian Bug report #1056877, regarding pyyaml: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1037852: May be new upstream version fixes this issue

2024-01-11 Thread Andreas Tille
Hi, I tried to check whether the new upstream version might fix gcc-13 / Python3.12 issues. I've pushed my work to Salsa but it needs new dependencies (at least https://github.com/emeryberger/Heap-Layers may be two more) and I gave up here since I have no specific interest in this package. Hope