| 25 Jan 2023 |
 dminuoso | Well I am setting in nixpkgs.config inside the host config. Im just curious whether I can even make the warning disappear. | 18:44:03 |
 Zhaofeng Li | I think you can explicitly set all of them in meta.nodeNixpkgs but it's quite tedious. The warning is defined here: https://github.com/zhaofengli/colmena/blob/64c46fa0169233d4faed70c52583cd3183c7f5aa/src/nix/hive/eval.nix#L132-L141 | 20:18:56 |
 hexa | dminuoso: can I ask what's holding you back? Interested from a security team perspective. | 20:36:01 |
| hexa | I assume this is work related? | 20:36:12 |
| dminuoso | hexa: Oh yeah. Updating closures for 22.11 is scheduled right after we're done with a critical project, so probably next week or so. | 20:54:16 |
| dminuoso | It was a bit of a mismanagement on my side, at the time it was released we had a lot of folks on vacation. Next time we should probably prepare closures for a new nixos release before the release, but oh well. | 20:55:44 |
| dminuoso | It's a bit of an effort because we have a lot of nixos machines involved, so we have to do audits, backport changes, etc.. | 20:56:28 |
| dminuoso | * It's a bit of an effort because we have a lot of nixos machines involved, so we have to do audits, rebase changes, etc.. | 20:56:39 |
| hexa | you can probably start evaluating the new release as soon as it is branched, which happens roughly ten days before the actual release | 20:58:39 |
| hexa | then you have like 5 weeks to migrate, which might sound short, but I think nixos makes updating far easier than other distros | 20:59:15 |
 Wanja Hentze | In reply to @dminuoso:matrix.org
It's a bit of an effort because we have a lot of nixos machines involved, so we have to do audits, rebase changes, etc.. same here | 22:11:48 |
| Wanja Hentze | for 22.11, we *did* start working on the upgrade in time, but it still took us til mid January to finish it because there was so much breakage this time | 22:12:22 |
| hexa | ok | 22:28:20 |
| 26 Jan 2023 |
| dminuoso | hexa: Sure, at the end its on our schedule, we're just lagging behind ever so slightly., | 07:48:58 |
| dminuoso | It's sometimes difficult to do what seems to be the right thing when there's additional external constraints. Priorities over priorities. | 07:51:12 |
| dminuoso | Zhaofeng Li: The warning still persists in nixos-22.11. Something is quirky here. | 08:13:29 |
| dminuoso | Let me ask differently. Am I supposed to configure nixpkgs inside the initialization import sources.nixpkgs { allowFree = true; } or as a nixos option nixpkgs.config.allowUnfree = true;? | 08:14:05 |
| Zhaofeng Li | In reply to @dminuoso:matrix.org
Zhaofeng Li: The warning still persists in nixos-22.11. Something is quirky here. Oh right, you may be using the released 0.3 version which doesn't have this: https://github.com/zhaofengli/colmena/commit/b5629dca | 08:15:47 |
| Zhaofeng Li | I was going to cut the 0.4.0 release but got sidetracked by so much other stuff 🙁 | 08:16:21 |
| Zhaofeng Li | In reply to @dminuoso:matrix.org
Let me ask differently. Am I supposed to configure nixpkgs inside the initialization import sources.nixpkgs { allowFree = true; } or as a nixos option nixpkgs.config.allowUnfree = true;? Either should work and it should merge the configs correctly | 08:17:19 |
| dminuoso | But only on the not-yet-released colmena. | 08:17:31 |
| dminuoso | Is there anything I can do to speed up the release? :) | 08:18:31 |
| Zhaofeng Li | In reply to @dminuoso:matrix.org
But only on the not-yet-released colmena. Right, at the moment | 08:18:33 |
| Zhaofeng Li | I kind of want to get a couple of PRs that I've neglected in for 0.4, but otherwise not much else is needed | 08:20:06 |
| hexa | using colmena from master for the improved reboot flow alone | 13:17:30 |
| dminuoso | reboot flow? | 13:27:29 |
| dminuoso | What was changed? | 13:27:52 |
| dminuoso | Do you mean that it no longer activates before reboot? | 13:30:01 |
| dminuoso | Oh well, I guess another reason is that my ssh target user name hasnt made it into 0.3.2 either. Mmm | 13:58:11 |
| hexa | In reply to @dminuoso:matrix.org
Do you mean that it no longer activates before reboot? yes, and --reboot | 15:10:43 |
