-
Notifications
You must be signed in to change notification settings - Fork 18
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
how can I change the default lock file version? (PACMAN-995) #76
Comments
Hi @mksafavi I can help provide a workaround: if you want to set the lock version to 1.0. You need to downgrade idf-component-manager to 1.x. pip install "idf-component-manager<2" could you help share the full file path which is being modified in the official docker image? We could see what we can do. |
Oh! It makes sense now. I thought the new It seems like my distro is shipping different versions. So the issue isn't from here ✌️ I looked in the esp-idf repository and the requirement.txt files don't contain the version limits. The docs mentioned that they are stored in espidf.constraints.*.txt. Is this file available in the Github repository? Thank you! |
@mksafavi you may download the constraint files here: https://dl.espressif.com/dl/esp-idf/espidf.constraints.v5.3.txt
|
Thanks 👍 |
The Component Manager version
2.0.2
ESP-IDF Version
v5.3.0
python Version
3.12.4
Operating System
Linux
Browser (for https://components.espressif.com Issues)
No response
Description
After updating IDF to version 5.3, the
dependencies.lock
schema version changed to2.0.0
.It modified the
dependencies.lock
like changing service_url to registry_url and so on.... which is fine, but on the official docker image, it still uses the first version schema and reverts the file back. I noticed this when my build pipeline added-dirty
to the versions.I couldn't find the documentation on how to set the lock version.
Manually changing 2.0.0 to 1.0.0 gives this warning:
So I assume there is a way to set this?
To Reproduce
Expected behaviour
setting the default lock version.
Additional info
No response
I have checked existing issues and online Documentation
The text was updated successfully, but these errors were encountered: