Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 1064126 - pending Bug #1064126 [libnss-libvirt,libvirt-daemon-system] libvirt: install NSS modules and systemd units into /usr Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064126:

Bug#1075489: sc: ftbfs with GCC-14

hi all, I fix this bug. Please review the debdiff. I plan to NMU this package. I will wait for 10 days for any comments before upload. And will upload to DELAY/10 queue. Yours, Paul diff -Nru sc-7.16/debian/changelog sc-7.16/debian/changelog --- sc-7.16/debian/changelog2024-04-07 09:47:51.

Bug#1078472: libgenomicsdb1: missing Breaks+Replaces: libgenomicsdb0 (<< 1.5.3)

Package: libgenomicsdb1 Version: 1.5.3-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to ove

Processed: request is for bookworm only

Processing commands for cont...@bugs.debian.org: > tags 1054412 bookworm Bug #1054412 [libc6.1-dev-alpha-cross] cross-toolchain-base-ports: Stable update request to include latest glibc Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 105441

Processed: Re: Processed (with 1 error): Re: Bug#1077340: libcbor fails to build on mips64el: testsuite failures

Processing commands for cont...@bugs.debian.org: > # duh > block 1070818 by 1069959 Bug #1070818 {Done: Paul Gevers } [src:libcbor] src:libcbor: fails to migrate to testing for too long: FTBFS on mips64el 1070818 was blocked by: 1077340 1070818 was not blocking any bugs. Added blocking bug(s) of

Processed (with 1 error): Re: Processed (with 1 error): Re: Bug#1077340: libcbor fails to build on mips64el: testsuite failures

Processing commands for cont...@bugs.debian.org: > block 1070818 by 1077340 Bug #1070818 {Done: Paul Gevers } [src:libcbor] src:libcbor: fails to migrate to testing for too long: FTBFS on mips64el 1070818 was blocked by: 1077340 1070818 was not blocking any bugs. Ignoring request to alter blockin

Bug#1023748: marked as done (ca-certificates-java: postinst script fails with OpenJDK 20: Error loading java.security file )

Your message dated Sun, 11 Aug 2024 07:39:29 +0200 with message-id <02a94804-56fe-450d-93d4-d478002d3...@debian.org> and subject line Re: ca-certificates-java: postinst script fails with OpenJDK 20: Error loading java.security file has caused the Debian Bug report #1023748, regarding ca-certificat

Bug#1077340: libcbor fails to build on mips64el: testsuite failures

Control: severity 1069959 serious Control: tags 1077340 patch Control: notfound 1077340 0.10.2-1.1 Control: found 1077340 0.10.2-1.1 Control: merge 1077340 1069959 Hi, On 11-08-2024 02:22, Adrian Bunk wrote: As already noted in bug 1070818, libcbor fails to build on mips64el. Let's have a prope

Processed (with 1 error): Re: Bug#1077340: libcbor fails to build on mips64el: testsuite failures

Processing control commands: > severity 1069959 serious Bug #1069959 [src:libcbor] libcbor FTBFS on hppa and mips to due different NaN encoding Severity set to 'serious' from 'normal' > tags 1077340 patch Bug #1077340 [src:libcbor] libcbor fails to build on mips64el: testsuite failures Added tag

Bug#1078470: FTBFS with OCaml 5.2.0 on armel: missing -latomic

Source: libguestfs Version: 1:1.52.2-2 Severity: serious Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-5.2.0-transition Dear Maintainer, Your package FTBFS with OCaml 5.2.0 on armel: https://buildd.debian.org/status/package.php?p=libguestfs This is due to -latomic mis

Bug#1078466: marked as done (openjdk-24 FTBFS on zero architectures)

Your message dated Sun, 11 Aug 2024 05:20:19 +0200 with message-id and subject line fixed in -2 has caused the Debian Bug report #1078466, regarding openjdk-24 FTBFS on zero architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Processed: Re: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

Processing control commands: > tags -1 patch Bug #1078208 [fail2ban] fail2ban: sshd.conf filter does not work with OpenSSH 9.8 Added tag(s) patch. -- 1078208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

Control: tags -1 patch I've attached a patch fixing both issues. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) --- fail2ban-1.1.0-a/config/filter.d/

Bug#1078467: opencpn builds with -march=native

Source: opencpn Version: 1:5.10.0+dfsg-1 Severity: serious Tags: ftbfs -march=native is a baseline violation on architectures where it is supported, and causes a FTBFS on architectures where it is not supported. It also changes the set of machines where the package might run based on the capabili

