[MCOL-1791] Fail to install mariadb-columnstore-api with deployed python3 newer version Created: 2018-10-11  Updated: 2023-10-26  Resolved: 2022-11-05

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 1.2
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Zdravelina Sokolovska (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None


 Description   

Fail to install mariadb-columnstore-api with deployed python3 newer version

note :
mariadb-columnstore-api-1.2.0-1-x86_64-centos7.rpm: Header V4 RSA/SHA512 Signature, key ID a41f5c14: get from mcs repos/1.2.0-1/nightly/ builds 2018-10-10 05:02

it's installed Python 3.6.6 but mariadb-columnstore-api-1.2.0-1 inatallation fails with
error: Failed dependencies:
python(abi) = 3.4 is needed by mariadb-columnstore-api-1.2.0-1.x86_64

# rpm -ivh  mariadb-columnstore-api-1.2.0-1-x86_64-centos7.rpm
 
warning: mariadb-columnstore-api-1.2.0-1-x86_64-centos7.rpm: Header V4 RSA/SHA512 Signature, key ID a41f5c14: NOKEY
 
error: Failed dependencies:
 
        python(abi) = 3.4 is needed by mariadb-columnstore-api-1.2.0-1.x86_64
 
 
 



#  python3 --version
 
Python 3.6.6



 Comments   
Comment by Jens Röwekamp (Inactive) [ 2019-01-02 ]

This is caused by Swig using Python 3.x'es shared libraries instead of the general Python 3 ones.
It probably can only be fixed on a Swig level. This "bug" only appears on CentOS and Windows.
In Debian / Ubuntu Swig uses the general Python 3 shared libraries for the name bindings.

Due to recent split into separate installation packages for pymcsapi and pymcsapi3 the dependency resolution is more fine graded and should suggest to install the right Python 3.x package to run pymcsapi3.

Of course, we could switch to a newer Python 3 version than 3.4 if required/requested.

Comment by Todd Stoffel (Inactive) [ 2022-11-05 ]

This item is being closed because it was well passed the expiration date with no activity. If you suspect this was done in error please create a new ticket.

Generated at Thu Feb 08 02:31:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.