Nix + dotnet | 120 Members | |
| 24 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 Apr 2023 | ||
| hi, i had a go at packaging a dotnet project https://github.com/NixOS/nixpkgs/commit/7d7d2bfee091dd389eb51bdac1a363cfc27643b4 | 14:06:06 | |
| did i miss anything obvious? or is there a way to get a more verbose failure? | 14:07:05 | |
| I don't see anything obvious in your code, but I'm getting a weird error when building all dotnet packages for some reason
| 22:30:04 | |
| * I don't see anything obvious in your code, but I'm getting a weird error when building all dotnet packages for some reason
| 22:30:09 | |
| * I don't see anything obvious in your code, but I'm getting a weird error when building all dotnet packages for some reason
An error that I'm getting for a different derivation, getting the same for all my dotnet derivations
| 22:30:16 | |
| * I don't see anything obvious in your code, but I'm getting a weird error when building all dotnet packages for some reason
An error that I'm getting for a different derivation, getting the same for all my dotnet derivations | 22:30:22 | |
| esterdayperhaps this is a nixpkgs issue that was introduced recently? didn't find anything on it when searching y | 22:30:56 | |
| * perhaps this is a nixpkgs issue that was introduced recently? didn't find anything on it when searching yesterday | 22:31:01 | |
| 2 May 2023 | ||
| ugh mkNugetSource is using mono to run nuget | 18:44:46 | |
| possibly related: https://lore.kernel.org/all/32f156ba80010fd97dbaf0a0cdfc84366608624d.camel@intel.com/ | 18:46:07 | |
| * possibly related: https://lore.kernel.org/all/cb8dc31a-fef2-1d09-f133-e9f7b9f9e77a@sony.com/ | 18:47:36 | |
| I suppose kernel regression would make sense for this issue, wonder if anyone has reported this for mono as well | 19:54:45 | |
In reply to @raphi:tapesoftware.netI think Nuget itself is packaged with mono, as MS only seems to release a .exe for it? | 19:55:30 | |
the bug seems to only happen if the stars align. if i run nuget init outside of the nix sandbox it succeeds. i can also run a highly nontrivial mono application just fine. i can also run a tiny c program that calls mmap(... MAP_32BIT) inside of the nix sandbox. | 19:56:53 | |
yeah i was looking into it. the closest thing the .net core CLI has is dotnet nuget push which doesn't have the same semantics | 19:57:15 | |
| Wish there was a good way to git bisect through kernel versions to check if it is a regression lol | 20:04:10 | |
| * Wish there was a good way to git bisect through kernel versions to check if it is a kernel regression lol | 20:05:40 | |
In reply to @raphi:tapesoftware.netMan it is so weird that the nuget CLI requires mono on linux still... I suppose ms expects people to mostly use the .net core cli? | 20:19:09 | |
| 3 May 2023 | ||
| 14:57:42 | ||
| 16:58:40 | ||
| o/ did anyone figure out whether that kernel bug is causing the nuget segfault? i asked a couple of friends to try building xivlauncher and it works for them on kernel 6.1.23, but fails for me on 6.3.0. (fwiw, the reproducer from the mailing list doesn't reproduce for me, though I didn't try running it in the nix sandbox (no idea how to do that)) | 17:07:22 | |
| 100% confident that it's MAP_32BIT related no evidence that it's this bug in particular | 17:35:49 | |
| 23:56:08 | ||
| 4 May 2023 | ||
| It being a kernel regression makes sense though, with my system rollback not fixing it. I would’ve have to gone back 2 system updates for the rollback to fix it, if it is a kernel regression | 00:34:21 | |
| https://github.com/NixOS/nixpkgs/pull/229851 | 08:41:03 | |
| cool PR! tag somebody with merge access so that it can be merged | 09:13:15 | |
| 6 May 2023 | ||
| 09:04:46 | ||
| 9 May 2023 | ||
| 02:32:37 | ||
| Most people concerned are probably watching #229476, but the kernel regression seems to be acknowledged upstream https://lore.kernel.org/all/20230414185919.4175572-1-Liam.Howlett@oracle.com/T/#m00a0ac8a72bf2f26711b7f8cc56612a8ef62c3d0 | 05:05:09 | |
| 11 May 2023 | ||
| Good that the kernel regression is getting fixed, we should still probably get #229851 merged anyway since it's good change in general Will we aim to get this merged by 23.05? | 02:38:49 | |