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

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1102241 0.4.0-1 Bug #1102241 [src:opkssh] opkssh: FTBFS: not enough arguments in call to choosers.NewWebChooser Marked as fixed in versions opkssh/0.4.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 11

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

2025-04-06 Thread Simon Josefsson
fixed 1102241 0.4.0-1 thanks Santiago Vila writes: > github.com/openpubkey/opkssh > # github.com/openpubkey/opkssh > src/github.com/openpubkey/opkssh/main.go:183:5: not enough arguments in call > to choosers.NewWebChooser > have ([]providers.BrowserOpenIdProvider) > want ([]provider

Bug#1102160: upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive

2025-04-06 Thread Martin-Éric Racine
On Sun, 6 Apr 2025 19:36:03 +0300 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= wrote: > On Sun, 6 Apr 2025 13:02:29 +0300 > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= > wrote: > > On Sun, 6 Apr 2025 10:00:45 +0300 > > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= > > wrote: > > > On Sat, 05 Apr 2025 22:56:46 +0300

Processed: severity of 1102160 is critical

2025-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1102160 critical Bug #1102160 [grub-efi-amd64] upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive Severity set to 'critical' from 'important' > thanks Stopping process

Processed: Bug#1101251 marked as pending in r-bioconductor-lpsymphony

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1101251 {Done: Charles Plessy } [r-bioc-lpsymphony] r-bioc-ihw: FTBFS: /usr/lib/R/site-library/lpsymphony/libs/lpsymphony.so: undefined symbol: _Z17sym_set_dbl_paramP15SYM_ENVIRONMENTPKcd Added tag(s) pending. -- 1101251: https://bugs.debian.o

Bug#1101251: marked as pending in r-bioconductor-lpsymphony

2025-04-06 Thread Charles Plessy
Control: tag -1 pending Hello, Bug #1101251 in r-bioconductor-lpsymphony 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/r-pkg-team/r-bioc-lpsymphony/-/commit/4

Bug#1101711: marked as done (r-bioc-ihw: FTBFS: unable to load shared object '/usr/lib/R/site-library/lpsymphony/libs/lpsymphony.so')

2025-04-06 Thread Debian Bug Tracking System
Your message dated Mon, 07 Apr 2025 04:19:04 + with message-id and subject line Bug#1101711: fixed in r-bioc-ihw 1.34.0+dfsg-3 has caused the Debian Bug report #1101711, regarding r-bioc-ihw: FTBFS: unable to load shared object '/usr/lib/R/site-library/lpsymphony/libs/lpsymphony.so' to be mar

Bug#1101251: marked as done (r-bioc-ihw: FTBFS: /usr/lib/R/site-library/lpsymphony/libs/lpsymphony.so: undefined symbol: _Z17sym_set_dbl_paramP15SYM_ENVIRONMENTPKcd)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Mon, 07 Apr 2025 04:19:12 + with message-id and subject line Bug#1101251: fixed in r-bioc-lpsymphony 1.34.0+dfsg-3 has caused the Debian Bug report #1101251, regarding r-bioc-ihw: FTBFS: /usr/lib/R/site-library/lpsymphony/libs/lpsymphony.so: undefined symbol: _Z17sym_set_d

Processed: Bug#1101711 marked as pending in r-bioc-ihw

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1101711 [src:r-bioc-ihw] r-bioc-ihw: FTBFS: unable to load shared object '/usr/lib/R/site-library/lpsymphony/libs/lpsymphony.so' Added tag(s) pending. -- 1101711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101711 Debian Bug Tracking Sys

Bug#1101711: marked as pending in r-bioc-ihw

2025-04-06 Thread Charles Plessy
Control: tag -1 pending Hello, Bug #1101711 in r-bioc-ihw 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/r-pkg-team/r-bioc-ihw/-/commit/e61e8f103843b99ff2bd867

Bug#1100341: marked as done (falcosecurity-libs: FTBFS on armel: /lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing from command line)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Mon, 07 Apr 2025 00:04:41 + with message-id and subject line Bug#1100341: fixed in falcosecurity-libs 0.20.0-2 has caused the Debian Bug report #1100341, regarding falcosecurity-libs: FTBFS on armel: /lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing f

Bug#1093461: marked as done (php-cache-tag-interop: Useless in Trixie)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Mon, 7 Apr 2025 00:22:59 +0200 with message-id and subject line Re: [pkg-php-pear] Bug#1093461: php-cache-tag-interop: Useless in Trixie has caused the Debian Bug report #1093461, regarding php-cache-tag-interop: Useless in Trixie to be marked as done. This means that you clai

