Bug 132636 - documentation uses topdir, but rpm does not accept the option
documentation uses topdir, but rpm does not accept the option
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
http://www.rpm.org/max-rpm/s1-rpm-any...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-15 07:52 EDT by Need Real Name
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-15 08:49:02 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)

  None (edit)
Description Need Real Name 2004-09-15 07:52:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
The documentation explains to use

topdir: <path>

to set a different top directory, but rpm does not understand this, it
complains with

error: bad option 'topdir' at /home/hat/.rpmrc:356


Version-Release number of selected component (if applicable):
rpm-4.2-0.69

How reproducible:
Always

Steps to Reproduce:
1. echo "topdir: /home/blabla/mydir" > ~/.rpmrc
2. rpm -i <something>
3. Observe the output of the rpm command
    

Actual Results:  it does not work !!
:-)

rpm switches to the default /usr/src/redhat but I have no write access
there, so the install fails

Expected Results:  It should have used /home/blabla/mydir as top
directory for the rpm command

Additional info:

There is no entry for reporting bugs in documentation in this bugzilla
instance
Comment 1 Paul Nasrat 2004-09-15 08:37:57 EDT
This has already been fixed in CVS.  Unfortunately the site hosting
the newer copy is down atm.  I'll update www.rpm.org with the latest
working copy also.

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