Skip to content
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

Merged
merged 1 commit into from May 16, 2020
Merged

rkt: remove #81860

merged 1 commit into from May 16, 2020

Conversation

zowoq
Copy link
Contributor

@zowoq zowoq commented Mar 6, 2020

rkt has basically been dead since 2018 and now upstream has made it official.

https://github.com/rkt/rkt/#warning-end-of-project-warning

This project has ended, and all development/maintenance activities have halted.

As it is free software, people are free and welcome to fork and develop the codebase on their own. However, to avoid any confusion, the original repository is archived and we recommend any further fork/development to proceed with an explicit rename and rebranding first.

We encourage all interested parties to mirror any relevant bits as we can't actively guarantee their existence in the future.

More detail in rkt/rkt#4024 (comment)

@Mic92
Copy link
Member

Mic92 commented Mar 6, 2020

What is the opinion of the maintainer? @ragnard @steveej

@Mic92
Copy link
Member

Mic92 commented Mar 6, 2020

Also @NeQuissimus who did maintenance on the package.

@NeQuissimus
Copy link
Member

All I can say is that I stopped using it :)
I would suggest keeping it around for a little while longer to see if any other entity takes over the repo. But if not, we should make sure this has been deleted for NixOS 20.09

@steveej
Copy link
Contributor

steveej commented Mar 6, 2020

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?

@infinisil
Copy link
Member

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.

@zowoq
Copy link
Contributor Author

zowoq commented Mar 7, 2020

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
cncf/toc#262
https://www.cncf.io/blog/2019/08/16/cncf-archives-the-rkt-project/
rkt/rkt#3999
https://www.twistlock.com/labs-blog/breaking-out-of-coresos-rkt-3-new-cves/

@infinisil
Copy link
Member

That sounds like reason enough to remove it pretty soon

@vcunat
Copy link
Member

vcunat commented Mar 7, 2020

It is only 1 month since the commercial team ceased work on it.

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.

@vcunat
Copy link
Member

vcunat commented Mar 7, 2020

As there are those CVEs, an alternative is to just use meta.knownVulnerabilities for now 🤷‍♂️

@zowoq
Copy link
Contributor Author

zowoq commented Mar 7, 2020

just use meta.knownVulnerabilities for now

Opened #82023

@Mic92
Copy link
Member

Mic92 commented Mar 9, 2020

I backported the cve list to 19.09 and 20.03 as well.

@Valodim
Copy link
Contributor

Valodim commented Mar 25, 2020

This issue is handled as discussed by #82023. Might as well close this, and revisit for 20.09.

@Mic92 Mic92 added this to the 20.09 milestone Mar 25, 2020
@Mic92
Copy link
Member

Mic92 commented Mar 25, 2020

We can also just keep this open for 20.09 as a milestone.

@Mic92
Copy link
Member

Mic92 commented May 14, 2020

Are there any news about a new fork of rkt?

@zowoq
Copy link
Contributor Author

zowoq commented May 15, 2020

I couldn't find anything.

Also added a comment to the release notes for 2009.

@Mic92 Mic92 merged commit 3233d3f into NixOS:master May 16, 2020
@zowoq zowoq deleted the rm-rkt branch May 16, 2020 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants