config: drop openssl from v2 ready since it does not work for 3.x version

[prince-chrismc]

Specify library name and version: lib/1.0

to unblock #15336

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[SpaceIm]

Actually #15336 changes both openssl 1.x.x & 3.x.x, and c3i should ensure that 1.x.x still work with conan v2

[jngrb]

OpenSSL 3.x.x is v2 ready in the sense that you can enable CONAN_V2_MODE on the cmake_find_package-based test package:

CONAN_V2_MODE=1 conan create . openssl/3.0.8@

builds successfully.

It is not v2 ready in the sense that you can consume OpenSSL 3.x.x with a CMakeDeps & CMakeToolchain-based recipe. That only works for OpenSSL 1.x.x for which a v2 test package using the new generators is already on the master branch.

The v2 test package with the new generators for OpenSSL 3.x.x and the fixed necessary to make it work will come with my PR #14426

I am not sure what the "c3i/conan-v2" CI tests for because I don't know the specifics and I cannot see results.

If it only runs the command above and does not make sure that the test package uses the CMakeDeps generator, this PR is not needed.

[SpaceIm]

openssl 3.x.x is not v2 ready because it just can't work with conan v2 client due to usage of conan python API removed in conan v2 library, and therefore it can't pass v2 pipeline (a recipe can be consumed with new generators, but it doesn't mean it's compatible with conan v2 client), that's what this conan_v2_ready_references.yml is tracking, to ensure that once a recipe passes v2 pipeline, a new PR cannot break it.
A test package relying on new generators is not sufficient, openssl 3.x.x must be fully migrated to conan v2.

[prince-chrismc]

OpenSSL 3.x.x is v2 ready in the sense that you can enable CONAN_V2_MODE on the

The variable does not actually change anything and only softly reports warnings. For example bad imports and not reported, it's very incomplete

The v2 pipeline runs the 2.0 client and does a conan create

[prince-chrismc]

I'd highly recommend taking a look at the logs posted by the bot if you want a detailed break down of all the different commands.

Conan 2.0 was released a few weeks ago and it's being used for CCI exclusively in its entirely for the v2 pipeline (aka there no v1 client)

[SpaceIm]

By the way, is this file updated regularly?

Its content is a little bit odd:

• many duplicated entries
• several recipes marked as ready references but with missing v2 packages
• many missing recipes for which v2 pipeline passed in recent PRs

(I've opened #16573)

[prince-chrismc]

AutoMerge is not running over config PRs :/

[prince-chrismc]

@SpaceIm @jwillikers @toge Can you please review? The auto merge is bugged with team reviews 🙏