Bug#968917: marked as done (release.debian.org: dbus-python without python-dbus not migrating to bullseye)
Your message dated Mon, 24 Aug 2020 10:48:31 +0200
with message-id <efa7605f-f4f5-6f65-71fc-6d8a7a42b873@debian.org>
and subject line Re: Bug#968917: release.debian.org: dbus-python without python-dbus not migrating to bullseye
has caused the Debian Bug report #968917,
regarding release.debian.org: dbus-python without python-dbus not migrating to bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
968917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968917
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: jackd2@packages.debian.org, python-defaults@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
--- End Message ---
--- Begin Message ---
On 23/08/2020 23:20, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: jackd2@packages.debian.org, python-defaults@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
I don't think it would need a trip through NEW yet, as the old python-dbus
binaries are still around in sid, so the overrides are likely to still be
present, though I could be wrong.
>
> * 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?
Another option would have been to remove jackd from testing.
However I see that the bug has already been downgraded and dbus-python has
migrated, so we're good. Let's close this.
Cheers,
Emilio
> 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
>
--- End Message ---
Reply to: