On Tue, Jan 19, 2016, at 08:05 AM, Nico Kadel-Garcia wrote:
> There are actually some very real security reasons not to let mock
> pull arbitrary configuration files from local directories. It would
> provide way, way too much power to the local developer to build
> arbitrary chroot cages on the
Dne 19.1.2016 v 06:51 Dmitrij S. Kryzhevich napsal(a):
> Like any others. Provide information about repo to /etc/mock/YOURCONFIG.cfg
> In most cases in would be: /etc/mock/default.cfg
>
> You could find details for your particular copr repo in file with
> corresponding name in /etc/yum.repos.d
On 19/01/16 08:05 -0500, Nico Kadel-Garcia wrote:
This has never worked. Please re-read the manual page for "mock" The
"-r config" option finds "/etc/mock/config.cfg".
The man page says:
"Optionally if CONFIG ends in '.cfg', it is interpreted as full path
to config file."
And it works fine
On Tue, Jan 19, 2016 at 4:48 AM, Miroslav Suchy wrote:
> Dne 19.1.2016 v 06:51 Dmitrij S. Kryzhevich napsal(a):
>> Like any others. Provide information about repo to /etc/mock/YOURCONFIG.cfg
>> In most cases in would be: /etc/mock/default.cfg
>>
>> You could find details for
Are there any instructions on how to use a COPR repo when testing
package builds with mock? My attempts at googling this sort of thing
didn't turn anything up.
Thanks,
Dave
Like any others. Provide information about repo to /etc/mock/YOURCONFIG.cfg
In most cases in would be:
Are there any instructions on how to use a COPR repo when testing package
builds with mock? My attempts at googling this sort of thing didn't turn
anything up.
Thanks,
Dave
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org