Bug 242167 - autocache generates stack trace
autocache generates stack trace
Status: CLOSED DUPLICATE of bug 242162
Product: Fedora
Classification: Fedora
Component: mock (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-01 18:18 EDT by Wart
Modified: 2013-01-09 20:38 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-02 20:38:11 EDT
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 Wart 2007-06-01 18:18:48 EDT
Description of problem:
Using the --autocache option with mock in F7 generates a python stack trace.  To
my untrained eye, it appears that the yum.conf symlink is unpacked as part of
the autocache, and then mock tries to create it a second time after unpacking
the cached root.
[rpmbuild@owl ~]$ time mock -r core7-64 --autocache
This may take a while
unpack cache
Traceback (most recent call last):
  File "/usr/bin/mock", line 1046, in <module>
  File "/usr/bin/mock", line 1043, in main
    do_rebuild(config_opts, srpms)
  File "/usr/bin/mock", line 910, in do_rebuild
  File "/usr/bin/mock", line 254, in prep
  File "/usr/bin/mock", line 659, in _prep_install
    os.symlink('../yum.conf', os.path.join(yumdir, 'yum.conf'))
OSError: [Errno 17] File exists

real    0m20.154s
user    0m7.986s
sys     0m7.151s

Version-Release number of selected component (if applicable):
Comment 1 Julian Sikorski 2007-06-02 20:38:11 EDT

*** This bug has been marked as a duplicate of 242162 ***

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