Bug#1035944: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common

2023-05-13 Thread Otto Kekäläinen
After some experimentation I found out that updating libkrb5-3 so that /usr/lib/x86_64-linux-gnu/libkrb5.so.3 upgrades will stop MariaDB from crashing. $ apt install libk5crypto3 libkrb5-3 ... libssl3 amd64 3.0.8-1 libgssapi-krb5-2 amd64 1.20.1-1+b1 libkrb5support0 amd64 1.20.1-1+b1 libkrb5-3

Bug#1035944: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common

2023-05-13 Thread Otto Kekäläinen
Hi! I was able to reproduce this with: apt install mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client sed s/bullseye/bookworm/g -i /etc/apt/sources.list apt update apt-get upgrade Upgrade only updates mysql-common and mariadb-common: $ dpkg -l | grep -e mysql -e maria ii

Bug#1034824: tomcat9 should not be released with Bookworm

2023-05-13 Thread Emmanuel Bourg
Le 2023-05-13 22:38, Markus Koschany a écrit : The question is: If we ship libtomcat9-java in Bookworm and change the dependency from tomcat9-user to tomcat10-user, will a web application like dogtag-pki, which is designed for Tomcat 9, continue to work with Tomcat 10? I'm pretty sure it

Processed: closing 1034081

2023-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1034081 8.0-1 Bug #1034081 [src:openbgpd] openbgpd: FTBFS twice in a row: src/bgpd/parse.c cannot be regenerated Marked as fixed in versions openbgpd/8.0-1. Bug #1034081 [src:openbgpd] openbgpd: FTBFS twice in a row: src/bgpd/parse.c

Bug#924151: grub2-common: wrong grub.cfg for efi boot and fully encrypted disk

2023-05-13 Thread Adam Hough
Copying /boot/grub/grub.cfg to /boot/efi/EFI/debian/ to replace the grub.cfg that was located there does allow for a complete boot. This does result in having to type in the unlock password a second time which is different than before. The contents of the /boot/efi/EFI/debian/grub.cfg was:

Bug#1035713: marked as done (google-android-ndk-r23b-installer: broken symlinks: /usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/*/bin/as -> /buildbot/src/android/...)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 22:56:01 + with message-id and subject line Bug#1035713: fixed in google-android-installers 1675172738 has caused the Debian Bug report #1035713, regarding google-android-ndk-r23b-installer: broken symlinks:

Bug#1035781: marked as done (emacs-common: needs Breaks against incompatible elpa packages from bullseye)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 22:50:07 + with message-id and subject line Bug#1035781: fixed in emacs 1:28.2+1-15 has caused the Debian Bug report #1035781, regarding emacs-common: needs Breaks against incompatible elpa packages from bullseye to be marked as done. This means that you

Bug#1034941: marked as done (emacs-common: missing Breaks+Replaces for emacs-bin-common when upgrading from bullseye)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 22:50:07 + with message-id and subject line Bug#1034941: fixed in emacs 1:28.2+1-15 has caused the Debian Bug report #1034941, regarding emacs-common: missing Breaks+Replaces for emacs-bin-common when upgrading from bullseye to be marked as done. This

Bug#924151: grub2-common: wrong grub.cfg for efi boot and fully encrypted disk

2023-05-13 Thread Adam Hough
Package: grub-efi-amd64-bin Version: 2.06-12 Followup-For: Bug #924151 Dear Maintainer, * What led up to the situation? Upgraded to the latest grub2 packages on 2023-05-02 and then had a power outage today resulting in a reboot. grep grub dpkg.log | grep upgrade 2023-05-02 16:44:00

Bug#1034824: tomcat9 should not be released with Bookworm

2023-05-13 Thread Markus Koschany
Hi Salvatore, adding Timo Aaltonen, maintainer of dogtag-pki and tomcatjss, to CC Am Samstag, dem 13.05.2023 um 20:50 +0200 schrieb Salvatore Bonaccorso: > Hi Markus, > > On Sat, May 13, 2023 at 06:27:49PM +0200, Markus Koschany wrote: > > I have just pushed the necessary changes to our Git

