selfci: init at 0-unstable-2026-01-17#481172
Conversation
|
cc @dpc |
08cf998 to
e8a36d2
Compare
| version = "0-unstable-2026-01-17"; | ||
|
|
||
| src = fetchgit { | ||
| url = "https://radicle.dpc.pw/z2tDzYbAXxTQEKTGFVwiJPajkbeDU.git"; |
There was a problem hiding this comment.
How important realistically this host becomes? It's a $5 Hetzner VPS, but if it ever has issues, I will not be breaking NixOS, right? :D
There was a problem hiding this comment.
Heh, if it goes down then it will simply break the package build. I don't really understand how radicle works, but is it possible to pull it from another "node" if your VPS were to go down?
There was a problem hiding this comment.
Are there any plans to add to Nixpkgs a fetchRadicle function that will actually use this protocol directly to download sources?
There was a problem hiding this comment.
Heh, if it goes down then it will simply break the package build. I don't really understand how radicle works, but is it possible to pull it from another "node" if your VPS were to go down?
While the radicle is p2p and the source code is redundantly stored in the network, the git link here is just a wrapper exposing git interface running on my $5 VPS. So when my VPS is down the link won't work. One would need to use radicle itself rad clone rad:z2tDzYbAXxTQEKTGFVwiJPajkbeDU to benefit from the redundancy directly. NixOS/nix#10567 would allow Nix to use rad directly, which would be sweet.
BTW. I thought NixOS / hydra / something was actually caching all the building sources so once this builds all NixOS users would be covered effectively forever, right? Just curious. I think that VPS easily has 99.9% uptime anyway.
There was a problem hiding this comment.
While the radicle is p2p and the source code is redundantly stored in the network, the git link here is just a wrapper exposing git interface running on my $5 VPS.
Why aren't there more of these "wrappers" among the nodes seeding the repo though? Is that just not how it works?
NixOS/nix#10567 would allow Nix to use rad directly, which would be sweet.
That would be nice to see merged.
BTW. I thought NixOS / hydra / something was actually caching all the building sources so once this builds all NixOS users would be covered effectively forever, right? Just curious. I think that VPS easily has 99.9% uptime anyway.
I'm not sure what the details are regarding caching, but regardless the VPS will need to be up on successive version bumps, of course.
There was a problem hiding this comment.
Why aren't there more of these "wrappers" among the nodes seeding the repo though? Is that just not how it works?
Well, git uses centralized URL, but what your comment made me realize, that any public node can serve the same URL, the same way my does. So e.g.
So my instance is:
But here is a public node hosted by Radicle team:
will show in "Clone -> Git":
git clone https://iris.radicle.xyz/z2tDzYbAXxTQEKTGFVwiJPajkbeDU.git selfci
I suspect their node might be a bit more capable and taken care of.
And it seems fetchGit can do urls, so actually we could have redundancy.
There was a problem hiding this comment.
The solution would be to have a fetchFromRadicle function that uses the node configured in your Nix config. This would be analog to a fetchFromIpfs function.
I also believe we need an issue to track the subject of content addressing vs location addressing with Nix fetchers
e8a36d2 to
971ad07
Compare
|
Can I get an approval @doronbehar? |
|
Merge is even better - thanks |
Git is not a hard dependency but some primary functionality will be broken without it.
Four tests fail, so tests are disabled. Did not spend much time investigating.
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.