On Mon, Dec 29, 2014 at 4:02 AM, Fabian Greffrath <fab...@greffrath.com> wrote: > > Am Sonntag, den 28.12.2014, 16:52 +0400 schrieb Stepan Golosunov: > > mplayer2 2.0-554-gf63dbad-1+b1 no longer starts after upgrading > > libdvdnav4 from 4.2.0+20120524-2 to 5.0.1-1: > > This is the mplayer2 package from stable and the libdvdnav4 package from > testing. Generally, partial upgrades are not supported, but ...
Partial upgrades are very much supported. Otherwise we wouldn't bother with dependencies so much. That does not mean every possible combination is supported. Just that apt should not leave your programs unusable. > > > % mplayer > > mplayer: error while loading shared libraries: libdvdnavmini.so.4: cannot > > open shared object file: No such file or directory > > ... since this specific issue gets reported every now and then, and it > has also been reported that adding a libdvdnavmini.so.4 -> > libdvdnav.so.4 symlink will fix it. So, shouldn't we just add this link > to the libdvdnav4 package and be done with it? The maintenance burden > will be a single line in debian/links and the gain would be better > upgrade robustness (for an otherwise unsupported scenario, though). Or > are there any objections against this way of "support" for a deprecated > interface? I would instead add a Breaks: mplayer2 (<< X) on libdvdnav, to force upgrade of mplayer2 alongside libdvdnav. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
