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 (funguloids) Fails To Install in Fedora 34: can't install funguloids: - nothing provides libOgreMain.so.1.9.0()(64bit) needed by funguloids-1.06-36.fc33.x86_64 - nothing provides libOgreOverlay.so.1.9.0()(64bit) needed by funguloids-1.06-36.fc33.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/rawhide-gating/multi-builds/ 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.
This is due to a bump of the ogre versions, unfortunately the new version breaks both abi and api compatibility. I do plan to fix this, but I do not know when I will get around to fixing this, updating status to assigned.
Hi, Just last Sunday I realized what you mean, Ogre upgarde will give a bunch of work and it will consume a bunch of time, which I don't have. What you suggest ? Should I rollback ogre to version 1.9 with EPOCH bump ? and about Ogre FTBFS on F33, what we should do ?
Hi, (In reply to Sergio Basto from comment #3) > Hi, > Just last Sunday I realized what you mean, Ogre upgarde will give a > bunch of work and it will consume a bunch of time, which I don't have. > What you suggest ? > Should I rollback ogre to version 1.9 with EPOCH bump ? Yes I think a rollback would be best, thanks. And then maybe setup a copr with the latest ogre, so that we can try to move things to that when we find time (if ever), we could then add things to the copr as we port them over; and then once we have everything there move it all over to Fedora proper. > and about Ogre FTBFS on F33, what we should do ? If you build the new epoch bumped 1.9 in rawhide successfully, then you can simply close the FTBFS bug with a resolution of rawhide. That is the normal way to deal with FTBFS bugs which are only fixed after the official release (or during the final freeze). Thanks & Regards, Hans
p.s. About the copr thing, that is just something which popped into my mind, it might be an option, but it is not important / is not high priority.
Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). All subpackages of a package against which this bug was filled are now installable or removed from Fedora 34. Thanks for taking care of it!