Bug#1101729: 1101729

2025-04-06 Thread Yue Gui
Dear r-cran-rcppparallel maintainer, For this issue, can we use the 'dpkg-query' command to replace 'dpkg -l'? For example, replacing the line in the rules file '' tbbversion=`dpkg -l libtbb-dev | grep 'ii' | sed 's/^.*libtbb-dev:[a-z0-9]\+[[:space:]]\+\([0-9.]\+\)-[0-9]\+[[:space:]]\+.*/\1/'`;''

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Santiago Vila
Hi. I confirm that the commit does not fix the problem. For the unreleased 3.6.0-3 version, I get a 50% failure rate with 1 CPU and 60% with 2 CPUs. (after trying 100 times each). Thanks.

Bug#1061241: marked as done (endless-sky: debian/copyright incomplete)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 13:34:36 + with message-id and subject line Bug#1061241: fixed in endless-sky 0.10.10-1 has caused the Debian Bug report #1061241, regarding endless-sky: debian/copyright incomplete to be marked as done. This means that you claim that the problem has been d

Bug#1102099: marked as pending in game-data-packager

2025-04-06 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #1102099 in game-data-packager 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: https://salsa.debian.org/games-team/game-data-packager/-/commit/d38a724

Processed: Bug#1102099 marked as pending in game-data-packager

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1102099 [src:game-data-packager] game-data-packager: FTBFS: inkscape SIGABRT after throwing an instance of 'Gio::DBus::Error' Added tag(s) pending. -- 1102099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102099 Debian Bug Tracking System

Bug#1088988: Is this bug solved?

2025-04-06 Thread Margarita Manterola
Hi, Looking at the latest uploads from Pandas, it seems this bug has been solved since 2.2.3+dfsg-6, which includes changelog entries about solving xarray incompatibilities. Is this really still a bug, or can it be closed? -- Regards, Marga

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Jérémy Lal
Le dim. 6 avr. 2025 à 12:43, Santiago Vila a écrit : > Hi. I confirm that the commit does not fix the problem. > > For the unreleased 3.6.0-3 version, I get a 50% failure rate > with 1 CPU and 60% with 2 CPUs. (after trying 100 times each). This test: "should not ignore further events on close

Bug#1093461: php-cache-tag-interop: Useless in Trixie

2025-04-06 Thread Paul Gevers
Hi taffit, On Sat, 18 Jan 2025 22:33:58 +0100 David =?iso-8859-1?Q?Pr=E9vot?= wrote: This package has currently no more dependencies in testing. Let’s not release Trixie with a useless package (unless someone disagrees before the freeze), and let’s get it removed from unstable once no packages

Processed: tagging 1061393

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1061393 + confirmed Bug #1061393 [runescape] runescape: Runescape launcher won't start because of missing dependencies Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061393: https:/

Processed: tagging 1089495

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1089495 + confirmed Bug #1089495 [unknown-horizons] unkown-horizons: Fails on startup, importing Python module "future" Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1089495: https:

Bug#1101624: marked as done (git-delta: FTBFS: unsatisfiable build-dependencies: librust-bat-0.24+minimal-application-dev, librust-bat-0.24+paging-dev, librust-bat-0.24+regex-onig-dev)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 13:49:34 + with message-id and subject line Bug#1101624: fixed in git-delta 0.18.2-4 has caused the Debian Bug report #1101624, regarding git-delta: FTBFS: unsatisfiable build-dependencies: librust-bat-0.24+minimal-application-dev, librust-bat-0.24+paging-d

Bug#1075379: Uploaded fixed version as NMU

2025-04-06 Thread Margarita Manterola
Hi, I have prepared a non-maintainer upload of pesign, including the upstream patch mentioned above. I have uploaded this version to the 5 day delayed queue. I'm attaching the debdiff of the NMU version. I will also send this as a merge request in salsa, in case that's your preferred workflo

Bug#1084954: Fwd: llvm-toolchain-*: assembly code seems to depend on build cpu capabilities

