On Mon, May 22, 2023 at 11:59:37AM +0200, Andreas Beckmann wrote: > On 19/05/2023 12.48, Martin Hostettler wrote: > > It seems what is needed is this: > > > > mv > > debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components > > debian/cadabra2/usr/share/javascript > > rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static > > rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook > > > > (The wildcards are used to avoid hard coding the current debian default > > python version) > > Does this still work if there is more than one supported python version > (during python transitions)? It's probably OK to to break support for > multiple python versions now (as we currently only have one and stable > releases only have one), but this may need to be revisited for bookworm+1. >
As this is in the temporary directory where the build code is installed i would suspect this will work with more supported python versions as well. I think this is just a case of the upstream build system including the python version of the python version used to build the package. (i think usually debhelper takes care of removing that, but this is before any of that runs) At least as long as the code there is compatible with all supported python versions in debian. But i don't know anything for certain, as i don't know cadabre but just want to help solve RC bugs against packages i use (like python3-notebook) - Martin
