 | Nix + dotnet | 114 Members |
| 23 Servers |
| Nix + dotnet | 114 Members |
| 23 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Aug 2025 | ||
 oatmealraisin | Every default.nix looks pretty much exactly like this | 19:07:52 |
 Whovian9369 | Anyone know if trying to build the Dotnet 10 Preview 6 dotnet-vmr is likely "worth it" for most users?I also noticed https://github.com/NixOS/nixpkgs/issues/431811 which is worrying me, since I'm on quite a lower end system. | 19:19:39 |
| Whovian9369 | * Anyone know if trying to build the Dotnet 10 Preview 6 dotnet-vmr is likely "worth it" for most users to build something?I also noticed https://github.com/NixOS/nixpkgs/issues/431811 which is worrying me, since I'm on quite a lower end system. | 19:19:51 |
| Whovian9369 | * Anyone know if trying to build the Dotnet 10 Preview 6 dotnet-vmr is likely "worth it" for most users to build something else?I also noticed https://github.com/NixOS/nixpkgs/issues/431811 which is worrying me, since I'm on a lower end system and I don't like the idea of waiting a while just for a failed build. | 19:21:04 |
 Corngood | That failure happens quite quickly (configure phase). We just merged a change today that provides debug symbols for VMR builds, so it would be useful if anyone can reproduce the crash and provide a core dump. So far I've never been able to reproduce it. The only caveat is that if stage0 isn't in the binary cache, but it builds and then stage1 crashes, that might take a while... | 19:33:12 |
| Whovian9369 | So it might be good for me to attempt the build anyway? | 19:33:45 |
| Corngood | Well if it's convenient for you, it would be nice to have more data about where it crashes and doesn't crash. You could always set it going and then use dotnetCorePackages.sdk_10_0-bin in the meantime. | 19:35:25 |
| Corngood | How lower end is your system? | 19:35:52 |
| Whovian9369 | Well for one it's running Windows 10 using NixOS-WSL, so ram's already limited there. Intel(R) Core(TM) i7-4770 (8) @ 3.40 GHz with 7.72 reported GB of RAM (supplied to WSL 2?) | 19:37:20 |
| Corngood | Okay, that's not so bad. Even just knowing if it gets past configurePhase without crashing would be interesting. | 19:38:01 |
| Corngood | The build dependencies are quite large though (GBs) in case that's a problem | 19:38:22 |
| Whovian9369 | Meaning what I'd get from the store, or the mid-build artifacts? | 19:38:46 |
| Whovian9369 | * Meaning what I'd get from the cache, or the mid-build artifacts? | 19:38:51 |
 6pak | will it even build with 8gb ram? | 19:38:53 |
| Corngood | It probably depends on the core count. For 8 cores it might be okay. | 19:39:14 |
| Whovian9369 | I'm running a "quick" $ sudo nix store optimise -v so I'll get a list of derivations to build and get back to ya | 19:40:12 |
| Corngood | If anyone else is able to repro https://github.com/NixOS/nixpkgs/issues/431811 and provide a core dump / system info I'd appreciate it. | 19:41:06 |
| Whovian9369 | Do you just want me to try building nixpkgs#dotnetCorePackages.dotnet_10.vmr then? | 19:41:44 |
| Corngood | Only if you're on nixpkgs/master. | 19:42:20 |
| Whovian9369 | I was depending on a fetch-deps output to tell me the derivations that I need for a certain package, so having a specific package to build would help me for testing imo. | 19:42:20 |
| Whovian9369 | Ah, I use Unstable normally. I could throw a flake together to run from nixpkgs/master for this then. | 19:42:54 |
| Corngood | I think you can even just do nix build nixpkgs/master#dotnetCorePackages.dotnet_10.vmr? | 19:43:56 |
| Whovian9369 | Good call | 19:44:16 |
| 6pak | wait, can you do that without github:NixOS/? | 19:44:50 |
| Whovian9369 | Seemingly so, huh. | 19:45:42 |
| 6pak | TIL | 19:45:53 |
| Corngood | I'm not exactly sure how that works when you have a pinned one like: | 19:45:56 |
| Corngood | it must fall back to the global one when there's a branch specified | 19:46:11 |
| Whovian9369 | That seems to match more or less what I'm seeing too then, interesting. | 19:46:58 |
| oatmealraisin | Seems the pack phase isn't using the correct directory, build phase output is Utils -> /build/afbw66jz03aj2fa6cllz2aa4qrf9ay69-source/src/Utils/bin/Release/net8.0/linux-x64/Utils.dll but then the pack phase is erroring with /build/afbw66jz03aj2fa6cllz2aa4qrf9ay69-source/src/Utils/bin/Release/net8.0/Utils.dll' to be packed was not found on disk. | 19:47:18 |