Bug#1100967: golang-step-crypto-dev and golang-github-smallstep-crypto-dev have undeclared file conflicts

2025-04-06 Thread Jérémy Lal
Le mer. 2 avr. 2025 à 10:39, Simon Josefsson a écrit : > A short-term fix to resolve the RC bug may be to simply add a > 'Conflicts: golang-step-crypto-dev' to > golang-github-smallstep-crypto-dev? Or is there a need to be able to > co-install these two packages? > > Meanwhile I looked into upda

Bug#1102268: motion: Dependency problem: requires libavdevice59 >=7:5.0 which is not available

2025-04-06 Thread afc
Package: motion Version: 4.5.1.2 (the version in debian 12.10) Severity: grave Justification: renders package unusable X-Debbugs-Cc: af...@comcast.net Dear Maintainer, * What led up to the situation? Trying to install motion on an up-to-date Debian 12.10 system. * What exactly did you

Bug#1093197: marked as done (wine: FTBFS on arm*)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 23:20:56 + with message-id and subject line Bug#1093197: fixed in wine 10.0~repack-2 has caused the Debian Bug report #1093197, regarding wine: FTBFS on arm* to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1100389: marked as done (sysdig: FTBFS on riscv64: ‘luaL_setfuncs’ was not declared in this scope;)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 23:19:56 + with message-id and subject line Bug#1100389: fixed in sysdig 0.40.0+repack-2 has caused the Debian Bug report #1100389, regarding sysdig: FTBFS on riscv64: ‘luaL_setfuncs’ was not declared in this scope; to be marked as done. This means that yo

Bug#1100442: marked as done (ruby-graphql: CVE-2025-27407)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 22:52:24 + with message-id and subject line Bug#1100442: fixed in ruby-graphql 2.2.17-1 has caused the Debian Bug report #1100442, regarding ruby-graphql: CVE-2025-27407 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1101865: Fix for this bug, proposed NMU

2025-04-06 Thread Thomas Goirand
Hi Sandro, It looks like to me that the bug is because, with newer kernels, the correct path for the power supply plug should be: /sys/class/power_supply/ADP0 At least, the above is what I have currently have in my laptop. The current code for psutil is expecting /AC0 or /AC, but not /ADP0. I

Bug#1081196: marked as done (crowdsec ssh log monitoring broken by latest "openssh-server" package)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 22:19:39 + with message-id and subject line Bug#1081196: fixed in crowdsec 1.4.6-10 has caused the Debian Bug report #1081196, regarding crowdsec ssh log monitoring broken by latest "openssh-server" package to be marked as done. This means that you claim th

Processed: Bug#1081196 marked as pending in crowdsec

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1081196 [crowdsec] crowdsec ssh log monitoring broken by latest "openssh-server" package Added tag(s) pending. -- 1081196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081196 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#1081196: marked as pending in crowdsec

2025-04-06 Thread Cyril Brulebois
Control: tag -1 pending Hello, Bug #1081196 in crowdsec 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/go-team/packages/crowdsec/-/commit/67bad0ec2c885b2a8b157

Bug#1081196: Crowdsec

2025-04-06 Thread Cyril Brulebois
Hi, Mathias Gibbens (2025-03-18): > On Wed, 2025-03-12 at 18:09 +, Martin Dosch wrote: > > Dear all, > > > > I'd like to see crowdsec in trixie, as I am using it myself. > > Is there any chance to get [1081196] fixed by delivering upstreams > > sshd-logs.yaml? This file is not in the repo a

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

2025-04-06 Thread Ted To
Never mind my last update. Seems to be a problem here too. Could it be a low memory problem? It is on a former Chromebook with only 2GB RAM. On Sun, Apr 6, 2025, at 10:33 AM, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug rep

Bug#1075379: Uploaded fixed version as NMU

2025-04-06 Thread Steve McIntyre
Thanks Marga, just merged your MR. IMHO this is one of the worst things the gcc folks have done in years, but we to cope with it. :-/ Cheers, Steve On Sun, Apr 06, 2025 at 03:52:07PM +0200, Margarita Manterola wrote: >Hi, > >I have prepared a non-maintainer upload of pesign, including the upstre

