Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-26 Thread Roberto C . Sánchez
On Fri, Aug 25, 2023 at 11:02:35PM -0400, Chris Frey wrote: > On Fri, Aug 25, 2023 at 07:02:07AM -0400, Roberto C. Sánchez wrote: > > To claim that "because this bug affects me, it *must* be > > fixed, even when it does not meet the criteria for a normal security bug > > and when the maintainer

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Chris Frey
On Fri, Aug 25, 2023 at 07:02:07AM -0400, Roberto C. Sánchez wrote: > To claim that "because this bug affects me, it *must* be > fixed, even when it does not meet the criteria for a normal security bug > and when the maintainer thinks there is a risk of breaking working > configurations for other

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Marc SCHAEFER
Hello, On Fri, Aug 25, 2023 at 01:41:36PM +0200, Christopher Huhn wrote: > Given that will give you an updated package in Bullseye you'd still have to > change your code to change the GDBM_PREREAD behaviour. Do you mean that something changed in bookworm that will create a problem for my

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Marc SCHAEFER
Hello, Thank you for your answers. In short: the work-around that I mentionned in the bug report is in place, and it works for me. The problem is "solved" for me and it does not look that any further effort to fix it in bullseye will work. Long version: Although it seems that ALL users of that

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Roberto C . Sánchez
On Fri, Aug 25, 2023 at 01:41:36PM +0200, Christopher Huhn wrote: > [SNIP a bunch of good recommdnations for getting a patch accepted] Definitely, that is the way to go if someone wants to get a bug fixed in a release before it becomes LTS. > That said, LTS point releases do contain functional

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Christopher Huhn
Am 25.08.23 um 12:30 schrieb Roberto C. Sánchez: I reported this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043023 The first reason is that bugs of this nature (i.e., bugs that are not of a serious security nature, but which might still require a fix) are handled by the

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Roberto C . Sánchez
On Fri, Aug 25, 2023 at 06:45:55AM -0400, PICCORO McKAY Lenz wrote: >this bug is not specific, the proble is that not all users report the >problems, just change the distro.. a normal tendency >in my case i downgrade to strecth and just works.. upgrading its not >always the right

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Sylvain Beucler
Hello Marc, On 25/08/2023 11:24, Marc SCHAEFER wrote: AFAIK is bullseye not yet LTS-handled. Will LTS fixes important bugs, or only security fixes? I reported this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043023 I have a local work-around (keep the buster version), and the

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread PICCORO McKAY Lenz
this bug is not specific, the proble is that not all users report the problems, just change the distro.. a normal tendency in my case i downgrade to strecth and just works.. upgrading its not always the right choose its pretty unconfortable that an important bug will be not solved just cos "its

Re: bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Roberto C . Sánchez
On Fri, Aug 25, 2023 at 11:24:18AM +0200, Marc SCHAEFER wrote: > Hello, > > AFAIK is bullseye not yet LTS-handled. > That is correct. This transition will happen in mid-2024. > Will LTS fixes important bugs, or only security fixes? > Generally speaking, the LTS team focuses only on fixing

bullseye / libgdbm6:amd64 is a catastrophgy

2023-08-25 Thread Marc SCHAEFER
Hello, AFAIK is bullseye not yet LTS-handled. Will LTS fixes important bugs, or only security fixes? I reported this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043023 I have a local work-around (keep the buster version), and the maintainer also proposed another local work-around.