Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

epel-10-x86_64 mock config mismatch #3560

Closed
carlwgeorge opened this issue Dec 20, 2024 · 2 comments
Closed

epel-10-x86_64 mock config mismatch #3560

carlwgeorge opened this issue Dec 20, 2024 · 2 comments

Comments

@carlwgeorge
Copy link

In a newly created copr, I enabled the epel-10-x86_64 chroot and attempted a build. This same build worked for me locally with mock-core-configs-41.5-1.fc41, but it failed in copr. The log file indicates a 404 error trying to ask mirrormanager for https://mirrors.fedoraproject.org/metalink?repo=epel-&arch=x86_64 (note the missing version on the repo parameter). I downloaded the build configs, and noticed something strange.

It appears to be using epel-10.tpl from mock-core-configs-41.5-1, but centos-stream-10.tpl from mock-core-configs-41.4-1. In rpm-software-management/mock@a80df1c (part of mock-core-configs-41.5-1, but not mock-core-configs-41.4-1) we defined the jinja variable releasever_major and use it in the EPEL metalink. Having a mismatch between those files results in the variable being undefined.

@github-project-automation github-project-automation bot moved this to Needs triage in CPT Kanban Dec 20, 2024
ryanlerch pushed a commit to fedora-infra/ansible that referenced this issue Dec 21, 2024
Use the config from mock-core-configs.

Fixes: fedora-copr/copr#3560
Reverts: 2528d84
@praiskup
Copy link
Member

Ah, forgotten work-arounds from early days... should be fixed now:
https://pagure.io/fedora-infra/ansible/c/8cdb4e1fbdfac269b4fb81c6afc9c3c00d40d6f1
Thank you for the report!

@carlwgeorge
Copy link
Author

Thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs triage
Development

No branches or pull requests

2 participants