For the repository:
I changed the default branch from `master` to `main`.
git checkout main
in your clone to reflect this change.
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
I was wondering whether it might be possible to use microdnf instead of dnf in
the boostrap mock chroots. Since dnf depends on Python, using the boostrap mode
now complicates upgrading Pythons to a newer version.
Basically, if/when Koji uses the bootstrap mock mode, as soon as we start
bootstrapping (different meaning) Python in a side tag, dnf becomes temporarily
uninstallable in that side tag and we can no longer do any builds.
This can be worked around by not using the boostrap mock option in Koji (ideally
only for Python upgrade side tags, but I am not yet sure if that's possible), or
by eliminating Python libraries out of the bootstrap chroot, hence the idea
about using microdnf.
I've started with this config:
config_opts['root'] = 'fedora-rawhide-microdnf'
config_opts['package_manager'] = 'dnf'
config_opts['dnf_command'] = '/usr/bin/microdnf'
config_opts['dnf_install_command'] = 'install microdnf'
config_opts['system_dnf_command'] = '/usr/bin/dnf'
config_opts['dnf_common_opts'] = ['--allowerasing']
But it fails pretty soon with:
error: (--setopt) Unknown tsflag: nocontexts
And when I patch that option out, I still get:
error: The "--installroot" argument must be used together with "--config",
"--noplugins", "--setopt=cachedir=<path>", "--setopt=reposdir=<path>",
But I guess that if I figure the right options for dnf_common_opts, this might
work...? Is there some crucial functionality that microdnf might be missing that
would prevent it from creating mock chroots like this?
> Today there will be a Copr outage starting at:
> $ date --date '2020-12-01 13:00 UTC'
The outage is over now. So, on Dec 01 2020, a new Copr (rather small) release
landed production. The list of user visible changes is in the release notes