Description of problem: When adding a COPR repository using the command: dnf copr enable <user>/<project_repository> it fails with error: Error: This repository does not have any builds yet so you cannot enable it now. How reproducible: Steps to Reproduce: 1. Try to add this repository: dnf copr enable ghibo/virtualbox-6 it will end with the error above. A workaround is to provide manually the distro, e.g.: dnf copr enable ghibo/virtualbox-6 mageia-cauldron-x86_64
I can't reproduce that: [root@localhost marja]# dnf copr enable ghibo/virtualbox-6 You are about to enable a Copr repository. Please note that this repository is not part of the main distribution, and quality may vary. The Fedora Project does not exercise any power over the contents of this repository beyond the rules outlined in the Copr FAQ at <https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr>, and packages are not held to any quality or security level. Please do not file bug reports about these packages in Fedora Bugzilla. In case of problems, contact the owner of this repository. Do you really want to enable copr.fedorainfracloud.org/ghibo/virtualbox-6? [y/N]: y Repository successfully enabled. [root@localhost marja]# No idea why you had to add " mageia-cauldron-x86_64" to the command. Anyway, assigning.
Assignee: bugsquad => ngompa13CC: (none) => ignatenko, marja11
The issue is caused by the fact the /etc/os-release file no longer identifies if a Mageia release is Cauldron or Official anymore. This is a bit of a problem, as the current detection code relies on that: https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/copr.py#L414 We probably need to add a MAGEIA_ prefixed variable to os-release to identify Cauldron vs released version like Fedora did: https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/copr.py#L406