2025-04-06 Thread Paul Gevers
Hi h01ger, On 29-01-2025 19:19, Holger Levsen wrote: On Thu, Jan 09, 2025 at 10:38:54AM +0100, Paul Gevers wrote: I did that for both the armel and armhf architectures (see the arm32-defaults.diff patch), but this is unchecked for any other release architectures, and obviously wrong for some ar

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Santiago Vila
If you're okay to try again with latest salsa commits ? Tried 200 times. Same failure rates as before. I've put build logs (both successful and failed) here: https://people.debian.org/~sanvila/build-logs/node-chokidar/ Thanks.

Bug#1101068: Acknowledgement (TypeError: AsyncClient.__init__() got an unexpected keyword argument 'proxies')

2025-04-06 Thread Ted To
I'm not sure what the problem was but I have since reinstalled using the Bunsenlabs Boron ISO which I then dist-upgraded to Trixie. nala now seems to work fine. On Sat, Mar 22, 2025, at 4:27 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can

Bug#1029043: marked as done (AttributeError: module 'adonthell' has no attribute 'audio_load_wave')

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 14:34:12 + with message-id and subject line Bug#1029043: fixed in adonthell 0.3.8-5 has caused the Debian Bug report #1029043, regarding AttributeError: module 'adonthell' has no attribute 'audio_load_wave' to be marked as done. This means that you claim th

Bug#1082975: marked as pending in node-kew

2025-04-06 Thread Yadd
Control: tag -1 pending Hello, Bug #1082975 in node-kew 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: https://salsa.debian.org/js-team/node-kew/-/commit/f5cb81884b9324960f0f8e4c4a469e

Processed: Bug#1082975 marked as pending in node-kew

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1082975 [src:node-kew] node-kew: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1082975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082975 Debian Bug Tracking System Contac

Bug#1084831: HELP needed for uploading a new debianisation of the Rheolef package

2025-04-06 Thread Anton Gladky
Hi Pierre, done! Regards Anton Am Sa., 5. Apr. 2025 um 12:31 Uhr schrieb PIERRE SARAMITO : > > Hi Anton, Hi all, > > > From Anton: > > it looks like some builds in the pipeline are failing. > > It should be now fixed, thanks to an additional patch (communicator.patch) > in the debianisation of

Bug#1084831: marked as done (rheolef FTBFS with MPICH as default)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 14:38:55 + with message-id and subject line Bug#1084831: fixed in rheolef 7.2-4 has caused the Debian Bug report #1084831, regarding rheolef FTBFS with MPICH as default to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1102099: marked as done (game-data-packager: FTBFS: inkscape SIGABRT after throwing an instance of 'Gio::DBus::Error')

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 14:49:02 + with message-id and subject line Bug#1102099: fixed in game-data-packager 85 has caused the Debian Bug report #1102099, regarding game-data-packager: FTBFS: inkscape SIGABRT after throwing an instance of 'Gio::DBus::Error' to be marked as done.

Bug#1089901: marked as pending in reqwest

2025-04-06 Thread Yadd
Control: tag -1 pending Hello, Bug #1089901 in reqwest 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: https://salsa.debian.org/js-team/reqwest/-/commit/8bb6fc7b2b3c9042b843672f6398d27e

Processed: Bug#1089901 marked as pending in reqwest

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1089901 [src:reqwest] reqwest: stop calling dh_buildinfo Bug #1089900 [src:reqwest] reqwest: stop calling dh_buildinfo Added tag(s) pending. Added tag(s) pending. -- 1089900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089900 1089901: htt

Processed: tagging 1075379

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075379 + pending Bug #1075379 [src:pesign] pesign: ftbfs with GCC-14 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075379 D

Bug#1060930: marked as pending in node-eslint-plugin-requirejs

2025-04-06 Thread Yadd
Control: tag -1 pending Hello, Bug #1060930 in node-eslint-plugin-requirejs 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: https://salsa.debian.org/js-team/node-eslint-plugin-requirej

Processed: Bug#1060930 marked as pending in node-eslint-plugin-requirejs

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1060930 [src:node-eslint-plugin-requirejs] node-eslint-plugin-requirejs: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 22 Added tag(s) pending. -- 1060930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060930 Debian Bu

