Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 842 - rpm bugs in package creation
Summary: rpm bugs in package creation
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm
Version: 5.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-01-15 16:53 UTC by sds
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-01-15 17:06:31 UTC

Attachments (Terms of Use)

Description sds 1999-01-15 16:53:37 UTC
1. I have to untar, build and install every time I want to
re-build the
   package.  This is a design flaw.

2. RPM cannot grok rpmrc created by `rpm --showrc >

3. RPM runs chown -R root.root/chmod -R.  While the latter
can be
   rendered (relatively) harmless by a `fixperms' in rpmrc,
the former
   does damage which can be fixed by hand.  If you want the
files in the
   RPMs to have certain ownership/permission, you don't have
to mess
   with the actual filesystem on disk.

Comment 1 Jeff Johnson 1999-01-15 17:06:59 UTC
Specific answers:
1) You can do
	a) tarball:	rpm -ta foo.tar.gz
	b) src.rpm:	rpm --rebuild foo*src.rpm
to eliminate unnecessary steps.

2) rpm --shworc is for humans. Why should the displayed output
use the same syntax as the rpmrc file?

3) I build rpm's all day long using non-root uid without rpm running
chown/chmod root.root. I need to know more specifics in order to
remedy. As for ownership of files within the binary rpm, I routinely
add %defattr(-,root,root) to top of %files to get predictable
ownership. Make sure that you have specific %attr's for setuid
programs however.

Try if you need more info.

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