On Tue, 4 Jun 2013 03:02:26 Holger Levsen wrote: > this bug is not fixed just because all versions are accidently in sync again, > instead, this needs to be ensured by a dependency.
I'm not convinced that "synfigstudio" needs vesrsioned dependency on exact version of "libsynfig0". Perhaps the real problem is how library mini-transition was handled. Upstream broke it and I uploaded "synfig" (library) and "synfigstudio" (GUI) in a way that "synfig" propagated to testing a bit earlier than "synfigstudio". The older version of "synfigstudio" in testing was effectively broken for few days until newer "synfigstudio" migrated. I agree that perhaps packages could benefit from tighter dependency. I committed .symbols file and "dh_makeshlibs -V" override [1] so when both packages will be rebuilt new dependency (calculated by `dh_shlibdeps`) will look like this: "libsynfig0 (>= 0.64.0)". However it won't save from potential breakage if future "libsynfig0" versions will be backwards incompatible with "synfigstudio". I think hard-coded dependency on exact version of "libsynfig0" is a bad idea. I'm not sure how to handle this bug. Perhaps I need advise on how to upload future updates to "synfig" package without breaking "synfigstudio"... Would it be a good idea to follow the usual transition procedure when the only one dependency package is involved to library update? [1]: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/synfig-synfig.git;a=commitdiff;h=4bbd2508f8ace12687e904015d15628ce63d79c1 Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B --- Good luck happens when preparedness meets opportunity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org