Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] openssl version conflict, even with override=True #13519

Closed
AtnNn opened this issue Mar 23, 2023 · 4 comments · Fixed by #13597
Closed

[bug] openssl version conflict, even with override=True #13519

AtnNn opened this issue Mar 23, 2023 · 4 comments · Fixed by #13597
Assignees
Milestone

Comments

@AtnNn
Copy link

AtnNn commented Mar 23, 2023

Environment details

  • Operating System+version: Windows 11
  • Compiler+version: N/A
  • Conan version: 2.0.2
  • Python version: 3.11

Steps to reproduce

Given a project that requires openssl 1.1.1.t and also transitively 1.1.1s:

from conan import ConanFile
class Mwe(ConanFile):
  def requirements(self):
    self.requires("grpc/1.50.0#d2c60eb68fdeae68328741258897b5c8")
    self.requires("openssl/1.1.1t#7d9fc949345908e1b8609d9d9f528a08")

With it, I can reproduce the error from #13368. It looks like Conan can't order these version numbers.

$ conan lock create .
ERROR: Version conflict: grpc/1.50.0->openssl/1.1.1s, ->openssl/1.1.1t.

Changing the last line to

    self.requires("openssl/1.1.1t#7d9fc949345908e1b8609d9d9f528a08", override=True)

Causes conan lock create . to succeed, but then

$ conan graph info .
ERROR: Requirement 'openssl/1.1.1s' not in lockfile

Is this a bug? What is the proper way to depend on a different version of openssl? Thanks!

Logs

No response

@memsharded memsharded self-assigned this Apr 2, 2023
@memsharded memsharded added this to the 2.0.3 milestone Apr 2, 2023
@memsharded
Copy link
Member

Thanks very much @AtnNn for the detailed report, it helped to reproduce the issue.
It was indeed a bug in lockfiles, I am proposing #13597 to fix it, hopefully for next 2.0.3 release

@memsharded memsharded modified the milestones: 2.0.3, 2.0.4 Apr 3, 2023
@memsharded memsharded modified the milestones: 2.0.4, 2.0.5 Apr 11, 2023
@memsharded
Copy link
Member

#13597 finally merged, it was more challenging than expected, it will be in next 2.0.5

@AtnNn
Copy link
Author

AtnNn commented May 4, 2023

Thanks! I've verified that my issue is fixed in 9dd1257.

@memsharded
Copy link
Member

Fantastic, thanks for checking it @AtnNn !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants