| 7 Aug 2025 |
 K900 | WSL 2.6.1 is out | 11:22:13 |
| K900 | And it includes my user session fix | 11:22:19 |
| K900 | So now you don't have to wait 10 seconds for it to time out anymore | 11:22:27 |
|  @eju:matrix.org left the room. | 12:20:06 |
| 8 Aug 2025 |
|  0x4A6F joined the room. | 06:28:53 |
| 9 Aug 2025 |
|  seapat set a profile picture. | 14:23:02 |
| 11 Aug 2025 |
 Sandro 🐧 | Can we remove that the base branch always must be up to date? That makes merging trivial dependency updates are real pain. | 16:57:25 |
| K900 | Doesn't github have a ff-and-merge button? | 16:58:47 |
 Alyssa Ross | You'd need a merge queue for it to work, wouldn't you? | 16:59:31 |
 nzbr (they/it) | Done | 19:50:48 |
| nzbr (they/it) | GitHub either creates a merge commit, rebases and fast-forward merges or squashes the PR and applies it as a commit to the base branch. For merging all of these should work in most cases even if the base branch is out of date. If there's a conflict merging will still require manually updating the branch beforehand
The merge queue makes sure that every PR's pipeline will still pass when the PRs that are queued before it are merged. Without a merge queue it's possible to merge two passing branches and end up with failing tests on main. I'd enable the merge queue, but our tests are too unreliable, because WSL just does not start up properly sometimes on the test runners | 19:55:30 |
| nzbr (they/it) | Uhh nice, now there's a button that merges when the pipeline passes | 20:49:40 |
| Sandro 🐧 | thanks! | 22:26:30 |
| nzbr (they/it) | I finally got around to tagging the new release:
https://github.com/nix-community/NixOS-WSL/releases/tag/2505.7.0
We now have release channels, so we can just push changes that would break on versions older than unstable to main and backport those that don't
(Though we should give people a reasonable amount of time to change their channel first. It might even be a good idea to introduce a warning if the nixpkgs version does not match) | 23:31:22 |
|  Ashton joined the room. | 23:37:05 |
| 18 Aug 2025 |
|  fabdb joined the room. | 06:58:21 |
| fabdb | Hey. On an upgrade, do I need to reinstall the whole thing or is nixos-rebuild enough? Couldn't find any documentation on how to upgrade nixos-wsl so I'm assuming the latter?
| 07:17:50 |
| K900 | Upgrade of what? | 07:19:09 |
| nzbr (they/it) | Normally, you just update like on regular NixOS. Because we recently switched to release branches, you'll need to update the channel URL. I put instructions on how to do that in the release notes: https://github.com/nix-community/NixOS-WSL/releases/tag/2505.7.0 | 07:23:01 |
| fabdb | Well, whatever what nixos-wsl does :). There are releases of images anyway. I guess it is not necessary to add a new wsl distribution on every release?
| 08:07:19 |
| fabdb | Thanks, this is what I thought. Wasn't totally clear to me
| 08:08:02 |
|  Shreyas Yadav joined the room. | 13:00:05 |
|  knownasred set a profile picture. | 14:26:00 |
| knownasred changed their display name from redblueflame to knownasred. | 14:26:06 |
 rosssmyth | I am getting some sigsevs, but it seems that systemd-coredump isn't able to be connected to. I get this in journalctl
Aug 18 15:40:13 work kernel: Core dump to |/nix/store/syj2424f551q4l6rvwpx5jzhf4zw8ylh-systemd/lib/systemd/systemd-coredump pipe failed
| 19:54:55 |
| rosssmyth | I'm not that well verse in systemd things so I'm unsure what to look for | 19:55:14 |
| K900 | coredumpd is broken with the WSL container setup | 20:29:48 |
| K900 | Not much you can do really except maybe running it under gdb | 20:30:07 |
| K900 | Or waiting for the possibly eventual coredump socket implementation | 20:30:18 |
| 19 Aug 2025 |
| rosssmyth | unfortunate | 00:42:39 |
