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

Could we advice the dnf5 what are the available repository fallbacks? #3470

Open
praiskup opened this issue Oct 10, 2024 · 2 comments
Open

Comments

@praiskup
Copy link
Member

At this point in time, dnf5 copr enable implements the fallback mechanism itself:
https://github.com/rpm-software-management/dnf5/blob/117bc3e552147925ac469179d4c8f79f06a1eaca/dnf5-plugins/copr_plugin/helpers.cpp#L8-L15

This is much better than with dnf4 variant, where we had to decide server-side (copr-frontend), and we didn't have good enough information about the client machine (is that Alma? is that CentOS Stream? RHEL? What user prefers?).

I'm curious if we could provide some "hint" like info in the /api_3/rpmrepo/<owner>/<project>/ call, saying that some chroots are good enough fallbacks for other chroots (like that epel-10 is a good fallback for rhel+epel-10 and vice versa).
Maybe let the Copr owner decide it.

@praiskup
Copy link
Member Author

Relates to #3469

@FrostyX
Copy link
Member

FrostyX commented Oct 11, 2024

Sounds good. Maybe we can even interactively prompt the user when enabling, to specify what alternative he wants?

Maybe let the Copr owner decide it.

IMHO probably not

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

No branches or pull requests

2 participants