Bug 1830657

Summary: FTI: python-aiomysql: python3-aiomysql
Product: [Fedora] Fedora Reporter: Igor Raits <igor.raits>
Component: python-aiomysqlAssignee: Fabian Affolter <mail>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: code, itamar, mail, mhroncok, tredaelli
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 18:08:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1668058, 1783776, 1822004    
Bug Blocks: 1750909, 1803235    

Description Igor Raits 2020-05-03 09:47:15 UTC
Hello,

Your package (python-aiomysql) Fails To Install in Fedora 33:

---
can't install python3-aiomysql-0.0.20-3.fc32.noarch:
  - nothing provides (python3.8dist(pymysql) >= 0.9 with python3.8dist(pymysql) <= 0.9.2) needed by python3-aiomysql-0.0.20-3.fc32.noarch
---

According to a 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 if you won't reply to this bug.

Thanks!

Comment 1 Fabian Affolter 2020-05-03 10:36:12 UTC
Update on the way: https://github.com/aio-libs/aiomysql/pull/485

Comment 2 Fabian Affolter 2020-06-02 09:55:15 UTC
*** Bug 1834084 has been marked as a duplicate of this bug. ***

Comment 3 Miro Hrončok 2020-06-30 16:24:26 UTC
The Sphinx 3 build is in progress, you can wait for it with:

$ koji wait-repo f33-build --build python-sphinx-3.1.1-1.fc33

Comment 4 Ben Cotton 2020-08-11 13:22:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 5 Fabian Affolter 2020-08-21 06:23:24 UTC
*** Bug 1828950 has been marked as a duplicate of this bug. ***

Comment 6 Itamar Reis Peixoto 2020-10-06 01:31:21 UTC
when you have a time please build with this patch 

https://src.fedoraproject.org/rpms/python-aiomysql/c/3c3402005f94226807fb1eb76a49d79eeb286c6f

I think theres an extra +, preventing it to build.

https://src.fedoraproject.org/rpms/python-aiomysql/blob/master/f/python-aiomysql.spec#_33

Comment 7 Fabian Affolter 2020-10-30 11:05:14 UTC
*** Bug 1878410 has been marked as a duplicate of this bug. ***

Comment 8 Miro Hrončok 2021-02-02 21:57:08 UTC
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!

Comment 9 Ben Beasley 2021-02-26 16:58:01 UTC
Any chance of fixing this on Fedora 33 and Fedora 32 (https://bugzilla.redhat.com/show_bug.cgi?id=1887016)?

Comment 10 Fabian Affolter 2021-03-02 19:08:17 UTC
Sorry, no. Upstream is pretty much dead now. There was some activity back in November but none of the major issues were addressed.

Comment 11 Ben Cotton 2021-11-04 15:00:10 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Ben Cotton 2021-11-04 15:58:48 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Ben Cotton 2021-11-30 18:08:56 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.