Probably unrelated but FYI, do you realize that you have circular (runtime) dependencies across two different source packages? That is a common cause of headaches but I can't say for certain it's forbidden.
In unstable, one currently has pyinstaller-hooks-contrib:all=2026.6-1 (from src:pyinstaller-hooks-contrib) Depends on pyinstaller:all (from src:pyinstaller) pyinstaller:all Depends on python3-pyinstaller:any (>= 6.19.0+ds-2) python3-pyinstaller:any [which is only built for a few architectures in practice] Depends on pyinstaller-hooks-contrib:all I see at https://salsa.debian.org/python-team/packages/pyinstaller/-/commit/f95217c33516c24aad8c082e5c0712990c9157ab?file_path=debian%2Fcontrol that your intention was for the last relationship to be merely a Recommends, but the packages in the archive show it's actually a Depends. This is presumably because pyinstaller-hooks-contrib is working its way into the ${misc:Depends}, ${python3:Depends}, or ${shlibs:Depends} substvars somehow. When a package is in both Depends and Recommends like this, Debhelper will automagically remove the latter as part of its tidying up, so this is why the Recommends field totally vanishes. If this could be fixed the cycle would be broken. P.S. Your package has added Build-Depends on PyQt5 WebEngine for tests in https://salsa.debian.org/python-team/packages/pyinstaller/-/commit/bdabef84cd560cb717c716b6791486124ec629ab I can see you're well aware of the dire situation of supporting Qt WebEngine security-wise https://bugs.debian.org/1057755 but the Qt 5 version appears to have not had an upstream commit in over a year. To help its eradication, I'm sure dropping the Build-Depends would be appreciated by those folks. https://bugs.debian.org/1099772#10 https://bugs.debian.org/1140142#5
signature.asc
Description: This is a digitally signed message part
