| 3 Nov 2025 |
 Katie | * Another question: How does nix-darwin detection work? I keep running the uninstaller but /nix/nix-installer uninstall keeps claiming to detect it
EDIT: Okay, I think I figured this one out on my own, I don't think I had read far enough here: https://git.lix.systems/lix-project/lix-installer#uninstalling | 21:34:00 |
| 4 Nov 2025 |
|  whispers (it/fae) joined the room. | 00:45:18 |
|  @dawnofmidnight:catgirl.cloud left the room. | 00:48:32 |
|  yamabukiiro joined the room. | 03:38:36 |
|  cafkafk changed their profile picture. | 08:23:30 |
|  ncfavier changed their profile picture. | 23:55:14 |
| 5 Nov 2025 |
|  UlyssesZhan joined the room. | 04:57:29 |
 aleksi | Has anybody else encountered a segfault in the Clang linker, when cross-compiling Lix x86_64-linux->armv7l-linux? | 11:33:52 |
| aleksi | [110/386] armv7l-unknown-linux-gnueabihf-clang++ -o lix/libutil/liblixutil.so lix/libutil/liblixutil.so.p/archive.cc.o lix/libutil/liblixutil.so.p/args.cc.o lix/libutil/liblixutil.so.p/async-io.cc.o lix/libuti>
FAILED: lix/libutil/liblixutil.so
armv7l-unknown-linux-gnueabihf-clang++ -o lix/libutil/liblixutil.so lix/libutil/liblixutil.so.p/archive.cc.o lix/libutil/liblixutil.so.p/args.cc.o lix/libutil/liblixutil.so.p/async-io.cc.o lix/libutil/liblixut>
clang++: warning: argument unused during compilation: '-Wa,--compress-debug-sections' [-Wunused-command-line-argument]
/nix/store/p62fsx79cp4ml2mrpxhlk52xxa7x6ns4-armv7l-unknown-linux-gnueabihf-binutils-wrapper-2.44/bin/armv7l-unknown-linux-gnueabihf-ld: line 273: 1390 Segmentation fault (core dumped) /nix/store/yp8bf0w3w>
clang++: error: linker command failed with exit code 139 (use -v to see invocation)
| 11:34:08 |
| aleksi | * armv7l-unknown-linux-gnueabihf-clang++ -o lix/libutil/liblixutil.so lix/libutil/liblixutil.so.p/archive.cc.o lix/libutil/liblixutil.so.p/args.cc.o lix/libutil/liblixutil.so.p/async-io.cc.o lix/libutil/liblixutil.so.p/canon-path.cc.o lix/libutil/liblixutil.so.p/cgroup.cc.o lix/libutil/liblixutil.so.p/compression.cc.o lix/libutil/liblixutil.so.p/compute-levels.cc.o lix/libutil/liblixutil.so.p/config.cc.o lix/libutil/liblixutil.so.p/current-process.cc.o lix/libutil/liblixutil.so.p/deprecated-features.cc.o lix/libutil/liblixutil.so.p/english.cc.o lix/libutil/liblixutil.so.p/environment-variables.cc.o lix/libutil/liblixutil.so.p/error.cc.o lix/libutil/liblixutil.so.p/escape-char.cc.o lix/libutil/liblixutil.so.p/escape-string.cc.o lix/libutil/liblixutil.so.p/experimental-features.cc.o lix/libutil/liblixutil.so.p/file-descriptor.cc.o lix/libutil/liblixutil.so.p/file-system.cc.o lix/libutil/liblixutil.so.p/fmt.cc.o lix/libutil/liblixutil.so.p/git.cc.o lix/libutil/liblixutil.so.p/hash.cc.o lix/libutil/liblixutil.so.p/hilite.cc.o lix/libutil/liblixutil.so.p/json-utils.cc.o lix/libutil/liblixutil.so.p/logging.cc.o lix/libutil/liblixutil.so.p/monitor-fd.cc.o lix/libutil/liblixutil.so.p/mount.cc.o lix/libutil/liblixutil.so.p/namespaces.cc.o lix/libutil/liblixutil.so.p/position.cc.o lix/libutil/liblixutil.so.p/print-elided.cc.o lix/libutil/liblixutil.so.p/processes.cc.o lix/libutil/liblixutil.so.p/references.cc.o lix/libutil/liblixutil.so.p/regex.cc.o lix/libutil/liblixutil.so.p/serialise.cc.o lix/libutil/liblixutil.so.p/shlex.cc.o lix/libutil/liblixutil.so.p/signals.cc.o lix/libutil/liblixutil.so.p/source-path.cc.o lix/libutil/liblixutil.so.p/strings.cc.o lix/libutil/liblixutil.so.p/suggestions.cc.o lix/libutil/liblixutil.so.p/tarfile.cc.o lix/libutil/liblixutil.so.p/terminal.cc.o lix/libutil/liblixutil.so.p/thread-name.cc.o lix/libutil/liblixutil.so.p/thread-pool.cc.o lix/libutil/liblixutil.so.p/unix-domain-socket.cc.o lix/libutil/liblixutil.so.p/url-name.cc.o lix/libutil/liblixutil.so.p/url.cc.o lix/libutil/liblixutil.so.p/users.cc.o lix/libutil/liblixutil.so.p/xml-writer.cc.o -flto -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,-soname,liblixutil.so -fsanitize=signed-integer-overflow -fsanitize-undefined-trap-on-error -shared-libsan -pthread -Wl,--no-copy-dt-needed-entries -Wl,--start-group /nix/store/g467h9kds325j3qbx89y8f460di2aa75-aws-sdk-cpp-armv7l-unknown-linux-gnueabihf-1.11.448/lib/libaws-cpp-sdk-core.so /nix/store/g467h9kds325j3qbx89y8f460di2aa75-aws-sdk-cpp-armv7l-unknown-linux-gnueabihf-1.11.448/lib/libaws-cpp-sdk-s3.so /nix/store/jzfhg64w6ma28gnzskaprafjjd9y4cb4-boehm-gc-armv7l-unknown-linux-gnueabihf-8.2.8/lib/libgc.so -lpthread -ldl /nix/store/kgdd79qn2hk82azala1g4ppwf8qrdgnd-boost-armv7l-unknown-linux-gnueabihf-1.87.0/lib/libboost_container.so.1.87.0 /nix/store/s7fa63wvd1y5278lh1rhy2d2ncy32mpi-libseccomp-armv7l-unknown-linux-gnueabihf-2.6.0-lib/lib/libseccomp.so /nix/store/ipzk6pqaqh7d4gyybflpbkw3gxbj4kxz-libarchive-armv7l-unknown-linux-gnueabihf-3.8.0-lib/lib/libarchive.so /nix/store/vg27sszdgp4jfrzmd973sxk5cywq0cdc-brotli-armv7l-unknown-linux-gnueabihf-1.1.0-lib/lib/libbrotlicommon.so /nix/store/vg27sszdgp4jfrzmd973sxk5cywq0cdc-brotli-armv7l-unknown-linux-gnueabihf-1.1.0-lib/lib/libbrotlidec.so /nix/store/vg27sszdgp4jfrzmd973sxk5cywq0cdc-brotli-armv7l-unknown-linux-gnueabihf-1.1.0-lib/lib/libbrotlienc.so /nix/store/cdmrkcwl24rrj1v8g5rixdw702fy27qm-openssl-armv7l-unknown-linux-gnueabihf-3.4.2/lib/libcrypto.so /nix/store/z0h9244p1cgrj1h9wj7fkc9qp0070ni4-capnproto-armv7l-unknown-linux-gnueabihf-1.1.0/lib/libkj-async.so /nix/store/z0h9244p1cgrj1h9wj7fkc9qp0070ni4-capnproto-armv7l-unknown-linux-gnueabihf-1.1.0/lib/libkj.so -Wl,--end-group
clang++: warning: argument unused during compilation: '-Wa,--compress-debug-sections' [-Wunused-command-line-argument]
/nix/store/p62fsx79cp4ml2mrpxhlk52xxa7x6ns4-armv7l-unknown-linux-gnueabihf-binutils-wrapper-2.44/bin/armv7l-unknown-linux-gnueabihf-ld: line 273: 1390 Segmentation fault (core dumped) /nix/store/yp8bf0w3wxh62w5xp5f161pkrfkm16am-armv7l-unknown-linux-gnueabihf-binutils-2.44/bin/armv7l-unknown-linux-gnueabihf-ld ${extraBefore+"${extraBefore[@]}"} ${params+"${params[@]}"} ${extraAfter+"${extraAfter[@]}"}
clang++: error: linker command failed with exit code 139 (use -v to see invocation)
| 11:35:38 |
 K900 | This is not clang linker, it's GNU binutils linker | 13:24:38 |
