Bug#981838: fixed in mplayer-blue 1.13-2
> mplayer-blue (1.13-2) unstable; urgency=medium
>
> * debian/control: Add missing dependency on mplayer-gui (Closes: #981838)
Is there a circular dependency now?
mplayer-gui depends on mplayer-skin = mplayer-skin-blue which depends on
mplayer-gui.
Since the user should only install skins matching their mplayer-gui, it's
probably necessary to replace the dependency on mplayer-skin in mplayer-gui
with a recommendation, right?
It is unpleasant that it is possible to install mplayer-gui without a skin
then (which gives a related error message at startup), but without the
dependency in mplayer-skin-blue the user does not know at all which skin
version is suitable for their mplayer-gui.
Or is there another way to ensure the mutual dependency?
Reply to: