!UNVBThoJtlIiVwiDjU:nixos.org

Staging

401 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/129 Servers

Load older messages


SenderMessageTime
29 Jun 2026
@hexa:lossy.networkhexaand jax19:27:29
@glepage:matrix.orgGaƩtan LepageI really don't like how this message sounds X)19:57:43
@k900:0upti.meK900OK I've hit the bootctl thing20:17:33
@k900:0upti.meK900 ElvishJerricco bootctl update just exits with 1 20:17:41
@k900:0upti.meK900https://github.com/systemd/systemd/commit/38433a6d06ef4b3fa1a8e0f92fc1a1e22cdbc49920:22:34
@k900:0upti.meK900I think this is the commit that changed it20:22:38
@grimmauld:m.grimmauld.deGrimmauld (any/all)my jumphost is now running against current staging-next20:22:39
@grimmauld:m.grimmauld.deGrimmauld (any/all)image.png
Download image.png
20:22:39
@debtquity:matrix.orgdebtquitycan this be merged? or is the number of rebuilds the issue and waiting for something else?21:11:22
@hexa:lossy.networkhexanot into this cycle21:11:50
@hexa:lossy.networkhexasays -stdenv on the labels21:12:07
@k900:0upti.meK900OK no it's https://github.com/systemd/systemd/commit/037b9a0680b6dd07dec5c2ef1a13da6eabd398d221:17:21
@k900:0upti.meK900There's some seriously uhhh unconventional logic going on there21:17:38
@k900:0upti.meK900Like genuinely I have no idea who came up with that but it's using error codes to smuggle in non-error info21:20:51
@k900:0upti.meK900In a way that is somehow more confusing the more I stare at it21:21:17
@k900:0upti.meK900OK no wait what the fuck is happening anymore21:41:41
@k900:0upti.meK900I need sleep21:41:43
30 Jun 2026
@k900:0upti.meK900OK great09:37:34
@k900:0upti.meK900 Building 260.2 in a nix-shell bootctl update also fails 09:37:52
@9hp71n:matrix.orgghpzin As mentioned before I am pretty sure it is just systemd-boot-builer picking "fallback" file as installed_version.
The easiest is just a 1 line fix for filtering it out from bootctl status output before matching, ie:
--- a/nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py
+++ b/nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py
@@ -488,6 +488,8 @@
             stdout=subprocess.PIPE,
         ).stdout

+        installed_out = "\n".join([line for line in installed_out.splitlines() if "fallback" not in line])
+
         # See status_binaries() in systemd bootctl.c for code which generates this
         # Matches
         # Available Boot Loaders on ESP:
09:43:14
@k900:0upti.meK900No, it's not09:48:40
@k900:0upti.meK900Actually wait09:49:25
@k900:0upti.meK900Ugh09:49:26
@k900:0upti.meK900I see the problem09:49:29
@k900:0upti.meK900It is that but not in the way I thought09:49:41
@k900:0upti.meK900 We just didn't call bootctl update if our own update check succeeded 09:49:52
@k900:0upti.meK900Which is honestly kinda bad09:49:57
@k900:0upti.meK900Yeah OK this is so stupid09:51:15
@k900:0upti.meK900Ughhhhh the varlink interface works09:53:22
@k900:0upti.meK900But we can't rely on it09:53:24

Show newer messages


Back to Room ListRoom Version: 6