Bug 1692037 - Switch ursa-major to Python 3 or retire it from Fedora
Summary: Switch ursa-major to Python 3 or retire it from Fedora
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ursa-major
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: cqi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PY2REMOVAL
TreeView+ depends on / blocked
 
Reported: 2019-03-23 15:00 UTC by Miro Hrončok
Modified: 2019-05-15 16:18 UTC (History)
2 users (show)

Fixed In Version: ursa-major-0.2.2-3.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-15 16:18:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2019-03-23 15:00:59 UTC
Hi, ursa-major was added to Fedora and it just popped up in my https://fedora.portingdb.xyz/ check/update (not yet deployed).

ursa-major uses Python 2, Python 2 is deprecated and adding Python 2 dependent packages is forbidden without FESCo/FPC exception.

Please switch it to Python 3 or retire it from Fedora.

Please don't add any more Python 2 software to Fedora.


Thanks.

Comment 1 cqi 2019-03-26 03:38:40 UTC
Hi Miro, if python 2 package is still required, should Ursa-Major be built in module?

Comment 2 Miro Hrončok 2019-03-26 10:00:36 UTC
Hi cqi. No idea about modules. Please try to explain why it is required in the first place, as it is hard for me to understand.

It makes our efforts hard, as we try to remove Python 2 packages from Fedora on one side and other Red Hatters are adding new Python 2 packages back from the other side.

Do packaging guidelines apply to modules? If so, adding to a module is not a solution. You need an exception. AFAIK both FPC and FESCo can give you such exception.

The following answers might help:

 - why is ursa-major packaged in Fedora? who is the consumer - aka is it our infra, or actual users?
 - why was a new piece of software written in 2018 still written in Python 2?
 - I see in spec: "we have some koji hubs doesn't support Python3 with kerberos auth at this moment, so we build with Python2 for all platforms now"
   - on what Fedora versions do those koji hubs run? is that information relevant to packaging of ursa-major?
   - what is planned to do to fix those hubs?
   - who is responsible to fix them?
   - when is the estimation to have them fixed?


If packaging guidelines do not apply to modules, you are good, but we are all doomed :D

Thanks.

Comment 3 cqi 2019-04-12 06:46:52 UTC
I'm not the original one who did the open source for ursa-major in Fedora.
I don't have all detailed information, but I can try my best to answer your
questions.

(In reply to Miro Hrončok from comment #2)
> Hi cqi. No idea about modules. Please try to explain why it is required in
> the first place, as it is hard for me to understand.
> 
> It makes our efforts hard, as we try to remove Python 2 packages from Fedora
> on one side and other Red Hatters are adding new Python 2 packages back from
> the other side.
> 
> Do packaging guidelines apply to modules? If so, adding to a module is not a
> solution. You need an exception. AFAIK both FPC and FESCo can give you such
> exception.
> 
> The following answers might help:
> 
>  - why is ursa-major packaged in Fedora? who is the consumer - aka is it our
> infra, or actual users?

There is a ticket[1] for deployment in Fedora, which is in Open status now.

[1] https://pagure.io/fesco/issue/2003

>  - why was a new piece of software written in 2018 still written in Python 2?

Ursa-Major was written originally for internal use and has been running in RHEL7.

>  - I see in spec: "we have some koji hubs doesn't support Python3 with
> kerberos auth at this moment, so we build with Python2 for all platforms now"
>    - on what Fedora versions do those koji hubs run? is that information
> relevant to packaging of ursa-major?

I heard of this issue from maintainer who did the open source and initiated
the deployment in Fedora. I will talk with him to learn something new.

However, from my point of view, it should not be a blocker for Ursa-Major to
build Python 3 package for Fedora. After all, we could build Python 2 package
for EPEL7, which can be used to deploy once the ticket is approved.

>    - what is planned to do to fix those hubs?
>    - who is responsible to fix them?
>    - when is the estimation to have them fixed?

I think Koji team might be the right one to get such info.

> 
> If packaging guidelines do not apply to modules, you are good, but we are
> all doomed :D
> 
> Thanks.

Comment 4 Miro Hrončok 2019-04-12 08:57:27 UTC
(In reply to cqi from comment #3)
> However, from my point of view, it should not be a blocker for Ursa-Major to
> build Python 3 package for Fedora. After all, we could build Python 2 package
> for EPEL7, which can be used to deploy once the ticket is approved.

Works for us.

I fail to understand why https://pagure.io/fesco/issue/2003 needs this package to be in Fedora. FWIW, it seem that ursa-major will not be approved by FESCo, the current proposal goes elsewhere. But even if ursa-major was supposed to be used by infra, I don't understand why it needs to be in Fedora repos.

Comment 5 cqi 2019-04-12 09:05:08 UTC
I actually don't follow up that ticket completely yet. :) Anyway, I just created an issue (in internal jira) to change spec to build python 3 package for Fedora. Will make a plan for it.

Comment 7 Miro Hrončok 2019-04-15 13:31:04 UTC
Thanks!

Comment 8 Miro Hrončok 2019-04-22 14:53:09 UTC
This was still not yet built in rawhide.

Comment 9 Miro Hrončok 2019-05-11 23:39:12 UTC
I've triggered a rawhide build.

https://koji.fedoraproject.org/koji/taskinfo?taskID=34800378


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