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
ruby_2_4: remove #76600
ruby_2_4: remove #76600
Conversation
320e630
to
c0733c8
Compare
We do? |
Maybe policy is too strong of a word. It's a number I have seen in multiple places (don't have the sources right now). Typically libraries would have between 1 and 2, with a strong bias towards 1. Programs between 1-3. Programming languages, around 3. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t have strong feelings about doing this now or in a few months.
Actually, I think we should hold off. People might be, say, using 2.4 at work and not upgraded yet, with a schedule to do so before EOL (I was in this situation with 2.3 last year). I think maybe we should give them until a little closer to the deadline. |
that's fine, they can stay on 19.09 for a bit longer |
that's fine, they can stay on 19.09 for a bit longer
I'd like to keep it around in unstable, just for a couple of months, and
remove it closer to EOL. It's not hurting anyone.
|
We also keep Python 2.7, despite it going EOL. It should however be possible to disable the derivation if issues come up that we cannot resolve. |
in that case the bits that add ruby 2.7 should probably be cherry-picked out of this PR |
We also keep Python 2.7, despite it going EOL. It should however be
possible to disable the derivation if issues come up that we cannot
resolve.
I definitely want 2.4 gone by 20.03. There's no good reason to keep it
round past EOL, unlike with Python.
|
Comment indicates that approval is out of date.
Marking sonic-pi as broken here is fine, just read sonic-pi-net/sonic-pi#2179 (comment) and you'll get the idea. |
According to https://endoflife.software/programming-languages/server-side-scripting/ruby ruby 2.4 will go end-of-life in march, where the new release of nixpkgs will be cut. We won't be able to support it for security updates. Remove all references to ruby_2_4 and add ruby_2_7 instead where missing. Mark packages that depend on ruby 2.4 as broken: * chefdk * sonic-pi
c0733c8
to
1b5d37a
Compare
@GrahamcOfBorg eval |
For reference, done as f8f607b. |
According to https://endoflife.software/programming-languages/server-side-scripting/ruby
ruby 2.4 will go end-of-life in march, where the new release of nixpkgs
will be cut. We won't be able to support it for security updates.
Remove all references to ruby_2_4 and add ruby_2_7 instead where
missing.
Mark packages that depend on ruby 2.4 as broken:
Motivation for this change
rubyPackages_2_4.libv8 was breaking in #76595 which prompted me to look at the ruby situation.
Ruby 2.4 will be EOL for our next release. We also have a policy of keeping only 3 versions of the same thing in nixpkgs.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @alyssais @manveru