Description of problem: You've got dangling symbolic links in /lib/modules/<version> when no -devel package is installed, to be exact /lib/modules/<version>/{build,source} are dangling. I'm no kernel maintainer, but I can't see any reason to keep both symlinks in the main package rather to move them to the -devel package. Both symlinks are pointing at least to /usr/src/kernels/<version> which is only available, when the -devel package is installed - so why not also move the symlinks into -devel? Version-Release number of selected component (if applicable): kernel-2.6.16-1.2227_FC6 Actual results: /lib/modules/<version>/{build,source} are dangling symbolic links. Expected results: Move /lib/modules/<version>/{build,source} to -devel package. Additional info: Untested patch is attached...
Created attachment 130191 [details] Untested patch against CVS which should work
Robert, the symlinks `build' and `source' were only recently moved over from the `kernel-*-devel' packages to the `kernel-*' packages as per bug #149210. I, too, personally don't consider this to be the best thing. I filed rather complex bug #193990 on this overall issue.
Jiri, the reason for opening up this bug report was, that current versions of rpm *are* detecting dangling symlinks on runtime, that means while installing the package for example (yeah, Fedora is shipping nearly an antiquaric rpm version). Nevertheless current behaviour it's worse and very very insane rpm packaging - delivering dangling symlinks within a rpm package. Bad thing to tell guys of the company which invented rpm some years ago about the sane rpm packaging... :-(
Ping?
my vague recollection on why it was done this way, was that the kernel package owns the /lib/modules/{version}/ directory, and having kernel-devel put files into that subdir would mean that if someone removed the kernel rpm, the subdir wouldn't get removed, due to another package owning files in the hierarchy. Whether rpm has changed any since this was decided (that was ~5 years back at least) I have no idea.
*** Bug 444297 has been marked as a duplicate of this bug. ***
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Ping? This is still a rawhide thing...
This is duplicate of bug 149210 -- either we should go this or other direction, but no reason to keep both bugs around. If you want to complain against the current direction, I think you have very short time -- warren on the other bug is asking for comments. *** This bug has been marked as a duplicate of 149210 ***
Are you kidding me? Is asking for comments? This was in 2005 - three years ago!
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The symlinks are still dangling with kernel-2.6.32.8-58.fc12.i686. Is this definitely going to stay this way, or is this still considered a problem? If so, what is the preferred solution?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is still a rawhide thing...