Bug#1132468: libc6: pthread_cond_signal failed to wake up pthread_cond_wait due to a bug in undoing stealing

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?

Regards
Aurelien