| 17 Feb 2025 |
 522 | # nix flake update
warning: Ignoring the client-specified setting 'tarball-ttl', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'tarball-ttl', because it is a restricted setting and you are not a trusted user
any clue what would be causing this? nix run nixpkgs#nix -- flake update doesn't cause this, so this seems to be a lix specific thing?
# nix --version
nix (Lix, like Nix) 2.92.0
(installed using the lix module on a flakes system)
grepping through my dotfiles for tarball-ttl finds nothing, so i have no clue where it's actually picking that up from
| 02:52:47 |
 Charles | yeah i've been seeing this too, i suspect there's something inside lix that's setting this specifically for nix flake update to try to refresh tarballs | 03:24:40 |
| Charles | i don't think i've seen those warnings appear when doing any operation other than nix flake update | 03:25:03 |
| Charles | friendship ended with nixpkgs.lib.packagesFromDirectoryRecursive, now loadFromDirectoryRecursive and makeScopedPackagesFromDirectoryRecursive are my new best friends: https://gitlab.computer.surgery/charles/dotfiles/-/blob/main/nix/lib/fs.nix?ref_type=heads | 07:25:56 |
| Charles | i've just opened an issue about this since i didn't see an existing one: https://git.lix.systems/lix-project/lix/issues/680 | 07:37:06 |
 julia | In reply to @charles:computer.surgery
yeah i've been seeing this too, i suspect there's something inside lix that's setting this specifically for nix flake update to try to refresh tarballs guessing it's this https://git.lix.systems/lix-project/lix/src/commit/d745b28500c4cd9d865e219502e363efd82751f7/lix/nix/flake.cc#L121 | 10:14:24 |
|  Odd joined the room. | 11:58:51 |
 Arian | “Hmm I wonder why the lack of manpages in 2.26 wasn’t caught by tests” | 15:18:47 |
| Arian |
- apparently they disabled the test because it stopped working after the migration to meson instead of fixing the fact that there are no man pages
https://github.com/NixOS/nix/issues/12382#issuecomment-2661640562
| 15:19:29 |
| Arian | .-. | 15:19:36 |
|  Marcus changed their profile picture. | 21:38:25 |
 Andy Hamon | Is there any sort of tracker that makes it easy to find out which notable bugfixes, features, etc. have been ported from Lix to og Nix and vice versa? | 23:41:39 |
| Andy Hamon | Also, I assume it is fine to submit patches to both projects, right? e.g. i landed my first ever patch to nix, which is something that will soon be a hard dep at my company. So I would need to patch Lix if i want to use it. | 23:45:30 |
| Andy Hamon | Reading the contributing guide, i think so:
For example, the following would likely be accepted assuming it has tests, without needing prior discussion
Backports of CLI UX features from CppNix
| 23:48:19 |
| Charles |
Also, I assume it is fine to submit patches to both projects, right?
yes
| 23:52:05 |
| 18 Feb 2025 |
|  norta joined the room. | 00:10:22 |
|  @mlaga97:matrix.mlaga97.space left the room. | 03:25:12 |
|  Unit 1721344 [polygon] (it/she) changed their profile picture. | 13:02:02 |
|  Nehu joined the room. | 19:44:35 |
| Nehu | Hi ppl! I have an issue with Lix on mac (had it with nix too). I installed rustup (with nix-env -iA) to build rust apps, but when linking, cargo/rustc complains: ld: library not found for -liconv. And here’s the weird thing: if I run nix-shell -p libiconv, it works. But if I install the library with nix-env -iA libiconv, cargo/rustc/ld does’t find the library… | 19:49:59 |
| Nehu | Would someone with more nix knowledge than me be able to tell me why the library is found when inside a nix-shell, but not when the package is installed normally? | 19:51:41 |
 K900 | That is normal and working as intended | 19:51:52 |
| K900 | nix-shell runs setup hooks, nix-env does not | 19:52:05 |
| Charles | not necessarily related to your problem but rustup is not really in the spirit of nix | 19:52:16 |
| Nehu | In reply to @k900:0upti.me
nix-shell runs setup hooks, nix-env does not I see… do you know what kind of hook does the magic? Something with otool? I couldn’t find much but… I also don’t know where to look for answers. | 19:54:00 |
| Nehu | In reply to @charles:computer.surgery
not necessarily related to your problem but rustup is not really in the spirit of nix I assume because the nix way would be to build the apps with nix right? I‘m not quite there yet. Or at least, not anymore for now; there used to be a time where I would nixify both my projects and my environment (with nix-darwin + home manager), but it led to me having to invest too much time in learning nix. | 19:56:50 |
| Charles |
- if you're packaging something, you should make a nix expression to build it entirely in nix
- if you're developing something, you should get your toolchain from nix, e.g. putting
cargo and rustc in your mkShell's packages, or using fenix, or rust-overlay, or something like that. rustup doesn't pin the toolchain, which makes it less reproducible
| 19:58:27 |
 just1602 | Yeah I got my ass bitten by using rustup and not pinning rust in development | 20:00:00 |
| Charles | here is the rust project template i maintain and use frequently if it helps you: https://gitlab.computer.surgery/charles/nix-rust-quickstart | 20:01:36 |
| Nehu | It’s a common problem, which rust also solves outside of nix, even if it’s by far not as reproducible. You can specify which rust toolchain a project targets. | 20:01:56 |
