Add AlmaLinux 10 configs#1586
Conversation
|
Also, running: Fails with: I guess it's because it's not pulling the x86_64_v2 image from dockerhub (is it even available?). Maybe for that use case would be beneficial to drop the usage of the bootstrap image. |
The v2 arch is set to not use docker/quay base images because there's not a way (that I'm aware of) in mock to properly point it at the x86_64_v2 variant so on v3 hosts it would just pull the x86_64 images (v3) which would produce unexpected results (ie, not proper v2 builds). |
|
The CI failure looks unrelated to this PR. |
|
A new release of distribution-gpg-keys needs to be made and mock-core-configs needs to be bumped to require it. |
|
Can you squash this into one commit? Then the only thing missing is @xsuchy making a distribution-gpg-keys release and shipping it to Fedora so the dependency in the mock-core-configs spec can be bumped. |
I figured it would get squashed on merge, but I can. |
|
We do rebase merging in this project exclusively, so you need to do your own squashing. |
All squashed. |
|
Testing farm is failing for x86_64_v2, can you double-check this is OK? |
|
We need to let this one finish, and then re-trigger CI: |
|
/packit build |
1 similar comment
|
/packit build |
|
Argh, sorry! I meant to submit the bulid here: https://copr.fedorainfracloud.org/coprs/build/9137091 |
|
/packit build |
|
Would you mind rebasing one last time, against current |
The rpm-software-management#1586 introduced broken config files: $ mock -r alma-kitten+epel-10-x86_64_v2 --scrub=all ERROR: Could not find included config file: /etc/mock/almalinux-kitten-10-x86_64_v2.cfg It doesn't make sense to skip the testing in this situation.
The #1586 introduced broken config files: $ mock -r alma-kitten+epel-10-x86_64_v2 --scrub=all ERROR: Could not find included config file: /etc/mock/almalinux-kitten-10-x86_64_v2.cfg It doesn't make sense to skip the testing in this situation.
4 participants
No description provided.