Description of problem: Option --chroot (or -r) allows to specify systems to build the package. In my experience reverse option --no-chroot (or -R) would be much more useful: to build on all systems (enabled in the project), *except* specified in the command line. Version-Release number of selected component (if applicable): copr-cli-1.57-1.fc24.noarch
Thanks for the report. (In reply to Van de Bugger from comment #0) > Description of problem: > > Option --chroot (or -r) allows to specify systems to build the package. In > my experience reverse option --no-chroot (or -R) would be much more useful: > to build on all systems (enabled in the project), *except* specified in the > command line. Can you please elaborate a bit? '--no-chroot' sounds like you wanted to build for no chroot. What you talk about looks like the default copr-cli behavior (build for all chroots enabled in copr). But most likely I misinterpreted your request..
Existing options: $ copr-cli build project foo-1.1.1-1.src.rpm # Initiate build foo in ALL chroots enabled in the project settings. $ copr-cli build -r fedora-25-i386 project foo-1.1.1-1.src.rpm # Initiate build foo in ONE chroot fedora-25-i386. Desired option: $ copr-cli build -R fedora-25-i386 project foo-1.1.1-1.src.rpm # Initiate build foo in all chroots enabled in the project settings EXCEPT fedora-25-i386.
Reading your initial description again, it is clear, sorry. The `--exclude-chroot` sounds more self-descriptive (and I would rather avoid using short options). Also I would encourage to use fnmatch to support pattern matching.
> The `--exclude-chroot` sounds more self-descriptive… However, I am not aware about copr server internals. To me option --chroot is not self-descriptive and rather cryptic. I do not insist on particular option name anyway. > Also I would encourage to use fnmatch to support pattern matching. Yes, it would be nice.
(In reply to Van de Bugger from comment #4) > To me option --chroot is not self-descriptive and rather cryptic. I guess some documentation asks for a fix then, but I doubt Copr is the right place anyway - that would different issue: From `man 2 chroot`, 'chroot - change root directory'. That is rather really low level term, "syscall", used widely in Fedora and especially in `mock` (Copr is built on top of `mock` tool).
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1475134 has been marked as a duplicate of this bug. ***
Once we have fixed https://pagure.io/copr/copr/issue/1350, I think we can look at this - and enhance your proposal by bug 1475134 - so both `--chroot` and `--no-chroot` also accept patterns. Note for myself: similar thing is in GNU tar for --xattrs-include= and --xatrrs-exclude.
The `--exclude-chroot` is implemented in PR#1650 except for the pattern support, which I would like to add separately (and to the --chroot parameter as well)
The bugs related to Copr build system are now migrated to the default Copr team tracker: https://github.com/fedora-copr/copr/issues/2645