Bug#1078466: openjdk-24 FTBFS on zero architectures

Source: openjdk-24 Version: 24~10ea-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=openjdk-24&ver=24~10ea-1 ... dpkg-gencontrol: error: parsing package 'openjdk-24-jre-headless' Provides field: java-runtime-headless (= 24), java2-runtime-headless, java5-runtime-he

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

On 2024-08-11 02:53:27 +0200, Vincent Lefevre wrote: > On 2024-08-08 11:25:07 +0200, Vincent Lefevre wrote: > > As seen at https://github.com/fail2ban/fail2ban/pull/3782/files > > the change is quite simple: change > > > > _daemon = sshd > > > > to > > > > _daemon = sshd(?:-session)? > > Unfort

Bug#1078208: fail2ban: sshd.conf filter does not works with OpenSSH 9.8

On 2024-08-08 11:25:07 +0200, Vincent Lefevre wrote: > As seen at https://github.com/fail2ban/fail2ban/pull/3782/files > the change is quite simple: change > > _daemon = sshd > > to > > _daemon = sshd(?:-session)? Unfortunately this change alone does not solve the issue. I'm wondering whether

Bug#1075133: marked as done (levee: ftbfs with GCC-14)

Your message dated Sun, 11 Aug 2024 00:34:01 + with message-id and subject line Bug#1075133: fixed in levee 4.0-2 has caused the Debian Bug report #1075133, regarding levee: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1077340: libcbor fails to build on mips64el: testsuite failures

On Sun, Jul 28, 2024 at 05:59:05PM +0200, Paul Gevers wrote: > Source: libcbor > Version: 0.10.2-1.1 > Severity: serious > Tags: ftbfs > Justification: FTBFS > X-Debbugs-Cc: davidp...@librem.one > Control: block 1070818 by -1 > > Hi, Hi Paul, > As already noted in bug 1070818, libcbor fails to b

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 1078068 patch Bug #1078068 [accerciser] accerciser: Broken with Python 3.12: ModuleNotFoundError: No module named 'imp' Added tag(s) patch. > severity 1077629 serious Bug #1077629 [safeeyes] safeeyes: safeeyes crashes immediately Severity se

Bug#1078068: accerciser: Broken with Python 3.12: ModuleNotFoundError: No module named 'imp'

The attached patch should fix the issue. -- Regards Sudip diff -Nru accerciser-3.42.0/debian/changelog accerciser-3.42.0/debian/changelog --- accerciser-3.42.0/debian/changelog 2023-10-08 11:27:48.0 +0100 +++ accerciser-3.42.0/debian/changelog 2024-08-11 00:20:38.0 +0100 @@ -1,3

Bug#1078454: marked as done (golang-github-container-orchestrated-devices-container-device-interface-dev,golang-tags.cncf-container-device-interface-dev: both ship /usr/share/gocode/src/tags.cncf.io/c

Your message dated Sat, 10 Aug 2024 23:05:44 + with message-id and subject line Bug#1078454: fixed in golang-github-container-orchestrated-devices-container-device-interface 0.8.0-2 has caused the Debian Bug report #1078454, regarding golang-github-container-orchestrated-devices-container-de

Bug#1078433: marked as done (python-jupyter-server-doc: missing Breaks+Replaces: python3-jupyter-server (<< 2))

Your message dated Sat, 10 Aug 2024 22:26:19 + with message-id and subject line Bug#1078433: fixed in jupyter-server 2.14.2-3 has caused the Debian Bug report #1078433, regarding python-jupyter-server-doc: missing Breaks+Replaces: python3-jupyter-server (<< 2) to be marked as done. This mean

Bug#1078413: pdns: FTBFS: make[6]: *** [Makefile:3871: test-suite.log] Error 1

The interesting part of that build log (the bit that fits the test failure) is "configure: OpenSSL ecdsa: no". (I'm off work for another week, I'm happy to debug after that)

Processed: Bug#1078433 marked as pending in jupyter-server

Processing control commands: > tag -1 pending Bug #1078433 [python-jupyter-server-doc] python-jupyter-server-doc: missing Breaks+Replaces: python3-jupyter-server (<< 2) Added tag(s) pending. -- 1078433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078433 Debian Bug Tracking System Contact

Processed: Bug#1078454 marked as pending in golang-github-container-orchestrated-devices-container-device-interface

