Description of problem: When using mock on an EL7 host and trying to build a Fedora 28+ chroot, the config needs to add config_opts['use_bootstrap_container'] = True Version-Release number of selected component (if applicable): mock-1.4.14-2.el7.noarch How reproducible: 100% Steps to Reproduce: 1.Install mock on an EL7 system 2.mock -r rhelbeta-8-x86_64 --init Actual results: fails due to new RPM features Expected results: Enable the bootstrap container by default for those profiles in EPEL7 Additional info:
Yes, that is true. But the solution is not easy - it will be either pain to maintain or very hard to code. The great approach - to use host configs is discussed here: https://github.com/rpm-software-management/mock/issues/199
I was thinking a fairly simple %if within the specfile.... something like %if 0%{?rhel} < 8 echo "config_opts['use_bootstrap_container'] = True" >> fedora_whatever_.cfg %endif That should keep the maintenance fairly low and provide the expected behavior.
I agree that a small loop in the .spec file is suitable. But since the problem is not merely fedora, but will also occur with rhel-8 and centos-8, it's safer to test for the "package_manager" line being "dnf" and edit the file to reset use_bootstrap_container accordingly. Piping options into the end of the .cfg file is confusing, because this starts putting options after the "yum" stanza. Definitely put it with the
Note that the spec file in question is the mock-core-config.spec file. And I meant to say: Definitely put it in all the /etc/mock/*.cfg file with the "package_manager" set to "dnf". This will also et the rhel-8 and other dnf based configs as they are published.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
FEDORA-EPEL-2020-88ef4b4d66 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-88ef4b4d66
FEDORA-2020-fba9845e22 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fba9845e22
FEDORA-2020-6b7c342fb4 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6b7c342fb4
FEDORA-2020-85df0014c1 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-85df0014c1
FEDORA-2020-fba9845e22 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fba9845e22` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fba9845e22 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-85df0014c1 has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-85df0014c1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-85df0014c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-6b7c342fb4 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-6b7c342fb4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6b7c342fb4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-88ef4b4d66 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-88ef4b4d66 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fba9845e22 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-6b7c342fb4 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-85df0014c1 has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-88ef4b4d66 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.