Bug 51744 – dirs not owned by any package

Bug 51744 - dirs not owned by any package

Summary:	dirs not owned by any package

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	distribution (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-08-14 12:52 EDT by Peter Bowen
Modified:	2007-04-18 12:35 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-08-14 14:19:20 EDT
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 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.