| 27 Jul 2021 |
 @gytis-ivaskevicius:matrix.org | yeah, I ended up with droping this idea anyways | 04:20:09 |
| @gytis-ivaskevicius:matrix.org | it is such a pain to pick out all the dependencies | 04:20:18 |
| @gytis-ivaskevicius:matrix.org | and somehow in the background those dependencies seem to mix and match between 2.7 and 3.x | 04:20:40 |
| @gytis-ivaskevicius:matrix.org | and you can already see how many of them i have went through, it was such a pain | 04:20:59 |
| @gytis-ivaskevicius:matrix.org | TL;DR: First we need to see nixops v1 deprecated | 04:21:11 |
| @gytis-ivaskevicius:matrix.org | then we can talk | 04:21:17 |
 David Arnold (blaggacao) | In reply to @gytis-ivaskevicius:matrix.org
TL;DR: First we need to see nixops v1 deprecated I have an aversion for (state-full) nixops, v1 & v2 | 21:31:54 |
| David Arnold (blaggacao) | I'm considering the possibility of adding a lib api container to digga, so that we can have a more standardized take on: https://github.com/divnix/devos/blob/8b67cae20a110f296abf91cdba94a3946b1ba647/flake.nix#L92-L94 | 21:34:14 |
| David Arnold (blaggacao) | Such should give sensible guardrails to system-spaced libs, which I apparently happen to be using in every devos env so far. | 21:35:59 |
| David Arnold (blaggacao) | And if system-spacing is superfluous in a particular case, import memoization would make it cheap to do it anyways. | 21:37:49 |
| David Arnold (blaggacao) | (that's the Super Stupid Flakes argument to system-space everything by default, btw.) | 21:56:41 |
| 28 Jul 2021 |
| @gytis-ivaskevicius:matrix.org | This reminds me that Nix impurity removal should be added to that unofficial flakes roadmap. Can anyone send url to that sheet? | 08:35:07 |
| @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 |
