Hi Julian,
Draft which may save you some time:
First patch against trunk:
[[[
* site/staging/faq.html:
Add entry for "An error occurred during SSL communication" error.
]]]
Second patch against trunk:
[[[
* site/staging/docs/release-notes/1.10.html:
Add entry for an OpenSSL upgrade causing "An error occurred during SSL communication" error.
]]]
Cheers,
Folker
On 2018-08-01 15:03, Julian Foad wrote:
> Folker Schamel wrote:
>> Hi Stefan,
>>> That's the catch here. Subversion does not ship with OpenSSL by
>>> itself. From Subversion's point of view this is a 3rd-party
>>> dependency. [...] It could be something worthwhile adding to the FAQ
>>> however, though then in a more general manner like: Troubleshooting
>>> Subversion SSL connection.
>> Good point.
>> The FAQ seems to be a good place.
>>
>> Nevertheless, in such situations we are probably not the only ones
>> looking primarily into the Subversion release notes, not so much into
>> the Debian documentation or Subversion FAQ, because the problem
>> seemingly was caused - in simple terms - by the Subversion update.
>> Also note that new releases of distributions of Subversion are
>> usually strongly correlated with new Subversion releases.
>>
>> So I still suggest to also put a warning in the Subversion release
>> notes, for example:
>> "Your distribution may also upgrade OpenSSL along with the Subversion
>> upgrade, which may cause trouble, see xxxx in the FAQ."
>> At least us it would have spared a lot of time ;-)
>>
>> Even if you may insist that this logically the "wrong" place,
>> sometimes a note in such a "wrong" place can be very helpful for
>> users who are looking in that "wrong" place, ;-)
>
> I agree -- when something like this hits users in real life, we should
> add it to the release notes, either in total or as a pointer to a FAQ.
> And I want to say thank you for writing a helpful description for
> other users to diagnose the problem after being troubled by it yourself.
>
> If no-one else volunteers, I will try to do it in the next day or two
> (but I haven't much time).
>
> - Julian
>
Received on 2018-08-01 17:52:12 CEST