| aleksi | True, my mistake | 14:32:58 |
 Cyborus | very minor question: is Lix pronounced like "Licks" or like "Leaks"? | 15:50:36 |
 522 it/its ⛯ΘΔ | licks
it's on the faq, https://lix.systems/faq/ bottom question | 15:51:09 |
| 522 it/its ⛯ΘΔ |
Lix is pronounced like licks — i.e. what you might do if someone handed you a delicious ice cream cone; which may or may not be stacked up with lambdas.
| 15:51:15 |
| Cyborus | ooh should've looked there. thanks! | 15:51:37 |
 Unawarewolf | OOOOooooooh that explains the icecream logo!!!!!!!! | 18:55:48 |
| Unawarewolf | that just clicked now!!!! | 18:55:55 |
| Unawarewolf | (having a username checks out moment I think) | 18:56:51 |
| 6 Nov 2025 |
|  nhnn changed their profile picture. | 15:12:33 |
| nhnn changed their profile picture. | 15:18:29 |
| 7 Nov 2025 |
 MangoIV | there seems to be issues with downgrading flake locks resulting into flake locks which follow inputs that are newer than themselves. | 11:34:21 |
| MangoIV | i.e. flakelock with input i1 is has been updated at 10, now it is downgraded to 1, but its inputs, i.e. i1.i2 i1.i3 still are at 7,8, etc. deleting the flake.lock and recreating it fixes it. | 11:35:21 |
| MangoIV | this obviously leads to really problematic incosistencies. | 11:35:41 |
| MangoIV | and it's of course a direct consequence of flake.locks being flat | 11:36:02 |
| MangoIV | It really puzzled me because it made the upstream flake not reproduce anymore. | 11:38:38 |
 kuruczgy | What's the standard procedure when nix store gc breaks with a full disk (is it intended to be broken in this case?
