Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34890 - [stfl] missing libstfl.so.0

Attached to Project: Community Packages
Opened by Jakub Klinkovský (lahwaacz) - Monday, 22 April 2013, 16:59 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Sunday, 05 August 2018, 19:28 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Package doesn't provide libstfl.so.0 symlink, which is required by newsbeuter:

newsbeuter: error while loading shared libraries: libstfl.so.0: cannot open shared object file: No such file or directory

Package versions (all from community):
* stfl 0.22-1
* newsbeuter 2.6-1
This task depends upon

Closed by  Jaroslav Lichtblau (Dragonlord)
Sunday, 05 August 2018, 19:28 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in stfl-0.24-4
Comment by Jelle van der Waa (jelly) - Thursday, 25 April 2013, 07:35 GMT
Newsbeuter works fine here, you're install or stfl package is broken.
[jelle@P9][~]%pacman -Ql stfl | grep so
stfl /usr/lib/libstfl.so
stfl /usr/lib/libstfl.so.0.22

^ nevermind above. I seem to have libstfl.so.0
[jelle@P9][~]%pacman -Qo /usr/lib/libstfl.so.0
error: No package owns /usr/lib/libstfl.so.0

Ok ldconfig creates the symlink when you install sftl. Try re-installing
Comment by Jakub Klinkovský (lahwaacz) - Thursday, 25 April 2013, 10:18 GMT
Ah, that's it. But still, shouldn't the link be in the package?
Comment by Jelle van der Waa (jelly) - Thursday, 25 April 2013, 11:16 GMT
I guess not, ldconfig should just create it.
Comment by Doug Newgard (Scimmia) - Monday, 25 June 2018, 00:03 GMT
The conclusion here was very wrong. The soname symlink should be in the package, not created after the fact.

Loading...