| 6 Nov 2023 |
 K900 | And then tries to install it | 17:29:57 |
 pareto-optimal-dev | Oh... hence the dist directory missing | 17:30:31 |
| pareto-optimal-dev |
In reply to
pareto-optimal-dev
In reply to @k900:0upti.me
Your build does nothing Well.. it fails :) But seriously I'm not sure what you mean by does nothing since I get an error. I did find the preferWheels setting though after you said that and will try that route for now before investigating rust/maturin.
Well nix-locate returns nothing for `libmupdfcpp.so` so maybe I delve into rust/maturin instead | 17:31:13 |
| pareto-optimal-dev | matthewcroughan - nix.how: How far are you? I'm pretty clueless on packaging python stuff? | 17:41:36 |
 matthewcroughan | it's not about python, it's about rust | 17:42:55 |
| matthewcroughan | it's just such a bad situation lol | 17:43:49 |
| pareto-optimal-dev | I was just trying to understand importCargoLock if that's what you mean the difficulties are. | 17:44:06 |
| pareto-optimal-dev | It's probably not that and there are bigger dragons past there huh? | 17:44:51 |
| matthewcroughan | it's solvable, it's just annoying and required manual steps | 17:45:23 |
| matthewcroughan | I've found that some of the rust stuff has cargo.locks, but poetry2nix isn't using them even when the maturin and cargo hooks are there | 17:45:45 |
| matthewcroughan | because that would mean IFD | 17:45:54 |
| matthewcroughan | because builtins.fetchTarball isn't being used, so src refers to the tar.gz, not the outPath (narHashed output) | 17:46:23 |
| pareto-optimal-dev | Hm... I guess in the short term I'll have to go back to trying to get docker to work with gpu's then it sounds like. | 17:47:26 |
| matthewcroughan | No, you just have to learn Nix, and do the hard work | 17:48:02 |
| matthewcroughan | if you want it to work for a day, use docker, if you want to use it for a year, or maybe build something that will last, use nix | 17:48:14 |
| matthewcroughan | I know that's tough, but it is true in the python ecosystem | 17:48:30 |
| pareto-optimal-dev | Yeah, it's very brittle. I've been using Nix for many years and manage my system with it. Which is why I know "you just have to learn Nix and do the hardwork" is true but in cases like this could take 100+ hours for me. | 17:49:23 |
| matthewcroughan | yeah, it has taken me hours to do this stuff too, where docker would have potentially taken a few minutes | 17:50:38 |
| matthewcroughan | but the missing information in that statement, is that Docker would have only worked for a few minutes | 17:50:49 |
| matthewcroughan | Once done in Nix, it will continue working, the Dockerfile for the project is probably not reproducible. | 17:51:26 |
| matthewcroughan | So if you care about reproducibility, you kind of have to do it in Nix | 17:51:36 |
| pareto-optimal-dev | In reply to @matthewcroughan:defenestrate.it
So if you care about reproducibility, you kind of have to do it in Nix My problem is typically putting too much time/effort into packaging with Nix honestly. | 17:58:03 |
| matthewcroughan | It's not Nix. It's software in general. | 17:58:29 |
| pareto-optimal-dev | Also, here is an issue related to poetry2nix and tiktoken, not sure if you've seen it:
https://github.com/nix-community/poetry2nix/issues/1155 | 17:58:22 |
| matthewcroughan | I see a lot of misattributed blame on Nix. | 17:58:44 |
| pareto-optimal-dev | I agree that Nix surfaces the mess that crappy build practices have made. However, sometimes I don't have enough free time to counteract that by getting Nix to work ;) | 17:59:23 |
| matthewcroughan | Okay, we can debug this. | 17:59:38 |
| matthewcroughan | First,
Validating consistency between /build/Cargo.lock and /Cargo.lock
/nix/store/546ykj3xf8w5vznnk4m29a0wkzi4phf7-diffutils-3.9/bin/diff: /Cargo.lock: No such file or directory
| 18:00:00 |
| matthewcroughan | Now, you tell me, who's fault is that? | 18:00:05 |
| matthewcroughan | Is that nix's fault? Or is that tiktoken's fault?. | 18:00:12 |
