Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (ignatenkobrain). Your package (python-asynctest) Fails To Install in Fedora 34: can't install python3-asynctest: - nothing provides python(abi) = 3.8 needed by python3-asynctest-0.13.0-4.fc32.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/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 basically a duplicate of Bug 1831130. The status quo is the following: The python-asynctest upstream is dead. (cf. e.g. https://github.com/Martiusweb/asynctest/issues/151 and linked issues there) Granted, since Python 3.8+ includes functionality similar to asynctest there isn't much point in maintaining asynctest for newer Python version. Unfortunately, instead of posting a small statement regarding the current state of affairs and future plans for asynctest - or even a migration recommendation, it's author silently abandoned the package. In Fedora 31, there is just just one package (python-aioresponses) that build-requires asynctest. There is no package which runtime-requires it. I'm also the package-maintainer of python-aioresponses and I've already removed the asynctest dependency in rawhide. The aioresponses upstream also eliminated the asynctest dependency in the master branch. Thus, the next release will build without asynctest, out-of-the-box. (cf. https://github.com/pnuckowski/aioresponses/issues/162) I thus plan to remove the python-asynctest package from Fedora, following the steps described in: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life If I understand the process correctly, I shall first retire the epel8 branch and then the master branch. All other branches I can leave as-is - including the empty epel8-playground branch. Right?
PS: Ok, I shall also retire it from f33 since the final freeze haven't happened yet.
I've just retired asynctest in the f33 and master branches. FWIW, retiring the epel8 branch failed with: > Fedora release (epel8) is in state 'current' - retire operation is not allowed. The how-to https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life seem to suggest that retiring epel branches always works. Looks like there are some undocumented nuances regarding retiring epel branches.
> Fedora release (epel8) is in state 'current' - retire operation is not allowed. That is a bug in fedpkg, feel free to open a releng ticket to retire the epel8 branch.
(In reply to Miro Hrončok from comment #5) > > Fedora release (epel8) is in state 'current' - retire operation is not allowed. > > That is a bug in fedpkg, feel free to open a releng ticket to retire the > epel8 branch. Ok, I've opened a ticket: https://pagure.io/releng/issue/9751