| 31 Mar 2026 |
 neobrain | but I always thought that the absolute store path would be hardcoded e.g. into the DT_NEEDED entries of ELF files - how can that work if the store path is in a different location? | 16:15:10 |
| neobrain | * but I always thought that the absolute store path would be hardcoded e.g. into the DT_NEEDED entries of ELF files - how can that work if the store is in a different location? | 16:15:15 |
| neobrain | * but I always thought that the absolute store path would be hardcoded e.g. into the RUNPATH entries of ELF files - how can that work if the store is in a different location? | 16:16:13 |
 aloisw | There are two ways to have a store in a different location: chroot store (enabled by store setting) which can reuse the cache but needs chroot (or similar) to actually run stuff, and changing the store directory (NIX_STORE_DIR environment variable) which does not need chroot but rebuilds everything (and breaks things that hardcode /nix/store). | 16:23:25 |
| neobrain | ah, that makes sense | 16:28:06 |
 Charles | terminology question: is (_: {}) the fixpoint or is lib.fix (_: {}) the fixpoint | 17:20:03 |
| Charles | * terminology question: is _: {} the fixpoint or is lib.fix (_: {}) the fixpoint | 17:20:30 |
| Charles | or maybe, is _ the fixpoint | 17:26:54 |
| Charles | https://nixos.org/manual/nixpkgs/stable/#auto-generated-11-1.6.3 | 17:28:23 |
| Charles | sounds like lib.fix (_: {}) is the fixed point | 17:28:31 |
| Charles | * sounds like lib.fix (_: {}) is the fixpint | 17:28:34 |
| Charles | * sounds like lib.fix (_: {}) is the fixpoint | 17:28:36 |
| Charles | in the example in that section it has:
# Calculate the fixed point of all composed overlays.
fixedpoint = lib.fix (lib.extends extensions original );
| 17:29:33 |
| aloisw | Both lib.fix (_: {}) and _ should be the fixpoint if I'm not confusing things. | 17:30:38 |
| Charles | good point | 17:31:16 |
 piegames | And {} in that case, for that matter | 17:44:50 |
| Charles | also true | 17:47:53 |
| Charles | well, this is unfortunate. i just tested whether lix's nix-store --import loads everything in memory with a rust program that writes a valid but garbage NAR, and nix-store --import's RSS happily climbed to over 2GB before i decided that was conclusive and killed it | 19:00:46 |
| Charles | is it theoretically possible for nix-store --import to... not do that? | 19:01:23 |
 zoë (she/her) | this install isn't on nixos, no. could you tell me how i could use the installer for this if i don't have root? it immediately tries to escalate permissions and just fails if it doesn't have them, so that's not an option. i also had a look through the options and didn't see anything that would help me for this (tho i was admittedly very tired so it's pretty likely i missed something) | 21:32:21 |
 K900 | What's the end goal? | 21:33:20 |
| zoë (she/her) | basically just getting lix on a remote machine i'm a user on but don't own/administrate | 21:37:29 |
| zoë (she/her) | * | 21:45:58 |
 marshmallow | does anyone know if nix internal json log's ID fields are globally unique? im going to guess maybe within a daemon but not across daemons | 22:55:17 |
| marshmallow | * | 22:57:24 |
| 1 Apr 2026 |
 raitobezarius | id(nextId++ + (((uint64_t) getpid()) << 32)) that's the algorithm for IDs | 08:37:24 |
| raitobezarius | it's unlikely they're unique across multiple invocations | 08:37:45 |
| raitobezarius | (nextId is a global atomic of uint64_t) | 08:38:20 |
| 2 Apr 2026 |
|  TechWiz joined the room. | 08:58:04 |
| TechWiz | hi I'm trying to update from 2.94.0 to 2.95.1 and I got ```WARNING: manual intervention will be required to complete this Lix install!
The Lix daemon is now an instanced unit that is fully socket-activated.
This requires a new systemd unit: nix-daemon@.service
'nix upgrade-nix' will provide a profile with a new Lix, likely one of:
/nix/var/nix/profiles/default
/nix/var/nix/profiles/per-user/root/profile
It will have the instanced systemd unit file at 'lib/systemd/system/nix-daemon@.service'
You should symlink or copy this file to '/etc/systemd/system/nix-daemon@.service',
and then run 'systemctl daemon-reload && systemctl restart nix-daemon.socket'.
Until you do that, all nix commands will require root and '--store local'.
I'm trying to symlink said file `lib/systemd/system/nix-daemon@.service` to `/etc/systemd/system/nix-daemon@.service` but it's not there to begin with?
| 09:07:14 |
