We're just testing 7.1.6.3 in our environment.
The package 'gskcrypt64-8.0.50.66.linux.x86_64.rpm' and 'gskssl64-8.0.50.66.linux.x86_64.rpm' could be installed without problems.
When installing 'TIVsm-API64.x86_64.rpm' The first dependency errors arose:
schooladmin.innenstadtwest.schuledo.de:~/TSM/TSM_test # rpm -Uvh TIVsm-API64.x86_64.rpm
error: Failed dependencies:
libxmlutil-7.1.2.0.so()(64bit) is needed by (installed) TIVsm-BA-7.1.2-0.x86_64
TIVsm-API64 = 7.1.2-0 is needed by (installed) TIVsm-BA-7.1.2-0.x86_64
TIVsm-API64 = 7.1.2-0 is needed by (installed) TIVsm-msg.DE_DE-7.1.2-0.x86_64
With support by 'http://www-01.ibm.com/support/docview.wss?uid=swg21652270' I could limit this down to the following dependency:
schooladmin.innenstadtwest.schuledo.de:~/TSM/TSM_test # rpm -Uvh TIVsm-API64.x86_64.rpm TIVsm-BA.x86_64.rpm
error: Failed dependencies:
TIVsm-API64 = 7.1.2-0 is needed by (installed) TIVsm-msg.DE_DE-7.1.2-0.x86_64
We tried the paramter 'rpm -F' for update, but the error still exists further.
Is there possibly a new 'TIVsm-msg.DE_DE' ?
We use today 'Client Version 7, Release 1, Level 2.0'
The package 'gskcrypt64-8.0.50.66.linux.x86_64.rpm' and 'gskssl64-8.0.50.66.linux.x86_64.rpm' could be installed without problems.
When installing 'TIVsm-API64.x86_64.rpm' The first dependency errors arose:
schooladmin.innenstadtwest.schuledo.de:~/TSM/TSM_test # rpm -Uvh TIVsm-API64.x86_64.rpm
error: Failed dependencies:
libxmlutil-7.1.2.0.so()(64bit) is needed by (installed) TIVsm-BA-7.1.2-0.x86_64
TIVsm-API64 = 7.1.2-0 is needed by (installed) TIVsm-BA-7.1.2-0.x86_64
TIVsm-API64 = 7.1.2-0 is needed by (installed) TIVsm-msg.DE_DE-7.1.2-0.x86_64
With support by 'http://www-01.ibm.com/support/docview.wss?uid=swg21652270' I could limit this down to the following dependency:
schooladmin.innenstadtwest.schuledo.de:~/TSM/TSM_test # rpm -Uvh TIVsm-API64.x86_64.rpm TIVsm-BA.x86_64.rpm
error: Failed dependencies:
TIVsm-API64 = 7.1.2-0 is needed by (installed) TIVsm-msg.DE_DE-7.1.2-0.x86_64
We tried the paramter 'rpm -F' for update, but the error still exists further.
Is there possibly a new 'TIVsm-msg.DE_DE' ?
We use today 'Client Version 7, Release 1, Level 2.0'