Control: severity -1 important Hi,
Ralf Jung wrote (28 Oct 2014 09:38:10 GMT) : > I just upgraded pidgin-otr on my testing system. Then pidgin fails > to start, saying Expected libotr API version 4.1.0 incompatible with > actual version 4.0.0. Aborting. Thanks for reporting this bug to us. > I had to upgrade libotr5 to the current unstable version to fix this. > Obviously, the > dependencies are not tight enough. Right. The root cause of the problem was in libotr itself, and has been fixed (short-term: #767230; long-term: #767652) in 4.1.0-2, which is now in sid, has been unblocked by the release team, and should then migrate to testing in 10 days. Given this, pidgin-otr will automatically pick up the right versioned dependency on libotr next time it is rebuilt. Also, libotr 4.1.0-1 has now migrated to testing, so this bug should not be an issue in practice (since libotr5 didn't exist in Wheezy, so partial upgrades are not a problem for Wheezy->Jessie upgrades). Hence, I'm downgrading the severity of this bug. The only remaining problematic case I can think of is partial upgrades from Wheezy + backports to Jessie, with pidgin-otr being upgraded but libotr being kept at the version that's currently in wheezy-backports. To address this potential problem, I'm going to upload libotr 4.1.0-2 to wheezy-backports soon after it reaches testing. Once this is done, I'll close this bug, as all real-world issues it may trigger will have been solved in some way. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