Processing control commands: > tag -1 pending Bug #1078454 [golang-github-container-orchestrated-devices-container-device-interface-dev,golang-tags.cncf-container-device-interface-dev] golang-github-container-orchestrated-devices-container-device-interface-dev,golang-tags.cncf-container-device-

Bug#1078433: marked as pending in jupyter-server

Control: tag -1 pending Hello, Bug #1078433 in jupyter-server 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/jupyter-server/-/commit/880ce

Bug#1078454: marked as pending in golang-github-container-orchestrated-devices-container-device-interface

Control: tag -1 pending Hello, Bug #1078454 in golang-github-container-orchestrated-devices-container-device-interface 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.de

Bug#1077202: renpy: exception while trying to start renpy

Here's a new patch that should resolve the actual root of the problem[1]. Thanks to PyTom for the hint about the loader. [1] https://docs.python.org/3/library/sys.html#sys.meta_pathcommit 2901314d05cf0ec29e35b3f8d7199927eaf8001e Author: Gregor Riepl Date: Fri Aug 9 00:36:08 2024 +0200 Fi

Bug#1078462: nvidia-kernel-dkms: fails to compile with linux-image-6.10.3-amd64 (6.10.3-1)

Package: nvidia-kernel-dkms Version: 535.183.01-1 Severity: serious The nvidia kernel module fails to compile with linux-image-6.10.3-amd64 (6.10.3-1). Attached is a complete log (/var/lib/dkms/nvidia-current/535.183.01/build/make.log); the error is on lines 1474 onwards: /var/lib/dkms/nvidia-cu

Processed: lower severity for #1078430 (rust-just: flaky autopkgtest on s390x: *nearly* always fails)

Processing commands for cont...@bugs.debian.org: > severity 1078430 important Bug #1078430 [src:rust-just] rust-just: flaky autopkgtest on s390x: *nearly* always fails Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1078

Processed: libapache2-mod-watchcat: depends on to be removed watchcatd

Processing control commands: > block 1074225 by -1 Bug #1074225 [ftp.debian.org] RM: watchcatd -- RoQA; dead upstream, obsolete 1074225 was not blocked by any bugs. 1074225 was not blocking any bugs. Added blocking bug(s) of 1074225: 1078461 -- 1074225: https://bugs.debian.org/cgi-bin/bugreport.

Bug#1078461: libapache2-mod-watchcat: depends on to be removed watchcatd

Source: libapache2-mod-watchcat Severity: serious Tags: sid trixie Control: block 1074225 by -1 watchcatd is supposed to be removed, see #1074225. If libapache2-mod-watchcat is useful without it, please remove the (build-)depends; otherwise please consider removing libapache2-mod-watchcat too.

Processed: Re: Bug#1067200: RM: cython-legacy -- ROM; Legacy transition package no longer needed

Processing control commands: > clone -1 -2 Bug #1067200 [ftp.debian.org] RM: cython-legacy -- ROM; Legacy transition package no longer needed Bug 1067200 cloned as bug 1078460 1078460 was blocked by: 1076515 1078460 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #107846

Bug#1074828: atril: ftbfs with GCC-14

Control: tags 1074828 + patch I don't know if there's a fix upstream, but the attached patch seems to fix this build problem. /Andreas Rönnquist gus...@debian.org From: =?utf-8?q?Andreas_R=C3=B6nnquist?= Date: Sat, 10 Aug 2024 21:16:25 +0200 Subject: Cast mimetypes to gchar** to fix building on

Processed: atril: ftbfs with GCC-14

Processing control commands: > tags 1074828 + patch Bug #1074828 [src:atril] atril: ftbfs with GCC-14 Added tag(s) patch. -- 1074828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1078430: rust-just: flaky autopkgtest on s390x: *nearly* always fails

On 11/08/2024 01:17, Blair Noctis wrote: > On 10/08/2024 18:04, Paul Gevers wrote: (...) >> https://ci.debian.net/packages/r/rust-just/testing/s390x/50327770/ >> >> 149s failures: >> 149s >> 149s choose::status_error stdout >> 149s thread 'choose::status_error' panicked at tests/choose.rs

Bug#1078430: rust-just: flaky autopkgtest on s390x: *nearly* always fails

Hi, On 10-08-2024 19:17, Blair Noctis wrote: On the infra side, I'm pondering the idea of a "debug" patch that captures more information the next time it goes south. However, "fixing" (or rather frankly, ignoring) the test failures makes following runs pass. Is there a way to monitor such an out

