it does not have to be a symbolic link - that is ldconfig cleaning up its database and being extra verbose

well a lot extra verbose. every call to ldconfig emits this warning. if it doesnt have to be a symlink ... then why does it warn?

poseidon:/var/log/zypp # /sbin/ldconfig /usr/lib64
poseidon:/var/log/zypp # 


# grep -B2 libproxy.so.1 /var/log/zypp/history 
# 2023-05-16 22:37:25 libproxy1-0.5.0-237.1.x86_64.rpm installed ok
# Additional rpm output:
# /sbin/ldconfig: /lib64/libproxy.so.1 is not a symbolic link

so this happened exactly once in e.g. my zypp history and ldconfig has been quiet about this ever since (which is what I would expect)

Please check:

ls -la /lib64/libproxy* - do you have multiple (possibly stale) libraries there?

you want zypper.log for the ldconfig output:
 
```
grep -B1 -c '2023-09-23.*libproxy.so.1' /var/log/zypper.log
182
```

```
ls -ld /lib64/libproxy*   
drwxr-xr-x 2 root root  4096 Sep 23 02:18 /lib64/libproxy
drwxr-xr-x 3 root root  4096 Nov  3  2020 /lib64/libproxy-0.4.15
drwxr-xr-x 3 root root  4096 Dez 14  2020 /lib64/libproxy-0.4.16
-rwxr-xr-x 1 root root 14368 Sep 20 13:40 /lib64/libproxy.so.1
```

it seems nothing cleans up empty libproxy module directories

```
find /lib64/libproxy*/
/lib64/libproxy/
/lib64/libproxy/libpxbackend-1.0.so
/lib64/libproxy-0.4.15/
/lib64/libproxy-0.4.15/modules
/lib64/libproxy-0.4.16/
/lib64/libproxy-0.4.16/modules
```