--bootstrap-chroot --yum fails with EL8
#233
Labels
Comments
|
The correct thing in this case would be allow using |
|
This bug was reported for rhel-8-beta. I'd encourage testing it with rhel-8, or with centos-8 as soon as that is published. |
|
In the end I just ported the entire dnf stack to Debian to allow rhel8 work |
|
It really needs to go in the /etc/mock/*.conf files on different distribubuted .conf files, as needed. There is a sample in https://github.com/nkadel/mockrepo/blob/master/mock-core-configs-srpm/mock-core-configs.spec , lines 56 to 63. |
|
Automatic activation of the bootstrap is in #329 |
|
Sorry, I meant to say the "/etc/mock/.cfg" or now "/etc/mock/.tpl" files. mock works fine locally compiled on rhel-8 now, with no need for the "--bootstrapm-chroot --yum" option. I tested that 2 days ago with an up-to-date mock and mock-core-configs build. |
There are epel8 builds now. |
|
Yuu still need these lines added to centos-8.tpl for compilation to work well on CentOS 7 or CentOS 6 The dnf available on CentOS 7 is not complete enough for mock to use it dorectly for building Fedora or RHEL 8 packages. |
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 14, 2019
This is likely a bug caused by the fact that `--yum` option tells: 1. to use /bin/yum on host to install bootstrap 2. to install /bin/yum inside bootstrap to install normal chroot. The problem of 1. is that a) in el8-bootstrap is that yum.rpm is not easily installable (see rpm-software-management#233) and b) that user typically doesn't want to use /bin/yum in bootstrap to install dnf-capable system. So 1. and 2. are two orthogonal things, and we should have two config options for this (or use --yum only to affect host pkg manager decision). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 15, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 15, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 15, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 27, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 27, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 27, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
praiskup
added a commit
to praiskup/mock
that referenced
this issue
Nov 29, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (rpm-software-management#233). Fixes: rpm-software-management#233
xsuchy
pushed a commit
that referenced
this issue
Nov 29, 2019
Previously we only warned when 'dnf' was expected for chroot initialization, but wasn't available. Now we detect this situation also for other package managers (e.g. missing /bin/yum, etc.). When installing bootstrap chroot, we aren't anymore that much picky about host pkg manager. This means that '/bin/yum' doesn't have to be installed at all on host to install yum-based bootstrap, but more importantly '/bin/dnf' doesn't have to exist on YUM based hosts when installing DNF based chroots. This should demotivate users from using '--yum' option on YUM based options to install bootstrap (#233). Fixes: #233
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
--bootstrap-chroot --yumought to allow for working around distributions whereyumon its own fails (i.e. distributions with rich dependencies), butdnfis not available on the host OS (for example, on Debian derivatives where nodnfpackage exists).In the case of RHEL 8, using the config file from https://github.com/rpm-software-management/mock/blob/devel/mock-core-configs/etc/mock/rhelbeta-8-x86_64.cfg errors out:
The
yumfailure comes fromyum.rpmcontaining a symlinketc/yum/pluginconf.d -> etc/dnf/plugins, butetc/yum/pluginconfig.dalready exists as a directory courtesy ofmock/mock/py/mockbuild/package_manager.py
Line 261 in 0f8acb8
I'm trying to determine how to detect the case where RHEL 8 is being installed, and special case it.
The text was updated successfully, but these errors were encountered: