This feature is not enabled by default right now. If you want to enable it you can use --bootstrap-chroot command-line option or set config_opts['use_bootstrap_container'] = True in your configuration.
This has worked for many years, but with mock-2.0-2.fc31.noarch, I get:
Errors during downloading metadata for repository 'jerry':
- Curl error (37): Couldn't read a file:// file for file:///home/jjames/yum/33/x86_64/Packages/repodata/repomd.xml [Couldn't open file /home/jjames/yum/33/x86_64/Packages/repodata/repomd.xml]
Error: Failed to download metadata for repo 'jerry': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
The man page is not revealing what changed, or what I need to do to make this work again. I'm sure I'm not the only packager with a private repository, so if this needs to be done differently now, i think attention should be drawn to the new way of configuring mock. The path that curl is complaining about does exist, but is only readable by me and privileged processes. What user needs ACLs to that path to keep this working?
I'm not going to give negative karma, because this update is important, but it does break a workflow that I use frequently.
The trick is to make baseurl=file://<path>. The file:// prefix has never been necessary before, and the error message includes it, which is quite misleading.
@mooninite, I'm going to push this to stable as soon as possible, this turned out to be important update.
I set the high karma limit because I didn't want to get this merged sooner than I test several other things.
@jjames, thanks for the note. I remember I tried the variant without file:// prefix, and that didn't seem
to work for me even with old mock.... I'll try.
For some reason, all lines after INFO buildroot.py:398: Mock Version: 2.0 in root.log, lines are duplicated (in root.log after that INFO line, and all of build.log)
This update has been submitted for testing by praiskup.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
praiskup edited this update.
This update has been pushed to testing.
After trying to build something I receive this error:
Example command:
mock -r epel-8-x86_64 --rebuild ~/rpmbuild/SRPMS/ImageMagick-6.9.10.91-1.fc31.src.rpmBodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
praiskup edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by praiskup.
praiskup edited this update.
praiskup edited this update.
@elxreno, thank you for the feedback, I attached new build with fix.
praiskup edited this update.
Now it works for me. Thanks for the fix!
@praiskup I'm not sure, but maybe bootstrap feature should be disabled by default? Source: https://github.com/rpm-software-management/mock/wiki/Feature-bootstrap
It was long term plan to flip the default. So we need to fix the wiki page now actually, thanks for the hint and testing.
Ah, thanks for the wiki edit!
LGTM. But still experiencing #1754807 (not Mock bug). Only works with
--old-chroot(now--isolation=simple).Kernel 5.5.2This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Went here to report the same problem with epel8, updated. It fixed the problem. Otherwise so far so good. Thanks.
Works
Works for me!
Without this update mock rawhide builds are broken.
It works for me. Mock build on rawhide works without a problem with this update. Thank you!
LGTM
praiskup edited this update.
Working great. Thanks!
You want 15 +1s? Really? OK... and the custom update name? :(
I have a custom mock config which is a copy of /etc/mock/fedora-rawhide-x86_64.cfg with this added to the end:
This has worked for many years, but with mock-2.0-2.fc31.noarch, I get:
The man page is not revealing what changed, or what I need to do to make this work again. I'm sure I'm not the only packager with a private repository, so if this needs to be done differently now, i think attention should be drawn to the new way of configuring mock. The path that curl is complaining about does exist, but is only readable by me and privileged processes. What user needs ACLs to that path to keep this working?
I'm not going to give negative karma, because this update is important, but it does break a workflow that I use frequently.
The trick is to make
baseurl=file://<path>. Thefile://prefix has never been necessary before, and the error message includes it, which is quite misleading.Works for me. I can now enable and use the EL8
epel-modularrepo.@mooninite, I'm going to push this to stable as soon as possible, this turned out to be important update. I set the high karma limit because I didn't want to get this merged sooner than I test several other things.
@jjames, thanks for the note. I remember I tried the variant without
file://prefix, and that didn't seem to work for me even with old mock.... I'll try.@jjames I created this for now https://github.com/rpm-software-management/mock/issues/480
Works for me!
This update has been submitted for stable by praiskup.
For some reason, all lines after
INFO buildroot.py:398: Mock Version: 2.0in root.log, lines are duplicated (in root.log after that INFO line, and all of build.log)This update has been pushed to stable.