-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Unable to lock previously locked packages #5843
Comments
What is including I do apologize for this issue you are experiencing, it is definitely caused by the refactor to move away from requirementslib in order to fix issues with file and remote installs with extras and other edge cases. We will work towards a patch of this in the coming week. Just to recap, I think the first thing to fix is supporting a Pipfile entry without a revision, and then to explore the case of a vcs Pipfile entry being just a string. |
Hi, I did checked out your fix and it worked smoothly!🤩 |
Just cut release |
Hey @matteius, I managed to reproduce the error again...🙂 Here is what happened... Now I am playing with
Also I have the following entry in piplock from the previous installs
and my pipfile have the following entry in Now I am trying to install one of my private library
If it helps, my private library was build using poetry with the following entry in
|
This happens with our team 50% of the time running |
I was tinkering around the latest pipenv version
2023.8.20
and had trouble moving from2023.7.23
. It seems this version is not backwards compatible.Issue description
Unable to lock previously locked versions
Expected result
Lock to be completed as previous version
Actual result
Locking failed!
Steps to replicate
I really doubt if this information could help to debug the issue! 🙊
My attempt to debug
I have the lock file which was build using
2023.7.23
, now I am trying to deploy it using2023.8.20
checking the lock file, I found the following line
Hmmm!... Then let me re-install
retry-extended
with versionUgh! Let's retry with old pipenv version
Success!!.... Heh! So the lock was actually possible!!
Now the lock file is updated as follows
OK. It seems the issue might have resolved. Let me deploy using the new pipenv
Ops!. Should I do the same with
python-zeep
??? but this dependency is from one of my private libraryWhat is happening here? Any help?
The text was updated successfully, but these errors were encountered: