Bug 1352764 - Kernels still seem to leave broken symlinks to dirs that should be "owned" by the "devel" package rather than the "core" package.
Summary: Kernels still seem to leave broken symlinks to dirs that should be "owned" by...
Keywords:
Status: CLOSED DUPLICATE of bug 149210
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-05 02:59 UTC by John Dodson
Modified: 2016-07-06 04:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 16:07:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Dodson 2016-07-05 02:59:01 UTC
Description of problem:

Kernels still seem to leave broken symlinks to dirs that should be "owned" by the "devel" package rather than the "core" package.

Version-Release number of selected component (if applicable):
Fedora release 23 (Twenty Three)


How reproducible:
Always if "devel" package is not installed.
See also Bug 1185918

Steps to Reproduce:
1.# symlinks -r / | grep -i dangling | grep fc23
dangling: /usr/lib/modules/4.5.7-202.fc23.i686/build -> /usr/src/kernels/4.5.7-202.fc23.i686
dangling: /usr/lib/modules/4.5.7-202.fc23.i686/source -> build

2.file /usr/lib/modules/4.5.7-202.fc23.i686/build
/usr/lib/modules/4.5.7-202.fc23.i686/build: broken symbolic link to /usr/src/kernels/4.5.7-202.fc23.i686
owned by: kernel-core-4.5.7-202.fc23.i686

file /usr/lib/modules/4.5.7-202.fc23.i686/source
/usr/lib/modules/4.5.7-202.fc23.i686/source: broken symbolic link to build
kernel-core-4.5.7-202.fc23.i686

3.

Actual results:
See above


Expected results:
Broken symlinks (Dangling) should not be present.

Additional info:

Comment 1 Josh Boyer 2016-07-05 16:07:41 UTC
One of our long term kernel maintainers found the reasons we have for keeping this as it is.  Nothing has really changed, so we aren't going to move the symlinks.

*** This bug has been marked as a duplicate of bug 149210 ***

Comment 2 John Dodson 2016-07-06 01:22:06 UTC
Really? what were his reasons?

Broken means broken.

The code should probably be better at working out what it should do rather than rely on what will probably be broken symlinks or symlinks generally (symlinks
have always been a lazy way to fix something that usually bites later)

Comment 3 Josh Boyer 2016-07-06 01:29:42 UTC
The reasons are in the bug I duplicated this against.

Comment 4 John Dodson 2016-07-06 04:59:34 UTC
Sorry I'm not convinced that this could not be fixed in a more elegant way that maintains the files appropriately with no broken links.


Note You need to log in before you can comment on or make changes to this bug.