Comment 5 for bug 1919468

Hello Malte, thanks for this bug report and for providing some minimal steps to reproduce it. I could reproduce the issue you described and verified that it doesn't happen when using vbernat's PPA, as you stated. I checked the haproxy changelog for the 2.0 branch [1] and its full git history [2] hoping to find the fixing change, but I had no luck, hwever I did spot a number of commits that could possibly be relevant. I also checked the GitHub issue tracker [3] and the past Debian bugs for the haproxy package [4] but again with no luck.

If we want to to find a minimal fix to this bug to SRU I think we'll have to:

 - bisect across releases [3] by manually compiling each;
 - bisect across commits of the first fixed release
 - hope that the commit(s) fixing this have a clear and
   limited (= SRUable) scope.

However I'm not sure this is the best way forward. Looking again at the changelog [1] basically all the changes would be nice to ship. I'll check with the team to decide how to proceed, for the moment I'm setting the status of this bug to Confirmed.

[1] http://www.haproxy.org/download/2.0/src/CHANGELOG
[2] http://git.haproxy.org/?p=haproxy-2.0.git
[3] https://github.com/haproxy/haproxy/issues
[4] https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=unstable;package=haproxy
[5] https://www.haproxy.org/download/2.0/src/