Description of problem: "dnf copr enable sharkcz/talos" fails to enable that repository on ppc64le. Version-Release number of selected component (if applicable): dnf-plugins-core-4.0.11-1 How reproducible: Always Steps to Reproduce: 1."dnf copr enable sharkcz/talos" Actual results: "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/sharkcz/talos? [y/N]: y Error: This repository does not have any builds yet so you cannot enable it now." Expected results: "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/sharkcz/talos? [y/N]: y Repository successfully enabled." Additional info: I have discussed this issue with praiskup. This seems to be regression from dnf-plugins-core-4.0.9-1 which works just fine. Also this issue could be workarounded by specifying the repo explicitly like "dnf copr enable sharkcz/talos fedora-31-ppc64le"(thanks to praiskup for the workaround).
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug was accidentally closed due to a query error. Reopening.
This needs a followup patch, per discussion in https://github.com/rpm-software-management/dnf-plugins-core/pull/379
Patch was merged (https://github.com/rpm-software-management/dnf-plugins-core/pull/385).
FEDORA-2020-d51dbe83a9 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d51dbe83a9
FEDORA-2020-d51dbe83a9 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d51dbe83a9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d51dbe83a9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-d51dbe83a9 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.