Bug#1030545: qemu-(img|system-s390x) hang on s390x bullseye kernel

2023-05-13 Thread James Addison
Followup-For: Bug #1030545 X-Debbugs-Cc: ben...@debian.org, dipak.zo...@ibm.com Hi Hilko (plus Dipak, fix author on cc for awareness), Debian kernel package 5.10.179-1 that includes a fix for this has been accepted into the stable-security (bullseye-security) suite today, and should resolve this

Bug#1034824: tomcat9 should not be released with Bookworm

2023-05-13 Thread Salvatore Bonaccorso
Hi Markus, On Sat, May 13, 2023 at 06:27:49PM +0200, Markus Koschany wrote: > I have just pushed the necessary changes to our Git repository. > > https://salsa.debian.org/java-team/tomcat9/-/commit/adbd0b0711de66b67278b10e258c47c805e9b993 Do we need to have done more here? When Paul asked on

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
Followup-For: Bug #1030284 I decline to participate further with this bugreport, although others are welcome to pick up from the patches I've submitted (please don't merge them as-is; modify them to apply corrections).

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread Thorsten Glaser
James Addison dixit: >AssertionError [ERR_ASSERTION]: The input did not match the regular > expression /RangeError: Maximum call stack size exceeded/. Input: > >'Segmentation fault\n' You removed the subtraction of V8_STACK_RESERVE when mutilating my patch; this may be related (if

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
Followup-For: Bug #1030284 X-Debbugs-Cc: t...@mirbsd.de It does seem to (continue to) function, at least on x86: ~/dygraphs-2.2.0$ NODE_PATH=/usr/share/nodejs ../nodejs-18.13.0+dfsg1/out/Release/node /usr/bin/babeljs --config-file $PWD/babel.config.json --compact false --source-maps inline

Bug#1034824: marked as pending in tomcat9

2023-05-13 Thread Markus Koschany
Control: tag -1 pending Hello, Bug #1034824 in tomcat9 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#1034824 marked as pending in tomcat9

2023-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1034824 [src:tomcat9] tomcat9 should not be released with Bookworm Added tag(s) pending. -- 1034824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1034824: tomcat9 should not be released with Bookworm

2023-05-13 Thread Markus Koschany
I have just pushed the necessary changes to our Git repository. https://salsa.debian.org/java-team/tomcat9/-/commit/adbd0b0711de66b67278b10e258c47c805e9b993 signature.asc Description: This is a digitally signed message part

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
Followup-For: Bug #1030284 X-Debbugs-Cc: t...@mirbsd.de Hmm.. although the build itself succeeded, there was a unit test failure that appears related to the change: not ok 3213 sequential/test-fs-stat-sync-overflow --- duration_ms: 1.111 severity: fail exitcode: 1 stack: |-

Bug#944016: marked as done (orangeassassin: depends on no longer available python3-raven)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 14:49:44 + with message-id and subject line Bug#1036024: Removed package(s) from experimental has caused the Debian Bug report #944016, regarding orangeassassin: depends on no longer available python3-raven to be marked as done. This means that you claim

Bug#915504: marked as done (sbt: Fails to detect version of java)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 14:47:09 + with message-id and subject line Bug#1035929: Removed package(s) from unstable has caused the Debian Bug report #915504, regarding sbt: Fails to detect version of java to be marked as done. This means that you claim that the problem has been

Bug#894540: marked as done (sbt FTBFS with openjdk-9)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 14:47:09 + with message-id and subject line Bug#1035929: Removed package(s) from unstable has caused the Debian Bug report #894540, regarding sbt FTBFS with openjdk-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1026386: marked as done (orangeassassin: FTBFS with Python 3.11)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 14:49:44 + with message-id and subject line Bug#1036024: Removed package(s) from experimental has caused the Debian Bug report #1026386, regarding orangeassassin: FTBFS with Python 3.11 to be marked as done. This means that you claim that the problem has

Bug#1035503: marked as done (glewlwyd-common: prompting due to modified conffiles which were not modified by the user: /etc/glewlwyd/config.json)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 14:34:50 + with message-id and subject line Bug#1035503: fixed in glewlwyd 2.7.5-3 has caused the Debian Bug report #1035503, regarding glewlwyd-common: prompting due to modified conffiles which were not modified by the user: /etc/glewlwyd/config.json to

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
Followup-For: Bug #1030284 X-Debbugs-Cc: t...@mirbsd.de Thanks, Thorsten. I'm currently rebuilding (on x86) from the attached patch, adapted from yours. * prefers a one-time repeat division over the clever-but-fragile div-assign * removes the upperbound check because integer greater-than

Bug#1036028: squidguard relies on packet squid instead of squid or squid-openssl

2023-05-13 Thread domele
Package: squidguard Version: 1.6.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? installing squid-openssl * What exactly did you do (or not

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread Thorsten Glaser
James Addison dixit: >... to add something like this: Ouch, by going via a string?! I wouldn’t have thought of that… > if (!(flags & ProcessInitializationFlags::kNoAdjustResourceLimits)) { >struct rlimit lim; >if (getrlimit(RLIMIT_STACK, ) == 0) { > char stackSize[32]; 32 is

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
On Sat, 13 May 2023 at 12:15, James Addison wrote: > > On Sat, 13 May 2023 at 11:14, James Addison wrote: > > > > On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote: > > > > > > James Addison dixit: > > > > > > >I'm going to stay involved with this thread, but I think that it is > > > >upon

Bug#1035732: libkscreenlocker5: Endless loop when using PAM

2023-05-13 Thread Patrick Franz
Hi Andreas, On Mon, 8 May 2023 14:15:17 +0200 "Poenicke, Andreas (TKM)" wrote: > Package: libkscreenlocker5 > Version: 5.20.5-1 > Severity: critical > Tags: patch upstream > Justification: breaks the whole system [...] > Please include the short patch >

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
On Sat, 13 May 2023 at 11:14, James Addison wrote: > > On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote: > > > > James Addison dixit: > > > > >I'm going to stay involved with this thread, but I think that it is > > >upon you to develop or provide further guidance towards a patch if > > >it's

Bug#1034943: marked as done (liblxqt1-dev: missing Breaks+Replaces for liblxqt0-dev when upgrading from bullseye)

2023-05-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 May 2023 10:20:21 + with message-id and subject line Bug#1034943: fixed in liblxqt 1.2.0-7 has caused the Debian Bug report #1034943, regarding liblxqt1-dev: missing Breaks+Replaces for liblxqt0-dev when upgrading from bullseye to be marked as done. This means

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote: > > James Addison dixit: > > >I'm going to stay involved with this thread, but I think that it is > >upon you to develop or provide further guidance towards a patch if > >it's something you'd like to have implemented, Thorsten. > > I actually

Bug#1036022: altos,lprint: undeclared file conflict on /usr/lib/x86_64-linux-gnu/systemd/system

2023-05-13 Thread Helmut Grohne
Package: altos,lprint Severity: serious X-Debbugs-Cc: a...@debian.org Hi, while Andreas usually files bugs about file conflicts, his tooling seems to have missed this one. It's quite special. While altos ships /usr/lib/x86_64-linux-gnu/systemd/system as a directory containing a systemd unit,

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

2023-05-13 Thread Helmut Grohne
Package: cadabra2,python3-notebook Severity: serious X-Debbugs-Cc: a...@debian.org, debian-d...@lists.debian.org Hi, I noticed a suprising undeclared file conflict. While Andreas' tooling finds most of these, it missed this one. It's about

Processed: Re: Bug#1035438: cl-quicklisp: installation instructions do not work

2023-05-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1035438 [cl-quicklisp] cl-quicklisp: installation instructions do not work Severity set to 'minor' from 'grave' -- 1035438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035438 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1035438: cl-quicklisp: installation instructions do not work

2023-05-13 Thread Sébastien Villemot
Control: severity -1 minor Dear Michael, Le mercredi 03 mai 2023 à 09:23 -0400, Michael P. Soulier a écrit : > Package: cl-quicklisp > Version: 20150128-1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: msoul...@digitaltorque.ca > > Dear Maintainer, > > I followed