[Pkg-mutt-maintainers] Bug#839813: mutt depends on libxapian22v5 which is for autoremove on testing today

[Gregor Zattler]

Hi Elimar,
* Elimar Riesebieter <riesebie at lxtec.de> [07. Okt. 2016]:
> * Gregor Zattler <telegraph at gmx.net> [2016-10-07 00:18 +0200]:
>> * Elimar Riesebieter <riesebie at lxtec.de> [06. Okt. 2016]:
> [...]
>>> What tells
>>> $ ldd $(which mutt) | grep xapian?
>> 
>> libxapian.so.22 => /usr/lib/x86_64-linux-gnu/libxapian.so.22 (0x00007f7f4d900000)
> 
> On my systems mutt 1.7.0-6 should have been build against
> libxapian-dev 1.4 which let mutt point to:
> 
> libxapian.so.30 => /usr/lib/i386-linux-gnu/sse2/libxapian.so.30 (0xb680e000)
> libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 (0x00007f9790569000)
> 
> From where did you get the mutt package? Did you compiled it by
> your self?

This is mutt-1.70-6 from testing repository but I compiled
notmuch myself and this was the reason fro the wrong library
version (don't ask me why.  Since I updated notmuch

$ ldd $(which mutt) | grep xapian
        libxapian.so.30 =>
        /usr/lib/x86_64-linux-gnu/libxapian.so.30
        (0x00007fad41a27000)


I discovered this by purging libxapin22v5, not beeing able to
start mutt any more, trying to compile mutt myself which failed,
installing libxapian22 form jessie backports, mutt then does not
start with symbol not found message which point to notmuch ....

Thanks, gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-