Bug 473651 - epiphany : Unowned directories
Summary: epiphany : Unowned directories
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-29 19:01 UTC by Michael Schwendt
Modified: 2009-05-22 14:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-22 14:24:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Fixes the devel subpackage %files listing to grab the top-level include directory, rather than glob everything below it. (532 bytes, patch)
2008-12-22 20:28 UTC, Peter Gordon
no flags Details | Diff

Description Michael Schwendt 2008-11-29 19:01:01 UTC
One or more directories are not included within this
package and/or its sub-packages:

=> epiphany-devel-2.24.1-3.fc11.i386 (rawhide-development-i386)
/usr/include/epiphany

[...]

Further information:

https://fedoraproject.org/wiki/Packaging/ReviewGuidelines

MUST: A package must own all directories that it creates. If it does not
create a directory that it uses, then it should require a package which
does create that directory.

https://fedoraproject.org/wiki/Packaging/Guidelines#FileAndDirectoryOwnership
https://fedoraproject.org/wiki/Packaging/UnownedDirectories

Comment 1 Peter Gordon 2008-12-22 20:28:03 UTC
Created attachment 327688 [details]
Fixes the devel subpackage %files listing to grab the top-level include directory, rather than glob everything below it.

Seems that the line in the %files for the devel subpackage should not be a glob, just the top-level directory; that should fix it.

Comment 2 Michael Schwendt 2009-05-22 14:24:19 UTC
Yes, that's the correct trivial fix.

I've committed it a minute ago in devel (F-12) to get rid of old open tickets, which have not been responded to in several months.


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