Mock 4+ no longer uses the DNF config shipped in bootstrap_image #1088
Comments
kdudka
changed the title
mock-4.0 with certain configurationmock-4.0 with certain configurations
|
Thank you for the report! I did not realize this issue before. The point of bootstrap chroot is (historically) to make it as close as Here we use The mock v4.0 process fails here of course because we try to install EL8 packages Now I'm not sure. We either can document this as a known thing, or we can |
|
Thanks for the quick reply on this! I think you are right. It is a bad idea to use the |
|
I am still testing it with the other mock configs. |
|
Thank you for the research here. Does it make sense to experiment with older images like |
|
I was able to bootstrap the |
|
There are two things we could do to solve all potential issues. And both IMO seems worth implementing.
Option 1. is not as trivial to implement as it sounds. There are several layers of abstraction Option 2. seems a bit easier at first sight, we would simply stop doing Both those options seem complementary. Also, there is yet another option, we could experiment with and document some bootstrap-specific |
With
I namely think about the |
praiskup
changed the title
mock-4.0 with certain configurations
|
Similar problems with openSUSE Tumbleweed i686: |
|
Sounds like great news. Thank you for working on it, Pavel! If any testing is needed from the OpenScanHub team, please let me know. |
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
|
I realized that So, for the RHEL 8+ case, using ubi, #1126 should help by actually "doing nothing" with DNF in the bootstrap chroot. |
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
There's a new option config_opts['bootstrap_image_ready'] which, if set, causes that Mock doesn't try to install any tooling into it (silently expecting that 'dnf' and 'dnf builddep' works inside). Turns out that e.g. the ubi8 and ubi9 images have the 'builddep' command installed by default, therefore we can turn this option ON by default. Fixes: rpm-software-management#1088
Short description of the problem
After upgrading to
mock-4.0,mock --initfails for a configuration that worked fine withmock-2.16on the same host.Output of
rpm -q mockmock-4.0-1.fc37.noarch
Steps to reproduce issue
The second command fails with :
This is the configuration file:
I think it is related to pull request #1073, which is the reason why we updated to
mock-4.0on OpenScanHub workers. Thank you for working on it!The text was updated successfully, but these errors were encountered: