| 2 Sep 2021 |
David Arnold (blaggacao) | grahamc (he/him): would the operating theory also work for sd iso? (havn't had time to look at it in greater detail) | 15:03:56 |
David Arnold (blaggacao) | * grahamc (he/him): would the operating theory also work for sd and other iso? (havn't had time to look at it in greater detail) | 15:04:05 |
@grahamc:nixos.org | if you're ever making a "real" filesystem like ext4 or whatever: no | 15:05:09 |
@grahamc:nixos.org | if you're saying well we don't need that, let's just do a ramfs: it could work, but you'd need to figure out putting down a bootloader | 15:05:31 |
David Arnold (blaggacao) | I was associating with the time it takes to build the squashfs.. | 15:05:47 |
@grahamc:nixos.org | again, a squashfs is too much of a real FS | 15:06:20 |
@grahamc:nixos.org | there are other approaches you could take | 15:06:40 |
@grahamc:nixos.org | but they have downsides | 15:06:45 |
@grahamc:nixos.org | this is the second time I've tried to make a fast ipxe server for nixos | 15:06:54 |
@grahamc:nixos.org | the first time I took a squashfs-based approach | 15:07:12 |
David Arnold (blaggacao) | manveru pointed to the link today... He's sitting in quite the same boat. | 15:07:31 |
@grahamc:nixos.org | every store path got its own squashfs, each squashfs got its own cpio, and then I'd loop over all the squashes and mount them: | 15:07:33 |
@grahamc:nixos.org | https://github.com/grahamc/netboot.nix/blob/master/quickly.nix#L49-L74 | 15:07:34 |
@grahamc:nixos.org | this repo uses recursive nix to share those cpios / squashes between builds to reduce duplicate work | 15:07:50 |
@grahamc:nixos.org | but recursive nix was not a very good experience, and still had a major issue of UX of copying around big initrd's from build machines to the machine hosting the imafges | 15:08:24 |
@grahamc:nixos.org | by keeping everything Nix does small, the nix-build and nix-copy-closure time is very small | 15:09:15 |
b12f | After updating to devos' master branch, we're running into the following issue:
❯ nix flake update
warning: Git tree '/home/ben/Workspace/os' is dirty
error: input 'bud/beautysh/poetry2nix/flake-utils' follows a non-existent input 'beautysh/flake-utils'
(use '--show-trace' to show detailed location information)
| 15:48:43 |
b12f | Anyone know where this might be coming from? We've tried going back and forth between different branches, deleting lockfiles, etc. | 15:49:11 |
b12f | This doesn't work
bud.inputs.beautysh.inputs.poetry2nix.inputs.flake-utils.follows = "digga/flake-utils-plus/flake-utils";
But I guess something like this would be the way to fix this, no? Interestingly, our flake.nix inputs are basically the same as for devos master
| 15:58:27 |
@timdeh:matrix.org | It should work in theory at least | 15:59:37 |
b12f | results in the following:
error: cannot find flake 'flake:beautysh' in the flake registries)
| 16:00:18 |
@ultranix:matrix.org | what do i do about error: input 'bud/beautysh/poetry2nix/flake-utils' follows a non-existent input 'beautysh/flake-utils' while trying to update flakes | 22:38:45 |
David Arnold (blaggacao) | nix develop github.com:divnix/digga --command nix flake update | 22:41:55 |
David Arnold (blaggacao) | may that could work... | 22:42:02 |
David Arnold (blaggacao) | the problem is the local unpatched nix version... | 22:42:19 |
@ultranix:matrix.org | yeah i figured | 22:43:10 |
David Arnold (blaggacao) | since that patch was merged, pain will be temporary. | 22:43:47 |
b12f | I think for us what did it was running `nix flake lock --update-input <name>` at least the build has now been running for a while | 22:55:40 |
b12f | `<name>` with the name of an input, one after the other down the list | 22:56:44 |
tomberek | This came up in another channel as well. The UI for “nix flake update NAME” means that the NAME flake’s inputs are fetched. And this ends up being a registry lookup. And the most common failure case is “nixpkgs”. Because it resolves and looks as if it updated. But not your input in the current directory, but nixpkgs in your registry. | 23:13:22 |