| 23 Nov 2023 |
 hexa | we need to understand the error | 23:28:14 |
 dpc ⚡️ | In reply to @hexa:lossy.network
post the trace please for allowAliases https://pastebin.com/fWShsnXB | 23:30:02 |
| dpc ⚡️ | In reply to @dpc:dpc.pw
for allowAliases https://pastebin.com/fWShsnXB for cudaSupport https://pastebin.com/4weZkWG5 | 23:31:01 |
| hexa | are you maybe mixing packages between branches? | 23:32:17 |
| dpc ⚡️ | I do have an overlay that adds stuff to the package set:
overlay = { system, pkgs-unstable, pkgs-master }: (final: prev: {
config.allowAliases = true;
# config.cudaSupport = false;
xremap = xremap.packages.${system}.default;
helix = dpc-helix.packages.${system}.default;
dpc-todo = todo.packages.${system}.default;
rblake2sum = rblake2sum.packages.${system}.default;
intel-one-mono = pkgs-x86_64.callPackage ./pkgs/intel-one-mono.nix { };
});
| 23:33:10 |
| dpc ⚡️ | But I decided to switch to 23.11 pre-release to get rid of bunch of things that were adding unstable/master packages to 23.05 package set. | 23:33:59 |
 Lily Foster | In reply to @dpc:dpc.pw
I do have an overlay that adds stuff to the package set:
overlay = { system, pkgs-unstable, pkgs-master }: (final: prev: {
config.allowAliases = true;
# config.cudaSupport = false;
xremap = xremap.packages.${system}.default;
helix = dpc-helix.packages.${system}.default;
dpc-todo = todo.packages.${system}.default;
rblake2sum = rblake2sum.packages.${system}.default;
intel-one-mono = pkgs-x86_64.callPackage ./pkgs/intel-one-mono.nix { };
});
wait can you even add config in an overlay like that? | 23:34:01 |
| dpc ⚡️ | Seems to work. | 23:34:38 |
 Artturin | but probably overrides the other config options | 23:34:54 |
| dpc ⚡️ | I only added it because evaluation was failing and it worked so I didn't think about it too much. | 23:35:47 |
| dpc ⚡️ | But yeah ... this is not a deep merge. :D | 23:36:09 |
| Artturin | `config = prev.config // { allowAliases = true; }; | 23:36:31 |
| Artturin | * `config = prev.config // { allowAliases = true; };` | 23:36:33 |
| Artturin | * config = prev.config // { allowAliases = true; }; | 23:36:39 |
| dpc ⚡️ | In reply to @artturin:matrix.org
config = prev.config // { allowAliases = true; }; Didn't even cause any rebuilds, so I guess it happens to be the same result as the previous versions. But I do see a point. | 23:38:48 |
| dpc ⚡️ | In reply to @hexa:lossy.network
are you maybe mixing packages between branches? I do include bunch of modules from other places like nixos-hardware, home-manager, etc. I guess these might cause it then? I should probably force them to follow the 21.11 nixpkgs input and that's the explanation here? | 23:42:06 |
| 24 Nov 2023 |
| dpc ⚡️ | In reply to @dpc:dpc.pw
I do include bunch of modules from other places like nixos-hardware, home-manager, etc. I guess these might cause it then? I should probably force them to follow the 21.11 nixpkgs input and that's the explanation here? That was it. Thanks. | 00:11:23 |
 Vladimír Čunát | Schedule needs updating:
https://github.com/NixOS/nixpkgs/issues/258640 | 08:12:40 |
 raitobezarius | vcunat: updated | 11:34:40 |
 figsoda | In reply to @hexa:lossy.network
figsoda: can we get 23.11 on search? https://github.com/NixOS/nixos-search/pull/705, btw the command command in the release wiki didn't seem right, I will submit a fix | 16:53:12 |
| figsoda | In reply to @hexa:lossy.network
figsoda: can we get 23.11 on search? * https://github.com/NixOS/nixos-search/pull/705, btw the nix command in the release wiki didn't seem right, I will submit a fix | 16:53:53 |
| figsoda | https://github.com/NixOS/release-wiki/pull/76 | 16:55:34 |
| raitobezarius | For next release: https://github.com/NixOS/nixpkgs/issues/269713 | 20:51:19 |
| 25 Nov 2023 |
| Vladimír Čunát | https://status.nixos.org got updated, showing the 23.11 beta channels now. | 09:09:41 |
|  thoth joined the room. | 11:01:12 |
|  @ciferkey:gnulinux.club joined the room. | 18:52:46 |
| 26 Nov 2023 |
|  Paul Meyer (katexochen) joined the room. | 16:36:52 |
| Paul Meyer (katexochen) | Hey, I've noticed that in the current state, the PR template is a bit confusing, as it still points to the previous release notes after the branch-off. Currently, when opening a PR with breaking changes that won't be backported, the template suggests to update release notes of 23.11. I've found that the PR template will be updated as part of the final release step, see https://nixos.github.io/release-wiki/Final-Release.html#on-the-master-branch. Any objections moving this to the branch-off step (https://nixos.github.io/release-wiki/Branch-Off.html#back-on-the-master-branch) for the future? | 16:49:58 |
| figsoda | I think it makes more sense to be part of branch-off, I will submit a PR | 16:52:04 |
| figsoda | https://github.com/NixOS/release-wiki/pull/77 https://github.com/NixOS/nixpkgs/pull/270196 | 17:05:31 |
