| 13 Sep 2024 |
 colemickens | okay, filed the issue for xcp, and sent a PR for impure-memSize: https://github.com/nix-community/disko/pull/770 | 19:08:09 |
| 14 Sep 2024 |
|  relichunter set a profile picture. | 17:40:58 |
| 15 Sep 2024 |
 lassulus | Enzime: is helping out with maintaining disko from now on, please welcome him kindly :) | 11:46:47 |
| colemickens | I found it a bit tricky to do this right, how can I better specify these partition start/ends that don't leave such awkward gaps: https://github.com/colemickens/nixcfg/blob/06d838e8abe1392433c3ddf08cff23da381f7cee/hosts/h96maxv58/base.nix#L80-L110 | 21:39:51 |
| lassulus | You can do start = 0. sgdisk will choose the next free block then | 21:51:07 |
| lassulus | Which is also the default | 21:51:16 |
| colemickens | the problem with start=0 is ordering | 22:02:24 |
| colemickens | esp with it hoisting ESP to be partition 1 | 22:05:37 |
| colemickens | well I don't know why ESP is being made first, maybe it's alpha sorted by default (since I'm using EF00 not EF02). anyway, I'll set priority. Now just looking for growpart. | 22:18:42 |
| colemickens | I keep doing it by hand and forgetting to set the part label and causing myself a lot of pain. | 22:18:59 |
| colemickens | oh I guess that's a system-level nixos option. hm | 22:34:51 |
| colemickens | I seriously love disko so much. I wish I could fund someone to make a non-VM install process, with lanzaboote, bootspec, etc. I don't think it's that outlandish. If one could compose images with cross-compiled systems without needing to involve qemu, that would just be "end-game". | 22:51:10 |
| colemickens | still, doing a native build, using disko, and then pivoting to a cross-built system is still such a nicer experience than sdcard or other things people do to get nixos on weird platforms. I'm excited to use it for ec2 image as well. | 22:52:21 |
| 16 Sep 2024 |
 arjan5 | colemickens Not sure if it's what you're looking for, but nixos-anywhere can install different-arch systems remotely, even for configs containing disko, lanzaboote, impermanence, etc. I have done this before. | 09:12:30 |
| lassulus | Lanzaboote needs interaction with the efi/bios to deploy your keys there. But I guess everything else could be done by the image builder | 12:43:32 |
 Janik (they/them) | In reply to @lassulus:lassul.us
Lanzaboote needs interaction with the efi/bios to deploy your keys there. But I guess everything else could be done by the image builder I have done that once | 12:44:35 |
| Janik (they/them) | https://github.com/nix-community/disko/pull/383 | 12:45:24 |
| lassulus | ah nice, thanks for the link | 12:46:56 |
 matthewcroughan | error:
… in the condition of the assert statement
at /nix/store/l3amk5lsakpc93him5kry24kax23sn4h-source/lib/customisation.nix:365:17:
364| in commonAttrs // {
365| drvPath = assert condition; drv.drvPath;
| ^
366| outPath = assert condition; drv.outPath;
… while calling the 'seq' builtin
at /nix/store/l3amk5lsakpc93him5kry24kax23sn4h-source/lib/customisation.nix:80:32:
79| newDrv = derivation (drv.drvAttrs // (f drv));
80| in flip (extendDerivation (seq drv.drvPath true)) newDrv (
| ^
81| { meta = drv.meta or {};
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: attribute 'diskoScript' missing
at /nix/store/w4k2mviwfgnqf7bpq3j725b4wghgc2yx-source/lib/make-disk-image.nix:81:7:
80| ''}
81| ${systemToInstall.config.system.build.diskoScript}
| ^
82| '';
| 17:10:10 |
| matthewcroughan | Maybe due to refactors lately? Enzime | 17:10:21 |
| matthewcroughan | This happens by accessing config.system.build.diskoImages | 17:12:41 |
| matthewcroughan | Ah was it changed to diskoImagesScript now? | 17:13:21 |
| matthewcroughan | Oooh it's because I didn't import my disko.nix, but this wasn't caught by the module system | 17:16:06 |
| matthewcroughan | Odd how the diskoImages attribute still gets made | 17:16:16 |
|  silentlurker joined the room. | 20:02:34 |
| 17 Sep 2024 |
|  vandycarlos joined the room. | 01:25:44 |
 Enzime | In reply to @matthewcroughan:defenestrate.it
Odd how the diskoImages attribute still gets made fixed here https://github.com/nix-community/disko/pull/776 :) | 02:03:57 |
| Enzime | Mic92 lassulus what's the difference between merging with the GitHub UI and using mergify queue? should I prefer one or the other? | 03:27:13 |
 Mic92 | @enzime:nixos.dev: mergify builds pull requests with the latest master and merges after ci succeeds. So master should be always green doing this minus flaky tests. That's why this is our preferred merge method. | 04:46:07 |
| lassulus | Sometimes it's easier to press the button if everything is already green | 06:20:08 |
