| 28 Jul 2021 |
 @gytis-ivaskevicius:matrix.org | I will write something up and will ask to insert it somewhere | 08:35:23 |
 David Arnold (blaggacao) | https://demo.hedgedoc.org/uyQYTpTVQbyvpdcJ6MvlQg# | 10:22:28 |
| David Arnold (blaggacao) | Although flakes is "purity by default", already. Do you refer to banning impurity outright? | 10:23:10 |
| David Arnold (blaggacao) | fufexan: the root cause of the error you had about bud having a __functor w.r.t. nix registry option: https://github.com/NixOS/nixpkgs/pull/131814 | 12:55:14 |
| David Arnold (blaggacao) | Gytis Ivaskevicius: also affects (until fix is merged and backported) https://github.com/gytis-ivaskevicius/flake-utils-plus/blob/51a82925db31073bc4822c9b538a0a3ebf1134b2/lib/autoRegistry.options.nix#L4 | 12:56:17 |
 @teutat3s:pub.solar | Could someone check if with latest commits on digga/main and devos/develop overlays/overrides.nix still works as expected to override the channel to latest for home-manager packages? Got issues with the home-manager neovim option pulling the version from 21.05 instead of unstable again... 😇
I added neovim-unwrapped to the overrides.nix packages
https://rycee.gitlab.io/home-manager/options.html#opt-programs.neovim.enable
| 13:02:23 |
| @teutat3s:pub.solar | I'd like to get neovim version 0.5.0 from unstable but 0.4.4 gets installed | 13:04:57 |
| David Arnold (blaggacao) | teutat3s: What's the failure hypothesis? | 13:42:16 |
| @teutat3s:pub.solar | I add neovim-unwrapped to overlays/overrides.nix, but home-manager doesn't seem to pick up the latest channel and pulls in packages from 21.05 regardless. I expected home-manager to follow the overridden channel, too - is that a misunderstanding on my end? | 13:44:16 |
| David Arnold (blaggacao) | So according to the fup-adapter the overlays get consumed by their respective channel. According to the outputs-builder, the default channel is used as pkgs outside of hosts. | 13:49:34 |
| David Arnold (blaggacao) | * So according to the fup-adapter the overlays get consumed by their respective channel. According to the outputs-builder, the default channel is used as pkgs outside of hosts, that override it. | 13:49:51 |
| David Arnold (blaggacao) | I also tried to make that fact a little more discoverable in this gotcha | 13:50:24 |
| David Arnold (blaggacao) | However, non-portable home confiurations, that is per-host home configurations take pkgs as definied by their respective host, and therefore use that hosts' channel, which might be different from the default channel | 13:52:16 |
| David Arnold (blaggacao) | (which makes sense for very host-specific home-configurations) | 13:52:46 |
| David Arnold (blaggacao) | I think to get to the root of the problem that you described, the next step would be to identify which channel is used for your home configuration in your specific case (portable or non-portable home configuration) and then check if that channel has the overlays that you expect, including overlays/override.nix | 13:56:37 |
| David Arnold (blaggacao) | I clarified the docs. Thanks for bringing this question up teutat3s 👍️ | 14:03:45 |
| David Arnold (blaggacao) | I'll be starting to work on integrating deploy-rs into divnix/bud as a replacement for those somewhat brittle nixos-rebuild* commands. | 14:08:41 |
| @teutat3s:pub.solar | Thanks David Arnold for the detailed explanations, what's the best way to identify which channel is used?
I think our setup is still non-portable, because we didn't integrate the latest changes like https://github.com/divnix/devos/commit/4b9cab40cb1c5d7989c2e3719d743e764128ac2a#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0 for our users yet | 14:15:01 |
| @teutat3s:pub.solar | https://git.b12f.io/pub-solar/os/src/branch/teutat3s-develop/flake.nix#L131 | 14:16:52 |
| David Arnold (blaggacao) | teutat3s: At the example of devos, we can see what overlays are applied to the nixos channel and what overlays are applied to all channels | 14:17:12 |
| David Arnold (blaggacao) | In reply to @teutat3s:pub.solar
https://git.b12f.io/pub-solar/os/src/branch/teutat3s-develop/flake.nix#L131 teutat3s: I had a quick look, but I couldn't find where you are actually accessing pkgs.neovim-unwrapped for any config... | 14:23:37 |
 @kraftnix:matrix.org | Getting a bug with building iso's again ☹️, the error is error: attribute 'our' missing and the target file is in one of my custom modules set in ./modules, but i don't have any issues with bud rebuild or deploy. | 15:41:12 |
| @kraftnix:matrix.org | * Getting a bug with building iso's again ☹️, the error is error: attribute 'our' missing and the target file is in one of my custom modules set in ./modules which uses lib.our, but i don't have any issues with bud rebuild or deploy. | 15:41:48 |
| @kraftnix:matrix.org | * Getting a bug with building iso's again ☹️, the error is error: attribute 'our' missing and the target file is in one of my custom modules set in ./modules which uses lib.our, but i don't have any issues with bud rebuild or deploy.
EDIT: current easy workaround is to comment out imports = [ (digga.lib.importModules ./modules) ]; just to build to iso, although it means I won't be able to build anything that relies on my custom modules when I boot up the iso.
| 15:48:16 |
| @teutat3s:pub.solar | David Arnold: thanks, it’s the default pkg for that home manager neovim option Ii mentioned earlier | 17:48:53 |
| @teutat3s:pub.solar | Which we enable here
https://git.b12f.io/pub-solar/os/src/branch/teutat3s-develop/modules/terminal-life/nvim/default.nix#L44 | 17:50:27 |
 b12f |
Which we enable here
https://git.b12f.io/pub-solar/os/src/branch/teutat3s-develop/modules/terminal-life/nvim/default.nix#L44
We're not following the clean separation between home-manager modules and nixos modules, since some modules set on options from both, and we haven't rewritten to comply with devos standards there.
| 17:56:11 |
| b12f | Not sure if this is an anti pattern that we should strive to resolve sooner rather than later | 17:56:30 |
| David Arnold (blaggacao) | In reply to @kraftnix:matrix.org
Getting a bug with building iso's again ☹️, the error is error: attribute 'our' missing and the target file is in one of my custom modules set in ./modules which uses lib.our, but i don't have any issues with bud rebuild or deploy.
EDIT: current easy workaround is to comment out imports = [ (digga.lib.importModules ./modules) ]; just to build to iso, although it means I won't be able to build anything that relies on my custom modules when I boot up the iso.
Are we talking about pkgs.lib.our as applied to all channels via https://github.com/divnix/devos/blob/8b67cae20a110f296abf91cdba94a3946b1ba647/flake.nix#L89-L96? | 18:11:32 |
| David Arnold (blaggacao) | In reply to @kraftnix:matrix.org
Getting a bug with building iso's again ☹️, the error is error: attribute 'our' missing and the target file is in one of my custom modules set in ./modules which uses lib.our, but i don't have any issues with bud rebuild or deploy.
EDIT: current easy workaround is to comment out imports = [ (digga.lib.importModules ./modules) ]; just to build to iso, although it means I won't be able to build anything that relies on my custom modules when I boot up the iso.
* Are we talking about pkgs.lib.our as (eventually) applied to all channels via https://github.com/divnix/devos/blob/8b67cae20a110f296abf91cdba94a3946b1ba647/flake.nix#L89-L96? | 18:11:42 |
