[Python-modules-team] Bug#911904: Processed: block 911904 with 911915

[Ondřej Surý]

Also libtidy5deb1 doesn’t have libtidy.so, just libtidy.so.5deb1 and libtidy.so.5deb1.0.0. It worked before because there was fallback to libtidy.so.5 in LIBNAMES. But now instead of whacking the new SONAME into the package every time it changes, you should solve it once and forever to resolve SONAME from libtidy-dev package and depend only on runtime library package.

Sorry for multiple emails, I am on my phone on the move...

--
Ondřej Surý <ondrej at sury.org>

> On 26 Oct 2018, at 13:49, Michal Čihař <nijel at debian.org> wrote:
> 
> Hi
> 
>> On Fri, 2018-10-26 at 10:51 +0200, Ondřej Surý wrote:
>> LIBTIDY_LIBRARY=$(shell readlink -f
>> /usr/lib/$(DEB_HOST_MULTIARCH)/libtidy.so)
> 
> Well it all started from this file being absent from the package :-)
> 
>> LIBTIDY_PACKAGE=$(shell dpkg-query --search $(LIBTIDY_LIBRARY) | cut
>> -f 1 -d :)
>> LIBTIDY_LIBRARY_FILE$(shell basename $(LIBTIDY_LIBRARY))
>> 
>> then
>> 
>> sed -e “s/libtidy.so/$(LIBTIDY_LIBRARY_FILE)” lib.py
>> 
>> echo libtidy:Depends=$(LIBTIDY_PACKAGE) > python-utidylib.substvars
>> 
>> and replace
>> 
>> libtidy5deb1 | libtidy5,
> 
> I don't get what this would solve - there is nothing wrong with
> alternate dependecies as long as they both provide libtidy.so. Anyway
> same is in Build-Depends as well, where substvars are not really
> helpful.
> 
> -- 
>    Michal Čihař | https://cihar.com/ | https://weblate.org/
>