Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (ansible-collection-community-kubernetes) Fails To Install in Fedora 36: can't install ansible-collection-community-kubernetes: - nothing provides ansible-collection(kubernetes.core) >= 2.0.0 needed by ansible-collection-community-kubernetes-2.0.1-1.fc36.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
Hello, This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
Hello, This is the second reminder (step 4 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
I can try and take a look into this one...
So, this is because the collection has moved/renamed itself and it was my fault for updating it. ;) So, we need a package rename here. ;(
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
Hello, are there any updates on this issue? We are currently hitting this problem with ansible-collection-community-kubernetes-2.0.1-2.fc36.noarch and it's at the point where it's blocking us from updating to a new Fedora version :(
I've not had time to rename this collection. ;( Perhaps Maxwell G has some cycles for it? (adding to cc)
*** Bug 2031768 has been marked as a duplicate of this bug. ***
FEDORA-2022-b8ad3b3961 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8ad3b3961
FEDORA-2022-b8ad3b3961 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-1f4e043f75 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1f4e043f75
FEDORA-2022-1f4e043f75 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1f4e043f75` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1f4e043f75 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-1f4e043f75 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.