Patch to fix async_ssl build

[raphael-proust]

DO NOT MERGE: wait until the CI succeeds, then merge ocaml/opam-source-archives#34, then change the URL for the patch, then merge

[mseri]

I have merged the patches before checking this, sorry

[mseri]

But the build of async_ssl is fine on the whole matrix, there are only a few ssl issues that are unrelated as far as I can see

[raphael-proust]

CI failures are:

• linting errors that pre-date this fix
• some ssl issues on fedora which seem unrelated to this fix
• a core_unix issue on windows (probably needs an available: os != "win32" added to core_unix.v0.17.0)

AFAICT, this is good to merge.

[mseri]

Should we make this a patch -1 release instead? Or it will mess up with strict versioning of some packages?

[raphael-proust]

Or it will mess up with strict versioning of some packages?

How so? I guess I can make a script that would break with this update, but I'm not sure there are standard tools around opam that would break.

But yeah, we might as well fix it just in case. Question is: should we mark the unpatched package as not available because it's broken several plateforms?

[mseri]

What I mean is if there are janestreet packages with version v0.17 requiring async_ssl with the =version flag. In this case I think we should merge as is, if not, I think we should merge a -1 patch. In the latter case I would not mark anything as unavailable because there could be still people happyly using them which do not need or want to move to the new one.

(This all in the spirit of path to the least breakage/change, it will change once the new maintainership policy is in place)

[raphael-proust]

I see. Done, it's now a patch version (which makes sense because it's a patch I guess).

[mseri]

Tests have already run, the lint and many tests have already passed

[mseri]

Thanks