Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 51744 - dirs not owned by any package
dirs not owned by any package
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-08-14 12:52 EDT by Peter Bowen
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-14 14:19:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Bowen 2001-08-14 12:52:12 EDT
The directories in the attached list are not currently owned by any
package.  They should be owned by the package listed.  When the packages
are installed RPM will throw warnings about creating directories.  Jeff
Johnson has already stated that future versions of RPM will not allow this,
and these are easy to fix.
Comment 1 Glen Foster 2001-08-14 13:45:39 EDT
Honestly, if the errors/requests are filed on a package-by-package basis, it'll
be much easier to track.
Comment 2 Peter Bowen 2001-08-14 14:19:16 EDT
Bugzilla doesn't seem to like my attachment.  There are 170+ affected packages,
so it would be _very_ time consuming to file a seperate bug for each package. 
The complete list is available at http://www.scyld.com/~pzb/unowneddirs.1
Comment 3 Glen Foster 2001-08-14 14:58:07 EDT
It's too large a list to commit to for this release.  I'm marking it deferred
for now and we'll try to re-examine in for a future release. Thanks for the
details, though!
Comment 4 Peter Bowen 2001-08-14 15:15:03 EDT
I just wanted to get it into bugzilla.  I didn't expect it to be fixed this late
in the cycle.  May I suggest that the script that I attached to Bug #51582 be
used to help find these errors in the future?

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