Packaged libs are still under 3.8 folder

[rzvoncek]

Hello. We're using dh-virtualenv to package cassandra-medusa, a Cassandra backup tool.

I've found out recently Github is phasing out GHA runners of Ubuntu 20.04, so I have to modernise our CI. Part of this caused Python 3.8 not being present anymore. As I'm just finding out, it EoLed. Instead, we have 3.10 now.

Anyhow, the package builds, but the libs get placed in a wrong place, under a 3.8 path. For example:

/usr/share/cassandra-medusa/lib/python3.8/site-packages/pssh/clients/common.py

I've tried several things already, but none of this helped.

Could you please help me figure out how to make the libraries go to the correct place?

[rzvoncek]

I've gained some insight now. I found out that passing Ubuntu distro code name into the our build process dictates where will the libraries end up. After replacing focal with jammy, things started to look like I need them to.

I'm still stuck with the packages under python3.10 folders, with not much control over it, but at least I'm not blocked now.