On Tue, Apr 12 2022, Nicholas D Steeves wrote: >> This also requires that shiboken2 should be currently rebuilt. >> > > Agreed. > >> Either the python3 dependency should be tightened, or FORCE_LIMITED_API >> should be used. > > These are not the only available options. Are you aware of binNMUs? > https://wiki.debian.org/binNMU
I'm using it for development, and not being able to work if the minor version changes is a bigger problem than it sounds: I cannot rebuild third-party software which is using shiboken/pyside unless I completely rebuild pyside in parallel. I remember I already had this issue with the 3.9 transition. IMHO if shiboken2 is tied to the minor version, it should depend on the minor version as well so that the whole pyside/shiboken2 so that transitions and downstream dependencies will also be handled as part of the transitions? For example, the current situation is probably breaking packages which are currently build with shiboken. This makes shiboken2 completely useless if you have more than a one minor version of python installed (for example during transition periods). shiboken2 will work only for _one_ minor version. I actually don't use shiboken2 _directly_ myself, but is there any real drawback to build with FORCE_LIMITED_API ?
