Bug#863705: [Aptitude-devel] Bug#863705: aptitude: symbol lookup error: aptitude: undefined symbol:

2017-06-09 Thread Olly Betts
[Dropping aptitude@ as it doesn't allow non-subscriber messages] On Tue, May 30, 2017 at 10:57:06PM +0100, Olly Betts wrote: > I can try to fix the xapian-core version in backports, but that only > helps people with 1.4.1-1~bpo8+1 installed if they upgrade from > backports before trying to mix in

Bug#863705: [Aptitude-devel] Bug#863705: aptitude: symbol lookup error: aptitude: undefined symbol:

2017-05-30 Thread Olly Betts
So if I understand the issue correctly, it's that libxapian30 in unstable is built with the new C++ ABI while libxapian30 in backports was built with the old C++ ABI, so really should have been libxapian30v4 or something (not sure if there's a reverse convention to the v5 suffix)? Sorry for not

Bug#863705: [Aptitude-devel] Bug#863705: aptitude: symbol lookup error: aptitude: undefined symbol:

2017-05-30 Thread Axel Beckert
Hi Sven, Sven Joachim wrote: > Control: reassign -1 libxapian30 1.4.1-1~bpo8+1 I wouldn't be so quick with reassigning. > > aptitude: symbol lookup error: aptitude: undefined symbol: > > _ZNK6Xapian8Database14postlist_beginERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE > > This