Bug 455466 - installed files are not owned by any package
Summary: installed files are not owned by any package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 9
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-15 17:04 UTC by Vegard Nossum
Modified: 2008-07-15 17:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-15 17:18:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vegard Nossum 2008-07-15 17:04:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061712 Fedora/3.0-1.fc9 Firefox/3.0

Description of problem:
After a fresh install of F9, a lot of files are not owned by any package, for instance:

$ rpm -q -f /usr/bin/gpk-application 
file /usr/bin/gpk-application is not owned by any package

..making it difficult to know which package a program belongs to. In fact, it seems that there are more problems:

# yum install pirut
[...]
Package gnome-packagekit-0.1.12-12.20080430.fc9.i386 already installed and latest version

$ rpm -q -l gnome-packagekit
package gnome-packagekit is not installed

..this just doesn't make any sense whatsoever. I'm *assuming* this has something to do with how Anaconda initializes the RPM database, though I'm definitely no expert in this area. Feel free to relabel the bug if it belongs to another package.

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


How reproducible:
Sometimes


Steps to Reproduce:
1. Install F9
2. Run 'rpm -q -f /usr/bin/gpk-application'

Actual Results:
file /usr/bin/gpk-application is not owned by any package

Expected Results:
RPM should have told me which package the program belonged to.

Additional info:

Comment 1 Vegard Nossum 2008-07-15 17:18:16 UTC
This was actually all my fault. Apparently I had a stale ~/.rpmmacros which
followed my $HOME backup when I installed F9. So please disregard this report.


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