Bug#1101965: marked as done (systemd-resolved declares ineffective Replaces for systemd due to the /usr-move potentially loosing /usr/lib/systemd/resolv.conf (DEP17 P1))

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 21:15:17 + with message-id and subject line Bug#1101965: fixed in systemd 257.5-1 has caused the Debian Bug report #1101965, regarding systemd-resolved declares ineffective Replaces for systemd due to the /usr-move potentially loosing /usr/lib/systemd/resol

Bug#1100308: ruby-haml: FTBFS: failing tests (fix available)

2025-04-06 Thread Sérgio Cipriano
Hi, The fix is available at: https://salsa.debian.org/ruby-team/ruby-haml/-/merge_requests/4 -- Thanks, Sérgio Cipriano. signature.asc Description: PGP signature

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

2025-04-06 Thread Philip Hands
Roland Clobus writes: > 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://git

Bug#1079874: marked as done (valgrind: FTBFS with mpich instead of openmpi)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 15:46:16 -0400 with message-id <87jz7xvzsn@sergiodj.net> and subject line Re: Bug#1079874: valgrind: FTBFS with mpich instead of openmpi has caused the Debian Bug report #1079874, regarding valgrind: FTBFS with mpich instead of openmpi to be marked as done.

Bug#1062190: marked as done (synaptic: releases frontend lock while running dpkg)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 19:42:33 + with message-id and subject line Bug#1062190: fixed in synaptic 0.91.7 has caused the Debian Bug report #1062190, regarding synaptic: releases frontend lock while running dpkg to be marked as done. This means that you claim that the problem has b

Processed: Re: node-blueprintjs-core overwrites node-blueprintjs-colors

2025-04-06 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 node-blueprintjs-colors Bug #1101969 [node-blueprintjs-core] node-blueprintjs-core overwrites node-blueprintjs-colors Bug reassigned from package 'node-blueprintjs-core' to 'node-blueprintjs-colors'. No longer marked as found in versions node-blueprint

Bug#1082975: [Pkg-javascript-devel] 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 Jérémy Lal
Le dim. 6 avr. 2025 à 17:03, Santiago Vila a écrit : > Hi. > > Will the committed fix really work, considering that the package > also FTBFS on single-cpu systems? Yes, it does really work ;)

Bug#1102256: rust-hstr: librust-is-macro-dev binary package is also built by src rust-is-macro

2025-04-06 Thread Jeremy Bícha
Source: rust-hstr Version: 0+20250106-2 Severity: serious Tags: trixie sid The source package rust-hstr builds the binary package librust-is-macro-dev for Architecture:all with version 0.3.7+0+20250106-2 The source package rust-is-macro builds the binary package librust-is-macro-dev for Architect

Bug#1102255: rust-is-macro: librust-is-macro-dev is also built by src rust-hstr

2025-04-06 Thread Jeremy Bícha
Source: rust-is-macro Version: 0.3.6-1 Severity: serious Tags: trixie sid X-Debbugs-CC: debian-r...@lists.debian.org The source package rust-hstr builds the binary package librust-is-macro-dev for Architecture:all with version 0.3.7+0+20250106-2 The source package rust-is-macro builds the binary

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

2025-04-06 Thread Jérémy Lal
Le dim. 6 avr. 2025 à 18:31, Jérémy Lal a écrit : > > > Le dim. 6 avr. 2025 à 17:57, Santiago Vila a écrit : > >> > 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 in

Bug#1101749: marked as done (ga68-15 and ga68-15-doc have undefined unpack behavior due to filesystem aliasing)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 18:48:36 + with message-id and subject line Bug#1101749: fixed in gcc-15 15-20250406-1 has caused the Debian Bug report #1101749, regarding ga68-15 and ga68-15-doc have undefined unpack behavior due to filesystem aliasing to be marked as done. This means

Bug#1101750: marked as done (libgccjit-15-doc overwrites info files from libgccjit-14-doc)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 18:48:37 + with message-id and subject line Bug#1101750: fixed in gcc-15 15-20250406-1 has caused the Debian Bug report #1101750, regarding libgccjit-15-doc overwrites info files from libgccjit-14-doc to be marked as done. This means that you claim that

Bug#1101594: marked as done (pytroll-schedule: 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 18:49:55 + with message-id and subject line Bug#1101594: fixed in pytroll-schedule 0.7.2-3 has caused the Debian Bug report #1101594, regarding pytroll-schedule: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned ex

Bug#1100308: ruby-haml: FTBFS: failing tests

