Hi, today we have a short but important update.
As was mention in previous mails, Copr enabled gpg signing for new
builds. During the last week all older packages were also signed.
Thus allowed us to set "gpgcheck=1" in the .repo files, so a bit more
secure packaging with Copr!
I just got done with a couple of builds for EPEL6 which I based on SRPMS
from rawhide which completed fine but the version column in both the build
and monitor screen show the Release and dist tag.
Is this expected?
Fedora 19 is EOLed. Therefore I plan to disable building for Fedora 19 in Copr by end of this month.
If want to build something for F19, you have last chance.
By end of the month new builds for F19 will not be allowed. However existing yum repos for F19 will be preserved.
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
I want to use COPR for public i686 rebuilds of CentOS 7 base, CentOS 7
updates and EPEL 7 repos but it will obviously generate a huge load on
Would it be treated as misuse of COPR or I could do anything I want?
I've already made almost complete local rebuild and just want to make
it automatic and public.