Bug 842 - rpm bugs in package creation
rpm bugs in package creation
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-01-15 11:53 EST by sds
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-01-15 12:06:31 EST
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 sds 1999-01-15 11:53:37 EST
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 12:06:59 EST
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 rpm-list@redhat.com if you need more info.

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