2025-04-06 Thread Sérgio Cipriano
user debian-rele...@lists.debian.org usertags 1100308 + bsp-2025-04-brazil thanks Hi, It seems that the new upstream version will fix this issue. I'm working on this as part of the Debian Brazil BSP. -- Sérgio Cipriano. signature.asc Description: PGP signature

Bug#1100273: marked as done (python-mne: FTBFS: failing tests)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 18:08:15 + with message-id and subject line Bug#1100273: fixed in python-mne 1.9.0-2 has caused the Debian Bug report #1100273, regarding python-mne: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1074735: marked as done (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
Your message dated Sun, 06 Apr 2025 18:06:35 + with message-id and subject line Bug#1074735: fixed in node-chokidar 3.6.0-3 has caused the Debian Bug report #1074735, regarding node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as

Bug#1102251: rust-sudo-rs: failing autopkgtests

2025-04-06 Thread Jeremy Bícha
Source: rust-sudo-rs Version: 0.2.5-1 Severity: serious Tags: trixie sid X-Debbugs-CC: sylves...@debian.org rust-sudo-rs is unable to migrate to Testing because its autopkgtests are failing. https://qa.debian.org/excuses.php?package=rust-sudo-rs Summary rust-sudo-rs:@ FAIL non-zero

Bug#1100380: plasma-mobile: undeclared file conflict with kde-config-mobile-networking

2025-04-06 Thread Aurélien COUDERC
Le 5 avril 2025 18:23:54 GMT+02:00, Marco Mattiolo a écrit : >Hi, >I've tried to reproduce this issue by upgrading a Mobian VM from bookworm to >trixie. Conflicts in file ownership must always be correctly declared with breaks/replaces even when you can't reproduce them. Because it depends

Bug#1102177: marked as done (flask-sqlalchemy: autopkgtest needs update for new version of sqlalchemy: test already defines a '__table__')

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 17:04:27 + with message-id and subject line Bug#1102177: fixed in flask-sqlalchemy 3.1.1-4 has caused the Debian Bug report #1102177, regarding flask-sqlalchemy: autopkgtest needs update for new version of sqlalchemy: test already defines a '__table__' to b

Bug#1102107: marked as done (boost1.88 ftbfs on i386)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 16:52:37 + with message-id and subject line Bug#1102107: fixed in boost1.88 1.88.0~beta1-1 has caused the Debian Bug report #1102107, regarding boost1.88 ftbfs on i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1100380: marked as done (plasma-mobile: undeclared file conflict with kde-config-mobile-networking)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 16:54:24 + with message-id and subject line Bug#1100380: fixed in plasma-mobile 6.3.4-1 has caused the Debian Bug report #1100380, regarding plasma-mobile: undeclared file conflict with kde-config-mobile-networking to be marked as done. This means that you

Bug#1102246: mender-connect: FTBFS: FAIL github.com/mendersoftware/mender-connect/app

2025-04-06 Thread Santiago Vila
Package: src:mender-connect Version: 2.3.0+ds1-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 ] ---

Bug#1101855: marked as done (litestar: FTBFS: test_unwrap_type_alias_type_keyword fails)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 16:34:29 + with message-id and subject line Bug#1101855: fixed in litestar 2.15.2-1 has caused the Debian Bug report #1101855, regarding litestar: FTBFS: test_unwrap_type_alias_type_keyword fails to be marked as done. This means that you claim that the prob

Bug#1101242: marked as done (node-immutable-tuple: FTBFS: Exception during run: ReferenceError: require is not defined in ES module scope, you can use import instead)

2025-04-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Apr 2025 16:34:36 + with message-id and subject line Bug#1101242: fixed in node-immutable-tuple 0.4.10-12 has caused the Debian Bug report #1101242, regarding node-immutable-tuple: FTBFS: Exception during run: ReferenceError: require is not defined in ES module scop

Bug#1062190: packagekit: locks the dpkg frontened in the middle of a running update by synaptic package manager

2025-04-06 Thread Michael Vogt
On Sat, Apr 5, 2025, at 00:00, Julian Andres Klode wrote: [..] > synaptic calls releaseLock() before running dpkg; which in turn calls > APT's UnLock(). I believe, but am not sure, that we can drop that call > entirely and APT should do the right thing. > > I don't quite know and I'd need to do mor

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

2025-04-06 Thread Jérémy Lal
Le dim. 6 avr. 2025 à 17:57, Santiago Vila a écrit : > > 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,

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

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

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

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

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

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

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#1099251: Unable to reproduce

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

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

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

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:

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

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

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

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

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

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

  1   2   >