Archlinux package management strategies: Difference between revisions
From wikinotes
(Created page with "The painful parts of arch are mostly related to libraries: * python updates take a while to reach all packages (so they get installed to the wrong site-packages) * libva updates may be too new for makemkv etc * qt updates are sometimes problematic as well To mitigate this, I've been exposing old versions of the libraries to my package-repo * ex. installing python-311 when python-3.12 became default") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
To mitigate this, I've been exposing old versions of the libraries to my package-repo | To mitigate this, I've been exposing old versions of the libraries to my package-repo | ||
* ex. installing python-311 when python-3.12 became default | * ex. installing python-311 when python-3.12 became default | ||
= Python Upgrades = | |||
<blockquote> | |||
See [[pacman troubleshooting]]. | |||
TL;DR rebuild all python AUR packages, and reinstall. | |||
</blockquote><!-- Python Upgrades --> | |||
Latest revision as of 17:10, 11 May 2024
The painful parts of arch are mostly related to libraries:
- python updates take a while to reach all packages (so they get installed to the wrong site-packages)
- libva updates may be too new for makemkv etc
- qt updates are sometimes problematic as well
To mitigate this, I've been exposing old versions of the libraries to my package-repo
- ex. installing python-311 when python-3.12 became default
Python Upgrades
TL;DR rebuild all python AUR packages, and reinstall.
