| 2 Dec 2021 |
David Arnold (blaggacao) | ^^ that also makes me think if we can create a compat catchall patch layer, so that we can maintain a central file in digga where all the compat stuff could go. A bit tricky, but collecting it structurally and from the community this way, might at least push the boundaries of what "best-effort" actually means. | 17:09:47 |
David Arnold (blaggacao) | (not only for nix,but also for other things that exhibit drift across nix / hm /dawin versions) | 17:10:19 |
| Jarosław Wygoda joined the room. | 21:58:29 |
Jarosław Wygoda | Hi all! I'd like to to build an sd-aarch64 image on x86_64 machine. nixos-generators uses --argstr to specify the target system but it doesn't seem to be compatible with flakes [2]. Is there some workaround for this issue?
[1] https://github.com/nix-community/nixos-generators/blob/ea58f35cba7365b2a661f2bd17fb35cbc7bff572/nixos-generate#L158
[2] https://discourse.nixos.org/t/passing-options-to-flakes/7579 | 22:17:13 |
@danielphan.2003:matrix.org | In reply to @jwwygoda:matrix.org Hi all! I'd like to to build an sd-aarch64 image on x86_64 machine. nixos-generators uses --argstr to specify the target system but it doesn't seem to be compatible with flakes [2]. Is there some workaround for this issue?
[1] https://github.com/nix-community/nixos-generators/blob/ea58f35cba7365b2a661f2bd17fb35cbc7bff572/nixos-generate#L158
[2] https://discourse.nixos.org/t/passing-options-to-flakes/7579 Add boot.binfmt.emulatedSystems = [ "aarch64-linux" ]; to your host config and it should be able to compile. | 22:52:38 |
| 3 Dec 2021 |
Jarosław Wygoda | I've already done that. I'm getting error: Package ‘uboot-rpi_3_defconfig-2021.04’ in /nix/store/bwi8ibq0f0phc01cd6mqsz5hfm27zwgr-source/pkgs/misc/uboot/default.nix:101 is not supported on ‘x86_64-linux’, refusing to evaluate. when executing bud build rpi3 sd-aarch64. nixos-generators suggest using the --system flag. I don't know how to pass it to bud.
https://github.com/nix-community/nixos-generators/tree/ea58f35cba7365b2a661f2bd17fb35cbc7bff572#cross-compiling
| 09:41:38 |
| 4 Dec 2021 |
@gytis-ivaskevicius:matrix.org | https://github.com/NixOS/nix/pull/5577 | 06:02:53 |
@gytis-ivaskevicius:matrix.org | poggers | 06:02:56 |
David Arnold (blaggacao) |
Right associativity has an interesting use case in designing small DSLs around nix use cases
| 20:28:11 |
David Arnold (blaggacao) | ^ would have been my comment, if I could. | 20:28:35 |
David Arnold (blaggacao) | * ^^ would have been my comment, if I could. | 20:28:42 |
David Arnold (blaggacao) | Gytis Ivaskevicius: maybe you remembered when I tried some in fup once. These had been quite bit cleaner had there been right associativity. | 20:29:32 |
David Arnold (blaggacao) | * Gytis Ivaskevicius: maybe you remember when I tried some in FUp once. These had been quite bit cleaner had there been right associativity. | 20:29:59 |
David Arnold (blaggacao) | * Gytis Ivaskevicius: maybe you remember when I tried some in FUP once. These had been quite bit cleaner had there been right associativity. | 20:30:04 |
| 7 Dec 2021 |
@kraftnix:matrix.org | hey all, is anyone having issues with the latest digga where the deploy flake input is no longer following digga's nixpkgs.follows when using deploy.follows = "digga/deploy in a devos-like setup?
not sure if I explained that well, basically since updating from a55450a16d362b6e1c50bb4025aaa604b385d3ba to latest on main, I suddenly have a duplicated nixpkgs which only deploy uses.
| 19:23:58 |
@kraftnix:matrix.org | I also suddenly have three different flake-utils in my lockfile as well, i tend to make all my flake inputs use the same inputs as each other to reduce the size of my closures (particularly for nixpkgs, but I like to do it for all), and this latest updates has introduced a lot of duplicates where I haven't had any for months | 19:27:34 |
@kraftnix:matrix.org | so the only way I managed to workaround and get my devos to behave like it used to (force all inputs to be followed correctly) was to add this horrible best in my inputs:
deploy.url = "github:serokell/deploy-rs";
deploy.inputs.nixpkgs.follows = "latest";
deploy.inputs.utils.follows = "flake-utils-plus/flake-utils";
digga.inputs.deploy.follows = "deploy";
digga.inputs.flake-utils.follows = "flake-utils";
digga.inputs.flake-utils-plus.follows = "flake-utils-plus";
digga.inputs.beautysh.follows = "beautysh";
flake-utils.url = "github:numtide/flake-utils";
flake-utils-plus.url = "github:divnix/flake-utils-plus";
flake-utils-plus.inputs.flake-utils.follows = "flake-utils";
bud.inputs.beautysh.follows = "beautysh";
beautysh.url = "github:lovesegfault/beautysh";
beautysh.inputs.nixpkgs.follows = "nixos";
beautysh.inputs.flake-utils.follows = "flake-utils-plus/flake-utils";
beautysh.inputs.poetry2nix.follows = "poetry2nix";
poetry2nix.url = "github:nix-community/poetry2nix";
poetry2nix.inputs.flake-utils.follows = "flake-utils-plus/flake-utils";
poetry2nix.inputs.nixpkgs.follows = "nixos";
as well as changing all other follows that use flake-utils from digga/flake-utils-plus/flake-utils to flake-utils-plus/flake-utils, it's pretty nasty and I'd rather not have to define these dependencies in my flake inputs when I don't really care about them that much (such as beautysh, poetry2nix) and i'd rather keep following digga's fu and fup without having to deal with the inputs myself, does anyone know why this change might have happened?
| 19:49:59 |
@kraftnix:matrix.org | * so the only way I managed to workaround and get my devos to behave like it used to (force all inputs to be followed correctly) was to add this horrible beast in my inputs:
deploy.url = "github:serokell/deploy-rs";
deploy.inputs.nixpkgs.follows = "latest";
deploy.inputs.utils.follows = "flake-utils-plus/flake-utils";
digga.inputs.deploy.follows = "deploy";
digga.inputs.flake-utils.follows = "flake-utils";
digga.inputs.flake-utils-plus.follows = "flake-utils-plus";
digga.inputs.beautysh.follows = "beautysh";
flake-utils.url = "github:numtide/flake-utils";
flake-utils-plus.url = "github:divnix/flake-utils-plus";
flake-utils-plus.inputs.flake-utils.follows = "flake-utils";
bud.inputs.beautysh.follows = "beautysh";
beautysh.url = "github:lovesegfault/beautysh";
beautysh.inputs.nixpkgs.follows = "nixos";
beautysh.inputs.flake-utils.follows = "flake-utils-plus/flake-utils";
beautysh.inputs.poetry2nix.follows = "poetry2nix";
poetry2nix.url = "github:nix-community/poetry2nix";
poetry2nix.inputs.flake-utils.follows = "flake-utils-plus/flake-utils";
poetry2nix.inputs.nixpkgs.follows = "nixos";
as well as changing all other follows that use flake-utils from digga/flake-utils-plus/flake-utils to flake-utils-plus/flake-utils, it's pretty nasty and I'd rather not have to define these dependencies in my flake inputs when I don't really care about them that much (such as beautysh, poetry2nix) and i'd rather keep following digga's fu and fup without having to deal with the inputs myself, does anyone know why this change might have happened?
| 19:50:23 |
| 9 Dec 2021 |
@cw:kernelpanic.cafe | https://github.com/divnix/devos/blob/main/flake.nix has a bit that refers to core at line 126: base = [ core users.nixos users.root ];
what is that core and where is it defined?
| 02:19:40 |
@cw:kernelpanic.cafe | Answering: https://github.com/divnix/devos/blob/287cb82d1ccd74693ae844869baa34228f143c21/profiles/core/default.nix | 02:21:01 |
@cw:kernelpanic.cafe | I try to enter nix-shell in my devos folder and get error: attribute 'cw' missing, at /nix/store/... which is the middle line here:
suites = with profiles; rec {
base = [ core users.cw users.root ];
};
my user is defined in users/cw/default.nix so it should be raked in. any ideas?
| 06:21:51 |
@danielphan.2003:matrix.org | Have you staged users/cw/default.nix in git? | 06:45:36 |
@cw:kernelpanic.cafe | no! | 07:22:42 |
@cw:kernelpanic.cafe | staging didn't help | 07:25:58 |
@cw:kernelpanic.cafe | Oddly though, the cw user change wasn't staged | 07:26:24 |
@cw:kernelpanic.cafe | * Oddly though, the cw user change wasn't staged either | 07:26:41 |
@cw:kernelpanic.cafe | In reply to @cw:kernelpanic.cafe no! Not intended to be bitchy, lol | 08:20:42 |
David Arnold (blaggacao) | In reply to @kraftnix:matrix.org
hey all, is anyone having issues with the latest digga where the deploy flake input is no longer following digga's nixpkgs.follows when using deploy.follows = "digga/deploy in a devos-like setup?
not sure if I explained that well, basically since updating from a55450a16d362b6e1c50bb4025aaa604b385d3ba to latest on main, I suddenly have a duplicated nixpkgs which only deploy uses.
At work I learned that the follows inputs are not completely gone and that the only really effective way is to reduce & push to the leave:
- reduce -> don't bother about non-nixpkgs, since they are usually libs, are small and don't have huge deps themselves
- push to the leaf: make it a responsability of the end user flake. (Almost) all follows issues that I still hace seen with recent versions could be resolve when the follows statements are used at the leaf.
| 14:27:48 |
David Arnold (blaggacao) | I also may add, that even if it is a "horrible beast" indeed, it's also more transparent and locally reasonable. The latter is a huge win in complexity reduction. | 14:29:18 |
David Arnold (blaggacao) | * I also may add, that even if it is a "horrible beast" indeed, it's also more transparent and locally reasonable. The latter is a huge win in complexity containment. | 14:29:46 |