Processed: your mail

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1069437 libnginx-mod-http-set-misc Bug #1069437 [nginx] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Added indication that 1069437 affects libnginx-mod-http-set-misc > affects 1069437 -

Processed: your mail

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1069525 libnginx-mod-http-srcache-filter Bug #1069525 [nginx] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Added indication that 1069525 affects libnginx-mod-http-srcache-filter > affects

Processed: your mail

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1069525 nginx Bug #1069525 [src:libnginx-mod-http-srcache-filter] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Bug reassigned from package 'src:libnginx-mod-http-srcache-filter' to

Processed: your mail

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1069437 nginx Bug #1069437 [src:libnginx-mod-http-set-misc] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Bug reassigned from package 'src:libnginx-mod-http-set-misc' to 'nginx'. No longer

Bug#1070476: openjdk-21: autopkgtest on i386: /usr/bin/ld: /usr/lib/jvm/java-21-openjdk-i386/lib/server/libjvm.so: undefined reference to `_SafeFetch32_impl'

2024-05-05 Thread Sebastian Ramacher
Source: openjdk-21 Version: 21.0.3+9-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org openjdk-21 is unable to migrate since the version in unstable fails its autopkgtests on i386. https://ci.debian.net/packages/o/openjdk-21/testing/i386/46308616/#S21 9507s autopkgtest [09:27:46]: test

Processed: your mail

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1069482 nginx Bug #1069482 [src:libnginx-mod-http-lua] libnginx-mod-http-lua: FTBFS on armhf: module "/usr/share/nginx/modules/ndk_http_module.so" is not binary compatible Bug reassigned from package 'src:libnginx-mod-http-lua' to

Bug#1070421: marked as done (src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 06 May 2024 04:19:21 + with message-id and subject line Bug#1070421: fixed in mac-widgets 0.10.0+svn416-dfsg1-4 has caused the Debian Bug report #1070421, regarding src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc to be marked as

Processed: Bug#1070421 marked as pending in mac-widgets

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1070421 [src:mac-widgets] src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc Added tag(s) pending. -- 1070421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070421 Debian Bug Tracking System Contact

Bug#1070421: marked as pending in mac-widgets

2024-05-05 Thread Tony Mancill
Control: tag -1 pending Hello, Bug #1070421 in mac-widgets 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:

Bug#1070472: Uses the obsolete /sbin/route without a dependency

2024-05-05 Thread Marco d'Itri
Package: miniupnpd Version: 2.3.1-1 Severity: serious Tags: patch Pseudo-patch for miniupnpd.config: - MiniUPnPd_EXTERNAL_INTERFACE=$(LC_ALL=C /sbin/route | grep -m 1 default | awk -- '{ print $8 }') + MiniUPnPd_EXTERNAL_INTERFACE=$(LC_ALL=C ip -o route show | sed -nre '/^default

Bug#1070300: pmix_psquash_base_select failed during MPI_INIT on 32bit architectures

2024-05-05 Thread Samuel Thibault
Samuel Thibault, le sam. 04 mai 2024 11:49:40 +0200, a ecrit: > Samuel Thibault, le ven. 03 mai 2024 19:00:22 +0200, a ecrit: > > This has been posing migration issues for quite some time, I have > > uploaded the attached fix to delayed/0. > > Some of the components depend on

Bug#1069432: mpi4py: FTBFS on armhf: ld: cannot find -llmpe: No such file or directory

2024-05-05 Thread Drew Parsons
Source: mpi4py Followup-For: Bug #1069432 There have been ongoing issues with OpenMPI on 32-bit architectures, partly related to drop of 32-bit support by pmix. This bug is likely related to that i.e. not a bug in mpi4py itself.

Bug#1065725: marked as done (adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 22:34:10 + with message-id and subject line Bug#1065725: fixed in adns 1.6.1-1 has caused the Debian Bug report #1065725, regarding adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0 to be marked as done.

Bug#1065725: adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0

2024-05-05 Thread Ian Jackson
Dan Bungert writes ("Bug#1065725: adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0"): > I took a look at this bug today. > I found that the regress testsuite make use of some negative offsets, which > seem to perplex the reader on 32 bit

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

2024-05-05 Thread Jussi Pakkanen
On Sun, 5 May 2024 at 04:33, Shmerl wrote: > May be for rustc? It's worth filing the bug if it's not clear what the > root cause is. If it's not really rustc, developers will point that out. Filed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070470

Processed: closing 1070458

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # fallout from the fix of #22 in xneur > close 1070458 Bug #1070458 [src:gxneur] gxneur: FTBFS: Package 'libpcre', required by 'xnconfig', not found Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#1066278: marked as done (xnee: FTBFS: xnee_fake.c:809:15: error: implicit declaration of function ‘xnee_check_key’; did you mean ‘xnee_check_true’? [-Werror=implicit-function-declaration])

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 21:43:42 + with message-id and subject line Bug#1066278: fixed in xnee 3.19-9.2 has caused the Debian Bug report #1066278, regarding xnee: FTBFS: xnee_fake.c:809:15: error: implicit declaration of function ‘xnee_check_key’; did you mean ‘xnee_check_true’?

Processed: Re: transition: jpeg-xl

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1061627 Bug #1053866 [release.debian.org] transition: jpeg-xl 1053866 was not blocked by any bugs. 1053866 was not blocking any bugs. Added blocking bug(s) of 1053866: 1061627 -- 1053866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053866 Debian

Bug#1070446: rocm-hipamd: arm64 FTBFS with glibc 2.38

2024-05-05 Thread Cordell Bloor
Tags: patch Hi Graham, On 2024-05-05 07:31, Graham Inggs wrote: As can be seen in reproducible builds [1], rocm-hipamd FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider

Bug#1070387: marked as done (gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 20:42:20 + with message-id and subject line Bug#1070387: fixed in gdcm 3.0.24-1 has caused the Debian Bug report #1070387, regarding gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 to be marked as done. This means that you claim that the problem has

Processed: Re: [Debian-med-packaging] Bug#1070387: gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > found -1 3.0.21-1 Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 Marked as found in versions gdcm/3.0.21-1. > found -1 3.0.8-2 Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 Marked as found in versions

Bug#1070387: [Debian-med-packaging] Bug#1070387: gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391

2024-05-05 Thread Étienne Mollier
Control: found -1 3.0.21-1 Control: found -1 3.0.8-2 Control: fixed -1 3.0.24-1 Hi Moritz, Thanks for the tracking and the triaging of these issues! Moritz Mühlenhoff, on 2024-05-04: > Please adjust the affected versions in the BTS as needed. Done with the present email; an upload of 3.0.24-1

Bug#1070455: ayatana-indicator-display: FTBFS: Errors while running CTest

2024-05-05 Thread Mike Gabriel
Control: forwarded -1 https://github.com/AyatanaIndicators/ayatana-indicator-display/pull/96 Hi Santiago, On So 05 Mai 2024 18:50:27 CEST, Santiago Vila wrote: Package: src:ayatana-indicator-display Version: 24.1.1-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all

Bug#1070457: dino-im: FTBFS: error: ‘struct _gpgme_key’ has no member named ‘subkeys_length1’

2024-05-05 Thread Stefan Kropp
I found this bug at upstream project: Dino 0.4.3 fails to compile after Vala-c update to 0.56.17 https://github.com/dino/dino/issues/1576 -- Stefan

Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:13 + with message-id and subject line Bug#1068938: fixed in less 551-2+deb11u2 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths to be marked as done. This means that you claim that the

Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:09 + with message-id and subject line Bug#1068938: fixed in less 551-2+deb11u1 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths to be marked as done. This means that you claim that the

Bug#1068412: marked as done (apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:17:41 + with message-id and subject line Bug#1068412: fixed in apache2 2.4.59-1~deb11u1 has caused the Debian Bug report #1068412, regarding apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709 to be marked as done. This means that you claim that the

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:13 + with message-id and subject line Bug#1064293: fixed in less 551-2+deb11u2 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1064989: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:20 + with message-id and subject line Bug#1064989: fixed in nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 has caused the Debian Bug report #1064989, regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:09 + with message-id and subject line Bug#1064293: fixed in less 551-2+deb11u1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1063706: marked as done (linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't build in 6.1.0-18 kernel)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:20 + with message-id and subject line Bug#1063361: fixed in nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 has caused the Debian Bug report #1063361, regarding linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't build in 6.1.0-18 kernel to

Bug#1063361: marked as done (nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:20 + with message-id and subject line Bug#1063361: fixed in nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 has caused the Debian Bug report #1063361, regarding nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of

Processed: severity of 1064991 is serious

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1064991 serious Bug #1064991 {Done: Andreas Beckmann } [src:nvidia-open-gpu-kernel-modules] nvidia-open-gpu-kernel-modules: CVE-2024-0074, CVE-2024-0075, CVE-2024-0078 Severity set to 'serious' from 'important' > thanks Stopping

Bug#1068755: docker.io: FTBFS: failing tests

2024-05-05 Thread Reinhard Tartler
Turns out that backporting https://github.com/moby/moby/commit/97921915a801dd82b1f5a70e0a69353539c1e3ae.patch seems to actually make the test pass I'm not sure why that worked before, but I've pushed a backport of that patch to

Bug#1068755: marked as pending in docker.io

2024-05-05 Thread Reinhard Tartler
Control: tag -1 pending Hello, Bug #1068755 in docker.io 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:

Processed: Bug#1068755 marked as pending in docker.io

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068755 [src:docker.io] docker.io: FTBFS: failing tests Added tag(s) pending. -- 1068755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1064003: patch for c-t-b build

2024-05-05 Thread Helmut Grohne
Control: tags -1 + patch Hi Matthias, I'm attaching a patch for the c-t-b FTBFS. Note that due to the glibc/2.38 upload c-t-b has become completely uninstallable. Hence, a timely upload is appreciated. Due to linux-libc-dev currently providing the -$arch-cross packages, we have to remove the

Processed: patch for c-t-b build

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1067370 [src:cross-toolchain-base] cross-toolchain-base: FTBFS: unsatisfiable build-dependencies Added tag(s) patch. -- 1067370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067370 Debian Bug Tracking System Contact

Processed: patch for c-t-b build

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1064003 [src:cross-toolchain-base] src:cross-toolchain-base: unsatisfied build dependency in testing: linux-source-6.5 (>= 6.5.8) Added tag(s) patch. -- 1064003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064003 Debian Bug Tracking

Bug#1067016: nvidia-settings 470.239.06-1 flagged for acceptance

2024-05-05 Thread Adam D Barratt
package release.debian.org tags 1067016 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-settings Version:

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:09 + with message-id and subject line Bug#1064293: fixed in less 590-2.1~deb12u2 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:09 + with message-id and subject line Bug#1068938: fixed in less 590-2.1~deb12u2 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths to be marked as done. This means that you claim that the

Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:05 + with message-id and subject line Bug#1068938: fixed in less 590-2.1~deb12u1 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths to be marked as done. This means that you claim that the

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:05 + with message-id and subject line Bug#1064293: fixed in less 590-2.1~deb12u1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1063879: marked as done (linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image

Bug#1064034: marked as done (FTBFS: Expired test certificate)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:49:19 + with message-id and subject line Bug#1064034: fixed in ruby3.1 3.1.2-7+deb12u1 has caused the Debian Bug report #1064034, regarding FTBFS: Expired test certificate to be marked as done. This means that you claim that the problem has been dealt

Bug#1063729: marked as done (Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot to be marked

Bug#1063689: marked as done (linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU to be marked as done. This means that

Bug#1063717: marked as done (cuda-drivers: Build of module nvidia.ko fails)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding cuda-drivers: Build of module nvidia.ko fails to be marked as done. This means that you

Bug#1063713: marked as done (linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with building modules)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with

Bug#1063668: marked as done (linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues to be marked as done. This means

Bug#1055144: marked as done (nvidia-open-gpu-kernel-modules: CVE-2023-31022)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:21 + with message-id and subject line Bug#1055144: fixed in nvidia-open-gpu-kernel-modules 535.161.08-1~deb12u1 has caused the Debian Bug report #1055144, regarding nvidia-open-gpu-kernel-modules: CVE-2023-31022 to be marked as done. This means that

Bug#1069586: marked as done (Chromium native Wayland support broken)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:47:39 + with message-id and subject line Bug#1069586: fixed in chromium 124.0.6367.78-1~deb12u1 has caused the Debian Bug report #1069586, regarding Chromium native Wayland support broken to be marked as done. This means that you claim that the problem

Bug#1068412: marked as done (apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:47:10 + with message-id and subject line Bug#1068412: fixed in apache2 2.4.59-1~deb12u1 has caused the Debian Bug report #1068412, regarding apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709 to be marked as done. This means that you claim that the

Bug#999922: marked as done (xneur: depends on obsolete pcre3 library)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 17:50:31 + with message-id and subject line Bug#22: fixed in xneur 0.20.0-3.3 has caused the Debian Bug report #22, regarding xneur: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt

Processed: unarchiving 1008010, fixed 1008010 in 7.5.1-1.1+deb10u2, archiving 1008010, unarchiving 1016978 ...

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1008010 Bug #1008010 {Done: David Lamparter } [src:frr] frr: CVE-2022-26125 CVE-2022-26126 CVE-2022-26127 CVE-2022-26128 CVE-2022-26129 Unarchived Bug 1008010 > fixed 1008010 7.5.1-1.1+deb10u2 Bug #1008010 {Done: David Lamparter }

Processed: unarchiving 1066108, fixed 1066108 in 3.20240312.1~deb10u1, fixed 1066108 in 3.20240312.1~deb9u1 ...

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1066108 Bug #1066108 {Done: Henrique de Moraes Holschuh } [src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746 Unarchived Bug 1066108 > fixed 1066108 3.20240312.1~deb10u1

Bug#999922: xneur: diff for NMU version 0.20.0-3.3

2024-05-05 Thread Sebastian Ramacher
Dear maintainer, I've prepared an NMU for xneur (versioned as 0.20.0-3.3). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru xneur-0.20.0/debian/changelog xneur-0.20.0/debian/changelog --- xneur-0.20.0/debian/changelog 2024-05-05 15:23:15.0 +0200 +++

Bug#1069997: marked as done (nginx: NGX_MODULE_SIGNATURE has changed on 32-bit t64 architectures, but the ${nginx:abi} substvar has not)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 17:36:23 + with message-id and subject line Bug#1069997: fixed in nginx 1.26.0-1 has caused the Debian Bug report #1069997, regarding nginx: NGX_MODULE_SIGNATURE has changed on 32-bit t64 architectures, but the ${nginx:abi} substvar has not to be marked as

Bug#1070463: gnome-remote-desktop: 46 has failing build tests

2024-05-05 Thread Jeremy Bícha
Source: gnome-remote-desktop Version: 46.1-1 Severity: serious Tags: ftbfs experimental Control: block 1050237 by -1 X-Debbugs-CC: ma...@ubuntu.com gnome-remote-desktop's build tests are failing. This is blocking the GNOME Shell 46 transition since GNOME Shell & GNOME Remote Desktop should have

Processed: gnome-remote-desktop: 46 has failing build tests

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > block 1050237 by -1 Bug #1050237 [release.debian.org] transition: mutter/gnome-shell 45 1050237 was blocked by: 1050241 1040005 1052414 1052145 1050237 was not blocking any bugs. Added blocking bug(s) of 1050237: 1070463 -- 1050237:

Bug#1070461: marked as done (uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 13:06:41 -0400 with message-id and subject line Re: Bug#1070461: uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration has caused the Debian Bug report #1070461, regarding

Bug#1070460: translate-toolkit: FTBFS: failing tests

2024-05-05 Thread Santiago Vila
Package: src:translate-toolkit Version: 3.12.2-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1070459: psortb: FTBFS: binding.c:52:13: error: implicit declaration of function ‘free’

2024-05-05 Thread Santiago Vila
Package: src:psortb Version: 3.0.6+dfsg-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1070461: uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration

2024-05-05 Thread Santiago Vila
Package: src:uhttpmock0 Version: 0.5.5-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1070458: gxneur: FTBFS: Package 'libpcre', required by 'xnconfig', not found

2024-05-05 Thread Santiago Vila
Package: src:gxneur Version: 0.20.0-2.2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --with

Bug#1070456: crystal: FTBFS: failing tests

2024-05-05 Thread Santiago Vila
Package: src:crystal Version: 1.11.2+dfsg-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1070455: ayatana-indicator-display: FTBFS: Errors while running CTest

2024-05-05 Thread Santiago Vila
Package: src:ayatana-indicator-display Version: 24.1.1-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh

Bug#1064486: rnp: FTBFS: Errors while running CTest

2024-05-05 Thread Andreas Metzler
On 2024-05-04 Santiago Vila wrote: > found 1064486 0.16.3-1 > tags 1064486 + ftbfs bookworm trixie sid > thanks > El 20/4/24 a las 14:12, Andreas Metzler escribió: > > FWIW I also get testsuite errors on current sid on amd64 > > The following tests FAILED: > > 83 -

Bug#1070428: marked as done (bin86,elks-libc: copyright file missing (policy 12.5))

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 16:21:03 + with message-id and subject line Bug#1070428: fixed in linux86 0.16.17-3.6 has caused the Debian Bug report #1070428, regarding bin86,elks-libc: copyright file missing (policy 12.5) to be marked as done. This means that you claim that the

Bug#1070270: riseup-vpn: client no longer works due to cert verification problem

2024-05-05 Thread Nilesh Patra
On Sat, May 04, 2024 at 08:59:19PM +0530, Nilesh Patra wrote: > Hi Matt, > > Quoting Matt Taggart: > > Package: riseup-vpn > > Version: 0.21.11+ds1-5+b1 > > Severity: grave > > > > When attempting to run the bookworm riseup-vpn package, it fails to > > connect to riseup's servers and

Bug#1070428: bin86,elks-libc: copyright file missing (policy 12.5)

2024-05-05 Thread Bastian Germann
I am uploading another NMU to fix this issue. Sorry about that. See the attached debdiff.diff -Nru linux86-0.16.17/debian/.debhelper/generated/bin86/installed-by-dh_installman linux86-0.16.17/debian/.debhelper/generated/bin86/installed-by-dh_installman ---

Processed: Re: Bug#1063026: helvum: Upcoming gtk update

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1063026 {Done: Jonas Smedegaard } [src:helvum] Upcoming gtk update Severity set to 'serious' from 'normal' > tags -1 + ftbfs Bug #1063026 {Done: Jonas Smedegaard } [src:helvum] Upcoming gtk update Added tag(s) ftbfs. -- 1063026:

Bug#1068755: docker.io: FTBFS: failing tests

2024-05-05 Thread Reinhard Tartler
I've been looking at this test failure, but remain puzzled. Basically, the source for this test is here: https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-2/engine/distribution/xfer/download_test.go/#L364-L429. This test is testing code in

Bug#1070225: marked as done (Built from wrong version (3.2 instead of 7.2))

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 14:37:06 + with message-id and subject line Bug#1070172: fixed in gcovr 7.2+really-1.1 has caused the Debian Bug report #1070172, regarding Built from wrong version (3.2 instead of 7.2) to be marked as done. This means that you claim that the problem has

Bug#1070172: marked as done (Built from wrong version (3.2 instead of 7.2))

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 14:37:06 + with message-id and subject line Bug#1070172: fixed in gcovr 7.2+really-1.1 has caused the Debian Bug report #1070172, regarding Built from wrong version (3.2 instead of 7.2) to be marked as done. This means that you claim that the problem has

Bug#1069789: test_bluetooth_hidpp_mouse autopkgtest fails

2024-05-05 Thread Michael Biebl
Control: severity -1 important Seems to pass pretty reliably on debci, thus downgrading to important. https://ci.debian.net/packages/u/upower/ Regards, Michael On Wed, 24 Apr 2024 23:34:48 +0500 Andrey Rakhmatullin wrote: Package: upower Version: 1.90.3-1 Severity: serious Control:

Processed: Re: test_bluetooth_hidpp_mouse autopkgtest fails

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1069789 [upower] test_bluetooth_hidpp_mouse autopkgtest fails Severity set to 'important' from 'serious' -- 1069789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069789 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1070450: qm-dsp: autopkgtest regression on arm64, ppc64el and s390x

2024-05-05 Thread Sebastian Ramacher
Source: qm-dsp Version: 1.7.1-8 Severity: serious X-Debbugs-Cc: sramac...@debian.org qm-dsp currently fails to migrate due to autopkgtest failures on arm64, ppc64el and s390x. https://ci.debian.net/packages/q/qm-dsp/testing/arm64/46236204/ 112s for t in test-mathutilities test-window test-fft

Bug#999922: marked as done (xneur: depends on obsolete pcre3 library)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 13:36:39 + with message-id and subject line Bug#22: fixed in xneur 0.20.0-3.2 has caused the Debian Bug report #22, regarding xneur: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt

Bug#1063948: marked as done (ipyparallel: autopkgtest regression with pytest 8)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 13:35:48 + with message-id and subject line Bug#1063948: fixed in ipyparallel 8.8.0-1~exp1 has caused the Debian Bug report #1063948, regarding ipyparallel: autopkgtest regression with pytest 8 to be marked as done. This means that you claim that the

Bug#1061744: marked as done (ipyparallel ftbfs with Python 3.12 as default)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 13:35:48 + with message-id and subject line Bug#1061744: fixed in ipyparallel 8.8.0-1~exp1 has caused the Debian Bug report #1061744, regarding ipyparallel ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the problem

Bug#1070447: sdpa: dependency generation does not account for t64 changes

2024-05-05 Thread Sebastian Ramacher
Source: sdpa Version: 7.3.16+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Dependencies on libmumps-seq are produced using ${mumps-seq:Version} which does not include the changes from the t64 transition. Please adopt the dependency generation accordingly. Cheers -- Sebastian

Bug#999922: xneur: diff for NMU version 0.20.0-3.2

2024-05-05 Thread Sebastian Ramacher
Dear maintainer, I've prepared an NMU for xneur (versioned as 0.20.0-3.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru xneur-0.20.0/debian/changelog xneur-0.20.0/debian/changelog --- xneur-0.20.0/debian/changelog 2024-04-24 23:52:01.0 +0200 +++

Bug#1070446: rocm-hipamd: arm64 FTBFS with glibc 2.38

2024-05-05 Thread Graham Inggs
Source: rocm-hipamd Version: 5.7.1-3 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], rocm-hipamd FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream

