1/ We need to rebuild :
https://koji.mbox.centos.org/koji/buildinfo?buildID=2651
for all supported distributions.

In CBS configuration, today the easier would be to build/tag it to the buildsysX tags.

2/ whitelist git.centos.org in kojihub

Step 1.) https://cbs.centos.org/koji/packageinfo?packageID=8196

Thanks Brian, I'll be testing on koji-dev in next days.

Due to hardware failure on the only kojid host in that dev setup, I had to redeploy quickly an old node that is now kojid/builder in cbs.dev.
That should help us testing and troubleshooting the issue with the nspawn chroot issue

Hi,

I had time today to investigate the issue with new_chroot in mock.

It is not related to koji, but rather than systemd-nspawn from el7 (systemd-219-73.el7_8.9.x86_64) not supporting the option "--chdir"

I don't remember the implications of not using new_chroot and rather stick to old_chroot in mock. Likely not many but maybe we should quickly check the impact.

The current -build tags can be (re)configured with :
koji <tag>-el8-build -x mock.new_chroot=False

Fabian, Brian,
* allowed_scm can be amended with git.centos.org:/rpms/*:no:get_sources.sh"
* create_sig.sh need to be modified to add "centpkg-minimal" in the buildroots and to set the chroot option correctly if we decide to go this way.

I'll work on the PR this week if we agree on the solution.

bug triage : closing this old one as in fact, all the work was done and documented in https://wiki.centos.org/SIGGuide , that some SIGs started to use (hyperscale SIG is pushing to git/lookaside and building from git.centos.org directly)