Bug#1073459: uhttpmock0: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory

2024-06-16 Thread Lucas Nussbaum
Source: uhttpmock0 Version: 0.5.5-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering direc

Bug#1073463: bacula-doc: FTBFS: grep: tcrm0700.log: No such file or directory

2024-06-16 Thread Lucas Nussbaum
Source: bacula-doc Version: 9.6.7-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering direc

Bug#1073465: python-wsgi-intercept: FTBFS: tests failed

2024-06-16 Thread Lucas Nussbaum
Source: python-wsgi-intercept Version: 1.9.3-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Ent

Bug#1073466: 389-ds-base: FTBFS: make[2]: *** [Makefile:13095: /<>/rs/rnsslapd/release/librnsslapd.a] Error 101

2024-06-16 Thread Lucas Nussbaum
Source: 389-ds-base Version: 2.4.5+dfsg1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Enterin

Bug#1073467: freecol: FTBFS: make: *** [debian/rules:8: binary] Error 25

2024-06-16 Thread Lucas Nussbaum
Source: freecol Version: 1.1.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules bin

Bug#1073464: libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory

2024-06-16 Thread Lucas Nussbaum
Source: libgweather4 Version: 4.4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering dir

Bug#1073473: magit: FTBFS: make[3]: *** [Makefile:6: test] Error 1

