Arch Linux

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#77419 - [nvidia-utils] so link that is not owned by any package related to nvidia-utils

Attached to Project: Arch Linux
Opened by Arvid Norlander (VorpalGun) - Tuesday, 07 February 2023, 10:09 GMT
Last edited by Toolybird (Toolybird) - Friday, 17 February 2023, 22:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
It appears that a symlink that should be installed is not, it insteads ends up created by ldconfig which (I believe) pacman executes. This is a problem since I have a script that warns about files under /usr that are not owned by any package. And while some post install scripts etc create such files, this is the first time I have seen it for a .so symlink (usually it is Haskell stuff or mime caches or what not). I don't want to have to whitelist yet another file, especially since this one seems pretty pointless.

~ ❯ ls -l /usr/lib/libnvidia-vulkan-producer.so.525
lrwxrwxrwx 1 root root 38 7 feb 11.05 /usr/lib/libnvidia-vulkan-producer.so.525 -> libnvidia-vulkan-producer.so.525.85.05
~ ❯ pacman -Qo /usr/lib/libnvidia-vulkan-producer.so.525
error: No package owns /usr/lib/libnvidia-vulkan-producer.so.525
~ ❯ pacman -Qo /usr/lib/libnvidia-vulkan-producer.so.525.85.05
/usr/lib/libnvidia-vulkan-producer.so.525.85.05 is owned by nvidia-utils 525.85.05-1

Additional info:
* package version(s) nvidia-utils 525.85.05-1
* link to upstream bug report, if any: N/A, this seems like a Arch packaging problem.

Steps to reproduce:
* Install nvidia-utils.
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 17 February 2023, 22:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  Reporter says "It's fixed isn't it?"
Answer "yes"
Comment by Mike Yuan (YHNdnzj) - Wednesday, 08 February 2023, 03:15 GMT
Running into this too. The hardcoded soname in https://github.com/archlinux/svntogit-packages/blob/packages/nvidia-utils/trunk/PKGBUILD#L148 should be the culprit.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 08 February 2023, 03:33 GMT
Ok, I'm now setting the missing SONAME manually using patchelf. It's not pretty but it works. You'll then have to manually delete that symlink once but it shouldn't be re-created. Please test.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 08 February 2023, 03:39 GMT
No, I checked it and the original file doesn't have a SONAME at all which is in fact the problem. I'm now patching one in using patchelf.
Comment by Mike Yuan (YHNdnzj) - Wednesday, 08 February 2023, 03:49 GMT
Hmm, I'm wondering why this didn't trigger before, if so.
Comment by Arvid Norlander (VorpalGun) - Wednesday, 08 February 2023, 12:35 GMT
@Mike Yuan It it possible that it used to have an SONAME but nvidia broke it in a recent version? After all, it is nvidia we are talking about here :P
Comment by Arvid Norlander (VorpalGun) - Wednesday, 08 February 2023, 12:38 GMT
@Sven-Hendrik Haase (Svenstaro) Seems to work, the old file does indeed have to be manually deleted.

A bit annoying that this will leave cruft on every user's computer (which most will never notice), but I don't think there is much that can be done, apart from an install script to clean this up? Probably not worth it though.

EDIT: Hm, will this break compatibility with binaries built on other distros? Flatpaks provide their own GPU runtimes, so not an issue. But I'm wondering about things like AppImage etc. Hopefully this is an indirect dependency and thus not affected by that? Should be, since it seems to be nvidia specific.

Loading...