@@ -881,9 +881,13 @@ mailing list.
881881To give you flexibility in what distributions you want to target with your EPEL builds,
882882Packit provides these aliases :
883883
884- * `epel-X` — the current/leading minor release (e.g. `epel10`)
885- * `epel-X-branched` — the branched/trailing minor release (e.g. `epel10.0`)
886- * `epel-X-all` — both minor releases (e.g. `epel10`, `epel10.0`)
884+ * `epel-X` — the current/leading minor release, e.g.:
885+ - ` epel10` in dist-git and Koji
886+ - ` epel-10` in mock and Copr
887+ * `epel-X-branched` — the branched/trailing minor release, e.g.:
888+ - ` epel10.0` in dist-git and Koji
889+ - ` rhel+epel-10` in mock and Copr
890+ * `epel-X-all` — both minor releases
887891
888892:::note
889893
@@ -893,8 +897,31 @@ The `epel-all` alias includes all active minor versions of all active major EPEL
893897
894898:::info
895899
896- For Copr builds all EPEL 10 minor version aliases are currently mapped to the `epel-10` target.
897- This is subject to change.
900+ Unlike `epel-10`, which is mapped to `CentOS-Stream-10` Testing Farm compose by default,
901+ there is no default mapping for the `rhel+epel-10` Copr chroot. You have to specify
902+ a compose explicitly, e.g. :
903+
904+ ` ` `
905+ targets:
906+ rhel+epel-10-x86_64:
907+ distros: [CentOS-Stream-10]
908+ ` ` `
909+
910+ or :
911+
912+ ` ` `
913+ use_internal_tf: true
914+ targets:
915+ rhel+epel-10-x86_64:
916+ distros: [RHEL-10.0-Nightly]
917+ ` ` `
918+
919+ :: :
920+
921+ :::warning
922+
923+ Be aware that there is currently a Testing Farm [issue](https://gitlab.com/testing-farm/general/-/issues/74)
924+ that prevents installing Copr builds from chroots with `+` in their name, including `rhel+epel-10`.
898925
899926:: :
900927
0 commit comments