Bug#999922: xneur: depends on obsolete pcre3 library

2024-05-05 Thread Sebastian Ramacher
Control: reopen -1 On 2024-04-25 00:50:36 +0200, Andreas Rönnquist wrote: > > Hi! > > I intend to nmu xneur shortly, fixing the two RC bugs (#22, > #1037902, which has been open 7 months and 2,5 years) using the fixes > that have been posted to the bugs, to help the progress of the time_t

Processed: Re: Bug#999922: xneur: depends on obsolete pcre3 library

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #22 {Done: Andreas Rönnquist } [src:xneur] xneur: depends on obsolete pcre3 library 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No

Bug#1070444: cxref: arm64 FTBFS with glibc 2.38

2024-05-05 Thread Graham Inggs
Source: cxref Version: 1.6e-5 Severity: serious Tags: ftbfs trixie sid Hi Maintainer As can be seen in reproducible builds [1], cxref FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do

Bug#1070443: aspectc++: arm64 FTBFS with glibc 2.38

2024-05-05 Thread Graham Inggs
Source: aspectc++ Version: 1:2.3+git20230726-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], aspectc++ FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc

Bug#1066549: marked as done (geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration])

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 13:19:41 + with message-id and subject line Bug#1066549: fixed in geki2 2.0.8-1 has caused the Debian Bug report #1066549, regarding geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration]

