You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upcoming rpmdb change for Fedora 33, it is strongly recommended that Mock is used with bootstrap chroots enabled to remove the influence of the host RPM package manager on the build environment.
This ensures that macros, rpm commands, etc. all work correctly in the build environment for producing SRPMs and building RPMs. This would also make issues like handling distro-specific macros in the NEVR fields not a problem.
We could flip the default now (historically we already tried that,
but at that time bootstrap was pretty broken).
But before we do that, I'd rather wait for finishing the #1445 PR;
otherwise, we can only turn on/off bootstrap for the whole project,
not per-chroot. There used to be some strange bootstrap
installation failures for non-fedora chroots, so each chroot may
need special setup (no bootstrap, normal bootstrap or podman).
Anyone can turn the bootstrap ON even now as opt-in if necessary,
so I don't think we have to be in extreme hurry.
The text was updated successfully, but these errors were encountered:
Original issue: https://pagure.io/copr/copr/issue/1483
Opened: 2020-08-27 00:24:34
Opened by: ngompa
With the upcoming rpmdb change for Fedora 33, it is strongly recommended that Mock is used with bootstrap chroots enabled to remove the influence of the host RPM package manager on the build environment.
This ensures that macros, rpm commands, etc. all work correctly in the build environment for producing SRPMs and building RPMs. This would also make issues like handling distro-specific macros in the NEVR fields not a problem.
Koji will be switching to bootstrap chroot builds, and COPR should as well, ASAP.
praiskup commented at 2020-08-27 07:06:58:
We could flip the default now (historically we already tried that,
but at that time bootstrap was pretty broken).
But before we do that, I'd rather wait for finishing the #1445 PR;
otherwise, we can only turn on/off bootstrap for the whole project,
not per-chroot. There used to be some strange bootstrap
installation failures for non-fedora chroots, so each chroot may
need special setup (no bootstrap, normal bootstrap or podman).
Anyone can turn the bootstrap ON even now as opt-in if necessary,
so I don't think we have to be in extreme hurry.
The text was updated successfully, but these errors were encountered: