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 1737928 - subversion depends on Python 2
Summary: subversion depends on Python 2
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: subversion
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31_PY2REMOVAL 1739053
TreeView+ depends on / blocked
 
Reported: 2019-08-06 11:40 UTC by Lumír Balhar
Modified: 2019-11-13 17:54 UTC (History)
4 users (show)

Fixed In Version: subversion-1.12.2-2.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-13 17:54:22 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Lumír Balhar 2019-08-06 11:40:02 UTC 
Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime.
Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages
Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2

To help planning, we'd like to know the plans for subversion's future. Specifically:


- What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) 

- What are the upstream/community plans/timelines regarding Python 3?

- What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?)


This bug is filed semi-automatically, and might not have all the context specific to subversion.
If you need anything from us, or something is unclear, please mention it here.

Thank you.
Comment 1 Ben Cotton 2019-08-13 17:04:26 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 2 Ben Cotton 2019-08-13 17:09:53 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.
Comment 3 Lumír Balhar 2019-08-15 07:43:52 UTC 
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.
Comment 4 Joe Orton 2019-08-15 09:31:38 UTC 
(In reply to Lumír Balhar from comment #0)
> - What is the reason for the Python2 dependency? (Is it software written in
> Python, or does it just provide Python bindings, or use Python in the build
> system or test runner?) 
> 
> - What are the upstream/community plans/timelines regarding Python 3?

Upstream Subversion python bindings are not ported to py3 in current releases.
 
> - What is the guidance for porting to Python 3? (Assuming that there is
> someone who generally knows how to port to Python 3, but doesn't know
> anything about the particular package, what are the next steps to take?)
 
Porting to Py3 is a WIP upstream - there's a branch for it not yet merged.

For F31 we can rebuild subversion w/o python bindings (it is all conditinoalized in the spec) though it'll mean dropping the packages which depend on it:

$ repoquery -q --whatrequires python2-subversion
svnmailer-0:1.0.9-15.fc30.noarch
viewvc-0:1.1.26-9.fc30.noarch
Comment 5 Petr Viktorin 2019-08-15 11:01:31 UTC 
Thanks for the info!
F31 is okay. Python 2 will be retired in Fedora 32. Sorry for the confusing wording there.

Similar bugs should be open for svnmailer and trac. If they (or python2-subversion) need to stay in Fedora 32, they'll need a FESCo exception for themselves and their dependencies. Otherwise, we plan to remove them by November.

Until then, please don't break the dependencies.
Comment 6 Joe Orton 2019-08-30 12:11:53 UTC 
Commit: https://src.fedoraproject.org/rpms/subversion/c/1009d9c40134fac8ebbee82b9cfb2ce93980440c
Comment 7 Joe Orton 2019-08-30 12:12:31 UTC 
svnmailer and viewvc have both been retired now, so I'm rebuilding f32 subversion as py3-only.
Comment 8 Joe Orton 2019-08-30 14:45:45 UTC 
Package: subversion-1.12.2-2.fc32
Comment 9 Paul Howarth 2019-09-01 09:24:49 UTC 
Note that the build of subversion-1.12.2-2.fc32 has not produced a python3-subversion package due to the "%bcond_with pyswig" conditional, presumably because upstream isn't ready for python3 yet as mentioned in comment #4?
Comment 10 Joe Orton 2019-09-02 08:40:36 UTC 
Paul - yes, exactly right.

It's possible there will be an 1.13.x release in time for F32 which merges the py3 branch upstream, there has been discussion about this upstream and I may be able to put some time into testing. But otherwise F32 will ship without Python bindings for SVN.
Comment 11 Joe Orton 2019-11-13 17:54:22 UTC 
There is progress and active discussion on Python 3 support upstream now and it should be fully supported (including bindings) at least by Subversion 1.14.  Subversion 1.13 is now built, but only as a module (since SWIG 4 is also not supported) and I'll continue to track this upstream.
Note You need to log in before you can comment on or make changes to this bug.