FS#63344 - [tensorflow] soname symlinks not included in package

Attached to Project: Community Packages
Opened by Felix Yan (felixonmars) - Friday, 02 August 2019, 05:26 GMT
Last edited by Konstantin Gizdov (kgizdov) - Tuesday, 20 August 2019, 22:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Konstantin Gizdov (kgizdov)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Some soname symlinks are generated by ldconfig and are not included in the packages. They should be included.

For example:

error: No package owns /usr/lib/libtensorflow.so.1
error: No package owns /usr/lib/libtensorflow_cc.so.1
error: No package owns /usr/lib/libtensorflow_framework.so.1

Additional info:
* package version(s)
tensorflow-opt-cuda 1.14.0-2
This task depends upon

Closed by  Konstantin Gizdov (kgizdov)
Tuesday, 20 August 2019, 22:03 GMT
Reason for closing:  Fixed
Comment by Bastian Beranek (totsilence) - Monday, 19 August 2019, 07:16 GMT
After upgrading to tensorflow 1.14.0-3 (which I assume was meant to fix this bug), I get:

ldconfig: /usr/lib/libtensorflow.so.1.14.0-2.params is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libtensorflow_cc.so.1.14.0-2.params is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libtensorflow_framework.so.1.14.0-2.params is not an ELF file - it has the wrong magic bytes at the start.

When running "ldconfig" (which is in turn called by pacman, for example).
Comment by DarcyHu (DarcyHu) - Tuesday, 20 August 2019, 02:04 GMT
This also leads to file conflicts when upgrade to 1.14.0-3. I got file conflicts:
/usr/lib/libtensorflow.so.1
/usr/lib/libtensorflow_cc.so.1
/usr/lib/libtensorflow_framework.so.1

Loading...