The very same way I can add additional repositories into mock chroot through UI - it would be nice if I could enable concrete module stream. E.g.: - enabled modules: httpd:2.4 Note that I do not want to build module; I want to build non-modular package (shipped as separate repository) _against_ module.
(In reply to Pavel Raiskup from comment #0) > The very same way I can add additional repositories into mock chroot > through UI UI?? > E.g.: > - enabled modules: httpd:2.4 Where does this go? > Note that I do not want to build module; I want to build non-modular > package (shipped as separate repository) _against_ module. Indeed, me too.
(In reply to Jens Petersen from comment #1) > (In reply to Pavel Raiskup from comment #0) > > The very same way I can add additional repositories into mock chroot > > through UI > > UI?? Well, by that I meant CLI/config. > > E.g.: > > - enabled modules: httpd:2.4 > > Where does this go? I guess you are ask for mock, then please follow bug 1572597. Copr doesn't have this implemented, yet.
Sorry, I misinterpreted myself now :-) well you can add external repositories you build against in Copr, see `copr create --help` and the `--repo` option. Some incomplete documentation IMO is in this documentation: https://docs.pagure.org/copr.copr/user_documentation.html#can-i-depend-on-other-packages-which-are-not-in-fedora-epel
I've same issue here, I'd like to build a java package in copr requiring javapackages-local but I can't being it excluded by modular filtering. We miss a way to change the mock chroot adding something like config_opts['module_enable'] = ['javapackages-tools', 'python36'] enabling modules needed in order to perform the build.
FYI - we started working on this one. It will be done in several steps as it requires changes in frontend, backend and builder.
Fixed, per release notes: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZAHZBHXYT5VI5EIR4D7LM5IYFTS5NIE6/