There seems to be broad support for a 1.1.1f release. Unless I hear an OMC objection I will formally announce this tomorrow.
Matt On 27/03/2020 00:10, Viktor Dukhovni wrote: > On Thu, Mar 26, 2020 at 11:33:40PM +0000, Matt Caswell wrote: > >> On 26/03/2020 23:15, Viktor Dukhovni wrote: >>> On Thu, Mar 26, 2020 at 09:13:32PM +0100, Bernd Edlinger wrote: >>> >>>> we got into this situation because everything moves so quickly, >>>> why does everyone here think we should move even faster now? >>>> >>>> What is the reason for this? >>> >>> We've published a bug-fix release (1.1.1e) that's liable to cause more >>> problems than it fixes. In such cases a closely-timed "fixup" (oops) >>> release is expected. One that only reverts the (two) problem >>> EOF-handling commits. >> >> Actually a partial revert of one of them is sufficient to resolve the >> problem. > > Yes, probably so. I took a sledge-hammer to the problem, and since the > second commit depended on the first, I reverted both. If you leave > the pre-requisites for the second commit in place, and just remove > the changed error handling, then indeed that may also work. >