| 30 Jul 2025 |
 WeetHet | I don't care about attribution | 16:06:20 |
 emily | what am I holding wrong that just setup fails with lix/lix-doc/meson.build:1:7: ERROR: Subproject exists but has no Cargo.toml file. | 16:52:06 |
| emily | (yes I have been doing non-incremental builds all this time) | 16:52:44 |
 jade_ | oh it's related yes. one of the things i want to know is "how long did this eval spend copying to the store and why/where" | 17:46:55 |
| jade_ | i have no idea. is this some gitignored nonsense state? | 17:47:28 |
| emily | I don't believe so. but it is Jujutsu :) | 17:56:27 |
| emily | lix/lix-doc/Cargo.toml does in fact exist. | 17:56:37 |
| emily | but it's complaining about rnix | 17:56:55 |
| emily | sorry I should have included more output | 17:57:00 |
| emily | Run-time dependency rnix-0.12-rs found: NO (tried pkgconfig, framework and cmake)
Looking for a fallback subproject for the dependency rnix-0.12-rs
Executing subproject rnix-0.12-rs method cargo
lix/lix-doc/meson.build:1: WARNING: Cargo subproject is an experimental feature and has no backwards compatibility guarantees.
rnix-0.12-rs| WARNING: Binary entry all-packages has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry dump-ast has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry error-report has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry from-stdin has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry list-fns has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry preserve has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry test-nixpkgs has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry tidy has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry math has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
rnix-0.12-rs| WARNING: Binary entry s_expressions has unexpected keys "path". This may (unlikely) be an error in the cargo manifest, or may be a missing implementation in Meson. If this issue can be reproduced with the latest version of Meson, please help us by opening an issue at https://github.com/mesonbuild/meson/issues. Please include the crate and version that is generating this warning if possible.
lix/lix-doc/meson.build:1:7: ERROR: Subproject exists but has no Cargo.toml file.
| 17:57:20 |
 Katalin 🔪 | did you somehow manage to get an empty or partial subproject directory, if this is some dependency downloaded using a wrap file? | 17:59:02 |
| Katalin 🔪 | that’s line 1? https://git.lix.systems/lix-project/lix/src/branch/main/lix/lix-doc/meson.build#L1 | 17:59:57 |
| Katalin 🔪 | check the corresponding folder in subprojects (just deleting it should fix it) | 18:00:40 |
| emily | yep, I have exactly that file. subprojects/rnix-0.12.0 seems to contain a full rnix | 18:01:01 |
| emily | but I'll blow away that dir and see | 18:01:10 |
| Katalin 🔪 | * did you somehow manage to get an empty or partial subproject directory, if this is some dependency downloaded using a wrap file the cargo.lock loader? | 18:01:35 |
| emily | now it's happy. go figure | 18:02:00 |
| emily | my guess is that something got interrupted and left the state broken | 18:02:09 |
| Katalin 🔪 | nice! | 18:02:12 |
| emily | if only we had some kind of hash-addressed atomic build system to avoid cache invalidation problems | 18:02:21 |
| Katalin 🔪 | yeah, that can happen, because it only unpacks it if it;s missing | 18:02:28 |
| emily | thanks for the pointer | 18:02:30 |
| Katalin 🔪 | hey, the wrap system is hash-checked! however it is intended to allow you to modify the source directory so you can more easily write a patch for it (meson subprojects packagefiles --save) so it won’t check modifications. | 18:04:44 |
| Katalin 🔪 | but yeah just nuke the subproject source and it will set it up fresh if this happens | 18:05:14 |
| 31 Jul 2025 |
|  Rafael Girão joined the room. | 13:22:38 |
| Rafael Girão | Hi! What's the technical reason against lazy-trees? (assuming it is a technical one)
I just learned about the feature in determinate nix, then I saw Lix's about page:
Lix does not include lazy trees, and does not intend to use the upstream implementation of lazy trees; a functionally equivalent replacement is planned (FIXME: publish the planning document for that).
| 13:29:22 |
| Rafael Girão | Is the planning document public yet? 😅 | 13:29:32 |
 K900 | The implementation in cppnix is basically horribly broken | 13:30:37 |
 raitobezarius | Lix already has an implementation of lazy trees: https://git.lix.systems/lix-project/flake-compat#copying-to-the-store | 13:42:26 |
| raitobezarius | It's not just public yet | 13:42:29 |
