Dne 30. 11. 20 v 13:44 Neal Gompa napsal(a): > Then that's easy: we define a list of packages that are needed to get > the package manager working, and Koji would just download and unpack > them with no script execution, then it would manually run some > predefined scripts and invoke the package manager after that.
That is not needed. This: config_opts['update_before_build'] = True config_opts['dnf_install_command'] = '--help' config_opts['use_bootstrap'] = True config_opts['use_bootstrap_image'] = True config_opts['bootstrap_image'] = 'fedora:rawhide' The last 3 lines enables this feature: https://github.com/rpm-software-management/mock/wiki/Feature-container-for-bootstrap Then config_opts['dnf_install_command'] = '--help' just shortcut dnf install dnf dnf-plugins-core after downloading the image. It is there just to make sure that we have DNF in that container and not just microdnf. Rawhide image has it there. So this step is redundant. Fedora-infra will need whitelist fedora registry on Koji builders so they are network reachable. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys _______________________________________________ buildsys mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
