| 24 May 2023 |
raitobezarius | But my priority/urgency is stabilizing the NixOS test framework | 16:10:11 |
raitobezarius | I wanted at least to have something to generate valid empty release notes | 16:10:31 |
raitobezarius | so that next release managers can write a file without feeling stupid :D | 16:10:39 |
raitobezarius | I think we should also add the "test building your manual before pushing anything" step | 16:10:57 |
raitobezarius | My plan though was something much more simpler Robert Hensing (roberth) | 16:11:32 |
raitobezarius | Let's discuss this post-release indeed :) | 16:11:41 |
| 25 May 2023 |
| raitobezarius changed their display name from raitobezarius to disko in NixOS 23.11 when. | 13:32:55 |
| raitobezarius changed their display name from disko in NixOS 23.11 when to raitobezarius. | 13:37:47 |
raitobezarius | FWIW, my current focus / goal is documented here: https://github.com/orgs/NixOS/projects/34/views/1 for ZHF | 17:29:53 |
raitobezarius | squashing all NixOS tests issues (some of them I caused coughs) | 17:30:04 |
lennart | raitobezariusand me had a good meeting today about the Release Notes editing | 17:30:50 |
lennart | the rest is just doing | 17:31:00 |
lennart | hexa: I'd do want your input when i'm i Darmstadt if possible | 17:31:23 |
lennart | * hexa: I'd do want your input when i'm in Darmstadt if possible | 17:31:33 |
hexa | sure | 17:31:57 |
| 26 May 2023 |
raitobezarius | I don't really care about the colors of the bike but | 14:08:02 |
raitobezarius | did backport release-23.05 took the color of backport release-22.11 ?! :D | 14:08:14 |
raitobezarius | if so, do we need to update the release wiki? | 14:08:19 |
hexa | the color on the 22.11 tag is wrong | 14:10:18 |
hexa | this is about a label, not a shed | 14:10:29 |
raitobezarius | bikelabels? | 14:11:29 |
raitobezarius | will update | 14:12:03 |
@me:indeednotjames.com | In reply to @raitobezarius:matrix.org FWIW, my current focus / goal is documented here: https://github.com/orgs/NixOS/projects/34/views/1 for ZHF I am out of the loop, but somehow mkForceing or even stopping eval on i686-linux (or any 32bit, really) when virtualisation.memorySize > 2047 might make sense. See https://github.com/NixOS/nixpkgs/pull/230871
In case that's something you weren't really aware of 😇
| 14:13:05 |
raitobezarius | also: https://github.com/NixOS/release-wiki/pull/64 | 14:13:42 |
raitobezarius | In reply to @me:indeednotjames.com
I am out of the loop, but somehow mkForceing or even stopping eval on i686-linux (or any 32bit, really) when virtualisation.memorySize > 2047 might make sense. See https://github.com/NixOS/nixpkgs/pull/230871
In case that's something you weren't really aware of 😇
Sounds good | 14:14:13 |
raitobezarius | Would you send the PR to qemu-vm? :-] | 14:14:17 |
raitobezarius | This is just an assert to add :) | 14:14:23 |
raitobezarius | I wonder if this was present in previous QEMU versions | 14:14:36 |
raitobezarius | Or is this a QEMU 8.0 new thing | 14:14:43 |
@me:indeednotjames.com | In reply to @raitobezarius:matrix.org Or is this a QEMU 8.0 new thing nope, that has been the case since like ever :) | 14:15:13 |