On 11/11/2016 07:00 PM, Miroslav Suchý wrote:
Dne 10.11.2016 v 13:00 Chenxiong Qi napsal(a):
> There is a difference result in copr build. In build, the RPM is
> placed to package repository root directory directly.
> Wrote: /tmp/rpkg-commands-tests-cloned-o2Dtnc/docpkg-1.2-2.el6.x86_64.rpm
> But, in my development machine running Fedora 23, the RPM is placed into
> an arch directory, e.g.
How do you build the package. I suspect that you are calling `rpmbuild`
command. You should use `mock`. This is wrapper around rpmbuild, which
create reproducible builds.
Yes, rpmbuild is called, but from rpkg local command. I wrote some test
cases for rpkg local command, each of the cases does following two steps
1. invoke local command
2. verify the outcome, e.g. verify the existence of built RPMs
local command calls rpmbuild under the hood. There is mockbuild command
using mock, but local just uses rpmbuild to build RPMs.
Copr you `mockchain` which is wrapper around mock with some
The exact command which Copr runs is here:
[2016-11-10 09:33:29,449][ INFO][PID:24412] executing:
/usr/bin/mockchain -r /var/tmp/mockremote-g5se5/fedora-25-x86_64.cfg -l
-m '--define=copr_username lsedlar' -m '--define=copr_projectname
compose-tools' -m '--define=vendor Fedora Project COPR