2024-06-16 Thread Lucas Nussbaum
Source: magit Version: 3.3.0+git20240412.1.da14749d-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[

Bug#1073471: quickml: FTBFS: lib/quickml/gettext.rb:30:in `load': messages.ja:5: invalid multibyte char (EUC-JP) (SyntaxError)

2024-06-16 Thread Lucas Nussbaum
Source: quickml Version: 0.8-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory

Bug#1073472: lilypond: FTBFS: grep: tcrm1200.log: No such file or directory

2024-06-16 Thread Lucas Nussbaum
Source: lilypond Version: 2.24.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering direct

Bug#1073474: wp2latex: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

2024-06-16 Thread Lucas Nussbaum
Source: wp2latex Version: 4.7~ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering direct

Bug#1073476: uhttpmock: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory

2024-06-16 Thread Lucas Nussbaum
Source: uhttpmock Version: 0.10.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering direc

Bug#1073477: python-livereload: FTBFS: make[1]: *** [debian/rules:23: override_dh_installman] Error 1

2024-06-16 Thread Lucas Nussbaum
Source: python-livereload Version: 2.6.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enterin

Bug#1073479: gdcm: FTBFS: make[1]: *** [debian/rules:108: override_dh_auto_configure] Error 2

2024-06-16 Thread Lucas Nussbaum
Source: gdcm Version: 3.0.24-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory

Bug#1073481: pydantic-core: FTBFS: make[1]: *** [debian/rules:15: execute_before_dh_auto_build] Error 101

2024-06-16 Thread Lucas Nussbaum
Source: pydantic-core Version: 2.11.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering d

Bug#1073483: apt-src: FTBFS: make: *** [debian/rules:23: clean] Error 25

2024-06-16 Thread Lucas Nussbaum
Source: apt-src Version: 0.25.3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh_te

Bug#1073480: qt6-tools: FTBFS: make[1]: llvm-config: No such file or directory

2024-06-16 Thread Lucas Nussbaum
Source: qt6-tools Version: 6.6.2-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering direct

Bug#1073482: kissplice: FTBFS: make[3]: *** [doc/CMakeFiles/doc.dir/build.make:78: doc/user_guide.pdf] Error 1

2024-06-16 Thread Lucas Nussbaum
Source: kissplice Version: 2.6.2-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering direct

Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-06-16 Thread Jörn Heusipp
This is fixed in upstream 6.10: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.10-rc3&id=2a38e4ca302280fdcce370ba2bee79bac16c4587 and should also end up back-ported in 6.9.5: https://lore.kernel.org/all/20240616133543.1590007-1-osm...@heusipp.de/ Regards, Jör

Bug#1073487: cdist: FTBFS: Could not import extension cdist.sphinxext.manpage (exception: No module named 'six')

2024-06-16 Thread Lucas Nussbaum
Source: cdist Version: 7.0.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory

Bug#1073488: python-releases: FTBFS: Could not import extension releases (exception: No module named 'six')

2024-06-16 Thread Lucas Nussbaum
Source: python-releases Version: 1.6.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering

Bug#1073486: genimage: FTBFS: ./test/test-setup.sh: line 117: fdisk: command not found

2024-06-16 Thread Lucas Nussbaum
Source: genimage Version: 17-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-16 Thread Paul Gevers
Hi Dirk, On 16-06-2024 2:42 p.m., Dirk Eddelbuettel wrote: I may need a hgand with riscv64. That's normally a question to the porters, in CC now, so they can have a look. The 1.34-1 revision needed some build changes I had done poorly in such a way that the -O0 no longer applied to some ar

Bug#1073459: marked as done (uhttpmock0: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 10:12:28 -0400 with message-id and subject line Re: Bug#1073459: uhttpmock0: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory has caused the Debian Bug repor

Bug#1073422: marked as done (msgraph: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 4)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 10:10:39 -0400 with message-id and subject line Re: Bug#1073422: msgraph: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 4 has caused the Debian Bug report

Bug#1073476: marked as done (uhttpmock: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 10:11:35 -0400 with message-id and subject line Re: Bug#1073476: uhttpmock: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory has caused the Debian Bug report

Processed: Re: Bug#1073332: mapnik: FTBFS: src/libxml2_loader.cpp:82:51: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive]

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 mapnik/4.0.0~rc1+ds-1~exp1 Bug #1073332 [src:mapnik] mapnik: FTBFS: src/libxml2_loader.cpp:82:51: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive] Marked as fixed in versions mapnik/

Bug#1073332: mapnik: FTBFS: src/libxml2_loader.cpp:82:51: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive]

2024-06-16 Thread Sebastiaan Couwenberg
Control: fixed -1 mapnik/4.0.0~rc1+ds-1~exp1 On 6/16/24 2:48 PM, Lucas Nussbaum wrote: c++ -o src/json/mapnik_json_feature_collection_grammar.o -c -std=c++14 -DU_USING_ICU_NAMESPACE=0 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-secur

Processed: Bug#1073337 marked as pending in gupnp-tools

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073337 [src:gupnp-tools] gupnp-tools: FTBFS: ../src/common/pretty-print.c:37:9: error: ‘xmlRecoverMemory’ is deprecated [-Werror=deprecated-declarations] Added tag(s) pending. -- 1073337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073

Bug#1073337: marked as pending in gupnp-tools

2024-06-16 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1073337 in gupnp-tools 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/gnome-team/gupnp-tools/-/commit/dd02718c6de2db3f094c4

Bug#1073474: marked as done (wp2latex: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 14:35:56 + with message-id and subject line Bug#1073474: fixed in wp2latex 4.7~ds-2 has caused the Debian Bug report #1073474, regarding wp2latex: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. Thi

Bug#1073337: marked as done (gupnp-tools: FTBFS: ../src/common/pretty-print.c:37:9: error: ‘xmlRecoverMemory’ is deprecated [-Werror=deprecated-declarations])

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 14:35:02 + with message-id and subject line Bug#1073337: fixed in gupnp-tools 0.12.1-2 has caused the Debian Bug report #1073337, regarding gupnp-tools: FTBFS: ../src/common/pretty-print.c:37:9: error: ‘xmlRecoverMemory’ is deprecated [-Werror=deprecated-de

Bug#1073454: marked as pending in sphinx

2024-06-16 Thread Dmitry Shachnev
Control: tag -1 pending Hello, Bug #1073454 in sphinx 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/python-team/packages/sphinx/-/commit/510066c27657ed182b571

Processed: Bug#1073454 marked as pending in sphinx

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

Processed: Merging 1073395 1073454

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1073395 1073454 Bug #1073395 [src:sphinx] sphinx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Bug #1073395 [src:sphinx] sphinx: FTBFS: dh_auto_test: error: pybuild --test

Bug#1073218: src:vim-eblook: fails to migrate to testing for too long: uploader built arch:all binaries

2024-06-16 Thread Yukiharu YABUKI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thank you for answering quickly. Okay I realized that mistaken point. I uploaded binary and source. That is wrong. I needed to upload source only. And I choose 2) Wait option. You taught me improving point. Thanks again. Best Regard. Yukiharu O

