reinstall-all don't use the initial spec but install latest version of each packages
See original GitHub issueDescribe the bug
When using the command pipx resintall-all the packages are uninstalled and installed again but without taking into account the spec used during the initial installation. it’s mean it reinstall only latest version for each packages.
How to reproduce
pipx install --suffix=1010 poetry==1.0.10 will install poetry 1.0.10
pipx reinstall-all will install poetry 1.1.3
Expected behavior The initial spec should be reused during reinstall-all or at least give an option to choose to have latest versions or initial versions.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
python - Conda install and update do not work also solving ...
1) I cannot use conda install for any package. It will give me the error in solving environment list this: failed with initial...
Read more >Troubleshoot Visual Studio installation and upgrade issues
This troubleshooting guide includes step-by-step instructions that should resolve most installation issues.
Read more >Install or update packages - AWS Systems Manager
Scheduling a package installation or update (console) · Uninstall and reinstall: The package is completely uninstalled, and then reinstalled. · In-place update: ...
Read more >pip install - pip documentation v22.3.1
Ignore the installed packages, overwriting them. This can break your system if the existing package is of a different version or was installed...
Read more >DNF Command Reference — dnf latest documentation
`DNF`_ is the next upcoming major version of `YUM`_, a package manager for RPM-based Linux ... To persist the packages, use the download...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Can you point me where the specifier is removed from the metadata. I can try to work on a fix.
Ok I found the reason. Exit code is 1 after a version bump. Exit code 0 is when package is already at latest version.