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

dotnetCorePackages.net_5_0 is out of date, and out of sync with sdk_5_0 #125735

Closed
2 tasks done
leo60228 opened this issue Jun 4, 2021 · 1 comment
Closed
2 tasks done
Labels
9.needs: package (update) This needs a package to be updated

Comments

@leo60228
Copy link
Member

leo60228 commented Jun 4, 2021

Checklist
Project name

nix search name: (I'm not sure how to check this on a system with flakes)

current version: 5.0.0 / 5.0.3
desired version: 5.0.6

Additional note

I have a PR open for packaging netcoredbg (#103940). Building netcoredbg requires knowing the version of the runtime bundled with the SDK. Currently, the net_5_0 package and sdk_5_0 package are out of sync, making this difficult. The easiest solution would be to make sure to keep these in sync, but another option might be to add something like passthrough.runtimeVersion.

Notify maintainers

maintainers: @kuznero

Note for maintainers

Please tag this issue in your PR.

@leo60228 leo60228 added the 9.needs: package (update) This needs a package to be updated label Jun 4, 2021
@avdv
Copy link
Member

avdv commented Sep 20, 2021

Fixed by #138296

What's a bit confusing is that release 5.0.10 includes two SDKs (see https://dotnetcli.blob.core.windows.net/dotnet/checksums/5.0.10-sha.txt
):

  • dotnet-sdk-5.0.207
  • dotnet-sdk-5.0.401

I do not understand the difference nor why there are two inside the same release.

I have upgraded the dotnet 5 sdk to the latter in nixpkgs.

@avdv avdv closed this as completed Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9.needs: package (update) This needs a package to be updated
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants