This has broken other packages, e.g. https://bugzilla.redhat.com/show_bug.cgi?id=2036264 https://bugzilla.redhat.com/show_bug.cgi?id=2036263 https://bugzilla.redhat.com/show_bug.cgi?id=2036262 https://bugzilla.redhat.com/show_bug.cgi?id=2036261 https://bugzilla.redhat.com/show_bug.cgi?id=2036260 https://bugzilla.redhat.com/show_bug.cgi?id=2036259
This is not a bug in mock, but the mock-core-configs update introduced a regression for fedpkg users. As such, it should not be pushed to a stable release. Packagers who need the new features or fixes are more likely to be able to install this from updates-testing than packagers who would install this and suddenly got their EPEL 8 packaging experience broken are likely to be able to find the workaround.
fedpkg mockbuild fails on epel8 branches. For me, it fails with:
Status code: 403 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/basesystem-11-5.el8.noarch.rpm. It seems it fallbacks to Koji's mock config instead of using the installed one. And after running
ln -s /etc/mock/alma+epel-8-x86_64.cfg /home/churchyard/.config/mock/epel-8-x86_64.cfg I get the same error as reported by @gotmax23.
Note that prusa-slicer-2.3.1 update received some negative karma and I did not intend to push it stable until this is fixed. Not sure what to do here, but backward-incompatible updates that need rebuilds are generally not permitted on stable Fedora releases. I'll try to rebuild the 2.2.0 release with this and replace it here.
Adding negative karma, for now, to avoid accidental autopush.
Where can I see how the test does that? I have no idea how to deploy a server and a client. I am looking at https://fedoraproject.org/wiki/FreeIPA_step_by_step but it feels quite old and it gives very ambiguous instructions like "make sure that the host names are set properly" -- it seems I need to know what I am trying to accomplish when I want to setup FreeIPA and unfortunately I don't.