Hi, thanks for your response; if I manually update all libpj* to 2.5.5~dfsg-3, it works.
> Yes and no. You seem to be running a weird mixture of old and new > versions of the pjproject libs > > > ii libpj2 2.5.5~dfsg-3 > > ii libpjlib-util2 2.1.0.0.ast20130823-1 > > ii libpjmedia-audiodev2 2.1.0.0.ast20130823-1 > > ii libpjmedia-codec2 2.1.0.0.ast20130823-1 > > ii libpjmedia-videodev2 2.5.5~dfsg-3 > > ii libpjmedia2 2.5.5~dfsg-3 > > ii libpjnath2 2.5.5~dfsg-3 > > ii libpjsip-simple2 2.1.0.0.ast20130823-1 > > ii libpjsip-ua2 2.1.0.0.ast20130823-1 > > ii libpjsip2 2.1.0.0.ast20130823-1 > > ii libpjsua2 2.1.0.0.ast20130823-1 I have just used "aptitude install python-pjproject", and it installed the above packages. > I assume when you update all libs to the same release it will work. Yes. > I think python bindings should depend on the libs of the same version. > I'll have a look on how to code this dependency into the package. But I > don't agree that this is a grave bug. Ok, so this probably just appears when using Debian stable plus some testing-packages. thanks, Roland