RPM installed but unowned files and dirs
Hans de Goede
j.w.r.degoede at hhs.nl
Thu Mar 24 21:05:25 UTC 2005
Jeff Spaleta wrote:
> On Thu, 24 Mar 2005 21:37:33 +0100, Hans de Goede <j.w.r.degoede at hhs.nl> wrote:
>>I've already entered some of these in bugzilla but gave up when I saw
>>how many there are, should I enter these in bugzilla?
> How exactly are you determining which component to file about for
> unowned directories?
So far I have based this on which package owns files in the dir for
example db4 puts files in /lib/tls/i?86 and /usr/lib/tls/i?86 so I've
filed a bug against db4, although I think maybe glibc would be a better
target for the bug. So it is a mix between file against owner of files
in dir (as done for db4) and common sense, I used db4 assuming that the
db4 maintainer would reassing the bug to glibc if he concidered this a
> You have to try to make a determination of
> directory ownership based on what packages own files down inside the
> directory or else you really can't be sure what package was suppose to
> own the directory to begin with.
> If any of these unowned directories are empty.. you really can't be
> sure which package is the culprit, nor even which package vendor, if
> this system ever saw any packages from a second vendor.
They aren't my script nuckes any unowned empty dirs and does this
recursivly untill there are no more before building the list of unowned
> For example /usr/man/man3 in your list... I don't seem to have that
> on any of my systems.. not my fc2 or fc3 or my rawhide system.
> And on my fc2 system /usr/man/man1 contains only files i have
> installed from packages from Non redhat and Non Fedora Core/Extras
> locations (namely packages I've hacked together... once again proving
> I can't package worth crap)
> On my stock+updated fc3 system.. i don't even have /usr/man/ directory.
Thats from the libc 5 compatibility stuff:
[hans at cq229 ~]$ rpm -qf /usr/man/man3/dlopen.3.gz
I'm not claiming this is a perfect list, but most are real bugs, I've
already removed the easy not an FC bug candidates from the list, but
missed this one.
The real problem ones are perl and python modules, I had a lot of
/usr/lib/python-1.? dirs which all contained dirs from modules which
were never cleaned up, because they were unowned. Same for perl.
Still the question should I walk through this list and file them all?
Concidering how easy to fix these are the repsonse to the ones I've
filed sofar (about 1 week ago) are less then overwelming. Some got the
keyword easy fix tagged to them, fixing them is about as much work....
More information about the devel