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 users" is somewhat inconsiderate of others and
> shows a disregard for the rather robust process that we try to utilize
> to ensure that we properly balance the needs of everyone involved.
I don't think that's the claim, to be fair.
It's more:
Release gdbm version Status
----------- ------------- --------------
Buster 1.18 no pre-read feature
Bullseye 1.19 pre-read added, no way to disable it
Bookworm 1.20 reverted back to default behaviour,
added GBM_PREREAD to enable it
It's a regression in upstream, which upstream agreed with, and upstream
fixed it. The question is how to get the benefits to Bullseye users.
On Fri, Aug 25, 2023 at 01:41:36PM +0200, Christopher Huhn wrote:
> A backport of the bookworm package would be my way to go, I guess.
This is probably the easiest path, if someone can upload it to
debian backports for Marc.
- Chris
