-
Notifications
You must be signed in to change notification settings - Fork 3k
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
empty transition packages don't seem to work on upgrades #4961
Labels
state: needs discussion
This needs some more discussion
type: enhancement
Improvements to functionality
Comments
this seems to be a order issue, the new package with the shared files is installed before the other one is removed - that way |
terceiro
added a commit
to Linaro/squad
that referenced
this issue
Jan 9, 2018
msgpack was renamed from msgpack-python. msgpack-python became an empty transition packages that depends on msgpack, but on upgrades the actual code files are removed. See: pypa/pip#4961
encukou
added a commit
to encukou/pyldap
that referenced
this issue
Mar 27, 2018
See pip bug #4961: pypa/pip#4961 Discussion: pyldap#148
This was referenced Jan 30, 2019
This may be a use case considered for #988, assuming that encompasses the eventual installation order of resolved packages. |
chrahunt
added
state: needs discussion
This needs some more discussion
type: enhancement
Improvements to functionality
labels
Jul 21, 2019
triage-new-issues
bot
removed
the
S: needs triage
Issues/PRs that need to be triaged
label
Jul 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
state: needs discussion
This needs some more discussion
type: enhancement
Improvements to functionality
Description:
msgpack-python
was recently renamed to justmsgpack
. To ease upgrades, the msgpack maintainers uploaded a new version ofmsgpack-python
which is empty and depends onmsgpack
. However, when you do the upgrade, it seems that the upgrade ofmsgpack-python
removes the files that should now be provided bymsgpack
.I am not sure whether this is a feature or a bug, but it makes it impossible to provide transition packages to ease upgrades when renaming a package.
What I've run:
The text was updated successfully, but these errors were encountered: