Bug#1088905: marked as done (asciiart: autopkgtest failing with imagemagick 7)

Your message dated Tue, 10 Dec 2024 07:49:00 + with message-id and subject line Bug#1088905: fixed in asciiart 0.3.0-3 has caused the Debian Bug report #1088905, regarding asciiart: autopkgtest failing with imagemagick 7 to be marked as done. This means that you claim that the problem has bee

Bug#1089113: marked as done (transition: qtermwidget)

Your message dated Tue, 10 Dec 2024 07:20:15 + with message-id and subject line Bug#1089113: fixed in texstudio 4.8.4+ds-2 has caused the Debian Bug report #1089113, regarding transition: qtermwidget to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1071045: marked as done (gauche-c-wrapper: FTBFS against gauche 0.9.14 (0.98))

Your message dated Tue, 10 Dec 2024 06:04:14 + with message-id and subject line Bug#1071045: fixed in gauche-c-wrapper 0.6.1-13 has caused the Debian Bug report #1071045, regarding gauche-c-wrapper: FTBFS against gauche 0.9.14 (0.98) to be marked as done. This means that you claim that the pr

Bug#1087816: marked as done (lsdvd: misrepresents location of upstream source)

Your message dated Tue, 10 Dec 2024 06:20:42 + with message-id and subject line Bug#1087816: fixed in lsdvd 0.17-2 has caused the Debian Bug report #1087816, regarding lsdvd: misrepresents location of upstream source to be marked as done. This means that you claim that the problem has been de

Bug#1089621: xen: Invalid copyright years "2022-present"

Source: xen Version: 4.17.3+36-g54dacb5c02-1 Severity: serious Justification: Policy 2.3, 4.5, 12.5 X-Debbugs-CC: ftpmas...@debian.org Dear maintainer, Copyright 2022-present Keir Fraser and/or many others" is not a valid copyright claim. Copyright is always time-limited, so it simply does

Bug#1087747: marked as done (claws-mail: Links with license-incompatible library)

Your message dated Tue, 10 Dec 2024 01:04:14 + with message-id and subject line Bug#1087747: fixed in libetpan 1.9.4-5 has caused the Debian Bug report #1087747, regarding claws-mail: Links with license-incompatible library to be marked as done. This means that you claim that the problem has

Bug#1087362: marked as done (how-can-i-help: /usr/bin/how-can-i-help script returns a "no implicit conversion" error)

Your message dated Tue, 10 Dec 2024 00:48:57 + with message-id and subject line Bug#1087362: fixed in how-can-i-help 20 has caused the Debian Bug report #1087362, regarding how-can-i-help: /usr/bin/how-can-i-help script returns a "no implicit conversion" error to be marked as done. This mean

Processed: Bug#1052292 marked as pending in inkscape

Processing control commands: > tag -1 pending Bug #1052292 [inkscape] inkscape: missing Breaks+Replaces: inkscape-open-symbols (<< 1.3) Added tag(s) pending. -- 1052292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052292 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#1052292: marked as pending in inkscape

Control: tag -1 pending Hello, Bug #1052292 in inkscape 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/inkscape/-/commit/d5907106b4ffe620854bec

Bug#1086285: marked as done (libplacebo: FTBFS: undefined reference to `glslang::TShader::setStrings(char const* const*, int)')

Your message dated Mon, 09 Dec 2024 23:35:00 + with message-id and subject line Bug#1086285: fixed in libplacebo 7.349.0-3 has caused the Debian Bug report #1086285, regarding libplacebo: FTBFS: undefined reference to `glslang::TShader::setStrings(char const* const*, int)' to be marked as don

Bug#1088268: marked as done (inkscape and lib2geom-dev have an undeclared file conflict on 5 files)

Your message dated Tue, 10 Dec 2024 00:16:27 +0100 with message-id and subject line Re: inkscape and lib2geom-dev have an undeclared file conflict on 5 files has caused the Debian Bug report #1088268, regarding inkscape and lib2geom-dev have an undeclared file conflict on 5 files to be marked as

Bug#1089551: marked as done (inkscape and lib2geom1.4.0 have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/lib2geom.so.1.4.0)

