Bug#1093992: marked as done (lynkeos.app: FTBFS with the GNUstep multiarch layout: dh_install errors)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 07:50:16 + with message-id and subject line Bug#1093992: fixed in lynkeos.app 3.7+dfsg-6 has caused the Debian Bug report #1093992, regarding lynkeos.app: FTBFS with the GNUstep multiarch layout: dh_install errors to be marked as done. This means that you

Bug#1093995: marked as done (systempreferences.app: FTBFS with the GNUstep multiarch layout: dh_install errors)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 07:50:36 + with message-id and subject line Bug#1093995: fixed in systempreferences.app 1.2.1-2 has caused the Debian Bug report #1093995, regarding systempreferences.app: FTBFS with the GNUstep multiarch layout: dh_install errors to be marked as done. Thi

Bug#1093991: marked as done (grr.app: FTBFS with the GNUstep multiarch layout: dh_install errors)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 07:50:06 + with message-id and subject line Bug#1093991: fixed in grr.app 1.0-3 has caused the Debian Bug report #1093991, regarding grr.app: FTBFS with the GNUstep multiarch layout: dh_install errors to be marked as done. This means that you claim that the

Bug#1093990: marked as done (gorm.app: FTBFS with the GNUstep multiarch layout: dh_install errors)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 07:49:56 + with message-id and subject line Bug#1093990: fixed in gorm.app 1.4.0-6 has caused the Debian Bug report #1093990, regarding gorm.app: FTBFS with the GNUstep multiarch layout: dh_install errors to be marked as done. This means that you claim that

Bug#1095022: marked as done (fiat: autopkgtests fail with numpy 2.x)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 07:19:23 + with message-id and subject line Bug#1095022: fixed in fiat 2019.2.0~git20210419.7d418fa-6 has caused the Debian Bug report #1095022, regarding fiat: autopkgtests fail with numpy 2.x to be marked as done. This means that you claim that the proble

Bug#1094126: marked as done (ngspetsc: FTBFS: RuntimeError: The Poetry configuration is invalid:)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 07:05:15 + with message-id and subject line Bug#1094126: fixed in ngspetsc 0.0.8-3 has caused the Debian Bug report #1094126, regarding ngspetsc: FTBFS: RuntimeError: The Poetry configuration is invalid: to be marked as done. This means that you claim that

Processed: src:gnocchi: fails to migrate to testing for too long

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.6.4-5 Bug #1095051 [src:gnocchi] src:gnocchi: fails to migrate to testing for too long Marked as fixed in versions gnocchi/4.6.4-5. Bug #1095051 [src:gnocchi] src:gnocchi: fails to migrate to testing for too long Marked Bug as done -- 1095051: https://bu

Bug#1095051: src:gnocchi: fails to migrate to testing for too long

