Although most of the people may consider it obvious, I'd like to see the description of the config_opts['target_arch'] option somewhere in an official documentation. So far, if my program uses Mock, the only thing I can tell about one of its options is that it sets the value of "config_opts['target_arch']". This is not very user-friendly.
Let's make the request broader. I miss the documentation of at least these options: config_opts['root'] config_opts['target_arch'] config_opts['yum.conf']
*** Bug 1230749 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
I commit 27d1518 I added: +# Contains content of yum.conf or dnf.conf. If DNF is used and dnf.conf is not set, then content of yum.conf is +# used to populate dnf.conf # config_opts['yum.conf'] = '' # or # config_opts['dnf.conf'] = ''
Could it be the whole path (e.g. $CHROOT/etc/yum/yum.conf), please?
In commit e9f16de I added: +# Mock will set architecture to 'target_arch' using personality(2) syscall. # config_opts['target_arch'] = 'i386' +# When host system architecture is not in 'legal_host_arches' list, mock will refuse to switch to +# 'target_arch' and will raise error. +# config_opts['legal_host_arches'] = ('i386', 'i586', 'i686', 'x86_64')
(In reply to Radek Holy from comment #5) > Could it be the whole path (e.g. $CHROOT/etc/yum/yum.conf), please? Clified in commit 8e546e1
Thank you! Looks good so far!
mock-1.2.12-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mock-1.2.12-1.fc21
mock-1.2.12-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/mock-1.2.12-1.fc22
mock-1.2.12-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.12-1.el6
mock-1.2.12-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.12-1.el7
Package mock-1.2.12-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mock-1.2.12-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-7359/mock-1.2.12-1.el6 then log in and leave karma (feedback).
So, you are not going to document the 'root' option? I have no idea what could 'name-of-yum-build-dir' mean.
mock-1.2.12-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.12-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.12-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.12-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.