Hmm.. it's built with nixos-unstable, and we just published one yesterday. Is it stale?

Interesting. Nix carefully tracks runtime and build time dependencies, so this seems surprising to me.

Build for Linux from your Mac. It just works, with Determinate #Nix. Zero config.

Hell yea

@dangoodin.bsky.social re your DNS article ... for a good time:

dig +noall +short disk.vhd.gz.base64.grahamc.com TXT | cut -d'"' -f2 | base64 -d | gzip -d > minimal.vhd

Got a link?

ah! I need some custom stickers made in bulk on short order

Where do people get good stickers from? In the distant past I've used StickerMule.

Hey y’all, I could use help: if you’re using the determinate nix installer in GitHub actions and you’re seeing an increase in CI failures — let me know? We’re slowly rolling out a new version and suspect there is an edge case we haven’t covered.

Lazy trees v2 by edolstra · Pull Request #27 · DeterminateSystems/nix-src Motivation Less invasive variant of NixOS#6530. We now mount lazy accessors on top of /nix/store without materializing them, and only materialize them to the real store if needed (e.g. in the deriv...

So this merged: github.com/DeterminateS...

(not yet released, see the linked comment)

I love the sentiment of this style of message (which I’ve seen you do a bunch of times.) I’ve always wondered what it means though. Is there like, a procedure/coordination? I’d love to see behind the curtain!

Oh my god that is beautiful.

Upgrade to Determinate Nix 3.4, by ... I mean, that picture :) but for posterity:

determinate-nixd login
sudo determinate-nixd upgrade

Or install it for the first time from docs.determinate.systems (we recommend the package on macOS!)

Anyway, Determinate Nix 3.4.1 is now out. It warns if you're using channels, and implicit, or indirect (registry) flake references in flake.nix files. Determinate Nixd had some nits picked, like over-eager error logging. And of course, the `upgrade` command is more instructive.

This represents our values in a lot of ways:

Be honest & transparent: We know this isn't great, here's the bug.

Don't make things worse: Here's how to move forward.

It should feel good to use: It has system specific instructions depending if you're on macOS, NixOS, and Linux.

In the meantime, Determinate Nix 3.4.1 helps you upgrade more successfully. Where it used to crash out on a ridiculous error, now it _tells you_ that you have to log in.

Tracking: Upgrading Determinate Nix soft-requires credentials. · Issue #45 · DeterminateSystems/nix-src Because FlakeHub Cache does not offer any public caches, upgrading Determinate Nix requires being logged in to FlakeHub to download Determinate Nix. This is ... not ideal, to say the least. Further...

that means you have to log in to FlakeHub to download prebuilt upgrades. This is not some brain genius number-go-up-maxxing, but an annoying side effect of Product Design Decisions. I wrote up a tracking ticket for folks while we solve that: github.com/DeterminateS...

An awkward UX issue of Determinate Nix is that we serve it from FlakeHub Cache, which has no unauthenticated access. We do that to make the auth backend very straightforward, avoiding complexity that could lead to leaking customer cache entries. But...

💪

That is THE use case, yeah! I agree. That’s exactly why we’re doing this 💪

It is a VERY bizarre feature, and I’m glad to be deprecating it 😅

These two strategic changes are aimed at eliminating confusion and surprise, and are based on working with our users and hearing their feedback.

I can't wait for Determinate Nix 3.4 to ship on Monday!

The two issues compound with `nixpkgs` (indirect flakeref) and `<nixpkgs>` (nix path/channel "diamond" reference.) They look similar, but mean entirely different things.

It gets worse when root's channels are configured differently from a user's. Even worse still on macOS.

Intent to ship: deprecating usage of flake registry entries in `flake.nix` inputs · Issue #37 · DeterminateSystems/nix-src This is an entry of our roadmap for Determinate Nix, which is guided by user and customer feedback. Over the next months, we will progressively deprecate usage of shorthand flake registry entries a...

Similarly, we frequently see confusion when locking a flake which uses implicit inputs and indirect flakerefs. Indirect flakerefs are great on the CLI. Determinate Nix will start warning when you use them as a flake.nix input url, where they're a negative: github.com/DeterminateS...

Intent to ship: deprecation of channels · Issue #34 · DeterminateSystems/nix-src This is an entry of our roadmap for Determinate Nix, which is guided by user and customer feedback. Over the next months, we will progressively deprecate channels and the nix-channel command. This ...

We've seen countless users trip themselves up on outdated channels and confusing them for the `nixpkgs` flake ref used by `nix run nixpkgs#`, etc.

Determinate Nix Installer hasn't shipped configured channels for years, and now we're warning against them: github.com/DeterminateS...

The next release of Determinate Nix will start addressing two issues that commonly confuse our users:

1. `nix-channel` is deprecated, and using it will issue a warning.
2. Using an indirect flakeref or implicit registry input in a flake.nix will also raise a warning.

>>>

Changelog: JSON logging, a new experience around hash mismatches, and more JSON logging has the potential to unlock all kinds of ergonomic benefits, starting with hash mismatches but with plenty of room to expand beyond that

Determinate Nix 3.3.1 is now out and folks, it is not playing games. We've added JSON logging to Nix and a whole new UX around fixing hash mismatches during Nix builds—and we've fixed some long-standing paper cuts to boot.

determinate.systems/posts/change...

Determinate #Nix 3.2: we fixed the infamous `git add` error. Really.

Hm? No, the daemon tracked the error and the GitHub action wrote the annotation using the error from the daemon.