Processed: fixed 1078011 in 2.0.0-8, found 1067271 in 1.3.7-1~exp, found 1066704 in 4.2.0-1~exp1

Processing commands for cont...@bugs.debian.org: > fixed 1078011 2.0.0-8 Bug #1078011 {Done: Alastair McKinstry } [libgctp-dev] libgctp-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libgctp-2.0.0.so Marked as fixed in versions libgctp/2.0.0-8. > found 1067271 1.3.7-1~exp Bug #

Bug#1075452: marked as done (rplay: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 18:38:31 + with message-id and subject line Bug#1075452: fixed in rplay 3.3.2-19 has caused the Debian Bug report #1075452, regarding rplay: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1078454: golang-github-container-orchestrated-devices-container-device-interface-dev,golang-tags.cncf-container-device-interface-dev: both ship /usr/share/gocode/src/tags.cncf.io/container-device-

Package: golang-github-container-orchestrated-devices-container-device-interface-dev,golang-tags.cncf-container-device-interface-dev Version: 0.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your packages failed

Bug#1078390: marked as done (keyrings.alt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13)

Your message dated Sat, 10 Aug 2024 18:20:57 + with message-id and subject line Bug#1078390: fixed in keyrings.alt 5.0.1-2 has caused the Debian Bug report #1078390, regarding keyrings.alt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code

Bug#1075004: marked as done (gkrellm-radio: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 18:19:47 + with message-id and subject line Bug#1075004: fixed in gkrellm-radio 2.0.4-4 has caused the Debian Bug report #1075004, regarding gkrellm-radio: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1078390: marked as pending in keyrings.alt

Control: tag -1 pending Hello, Bug #1078390 in keyrings.alt 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/keyrings.alt/-/commit/eb4028dcb

Processed: Bug#1078390 marked as pending in keyrings.alt

Processing control commands: > tag -1 pending Bug #1078390 [src:keyrings.alt] keyrings.alt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13 Added tag(s) pending. -- 1078390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078390 Debia

Bug#1078422: marked as done (avifile: FTBFS on i386: afl.c:226:24: error: assignment to 'DRIVERPROC' {aka 'long int (__attribute__((stdcall)) *)(long unsigned int, unsigned int, unsigned int, long

Your message dated Sat, 10 Aug 2024 17:36:38 + with message-id and subject line Bug#1078422: fixed in avifile 1:0.7.48~20090503.ds-29 has caused the Debian Bug report #1078422, regarding avifile: FTBFS on i386: afl.c:226:24: error: assignment to 'DRIVERPROC' {aka 'long int (__attribute__((std

Bug#1077969: marked as done (roundcube: CVE-2024-42008, CVE-2024-42009, CVE-2024-42010: XSS and information leak vulnerabilities)

Your message dated Sat, 10 Aug 2024 17:33:19 + with message-id and subject line Bug#1077969: fixed in roundcube 1.6.5+dfsg-1+deb12u3 has caused the Debian Bug report #1077969, regarding roundcube: CVE-2024-42008, CVE-2024-42009, CVE-2024-42010: XSS and information leak vulnerabilities to be m

Bug#1073879: marked as done (FTBFS with OCaml 5.2.0 (Missing dependency on libfindlib-ocaml for bigarray))

Your message dated Sat, 10 Aug 2024 19:21:43 +0200 with message-id <15b7e449-0d42-45de-b23a-ebbaf9490...@debian.org> and subject line Re: FTBFS with OCaml 5.2.0 (Missing dependency on libfindlib-ocaml for bigarray) has caused the Debian Bug report #1073879, regarding FTBFS with OCaml 5.2.0 (Missin

Bug#1078430: rust-just: flaky autopkgtest on s390x: *nearly* always fails

On 10/08/2024 18:04, Paul Gevers wrote: > Source: rust-just > Version: 1.33.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > I looked at the results of the autopkgtest of your package because it was > blocking the migration of gcc-14. I noti

Bug#1077835: marked as done (zfs-dkms: module fails to build for Linux 6.10)

Your message dated Sat, 10 Aug 2024 16:54:37 + with message-id and subject line Bug#1077835: fixed in zfs-linux 2.2.5-1 has caused the Debian Bug report #1077835, regarding zfs-dkms: module fails to build for Linux 6.10 to be marked as done. This means that you claim that the problem has been

