We'd like to enable aarch64 builds for the hyperscale SIG. I believe this is a full list of our tags. Thanks!
hyperscale8s-packages-experimental-candidate hyperscale8s-packages-experimental-el8-build hyperscale8s-packages-experimental-release hyperscale8s-packages-experimental-testing hyperscale8s-packages-facebook-candidate hyperscale8s-packages-facebook-el8-build hyperscale8s-packages-facebook-release hyperscale8s-packages-facebook-testing hyperscale8s-packages-hotfixes-candidate hyperscale8s-packages-hotfixes-el8s-build hyperscale8s-packages-hotfixes-release hyperscale8s-packages-hotfixes-testing hyperscale8s-packages-main-candidate hyperscale8s-packages-main-el8-build hyperscale8s-packages-main-release hyperscale8s-packages-main-testing hyperscale8s-packages-spin-candidate hyperscale8s-packages-spin-el8s-build hyperscale8s-packages-spin-release hyperscale8s-packages-spin-testing hyperscale8s-spin_media-experimental-candidate hyperscale8s-spin_media-experimental-el8s-build hyperscale8s-spin_media-experimental-release hyperscale8s-spin_media-experimental-testing hyperscale8s-spin_media-main-candidate hyperscale8s-spin_media-main-el8s-build hyperscale8s-spin_media-main-release hyperscale8s-spin_media-main-testing
Metadata Update from @humaton: - Issue tagged with: cbs, low-gain, low-trouble
We can of course add it, but just be aware that existing ENVR can't be easily rebuilt (as mentioned previously : https://pagure.io/centos-infra/issue/208#comment-713769) and it was x86_64 only per ticket/request (https://pagure.io/centos-infra/issue/373) If you confirm that you'll only submit newer ENVR and don't expect previous ones to show up, I'll proceed
Metadata Update from @arrfab: - Issue assigned to arrfab
Yeah this is fine. Our plane is to bump all packages and submit new builds once the new architecture is added.
It's now added to all hyperscale8s tags, so closing. One remark : in case you don't bump envr and needs to rebuild same envr but for aarch64, koji will complain that such build already exists. There is a way to still do that but you have to build with --scratch option, and give us taskid and we can call (admin right) a koji api endpoint to merge the existing build and the scratch one into one (in case of) : it's tedious but can work if really needed
--scratch
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.