Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (knot-resolver) Fails To Install in Fedora 37: can't install knot-resolver: - nothing provides libknot.so.13()(64bit) needed by knot-resolver-5.7.0-2.fc37.x86_64 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. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-37-x86_64 --config-opts mirrored=False install knot-resolver 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!
I'm seeing this in f37, Problem 1: package knot-resolver-5.7.0-2.fc37.x86_64 from @System requires libknot.so.13()(64bit), but none of the providers can be installed - cannot install both knot-libs-3.3.0-1.fc37.x86_64 from updates and knot-libs-3.2.9-1.fc37.x86_64 from @System - cannot install both knot-libs-3.3.0-1.fc37.x86_64 from updates and knot-libs-3.2.1-1.fc37.x86_64 from fedora - cannot install the best update candidate for package knot-resolver-5.7.0-2.fc37.x86_64 - cannot install the best update candidate for package knot-libs-3.2.9-1.fc37.x86_64 I think this means that knot-resolver has to be rebuilt so it becomes dependent on the 3.3 version of knot-libs. In a way, this doesn't make sense, unless there was a soname bump between 3.2.9 and 3.3.0.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 4+ weeks. This is the second reminder (step 4) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
I don't know what this was about but I've submitted Fedora Multi-Build Update with both new knot-3.3.0 and knot-resolver-5.7.0-2 rebuilt against it: https://bodhi.fedoraproject.org/updates/FEDORA-2023-40a88fead0 I'm able to install knot-resolver-5.7.0-2.fc37.x86_64 in Fedora 37 docker image and in a VM so I'm closing this.
The Multi-Build Update contains: - knot-resolver-5.7.0-2.fc37.x86_64 which requires libknot.so.13()(64bit) - knot-libs-3.3.2-1.fc37.x86_64 which provides libknot.so.14()(64bit) Hence, the first package cannot be installed together with the other. The reason you can install knot-resolver-5.7.0-2.fc37.x86_64 in a Fedora 37 docker image is because it pulls knot-libs-3.2.1-1.fc37.x86_64 from the "fedora" repository. This does not work in the Koji buidlroot, where only the latest versions are available.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This package has been orphaned. You can pick it up at https://src.fedoraproject.org/rpms/knot-resolver by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ All subpackages of a package against which this bug was filled are now installable or removed from Fedora 37. Thanks for taking care of it!