Hi,
On Sun, 2026-05-31 at 23:44 +0200, Aurelien Jarno wrote:
> Hi,
>
> On 2026-05-17 00:54, Florian Bezdeka wrote:
> > Hi Aurelien,
> >
> > On Mon, 2026-04-13 at 00:13 +0200, Aurelien Jarno wrote:
> > >
> > > Yes, packages go through -proposed-updates before going to (old-)stable
> > > for a point release. But far less people are using that than testing, so
> > > I am not sure about the coverage we'll get. But if we decide to apply
> > > the patch series, we need to do that just after the point release to
> > > increase the testing time and the chance to catch issues.
> >
> > The point release (12.14) has been released a couple of days ago. Sadly
> > we did not get any further comments / input / feedback regarding this
> > issue. How do we proceed now?
>
> On my side, I still not sure how to get this patchset properly tested,
> especially
> for the db5.3 case. The only option I see is to get the package into
> stable-proposed-updates, ask users to test it and cross our fingers that
> any issues are detected before the point release. But that's not feel
> very comfortable though.
>
> > Our tests are still ongoing, all looking good so far. No additional
> > issues came up. I would love to increase the test coverage and to move
> > forward, but options seem limited.
>
> Great. Have your tests covered the db5.3 case as well?
Nope, for the following two reasons:
- I'm not sure what exactly needs to be patched into db5.3 to "fix" it.
Seems there are two fixes needed:
a) The initializer of glibc, so you have to rebuild against a
"fixed glibc". Covered by the glibc patch series. Done.
b) Something named re-initialization patch and seems to be available
via [1], taken from the upstream glibc bug report.
- Even if I would be able to "fix" or patch the db5.3 package I have no
idea how to make sure that the problem is gone. For the glibc issue
I have two reproducers (available via upstream bug report) and
our own application. For db5.3 I'm missing something similar.
[1]
https://gitlab.com/redhat/centos-stream/rpms/libdb/-/blob/c9s/db-5.3.28-condition_variable.patch?ref_type=heads
