-
-
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
.NET 6/7 are EOL #326335
Comments
Related: #358533 |
beatsabermodmanager: #361128 |
removing both 6 and 7 from roslyn-ls: #357963 - looking for reviewers/mergers. |
This comment has been minimized.
This comment has been minimized.
cc: @puffnfresh @mdarocha |
I'll do it in a separate PR from the ones I'm doing currently. I'll have to figure out how removals work in cc: @jirkadanek |
Unable to upgrade
cc: @eliandoran |
There are no maintainers so I'm unsure if this package should be kept at all unless if someone else picks it up. |
Taking care of |
OK, I'll have a look. Maybe in the newer version of NAPS2 they updated to a newer version of .NET. |
There is the newer https://github.com/dotnet/msbuild/ we can use instead. |
On another note, ever since #359409, the launcher has been broken for me (the launcher itself starts fine, but it can't launch the game). Since apparently only myself and one other unfortunate soul on the ss14 discord have ran into this, I'd guess the overall usage of this package is low. |
Hi, I was wondering why I got the notification. I get it now, same name different person. Could still be a half-brother :D Merry Christmas wishes jDanek :D |
That's already part of the .NET SDK, I think the only use it had was compiling .NET Framework projects on Linux, but I don't know how to move on with those as I don't think there are .NET Framework targeting packs for Linux |
Yeah, my bad 😅 |
hmm, any idea what could've happened to roslyn-ls In the past week? I have automatic dep updates on that flake every Friday, so it worked on Dec 10th (manual update), worked on Dec 13th, and stopped working somewhere between Dec 13th and Dec 20th (today). In particular, this works: https://github.com/konradmalik/neovim-flake/actions/runs/12253416030, and today this failed: https://github.com/konradmalik/neovim-flake/actions/runs/12424292928 |
Your PR did not remove the dependency on .NET 6, it's still in there, even though only |
@GGG-KILLER thanks, this makes sense. @corngood suggested that this could help with the insecurePackages warning. Seems like it does not, which is fine, but I still do not understand why it did not generate warnings for me for more than a week and started to do so again today. |
It used to, before we merged a change that made usage of packages from .NET 6 and 7 generate insecure warnings. This was done in #363439 |
gh-gei was done in #366482 already. Will remove it from my PR. |
Revert after NixOS/nixpkgs#360592 and NixOS/nixpkgs#326335 are sorted out.
* fix(dips): permit botnet 6 Revert after NixOS/nixpkgs#360592 and NixOS/nixpkgs#326335 are sorted out. * fix(deps): allow asp net core
.NET 7 went EOL on 14th May 20241. Similar to #202572, which dealt with the deprecation of .NET Core 3.1, we should make an effort to update or patch packages whick rely on .NET 7.
Packages
pkgs/applications/audio/famistudio/default.nix
pkgs/applications/audio/openutau/default.nix
pkgs/applications/blockchains/wasabibackend/default.nix
pkgs/applications/editors/jetbrains/default.nix
pkgs/applications/graphics/pinta/default.nix
pkgs/by-name/be/beatsabermodmanager/package.nix
pkgs/by-name/do/dotnet-outdated/package.nix
pkgs/by-name/lu/lumafly/package.nix
pkgs/by-name/pa/pablodraw/package.nix
pkgs/by-name/pu/pupdate/package.nix
pkgs/by-name/re/retrospy/package.nix
pkgs/by-name/ro/roslyn-ls/package.nix
pkgs/development/tools/fsautocomplete/default.nix
pkgs/development/tools/misc/netcoredbg/default.nix
pkgs/development/tools/omnisharp-roslyn/default.nix
pkgs/games/vintagestory/default.nix
pkgs/tools/security/certdump/default.nix
Footnotes
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core ↩
The text was updated successfully, but these errors were encountered: