-
-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rkt: remove #81860
rkt: remove #81860
Conversation
Also @NeQuissimus who did maintenance on the package. |
All I can say is that I stopped using it :) |
I don't know what the policy says about packages which are unmaintained upstream. If there's no policy I suggest establishing one so these decisions are covered in the future. Personally I agree with @volth that it seems premature to removing it now. Maybe wait 2 more months? |
On the other hand, if the software still works, has users and doesn't have glaring security vulnerabilities, I don't think there's a problem with not removing it. |
It seems that last year the CNCF archived it and Gentoo removed it because of security issues and an inactive upstream. https://bugs.gentoo.org/687100 |
That sounds like reason enough to remove it pretty soon |
The note in the ticket about dismantlement of the official team was a quotation from summer. They declared end now because "community" hasn't picked it up since then. |
As there are those CVEs, an alternative is to just use |
Opened #82023 |
I backported the cve list to 19.09 and 20.03 as well. |
This issue is handled as discussed by #82023. Might as well close this, and revisit for 20.09. |
We can also just keep this open for 20.09 as a milestone. |
Are there any news about a new fork of rkt? |
I couldn't find anything. Also added a comment to the release notes for 2009. |
rkt
has basically been dead since 2018 and now upstream has made it official.More detail in rkt/rkt#4024 (comment)