|
Bugzilla – Full Text Bug Listing |
| Summary: | ldconfig persistent libADM sym-link errors | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Robert Irvine <E.microcorys> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | E.microcorys, meissner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
where are the libADM_* coming from? Packages installing libraries call /sbin/ldconfig in their %post-install script to create the necessary symlinks to the most recent shared libraries found in your system.
@Robert: Please attach the output of:
> ls -ld /usr/lib64/libADM_coreSocket6.so*
> rpm -qf /usr/lib64/libADM_* | sort -u
This should help the glibc maintainer to judge, whether the ldconfig error messages are wrong or the package(s) providing the libADM_* libs needs to be fixed.
(In reply to Marcus Meissner from comment #1) > where are the libADM_* coming from? AFAIK avidemux. As requested:
> ls -ld /usr/lib64/libADM_coreSocket6.so*
-rwxr-xr-x 1 root root 23048 Feb 6 10:16 /usr/lib64/libADM_coreSocket6.so
-rwxr-xr-x 1 root root 18920 Feb 5 11:02 /usr/lib64/libADM_coreSocket6.so.rpmsave
Well, the message of ldconfig certainly is correct. /usr/lib64/libADM_coreSocket6.so is no symlink, and normally it should indeed be. ldconfig suppresses this message when the library soname is the library itself. The problem is created by the .rpmsave file. That has a soname of "libADM_coreSocket6.so" itself, but that target file is no symlink (because it's taken by the library proper), so the message results. No idea why rpm created this .rpmsave file, it normally does only for config files, but in any case, this is the problem, not ldconfig. Either a bug in the avidemux spec file, or in our installer. Back to screening. So it's an upstream packaging bug (inappropriate %confing in the spec file). This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |
Recent zypper updates display "Additional rpm output" messages relating to Idconfig libADM symbolic link errors similar to this: ( 12/203) Installing: glibc-2.18-4.44.1 ..............[done] Additional rpm output: /sbin/ldconfig: /usr/lib64/libADM_coreSocket6.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM_coreAudioDevice6.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM_coreAudio6.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM_coreLibVA6.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM6swscale.so.3 is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM_coreSqlLight3.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM_coreJobs.so is not a symbolic link /sbin/ldconfig: /usr/lib64/libADM6avutil.so.54 is not a symbolic link ... 50 similar lines relating to other libADM_*.so files only have been snipped. The most recent update generated 100 similar message sets - about 90% of total installation actions. After posting a request for technical assistance on openSUSE forum it was suggested that that I report this as a possible bug and provide uname - a output, which follows: > uname -a Linux linux-90ml 3.11.10-34-desktop #1 SMP PREEMPT Wed Jan 20 14:13:45 UTC 2016 (1e76e80) x86_64 x86_64 x86_64 GNU/Linux