Today in fun weird little bugs I inflicted upon myself with NixOS:

Flake containing configurations for all of my NixOS machines has configurations for hosts with different architectures (aarch64 and x86_64).

Probably because of that I added a line that explicitly set colmena.meta.nodeNixpkgs for all hosts - it ensured that the configured machines would use package definitions with the correct architecture set for them:

As a side effect, which I didn't notice initially, it also caused nixpkgs.overlays configurations to get duplicated, which didn't manifest itself as a problem until I added a configuration (based on Jovian Experiments) for my Steam Deck. Configs for all the other hosts still evaluated fine, but when I tried to deploy new configs on my steamdeck using colmena, I hit a fun error where it tried to rebuild gamescope, and failed.

Why would this happen? Let's take a look at these two bits of code:
https://github.com/Jovian-Experiments/Jovian-NixOS/blob/ad708a479968eac4ed0aef9bc6dd7380cc6c15da/overlay.nix#L24-L26
https://github.com/Jovian-Experiments/Jovian-NixOS/blob/ad708a479968eac4ed0aef9bc6dd7380cc6c15da/pkgs/gamescope/default.nix#L54-L57

What they essentially do, is that they take gamescope package definition and add a postInstall script. And if you evaluate the overlay twice, you get the postInstall script added twice. And because of how this one works (copies files from nix store, which are read only), next time it tries to overwrite the files, it errors out.

And because it only happened when using colmena, it made looking for the cause of error easier. My dumb luck worked for me this time.

Removing the aforementioned nodeNixpkgs definition fixed this issue, but caused another one: now my arm64 router config got built as x86-64. Good thing I noticed and didn't deploy it, because that sure would've been fun. Probably would've continued to work until reboot, because of binfmt misc emulation being enabled, but figuring out why things fail in weird way later on would probably be puzzling. And made more difficult by the fact that it's my router and I'd have no internet connection without it 

The proper solution turned out to be explicitly setting the node architecture in nixpkgs.system for every node.

Now, this is also weird because I'm already passing system = argument to nixosSystem, and that eventually gets passed along to: https://github.com/NixOS/nixpkgs/blob/master/nixos/lib/eval-config.nix#L50-L56 which, if I'm reading this correctly, should already define nixpkgs.system correctly, but somehow doesn't. I would love to know why that doesn't happen, but I'll have to leave that one little mystery for another time.

#nix #nixos

I might be picking up a replacement #secondHand #laptop tomorrow, a #Toshiba #Satellite L50D-B-172 15.6" (http://www.toshiba.no/discontinued-products/satellite-l50d-b-172/tab/accessories/)

Anyone here on the #Fediverse happen to have experience with this #ToshibaSatellite model, or similar ones?
This one (unfortunately) has a #Norwegian keyboard layout, so I'm not sure what the international model number would be.

Specifically interested in how well it's likely to be supported in #Linux (or even #BSD).

#L50DB172 #L50 #L50D