Comment 11 for bug 1919468

Hi Simon,

The server team discussed this bug and we do agree the debdiff in this case looks good, and having a point release of haproxy for the stable release likely would bring many good fixes to users in addition to this particular one, even though it doesn't appear that those issues have been reported against ubuntu in launchpad, yet.

That said, process-wise for getting a SRU accepted and released, it will assuredly be faster to do it with the specific fix you identified in comment #6 (i.e. https://github.com/FireBurn/haproxy/commit/c6eedcceef97f6a5a03e2b8b35e32ec31470483c.patch; attached), at least as a first step. Utkarsh is interested in taking a shot at solving this bug in this fashion.

If you're interested, the specific process we will need to follow for getting the full point release in, is documented at https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases. There are four key points listed there that we will need to demonstrate proof for. Along with that, knowing how to reliably reproduce some of the other bugs mentioned in the v2.0.13 release notes on Ubuntu 20.04 would help in making the justification for its acceptance.