Hi!
On Tue, 2018-06-26 at 23:08:48 +0200, Sven Joachim wrote:
> Package: timidity
> Version: 2.14.0-5
> Severity: serious
> In this version, timidity-daemon has become uninstallable:
>
> ,----
> | $ LANG=C aptitude -s install timidity-daemon
> | The following packages will be upgraded:
> | timidity{b} timidity-daemon
> | The following packages are RECOMMENDED but will NOT be installed:
> | fluid-soundfont-gm
> | 2 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
> | Need to get 676 kB of archives. After unpacking 49.2 kB will be used.
> | The following packages have unmet dependencies:
> | timidity : Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be
> installed
> | The following actions will resolve these dependencies:
> |
> | Keep the following packages at their current version:
> | 1) timidity [2.14.0-4 (now)]
> | 2) timidity-daemon [2.14.0-4 (now)]
> |
> |
> |
> | Accept this solution? [Y/n/q/?] q
> | Abandoning all efforts to resolve these dependencies.
> | Abort.
> `----
>
> Most likely you meant to break timidity-daemon (<= 2.14.0-1~) rather
> than (>= 2.14.0-1~).
I'm not sure that'd be correct either. From the bug that this was
supposed to fix (because the changelog description is not clear on
what was broken and what was the fix), this seems to be a new behavior
from timidity-daemon starting in that version, which does not play nice
when pulseaudio is also in the system, and both fight for exclusive
access to the sound devices.
But this seems to be both a (perhaps temporary) workaround (why not
instead try to diagnose why timidity-daemon now requires exclusive
access to the sound devices?), and in the wrong place (if the problem
is with pulseaudio, then either of the packages need to possibly Break
the other, but not between timidity and timidity-daemon, I for one do
not have pulseaudio on this particular system for example).
Thanks,
Guillem
