!bxVOQwsVoHhZcmNDGw:nixos.org

Nix + dotnet

113 Members
23 Servers

Load older messages


SenderMessageTime
7 Nov 2025
@corngood:corngood.comCorngoodIs it just because it happens to be newer than anything on nuget.org?03:15:50
@emma:rory.gayEmma [it/its]oh that, no that's unrelated03:16:06
@emma:rory.gayEmma [it/its] dotnet thinks the unlisted package is "newer" due to semver (old format being 1.0.0-preview987654321.abcdefg, new being 1.0.0-preview.20251106-123456+abcdefg, so a lexical string comparison would prefer the former) 03:18:41
@emma:rory.gayEmma [it/its] and well, its nuget.org, so theres nothing i can do about that, no way to delete old versions or whatever 03:20:20
@corngood:corngood.comCorngoodI still think the PackageReference version should just be pinned to the one from nix, and if that's not working because of something peculiar with the version number, trying 1.0.0 would prove it.03:24:22
@corngood:corngood.comCorngoodYou want to stop it from looking in nuget.org at all, so either an exact version match or package source mapping.03:25:21
@emma:rory.gayEmma [it/its] that sounds like pain maintenance wise ^^'
i think ill stick to manually removing it from deps.json for the time being?
03:26:43
@emma:rory.gayEmma [it/its]in other news, since you maintain dotnet-vmr in nixpkgs: any reason why the build output contains tarballs of the {dotnet,aspnetcore}-runtime packages? i'm not too familiar with building dotnet from source03:27:50
@emma:rory.gayEmma [it/its] (particularly in the lib/Private.SourceBuilt.Artifacts.10.0.100-rc.2.25502.107.linux-x64/ directory) 03:28:44
@corngood:corngood.comCorngood
In reply to @emma:rory.gay
that sounds like pain maintenance wise ^^'
i think ill stick to manually removing it from deps.json for the time being?
It shouldn't be that big of a deal. You could for example set a package source mapping in preConfigure
04:19:56
@emma:rory.gayEmma [it/its]oh? how would i do that?04:20:40
@corngood:corngood.comCorngood
In reply to @emma:rory.gay
in other news, since you maintain dotnet-vmr in nixpkgs: any reason why the build output contains tarballs of the {dotnet,aspnetcore}-runtime packages? i'm not too familiar with building dotnet from source
The vmr package shouldn't really be used directly if that's what you mean. Generally you want the runtime/sdk packages, which should have to references to it
04:21:05
@emma:rory.gayEmma [it/its]well yeah, im using the sdk package04:21:18
@emma:rory.gayEmma [it/its]i was just surprised by the 2.4GB download of dotnet-vmr ^^'04:21:29
@corngood:corngood.comCorngoodHow is it being referenced? You shouldn't need it for the ask 04:21:59
@corngood:corngood.comCorngood* How is it being referenced? You shouldn't need it for the sdk04:22:07
@emma:rory.gayEmma [it/its]if nix-output-monitor isnt lying to me, it was for dotnetHook04:22:28
@corngood:corngood.comCorngood
In reply to @emma:rory.gay
oh? how would i do that?
Add it to nuget.config for the _nix source (I'm pretty sure that's what it's called. Look at the source mapping docs
04:23:00
@corngood:corngood.comCorngoodIf anything has runtime deps on vmr that's bad. We should add some asserts for that 04:23:46
@emma:rory.gayEmma [it/its]
this path will be fetched (696.14 MiB download, 2429.92 MiB unpacked):
  /nix/store/hqj210bagnykmd8mj5l2cq9739m9pvfm-dotnet-vmr-10.0.0-rc.2
copying path '/nix/store/hqj210bagnykmd8mj5l2cq9739m9pvfm-dotnet-vmr-10.0.0-rc.2' from 'https://cache.nixos.org'
┏━ Dependency Graph:
┃    ┌─ ⏸ runtime.linux-x64.Microsoft.NETCore.DotNetAppHost-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.NETCore.App.Runtime.linux-x64-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.AspNetCore.App.Runtime.linux-x64-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.NET.ILLink.Tasks-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.NETCore.App.Host.linux-x64-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.DotNet.ILCompiler-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.NETCore.App.Ref-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃    ├─ ⏸ Microsoft.NETCore.DotNetAppHost-10.0.0-rc.2.25502.107 waiting for 1 ↓
┃ ┌─ ⏸ ArcaneLibs-1.0.0-preview.20251104-015635
┃ │  ┌─ ↓ ⏵ dotnet-vmr-10.0.0-rc.2 ⏱ 12s
┃ ├─ ⏸ Microsoft.NETCore.App.Crossgen2.linux-x64-10.0.0-rc.2.25502.107
┃ ⏸ LibMatrix.Federation-1.0.0-preview.20251101-191010+9065475-dirty
┣━━━ Builds           │ Downloads      
┗━ ∑ ⏵ 0 │ ✔ 0 │ ⏸ 14 │ ↓ 1 │ ↓ 0 │ ⏸ 0 │ ⏱ 13s^C
04:23:54
@emma:rory.gayEmma [it/its] tht was the dep graph according to nix-output-monitor 04:24:13
@emma:rory.gayEmma [it/its]no clue why it depends on crossgen2 either, i'm not cross-compiling, nor have AOT or similar enabled04:25:13
@emma:rory.gayEmma [it/its]i should note that ive seemingly always had vmr with dotnet1004:27:13
@emma:rory.gayEmma [it/its]* i should note that ive seemingly always had vmr with dotnet-sdk_1004:27:19
@corngood:corngood.comCorngoodThat will need some investigation and a disallowedReference I guess 04:28:54
@corngood:corngood.comCorngoodMaybe you can help me reproduce this. From your log it looks like it's building e.g. Crossgen2. That should be in the binary cache, and as far as I can tell, there's no runtime dependency on VMR.13:57:25
@emma:rory.gayEmma [it/its]if you need something from me, let me know :)18:55:47
@mahmoudk1000:matrix.orgMahmoud joined the room.19:07:17
@corngood:corngood.comCorngoodI just can't reproduce the requirement for vmr to be downloaded. If you can give me a way to reproduce it, that would be great 19:55:18
@emma:rory.gayEmma [it/its]hold on, let me go commit what i have right now21:34:53

Show newer messages


Back to Room ListRoom Version: 9