Re: how to kill a long awaiting build

2015-03-30 Thread Mikolaj Izdebski
possible to cancel builds that haven't been started yet. -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk ___ copr-devel mailing list copr-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/copr-devel

| Re: Fork "from" or "to" rawhide?

2016-10-06 Thread Mikolaj Izdebski
hat his package doesn't build anymore. Sounds like you are asking for Koschei for Copr. We are working on first bits of integration right now. See: https://github.com/msimacek/koschei/issues/113 -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk ___

Re: New COPR version deployed

2016-09-20 Thread Mikolaj Izdebski
On 09/20/2016 11:33 AM, Michal Novotny wrote: > - mock build configs are now available in the result directories (under > ./configs) Great! That made it possible for me to debug an issue related to custom chroots. Proposed fix submitted as https://github.com/fedora-copr/copr/pull/15 -- M

| Re: Loading changes to an own Copr project

2016-11-17 Thread Mikolaj Izdebski
es, then rebuild by command line > like happens with Fedora packages. 1. Set up your own git repository (for example on Github) with spec 2. Add package to Copr project 3. Select the source type - "Mock SCM" and configure it 4. From now on you can run builds using copr-cli 5. Optiona

| Re: Fork "from" or "to" rawhide?

2016-10-11 Thread Mikolaj Izdebski
if some dependency changed). Since there are no scratch builds in Copr, "testing builds" need to be simulated by building in separate Copr project, with appropriate repos added and createrepo disabled. Doing "real builds" is almost the same thing. -- M

Re: Determine root.log vs build.log failures

2019-04-26 Thread Mikolaj Izdebski
koji really does some log analysis, I'd love to review "backport" > pull-request of the same logic. Or at least fill an issue. The logic used by Koji is simple: if mock exits with status code 1 then it's "build.log". Otherwise (t