Bug 1165778 - fedpkg mockbuild doesn't work with mock-1.2
Summary: fedpkg mockbuild doesn't work with mock-1.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-19 16:52 UTC by Michael Simacek
Modified: 2015-01-06 02:07 UTC (History)
8 users (show)

Fixed In Version: mock-1.2.3-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-12 04:07:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Simacek 2014-11-19 16:52:24 UTC
Description of problem:
fedpkg mockbuild doesn't work with mock-1.2

Version-Release number of selected component (if applicable):
mock-1.2.1-1.fc20.noarch

How reproducible:
always

Steps to Reproduce:
1. fedpkg clone rnv
2. cd rnv
3. fedpkg mockbuild

Actual results:
Wrote: /home/msimacek/pkgs/rnv/rnv-1.7.11-7.fc22.src.rpm
ERROR: Bad macros 'config_opts['macros']['%distribution'] = ['None']'
Could not run mockbuild: Command '['mock', '--configdir', '/tmp/fedora-devel-x86_64.4xNqy6mockconfig', '-r', 'fedora-devel-x86_64', '--resultdir', '/home/msimacek/pkgs/rnv/results_rnv/1.7.11/7.fc22', '--rebuild', '/home/msimacek/pkgs/rnv/rnv-1.7.11-7.fc22.src.rpm']' returned non-zero exit status 5

Expected results:
It should build the package.

Additional info:
I already commented on this before mock was released on rhbz#1160765 where the bug was introduced (and marked as feature)

Comment 1 Miroslav Suchý 2014-11-20 13:44:33 UTC
Fixed in commit 1d2d247

Comment 2 Alexander Kurtakov 2014-12-03 08:13:34 UTC
Is there update for F21 pending?

Comment 3 Miroslav Suchý 2014-12-03 08:44:05 UTC
No. But I plan to do new release soon (in few days).

Comment 4 Alexander Kurtakov 2014-12-03 08:48:27 UTC
(In reply to comment #3)
> No. But I plan to do new release soon (in few days).
Which will be pushed to F21?

Comment 5 Fedora Update System 2014-12-04 12:06:33 UTC
mock-1.2.3-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/mock-1.2.3-1.fc21

Comment 6 Fedora Update System 2014-12-04 12:10:03 UTC
mock-1.2.3-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/mock-1.2.3-1.fc20

Comment 7 Fedora Update System 2014-12-04 12:11:00 UTC
mock-1.2.3-1.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/mock-1.2.3-1.el7

Comment 8 Fedora Update System 2014-12-04 12:12:28 UTC
mock-1.2.3-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/mock-1.2.3-1.el6

Comment 9 Fedora Update System 2014-12-05 00:46:43 UTC
Package mock-1.2.3-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mock-1.2.3-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-16285/mock-1.2.3-1.fc21
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2014-12-12 04:07:26 UTC
mock-1.2.3-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2014-12-17 04:42:30 UTC
mock-1.2.3-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2015-01-06 02:06:14 UTC
mock-1.2.3-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.

Comment 13 Fedora Update System 2015-01-06 02:07:38 UTC
mock-1.2.3-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.


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