| 16 Apr 2024 |
 Enric Morales | since the papis-zotero sitedir needs to be patched in papis, right? | 21:25:36 |
| 17 Apr 2024 |
|  @alex3829:matrix.org changed their display name from alex3829 to real_z22. | 04:36:32 |
| @alex3829:matrix.org changed their display name from real_z22 to real_z2. | 05:34:01 |
|  ahoneybun changed their profile picture. | 15:23:58 |
|  JoelMcCracken joined the room. | 16:21:40 |
|  @lychee:lefishe.club changed their display name from kay to kaylee. | 17:10:13 |
| 18 Apr 2024 |
|  @fractivore:cyberia.club left the room. | 02:36:53 |
| 19 Apr 2024 |
|  junglerobba joined the room. | 08:00:19 |
| @lychee:lefishe.club changed their profile picture. | 12:19:27 |
|  Tanja (Old; I'm now @tanja:catgirl.cloud) changed their display name from Tanja to Tanja (Old). | 14:20:55 |
| 20 Apr 2024 |
|  dailyherold joined the room. | 03:01:54 |
| 21 Apr 2024 |
 dminca | Hi everyone, I'm facing an issue when trying to add more nixpkgs urls to my inputs within my flake. I'm on aarm64-darwin
https://codeberg.org/dminca/nix-config/commit/e3802ac776b6829dcf1427581d1e02af05123339
Does anyone know what might've caused this? you think pinning the *-unstable channel to -23-11 could cause such problems?
| 10:24:04 |
| dminca | I forgot to run nix flake update beforehand ... otherwise the rebuild wouldn't have been aware of the new inputs right 🤦♂️ | 10:29:02 |
| dminca | alright this was a catastrophe ... seems the nixos-23-11 branch lacks zsh autosuggestions flag, therefore I just reverted back to nixpkgs-unstable ... | 11:27:26 |
| dminca | * alright this was a catastrophe ... seems the nixos-23-11 branch lacks zsh autosuggestions flag, therefore I just reverted back to nixpkgs-unstable ...
However I'm not sure if this is coming from me pinning nixpkgs or from pinning home-manager https://codeberg.org/dminca/nix-config/commit/decaf43182f8eaf4f4c92ebaf5d78755e72707f1#diff-58cb4f58166586c1ed7f076c568d41682df3661c
| 11:28:08 |
|  mabh joined the room. | 17:17:09 |
| 22 Apr 2024 |
|  sam joined the room. | 11:22:46 |
| sam | What commit of nixpkgs does nix build nixpkgs#foo use? | 11:37:04 |
 Jassuko | Current version of the channel your system or user environment has? | 12:31:53 |
| sam | How does that relate to nix registry? | 12:32:37 |
| sam | If that's the case, why does nix build --eval 'expression containing <nixpkgs>' require the --impure flag, but nix build nixpkgs#foo does not. Is it somehow pure? | 12:34:45 |
| sam | Docs say: --impure: Allow access to mutable paths and repositories., so does nix build nixpkgs#foo not use the mutable paths? | 12:35:48 |
| sam | I'm a little bit confused on the difference between registries and channels, and which are considered immutable | 12:36:20 |
| sam | Also, if that's the case, why does nix build sometimes fetch nixpkgs from GitHub, even though the channel hasn't changed? | 12:37:08 |
| sam | I believe I have a case on my machine where nix build nixpkgs#foo works, but nix-build <nixpkgs> -A foo does not work (build error) | 12:39:05 |
| sam | nix build --impure --expr '(import <nixpkgs> {}).foo' also encounters a build error. How can this kind of error be reproduced on another machine? | 12:45:27 |
 Qyriad | In reply to@charmonium:matrix.org
I'm a little bit confused on the difference between registries and channels, and which are considered immutable Your confusion is understandable, because this is, imho, a major design flaw in the flake registry. Unlike channels the online flake registry doesn't even require a user command to mutate, it simply does | 14:50:54 |
| Qyriad | On NixOS unstable, and the next NixOS release, this issue will be worked around to be much less confusing; flake:nixpkgs and <nixpkgs> will both point to the nixpkgs your system was built with: https://github.com/NixOS/nixpkgs/pull/254405 | 14:52:19 |
| 23 Apr 2024 |
|  nim65s changed their display name from Guilhem to nim65s. | 07:52:53 |
|  peacememories (Old) changed their display name from peacememories to peacememories (Old). | 09:25:38 |
