| 25 Jan 2023 |
 @linus:schreibt.jetzt | it's probably the nixpkgs follows. | 14:53:09 |
| @linus:schreibt.jetzt | Try without that | 14:53:14 |
 Ask Yourself🍉 | That worked, thanks. | 14:55:00 |
| @linus:schreibt.jetzt | It's always a tradeoff between using the same stuff that upstream is tested against, and having fewer copies of nixpkgs 😅 | 14:55:47 |
| Ask Yourself🍉 | Yeah, I thought it was good practice to standardize, but maybe I'm confused about that? | 14:56:24 |
| Ask Yourself🍉 | Should I be standardizing like that by default until something breaks or is it just not even a good idea? | 14:56:40 |
| @linus:schreibt.jetzt | Depends on what you want | 14:56:40 |
| @linus:schreibt.jetzt | if you want as little fuss as possible at the cost of disk space (and being more dependent on your upstreams for security updates), don't use any follows | 14:57:09 |
| Ask Yourself🍉 | Hmmm ok. | 14:57:49 |
| Ask Yourself🍉 | I think I need to get a better understanding of some of the inner workings of Nix.. | 14:58:02 |
| Ask Yourself🍉 | Thank you for the help! | 14:58:06 |
|  dminuoso joined the room. | 17:13:12 |
| dminuoso | Hi. We're still on 22.05 and get warnings like trace: warning: The following Nixpkgs configuration keys set in meta.nixpkgs will be ignored: allowUnfree allowUnsupportedSystem contentAddressedByDefault enableParallelBuildingByDefault showDerivationWarnings strictDepsByDefault
Given that we set meta.nixpkgs = import sources.nixpkgs; (i.e. non-initialised nixpkgs from niv), Im a bit unsure how to squelch those warnings.
Does anyone have an idea?
| 17:15:44 |
 Zhaofeng Li | In reply to @dminuoso:matrix.org
Hi. We're still on 22.05 and get warnings like trace: warning: The following Nixpkgs configuration keys set in meta.nixpkgs will be ignored: allowUnfree allowUnsupportedSystem contentAddressedByDefault enableParallelBuildingByDefault showDerivationWarnings strictDepsByDefault
Given that we set meta.nixpkgs = import sources.nixpkgs; (i.e. non-initialised nixpkgs from niv), Im a bit unsure how to squelch those warnings.
Does anyone have an idea?
If you aren't setting any of the configs, this warning should be harmless. The warning will disappear once you upgrade to 22.11 where most nixpkgs config keys became typed so merging would work as expected. | 18:23:46 |
| 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 |
