23.04.2022 11:28, Michael Tokarev wrote: ...
This also fixes a *sporaric* (rare) broken build which actually happened with previous security update: #1006935, #1009855, #1002059
The #1002059 slipped there by a mistake. It is a different problem, most likely a misconfiguration on the OP side. So I had to remove mention of this bug# from the changelog. The rest of it is okay. Please excuse me for the extra noise. There's just too many bugs - still open and being closed by this update too. Thanks, /mjt
