Reproducer: $ mock -r fedora-22-x86_64 --rebuild <srpm> It ends with an error caused by missing 'yum resolvedep' command, which is not part of dnf: http://dnf.readthedocs.org/en/latest/cli_vs_yum.html#no-resolvedep-command Workaround: put following line into mock config: config_opts['package_manager'] = 'dnf'
This is really unfortunate. I wonder whether we could avoid this big mistake. 1) DNF does not provide the "resolvedep" command. On the other hand, looking into the code of mock, mock does not need the command if it uses DNF. 2) YUM bumped just release number when it renamed "/usr/bin/yum" to "/usr/bin/yum-deprecated". On the other hand, I don't know whether CLI changes must be reflected in the package version somehow. I mean from point of view of version semantics. 3) Mock nevertheless requires just "yum >= 2.4" so any version change could not prevent a breakage of the affected system. 4) Neither dnf-yum nor the latest yum does Conflicts: with mock to prevent the breakage. On the other hand, neither DNF nor YUM does conflict with mock from the point of view of the Conflicts: tag. So, we should definitely let mock know about this change in advance but either doing that it could not prevent breakage of systems with an old mock and the latest YUM. Now, I can only express my apologies. Because of the reasons above, I think that the only correct solution in this situation is to fix mock so that it uses "/usr/bin/yum" if yum < 3.4.3-505 is installed and "/usr/bin/yum-deprecated" otherwise.
Yum is called on host. So this only happen if your host machine is F22+. So the solution can probably to ship config /etc/mock/site-defaults.cfg for F22+ with: config_opts['yum_command'] = '/usr/bin/yum-deprecated' Radek, yum-deprecated will be only F22+. Older Fedoras and RHELs will never get /usr/bin/yum-deprecated. Just want to make sure. Can you confirm?
(In reply to Miroslav Suchý from comment #2) > Yum is called on host. So this only happen if your host machine is F22+. > So the solution can probably to ship config /etc/mock/site-defaults.cfg for > F22+ with: > config_opts['yum_command'] = '/usr/bin/yum-deprecated' Just in case: I assume that you've noticed that the executable is called 'yum-deprecated' only with yum-3.4.3-505+. I mean e.g. this patch may break e.g. Rawhide systems with an old YUM version. But maybe it's OK to assume that no system with F22+ has yum < 3.4.3-505... Or maybe you are also going to require the newest YUM... Anyway, it's up to you. I just wanted to be sure that you've noticed that. > Radek, yum-deprecated will be only F22+. Older Fedoras and RHELs will never > get /usr/bin/yum-deprecated. Just want to make sure. Can you confirm? Yes, that's the plan, AFAIK.
Yes, config_opts['yum_command'] = '/usr/bin/yum-deprecated' do that job. Fixed in: * 0e41ca4 on F22+ use yum-deprecated instead of yum [RHBZ#1211978]
*** Bug 1210398 has been marked as a duplicate of this bug. ***
*** Bug 1208912 has been marked as a duplicate of this bug. ***
*** Bug 1213859 has been marked as a duplicate of this bug. ***
Why don't we fix mock to use dnf instead of yum? The whole point of deprecating yum is that things aren't supposed to use it any more, not just that they switch over to use the yum-deprecated command.
Because it is not easy. We already switched mock to use DNF for rawhide (F23+). We decided (after lot of discussion) to *not* use DNF for F22 because all F22 packages was already built by yum, so it can bring some regression and unexpected differences (koji use yum, local builds using mock would use DNF). Therefore we - just after branching of F23 - switched mock to use DNF for mock. Just to have some initial feedback before we deploy that change on Koji. And the plan is (pretty soon) start building F23 using DNF on Koji too. The presence of /usr/bin/yum-deprecated in F22 was quite unexpected (to me). Therefore this bug. I am working on other mock bugs right now and I expect new mock release within one week.
*** Bug 1214432 has been marked as a duplicate of this bug. ***
*** Bug 1214902 has been marked as a duplicate of this bug. ***
*** Bug 1216164 has been marked as a duplicate of this bug. ***
Discussed at the 2015-04-28 blocker review meeting.[1] Voted as RejectedBlocker. We're not aware of any case where this bug affects release-critical or critpath components, so it could be fixed as a regular update if necessary. [1]: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-28/
mock-1.2.8-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc22
mock-1.2.8-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc21
mock-1.2.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc20
mock-1.2.8-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.8-1.el7
mock-1.2.8-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.8-1.el6
Package mock-1.2.8-1.el7: * should fix your issue, * was pushed to the Fedora EPEL 7 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.8-1.el7' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-6057/mock-1.2.8-1.el7 then log in and leave karma (feedback).
*** Bug 1217700 has been marked as a duplicate of this bug. ***
mock-1.2.8-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.8-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.10-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.10-1.el7
mock-1.2.10-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.10-1.el6
mock-1.2.10-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.10-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.