Your message dated Tue, 10 Dec 2024 00:16:27 +0100 with message-id and subject line Re: inkscape and lib2geom-dev have an undeclared file conflict on 5 files has caused the Debian Bug report #1089551, regarding inkscape and lib2geom1.4.0 have an undeclared file conflict on /usr/lib/x86_64-linux-

Bug#1088725: marked as done (python-uvicorn: FTBFS: E DeprecationWarning: websockets.legacy is deprecated)

Your message dated Mon, 09 Dec 2024 22:50:34 + with message-id and subject line Bug#1088725: fixed in python-uvicorn 0.32.0-2 has caused the Debian Bug report #1088725, regarding python-uvicorn: FTBFS: E DeprecationWarning: websockets.legacy is deprecated to be marked as done. This means tha

Bug#1075445: marked as done (reprozip: ftbfs with GCC-14)

Your message dated Mon, 09 Dec 2024 21:54:56 + with message-id and subject line Bug#1075445: fixed in reprozip 1.3-3 has caused the Debian Bug report #1075445, regarding reprozip: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1079476: marked as done (plasma-dialer: FTBFS)

Your message dated Mon, 09 Dec 2024 21:34:54 + with message-id and subject line Bug#1079476: fixed in plasma-dialer 1:6.2.4-1 has caused the Debian Bug report #1079476, regarding plasma-dialer: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Bug#1088725 marked as pending in python-uvicorn

Processing control commands: > tag -1 pending Bug #1088725 [src:python-uvicorn] python-uvicorn: FTBFS: E DeprecationWarning: websockets.legacy is deprecated Added tag(s) pending. -- 1088725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088725 Debian Bug Tracking System Contact ow...@bugs.

Bug#1088725: marked as pending in python-uvicorn

Control: tag -1 pending Hello, Bug #1088725 in python-uvicorn 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-uvicorn/-/commit/6ba1c

Processed: bug 1088315 is forwarded to https://github.com/ipython/ipykernel/issues/1302

Processing commands for cont...@bugs.debian.org: > forwarded 1088315 https://github.com/ipython/ipykernel/issues/1302 Bug #1088315 [src:ipykernel] ipykernel: autopkgtest failure with Python 3.13 Set Bug forwarded-to-address to 'https://github.com/ipython/ipykernel/issues/1302'. > thanks Stopping

Bug#1089608: gimp-data-extras: Please package gimp 3 compatible version

Source: gimp-data-extras Version: 1:2.0.2-1.1 Severity: serious The Debian GNOME team will be uploading gimp 3 to Unstable soon for inclusion in Debian 13 Trixie. I am filing this as serious now since gimp has been removed from Testing and I don't expect gimp to re-enter Testing before the gimp 3

Bug#1075065: marked as done (heaptrack: ftbfs with GCC-14)

Your message dated Mon, 09 Dec 2024 20:38:26 + with message-id and subject line Bug#1075065: fixed in heaptrack 1.5.0+dfsg1-3 has caused the Debian Bug report #1075065, regarding heaptrack: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1072424: Upgrading to upstream version 1.2.3 would fix ffmpeg 7 + bootstrap bugs

Control: tag -1 fixed-upstream The following commit added support for bootstrap-html (v5): https://github.com/meetecho/janus-gateway/commit/5cc6c6c1f3cdaf96fc4adf19acff73f0006ccae9 which was the result of the following upstream PR: https://github.com/meetecho/janus-gateway/pull/3300 and that would

Bug#1075218: libx86: ftbfs with GCC-14

Control: tags 1075218 patch Dear libx86 maintainer, I have developed a fix for this failure to build from source with gcc-14 for the forthcoming trixie release and would be grateful if you would consider merging it, please! The merge request is available at:

Bug#1066196: marked as done (pacman4console: FTBFS: pacman.c:142:12: error: implicit declaration of function ‘GameOverScreen’ [-Werror=implicit-function-declaration])

Your message dated Mon, 09 Dec 2024 19:52:24 + with message-id and subject line Bug#1066196: fixed in pacman4console 1.3-1.1 has caused the Debian Bug report #1066196, regarding pacman4console: FTBFS: pacman.c:142:12: error: implicit declaration of function ‘GameOverScreen’ [-Werror=implicit-

Processed: Re: libx86: ftbfs with GCC-14

