| 13 Apr 2023 |
K900 | Just saw it fail to call wslpath | 11:00:01 |
K900 | WSLg: Revert change to use overlayfs for /run/user/ while a more complete fix is investigated | 16:20:08 |
K900 | Welp | 16:20:09 |
| 14 Apr 2023 |
| Siddhesh Bhupendra Kuakde joined the room. | 10:24:13 |
| Siddhesh Bhupendra Kuakde set a profile picture. | 10:35:01 |
| Nehu joined the room. | 13:52:23 |
Nehu | Could someone tell me how to update to a newer channel and get more up-to-date packages than from 22.05?
In a fresh installation, I did the following:
sudo nixos-rebuild switch
sudo nixos-channel --add https://channels.nixos.org/nixos-22.11 nixos
sudo nixos-channel --update
sudo nixos-rebuild switch
The second rebuild outputs errors:
activating the configuration...
Copying /usr/share/applications
Copying /usr/share/icons
rsync: [sender] change_dir "/nix/store/i2cy643r2znpj8bji5f67z3nyb8mwws9-nixos-system-nixos-22.11.3667.87edbd74246/sw/share/icons" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1327) [sender=3.2.6]
Activation script snippet 'copy-launchers' failed (23)
setting up /etc...
setting up /bin...
restarting systemd...
reloading user units for nixos...
setting up tmpfiles
reloading the following units: dbus.service
restarting the following units: nix-daemon.service, systemd-journald.service
starting the following units: logrotate-checkconf.service, network-local-commands.service, nscd.service, systemd-machined.service, systemd-sysctl.service, systemd-tmpfiles-setup-dev.service, systemd-update-done.service
the following new units were started: systemd-oomd.socket
warning: error(s) occurred while switching to the new configuration
and after that, I can't enter WSL anymore...
| 14:12:42 |
Nehu | * Could someone tell me how to update to a newer channel and get more up-to-date packages than from 22.05?
In a fresh installation, I did the following:
sudo nixos-rebuild switch
sudo nixos-channel --add https://nixos.org/channels/nixos-22.11 nixos
sudo nixos-channel --update
sudo nixos-rebuild switch
The second rebuild outputs errors:
activating the configuration...
Copying /usr/share/applications
Copying /usr/share/icons
rsync: [sender] change_dir "/nix/store/i2cy643r2znpj8bji5f67z3nyb8mwws9-nixos-system-nixos-22.11.3667.87edbd74246/sw/share/icons" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1327) [sender=3.2.6]
Activation script snippet 'copy-launchers' failed (23)
setting up /etc...
setting up /bin...
restarting systemd...
reloading user units for nixos...
setting up tmpfiles
reloading the following units: dbus.service
restarting the following units: nix-daemon.service, systemd-journald.service
starting the following units: logrotate-checkconf.service, network-local-commands.service, nscd.service, systemd-machined.service, systemd-sysctl.service, systemd-tmpfiles-setup-dev.service, systemd-update-done.service
the following new units were started: systemd-oomd.socket
warning: error(s) occurred while switching to the new configuration
and after that, I can't enter WSL anymore...
| 14:13:23 |
K900 | That's .. interesting | 14:33:39 |
K900 | Maybe disable copying launchers for now | 14:33:47 |
K900 | wsl.startMenuLaunchers = false; | 14:34:24 |
Arson Copperflame | I fixed that big some time ago, I think. We should really push out a new release sometime soon | 14:34:44 |
K900 | We need to fix the installer situation | 14:35:14 |
K900 | So nixos-wsl is added as a channel | 14:35:19 |
K900 | And updated as normal | 14:35:28 |
Arson Copperflame | I know, I started tinkering on that, but it's probably gonna take some time | 14:36:30 |
Arson Copperflame | I want to do some cleanup first. And I want to make syschdemd use more of the native systemd code, so it hopefully needs less extra maintenance. Microsofts recent patches make me even more reluctant to drop it; it seems we can't trust them to not spontaneously brick the systemd shim | 14:39:32 |
Arson Copperflame | In reply to @nehu:matrix.org
Could someone tell me how to update to a newer channel and get more up-to-date packages than from 22.05?
In a fresh installation, I did the following:
sudo nixos-rebuild switch
sudo nixos-channel --add https://nixos.org/channels/nixos-22.11 nixos
sudo nixos-channel --update
sudo nixos-rebuild switch
The second rebuild outputs errors:
activating the configuration...
Copying /usr/share/applications
Copying /usr/share/icons
rsync: [sender] change_dir "/nix/store/i2cy643r2znpj8bji5f67z3nyb8mwws9-nixos-system-nixos-22.11.3667.87edbd74246/sw/share/icons" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1327) [sender=3.2.6]
Activation script snippet 'copy-launchers' failed (23)
setting up /etc...
setting up /bin...
restarting systemd...
reloading user units for nixos...
setting up tmpfiles
reloading the following units: dbus.service
restarting the following units: nix-daemon.service, systemd-journald.service
starting the following units: logrotate-checkconf.service, network-local-commands.service, nscd.service, systemd-machined.service, systemd-sysctl.service, systemd-tmpfiles-setup-dev.service, systemd-update-done.service
the following new units were started: systemd-oomd.socket
warning: error(s) occurred while switching to the new configuration
and after that, I can't enter WSL anymore...
Can you still get a shell? If not, try the following:
wsl -d NixOS -e /bin/sh -c '/nix/var/nix/profiles/system/activate; source /etc/set-environment; bash -l'
From there you can edit the configuration and rebuild with nixos-rebuild boot (switch won't work). Then run wsl -t NixOS and try starting it again
| 14:52:32 |
K900 | In reply to@nzbr:nzbr.de I want to do some cleanup first. And I want to make syschdemd use more of the native systemd code, so it hopefully needs less extra maintenance. Microsofts recent patches make me even more reluctant to drop it; it seems we can't trust them to not spontaneously brick the systemd shim I wouldn't rely on them not bricking syschdemd either | 15:05:12 |
Arson Copperflame | True, but it's less likely that they brick both | 15:06:15 |
K900 | Maybe we should have some nixos-enter-esque script in a known location so you can run it from the mariner-cbl container | 15:07:28 |
K900 | And then fix your system from there | 15:07:34 |
Arson Copperflame | I think I put something like that into the DistroLauncher branch. The idea is that you can run nixos rescue to get a shell | 15:08:59 |
| 15 Apr 2023 |
K900 | Ugh | 17:41:41 |