Bug 476048 – "yum provides /some/file" fails (no cache)

Bug 476048 - "yum provides /some/file" fails (no cache)

Summary:	"yum provides /some/file" fails (no cache)

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	yum (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	x86_64 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Seth Vidal
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-12-11 12:53 EST by Horst H. von Brand
Modified:	2014-01-21 18:07 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-12-11 14:43:21 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Horst H. von Brand 2008-12-11 12:53:44 EST

Description of problem:
I tried:

$ yum provides /usr/lib64/gtk-2.0/modules/libpk-gtk-module.so
Loaded plugins: fastestmirror, refresh-packagekit
Importing additional filelist information
Error: Caching enabled but no local cache of //var/cache/yum/rawhide/4416992610e6a7aaf089a4c6cba2a694887f6c70-filelists.sqlite.bz2 from rawhide

Version-Release number of selected component (if applicable):
yum-3.2.20-7.fc11.noarch

How reproducible:
Always, the repo configuration doesn't matter

Steps to Reproduce:
1. yum provides /etc
2.
3.
  
Actual results:
Above message

Expected results:
Get the missing file and continue

Additional info:

Comment 1 seth vidal 2008-12-11 13:19:13 EST

If you run it as root does it work?

Comment 2 Horst H. von Brand 2008-12-11 14:37:27 EST

Yes, running as root does work.

Comment 3 seth vidal 2008-12-11 14:43:21 EST

right, then what is it you want this to do? The data yum needs to do the lookup is not present and you're not running as root. So it can't write to the paths where it normally would.

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