Bug 461724 - dhcpv6 can only be built by root
Summary: dhcpv6 can only be built by root
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: dhcpv6
Version: 4.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-10 07:58 UTC by loic
Modified: 2008-09-29 05:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-26 22:00:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
typescript.txt (44.43 KB, text/plain)
2008-09-26 21:59 UTC, David Cantrell
no flags Details

Description loic 2008-09-10 07:58:45 UTC
Description of problem:
dhcpv6 can only be built by root, because the file named configure is already shipped in dhcp-0.10.tgz and is read-only.

Version-Release number of selected component (if applicable):
0.10-24_EL4

How reproducible:
Always

Steps to Reproduce:
1. Build dhcpv6 while not being root
2.
3.
  
Actual results:
rpmbuild fails during %build phase with :
autom4te: cannot open configure: Permission denied

Expected results:
rpmbuild should end normally

Additional info:

Comment 1 loic 2008-09-10 08:12:28 UTC
Oops, I didn't saw bug 185598 and the %_fixperms workaround. Sorry.
I'm not sure that setting %_fixperms is a good idea, since this assumes that all
packages have correct %defattr and %attr settings, which is not obvious. It would be better to correct dhcpv6.spec as the user in 185598 suggested.

Comment 2 David Cantrell 2008-09-26 21:59:14 UTC
I am able to build the dhcpv6 package as a non-root user on RHEL 4.7 just fine.

You have to create a local rpmbuild directory and set that as your rpmbuild topdir, but this is standard practice.

The attached typescript.txt shows what I did.

Comment 3 David Cantrell 2008-09-26 21:59:50 UTC
Created attachment 317840 [details]
typescript.txt

Comment 4 loic 2008-09-29 05:58:47 UTC
Of course the build environment was fine. As I said, setting %_fixperms solved the problem of the non-writable configure file. Thanks for your answer.


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