Bug 388811 - dangling symlink
Summary: dangling symlink
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebluetooth
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Gilboa Davara
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-11-17 20:56 UTC by Denise Dumas
Modified: 2008-05-08 08:03 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2008-05-08 08:03:51 UTC

Attachments (Terms of Use)

Description Florian La Roche 2007-11-17 20:56:27 UTC
Description of problem:

kdebluetooth has dangling symlink from
/usr/share/doc/HTML/ca/kdebluetooth/common to /usr/share/doc/HTML/ca/common


Florian La Roche

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Gilboa Davara 2007-11-27 17:41:28 UTC
Nice catch.
Will be fixed in the next release.

Comment 3 Steven M. Parrish 2008-05-07 22:37:15 UTC
Is this fixed?  Can it be closed?

Comment 4 Gilboa Davara 2008-05-07 23:25:03 UTC
Uggh. Nope, sorry. :(
The fix must have slipped through the cracks.
I'll reapply the fix tomorrow and release an update.

- Gilboa

Comment 5 Gilboa Davara 2008-05-08 08:03:51 UTC
OK. Now I remember:

The dangling symlink is part of the Catalan translation; If kde-i18n-Catalan is
installed, the symlink will dangle no more.
If I remove it, I'll lose the Catalan translation. (Far worse, depending on your
 KDE configuration, additional dangling symlinks may appear.)
Creating empty directories that aren't being owned by anyone is also a bad
solution. (Directories will not be removed if/when KDE is uninstalled)

P.S. The problem seems to be shared by a number of other KDE applications:
E.g. /usr/share/doc/HTML/fr/common which is pointed by
/usr/share/doc/HTML/fr/kdebluetooth/common is actually being owned by k3b. (A
bug by itself)

In short, IMHO the least offending solution is keeping the dangling symlink as
it is.

Changing to CANTFIX. 

- Gilboa

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