| 18 May 2025 |
 Whovian9369 | ("Outdated" relative to the SDK that I'm using to build, anyway.) | 22:41:36 |
| Whovian9369 | Oh, maybe I could just change the allowPrerelease key to true? That may be the easiest solution here. | 22:47:52 |
 6pak | what is your actual case? | 22:48:21 |
| 6pak | is the global.json pinning a exactly specific version? | 22:48:32 |
| 6pak | or just the major/feature band | 22:48:39 |
| Whovian9369 | Specific version | 22:48:49 |
| Whovian9369 | $ PAGER= nix log .#git
warning: Git tree '/home/whovian/.flakes/aaru' is dirty
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking source archive /nix/store/czn1ndgzbim47hr5yaqsaagns42854yp-source
source root is source
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: configureNuget
@nix { "action": "setPhase", "phase": "configureNuget" }
The command could not be loaded, possibly because:
* You intended to execute a .NET application:
The application 'new' does not exist.
* You intended to execute a .NET SDK command:
A compatible .NET SDK was not found.
Requested SDK version: 9.0.100
global.json file: /build/source/global.json
Installed SDKs:
9.0.203 [/nix/store/j7w50zcrv5rybkj23vqw062zry8gn1wx-dotnet-sdk-9.0.203/share/dotnet/sdk]
Install the [9.0.100] .NET SDK or update [/build/source/global.json] to match an installed SDK.
Learn about SDK resolution:
https://aka.ms/dotnet/sdk-not-found
| 22:48:59 |
| 6pak | I'd just rm the global.json | 22:49:32 |
| 6pak | assuming the build still works on 9.0.2xx | 22:49:42 |
| Whovian9369 | My flake is https://github.com/Whovian9369/aaru-nix-flake (Updating it which is why I'm encountering this)
Upstream is https://github.com/aaru-dps/Aaru
global.json was introduced with https://github.com/aaru-dps/Aaru/commit/8ee0926210df8e3a443456b567e17ad6f319125f | 22:50:07 |
| 6pak | that global.json doesn't make much sense | 22:50:55 |
| 6pak | it would be better to rollForward=latestPatch (aka 9.0.1xx instead) to still receive bug fixes while avoiding bumping the feature band | 22:52:07 |
| 6pak | * it would be better to rollForward=latestPatch (aka 9.0.1xx) to still receive bug fixes while avoiding bumping the feature band | 22:52:16 |
| 6pak | * it would be better to rollForward=latestPatch (aka 9.0.1xx) to still receive bug fixes assuming avoiding the feature band bump was the intention | 22:53:01 |
| Whovian9369 | Are you saying in respect to what Upstream should do, or what I should do for my Nix packaging? | 22:53:28 |
| 6pak | what upstream should do | 22:53:50 |
| 6pak | you probably should just ^ | 22:53:57 |
| 6pak | global.json doesn't really matter because you specify the sdk version in nix anyway | 22:54:26 |
| 6pak | and if the build really breaks (or anything other unwanted) on 9.0.2xx, just specify sdk_9_0_1xx in nix | 22:55:07 |
| Whovian9369 | I imagine this would still be an issue with rollForward=latestPatch due to our dotnet version being newer, but I'd agree (from my non-programming background) that it sounds like a reasonable suggestion.
$ nix develop .#git
warning: Git tree '/home/whovian/.flakes/aaru' is dirty
[whovian@nixos-wsl:~/.flakes/aaru]$ dotnet --version
9.0.203
| 22:55:26 |
| 6pak | * and if the build really breaks (or anything other unwanted happens) on 9.0.2xx, just specify sdk_9_0_1xx in nix | 22:55:31 |
| Whovian9369 | Cool, thank you very much! | 22:55:33 |
| 6pak | you'd specify sdk_9_0_1xx then, yeah | 22:56:16 |
| Whovian9369 | Thank you for the thoughts! | 22:57:15 |
| 6pak | fyi (at least for now) the 1xx feature band is supported for the whole .net version lifetime | 22:57:15 |
| 6pak | while 2xx and 3xx get EOLed until you land on 4xx | 22:57:27 |
| Whovian9369 | That seems interesting. | 22:57:59 |
| 6pak | because source build officially supports only 1xx | 22:58:36 |
| 6pak | so newer feature bands are MS binaries only | 22:58:51 |
| 6pak | * so later feature bands are MS binaries only | 22:58:58 |
