Bug 1112409 - fedora-review claims that python dirs are unowned
Summary: fedora-review claims that python dirs are unowned
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-review
Version: 20
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Stanislav Ochotnicky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-23 21:34 UTC by Jerry James
Modified: 2014-10-14 12:10 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-14 12:10:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jerry James 2014-06-23 21:34:43 UTC
Description of problem:
In recent reviews, fedora-review has been issuing complaints like this:

[x]: Package requires other packages for directories it uses.
     Note: No known owner of /usr/lib64/python3.4/site-packages,
     /usr/lib64/python3.4, /usr/include/python3.4m
[x]: Package must own all directories that it creates.
     Note: Directories without known owners: /usr/lib64/python3.4/site-
     packages, /usr/lib64/python3.4, /usr/include/python2.7,
     /usr/include/python3.4m

All of those directories are owned by python-libs or python3-libs.

Version-Release number of selected component (if applicable):
fedora-review-0.5.1-2.fc20.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Run fedora-review on a package such as the one in bug 1102950
2.
3.

Actual results:
Fedora-review complains about unowned directories that are, in fact, owned by the python-libs or python3-libs packages.

Expected results:
No such complaints.

Additional info:

Comment 1 Alec Leamas 2014-10-14 12:10:08 UTC
Unfortunately,  the directory ownership are not complete for performance reasons. That said, f-r does *not* complain about unowned directories, it just says it does not have a known owner i. e., that the ownership should be checked manually.  So, this is not a bug and I'm closing it as such.

Yes, to do a complete, fully recursive ownership check would be nice if performance allowed. Perhaps it might make sense to check of the new depsolver is fast enough to make this feasible.

Thanks for reporting!


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