i believe was secipola how first mentioned this possibility (and since then i have refer to it a few times): -what happened here is caused by using the latest/incoming update-packs (which are frozen snapshots of the main debian repo) and tracking directly debian-multimedia.
one day debian-multimedia would update a pkg, with a lib v. recommend still not available in the frozen pack.
now how to solve this:
- wait until the next update-pack, main debian will be put up-to-date and the unsolved dependencies, solved (this waiting has the advantage, imho, of not messing with the sources.list - if one picked latest, is seeking some stability, not jumping forward and back in the sources.list will keep the system stable)
- if really annoys you to have a hold pkg for a few days/weeks, make a quick jump to testing and solve it;
- in the long run, debian-multimedia should be also mirrored in the update-packs
[ bliss of ignorance