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 (r2cutter) Fails To Install in Fedora 34: can't install r2cutter: - nothing provides libr_anal.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_asm.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_bin.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_bp.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_config.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_cons.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_core.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_crypto.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_debug.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_egg.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_flag.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_fs.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_hash.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_io.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_parse.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_reg.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_search.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_syscall.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.x86_64 - nothing provides libr_util.so.5.1.1()(64bit) needed by r2cutter-0.1.1-4.fc34.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. 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!
package retired - was renamed to iaito with the relevant Obsoletes/Provides
Packages in stable releases cannot be retired :/
*** Bug 1955350 has been marked as a duplicate of this bug. ***
Package is retired in rawhide. In branches it was Obsoleted and the renamee package has the relevant Provides so "dnf install r2cutter" will actually result in installing the iaito (r2cutter was renamed to iaito). I was trying to follow the procedure for package renaming. Please Miro do you suggest to do anything more with the r2cutter.
There is no way to retire a package on stable branch. It will remain in the repo forever: $ repoquery --releasever=34 --repo=fedora r2cutter r2cutter-0:0.1.1-4.fc34.i686 r2cutter-0:0.1.1-4.fc34.x86_64 If we close this bug, the automation will keep opening a new one. Maybe we could manually exclude it from the script.
Or we can just leave this bug open for another year for the reference till the obsoletion of F34. Fine with me.
Fine by me as well. Thanks.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.