Bug#1060582: marked as done (rust-whoami: Please switch Build-Depends to systemd-dev)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 14:49:21 + with message-id and subject line Bug#1060582: fixed in rust-whoami 1.4.1-2 has caused the Debian Bug report #1060582, regarding rust-whoami: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the probl

Processed: src:rust-snow: fails to migrate to testing for too long: autopkgtest regression

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.9.6-4 Bug #1073499 [src:rust-snow] src:rust-snow: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-snow/0.9.6-4. Bug #1073499 [src:rust-snow] src:rust-snow: fails to migrate to testing for too long: autopk

Bug#1073499: src:rust-snow: fails to migrate to testing for too long: autopkgtest regression

2024-06-16 Thread Paul Gevers
Source: rust-snow Version: 0.9.6-1 Severity: serious Control: close -1 0.9.6-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1071537 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstab

Bug#1073332: marked as done (mapnik: FTBFS: src/libxml2_loader.cpp:82:51: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive])

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 15:04:34 + with message-id and subject line Bug#1073332: fixed in mapnik 3.1.0+ds-8 has caused the Debian Bug report #1073332, regarding mapnik: FTBFS: src/libxml2_loader.cpp:82:51: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} t

Bug#1073408: rust-sequoia-sq: FTBFS: unsatisfiable build-dependencies: librust-zstd-0.12-dev, librust-zstd-safe-6-dev

2024-06-16 Thread Holger Levsen
On Sun, Jun 16, 2024 at 03:16:49PM +0200, Lucas Nussbaum wrote: > Source: rust-sequoia-sq > Version: 0.33.0-3 [...] > During a rebuild of all packages in sid, your package failed to build > on amd64. thanks, this will be fixed by a new upstream version soon to be uploaded. -- cheers, H

Bug#1073301: marked as done (compiz-plugins-extra: FTBFS: addhelper.c:332:10: error: implicit declaration of function ‘malloc’ [-Werror=implicit-function-declaration])

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 15:49:15 + with message-id and subject line Bug#1073301: fixed in compiz-plugins-experimental 2:0.8.18-4 has caused the Debian Bug report #1073301, regarding compiz-plugins-extra: FTBFS: addhelper.c:332:10: error: implicit declaration of function ‘malloc’ [

Bug#1073301: marked as done (compiz-plugins-extra: FTBFS: addhelper.c:332:10: error: implicit declaration of function ‘malloc’ [-Werror=implicit-function-declaration])

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 15:49:26 + with message-id and subject line Bug#1073301: fixed in compiz-plugins-extra 2:0.8.18-4 has caused the Debian Bug report #1073301, regarding compiz-plugins-extra: FTBFS: addhelper.c:332:10: error: implicit declaration of function ‘malloc’ [-Werror

Bug#1073301: marked as done (compiz-plugins-extra: FTBFS: addhelper.c:332:10: error: implicit declaration of function ‘malloc’ [-Werror=implicit-function-declaration])

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 15:49:36 + with message-id and subject line Bug#1073301: fixed in compiz-plugins-main 2:0.8.18-6 has caused the Debian Bug report #1073301, regarding compiz-plugins-extra: FTBFS: addhelper.c:332:10: error: implicit declaration of function ‘malloc’ [-Werror=

Bug#1073162: marked as pending in yojson

2024-06-16 Thread Julien Puydt
Control: tag -1 pending Hello, Bug #1073162 in yojson 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/ocaml-team/yojson/-/commit/0b97f0bcdba536ebd55ffe5d62d3c3d

Processed: Bug#1073162 marked as pending in yojson

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073162 [yojson-tools] yojson-tools: missing Breaks+Replaces: libyojson-ocaml-dev (<< 2.2) Added tag(s) pending. -- 1073162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073162 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1073162: marked as done (yojson-tools: missing Breaks+Replaces: libyojson-ocaml-dev (<< 2.2))

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 16:21:32 + with message-id and subject line Bug#1073162: fixed in yojson 2.2.1-2 has caused the Debian Bug report #1073162, regarding yojson-tools: missing Breaks+Replaces: libyojson-ocaml-dev (<< 2.2) to be marked as done. This means that you claim that th

Bug#1073329: marked as pending in libmusicbrainz5

2024-06-16 Thread Sebastian Ramacher
Control: tag -1 pending Hello, Bug #1073329 in libmusicbrainz5 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/libmusicbrainz/-/commit/cb7aa94ec

Processed: Bug#1073329 marked as pending in libmusicbrainz5

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073329 [src:libmusicbrainz5] libmusicbrainz5: FTBFS: xmlParser.cc:59:44: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlErrorPtr’ {aka ‘_xmlError*’} [-fpermissive] Added tag(s) pending. -- 1073329: https://bu

Bug#1073504: napari: fails to build wheel with python3.12

2024-06-16 Thread Étienne Mollier
Source: napari Version: 0.5.0~a1-6 Severity: serious Tags: ftbfs Justification: ftbfs Dear Maintainer, I noticed that napari is currently failing to build from source in sid. Symptoms appear somewhat early in the build log during the wheel building, as it fails first with python3.12, but then go

Bug#1073259: libyojson-ocaml-dev should depend on yojson-tools

2024-06-16 Thread julien . puydt
Hi, Le samedi 15 juin 2024 à 16:43 +0200, Johannes Schauer Marin Rodrigues a écrit : > > Quoting Johannes Schauer Marin Rodrigues (2024-06-15 14:03:34) > > > > Julien, do you want to take care of that rebuild or should I? > Sorry I was away for most of the weekend, but yes, I didn't test my la

Bug#1073313: gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’

2024-06-16 Thread Yavor Doganov
Control: fixed -1 1.30.0-1 Control: tags -1 + pending [ CCing libxml2@packages.d.o ] Lucas Nussbaum wrote: > Source: gnustep-base > Version: 1.29.0-7 > Severity: serious ... > > GSXML.m: In function ‘getEntityDefault’: > > GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no membe

Processed: Re: Bug#1073313: gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.30.0-1 Bug #1073313 [src:gnustep-base] gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’ Marked as fixed in versions gnustep-base/1.30.0-1. > tags -1 + pending Bug #1073313 [src:gnustep-base]

Bug#1073329: marked as done (libmusicbrainz5: FTBFS: xmlParser.cc:59:44: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlErrorPtr’ {aka ‘_xmlError*’} [-fpermissive])

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 16:49:28 + with message-id and subject line Bug#1073329: fixed in libmusicbrainz5 5.1.0+git20150707-11 has caused the Debian Bug report #1073329, regarding libmusicbrainz5: FTBFS: xmlParser.cc:59:44: error: invalid conversion from ‘const xmlError*’ {aka ‘co

Bug#1073313: gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’

2024-06-16 Thread Thorsten Glaser
On Sun, 16 Jun 2024, Yavor Doganov wrote: >IMVHO removing a public struct member constitutes an API break. Definitely. I just took a peek at this. >It is also an ABI break, because if a program or a library accesses >such member and is compiled against an old libxml2 version that is >supposed to

Bug#1073313: gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’

2024-06-16 Thread Thorsten Glaser
clone 1073313 -1 reassign -1 libxml2 found -1 2.12.7+dfsg-3 retitle -1 libxml2: just another API+ABI break; please bump soname severity -1 serious tags -1 sid thanks On Sun, 16 Jun 2024, Thorsten Glaser wrote: >This is not the first time in *very* recent history that libxml2 >has an ABI break (e.

Processed: Re: Bug#1073313: gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1073313 -1 Bug #1073313 [src:gnustep-base] gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’ Bug 1073313 cloned as bug 1073508 > reassign -1 libxml2 Bug #1073508 [src:gnustep-ba

Bug#1073313: another libxml2 ABI break, might need RM attention (Re: Bug#1073313: gnustep-base: FTBFS: GSXML.m:2674:22: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’)

2024-06-16 Thread Thorsten Glaser
On Sun, 16 Jun 2024, Thorsten Glaser wrote: >Better prevent this from landing in trixie until the package >gets its soname bumped. In fact, unless someone has the tuits to diff every single API and ABI surface of the package between trixie (ideally bookworm) and sid versions, it would be best if

Bug#1073515: git: FTBFS on mips64el

2024-06-16 Thread Jonathan Nieder
Source: git Version: 1:2.45.2-1 Severity: serious Justification: FTBFS (but possibly unreproducibly?) https://buildd.debian.org/status/logs.php?pkg=git&arch=mips64el shows the git package fairly regularly failing to build on mips64el this year. Example failure: ``` expecting success of 5526.25 '

Bug#1073516: tree-style-tab: remove?

2024-06-16 Thread Chris Hofstaedtler
Source: tree-style-tab Version: 3.5.20-1 Severity: serious Tags: sid trixie tree-style-tab wasn't updated since 2020, currently build-depends on mozilla-devscripts (to be removed), and doesn't build because python3-librdf disappeared (#1071896). #993548 also suggests it does not work with current

Bug#1073517: src:gcc-bpf: fails to migrate to testing for too long: blocked by build dependency

2024-06-16 Thread Paul Gevers
Source: gcc-bpf Version: 14 Severity: serious Control: close -1 15 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 days as having a Rele

Processed: src:gcc-bpf: fails to migrate to testing for too long: blocked by build dependency

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 15 Bug #1073517 [src:gcc-bpf] src:gcc-bpf: fails to migrate to testing for too long: blocked by build dependency Marked as fixed in versions gcc-bpf/15. Bug #1073517 [src:gcc-bpf] src:gcc-bpf: fails to migrate to testing for too long: blocked by build depe

Bug#1073451: wlgreet: FTBFS: unsatisfiable build-dependency: librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed

2024-06-16 Thread James McCoy
On Sun, Jun 16, 2024 at 03:17:54PM GMT, Lucas Nussbaum wrote: > Relevant part (hopefully): > > +--+ > > | Install package build dependencies > >| > > +

Bug#1072366: libndp: CVE-2024-5564

2024-06-16 Thread Moritz Muehlenhoff
On Fri, Jun 14, 2024 at 07:30:46AM +0200, Florian Ernst wrote: > On Thu, Jun 13, 2024 at 08:17:41PM +0200, Moritz Muehlenhoff wrote: > > Thanks, these look good! Please upload to security-master, I'll take care > > of the DSA over the weekend. > > Thanks for verifying, thus just uploaded to securi

Processed: notfound 1068016 in 7.20.15+ds1+~cs214.269.168-3+deb12u1 ..., notfound 1068932 in 2.3.0-3 ...

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # the package bugs need the versioning, not the p-u bugs... > notfound 1068016 7.20.15+ds1+~cs214.269.168-3+deb12u1 Bug #1068016 [release.debian.org] bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2 There is no source info fo

Bug#1073520: coyote: autopkgtest regression: times out

2024-06-16 Thread Paul Gevers
Source: coyote Version: 2022.04.12-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since around November 2023 on ppc64el because it times out. Can you please investigate the situation and fi

Bug#1013302: marked as done (ntopng FTBFS /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this' before calling super in derived class constructors)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 18:50:23 + with message-id and subject line Bug#1013302: fixed in ntopng 5.2.1+dfsg1-2 has caused the Debian Bug report #1013302, regarding ntopng FTBFS /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this'

Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-06-16 Thread Salvatore Bonaccorso
Control: tags -1 + fixed-upstream Hi Jörn, On Sun, Jun 16, 2024 at 03:50:57PM +0200, Jörn Heusipp wrote: > > This is fixed in upstream 6.10: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.10-rc3&id=2a38e4ca302280fdcce370ba2bee79bac16c4587 > > and should als

Processed: Re: Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + fixed-upstream Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot Added tag(s) fixed-upstream. -- 1071378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071378 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-06-16 Thread Jörn Heusipp
Hello ! and should also end up back-ported in 6.9.5: https://lore.kernel.org/all/20240616133543.1590007-1-osm...@heusipp.de/ Thanks for the notification. So this will end in our next upload based on at least 6.9.5. Looks like it just missed 6.9.5. Hopefully it will be in 6.9.6 then. Reg

Processed: limit source to parser, tagging 1073353

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source parser Limiting to bugs with field 'source' containing at least one of 'parser' Limit currently set to 'source':'parser' > tags 1073353 + pending Bug #1073353 [src:parser] parser: FTBFS: ../../src/include/pa_charset.h:145:40: error:

Bug#1073284: marked as done (librust-async-compression-dev: Depends: librust-zstd-safe-6-dev but it is not installable)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 22:11:35 +0200 with message-id <2e7fa26a-fcf9-4d6d-b1f5-2c953e211...@riseup.net> and subject line has caused the Debian Bug report #1073284, regarding librust-async-compression-dev: Depends: librust-zstd-safe-6-dev but it is not installable to be marked as done

Bug#890601: firmware-free: Source Package Doesn't Contain Source

2024-06-16 Thread Ben Hutchings
Control: clone -1 -2 Control: severity -1 wishlist Control: retitle -2 firmware-free: Incomplete source for carl9170-1.fw On Thu, 2024-06-06 at 21:18 +0200, Bastian Germann wrote: > Hi Ben, > > Am 05.06.24 um 20:59 schrieb Ben Hutchings: > > Please identify precisely which policy requirement is v

Processed (with 2 errors): Re: Bug#890601: firmware-free: Source Package Doesn't Contain Source

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #890601 [firmware-linux-free] firmware-linux-free uses prebuilt blobs instead of building from source Bug 890601 cloned as bug 1073525 1073525 was blocked by: 1050989 994625 1073525 was not blocking any bugs. Ignoring request to alter blocking bugs o

Processed: retitle 1073525 to firmware-free: Incomplete source for carl9170-1.fw

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1073525 firmware-free: Incomplete source for carl9170-1.fw Bug #1073525 [firmware-linux-free] firmware-linux-free uses prebuilt blobs instead of building from source Changed Bug title to 'firmware-free: Incomplete source for carl9170-1.fw

Bug#1037234: marked as done (node-babel7: missing Breaks+Replaces: node-babel-traverse (<< 7))

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:52 + with message-id and subject line Bug#1037234: fixed in node-babel7 7.20.15+ds1+~cs214.269.168-3+deb12u2 has caused the Debian Bug report #1037234, regarding node-babel7: missing Breaks+Replaces: node-babel-traverse (<< 7) to be marked as done. T

Bug#1068918: marked as done (node-zx: FTBFS test suite failure)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:54 + with message-id and subject line Bug#1068918: fixed in node-zx 7.1.1+~cs6.7.23-2+deb12u1 has caused the Debian Bug report #1068918, regarding node-zx: FTBFS test suite failure to be marked as done. This means that you claim that the problem has b

Bug#1068921: marked as done (node-v8-compile-cache: FTBFS in bookworm, test suite fails)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:53 + with message-id and subject line Bug#1068921: fixed in node-v8-compile-cache 2.3.0-3+deb12u1 has caused the Debian Bug report #1068921, regarding node-v8-compile-cache: FTBFS in bookworm, test suite fails to be marked as done. This means that you

Bug#1068933: marked as done (node-babel7: FTBFS in bookworm against nodejs 18.19.0+dfsg-6~deb12u1)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:53 + with message-id and subject line Bug#1068933: fixed in node-babel7 7.20.15+ds1+~cs214.269.168-3+deb12u2 has caused the Debian Bug report #1068933, regarding node-babel7: FTBFS in bookworm against nodejs 18.19.0+dfsg-6~deb12u1 to be marked as done

Bug#1069163: marked as done (libkf5kmanagesieve5: CVE-2023-52723: sends password as username when authenticating against sieve servers)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:50 + with message-id and subject line Bug#1069163: fixed in libkf5ksieve 4:22.12.3-1+deb12u1 has caused the Debian Bug report #1069163, regarding libkf5kmanagesieve5: CVE-2023-52723: sends password as username when authenticating against sieve servers

Bug#1070423: marked as done (php-composer-pcre: missing Breaks+Replaces: composer (<< 2.2))

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:54 + with message-id and subject line Bug#1070423: fixed in php-composer-pcre 3.1.0-1+deb12u1 has caused the Debian Bug report #1070423, regarding php-composer-pcre: missing Breaks+Replaces: composer (<< 2.2) to be marked as done. This means that you

Bug#1072119: marked as done (python-aiosmtpd: CVE-2024-34083)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:55 + with message-id and subject line Bug#1072119: fixed in python-aiosmtpd 1.4.3-1.1+deb12u1 has caused the Debian Bug report #1072119, regarding python-aiosmtpd: CVE-2024-34083 to be marked as done. This means that you claim that the problem has bee

Bug#1072847: marked as done (lacme: Post-issuance validation fails in the default configuration)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 20:33:49 + with message-id and subject line Bug#1072847: fixed in lacme 0.8.2-1+deb12u1 has caused the Debian Bug report #1072847, regarding lacme: Post-issuance validation fails in the default configuration to be marked as done. This means that you claim t

Bug#1072532: NMU: dh-sequence-phpcomposer: stop creating libpcre3 dependencies

2024-06-16 Thread David Prévot
Hi, Le Wed, Jun 12, 2024 at 01:27:29PM +0200, Bastian Germann a écrit : > I am uploading the experimental version to unstable (DELAYED/10) after I have > tested it against various php packages and have not found a problem. Athos just rebuilt all packages build-depending on pkg-php-tools. There a

Bug#1068422: marked as done (can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 21:04:12 + with message-id and subject line Bug#1068422: fixed in dask 2024.5.2+dfsg-1 has caused the Debian Bug report #1068422, regarding can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' objec

Bug#1069821: marked as done (satpy: FTBFS: tests failed)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 21:04:12 + with message-id and subject line Bug#1069821: fixed in dask 2024.5.2+dfsg-1 has caused the Debian Bug report #1069821, regarding satpy: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1073487: marked as done (cdist: FTBFS: Could not import extension cdist.sphinxext.manpage (exception: No module named 'six'))

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 21:19:50 + with message-id and subject line Bug#1073487: fixed in cdist 7.0.0-4 has caused the Debian Bug report #1073487, regarding cdist: FTBFS: Could not import extension cdist.sphinxext.manpage (exception: No module named 'six') to be marked as done. T

Bug#1068500: marked as done (Installs /usr/LICENSE)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 21:24:35 + with message-id and subject line Bug#1068500: fixed in python-xmlrunner 3.2.0-3 has caused the Debian Bug report #1068500, regarding Installs /usr/LICENSE to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1073376: marked as pending in python-fedora

2024-06-16 Thread Sergio Durigan Junior
Control: tag -1 pending Hello, Bug #1073376 in python-fedora 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/python-team/packages/python-fedora/-/commit/709024b

Processed: tagging 1073488

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1073488 + pending Bug #1073488 [src:python-releases] python-releases: FTBFS: Could not import extension releases (exception: No module named 'six') Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assis

Processed: Bug#1073376 marked as pending in python-fedora

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073376 [src:python-fedora] python-fedora: FTBFS: ModuleNotFoundError: No module named 'six' Added tag(s) pending. -- 1073376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073376 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#1069838: khard: Builds fine here.

2024-06-16 Thread Martin Dosch
Package: khard Followup-For: Bug #1069838 Dear Maintainer, I just built khard locally and it builds fine. Best regards, Martin -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debu

Bug#1073365: marked as done (django-cas-server: FTBFS: ModuleNotFoundError: No module named 'six')

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 21:50:15 + with message-id and subject line Bug#1073365: fixed in django-cas-server 2.0.0-3 has caused the Debian Bug report #1073365, regarding django-cas-server: FTBFS: ModuleNotFoundError: No module named 'six' to be marked as done. This means that you c

Bug#1073376: marked as done (python-fedora: FTBFS: ModuleNotFoundError: No module named 'six')

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 21:53:27 + with message-id and subject line Bug#1073376: fixed in python-fedora 1.1.1-2 has caused the Debian Bug report #1073376, regarding python-fedora: FTBFS: ModuleNotFoundError: No module named 'six' to be marked as done. This means that you claim tha

Bug#1071295: marked as done (apt-cacher-ng: FTBFS: src/meta.h:326:44: error: operator '!' has no right operand)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 22:05:00 + with message-id and subject line Bug#1071295: fixed in apt-cacher-ng 3.7.4-1.1 has caused the Debian Bug report #1071295, regarding apt-cacher-ng: FTBFS: src/meta.h:326:44: error: operator '!' has no right operand to be marked as done. This mean

Processed: reassign 1073480 to libzstd-dev ...

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1073480 libzstd-dev libzstd/1.5.6+dfsg-1 Bug #1073480 [src:qt6-tools] qt6-tools: FTBFS: make[1]: llvm-config: No such file or directory Bug reassigned from package 'src:qt6-tools' to 'libzstd-dev'. No longer marked as found in versions q

Processed: affects 1073480

2024-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1073480 + src:qt6-tools Bug #1073480 [libzstd-dev] zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd Added indication that 1073480 affects src:qt6-tools > thanks Stopping processing here. Please

Bug#1073525: marked as done (firmware-free: Incomplete source for carl9170-1.fw)

2024-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 22:22:43 + with message-id and subject line Bug#1073525: fixed in firmware-free 20240610-1 has caused the Debian Bug report #1073525, regarding firmware-free: Incomplete source for carl9170-1.fw to be marked as done. This means that you claim that the probl

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-16 Thread Dirk Eddelbuettel
Hi Paul, Thanks for the prompt and detailed reply. On 16 June 2024 at 16:13, Paul Gevers wrote: | Hi Dirk, | | On 16-06-2024 2:42 p.m., Dirk Eddelbuettel wrote: | > I may need a hgand with riscv64. | | That's normally a question to the porters, in CC now, so they can have a | look. | | > Th

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-16 Thread Bo YU
Hi, On Mon, Jun 17, 2024 at 6:41 AM Dirk Eddelbuettel wrote: > > > Hi Paul, > > Thanks for the prompt and detailed reply. > > On 16 June 2024 at 16:13, Paul Gevers wrote: > | Hi Dirk, > | > | On 16-06-2024 2:42 p.m., Dirk Eddelbuettel wrote: > | > I may need a hgand with riscv64. > | > | That's n

Processed: Re: Bug#1073040: dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split'

2024-06-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #1073040 [dput] dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split' Added tag(s) pending. -- 1073040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073040 Debian Bug Tracking Syste

  1   2   3   >