error (ignored): error: aborting transaction: SQL logic error, cannot rollback - no transaction is active (in '/nix/var/nix/db/db.sqlite')
0 store paths deleted, 0.00 MiB freed
error: committing transaction: database or disk is full, database or disk is full (in '/nix/var/nix/db/db.sqlite')
Also after running nix-store --gc a second time my nix daemon crashed, I assume this is not intended (but it's Lix 2.91.3, so maybe this has been fixed since)
systemd-coredump[1048338]: [🡕] Process 1048334 (nix-daemon) of user 0 dumped core.
| 17:37:34 |
| kuruczgy | * What's the standard procedure when nix store gc breaks with a full disk (is it intended to be broken in this case?)
error (ignored): error: aborting transaction: SQL logic error, cannot rollback - no transaction is active (in '/nix/var/nix/db/db.sqlite')
0 store paths deleted, 0.00 MiB freed
error: committing transaction: database or disk is full, database or disk is full (in '/nix/var/nix/db/db.sqlite')
Also after running nix-store --gc a second time my nix daemon crashed, I assume this is not intended (but it's Lix 2.91.3, so maybe this has been fixed since)
systemd-coredump[1048338]: [🡕] Process 1048334 (nix-daemon) of user 0 dumped core.
| 17:39:10 |
 hexa | are you on a cow filesystem? | 18:25:27 |
|  @awwpotato:envs.net changed their display name from awwpotato (she/her) to -> @da157:catgirl.cloud. | 18:30:23 |
