This does not work with OpenSSL 3. Which is available since Fedora 36.
Hence we are abandoing it. Contrary we can support this stream in
older Fedoras until a scheduled EOL. Hence this patch obsoletes only
one context.
bug #2059997.
This document is valid, but the tests in this repository do not pass because they do not support obsoletes for a context:
Obsoletes:==========
INFO:root:obsoletes/perl-IO-Socket-SSL:2.068.yaml obsoletes are valid
ERROR:root:Module name/stream "perl-IO-Socket-SSL:2.068" doesn't match filename "perl-IO-Socket-SSL:2.068:7b91f26c.yaml"
Before merging to main and f36, we need to fix the tests and check pungi that it does not error.
The story is that I have perl-IO-Socket-SSL:2.068 in F34, F35, and F36. I want keep it supported in F34 and F35 until 2022-06-01, but I need remove it from F36 now because it does not work there. (I could ask relengs to untag it from a not-yet-released F36, and I will try that. But in general we should support this use case, so we should fix the infrastructure.)
This does not work with OpenSSL 3. Which is available since Fedora 36.
Hence we are abandoing it. Contrary we can support this stream in
older Fedoras until a scheduled EOL. Hence this patch obsoletes only
one context.
bug #2059997.
This document is valid, but the tests in this repository do not pass because they do not support obsoletes for a context:
Before merging to main and f36, we need to fix the tests and check pungi that it does not error.
The story is that I have perl-IO-Socket-SSL:2.068 in F34, F35, and F36. I want keep it supported in F34 and F35 until 2022-06-01, but I need remove it from F36 now because it does not work there. (I could ask relengs to untag it from a not-yet-released F36, and I will try that. But in general we should support this use case, so we should fix the infrastructure.)