-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
treewide: remove deprecations up until 24.11 #356732
treewide: remove deprecations up until 24.11 #356732
Conversation
Scheduled for 24.11.
This is also true in 24.11 and up, so no need to state the version number explicitly.
Scheduled for 24.11. Added in NixOS#272147.
bde5418
to
07ae95e
Compare
Rebased, hoping that the eval errors before were not mine. No changes. |
Had been deprecated and scheduled for removal in 24.11.
This had been scheduled for removal in 23.11.
Those were scheduled for removal in 24.11.
Scheduled for removal for 24.11.
07ae95e
to
c35379a
Compare
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.
Approved by release manager; ping me after ofborg eval is done for merge.
BTW, it looks like this may leave some |
This was scheduled for 24.11.
This was scheduled for 24.11.
Scheduled for 24.05.
c35379a
to
6c258ee
Compare
@emilazy ofborg eval complete, but I noticed a left-over test for |
Looks good, thanks! |
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.
LGTM for redocly. I should have done this myself. Though personally I would just keep it as is since we're already past the change freeze.
@emilazy ofborg-eval is done again. |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release-24.11
git worktree add -d .worktree/backport-356732-to-release-24.11 origin/release-24.11
cd .worktree/backport-356732-to-release-24.11
git switch --create backport-356732-to-release-24.11
git cherry-pick -x 73df63f8ef1e0a578ed047428491bd02588c9f11 de69ff528bb5f3028f4c8f303b170c5fb83f9f8b 749a6fe1adb3a8bd9e9013d524e4fbae5ca6e901 9966353ee7cd830cb25b60d2360a3a0069802426 8bdfc5eca22d86b70b53f5422e273b29be20a3dc e1e2193dff2750fb33b8c115a21498e322879a71 4255d7a658c0b247588f38a64b96eaa7b74f8357 51da8b6b00c2b18b6a2fac9bc15e6fd67932396b 6646eeb500eeb27b8bcd56b9910fa967bf8ba410 89981f1968f2047bc7b860a726a8e6bf9b292711 352f462ad9d2aa2cde75fdd8f1734e86402a3ff6 97c3fa4ebd116c8e4983325afb87e5e7043cd092 b6c3e15ee52784dab633c8612dd5f20d3b3f011a 6c258ee2bd97c5211e582a59398cb1765f77ebb3 |
How ironic. |
Grepping through the repo for NixOS version numbers brought up those candidates for removal. Many were targeted at 24.11, but some have already been forgotten for a while.
If any of those are controversial, I can split those into a separate PR.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.