Bug#1075141: marked as done (libapache2-mod-encoding: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 16:49:36 + with message-id and subject line Bug#1075141: fixed in libapache2-mod-encoding 20040616-9 has caused the Debian Bug report #1075141, regarding libapache2-mod-encoding: ftbfs with GCC-14 to be marked as done. This means that you claim that the pro

Bug#1064126: [Pkg-libvirt-maintainers] Bug#1064126: libvirt: install NSS modules into /usr

On Sat, Aug 10, 2024 at 06:19:31PM +0200, Andrea Bolognani wrote: > So, here's my proposal: in two weeks' time, i.e. by September 25, I > will upload a version of libvirt that includes both the restructuring > and the usr-merge bits to experimental. I obviously meant *August* 25 here O:-) -- And

Bug#1075009: interest in fixing gLabels FTBFS very soon, possibly with NMU if necessary

Dear maintainer, As you know, the upstream gLabels maintainer shifted attention to a Qt rewrite several years ago that may not be a drop-in replacement, but that hasn't had any release yet either due to the author's dwindling ability to work on it. On the other hand, it's very feature-complete

Bug#1064126: [Pkg-libvirt-maintainers] Bug#1064126: libvirt: install NSS modules into /usr

On Sat, Aug 10, 2024 at 05:41:25PM +0200, Guido Günther wrote: > On Sat, Aug 10, 2024 at 03:30:23PM +0200, Andrea Bolognani wrote: > > Note that I have also uploaded 10.6.0-1 in the meantime, which is set > > to migrate to testing tomorrow. I wonder how the two uploads will > > interact with each o

Bug#1064126: [Pkg-libvirt-maintainers] Bug#1064126: libvirt: install NSS modules into /usr

Hi, On Sat, Aug 10, 2024 at 03:30:23PM +0200, Andrea Bolognani wrote: > On Tue, Aug 06, 2024 at 10:46:36PM +0200, Michael Biebl wrote: > [..snip..] > Anyway, you've uploaded the changes now, so it's a done deal I guess. > I'll just figure out how to deal with any potential fallout. Maybe > it wil

Processed: bump severity of openjdk 21 FTBFS bugs

Processing commands for cont...@bugs.debian.org: > severity 1052570 serious Bug #1052570 [src:jlapack] jlapack: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 Severity set to 'serious' from 'important' > severity 1052574 serious Bug #1052574 [src:geotranz] geotranz: FTBFS wi

Bug#1078363: marked as done (systemfixtures: FTBFS: ModuleNotFoundError: No module named 'six')

Your message dated Sat, 10 Aug 2024 15:36:25 + with message-id and subject line Bug#1078363: fixed in systemfixtures 0.6.7-2 has caused the Debian Bug report #1078363, regarding systemfixtures: FTBFS: ModuleNotFoundError: No module named 'six' to be marked as done. This means that you claim t

Processed: Bug#1078360 marked as pending in ruby-moneta

Processing control commands: > tag -1 pending Bug #1078360 {Done: Jérôme Charaoui } [src:ruby-moneta] ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load such file -- sqlite3 Added tag(s) pending. -- 1078360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078360 Debian B

Bug#1078360: marked as pending in ruby-moneta

Control: tag -1 pending Hello, Bug #1078360 in ruby-moneta 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/ruby-moneta/-/commit/2b1bc05ac08a178fc2c3cb

Bug#1073643: marked as done (nilfs-tools: move aliased files from / to /usr (DEP17))

Your message dated Sat, 10 Aug 2024 15:35:59 + with message-id and subject line Bug#1073643: fixed in nilfs-tools 2.2.11-2 has caused the Debian Bug report #1073643, regarding nilfs-tools: move aliased files from / to /usr (DEP17) to be marked as done. This means that you claim that the probl

Bug#1075493: marked as done (schroot: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 15:26:45 + with message-id and subject line Bug#1075493: fixed in schroot 1.6.13-4 has caused the Debian Bug report #1075493, regarding schroot: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Bug#1073643 marked as pending in nilfs-tools

Processing control commands: > tag -1 pending Bug #1073643 [nilfs-tools] nilfs-tools: move aliased files from / to /usr (DEP17) Added tag(s) pending. -- 1073643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1073643: marked as pending in nilfs-tools

Control: tag -1 pending Hello, Bug #1073643 in nilfs-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/debian/nilfs-tools/-/commit/b2ae6882518c39cd0ded64c5c