2025-02-02 Thread Paul Gevers
Source: gnocchi Version: 4.6.4-4 Severity: serious Control: close -1 4.6.4-5 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), You added autopkgtests to your package, however they fail on i386 (seems time_t related, I suspect those tests can

Bug#876231: marked as done (ruby-nmatrix: FTBFS with GCC 7: error: call of overloaded 'abs(nm::Rational&)' is ambiguous)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 3 Feb 2025 07:11:37 +0100 with message-id <20250203061137.3lw6wayu4xs6g...@jwilk.net> and subject line Re: Bug#876231: ruby-nmatrix: FTBFS with GCC 7: error: call of overloaded 'abs(nm::Rational&)' is ambiguous has caused the Debian Bug report #876231, regarding ruby-nmatri

Processed: reassign 1095004 to src:lomiri-online-accounts-plugins

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1095004 src:lomiri-online-accounts-plugins 0.18-1 Bug #1095004 [src:lomiri-online-account-plugins] lomiri-online-accounts-plugins: Unsatisfiable Depends: libaccount-plugin-generic-oauth Warning: Unknown package 'src:lomiri-online-accoun

Bug#1094893: Fixed upstream; need new upstream release

2025-02-02 Thread Singer, Leo P. (GSFC-6610)
Tags: fixed-upstream See https://github.com/astropy/astropy-healpix/pull/234

Bug#1075615: marked as done (vbetool: ftbfs with GCC-14)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 01:49:17 + with message-id and subject line Bug#1075615: fixed in vbetool 1.1-6 has caused the Debian Bug report #1075615, regarding vbetool: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: reassign src:jami bugs to package jami in prep for src:ring's removal

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 832067 jami 20160720.3.73cfbb9~dfsg1-5 Bug #832067 [ring] ring: No interaction via system tray in plasma5 (KDE) Bug reassigned from package 'ring' to 'jami'. No longer marked as found in versions ring/20160720.3.73cfbb9~dfsg1-5. Ignoring

Processed: Re: jami: Fails to build with webrtc-audio-processing

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1073942 ftbfs sid trixie experimental Bug #1073942 [jami] jami: Fails to build with webrtc-audio-processing Added tag(s) experimental, trixie, sid, and ftbfs. > End of message, stopping processing here. Please contact me if you need assistan

Bug#1089549: marked as done (exifprobe FTBFS on 32bit time64 architectures: ciff.c:450:26: error: passing argument 1 of ‘gmtime’ from incompatible pointer type [-Wincompatible-pointer-types])

2025-02-02 Thread Debian Bug Tracking System
Your message dated Mon, 03 Feb 2025 00:19:43 + with message-id and subject line Bug#1089549: fixed in exifprobe 2.0.1+git20201230.eee65ff-1 has caused the Debian Bug report #1089549, regarding exifprobe FTBFS on 32bit time64 architectures: ciff.c:450:26: error: passing argument 1 of ‘gmtime’

Bug#1095033: FTBFS: cruft-ng 0.9.65

2025-02-02 Thread Jing Luo
Control: close -1 Hi, On 2025-02-03 06:00, Jochen Sprickerhof wrote: Hi Jing, [...] I can't reproduce this, i.e. this works on a trixie system: sbuild --chroot-mode=unshare --dist=unstable cruft-ng Can you share your complete build log? I couldn't reproduce it either using unshare, so it

Processed: Re: Bug#1095033: FTBFS: cruft-ng 0.9.65

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #1095033 [src:cruft-ng] FTBFS: cruft-ng 0.9.65 Marked Bug as done -- 1095033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1089549: marked as pending in exifprobe

2025-02-02 Thread Sven Geuer
Control: tag -1 pending Hello, Bug #1089549 in exifprobe 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/pkg-security-team/exifprobe/-/commit/a7de418128854789ce

Processed: Bug#1089549 marked as pending in exifprobe

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1089549 [src:exifprobe] exifprobe FTBFS on 32bit time64 architectures: ciff.c:450:26: error: passing argument 1 of ‘gmtime’ from incompatible pointer type [-Wincompatible-pointer-types] Added tag(s) pending. -- 1089549: https://bugs.debian.org

Bug#1090266: marked as done (python-babel: FTBFS: AssertionError: assert '8.1.2016' == '8. tammik. 2016')

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 22:39:09 + with message-id and subject line Bug#1090266: fixed in python-babel 2.17.0-1 has caused the Debian Bug report #1090266, regarding python-babel: FTBFS: AssertionError: assert '8.1.2016' == '8. tammik. 2016' to be marked as done. This means that y

Bug#1095033: FTBFS: cruft-ng 0.9.65

2025-02-02 Thread Jochen Sprickerhof
Hi Jing, * Jing Luo [2025-02-02 19:44]: Hi! cruft-ng 0.9.65 fails to build from source. Here is the sbuild log: g++ -g -O2 -ffile-prefix-map=/build/reproducible-path/cruft-ng-0.9.65=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -We

Bug#1094122: marked as done (dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 20:34:30 + with message-id and subject line Bug#1094122: fixed in dqlite 1.18.1-1 has caused the Debian Bug report #1094122, regarding dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be mar

Bug#1092513: exaile: FTBFS: ModuleNotFoundError: No module named 'pipes'

2025-02-02 Thread André Flechs
Hi. I uploaded an update to upstream version 4.1.4-beta1 to m.d.n that fixes this. Please, can you review? Am 08.01.25 um 20:29 schrieb Lucas Nussbaum: Source: exaile Version: 4.1.3+dfsg-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-

Bug#1094102: marked as done (giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 19:49:38 + with message-id and subject line Bug#1094102: fixed in giza 1.4.4-2 has caused the Debian Bug report #1094102, regarding giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1 to be marked as done. This means that you claim that the pro

Bug#1095033: FTBFS: cruft-ng 0.9.65

2025-02-02 Thread Jing Luo
Source: cruft-ng Version: 0.9.65 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, Hi! cruft-ng 0.9.65 fails to build from source. Here is the sbuild log: g++ -g -O2 -ffile-prefix-map=/build/reproducible-path/cruft-ng-0.

Bug#1094718: marked as done (graph-tool: FTBFS with numpy 2.x)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 19:36:59 + with message-id and subject line Bug#1094718: fixed in graph-tool 2.88+ds-1 has caused the Debian Bug report #1094718, regarding graph-tool: FTBFS with numpy 2.x to be marked as done. This means that you claim that the problem has been dealt with

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Ole Streicher
Created #1095028 on xvfb to track this. As a workaround, I add a loop to repeatedly run XW.display = XOpenDisplay (NULL); until it was successfull. https://bugs.debian.org/1095028

Processed: nipype: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095029: nipype: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: nipype Version: 1.9.0-1 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/n/nipype/testing/amd64/57318668/ -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Archit

Bug#1095027: neo: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: neo Version: 0.13.4-1 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/n/neo/testing/amd64/57318667/ Several different failures. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101

Processed: neo: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095026: mdp: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: mdp Version: 3.6-9 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/m/mdp/testing/amd64/57318662/ AttributeError: `np.longfloat` was removed in the NumPy 2.0 release. Use `np.longdouble` instead. -- System Information: Debian Release: trixie/sid APT prefer

Processed: mdp: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095024: joblib: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: joblib Version: 1.3.2-6 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/j/joblib/testing/amd64/57318660/ AttributeError: `np.byte_bounds` was removed in the NumPy 2.0 release. Now it's available under `np.lib.array_utils.byte_bounds` -- System Information:

Processed: joblib: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095023: lmfit-py: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: lmfit-py Version: 1.2.2-4 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/l/lmfit-py/testing/amd64/57318661/ -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Ar

Processed: lmfit-py: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Processed: fiat: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095022: fiat: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: fiat Version: 2019.2.0~git20210419.7d418fa-5 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/f/fiat/testing/amd64/57321987/ AttributeError: module 'numpy' has no attribute 'math'. Did you mean: 'emath'? -- System Information: Debian Release: trixie/sid AP

Processed: dolfin: autopkgtests fail with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095020: dolfin: autopkgtests fail with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: dolfin Version: 2019.2.0~legacy20240219.1c52e83-16 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/d/dolfin/testing/amd64/57313372/ ImportError: cannot import name 'float_' from 'numpy' (/usr/lib/python3/dist- packages/numpy/__init__.py). Did you mean: 'float

Processed: dask: autopkgtest failures with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1095019: dask: autopkgtest failures with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: dask Version: 2024.12.1+dfsg-1 Severity: serious Control: block 1082237 by -1 https://ci.debian.net/packages/d/dask/testing/amd64/57321986/ E AttributeError: module 'numpy' has no attribute 'product' -- System Information: Debian Release: trixie/sid APT prefers unstable APT po

Bug#1085065: vim: FTBFS: failing tests

2025-02-02 Thread Thorsten Glaser
severity 1085065 serious found 1085065 2:9.0.1378-2+deb12u1 thanks This is now affecting stable-security builds.

Processed: Re: vim: FTBFS: failing tests

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1085065 serious Bug #1085065 [src:vim] vim: FTBFS: failing tests Severity set to 'serious' from 'important' > found 1085065 2:9.0.1378-2+deb12u1 Bug #1085065 [src:vim] vim: FTBFS: failing tests Marked as found in versions vim/2:9.0.1378-2

Bug#1094093: marked as done (hippotat: FTBFS: make[1]: *** [Makefile:52: stamp/cargo-build] Error 101)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 18:19:03 + with message-id and subject line Bug#1094093: fixed in hippotat 1.2.0 has caused the Debian Bug report #1094093, regarding hippotat: FTBFS: make[1]: *** [Makefile:52: stamp/cargo-build] Error 101 to be marked as done. This means that you claim t

Bug#1094990: [Pkg-puppet-devel] Bug#1094990: puppet crash on trixie

2025-02-02 Thread Thorsten Alteholz
Hi, On 02.02.25 15:32, Jérôme Charaoui wrote: According to the log it seems like there's a segfault happening in the Ruby SELinux binding. Do you have SELinux installed/enabled on this system? libselinux and ruby-selinux are installed, but I didn't configure SELinux. So it should still hav

Bug#1089574: marked as done (blender:FTBFS:build failure on riscv (error: #error Please add support for your architecture in BLI_build_config.h))

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 18:05:20 + with message-id and subject line Bug#1089574: fixed in blender 4.3.2+dfsg-2 has caused the Debian Bug report #1089574, regarding blender:FTBFS:build failure on riscv (error: #error Please add support for your architecture in BLI_build_config.h) t

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Santiago Vila
El 2/2/25 a las 17:43, Ole Streicher escribió: What happens is that xfvb-run does not really wait until the X server is able to be connected. From its sources:     wait || :     if kill -0 $XVFBPID 2>/dev/null; then     break Good work! which means that it just waits until the X ser

Processed: closing 1091452

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1091452 Bug #1091452 [phoc] Prevent testing migration until it uses a non-buggy, released version supporting wlroots 0.18 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1091452: https://

Bug#1091452: closing 1091452

2025-02-02 Thread Guido Günther
close 1091452 thanks

Bug#1089574: marked as pending in blender

2025-02-02 Thread Matteo F. Vescovi
Control: tag -1 pending Hello, Bug #1089574 in blender 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/multimedia-team/blender/-/commit/1aecaea0a84e69ab38a547c0

Processed: Bug#1089574 marked as pending in blender

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1089574 [src:blender] blender:FTBFS:build failure on riscv (error: #error Please add support for your architecture in BLI_build_config.h) Added tag(s) pending. -- 1089574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089574 Debian Bug Tra

Bug#1094127: marked as done (libmodbus: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 17:19:13 + with message-id and subject line Bug#1094127: fixed in libmodbus 3.1.11-2 has caused the Debian Bug report #1094127, regarding libmodbus: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to

Bug#1070434: marked as done (python-guizero-doc: unhandled symlink to directory conversion: /usr/share/doc/python3-guizero/html)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 16:49:28 + with message-id and subject line Bug#1070434: fixed in python-guizero 1.6.0+ds-1 has caused the Debian Bug report #1070434, regarding python-guizero-doc: unhandled symlink to directory conversion: /usr/share/doc/python3-guizero/html to be marked

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Ole Streicher
After some debugging (thanks to access to a VM provided by Santiago), I found the probably cause here: The test command that fails is tests/C/test-cairo-xw.c and this is the first program that requires X11. This code here: XW.display = XOpenDisplay (NULL); XW.screennum = DefaultScreen (XW.

Processed: Bug ownership for python-guizero

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 1070434 Nick Morrott Bug #1070434 [python-guizero-doc] python-guizero-doc: unhandled symlink to directory conversion: /usr/share/doc/python3-guizero/html Owner recorded as Nick Morrott . > owner 1079231 Nick Morrott Bug #1079231 [wnpp] O:

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Santiago Vila
El 2/2/25 a las 15:22, Ole Streicher escribió: which means we rely on a program which segfaults to determine if the package is ok or not. In my opinion a test which segfaults is not to be trusted and we might better disable it. Not sure I understand this. As I said, I also cannot reproduce the

Bug#1092890: mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault

2025-02-02 Thread Dmitry Shachnev
On Wed, Jan 29, 2025 at 11:54:34PM +0300, Dmitry Shachnev wrote: > In other news, I tried to use different linkers and linker options. With all > linkers, it crashes, but in a bit different ways: > > - bfd (default): jump happens to stderr(). > > - gold: jump happens to some incorrect place in libg

Processed: tagging 1093243

2025-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1093243 + fixed-upstream Bug #1093243 [src:linux] linux-image-6.1.0-29-amd64 causes mariadb hangs Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1093243: https://bugs.debian.org/

Bug#1094042: marked as done (nanoc: FTBFS: ERROR: Test "ruby3.3" failed: Failure/Error: expect { subject }.to raise_error(Nanoc::Core::Errors::CannotGetCompiledContentOfBinaryItem, 'You cannot ac

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 14:45:22 + with message-id and subject line Bug#1094042: fixed in nanoc 4.13.3-2 has caused the Debian Bug report #1094042, regarding nanoc: FTBFS: ERROR: Test "ruby3.3" failed: Failure/Error: expect { subject }.to raise_error(Nanoc::Core::Errors::Can

Bug#1094990: [Pkg-puppet-devel] Bug#1094990: puppet crash on trixie

2025-02-02 Thread Jérôme Charaoui
Hello, Le 2025-02-02 à 05 h 01, Thorsten Alteholz a écrit : Source: puppet-agent Version: 8.10.0-2.1 Severity: serious Hi, when running "puppet agent -v -d -t" on Debian Trixie, I get the attached backtrace. Is there some dependency missing? As this happens on several VMs, I selected Severit

Bug#1073508: Bug#1074338: Bug#1073508: Bug#1074338: src:libxml2: fails to migrate to testing for too long: unresolved RC issue

2025-02-02 Thread Aron Xu
Hi, On 2025年1月29日周三 19:32 Santiago Ruano Rincón wrote: > Hi Aron, > > Thanks a lot for your work on libxml2! > > El 21/08/24 a las 19:32, Aron Xu escribió: > > On Mon, Aug 19, 2024 at 3:54 PM Emilio Pozuelo Monfort > wrote: > > > > > > On 17/08/2024 11:13, Paul Gevers wrote: > > > > Hi, > > >

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Ole Streicher
Hi Santiago, Am 02.02.25 um 13:45 schrieb Santiago Vila: This package FTBFS 70% of the time for me when I try to build it on a single-CPU machine. Please try GRUB_CMDLINE_LINUX="nr_cpus=1" or contact me privately if you need a VM to reproduce it. I tried this on my laptop (AMD Ryzen 7; /proc/

Bug#1088523: Acknowledgement (oxigraph: FTBFS with librocksdb9.7-dev)

2025-02-02 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2025-01-25 10:15:01) > Quoting Otto Kekäläinen (2025-01-25 06:41:58) > > Sorry for the long delay, I didn't have time to import new RocksDB > > until yesterday and today. I have now a MR pending at > > https://salsa.debian.org/debian/rocksdb/-/merge_requests/9 for > > co-m

Bug#1095006: gumbo-parser: downstream soname bump

2025-02-02 Thread Jeremy Bícha
Source: gumbo-parser Version: 0.13.0+dfsg-2 Severity: serious X-Debbugs-CC: debian-rele...@lists.debian.org In an attempt to fix https://bugs.debian.org/1092247 a patch [1] was added to bump the soname from 2 to 3. However, this patch is unique to Debian and is not applied upstream. I don't thin

Bug#1094042: marked as pending in nanoc

2025-02-02 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #1094042 in nanoc 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/ruby-team/nanoc/-/commit/b734f76f5399a89e9290957c2de80c7642

Processed: Bug#1094042 marked as pending in nanoc

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1094042 [src:nanoc] nanoc: FTBFS: ERROR: Test "ruby3.3" failed: Failure/Error: expect { subject }.to raise_error(Nanoc::Core::Errors::CannotGetCompiledContentOfBinaryItem, 'You cannot access the compiled content of a binary item representa

Bug#1095005: lomiri-keyboard-greek: unsatisfiable dependency

2025-02-02 Thread Jeremy Bícha
Package: lomiri-keyboard-greek Version: 1.0.2-3 Severity: serious X-Debbugs-CC: sunwea...@debian.org lomiri-keyboard is unable to migrate to Testing because lomiri-keyboard-greek depends on myspell-el-gr which was removed from Debian after lomiri-keyboard was originally built for Debian but before

Bug#1095004: lomiri-online-accounts-plugins: Unsatisfiable Depends: libaccount-plugin-generic-oauth

2025-02-02 Thread Jeremy Bícha
Source: lomiri-online-account-plugins Version: 0.18-1 Severity: serious X-Debbugs-CC: sunwea...@debian.org lomiri-online-accounts-plugins is unable to migrate to Testing because its binary packages have Depends: libaccount-plugin-generic-oauth but that package does not exist in Debian. https://tr

Bug#1094758: marked as done (sep: FTBFS with numpy 2.x: 'int_t' is not a type identifier)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 13:13:26 + with message-id and subject line Bug#1094758: fixed in sep 1.2.1-8 has caused the Debian Bug report #1094758, regarding sep: FTBFS with numpy 2.x: 'int_t' is not a type identifier to be marked as done. This means that you claim that the problem h

Bug#1094909: marked as done (fast-histogram: missing dependency on numpy abi)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 13:06:48 + with message-id and subject line Bug#1094909: fixed in fast-histogram 0.14-4 has caused the Debian Bug report #1094909, regarding fast-histogram: missing dependency on numpy abi to be marked as done. This means that you claim that the problem has

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Santiago Vila
Note: When a package builds ok in my setup, I delete old build logs, but I start to collect build logs when it fails randomly, as in this case. Apparently this worked ok in 1.4.1-2 and started to fail in version 1.4.4-1. So, I suspect of this change as the trigger: * Run tests in xvfb Thanks.

Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Santiago Vila
Hello. This package FTBFS 70% of the time for me when I try to build it on a single-CPU machine. Please try GRUB_CMDLINE_LINUX="nr_cpus=1" or contact me privately if you need a VM to reproduce it. In this case I see this in the build log: ../../build/test-driver: line 112: 254916 Segmentation

Processed: Re: Bug#1094102: giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > tags -1 unreproducible moreinfo Bug #1094102 [src:giza] giza: FTBFS: make[6]: *** [Makefile:921: test-suite.log] Error 1 Added tag(s) moreinfo and unreproducible. -- 1094102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094102 Debian Bug Tracking System Cont

Bug#1092081: marked as done (virtualbox ftbfs with Python 3.13 as the default)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 12:26:13 + with message-id and subject line Bug#1092081: fixed in virtualbox 7.0.20-dfsg-1.2 has caused the Debian Bug report #1092081, regarding virtualbox ftbfs with Python 3.13 as the default to be marked as done. This means that you claim that the probl

Bug#1094883: marked as done (astropy FTBFS on mips64el)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 12:04:42 + with message-id and subject line Bug#1094883: fixed in astropy 7.0.0-4 has caused the Debian Bug report #1094883, regarding astropy FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1094883: marked as pending in astropy

2025-02-02 Thread Ole Streicher
Control: tag -1 pending Hello, Bug #1094883 in astropy 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/debian-astro-team/astropy/-/commit/2e0f347945494c0f04c506

Processed: Bug#1094883 marked as pending in astropy

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1094883 [src:astropy] astropy FTBFS on mips64el Added tag(s) pending. -- 1094883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: python-meshio: FTBFS with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/nschloe/meshio/issues/1499 Bug #1094985 [src:python-meshio] python-meshio: FTBFS with numpy 2.x Set Bug forwarded-to-address to 'https://github.com/nschloe/meshio/issues/1499'. -- 1094985: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#1094985: python-meshio: FTBFS with numpy 2.x

2025-02-02 Thread Francesco Ballarin
Source: python-meshio Followup-For: Bug #1094985 X-Debbugs-Cc: francesco.balla...@unicatt.it Control: forwarded -1 https://github.com/nschloe/meshio/issues/1499 Thanks for the report. The bug is open upstream at https://github.com/nschloe/meshio/issues/1499, and is currently waiting for a fix. Lat

Bug#1093043: dcmtk: leftover CVE status.

2025-02-02 Thread Étienne Mollier
Good day, Étienne Mollier, on 2025-02-01: > I believe these changes in dcmtk are good enough to contact the > stable release manager for an upload in the upcoming point > release and will proceed. And done, this is #1094991. Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b

Bug#1094992: haskell-gtk3: FTBFS: Conflicting exports for ‘WrapNone’

2025-02-02 Thread Sebastian Ramacher
Source: haskell-gtk3 Version: 0.15.9-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=haskell-gtk3&arch=amd64&ver=0.15.9-1%2Bb2&stamp=1738441079&raw=0 [2

Bug#1094993: haskell-gtk: FTBFS: Conflicting exports for ‘WrapNone’

2025-02-02 Thread Sebastian Ramacher
Source: haskell-gtk Version: 0.15.9-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=haskell-gtk&arch=amd64&ver=0.15.9-1%2Bb2&stamp=1738440872&raw=0 [207

Bug#1092471: pyqso: Type Error: takes 2 positional arguments but 3 were given

2025-02-02 Thread Enrico Rossi
Hi, I have patched it on salsa and build. Seems fine. It is waiting for someone with upload right to review it and, eventually, upload. The question *dead upstream* remains for the next stable cycle. Thanks E. -- GPG key: 4096R/5E0195FAF2133176 2010-10-19 Enrico Rossi

Bug#1094984: python-meshplex: FTBFS with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: python-meshplex Version: 0.17.1-4 Severity: serious Tags: ftbfs Control: block 1082237 by -1 Visible on https://ci.debian.net/packages/p/python- meshplex/testing/amd64/57299021/ but also fails during package build. _ ERROR collecting tests/test_remove_cells.py

Processed: python-meshio: FTBFS with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1094985: python-meshio: FTBFS with numpy 2.x

2025-02-02 Thread Andrey Rakhmatullin
Source: python-meshio Version: 7.0.0-really-5.3.5-3 Severity: serious Tags: ftbfs Control: block 1082237 by -1 Visible on https://ci.debian.net/packages/p/python- meshio/testing/amd64/57299020/ but also happens during package build. FAILED tests/test_dolfin.py::test_dolfin[mesh3] - ValueError: co

Processed: python-meshplex: FTBFS with numpy 2.x

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > block 1082237 by -1 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1063599 1066316 1067335 1071807 1086577 1086578 1088823 1090292 1091809 1091938 1092083 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375

Bug#1094444: marked as done (cmake breaks lfortran autopkgtest)

2025-02-02 Thread Debian Bug Tracking System
Your message dated Sun, 02 Feb 2025 08:35:31 + with message-id and subject line Bug#109: fixed in lfortran 0.45.0-1 has caused the Debian Bug report #109, regarding cmake breaks lfortran autopkgtest to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#1094069: rsyslog: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2025-02-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1094069 [src:rsyslog] rsyslog: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Severity set to 'important' from 'serious' -- 1094069: https://bugs.debian.org/cgi-bin/bugreport.cgi?

Bug#1094069: rsyslog: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2025-02-02 Thread Michael Biebl
Control: severity -1 important Hi Lucas On Sat, 25 Jan 2025 17:49:11 +0100 Lucas Nussbaum wrote: However, I tried it again and now I can't reproduce it. So there's probably something random/specific about the environment. I'm fine with downgrading the severity, but it might be worth keeping t