| 10 Mar 2025 |
 raitobezarius | that surprise me a lot | 21:11:42 |
 ElvishJerricco | yea me too | 21:11:56 |
| ElvishJerricco | makes me think it's not the 4GB issue at all | 21:12:03 |
| raitobezarius | at this point, i'd ask sha256sum | 21:12:45 |
| raitobezarius | for the uefi binary | 21:12:48 |
| ElvishJerricco | emily: btw can you think of a fancy jj command to find the commit where the systemd update commit I want them to test was merged into master? | 21:15:24 |
| ElvishJerricco | obviously the systemd update was on staging | 21:15:34 |
 emily | master here as a proxy for a channel bump? | 21:18:43 |
| ElvishJerricco | pretty much | 21:18:55 |
| ElvishJerricco | I'm trying to find the masters before and after that round of staging | 21:19:05 |
| emily | roots(commit:: & description(glob:"staging-next *")) is kinda lame, but it works | 21:24:12 |
| emily | there's probably something nicer you can do with the topology | 21:24:24 |
| emily | if you could access the first-parents (planned feature) it would be easy, but it's a little bit mind-bending without that | 21:24:48 |
| ElvishJerricco | yea, might be impossible if you can't distinguish first-parent | 21:28:39 |
| ElvishJerricco | ah darn, the merge's master parent is only mildly cached | 21:34:35 |
| ElvishJerricco | I don't suppose we keep an easily parsed list of commits the channel was bumped to, do we? | 21:35:25 |
| emily | sure. the Hydra eval list | 21:47:19 |
| ElvishJerricco | ended up using this :P https://releases.nixos.org/?prefix=nixos/unstable/ | 21:47:39 |
|  Gaël joined the room. | 22:07:57 |
|  Charles left the room. | 22:30:19 |
| ElvishJerricco | new development on the issue: The 256.7 version of systemd-boot that originally introduced the 4GB boundary bug successfully boots a 24.11 generation but not a nixos-unstable generation | 23:39:00 |
| ElvishJerricco | with the same failure as the 257.2 systemd-boot | 23:39:26 |
| ElvishJerricco | so given that the breakage definitely happens between 256.6 and 256.7, just like the 4GB issue, it's certainly related, but probably a little different since it doesn't happen on a 24.11 generation | 23:40:34 |
 eyJhb | In reply to @elvishjerricco:matrix.org
I don't suppose we keep an easily parsed list of commits the channel was bumped to, do we? I'm planning on starting such a list again. I'm so tired of it not being easily available | 23:56:54 |
| 11 Mar 2025 |
| raitobezarius | In reply to @elvishjerricco:matrix.org
so given that the breakage definitely happens between 256.6 and 256.7, just like the 4GB issue, it's certainly related, but probably a little different since it doesn't happen on a 24.11 generation exciting | 01:16:51 |
| * raitobezarius put one cent on d7ae71b9c187133db028a52cd05145f6c1ef8a50 and one cent on d64193a2a652b15db9cb9ed10c6b77a17ca46cd2 | 01:20:06 |
| ElvishJerricco | K900: I guess I should ask you if anything changed since 24.11 in how the kernels look to systemd-boot that could screw it up? | 02:55:41 |
| ElvishJerricco | because the same systemd-boot is only broken for kernels from unstable, not from 24.11 | 02:56:17 |
 K900 | In reply to @elvishjerricco:matrix.org
K900: I guess I should ask you if anything changed since 24.11 in how the kernels look to systemd-boot that could screw it up? Don't think so? | 05:41:08 |
| ElvishJerricco | yea I didn't think so... I wondered about file size too but the kernel and initrd are both only barely larger in unstable | 05:41:36 |