Processing control commands: > tags 1075218 patch Bug #1075218 [src:libx86] libx86: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075218 to the same tags previously set -- 1075218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075218 Debian Bug Tracking System Contact ow...@bugs

Processed: Re: libx86: ftbfs with GCC-14

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

Bug#1089503: marked as done (rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given)

Your message dated Mon, 09 Dec 2024 19:21:48 + with message-id and subject line Bug#1089503: fixed in rtpengine 12.5.1.18-1 has caused the Debian Bug report #1089503, regarding rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, bu

Processed: hypre: FTBFS: Unable to find reachable pairing between local and remote interfaces

Processing commands for cont...@bugs.debian.org: > # the first time it was the wrong bug > owner 1087784 ! Bug #1087784 {Done: Santiago Vila } [src:hypre] hypre: FTBFS: Unable to find reachable pairing between local and remote interfaces Owner recorded as Santiago Vila . > reopen 1087784 Bug #108

Processed: Upgrading to upstream version 1.2.3 would fix ffmpeg 7 + bootstrap bugs

Processing control commands: > tag -1 fixed-upstream Bug #1072424 [src:janus] janus: FTBFS with ffmpeg 7.0: postprocessing/pp-g722.c:215:61: error: ‘AVCodecContext’ has no member named ‘channels’ Added tag(s) fixed-upstream. -- 1072424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072424

Bug#1075615: vbetool: ftbfs with GCC-14

Control: tags 1075615 patch Dear maintainer, I have developed a fix for this failure to build from source with gcc-14 for the forthcoming trixie release and would be grateful if you would consider merging it, please! The merge request is available at:

Bug#1088887: marked as done (cctools FTBFS on 32-bit with 64-bit time_t)

Your message dated Mon, 09 Dec 2024 18:34:05 + with message-id and subject line Bug#107: fixed in cctools 1:7.13.1-3 has caused the Debian Bug report #107, regarding cctools FTBFS on 32-bit with 64-bit time_t to be marked as done. This means that you claim that the problem has been de

Bug#1089598: dhcpcd-base: Upgrade from bookworm (isc-dhcp-client) breaks DDNS

Source: dhcpcd Followup-For: Bug #1089598 X-Debbugs-Cc: martin-eric.rac...@iki.fi,d...@darkboxed.org Daniel, Please see recently closed bugs. Someone recently requested the same thing. Upstream insists on shipping that option commented out because he feels that exposing the hostname is a privac

Processed: Re: vbetool: ftbfs with GCC-14

Processing control commands: > tags 1075615 patch Bug #1075615 [src:vbetool] vbetool: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075615 to the same tags previously set -- 1075615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075615 Debian Bug Tracking System Contact ow...@bu

Processed: Re: vbetool: ftbfs with GCC-14

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

Bug#1037322: Librabbitmq : CVE-2023-35789

* P Tamil Selvam [241209 17:03]: > We are currently using Debian Bookworm 12.8 and have identified a > vulnerability issue with the librabbitmq package. Could you please confirm if > there is an ETA for a fix or update to address this in an upcoming Bookworm > release? The currently available

Bug#1087784: hypre: FTBFS: Unable to find reachable pairing between local and remote interfaces

owner 1068809 ! reopen 1068809 forwarded 1068809 https://github.com/hypre-space/hypre/issues/1194 thanks El 6/12/24 a las 0:05, Drew Parsons escribió: It's a strange warning, I don't yet understand what it means. I see it locally on my own system. It doesn't seem to be blocking processes from r

Processed: Re: Bug#1089590: xtrkcad dies with a Segementation Fault. I have included a strace log.

Processing commands for cont...@bugs.debian.org: > tags 1089590 + moreinfo Bug #1089590 [xtrkcad] xtrkcad dies with a Segementation Fault. I have included a strace log. Added tag(s) moreinfo. > severity 1089590 important Bug #1089590 [xtrkcad] xtrkcad dies with a Segementation Fault. I have in

Bug#1018021: marked as done (giblib: FTBFS with imlib2 1.9.1)

Your message dated Mon, 09 Dec 2024 18:14:23 + with message-id and subject line Bug#1089547: Removed package(s) from unstable has caused the Debian Bug report #1018021, regarding giblib: FTBFS with imlib2 1.9.1 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1087699: marked as done (cmdtest: remove from Debian?)