Bug#1082975: node-kew: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Santiago Vila
Hi. Will the committed fix really work, considering that the package also FTBFS on single-cpu systems? Thanks.

Processed: retitle 1090226 to gfpoken: FTBFS: crash on Blender invocation

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1090226 gfpoken: FTBFS: crash on Blender invocation Bug #1090226 [src:gfpoken] gfpoken: FTBFS: Couldn't open libEGL.so.1: libEGL.so.1: cannot open shared object file: No such file or directory Changed Bug title to 'gfpoken: FTBFS: crash o

Bug#1082992: marked as done (node-http-server: FTBFS: TypeError: util.puts is not a function)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:08:36 + with message-id and subject line Bug#1082992: fixed in node-http-server 14.1.1+~cs3.16.36-1 has caused the Debian Bug report #1082992, regarding node-http-server: FTBFS: TypeError: util.puts is not a function to be marked as done. This means that

Bug#1082975: marked as done (node-kew: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:08:43 + with message-id and subject line Bug#1082975: fixed in node-kew 0.7.0-3 has caused the Debian Bug report #1082975, regarding node-kew: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. Th

Bug#1089901: marked as done (reqwest: stop calling dh_buildinfo)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:08:52 + with message-id and subject line Bug#1089901: fixed in reqwest 2.0.5+dfsg-2 has caused the Debian Bug report #1089901, regarding reqwest: stop calling dh_buildinfo to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1089900: marked as done (reqwest: stop calling dh_buildinfo)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:08:52 + with message-id and subject line Bug#1089901: fixed in reqwest 2.0.5+dfsg-2 has caused the Debian Bug report #1089901, regarding reqwest: stop calling dh_buildinfo to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1094061: marked as done (ruby-jaeger-client: FTBFS: make: *** [debian/rules:8: binary] Error 25)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:16:03 + with message-id and subject line Bug#1102048: Removed package(s) from unstable has caused the Debian Bug report #1094061, regarding ruby-jaeger-client: FTBFS: make: *** [debian/rules:8: binary] Error 25 to be marked as done. This means that you c

Bug#1101735: marked as done (rust-sequoia-keyring-linter should not be released with trixie)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:28:28 + with message-id and subject line Bug#1101732: Removed package(s) from unstable has caused the Debian Bug report #1101735, regarding rust-sequoia-keyring-linter should not be released with trixie to be marked as done. This means that you claim tha

Bug#1101467: marked as done (redmine-plugin-redhopper: Should be removed from Debian)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:40:45 + with message-id and subject line Bug#1101511: Removed package(s) from unstable has caused the Debian Bug report #1101467, regarding redmine-plugin-redhopper: Should be removed from Debian to be marked as done. This means that you claim that the p

Bug#1095372: marked as done (python-hug: FTBFS: E AttributeError: module 'numpy' has no attribute 'bool8'.)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:48:26 + with message-id and subject line Bug#1088707: Removed package(s) from unstable has caused the Debian Bug report #1095372, regarding python-hug: FTBFS: E AttributeError: module 'numpy' has no attribute 'bool8'. to be marked as done. This me

Bug#1075507: marked as done (siggen: ftbfs with GCC-14)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:36:16 + with message-id and subject line Bug#1101709: Removed package(s) from unstable has caused the Debian Bug report #1075507, regarding siggen: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1093925: marked as done (ruby-premailer-rails: FTBFS: undefined method `ignored?' for an instance of Gem::Specification (NoMethodError))

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:19:35 + with message-id and subject line Bug#1101997: Removed package(s) from unstable has caused the Debian Bug report #1093925, regarding ruby-premailer-rails: FTBFS: undefined method `ignored?' for an instance of Gem::Specification (NoMethodError) to

Bug#1102199: marked as done (rust-libseccomp: flaky autopkgtests)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:52:59 + with message-id and subject line Bug#1102199: fixed in rust-libseccomp 0.3.0-11 has caused the Debian Bug report #1102199, regarding rust-libseccomp: flaky autopkgtests to be marked as done. This means that you claim that the problem has been dea

