Dependency to libpython3.4m.so.1.0 causes RPM validation fail
I need to use pycrypt in my application but since it has some binary libraries which are dependent on libpython3.4m.so.1.0, RPM validation fails.
Would it be possible to make libpython3.4 to be one of the allowed libraries? If not, what are my alternatives to include pycrypt into my application? I cannot use pure python implementations such as pyaes since they are simply too slow.
libpython3_4m1_0 package which provides libpython3.4m.so.1.0 is available on sfos. You can talk with thp about correct depend names for your project. It also helpful to send email to developer-care@jolla.com with such questions.
coderus ( 2016-06-25 21:20:24 +0200 )edit