Red Hat Bugzilla – Bug 39390
packages have dangling symlinks
Last modified: 2007-04-18 12:33:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2smp i686; en-US; 0.7)
Description of problem:
As part of the RedHat v7.1 installation many dangling symlinks are created.
Steps to Reproduce:
1. Install RedHat Linux v7.1
2. After initial boot, run this command:
symlinks -tr / | grep dangling
Actual Results: dangling: /var/lib/wnn6 -> /usr/local/OMRONWnn6/wnn6linux
dangling: /usr/share/doc/db3-devel-3.1.17/examples_c/tags -> ../dist/tags
dangling: /usr/share/doc/db3-devel-3.1.17/examples_cxx/tags -> ../dist/tags
dangling: /usr/share/doc/ltrace-0.3.10/ChangeLog -> debian/changelog
dangling: /usr/share/doc/screen-3.9.8/FAQ -> doc/FAQ
dangling: /usr/lib/libgdk_pixbuf_xlib-1.3.so -> libgdk_pixbuf_xlib-1.3.so.0.0.0
dangling: /lib/modules/2.4.2-2smp/build -> ../../../usr/src/linux-2.4.2
dangling: /lib/modules/2.4.2-2/build -> ../../../usr/src/linux-2.4.2
Expected Results: No dangling symlinks should have been found.
Note that this installation was done buy selecting All packages for
installation, then deselecting the kernel-doc and kernel-source packages.
The absence of the Linux source files means the absence of a Linux source
directory, which in turn explains those last 2 bad symlinks
This was seen on a dual Pentium III/850 system with 512MB of RAM.
I've verified this problem.
I think that this is more of a packaging problem...changing component to
tim, can you do a fresh test of this sort on our beta trees, and then send out notices to
anyone who owns packages with dangling symlinks?
Yes. I'll do that on the next test install that I do.
These have all been resolved. Closing -> rawhide.