tags 418843 pending thanks On Thursday 12 April 2007 10:37, Kim Hansen wrote: > It looks like it should depend on libccrtp1-1.5-1 instead.
Kim, This is fairly normal for the unstable distribution, especially during a library transition. (See apt-get below) The version of twinkle in unstable (1:1.0-2) does actually depend on libccrtp1-1.5-0, which you can get from the stable or testing distribution. As a work around if you include the testing distribution in your sources.list, then you should be fairy immune to library transitions. What needs to happen is twinkle in unstable needs to be rebuilt binNMU [1] against the current versions of libraries in unstable, once the transitions for libcommoncpp2 and libccrtp, libzrtpcpp are complete. Mark [1] http://wiki.debian.org/binNMU d620:~# apt-get install twinkle Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies. twinkle: Depends: libccrtp1-1.5-0 but it is not installable Depends: libzrtpcpp-0.9-0 but it is not going to be installed E: Broken packages
pgpBmvPwdbGSj.pgp
Description: PGP signature