Bug 460807 - Circular symbolic link in devel package
Summary: Circular symbolic link in devel package
Alias: None
Product: Fedora
Classification: Fedora
Component: libgphoto2
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-09-01 11:08 UTC by Denis Leroy
Modified: 2013-07-02 23:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-12-18 09:47:21 UTC
Type: ---

Attachments (Terms of Use)

Description Denis Leroy 2008-09-01 11:08:32 UTC
There seems to be a circular symbolic link in the /usr/include/gphoto2 directory :

lrwxrwxrwx 1 root root 1 2008-05-30 10:57 /usr/include/gphoto2/gphoto2 -> ./

This will cause spurious error messages from recursive greps or find commands, for example. There's not much sense to have that link there. If it's for backward compatibility reasons (to support include <gphoto2/gphoto2/gphoto2-foo.h> ??), it is those projects that should be patched and upstreams notified, rather than adding this link.

Comment 1 Bug Zapper 2008-11-26 02:55:13 UTC
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:

Comment 2 Bug Zapper 2009-11-18 08:20:38 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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: 

Comment 3 Bug Zapper 2009-12-18 06:21:11 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Denis Leroy 2009-12-18 07:50:42 UTC
Reopening, as this problem still exists in F-12.

Comment 5 Denis Leroy 2009-12-18 09:40:06 UTC
Could you please fix this ? The symbolic link serves no purpose. I can't think of a single backward-compatibility scenario where it would be useful. I tested all the packages that depend on libgphoto2-devel and they build fine without it. Here's the spec file patch:

@@ -124,6 +124,8 @@
 rm -rf %{buildroot}%{_libdir}/*.a
 rm -rf %{buildroot}%{_libdir}/*.la
+rm -f %{buildroot}%{_includedir}/gphoto2/gphoto2
 %find_lang %{name}-2
 %find_lang %{name}_port-0
 cat libgphoto2*.lang >> %{name}.lang
@@ -162,6 +164,9 @@


Comment 6 Jindrich Novy 2009-12-18 09:47:21 UTC
Indeed, this symlink is meant to assure compatibility with older libgphoto2 versions and it is no more needed as the pkgconfig --cflags points directly to /usr/incude/gphoto2 now.

It is fixed in rawhide and committed to F12 for now so it will occur along with the next update.

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