Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Python upgrade leading to problems with aws-cli-v2 (Read 291 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Python upgrade leading to problems with aws-cli-v2

Hello,

I have upgraded my system to the latest version, with the usual  "pacman -Syu". Now, the "aws-cli-v2" package is broken, because this particular package installs its module files in /usr/lib/python3.10/site-packages/awscli/, but the python package just got upgraded to 3.11, so the python interpreter doesn't search for its modules within the /usr/lib/python3.10 tree.

In contrast, in the debian package, the module files are placed in /usr/lib/python3/dist-packages/awscli/, which does not create a problem with minor python version upgrades.

Maybe we should place python modules in such a place, where a minor python version upgrade does not cause trouble with installed python packages ?

Thanks,
bed

Re: Python upgrade leading to problems with aws-cli-v2

Reply #1 –
aws-cli-v2 is not in the artix repos.
Does it come from arch?

Re: Python upgrade leading to problems with aws-cli-v2

Reply #2 –
Quote from: artoo – on
aws-cli-v2 is not in the artix repos.
Does it come from arch?
Yes, I did not realize this package was from arch. The problem I had was related to arch deprecating the community repo. Now this problem is fixed.

But still, except for a few python modules related to a particular python minor version, it seems a waste of resources to build python packages for a specific minor version. This leads to a need to rebuild python packages for every minor version, which in turn leads to users having to download all those packages for a minor python version upgrade. This is a waste of build time and mirror bandwidth.

This problem is not artix specific and is also a problem for arch packages, from what I gather. I'm new to arch/artix PKGBUILD system, so I don't know how to address this, but maybe there is a solution for both arch and artix that could work, to put python module in a minor version agnostic path, for the vast majority of python packages that don't depend on a particular minor version

Re: Python upgrade leading to problems with aws-cli-v2

Reply #3 –
That need to recompile packages e.g. version 1.0.0-2, 1.0.0-3 etc. actually doesn't happen too oftenly, and is most likely a coincidence at the moment, cause with modular stuff like python/qemu/etc they need to be done a few times and appears as many packages. Many, but small in overall size.
The "problem" itself can't be addressed by rolling distros. If you insist on using a rolling distro and you're bothered by lib. stuff then link them, or use a chroot, or container.