Bug#1075305: nat: ftbfs with GCC-14

Hi all, I plan to fix this bug by NMU. The attachment is the debdiff. I'll wait for 10 days if no one stops me. And I'll upload to DELAY/10 queue. Yours, Paul diff -Nru nat-1.0/debian/changelog nat-1.0/debian/changelog --- nat-1.0/debian/changelog2022-04-26 22:48:16.0 +0800 +++ nat-

Bug#1078373: marked as done (ruby-concurrent: FTBFS: make[1]: *** [debian/rules:18: execute_after_dh_auto_build-indep] Error 123)

Your message dated Sat, 10 Aug 2024 14:58:27 + with message-id and subject line Bug#1078373: fixed in ruby-concurrent 1.2.3-3 has caused the Debian Bug report #1078373, regarding ruby-concurrent: FTBFS: make[1]: *** [debian/rules:18: execute_after_dh_auto_build-indep] Error 123 to be marked a

Bug#1078431: marked as done (ruby-concurrent: flaky autopkgtest on arm64: Attempt to unlock a mutex which is locked by another thread/fiber)

Your message dated Sat, 10 Aug 2024 14:58:27 + with message-id and subject line Bug#1078431: fixed in ruby-concurrent 1.2.3-3 has caused the Debian Bug report #1078431, regarding ruby-concurrent: flaky autopkgtest on arm64: Attempt to unlock a mutex which is locked by another thread/fiber to

Bug#1078446: ceph: FTBFS on mips64el:

Source: ceph Version: 18.2.4+ds-4 Tags: ftbfs Severity: serious ceph currently FTBFS on mips64el but has built there before. buildd log: https://buildd.debian.org/status/fetch.php?pkg=ceph&arch=mips64el&ver=18.2.4%2Bds-4&stamp=1723159346&raw=0 Relevant lines, hopefully: -- Found Java: /usr/lib/

Processed: tagging 1078309

Processing commands for cont...@bugs.debian.org: > tags 1078309 + wontfix Bug #1078309 [src:python-m2r] python-m2r: FTBFS: AttributeError: module 'docutils.nodes' has no attribute 'reprunicode' Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1078283: marked as done (hugo: FTBFS: src/github.com/gohugoio/hugo/identity/identityhash.go:47:37: not enough arguments in call to hashstructure.Hash)

Your message dated Sat, 10 Aug 2024 14:41:48 + with message-id and subject line Bug#1078283: fixed in hugo 0.129.0-1 has caused the Debian Bug report #1078283, regarding hugo: FTBFS: src/github.com/gohugoio/hugo/identity/identityhash.go:47:37: not enough arguments in call to hashstructure.Ha

Bug#1077038: marked as done (ipwatchd: introduces aliased file /lib/systemd/system/ipwatchd.service (DEP17))

Your message dated Sat, 10 Aug 2024 14:41:55 + with message-id and subject line Bug#1077038: fixed in ipwatchd 1.3.0-1+nmu2 has caused the Debian Bug report #1077038, regarding ipwatchd: introduces aliased file /lib/systemd/system/ipwatchd.service (DEP17) to be marked as done. This means tha

Processed: Bug#1078283 marked as pending in hugo

Processing control commands: > tag -1 pending Bug #1078283 [src:hugo] hugo: FTBFS: src/github.com/gohugoio/hugo/identity/identityhash.go:47:37: not enough arguments in call to hashstructure.Hash Added tag(s) pending. -- 1078283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078283 Debian

Bug#1078283: marked as pending in hugo

Control: tag -1 pending Hello, Bug #1078283 in hugo 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/hugo/-/commit/66906ac680bb15a54b0537299787a

Bug#1077854: marked as done (libcurl4t64: SIGPIPE leaks in some cases)

Your message dated Sat, 10 Aug 2024 13:34:38 + with message-id and subject line Bug#1077854: fixed in curl 8.9.1-2 has caused the Debian Bug report #1077854, regarding libcurl4t64: SIGPIPE leaks in some cases to be marked as done. This means that you claim that the problem has been dealt with

Bug#1077650: marked as done (Binary build patching insanity)

Your message dated Sat, 10 Aug 2024 13:34:38 + with message-id and subject line Bug#1077650: fixed in curl 8.9.1-2 has caused the Debian Bug report #1077650, regarding Binary build patching insanity to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1064126: libvirt: install NSS modules into /usr

On Tue, Aug 06, 2024 at 10:46:36PM +0200, Michael Biebl wrote: > Hi Andrea > > I just uploaded the attached debdiff to DELAYED/7. > > As discussed in this bug report, the changes for usrmerge *must* happen for > trixie and are not optional. So it is better to get those out of the way. > Your plan

Bug#1073705: marked as done (ifupdown-extra: move aliased files from / to /usr (DEP17))

Your message dated Sat, 10 Aug 2024 13:04:28 + with message-id and subject line Bug#1073705: fixed in ifupdown-extra 0.33+nmu3 has caused the Debian Bug report #1073705, regarding ifupdown-extra: move aliased files from / to /usr (DEP17) to be marked as done. This means that you claim that th

Processed: Re: Bug#1075586: trickle: ftbfs with GCC-14

Processing control commands: > tag 1075586 patch Bug #1075586 [src:trickle] trickle: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075586 to the same tags previously set > forwarded 1075586 > https://github.com/mariusae/trickle/issues/34#issuecomment-2134139388 Bug #1075586 [src:trick

Processed: Re: Bug#1075586: trickle: ftbfs with GCC-14

Processing control commands: > tag 1075586 patch Bug #1075586 [src:trickle] trickle: ftbfs with GCC-14 Added tag(s) patch. > forwarded 1075586 > https://github.com/mariusae/trickle/issues/34#issuecomment-2134139388 Bug #1075586 [src:trickle] trickle: ftbfs with GCC-14 Set Bug forwarded-to-address

Bug#1075586: trickle: ftbfs with GCC-14

Control: tag 1075586 patch Control: forwarded 1075586 https://github.com/mariusae/trickle/issues/34#issuecomment-2134139388 On Wed, Jul 03, 2024 at 12:46:27PM +, Matthias Klose wrote: > [...] > xdr.c: In function ‘xdr_msg’: > xdr.c:106:32: error: passing argument 5 of ‘xdr_union’ from incompa

Bug#1075002: marked as done (gkrellm-mailwatch: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 12:49:09 + with message-id and subject line Bug#1075002: fixed in gkrellm-mailwatch 2.4.3-3 has caused the Debian Bug report #1075002, regarding gkrellm-mailwatch: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been d

Bug#1075292: 1075292 fixed ?

Just to note, my local machine is arm64, not amd64, which might be relevant. Alastair On 10/08/2024 12:45, Alastair McKinstry wrote: Hi, I'm looking at #1075292 and I cannot reproduce it. The fix is for 4.2.0-6 and we now have 4.2.0-9 in unstable - can you check if you still see the FTBFS

Bug#1075292: 1075292 fixed ?

Hi, I'm looking at #1075292 and I cannot reproduce it. The fix is for 4.2.0-6 and we now have 4.2.0-9 in unstable - can you check if you still see the FTBFS in an unstable environment, or perhaps its Ubuntu related? Best regards Alastair McKinstry mckins...@debian.org

Processed: Re: vimix: ftbfs with GCC-14

Processing control commands: > found -1 0.8.0+git20230331+ds-1 Bug #1075621 [src:vimix] vimix: ftbfs with GCC-14 Marked as found in versions vimix/0.8.0+git20230331+ds-1. -- 1075621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075621 Debian Bug Tracking System Contact ow...@bugs.debian.or

Bug#1075621: vimix: ftbfs with GCC-14

Followup-For: Bug #1075621 Control: found -1 0.8.0+git20230331+ds-1 The actual error in sid is /<>/src/SessionCreator.cpp: In member function ‘void SessionLoader::load(tinyxml2::XMLElement*)’: /<>/src/SessionCreator.cpp:516:39: error: no matching function for call to ‘find(std::__cxx11::l

Bug#1078438: inotifyrecursive: build-depends on no longer available python3-distutils

Package: inotifyrecursive Version: 0.3.5-1~exp1 Severity: serious Tags: ftbfs Justification: fails to build from source inotifyrecursive connot be built any longer since python3-distutils has been removed. Andreas

Bug#1078437: tinc: FTBFS with current miniupnpc: error: too few arguments to function 'UPNP_GetValidIGD'

Source: tinc Version: 1.1~pre18-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) tinc/experimental FTBFS with the current miniupnpc version in sid: gcc -DHAVE_CONFIG_H-Wdate-time -D_FORTIFY_SOURCE=2 -DFORTIFY_SOURCE=2 -fwrapv -fPI

Bug#1074877: marked as done (checkit-tiff: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 11:19:04 + with message-id and subject line Bug#1074877: fixed in checkit-tiff 1.4.4-2 has caused the Debian Bug report #1074877, regarding checkit-tiff: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1078436: kwin-data: missing Breaks+Replaces: kwin-addons (<< 4:6)

Package: kwin-data Version: 4:6.1.3-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails becau

Processed: golang-github-docker-docker-dev: moby/docker-image-spec/specs-go/v1 is now packaged separately

Processing control commands: > affects -1 + src:golang-github-moby-docker-image-spec Bug #1078435 [golang-github-docker-docker-dev] golang-github-docker-docker-dev: moby/docker-image-spec/specs-go/v1 is now packaged separately Added indication that 1078435 affects src:golang-github-moby-docker-im

Bug#1078435: golang-github-docker-docker-dev: moby/docker-image-spec/specs-go/v1 is now packaged separately

Package: golang-github-docker-docker-dev Version: 26.1.4+dfsg1-9 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Control: affects -1 + src:golang-github-moby-docker-image-spec Hi, during a test with piuparts I noticed your package failed to install because it tr

Bug#1078427: [Pkg-zfsonlinux-devel] Bug#1078427: zfs-linux: autopkgtest needs update for new version of linux-signed-amd64

On Sat, Aug 10, 2024 at 09:19:00AM +, 陈 晟祺 wrote: > > Is it possible to make the autopkgtest skip the > > test (restriction skipable with exit code 77) if a too new kernel is > > installed? > > I will try this in later versions. Thanks for your advice! This seems like the wrong thing to do.

Bug#1078433: python-jupyter-server-doc: missing Breaks+Replaces: python3-jupyter-server (<< 2)

Package: python-jupyter-server-doc Version: 2.14.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it

Bug#1078432: khelpcenter-data: missing Breaks+Replaces: khelpcenter (<< 4:24)

Package: khelpcenter-data Version: 4:24.05.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fa

Bug#1075552: marked as done (tcc: ftbfs with GCC-14)

Your message dated Sat, 10 Aug 2024 10:38:58 + with message-id and subject line Bug#1075552: fixed in tcc 0.9.27+git20200814.62c30a4a-2 has caused the Debian Bug report #1075552, regarding tcc: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt w

Processed: fixed 1077129 in 0.1.49

Processing commands for cont...@bugs.debian.org: > fixed 1077129 0.1.49 Bug #1077129 [src:verbiste] verbiste: needs rebuild against dh-elpa >=2.1.5 The source 'verbiste' and version '0.1.49' do not appear to match any binary packages Marked as fixed in versions verbiste/0.1.49. > thanks Stopping

Bug#1075552: tcc: ftbfs with GCC-14

Control: tags -1 + pending On Wed, Jul 03, 2024 at 12:45:22PM +, Matthias Klose wrote: > Package: src:tcc > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-14 I've uploaded a fix and pushed the changes to git. Should show up shortly.

Processed: Re: Bug#1075552: tcc: ftbfs with GCC-14

Processing control commands: > tags -1 + pending Bug #1075552 [src:tcc] tcc: ftbfs with GCC-14 Added tag(s) pending. -- 1075552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1078366: marked as done (hdf-eos5: FTBFS: ld: cannot find -lgctp: No such file or directory)

Your message dated Sat, 10 Aug 2024 10:20:31 + with message-id and subject line Bug#1078366: fixed in libgctp 2.0.0-9 has caused the Debian Bug report #1078366, regarding hdf-eos5: FTBFS: ld: cannot find -lgctp: No such file or directory to be marked as done. This means that you claim that th

Bug#1078431: ruby-concurrent: flaky autopkgtest on arm64: Attempt to unlock a mutex which is locked by another thread/fiber

Source: ruby-concurrent Version: 1.2.3-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package because it was blocking migration of gcc-14. I noticed that it regularly fails (I tested on arm64: 3/10).

Bug#1073682: marked as done (nvidia-tesla-470-kernel-support: move aliased files from / to /usr (DEP17))

Your message dated Sat, 10 Aug 2024 12:09:19 +0200 with message-id <7ccbf50e-8690-d16c-8d19-4cc34d703...@debian.org> and subject line Re: Bug#1073682: nvidia-tesla-470-kernel-support: move aliased files from / to /usr (DEP17) has caused the Debian Bug report #1073682, regarding nvidia-tesla-470-ke

  1   2   >