Package Details: tsmclient-dkms 8.1.23.0-1

Git Clone URL: https://aur.archlinux.org/tsmclient.git (read-only, click to copy)
Package Base: tsmclient
Description: IBM Tivoli Storage Manager Client Journal-based Backup Kernel Module
Upstream URL: http://www-03.ibm.com/software/products/en/tivostormana/
Licenses: GPL, BSD
Submitter: semi
Maintainer: codyps (zsoerenm, ninjaaron, alyst, bananana)
Last Packager: bananana
Votes: 5
Popularity: 0.000000
First Submitted: 2014-08-22 11:45 (UTC)
Last Updated: 2024-10-09 12:21 (UTC)

Latest Comments

1 2 3 Next › Last »

zzrzlk commented on 2022-12-07 09:59 (UTC) (edited on 2022-12-07 10:00 (UTC) by zzrzlk)

Hi Codyps. Thx for taking care of tsm users ! Please have a look on the (bad end) install below:

(3/3) Install DKMS modules ==> dkms install --no-depmod tsmclient/8.1.14.0 -k 6.0.8-arch1-1 Error! Bad return status for module build on kernel: 6.0.8-arch1-1 (x86_64) Consult /var/lib/dkms/tsmclient/8.1.14.0/build/make.log for more information. ==> WARNING: `dkms install --no-depmod tsmclient/8.1.14.0 -k 6.0.8-arch1-1' exited 10

[**@archtst04 tsmclient]$ cat /var/lib/dkms/tsmclient/8.1.14.0/build/make.log DKMS make.log for tsmclient-8.1.14.0 for kernel 6.0.8-arch1-1 (x86_64) Wed Dec 7 10:53:21 AM CET 2022 make: Entering directory '/usr/lib/modules/6.0.8-arch1-1/build' CC [M] /var/lib/dkms/tsmclient/8.1.14.0/build/audit.o In file included from /var/lib/dkms/tsmclient/8.1.14.0/build/jbb.h:63, from /var/lib/dkms/tsmclient/8.1.14.0/build/audit.c:69: /var/lib/dkms/tsmclient/8.1.14.0/build/log.h:58:10: fatal error: stdarg.h: No such file or directory 58 | #include <stdarg.h> | ^~~~~~~~~~ compilation terminated. make[1]: [scripts/Makefile.build:249: /var/lib/dkms/tsmclient/8.1.14.0/build/audit.o] Error 1 make: ** [Makefile:1852: /var/lib/dkms/tsmclient/8.1.14.0/build] Error 2 make: Leaving directory '/usr/lib/modules/6.0.8-arch1-1/build'

bananana commented on 2022-02-15 14:11 (UTC)

The current version seems to require libxcrypt-compat.

schween commented on 2021-12-23 08:17 (UTC)

@alyst I removed the previously created symlinks, updated and it works out of the box :)Thanks for taking care of this.

alyst commented on 2021-12-22 18:25 (UTC)

@schween Thanks for reporting, should be fixed now (the libs are properly installed to /usr/lib).

schween commented on 2021-12-22 11:39 (UTC) (edited on 2021-12-22 15:33 (UTC) by schween)

Since the last update, I am getting the following error message when executing dsmc dsmc: error while loading shared libraries: libtsmxerces-depdom.so.28: cannot open shared object file: No such file or directory

Maybe a new dependency? I found a solution: https://www.ibm.com/support/pages/apar/IT20524

I had to create symlinks in /usr/lib64, namely ln -s /opt/tivoli/tsm/client/api/bin64/libtsmxerces-c.so.28.0 /usr/lib64/libtsmxerces-c.so.28 and ln -s /opt/tivoli/tsm/client/api/bin64/libtsmxerces-depdom.so.28.0 /usr/lib64/libtsmxerces-depdom.so.28

alyst commented on 2019-12-24 17:24 (UTC)

@codyps Thanks!

codyps commented on 2019-12-24 16:56 (UTC)

@alyst: I've added you as a co-maintainer, feel free to push your changes here.

alyst commented on 2019-12-24 16:33 (UTC)

8.1.9 is out, I've updated the PKGBUILD, see here: https://github.com/alyst/tsmclient dkms build was not working for me, so I've tried to fix it as well ("make module" was supposed to start another make process internally, but it was not happening, so I've changed dkms.conf to initiate that 2nd make directly).

bigred15 commented on 2018-04-11 04:33 (UTC)

Differences between client versions change in almost every release, added and removed functionality and options. This doesn't just change between major releases (ie: 7 to 8) but also between minor updates from say 8.1.0 to 8.1.2 to 8.1.3 to 8.1.4 etc..

Reference link: https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.4/client/r_new_for_version.html

Server and Client Compatibility information can be found at this link: https://www-01.ibm.com/support/docview.wss?uid=swg21053218

codyps commented on 2017-06-06 22:18 (UTC)

I updated to the latest 7 as that is what my work's IT was using. I'm not sure what the compatibility story is between different client versions. It may make sense to have a seperate package per major version, but I'm not really sure.

1 2 3 Next › Last »