Your message dated Mon, 09 Dec 2024 18:08:29 + with message-id and subject line Bug#1088868: Removed package(s) from unstable has caused the Debian Bug report #1087699, regarding cmdtest: remove from Debian? to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#1088887 marked as pending in cctools

Processing control commands: > tag -1 pending Bug #107 [src:cctools] cctools FTBFS on 32-bit with 64-bit time_t Ignoring request to alter tags of bug #107 to the same tags previously set -- 107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107 Debian Bug Tracking System Cont

Bug#1088887: marked as pending in cctools

Control: tag -1 pending Hello, Bug #107 in cctools 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/neurodebian-team/cctools/-/commit/5cc01f550e6f2d157d9d2ed

Bug#1088062: marked as done (gimplensfun: Not compatible with gimp 3)

Your message dated Mon, 09 Dec 2024 18:10:04 + with message-id and subject line Bug#1089032: Removed package(s) from unstable has caused the Debian Bug report #1088062, regarding gimplensfun: Not compatible with gimp 3 to be marked as done. This means that you claim that the problem has been

Bug#1002102: marked as done (python-dugong: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Mon, 09 Dec 2024 18:02:18 + with message-id and subject line Bug#1079357: Removed package(s) from unstable has caused the Debian Bug report #1002102, regarding python-dugong: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This

Bug#1075400: marked as done (pth: ftbfs with GCC-14)

Your message dated Mon, 09 Dec 2024 18:06:12 + with message-id and subject line Bug#1087708: Removed package(s) from unstable has caused the Debian Bug report #1075400, regarding pth: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1082507: marked as done (RM: squizz -- RoM, RoQA, obsolete)

Your message dated Mon, 09 Dec 2024 18:03:54 + with message-id and subject line Bug#1082506: Removed package(s) from unstable has caused the Debian Bug report #1082507, regarding RM: squizz -- RoM, RoQA, obsolete to be marked as done. This means that you claim that the problem has been dealt

Bug#1032114: marked as done (Don't release with bookworm)

Your message dated Mon, 09 Dec 2024 18:04:26 + with message-id and subject line Bug#1086767: Removed package(s) from unstable has caused the Debian Bug report #1032114, regarding Don't release with bookworm to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1089503: rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given

Control: tag -1 fixed-upstream patch On Mon, 09 Dec 2024 08:42:14 + Victor Seva wrote: > forwarded 1089503 https://github.com/sipwise/rtpengine/issues/1882 Upstream fixed it in the following commit https://github.com/sipwise/rtpengine/commit/6b3f3b9698ed9670fedccd0db5f595d1c0db917e And als

Processed: Re: Bug#1089503: rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given

Processing control commands: > tag -1 fixed-upstream patch Bug #1089503 [rtpengine-kernel-dkms] rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given Added tag(s) patch and fixed-upstream. -- 1089503: https://bugs.deb

Bug#1089598: dhcpcd-base: Upgrade from bookworm (isc-dhcp-client) breaks DDNS

Package: dhcpcd-base Version: 1:10.1.0-2 Severity: serious Justification: Breaks network rechability, thus making unrelated software on system break (per rc_policy.txt). X-Debbugs-Cc: d...@darkboxed.org Hi Martin, dhcpcd-base does not send the system's hostname by default as isc-dhcp-client used

Bug#1085289:

Hi, > The attached patch resolves the issue in (at least) the lxc autopkgtest > environment. I would suggest a lower range, as the gid mapping inside containers (at least lxd in ubuntu) doesn't allow such a large range by default. Since the ping command is executed by the "backuppc" user, which i

Processed: [bts-link] source package src:qiime

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:qiime > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setti

Processed: [bts-link] source package src:blueprint-compiler

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:blueprint-compiler > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.deb

Bug#1075169: marked as pending in libgda5

Control: tag -1 pending Hello, Bug #1075169 in libgda5 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/libgda5/-/commit/b1740a74515375922d0217cf1ddc0

Bug#1089051: marked as done (python-picologging: autopkgtest failure with Python 3.13)

