Package: release.debian.org Severity: normal X-Debbugs-Cc: jac...@packages.debian.org, python-defau...@packages.debian.org
src:dbus-python version 1.2.16-3 removed the Python 2 binary package, python-dbus. Its migration is blocked by src:jackd2: the version in bullseye Depends on python-dbus, and the version in sid has a grave bug open (#965308) with a user reporting that jackd won't start (with some rather confusing debug information in which the user seems to have encountered two entirely different failure modes at different times). I attempted to reproduce jackd's failure to start, and could not reproduce it (but I don't use jackd myself and don't really know how, so perhaps I'm holding it wrong). I've pinged the multimedia team but so far have not managed to get either a regular jackd user confirming that it's broken, or a regular jackd user saying it works for them. Possible ways forward that I can see: * reinstate python-dbus (but don't run its regression tests, because those need python-gi, which has already gone away) - by now this is likely to need a trip through NEW * downgrade #965308 or mark it bullseye-ignore, on the basis that it's unreproducible and quite possibly local misconfiguration Do the release team have a preference, or any other ideas? If a RC bug is filed against dbus-python for not migrating in a reasonable time, I am not going to be able to fix that bug, other than by taking one of the actions above (unless someone has another idea). Thanks, smcv