Bug 993781 - givaro possibly affected by F-20 unversioned docdir change
Summary: givaro possibly affected by F-20 unversioned docdir change
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: givaro
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: mycae
QA Contact: Fedora Extras Quality Assurance
URL: http://fedoraproject.org/wiki/Changes...
Whiteboard:
Depends On:
Blocks: F20UnversionedDocDirs
TreeView+ depends on / blocked
 
Reported: 2013-08-06 12:13 UTC by Ville Skyttä
Modified: 2013-08-06 15:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-06 15:39:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ville Skyttä 2013-08-06 12:13:41 UTC
givaro was identified as a package possibly needing maintainer attention
due to the F-20 unversioned doc dir change. The identification is not
foolproof, it is basically this grep:

    grep -E "(/doc|_docdir|_defaultdocdir).+version" *.spec

Please review your package and make the appropriate changes, if any. A
good starting point is checking the lines output by the above grep for
your specfile. For the vast majority of packages, after the changes,
the expected outcome is that documentation dirs in /usr/share/doc
should no longer contain the package version.

More information and tips:
  https://fedoraproject.org/wiki/Changes/UnversionedDocdirs
  http://thread.gmane.org/gmane.linux.redhat.fedora.devel/183942/focus=183943
  http://thread.gmane.org/gmane.linux.redhat.fedora.devel/183942/focus=183973

Comment 1 Jerry James 2013-08-06 15:39:35 UTC
This one is a false alarm.  The target string does show up in the spec, as an argument to %configure, but since upstream's documentation installer is broken, we wind up installing documentation (using %doc) by hand anyway.

I will remove the "-%{version}" part in git so that if upstream fixes documentation installation, we will be correct automatically, but there is no need to rebuild right now.


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