Bug#1033170: libitext-rups-java: Does not work at all

2023-03-19 Thread Jorge Moraleda
Hello Tony, I propose that we either reduce the severity, ignore the bug for the > bookworm release cycle, or remove only the libitext-rups-java binary > package from bookworm. > Thank you. I believe the appropriate action is #3 (remove libitext-rups-java binary package from bookworm) because it

Bug#1033170: libitext-rups-java: Does not work at all

2023-03-19 Thread tony mancill
On Sat, Mar 18, 2023 at 05:42:12PM -0400, Jorge Moraleda wrote: > Package: libitext-rups-java > Version: 2.1.7-13 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: jorge.moral...@gmail.com > > Dear Maintainer, > > The package does not work at all. Based on the following

Bug#971783: marked as pending in mate-media

2023-03-19 Thread Maxime G.
Hi. Issue reproduced today on Debian Bookworm testing, the mate-volume-control-status-icon crash randomly. mate-volume-control-status-icon --version mate-volume-control-status-icon 1.26.0 Backtrace with gdb: $ gdb mate-volume-control-status-icon GNU gdb (Debian 13.1-2) 13.1 Copyright (C) 2023

Bug#1033210: cairomm FTBFS with nocheck profile: missing boost test

2023-03-19 Thread Helmut Grohne
Source: cairomm Version: 1.14.4-2 Severity: serious Tags: ftbfs trixie sid cairomm fails to build from source when built with the nocheck build profile, because the Boost Test dependency is annotated , but actually required. Such build failures are considered release critical in trixie and later.

Bug#1033039: marked as done (kde-config-flatpak: settings page "flatpak | permissions" is not populated)

2023-03-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Mar 2023 20:34:24 + with message-id and subject line Bug#1033039: fixed in flatpak-kcm 5.27.2-2 has caused the Debian Bug report #1033039, regarding kde-config-flatpak: settings page "flatpak | permissions" is not populated to be marked as done. This means that

Bug#1033167: usrmerge: messes with /etc/shells

2023-03-19 Thread Helmut Grohne
Hi Marco, On Sun, Mar 19, 2023 at 03:01:20AM +0100, Marco d'Itri wrote: > It is expected that /etc/shells can be edited by system administrators, > I have been doing that forever in my career as a professional system > administrator and until now I was not even aware of these programs from >

Bug#1032915: marked as done (guile-gnutls: missing Breaks+Replaces: gnutls-doc (<< 3.7.11))

2023-03-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Mar 2023 17:49:14 + with message-id and subject line Bug#1032915: fixed in guile-gnutls 3.7.11-2 has caused the Debian Bug report #1032915, regarding guile-gnutls: missing Breaks+Replaces: gnutls-doc (<< 3.7.11) to be marked as done. This means that you claim that

Bug#1032104: linux: ppc64el iouring corrupted read

2023-03-19 Thread Salvatore Bonaccorso
Hi, On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote: > Any updates on this one? > > I am still seeing the main.index_merge_innodb failure in > https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1678728871=0 > and rebuild >

Bug#1030595: dkms autoinstall fails if headers are not available but a module could be built

2023-03-19 Thread Andreas Beckmann
On 18/03/2023 18.02, Paul Gevers wrote: I'm trying to understand this bug and what it means for the bookworm release. How bad do you judge this issue to be? Is there any solution in sight? I haven't fully understood what's going on there either, but finally I've now a fix for an (at least)

Bug#1029851: marked as done (ruby-globalid: CVE-2023-22799)

2023-03-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Mar 2023 13:04:06 + with message-id and subject line Bug#1029851: fixed in ruby-globalid 0.6.0-2 has caused the Debian Bug report #1029851, regarding ruby-globalid: CVE-2023-22799 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#1029851 marked as pending in ruby-globalid

2023-03-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1029851 [src:ruby-globalid] ruby-globalid: CVE-2023-22799 Ignoring request to alter tags of bug #1029851 to the same tags previously set -- 1029851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029851 Debian Bug Tracking System Contact

Bug#1029851: marked as pending in ruby-globalid

2023-03-19 Thread Praveen Arimbrathodiyil
Control: tag -1 pending Hello, Bug #1029851 in ruby-globalid 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#1029851 marked as pending in ruby-globalid

2023-03-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1029851 [src:ruby-globalid] ruby-globalid: CVE-2023-22799 Added tag(s) pending. -- 1029851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1029851: marked as pending in ruby-globalid

2023-03-19 Thread Praveen Arimbrathodiyil
Control: tag -1 pending Hello, Bug #1029851 in ruby-globalid 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: Re: psi-plus segfaults

2023-03-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1032655 [psi-plus] psi-plus segfaults Severity set to 'important' from 'grave' > tag -1 moreinfo Bug #1032655 [psi-plus] psi-plus segfaults Added tag(s) moreinfo. -- 1032655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032655

Bug#1032655: psi-plus segfaults

2023-03-19 Thread Martin
Control: severity -1 important Control: tag -1 moreinfo As Stefan, I get warnings, but no crash on Debian 12 bookworm.

Bug#1032104: linux: ppc64el iouring corrupted read

2023-03-19 Thread Otto Kekäläinen
Any updates on this one? I am still seeing the main.index_merge_innodb failure in https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1678728871=0 and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64el=1%3A10.11.2-2%7Eexp1=1679174850=0. Logs