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

Please remove the distro-info project. #589

Closed
verhovsky opened this issue Aug 31, 2020 · 2 comments
Closed

Please remove the distro-info project. #589

verhovsky opened this issue Aug 31, 2020 · 2 comments

Comments

@verhovsky
Copy link

https://pypi.org/project/distro-info/#history

distro-info is a Python tool used for upgrading Ubuntu. https://packages.ubuntu.com/groovy/distro-info

If you use the standard way of upgrading all pip dependencies (as far as I can tell, a bash command copy-pasted from stackoverflow https://stackoverflow.com/questions/2720014/how-to-upgrade-all-python-packages-with-pip is still the canonical way to do that) this causes pip to install distro-info which was uploaded to PyPI in 2013 and hasn't been used since which causes the Ubuntu do-release-upgrade command to break https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874250

I haven't actually verified this is what causes do-release-upgrade to break, but when I do sudo pip3 list --outdated --format=freeze | grep -v '^\-e' | cut -d = -f 1 | xargs -n1 sudo pip3 install -U I see

$ sudo pip3 list --outdated --format=freeze | grep -v '^\-e' | cut -d = -f 1  | xargs -n1 sudo pip3 install -U
Processing /root/.cache/pip/wheels/70/41/44/7433bd9e251aed01842961adf793059948d1de98d25877c5b8/distro_info-0.0.0-py3-none-any.whl
Installing collected packages: distro-info
  Attempting uninstall: distro-info
    Found existing installation: distro-info 0.0.0
    Uninstalling distro-info-0.0.0:
      Successfully uninstalled distro-info-0.0.0
Successfully installed distro-info-0.0.0
[...]
@pradyunsg pradyunsg transferred this issue from pypi/warehouse Aug 31, 2020
@pradyunsg
Copy link
Contributor

If you use the standard way of upgrading all pip dependencies (as far as I can tell

As a pip maintainer, I suggest not using commands like that because they'll certainly break your environment in weird ways. There's a reason pip doesn't have a pip upgrade-all command, and it's due to complexities around doing it properly. None of the answers on that question are robust enough to not break things. :)


IIUC, @paulproteus is the owner of that package -- perhaps they might have context to bring into this discussion.

@di
Copy link
Member

di commented Oct 12, 2022

I don't think users running unsupported workflows is grounds to remove what appears to be a legitimate package.

Furthermore, the distro-info project has gotten a new release as of Oct 2021, which might help with the breakage experienced here.

@di di closed this as completed Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants