Bug 1288802
Summary: | python-abiword: please support Python 3 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David H. Gutteridge <dhgutteridge> |
Component: | abiword | Assignee: | Marc Maurer <uwog> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | herrold, mhroncok, pbrobinson, pviktori, uwog |
Target Milestone: | --- | Keywords: | Reopened, Tracking |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | abiword-3.0.4-3.fc32 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-01-30 08:45:18 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1285816, 1625773, 1698500, 1708725, 1739058 |
Description
David H. Gutteridge
2015-12-06 03:02:21 UTC
Although I just noticed the Makefile.am supplied does have a line with a compatibility problem, since it has overridesdir = `python -c "import gi; print gi._overridesdir"` I'll file this upstream. Submitted upstream as http://bugzilla.abisource.com/show_bug.cgi?id=13746. Upstream has committed the change in trunk. This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase Hello Marc, do you need any help adding Python 3 support to the RPM? If you need more instructions, a [guide] for porting Python-based RPMs is available. [guide] http://python-rpm-porting.readthedocs.io/ This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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. This is still an issue in F25/F26/rawhide. Changing version to rawhide, accordingly. This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. David I have added the upstream tracker item, and poked there as the patch seems not to have been applied yet David upstream indicates there will not be a backport ... I will hold this open against the possibility of finding time to backport it alternatively I am considering moving to an inter-release VCS CO build -- Russ This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. Still valid. Any news here? I submitted two trivial patches to address a build consideration where the "python" executable happens to be Python 3, and to reflect the relatively recent expectations of PyGObject 3. These were accepted into upstream's SVN trunk at the time. Upstream has indicated they aren't interested in integrating these patches into a point release. If Fedora maintainers feel strongly enough about it, they can simply take my patches and add them to the package's spec. Change set for both is: https://www.abisource.com/viewvc?view=rev&revision=35171 I was working on a pull from upstream yesterday, trying to get a clean build yesterday in an EPEL 7 environment, fwiw This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30. What's the status on this? It's in upstream's master branch, but it looks like there hasn't been a release for some time. Is a release coming? If not, can we do a downstram patch? Miro AFAICT this should build with python3 as it's mostly just gobject introspection generated python bits, can you see any reason why it fails? *** Bug 1787239 has been marked as a duplicate of this bug. *** (In reply to Peter Robinson from comment #18) > Miro AFAICT this should build with python3 as it's mostly just gobject > introspection generated python bits, can you see any reason why it fails? I think I got it working but if you could verify it's correct it would be appreciated. I'll have a look later. Not this week, sorry. The package is now Python 3 only. The python3-abiword package owns the following directories co-owned by python3-gobject-base: /usr/lib64/python3.8/site-packages/gi /usr/lib64/python3.8/site-packages/gi/overrides /usr/lib64/python3.8/site-packages/gi/overrides/__pycache__ It does not require python3-gobject-base, but I see no way how to use the package without it. Maybe it should require python3-gobject-base and only own the following files? /usr/lib64/python3.8/site-packages/gi/overrides/Abi.py /usr/lib64/python3.8/site-packages/gi/overrides/__pycache__/Abi.cpython-38.opt-1.pyc /usr/lib64/python3.8/site-packages/gi/overrides/__pycache__/Abi.cpython-38.pyc It should be possible to use the new %pycached macro: %files -n python3-abiword %pycached %{python3_sitearch}/gi/overrides/Abi.py > It should be possible to use the new %pycached macro: Got a link to the docs for this by chance? > %files -n python3-abiword > %pycached %{python3_sitearch}/gi/overrides/Abi.py Long spec in the commit: https://src.fedoraproject.org/rpms/python-rpm-macros/c/6c63a5b7f484f3c4b6bee13196561c9b1dff410a New guidelines: https://pagure.io/packaging-committee/pull-request/940 All fixed up. |