Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1871594 - F34FailsToInstall: python3-asynctest
Summary: F34FailsToInstall: python3-asynctest
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-asynctest
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Georg Sauthoff
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F34FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2020-08-23 17:27 UTC by Igor Raits
Modified: 2020-09-11 15:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-08 19:58:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Igor Raits 2020-08-23 17:27:20 UTC 
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!
Comment 1 Igor Raits 2020-08-31 09:08:22 UTC 
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.
Comment 2 Georg Sauthoff 2020-09-06 21:08:34 UTC 
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?
Comment 3 Georg Sauthoff 2020-09-06 21:14:11 UTC 
PS: Ok, I shall also retire it from f33 since the final freeze haven't happened yet.
Comment 4 Georg Sauthoff 2020-09-08 19:58:17 UTC 
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.
Comment 5 Miro Hrončok 2020-09-08 21:02:05 UTC 
> 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.
Comment 6 Georg Sauthoff 2020-09-11 15:54:40 UTC 
(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
Note You need to log in before you can comment on or make changes to this bug.