Bug 1737980

Summary:	jack-audio-connection-kit depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	jack-audio-connection-kit	Assignee:	Guido Aulisi <guido.aulisi>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	brendan.jones.it, dominik, guido.aulisi, kvolny, nphilipp, oget.fedora, pviktori
Target Milestone:	---	Keywords:	Triaged
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:	2019-10-11 07:48:27 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:	1698500, 1738949

Description Lumír Balhar 2019-08-06 12:17:59 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 jack-audio-connection-kit'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 jack-audio-connection-kit.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Guido Aulisi 2019-08-07 18:35:05 UTC

This package uses the WAF build system, which uses Python. The next upstream version should be compatible with Python 3.7, but the current one fails to build with Python 3.

Comment 2 Lumír Balhar 2019-08-08 06:39:48 UTC

Do you know about any plans for the next release with Python 3 compatibility?

Comment 3 Guido Aulisi 2019-08-08 07:22:46 UTC

According to latest commit https://github.com/jackaudio/jack2/commit/4828349f3dac9dd84d743011489b24999bb0705f

it should be soon...

Comment 4 Ben Cotton 2019-08-13 17:33:55 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 5 Lumír Balhar 2019-08-15 07:22:07 UTC

Package laditools is currently blocked by this package and a2jmidid but you are the maintainer of all three so it should not be a problem.

The current plan is to remove packages with dependency on Python 2 from Fedora 32 in the middle of November 2019. If you want to keep your package in Fedora after that date and you cannot port it to Python 3 yet, you need to request a FESCo exception for the package and all its Python 2 dependencies (even transitive) [1]. If you don't want to maintain it anymore, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.).

If you're considering filing the exception request, let us know. We can help (for example, we can help find all the dependencies).

[1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions

Comment 6 Guido Aulisi 2019-09-19 09:09:09 UTC

According to upstream new version will be released in the mid of October 2019

Comment 7 Petr Viktorin (pviktori) 2019-09-19 09:12:33 UTC

Thanks. Let us know if there's danger of the release being delayed.

Comment 8 Orcan Ogetbil 2019-09-19 23:04:03 UTC

Should there be a delay with new upstream release, it seems straightforward, with a few hours of work, to backport the Python3 compatible build system to the current package.

Comment 9 Lumír Balhar 2019-10-11 07:48:27 UTC

I can confirm that the latest build does not depend on Python 2 and all RPMs are installable.