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 227816 - mock can't use alternate config path properly
Summary: mock can't use alternate config path properly
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora Hosted Projects
Classification: Retired
Component: mock
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Clark Williams
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-02-08 12:48 UTC by Paul W. Frields
Modified: 2013-01-10 04:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-08 15:45:06 UTC


Attachments (Terms of Use)
Patch to correct attribute error (deleted)
2007-02-08 12:48 UTC, Paul W. Frields
no flags Details | Diff

Description Paul W. Frields 2007-02-08 12:48:04 UTC
Description of problem:
When I set --configdir mock produces an error (see below).


Version-Release number of selected component (if applicable):
0.6.10-1

How reproducible:
Every time

Steps to Reproduce:
1. mock --configdir=$HOME -r '<some_cfg_name>' <my.src.rpm>

  
Actual results:
Traceback (most recent call last):
  File "/usr/bin/mock", line 995, in ?
    main()
  File "/usr/bin/mock", line 941, in main
    if config_path != "/etc/mock" and os.file.exists("/etc/mock/defaults.cfg"):
AttributeError: 'module' object has no attribute 'file'


Expected results:
Working.

Additional info:
Patch attached, just a simple attribute error.

Comment 1 Paul W. Frields 2007-02-08 12:48:05 UTC
Created attachment 147651 [details]
Patch to correct attribute error

Comment 2 Clark Williams 2007-02-08 15:45:06 UTC
I ran in to this yesterday and the pending 0.6.11 release should fix it.


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