Bug 1808013 - seamonkey requires Python 2 to build
Summary: seamonkey requires Python 2 to build
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: BRPY27
TreeView+ depends on / blocked
 
Reported: 2020-02-27 16:20 UTC by Petr Viktorin
Modified: 2020-02-27 16:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Petr Viktorin 2020-02-27 16:20:00 UTC
Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's now provided from the compat package `python27`.
Packages that only use Python 2 at build time, like seamonkey, had a general exception to keep using it in Fedora 31. Now, the dependency should be removed.

I assume SeaMonkey is in a similar situation as the packages tracked here:
- Thunderbird BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1807555
- Firefox BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1805231
- IceCat exception request: https://pagure.io/fesco/issue/2346


If it's possible that the dependency won't be removed in Fedora 33. Please request a FESCo exception. You can refer to the exception for mercurial as an example: https://pagure.io/fesco/issue/2243
It's good to mention:

- What is the reason for the Python 2 build dependency?

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

- What is the guidance for porting the build 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?)

If you need anything from us, or something is unclear, please mention it here.

Comment 1 Dmitry Butskoy 2020-02-27 16:30:02 UTC
SeaMonkey is based on Firefox code, hence the answers are the same as:
https://bugzilla.redhat.com/show_bug.cgi?id=1805231#c1
https://bugzilla.redhat.com/show_bug.cgi?id=1805231#c2

Besides that, SeaMonkey is based on the "old" Firefox code (versions between 56<-->60 with some newer stuff backported). It looks likely that we will have a noticeable delay after the FF finished its switch to python3 (a time for non-trivial backport would be needed).

Comment 2 Dmitry Butskoy 2020-02-27 16:31:12 UTC
SeaMonkey is based on Firefox code, hence the answers are the same as:
https://bugzilla.redhat.com/show_bug.cgi?id=1805231#c1
https://bugzilla.redhat.com/show_bug.cgi?id=1805231#c2

Besides that, SeaMonkey is based on the "old" Firefox code (versions between 56<-->60 with some newer stuff backported). It looks likely that we will have a noticeable delay after the FF finished its switch to python3 (a time for non-trivial backport would be needed).

Comment 3 Dmitry Butskoy 2020-02-27 16:52:31 UTC
https://pagure.io/fesco/issue/2348


Note You need to log in before you can comment on or make changes to this bug.