| 15 Feb 2026 |
 lostmsu | * JamieMagee: I pinged you as I had a similar PR open. I also bump SDK to .NET 10 (so that we won't have to touch this for a while). | 23:25:14 |
| lostmsu | My PR: https://github.com/NixOS/nixpkgs/pull/486605 | 23:27:10 |
| lostmsu | BTW, I am co-maintainer of Python.NET (not just on NixOS) | 23:27:41 |
| 19 Feb 2026 |
 Whovian9369 | Hello! What exactly should I do if I go to build a derivation and run into this error?
ln: failed to create symbolic link '/build/nuget.1U96kM/fallback/microsoft.netcore.app.runtime.linux-x64/8.0.23': File exists
| 19:55:31 |
| Whovian9369 | Oh it's likely something to do with repeated entries in deps.json - I'll see if regenerating that fixes it! | 20:00:53 |
| Whovian9369 | Yep, that was it - Whoops. Oh well, apologies! | 20:02:17 |
| 21 Feb 2026 |
 Emma [it/its] | hm, i wonder why buildDotnetModule would... ignore a deps.json file? | 04:04:30 |
| Emma [it/its] | particularly, i did the fetch-deps stuff, the deps.json isnt empty, its staged into git, its referenced in my derivation, yet it complains it cant find any dependencies | 04:08:12 |
| Emma [it/its] | cleared out the deps file and i noticed that it doesnt even seem to write to it, it just does nothing | 04:36:02 |
 Corngood | fetch-deps can only write directly to a deps.json when it's evaluated impure. Maybe you're evaluating it through a flake? In that case you can pass it the output path as a command line arg | 14:22:32 |
| 22 Feb 2026 |
|  Blaze joined the room. | 02:54:34 |
| Emma [it/its] | that's what im doing already | 23:40:09 |
| Emma [it/its] | hence it not making sense that it just... returns [] | 23:41:03 |
| 23 Feb 2026 |
| Corngood | You can run `fetch-drv` in a dev shell and then see what ends up in the nuget packages dir. | 00:54:11 |
| 13 Oct 2022 |
|  Winter (she/her) joined the room. | 17:56:01 |
| 12 Nov 2022 |
|  321, jiayou! joined the room. | 09:31:11 |
| 321, jiayou! left the room. | 09:31:52 |
| 16 Nov 2022 |
|  omlet joined the room. | 20:33:57 |
| 25 Nov 2022 |
|  raphi changed their profile picture. | 19:41:53 |
| 1 Dec 2022 |
|  hexa changed their display name from hexa to hexa (22.11 now). | 13:08:55 |
| hexa changed their display name from hexa (22.11 now) to hexa. | 14:38:43 |
| 12 Jan 2023 |
|  daniel joined the room. | 12:58:04 |
| daniel | Anyone who has some experience with packaging a .NET-project using flakes? All prior art I’ve found seems to use the legacy way. | 13:02:55 |
| Winter (she/her) | In reply to @daniel:nopemail.org
Anyone who has some experience with packaging a .NET-project using flakes? All prior art I’ve found seems to use the legacy way. flakes are the same way as the "legacy way," all flakes help with is exposing the package.
what trouble are you running into? | 14:23:13 |
| daniel | In reply to @winterqt:nixos.dev
flakes are the same way as the "legacy way," all flakes help with is exposing the package.
what trouble are you running into? How to "expose"/run fetch-deps | 14:24:38 |
| Winter (she/her) | just do nix build .#whateverPackage.fetch-deps | 14:25:11 |
| daniel | I did that over and over, realized now that I of course called it with the wrong package name. Thanks though! | 14:29:12 |
| Winter (she/her) | In reply to @daniel:nopemail.org
I did that over and over, realized now that I of course called it with the wrong package name. Thanks though! (was it not erroring?) | 14:31:10 |
| daniel | In reply to @winterqt:nixos.dev
(was it not erroring?) It was, but I thought that meant that somehow fetch-deps didn't pass through correctly. | 14:33:24 |
| 17 Jan 2023 |
| daniel | Fetch-deps doesn't seem to handle project references correctly, am I observing this right? The script wants to look for the project dependencies in the "nuget.org" source. | 11:07:33 |
