The configuration for CentOS Stream 8 was renamed in mock-core-configs so it makes more sense now (currently the updated package is getting to updates-testing), and we'll have to adjust Fedora Copr to comply with that layout. The idea now is to try script the movement on backend (built results), and create compat symlink 'centos-stream-x86_64 => centos-stream-8-x86_64'. This way new build results will be put into the new location, and old clients will be able to access old/new results. Does this make sense, or is there a better idea? >From the UI/API perspective, I believe we'll be able to migrate the existing chroot transparently without disabling old one and creating a new one. If this doesn't happen to be possible (new chroot will be needed) I'll reply here to warn you that the centos-stream buildroot needs to be re-enabled. In any case, note that the `--chroot centos-stream-x86_64` option will stop working very soon, and you should start using `--chroot centos-stream-8-x86_64`. Pavel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
