Closed danielhalati closed 1 month ago
Hi @danielhalati
Thanks for your question.
Quick question: Are you using any other arguments for conan install
of your package? Like any settings, profiles? Because those same arguments should be used for the conan lock create
command. Lockfiles in Conan 1.X are 1 lockfile for each different configuration (combination of profiles, settings, etc), so the dependency graph has to be computed with the same inputs as the conan install
would do.
I am using a custom profile. Does the conan lock create accept a custom profile?
Yes you should pass the same -pr=profile -s settings=value ...
arguments you would be using for conan install
.
It works now. many thanks
Happy to help!
What is your question?
Hello. I am trying to use conan 1.65.0 with revision enabled and to generate lockfiles
I found out a new package will be generated every time the contents change which is perfect. That's what I am expecting
This is how packages look inside Artifactory:
And then I have a simple requirements.txt file
AFAIK from the docs: https://docs.conan.io/1/versioning/revisions.html I am downloading the latest available package, which is again correct
The next step I want to do is to generate the lockfile:
conan lock create requirements.txt
This is the output generated:
The thing is that the package doesn't exist for some reason, but I've just downloaded it ...
I also tried placing some revisions inside requirements.txt but it doesn't seem to have any effect. How can I pick up a certain package inside artifactory manually?
Have you read the CONTRIBUTING guide?