Your message dated Mon, 09 Dec 2024 17:21:36 + with message-id and subject line Bug#1089051: fixed in python-picologging 0.9.4-2 has caused the Debian Bug report #1089051, regarding python-picologging: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim that t

Bug#1087299: fonts-arapey: FTBFS: fontTools.varLib.errors.VariationModelError: Locations must be unique.

Control: forwarded -1 https://github.com/etunni/arapey/issues/8 On Mon, 11 Nov 2024 01:29:38 +0100 Santiago Vila wrote: > Package: src:fonts-arapey > Version: 0+git20200408-3 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > During a rebuild of all packages in unstable, your package fa

Processed: Re: fonts-arapey: FTBFS: fontTools.varLib.errors.VariationModelError: Locations must be unique.

Processing control commands: > forwarded -1 https://github.com/etunni/arapey/issues/8 Bug #1087299 [src:fonts-arapey] fonts-arapey: FTBFS: fontTools.varLib.errors.VariationModelError: Locations must be unique. Set Bug forwarded-to-address to 'https://github.com/etunni/arapey/issues/8'. -- 10872

Bug#1089488: [Pkg-zfsonlinux-devel] Bug#1089488: zfs-dkms: module build fails for kernel: 6.12.3-amd64 (x86_64)

Much appreciated, Craig! I started using zfs a year ago and was naively thinking that the Debian package system somehow "handled" things. I see that is not the case. What can be done better? On Sunday, December 8, 2024 7:53:03 P.M. CST Craig Sanders wrote: > If you use ZFS (or ANY other n

Bug#1037322: Shadow : CVE-2023-35789

Hi Team, We are currently using Debian Bookworm 12.8 and have identified a vulnerability issue with the librabbitmq package. Could you please confirm if there is an ETA for a fix or update to address this in an upcoming Bookworm release? Additionally, if there are any available workarounds or i

Bug#1037322: Librabbitmq : CVE-2023-35789

Hi Team, We are currently using Debian Bookworm 12.8 and have identified a vulnerability issue with the librabbitmq package. Could you please confirm if there is an ETA for a fix or update to address this in an upcoming Bookworm release? Additionally, if there are any available workarounds or i

Processed: Re: Bug#1078862: Please upload 1.3.x to unstable

Processing control commands: > block -1 by 1089551 1052292 Bug #1078862 [inkscape] Please upload 1.3.x to unstable 1078862 was not blocked by any bugs. 1078862 was not blocking any bugs. Added blocking bug(s) of 1078862: 1052292 and 1089551 -- 1078862: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#1075169: marked as done (libgda5: ftbfs with GCC-14)

Your message dated Mon, 09 Dec 2024 15:19:49 + with message-id and subject line Bug#1075169: fixed in libgda5 5.2.10-5 has caused the Debian Bug report #1075169, regarding libgda5: 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#1075169 marked as pending in libgda5

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

Bug#1082682: marked as done (gnome-robots: FTBFS: /usr/bin/ld: src/gnome-robots.p/meson-generated_game-area.c.o: undefined reference to symbol 'atan2@@GLIBC_2.2.5')

Your message dated Mon, 09 Dec 2024 14:39:12 + with message-id and subject line Bug#1082682: fixed in gnome-robots 1:40.0-3 has caused the Debian Bug report #1082682, regarding gnome-robots: FTBFS: /usr/bin/ld: src/gnome-robots.p/meson-generated_game-area.c.o: undefined reference to symbol '

Bug#1089212: marked as done (gnome-control-center:FTBFS:build failure on riscv (test-network-panel test timeout))

Your message dated Mon, 09 Dec 2024 14:39:03 + with message-id and subject line Bug#1089212: fixed in gnome-control-center 1:47.2-2 has caused the Debian Bug report #1089212, regarding gnome-control-center:FTBFS:build failure on riscv (test-network-panel test timeout) to be marked as done. T

Bug#1089590: xtrkcad dies with a Segementation Fault. I have included a strace log.

Package: xtrkcad Version: 1:5.2.0Beta2.1-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? I just ran the program (xtrkcad). * What was the outco

Bug#1082682: marked as pending in gnome-robots

Control: tag -1 pending Hello, Bug #1082682 in gnome-robots 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/gnome-robots/-/commit/a279d8d7924f3fa3172

Processed: Bug#1082682 marked as pending in gnome-robots

Processing control commands: > tag -1 pending Bug #1082682 [src:gnome-robots] gnome-robots: FTBFS: /usr/bin/ld: src/gnome-robots.p/meson-generated_game-area.c.o: undefined reference to symbol 'atan2@@GLIBC_2.2.5' Added tag(s) pending. -- 1082682: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#1018359: marked as done (freeipa: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Mon, 09 Dec 2024 13:49:21 + with message-id and subject line Bug#1018359: fixed in freeipa 4.12.2-1 has caused the Debian Bug report #1018359, regarding freeipa: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that th

Bug#1057677: marked as done (resteasy: ftbfs due to the missing dependency org.jboss.resteasy:resteasy-jaxrs:jar:3.6.2.Final)

Your message dated Mon, 09 Dec 2024 13:36:27 + with message-id and subject line Bug#1057677: fixed in resteasy 3.6.2-3 has caused the Debian Bug report #1057677, regarding resteasy: ftbfs due to the missing dependency org.jboss.resteasy:resteasy-jaxrs:jar:3.6.2.Final to be marked as done. Th

Bug#1088125: marked as done (libpgjava: FTBFS: dh_install: warning: Cannot find (any matches for) "target/site/apidocs/*")

Your message dated Mon, 09 Dec 2024 13:20:41 + with message-id and subject line Bug#1088125: fixed in libpgjava 42.7.3-2 has caused the Debian Bug report #1088125, regarding libpgjava: FTBFS: dh_install: warning: Cannot find (any matches for) "target/site/apidocs/*" to be marked as done. Thi

Bug#1088125: marked as pending in libpostgresql-jdbc-java

Control: tag -1 pending Hello, Bug #1088125 in libpostgresql-jdbc-java 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/java-team/libpostgresql-jdbc-java/-/commi

Processed: Bug#1088125 marked as pending in libpostgresql-jdbc-java

Processing control commands: > tag -1 pending Bug #1088125 [src:libpgjava] libpgjava: FTBFS: dh_install: warning: Cannot find (any matches for) "target/site/apidocs/*" Added tag(s) pending. -- 1088125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088125 Debian Bug Tracking System Contact

Bug#1088605: installation-reports: No installable kernel was found in the defined APT sources

Hi, Daniel Lewart wrote: > I did find 215 MiB of exact duplicate files. > ... > 24724624 Oct 30 10:07 firmware/firmware-atheros_20240909-2_all.deb > 24724624 Oct 30 10:07 > pool/non-free-firmware/f/firmware-nonfree/firmware-atheros_20240909-2_all.deb These two most probably share their content i

Bug#1084668: marked as pending in qiime

Control: tag -1 pending Hello, Bug #1084668 in qiime reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/qiime/-/commit/c3f8b14d6625670f8e924026157ab01c30c

Processed: Bug#1084668 marked as pending in qiime

Processing control commands: > tag -1 pending Bug #1084668 [src:qiime] qiime: removal of Python standard libraries in Python 3.13 Ignoring request to alter tags of bug #1084668 to the same tags previously set -- 1084668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084668 Debian Bug Track

Bug#1089220: marked as done (cockpit-ws has an undeclared file conflict)

Your message dated Mon, 09 Dec 2024 12:04:45 + with message-id and subject line Bug#1089220: fixed in cockpit 330-2 has caused the Debian Bug report #1089220, regarding cockpit-ws has an undeclared file conflict to be marked as done. This means that you claim that the problem has been dealt w

Bug#1088974: marked as done (chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected)

Your message dated Mon, 09 Dec 2024 12:02:22 + with message-id and subject line Bug#1088974: fixed in chromium 131.0.6778.108-1~deb12u1 has caused the Debian Bug report #1088974, regarding chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

Bug#1088605: installation-reports: No installable kernel was found in the defined APT sources

Cyril, et al, On Sat, Dec 7, 2024 at 2:29 PM Cyril Brulebois wrote: > ... > I haven't looked deeper at this point, maybe we have some other kinds of > “duplication” (not sure the t64 thing is over at this point, but I could > imagine how we might pull t64 and pre-t64 libraries until everything i

Bug#1081851: marked as done (python3-scruffy: 0001-Migrate-from-imp-to-importlib.patch breaks with Python 3.12)

Your message dated Mon, 09 Dec 2024 11:04:37 + with message-id and subject line Bug#1081851: fixed in python-scruffy 0.3.8.2-2 has caused the Debian Bug report #1081851, regarding python3-scruffy: 0001-Migrate-from-imp-to-importlib.patch breaks with Python 3.12 to be marked as done. This mea

Bug#1085192: [Debian-on-mobile-maintainers] Bug#1085192: phoc: build-depends on missing: libwlroots-dev:loong64 (>= 0.17.0)

On Mon, 2 Dec 2024 16:00:18 +0100 Chris Hofstaedtler wrote: > On Thu, Nov 14, 2024 at 11:11:43AM +0100, Guido Günther wrote: > > Not in this case. 0.18 is considerably different regarding > > e.g. rendering, damage tracking, etc. It's not just an API change. > > So, whats the plan here now? > >

Bug#1081851: python3-scruffy: 0001-Migrate-from-imp-to-importlib.patch breaks with Python 3.12

Hi, I switched back to python3-zombie-imp. At least a local build of voltron succeeds now. I hope a new upstream release show up some day. >Le jeu. 3 oct. 2024 à 23:49, Colin Watson a écrit :

Bug#1089580: visualvm: JVM crashes with StackOverflowError at startup

Package: visualvm Version: 2.1.8-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sre4e...@free.fr Dear Maintainers, VisualVM as packaged and using the provided /usr/bin/visualvm to launch it is currently unusable at least with the JDK 21 (default JDK) and JDK 11, I haven't

Bug#1089231: dials: autopkgtest regression in testing

Hi Andrius On Mon, 9 Dec 2024 at 08:54, Andrius Merkys wrote: > dials autopkgtest apparently does not pull in the dependency on > python3-gemmi. I think python3-dials should have 'Depends: python3-gemmi'. Upstream's changelog mentions "gemmi-less objects can be used by other gemmi-less software"

Bug#1089231: dials: autopkgtest regression in testing

Hello, On 2024-12-07 15:56, Graham Inggs wrote: 219s from .pinkindexer import PinkIndexer 219s /usr/lib/python3/dist-packages/dials/algorithms/indexing/lattice_search/pinkindexer.py:5: in 219s import gemmi 219s E ModuleNotFoundError: No module named 'gemmi' dials autopkgtest apparently does

Bug#1089548: /usr/bin/uscan: uscan die: OpenPGP signature did not verify. at /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.

On Sun, Dec 08, 2024 at 10:49:05PM -0500, James McCoy wrote: > On Mon, Dec 09, 2024 at 03:41:39AM +0100, Guillem Jover wrote: > > This is a consequence of the switch from gpg to gpgv, which has now > > surfaced issues in how the certificates are stored in the Linux > > packaging (and while checking

Bug#1066998: sift FTBFS fixup

On 09/12/24 5:39 am, Santiago Vila wrote: Hi. Here is a one-line patch. (After all, this is what prototypes were invented for) This is already defined in src/Matrix_Info.h and it is sort of weird for this error to be thrown in the first place. I did not dig too much, though. Thanks.

Bug#1089503: rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given

forwarded 1089503 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089503 -- - | ,''`. Victor Seva | | : :' : linuxman...@torreviejawireless.org | | `. `' PGP: 8

Bug#1089503: rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given

forwarded 1089503 https://github.com/sipwise/rtpengine/issues/1882 -- - | ,''`. Victor Seva | | : :' : linuxman...@torreviejawireless.org | | `. `' PGP: 8F19 CADC

Processed: Re: Bug#1089503: rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given

Processing commands for cont...@bugs.debian.org: > forwarded 1089503 https://github.com/sipwise/rtpengine/issues/1882 Bug #1089503 [rtpengine-kernel-dkms] rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given Changed Bu

Processed: Re: Bug#1089503: rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given

Processing commands for cont...@bugs.debian.org: > forwarded 1089503 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089503 Bug #1089503 [rtpengine-kernel-dkms] rtpengine-kernel-dkms: module fails to build for Linux 6.12: error: macro "_spin_lock_init" requires 2 arguments, but only 1 given S