That introduces a dependence on the registry which is strictly worse.
In any case the flake input isn’t the issue, if you can’t reach cache.nixos.org then either you have a network issue or Fastly’s CDN PoP is unreachable for you. It seems to be a problem particularly for users based in Asia. You can try the TUNA mirror as a workaround in that case.
and this gives the same 404s as cache.nixos.org, so it seems like the problem really is that my config is looking for hashes that aren’t present in the store. Any idea why that would be?
Ok, I was able to fix this by rolling back to Lix 2.91, which I had locally, and then using that to update to the latest Lix nightly, which has a fix for the issue above. Thanks @Postboote and @waffle8946 for taking the time to reply.
BTW (i am one of the lix developers), if you have weird stuff happening on lix nightly, please ask about it in the lix-beta channel on matrix or file a bug report; it’s the most likely place it will be seen. We generally don’t monitor this forum and it can confuse people to see weird bugs that we had in tree for about 2-3 days total.
I’ve been trying my best to post in there about mistakes like this one that we’ve fixed, since not everyone is (or should need to be) paying attention to the change stream.
Other than watching that channel or if we hypothetically added an online update check (specifically for nightlies), it’s going to be hard to notify people about this kind of thing appropriately.
Fair point about the bug tracker, but OP didn’t mention lix, we wouldn’t necessarily know it was a lix specific bug anyway. I assumed they were using nix and ended up searching on nix’s issue tracker instead.
But for other topics, is there an alternative communication channel for those who don’t want to maintain a matrix homeserver?