https://copr-be.cloud.fedoraproject.org/results/@rust/playground/srpm-builds/00644790/builder-live.log

Ye, it does, it does not use the same mock config as the rest but you can enable and install it manually.

@clime but I think it should. Agree?

also, enabling repositories doesn't really work...

dnf -y copr enable @rpm-software-management/with-rich-dependency
[Errno 20] Not a directory: '/dev/null/_copr_@rpm-software-management-with-rich-dependency.repo'

@clime but I think it should. Agree?

The mock chroot for srpm building is really a standalone thing at the moment and I think it might stay that way.

also, enabling repositories doesn't really work...
dnf -y copr enable @rpm-software-management/with-rich-dependency
[Errno 20] Not a directory: '/dev/null/copr@rpm-software-management-with-rich-dependency.repo'

Ah okay, that should be fixed. Could you please try with --repofrompath, just that we confirm the use-case works.

@clime but I think it should. Agree?

The mock chroot for srpm building is really a standalone thing at the moment and I think it might stay that way.

Actually, enabling project-level additional repositories might make some sense.

@clime

Ah okay, that should be fixed. Could you please try with --repofrompath, just that we confirm the use-case works.

Problem with this is that it requires playing around $releasever and rawhide, also will be broken on mageia chroots.

Actually, enabling project-level additional repositories might make some sense.

That's what I was talking, because those are enabled for RPM builds, but not the SRPM builds which is really weird.

@clime

Ah okay, that should be fixed. Could you please try with --repofrompath, just that we confirm the use-case works.

Problem with this is that it requires playing around $releasever and rawhide, also will be broken on mageia chroots.

The chroot used for this is the same as host machines' os version (see https://docs.pagure.org/copr.copr/user_documentation.html#scm). So it will work for Mageia chroots as well (mageia-macros package should be installed for building from Mageia-specific .spec files).

Actually, enabling project-level additional repositories might make some sense.

That's what I was talking, because those are enabled for RPM builds, but not the SRPM builds which is really weird.

The thing is that there are other project level settings like enable bootstrap_chroot that probably doesn't make so much sense for the initial srpm-build chroot.

The chroot used for this is the same as host machines' os version (see https://docs.pagure.org/copr.copr/user_documentation.html#scm). So it will work for Mageia chroots as well (mageia-macros package should be installed for building from Mageia-specific .spec files).

No because of the same reason: $releasever with cauldron..

The thing is that there are other project level settings like enable bootstrap_chroot that probably doesn't make so much sense for the initial srpm-build chroot.

I would argue that it should inherit same settings as RPM builder does, but for now it doesn't really matter. Using additional repositories is much bigger problem for me now.

This is not a bug. SRPM build-chroot is independent of the RPM build chroots. Adding repos might be done from within the script.