Bug#1070441: cmbc: arm64 FTBFS with glibc 2.38

2024-05-05 Thread Graham Inggs
Source: cbmc Version: 5.95.1-4 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], cbmc FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not

Bug#1070438: liblirc-dev: unhandled symlink to directory conversion: /usr/include/lirc/media

2024-05-05 Thread Andreas Beckmann
Package: liblirc-dev Version: 0.10.2-0.8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old

Processed: Re: Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multipli

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1069357 cpp-httplib: FTBFS: Test > SSLClientServerTest.ClientCertPresent fails with timeout Bug #1069357 [src:cpp-httplib] cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb

Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-arg

2024-05-05 Thread Santiago Vila
retitle 1069357 cpp-httplib: FTBFS: Test SSLClientServerTest.ClientCertPresent fails with timeout thanks El 26/4/24 a las 6:59, Julian Gilbey escribió: It looks like it's just that arm64 is slow (as are several other archs). Note: I can reproduce this on amd64 as well (using m6a.large

Bug#1055297: marked as done (ruby3.1: fails to build against glibc 2.38)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 12:26:40 +0200 with message-id and subject line Re: Bug#1055297: ruby3.1: fails to build against glibc 2.38 has caused the Debian Bug report #1055297, regarding ruby3.1: fails to build against glibc 2.38 to be marked as done. This means that you claim that the

Bug#1070434: python-guizero-doc: unhandled symlink to directory conversion: /usr/share/doc/python3-guizero/html

2024-05-05 Thread Andreas Beckmann
Package: python-guizero-doc Version: 1.5.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an

Processed: Re: Bug#1055297: ruby3.1: fails to build against glibc 2.38

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1055297 [ruby3.1] ruby3.1: fails to build against glibc 2.38 Severity set to 'serious' from 'important' -- 1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration]

2024-05-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1066721 [src:netcat] netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066721 Debian

Bug#1066721: netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration]

2024-05-05 Thread Andreas Beckmann
Followup-For: Bug #1066721 Control: tag -1 pending I've now uploaded the NMU to DELAYED/5. Please let me know if I should delay it lonegr. Andreas

Processed: user debian...@lists.debian.org, usertagging 1060896, found 1060896 in 1.8.10-2.1 ...

2024-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1060896 piuparts There were no usertags set. Usertags are now: piuparts. > found 1060896 1.8.10-2.1 Bug #1060896 [openafs-modules-dkms]

  1   2   >