| 20 Mar 2023 |
 K900 | Do you actually have a previous generation where it works the way you expect? | 16:46:39 |
| K900 | If yes, probably time to bisect | 16:46:45 |
 qbit | testing | 16:50:22 |
| qbit | at nixpkgs version 5a05160f7671434e1c833b1b01284b876e04eca4 everything is fine.. let me boot some more recent ones | 16:53:48 |
| qbit | ffec117f4b35cd5b11f5005ca8e614d9dd986dec is the commit from my repo where nixpkgs was at that rev | 16:55:45 |
| K900 | Then it might be time to bisect nixpkgs | 16:57:20 |
| qbit | hah, my machine autoupdated after jumping back to the previous generation (haven't restarted into the updated version yet) and now some tabs in firefox look normal and others have the font issue | 17:11:34 |
| qbit | any new tab has the font issue | 17:11:40 |
| K900 | OK, that's interesting | 17:11:52 |
| qbit | are there any guides on bisecting with nixpkgs? | 17:12:04 |
| K900 | Can you nix profile diff-closures the two generations? | 17:12:07 |
| K900 | That might be a good starting point | 17:12:13 |
| qbit | just the output of nix profile diff-closures --profile /nix/var/nix/profiles/system? | 17:18:16 |
| K900 | Well, yes, but also specify which generations are the working one and the non-working ne | 17:19:35 |
| K900 | * Well, yes, but also specify which generations are the working one and the non-working one | 17:19:37 |
| qbit | ok, and nix-env --list-generations --profile /nix/var/nix/profiles/system will show what is currently booted.. but nothing before that? | 17:21:06 |
| K900 | Uhh | 17:21:33 |
| K900 | It should show all of them | 17:21:36 |
| K900 | Did you GC all the old ones? | 17:21:46 |
| qbit | oh, it's showing the what my system was switched to because the upgrade | 17:21:59 |
| qbit | is there a way to show the generation number for a booted system? | 17:22:12 |
| K900 | I'm not sure there's an easy one | 17:22:29 |
| K900 | You can find the symlink in /nix/var/nix/profiles/ that points to the same toplevel as /run/current-system | 17:22:46 |
| K900 | (or /run/booted-system) | 17:22:55 |
| qbit | i could reboot and maybe disable the update process.. | 17:22:58 |
| K900 | Actually, you can just nix store diff-closures /run/booted-system /run/current-system | 17:23:13 |
| K900 | Since we know the booted system is OK and the current is not | 17:23:20 |
| qbit | qbit@europa[0]:~% nix store diff-closures /run/booted-system /run/current-system
dmidecode: 3.4 → 3.5
grantlee: 5.2.0 → 5.3.1, +57.0 KiB
imagemagick: 7.1.1-2 → 7.1.1-3
linux: +17.4 KiB
nixos-system-europa: 23.05.20230319.5a05160 → 23.05.20230320.8276a16
source: +24.8 KiB
systemsettings: -64.6 KiB
tailscale: 1.38.0 → 1.38.1
qbit@europa[0]:~%
| 17:23:46 |
| K900 | Huh. | 17:24:38 |
| K900 | That is not a lot | 17:24:56 |
