Bug 1632396 - the-new-hotness: Remove (sub)packages from Fedora 30+: the-new-hotness
Summary: the-new-hotness: Remove (sub)packages from Fedora 30+: the-new-hotness
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: the-new-hotness
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Čermák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PY2REMOVAL F31_PY2REMOVAL
TreeView+ depends on / blocked
 
Reported: 2018-09-24 17:01 UTC by Miro Hrončok
Modified: 2022-06-27 14:54 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-28 19:44:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2018-09-24 17:01:43 UTC
In line with the Mass Python 2 Package Removal [0], the following (sub)packages of the-new-hotness were marked for removal:

 * the-new-hotness

According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query.

Please remove them from your package.

As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here.

We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document [0].

[0] https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal

Comment 1 Miro Hrončok 2019-01-17 11:08:19 UTC
Can we retire that package from Fedora entirely?

Do we need it packaged in Fedora for the actual new hotness deployed in prod?

Comment 2 Miro Hrončok 2019-02-26 12:15:55 UTC
The beta freeze is at 2019-03-05. Could you please answer the question?

Comment 3 Miro Hrončok 2019-05-11 23:41:59 UTC
https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

1) What are the upstream plans/timelines regarding Python 3?

Comment 4 Miro Hrončok 2019-05-20 15:00:45 UTC
Could you please provide the requested information?

Comment 5 Miro Hrončok 2019-05-27 09:12:18 UTC
Could you please provide the requested information?

Comment 6 Miro Hrončok 2019-06-03 10:35:36 UTC
Could you please provide the requested information?

Comment 7 Miro Hrončok 2019-06-18 19:57:14 UTC
Helo Dan, I see you took this package. What are the upstream plans/timelines regarding Python 3?

Comment 8 Jeremy Cline 2019-06-18 20:36:03 UTC
Sorry, this got lost in my bugzilla mail. Michal is the upstream maintainer and as far as I know doesn't use the RPM so this package should probably be retired.

Comment 9 Dan Čermák 2019-06-19 10:14:26 UTC
I believe that upstream has migrated to python3 and if this package is still usefull, then I'll submit an update soon. Otherwise it can be retired if it is not needed by the infra team or anyone else.

Comment 10 Michal Konecny 2019-06-19 10:44:28 UTC
I can confirm that the-new-hotness was ported to python 3 on upstream.

Comment 11 Dan Čermák 2019-06-19 11:50:33 UTC
(In reply to Michal Konecny from comment #10)
> I can confirm that the-new-hotness was ported to python 3 on upstream.

Do you need this package in Fedora? I don't mind maintaining it, if it is useful for somebody, but not just for the sake of having it available as an RPM.

Comment 12 Michal Konecny 2019-06-19 12:06:28 UTC
(In reply to dan.cermak from comment #11)
> (In reply to Michal Konecny from comment #10)
> > I can confirm that the-new-hotness was ported to python 3 on upstream.
> 
> Do you need this package in Fedora? I don't mind maintaining it, if it is
> useful for somebody, but not just for the sake of having it available as an
> RPM.

Right now I'm installing it directly from Github repository in OpenShift, so I don't need the RPM package. If there will be need for it in future, I will maintain the package by myself.

Comment 13 Dan Čermák 2019-06-19 12:10:12 UTC
If there are no objections, then I'll directly retire the package.

Comment 14 Miro Hrončok 2019-06-19 12:38:53 UTC
I agree.

Comment 15 Jeremy Cline 2019-06-19 13:42:33 UTC
Please do retire it, thanks!

Comment 16 Dan Čermák 2019-06-28 06:05:07 UTC
the-new-hotness has been retired.

Comment 17 Miro Hrončok 2019-06-28 08:18:26 UTC
Thank you.

Comment 18 Sergio Basto 2022-05-27 22:40:05 UTC
(In reply to Dan Čermák from comment #11)
> (In reply to Michal Konecny from comment #10)
> > I can confirm that the-new-hotness was ported to python 3 on upstream.
> 
> Do you need this package in Fedora? I don't mind maintaining it, if it is
> useful for somebody, but not just for the sake of having it available as an
> RPM.

yes , of course is needed on Fedora you should use an rpm package to run the-new-hotness, 
I need the-new-hotness to run on other koji instance , how I do that without the package ?

Comment 19 Miro Hrončok 2022-05-28 19:44:39 UTC
This bug is not the correct place to discuss this. If you want the-new-hotness in Fedora, please follow https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming


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