Revision history [back]
 | 1 | initial version | posted 2016-06-25 21:07:05 +0200  |
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.
| | 2 | retagged |
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.
| | 3 | retagged |
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.