Bug#1102209: matomo: flaky autopkgtest (mostly on i386):

2025-04-06 Thread Paul Gevers
Source: matomo Version: 5.2.2+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package because it was shown as a regression for src:wine. I noticed that it regularly fails on i386, but there were fa

Processed: severity of 1098700 is important

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1098700 important Bug #1098700 [wvdial] wvdial: segmentation fault error when running wvdial Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1098700: https://bugs.

Bug#1093197: wine: FTBFS on arm*

2025-04-06 Thread Paul Gevers
Hi, On 06-04-2025 08:28, Paul Gevers wrote: With my Release Team hat on: I might be dropping wine from the key package list manually after checking the situation. Hmm, that's a bit harsh. Currently there are two RC bugs against wine in testing. The first one (#1100695) could be "fixed" by r

Bug#1102186: rust-cargo-outdated: FTBFS: rust-cargo-outdated build-depends on missing: librust-git2-curl-0.20+default-dev:amd64

2025-04-06 Thread Sebastian Ramacher
Source: rust-cargo-outdated Version: 0.16.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org Dear maintainer, rust-cargo-outdated cannot be built since it is BD-Uninstallable: https://buildd.debian.o

Bug#1074735: marked as pending in node-chokidar

2025-04-06 Thread Jérémy Lal
Control: tag -1 pending Hello, Bug #1074735 in node-chokidar 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: https://salsa.debian.org/js-team/node-chokidar/-/commit/d49be037fabbb06f911a

Processed: Bug#1074735 marked as pending in node-chokidar

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1074735 [src:node-chokidar] node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1074735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074735 Debian Bug Tracking Sys

Bug#1102198: rust-dirty-tracker: flaky autopkgtest

2025-04-06 Thread Sebastian Ramacher
Source: rust-dirty-tracker Version: 0.3.0-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org Dear maintainer, the autopkgtests of rust-dirty-tracker are flaky: https://ci.debian.net/packages/r/rust-dirty-tracker/testing/amd64/59604769/ test tests::test_create_and_follow_subdir ... FAILED fa

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Jérémy Lal
Le dim. 6 avr. 2025 à 11:54, Santiago Vila a écrit : > El 6/4/25 a las 11:23, Jérémy Lal escribió: > > Source: node-chokidar > > Followup-For: Bug #1074735 > > Control: tags -1 ftbfs > > > > It doesn't FTBFS in sbuild here. > > > > Could it be possible to check again ? > > This one fails around 7

Bug#1102197: rust-futures: flaky autopkgtest

2025-04-06 Thread Sebastian Ramacher
Source: rust-futures Version: 0.3.31-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Dear maintainer, the autopkgtests of rust-futures are flaky. The latest failure is: https://ci.debian.net/packages/r/rust-futures/testing/amd64/59604837/ test stream_select ... FAILED failures: st

Bug#1102199: rust-libseccomp: flaky autopkgtests

2025-04-06 Thread Sebastian Ramacher
Source: rust-libseccomp Version: 0.3.0-10 Severity: serious X-Debbugs-Cc: sramac...@debian.org Dear maintainer, the autopkgtests of rust-libseccomp are flaky: https://ci.debian.net/packages/r/rust-libseccomp/testing/ppc64el/59611330/ test test_check_api ... FAILED failures: test_check_api

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Santiago Vila
Hmm, please be cautious here. This one fails for me 70% of the time on machines with 2 CPUs, but also 50% of the time on machines with 1 CPU. (so serializing the tests might not be enough). Anyway, I will tell you how it goes after the package reaches unstable at 14:00 UTC. Thanks.

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Santiago Vila
Our emails have crossed. I prefer to check before you upload, that way we save debian release numbers and uploads. (mainly because I don't think the current fix will work) (Sorry for not telling all the info I had at first). Thanks.

Bug#1101417: marked as done (pydantic-core - upcoming rust-idna update)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 12:34:17 + with message-id and subject line Bug#1101417: fixed in pydantic-core 2.27.2-2 has caused the Debian Bug report #1101417, regarding pydantic-core - upcoming rust-idna update to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1091303 closed by Debian FTP Masters (reply to Richard Laager ) (Bug#1091303: fixed in ntpsec 1.2.3+dfsg1-4)

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1091303 patch Bug #1091303 [src:ntpsec] ntpsec: FTBFS on armhf: ../../ntpd/ntp_control.c:269:58: error: initialization of ‘const long int *’ from incompatible pointer type ‘long long int *’ [-Wincompatible-pointer-types] Added tag(s) patch.

Bug#1085522: marked as done (arduino-builder: FTBFS: FAIL arduino.cc/timeutils)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 12:49:10 + with message-id and subject line Bug#1085522: fixed in arduino-builder 1.3.25-5 has caused the Debian Bug report #1085522, regarding arduino-builder: FTBFS: FAIL arduino.cc/timeutils to be marked as done. This means that you claim that the proble

Bug#1101859: marked as done (pydantic-settings: FTBFS: test_cli_metavar_format_type_alias_312 fails)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 12:52:20 + with message-id and subject line Bug#1101859: fixed in pydantic-settings 2.8.1-2 has caused the Debian Bug report #1101859, regarding pydantic-settings: FTBFS: test_cli_metavar_format_type_alias_312 fails to be marked as done. This means that you

Bug#1101624: git-delta: patches to fix FTBFS

2025-04-06 Thread Jeremy Bícha
Control: tags -1 +patch git-delta fails to build because of two issues. First, rust-bat was updated to 0.25. That's https://bugs.debian.org/1101624 Second, the ongoing libgit2 1.9 transition (with rust-git2 updated to 0.20.1) requires an update in git-delta. I am attaching patches to fix these i

Processed: git-delta: patches to fix FTBFS

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +patch Bug #1101624 [src:git-delta] git-delta: FTBFS: unsatisfiable build-dependencies: librust-bat-0.24+minimal-application-dev, librust-bat-0.24+paging-dev, librust-bat-0.24+regex-onig-dev Added tag(s) patch. -- 1101624: https://bugs.debian.org/cgi-bin/

Bug#1093777: closing 1093777

2025-04-06 Thread Maximiliano Curia
close 1093777 0.25.0-1 thanks Closing the issue. As the tests for returns are now disabled on riscv64. This is actually a problem that it's going to be solved after better hardware (and probably better kernel support for it) is added to the riscv64 porters pool. Regards, -- Saludos, Maxy

Processed: closing 1093777

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1093777 0.25.0-1 Bug #1093777 [src:python-returns] Autopkgtests fail on riscv64: hypothesis.errors.FailedHealthCheck: Data generation is extremely slow Marked as fixed in versions python-returns/0.25.0-1. Bug #1093777 [src:python-returns] A

Processed: bug 1101855 is forwarded to https://github.com/litestar-org/litestar/issues/4088

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1101855 https://github.com/litestar-org/litestar/issues/4088 Bug #1101855 [src:litestar] litestar: FTBFS: test_unwrap_type_alias_type_keyword fails Set Bug forwarded-to-address to 'https://github.com/litestar-org/litestar/issues/4088'.

Bug#1102189: src:r-cran-argparser: fails to migrate to testing for too long

2025-04-06 Thread Paul Gevers
Source: r-cran-argparser Version: 0.7.1-1 Severity: serious Control: close -1 0.7.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 da

Processed: src:r-cran-argparser: fails to migrate to testing for too long

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.7.2-1 Bug #1102189 [src:r-cran-argparser] src:r-cran-argparser: fails to migrate to testing for too long Marked as fixed in versions r-cran-argparser/0.7.2-1. Bug #1102189 [src:r-cran-argparser] src:r-cran-argparser: fails to migrate to testing for too l

Bug#1089765: marked as done (mediawiki-skin-greystuff: autopkgtest failure with php-defaults (96))

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 08:48:28 + with message-id and subject line Bug#1089765: fixed in mediawiki-skin-greystuff 1.2.5~git20250311.35884cb-1 has caused the Debian Bug report #1089765, regarding mediawiki-skin-greystuff: autopkgtest failure with php-defaults (96) to be marked as

Bug#1084078: marked as done (xgks: Please upgrade build-dep to flang 18 or 19)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 09:06:14 + with message-id and subject line Bug#1084078: fixed in xgks 2.6.1+dfsg.2-17 has caused the Debian Bug report #1084078, regarding xgks: Please upgrade build-dep to flang 18 or 19 to be marked as done. This means that you claim that the problem has

Bug#1102107: boost1.88 also ftbfs on alpha, hppa, m68k, sh4.

2025-04-06 Thread Matthias Klose
the same failure is also seen on alpha, hppa, m68k, sh4.

Processed: fixed 1064558 in 5.6.0+dfsg-5

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1064558 5.6.0+dfsg-5 Bug #1064558 {Done: Jérémy Lal } [src:node-leveldown] node-leveldown: FTBFS on mips64el: not ok 1397 Error: batch(array) element must be an object and not `null` Marked as fixed in versions node-leveldown/5.6.0+dfsg-5.

Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Jérémy Lal
Source: node-chokidar Followup-For: Bug #1074735 Control: tags -1 ftbfs It doesn't FTBFS in sbuild here. Could it be possible to check again ? If not I'll just close the bug. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing

Processed: Re: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 ftbfs Bug #1074735 [src:node-chokidar] node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Ignoring request to alter tags of bug #1074735 to the same tags previously set -- 1074735: https://bugs.debian.org/c

Bug#1074735: [Pkg-javascript-devel] Bug#1074735: node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2025-04-06 Thread Santiago Vila
El 6/4/25 a las 11:23, Jérémy Lal escribió: Source: node-chokidar Followup-For: Bug #1074735 Control: tags -1 ftbfs It doesn't FTBFS in sbuild here. Could it be possible to check again ? This one fails around 70% of the time for me on AWS machines with 2 CPUs. Thanks.

Bug#1089764: marked as done (mediawiki-extension-youtube: autopkgtest failure with php-defaults (96))

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 07:35:33 + with message-id and subject line Bug#1089764: fixed in mediawiki-extension-youtube 1.9.4~git20241126.01673ce-1 has caused the Debian Bug report #1089764, regarding mediawiki-extension-youtube: autopkgtest failure with php-defaults (96) to be mar

Bug#1102187: rust-libxml - bindings unportable

2025-04-06 Thread Bastian Blank
Package: rust-libxml Version: 0.3.3-1 Severity: serious rust-libxml ships pre-generated and architecture specific bindings. Those need to be generated for the correct architecture during build or so. Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Foreve

Bug#1102186: marked as done (rust-cargo-outdated: FTBFS: rust-cargo-outdated build-depends on missing: librust-git2-curl-0.20+default-dev:amd64)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 10:50:30 + with message-id and subject line Bug#1102186: fixed in rust-cargo-outdated 0.17.0-1 has caused the Debian Bug report #1102186, regarding rust-cargo-outdated: FTBFS: rust-cargo-outdated build-depends on missing: librust-git2-curl-0.20+default-dev:

Bug#1101603: os-autoinst: FTBFS -> fix exists, needs a new upload

2025-04-06 Thread Roland Clobus
Hello Phil, Tina, On Wed, 2 Apr 2025 14:56:37 +0200 (CEST) =?ISO-8859-15?Q?Tina_M=FCller?= wrote: But for the actual problem: Which git version are you running this with? We had the same problem recently with git 2.49 and fixed it with this: https://github.com/os-autoinst/os-autoinst/commit/84

Bug#1101756: marked as done (Should libbson-xs-perl be shipped in trixie?)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 11:11:46 + with message-id and subject line Bug#1102138: Removed package(s) from unstable has caused the Debian Bug report #1101756, regarding Should libbson-xs-perl be shipped in trixie? to be marked as done. This means that you claim that the problem has

Processed: notfound 1067334 in node-iconv-lite/0.6.3-3, closing 1067334

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1067334 node-iconv-lite/0.6.3-3 Bug #1067334 [src:node-iconv-lite] node-iconv-lite: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 134 No longer marked as found in versions node-iconv-lite/0.6.3-3. >

Bug#1078631: Unable to reproduce

2025-04-06 Thread Yadd
Control: tags -1 + moreinfo Hi, I'm unable to reproduce this issue, maybe fixed elsewhere ?

Processed: Unable to reproduce

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1078631 [src:node-tough-cookie] node-tough-cookie: will FTBFS during trixie support period Added tag(s) moreinfo. -- 1078631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078631 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1101633: marked as done (xarray-sentinel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:50:32 + with message-id and subject line Bug#1101633: fixed in xarray-sentinel 0.9.5+ds-4 has caused the Debian Bug report #1101633, regarding xarray-sentinel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned e

Processed: Re: libcairomm-1.16-doc: broken symlink: /usr/share/doc/cairomm-1.0 -> libcairomm-1.0-doc

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1040561 1.16.2-3 Bug #1040561 {Done: Jeremy Bícha } [libcairomm-1.16-doc] libcairomm-1.16-doc: broken symlink: /usr/share/doc/cairomm-1.0 -> libcairomm-1.0-doc Bug #1100822 {Done: Jeremy Bícha } [libcairomm-1.16-doc] libcairomm-1.0-doc

Bug#1100273: python-mne: FTBFS: failing tests

2025-04-06 Thread Étienne Mollier
Control: forwarded -1 https://github.com/mne-tools/mne-python/issues/13193 Control: tags -1 + confirmed upstream Greetings, I have investigated the issue and transmitted relevant information directly upstream. I don't see an easy fix for the problem at play, because mitigation would require migr

Processed: Re: Bug#1100273: python-mne: FTBFS: failing tests

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/mne-tools/mne-python/issues/13193 Bug #1100273 [src:python-mne] python-mne: FTBFS: failing tests Set Bug forwarded-to-address to 'https://github.com/mne-tools/mne-python/issues/13193'. > tags -1 + confirmed upstream Bug #1100273 [src:

Processed: Re: nautilus-owncloud: menu doesn't appear due to nautilus API changes

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1037411 2.11.0.8354+dfsg-1 Bug #1037411 {Done: Pierre-Elliott Bécue } [nautilus-owncloud] nautilus-owncloud: menu doesn't appear due to nautilus API changes No longer marked as found in versions owncloud-client/2.11.0.8354+dfsg-1. > End

Bug#1088988: Is this bug solved?

2025-04-06 Thread Rebecca N. Palmer
Unfortunately not: those always were "ignore these tests to not block an unrelated transition" workarounds, not actual fixes (which is why I didn't close this bug). As far as I'm aware, the status of this bug hasn't changed since the description earlier in this thread.

Processed: Re: gnome-dvb-client: gnome-dvb-control fails to start with Python >= 3.8

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1036124 1:0.2.91~git20170110-4 Bug #1036124 {Done: Jeremy Bícha } [gnome-dvb-client] gnome-dvb-client: gnome-dvb-control fails to start with Python >= 3.8 No longer marked as found in versions gnome-dvb-daemon/1:0.2.91~git20170110-4. > E

Processed: Unable to reproduce

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1099251 [src:node-d3-timer] node-d3-timer: FTBFS: # fail 1 Added tag(s) moreinfo. -- 1099251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1101994: marked as done (libconfig-model-itself-perl: (autopkg)test failures with Path::Tiny 0.148)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:35:59 + with message-id and subject line Bug#1101994: fixed in libconfig-model-itself-perl 2.025-1 has caused the Debian Bug report #1101994, regarding libconfig-model-itself-perl: (autopkg)test failures with Path::Tiny 0.148 to be marked as done. This

Bug#1099251: Unable to reproduce

2025-04-06 Thread Yadd
Control: tags -1 + moreinfo Hi, I'm unable to reproduce this issue, maybe fixed alsewhere ?

Bug#1099251: node-d3-timer: FTBFS: # fail 1

2025-04-06 Thread Santiago Vila
I'm unable to reproduce this issue, maybe fixed alsewhere ? Hi. This one fails randomly with 50% of probability in my test setup. Jérémy currently has access to a VM instance where he can reproduce this one. But if you prefer, I can create another VM for you (contact me privately for details).

Bug#1088988: Is this bug solved?

2025-04-06 Thread Margarita Manterola
Hi Rebecca, On 2025-04-06 17:31, Rebecca N. Palmer wrote: Unfortunately not: those always were "ignore these tests to not block an unrelated transition" workarounds, not actual fixes (which is why I didn't close this bug). As far as I'm aware, the status of this bug hasn't changed since the

Bug#1094113: Uploaded fixed version as NMU

2025-04-06 Thread Margarita Manterola
tags 1094113 +pending thanks Hi! I have prepared a fix for this bug (changing the case from MiniTest to Minitest) and I have verified that this makes the package build correctly. Honestly, I don't understand how this ever worked, but I reproduced the build failure, and then got the package

Processed: Uploaded fixed version as NMU

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1094113 +pending Bug #1094113 [src:xdotool] xdotool: FTBFS: test_basic.rb:7:in `': uninitialized constant MiniTest (NameError) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1094113: h

Bug#1100273: marked as pending in python-mne

2025-04-06 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1100273 in python-mne 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: https://salsa.debian.org/med-team/python-mne/-/commit/bf349c2f5d8d34b28cdf404a5

Processed: Bug#1100273 marked as pending in python-mne

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1100273 [src:python-mne] python-mne: FTBFS: failing tests Added tag(s) pending. -- 1100273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1101242 marked as pending in node-immutable-tuple

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1101242 [src:node-immutable-tuple] node-immutable-tuple: FTBFS: Exception during run: ReferenceError: require is not defined in ES module scope, you can use import instead Added tag(s) pending. -- 1101242: https://bugs.debian.org/cgi-bin/bugre

Bug#1101242: marked as pending in node-immutable-tuple

2025-04-06 Thread Yadd
Control: tag -1 pending Hello, Bug #1101242 in node-immutable-tuple 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: https://salsa.debian.org/js-team/node-immutable-tuple/-/commit/4f3d11

Bug#1101994: libconfig-model-itself-perl: (autopkg)test failures with Path::Tiny 0.148

2025-04-06 Thread gregor herrmann
On Fri, 04 Apr 2025 23:44:51 +0200, gregor herrmann wrote: I'm going to fix this upstream. Thanks! Thanks for the quick fix and also the upload to Debian. Is it possible that you haven't pushed your changes to the salsa repo? I almost started to work on integrating the new upstream release

Bug#1100828: debian-archive-keyring: trixie archive signing keys

2025-04-06 Thread Ansgar 🙀
Hi, On Wed, 2025-03-19 at 07:47 +, Jonathan Wiltshire wrote: > New archive signing keys are now needed for trixie, ideally before the soft > freeze for trixie's update and then they can also be included in 12.11 > before 13.0. The keys are now published, see [1]. Ansgar [1]: https://lists

Bug#1101994: libconfig-model-itself-perl: (autopkg)test failures with Path::Tiny 0.148

2025-04-06 Thread Dominique Dumont
On Sunday, 6 April 2025 18:14:32 Central European Summer Time you wrote: > Is it possible that you haven't pushed your changes to the salsa > repo? Arg... yes... sorry about that. I've just pushed my changes. All the best

Bug#1101969: node-blueprintjs-core overwrites node-blueprintjs-colors

2025-04-06 Thread Yadd
Control: reassign -1 node-blueprintjs-colors Control: affects -1 node-blueprintjs-core [...] > It's not clear to me what the desired state here is. A reasonable > interpretation could be that node-blueprintjs-core accidentally > vendored node-blueprintjs-colors and should really depend on it and

Bug#1102241: opkssh: FTBFS: not enough arguments in call to choosers.NewWebChooser

2025-04-06 Thread Santiago Vila
Package: src:opkssh Version: 0.3.0-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [ please read notes at the end ] [...] deb

  1   2   >