| 16 Nov 2025 |
 niklaskorz | Patching the lockfile to make sure it only uses one version of dpi is also an option | 14:14:58 |
 PixelHamster | cargo generates the lock file, that's not a maintainable solution | 16:04:27 |
| PixelHamster | I've tried naersk but it sadly couldn't fetch the correct repository, I made an issue on their bug tracker for it | 16:05:15 |
| 17 Nov 2025 |
|  @kttns0ut:matrix.org left the room. | 02:30:11 |
|  Pol joined the room. | 16:20:52 |
| Pol | Hello,
I'm trying to find the issue in here: https://github.com/typst/typst/pull/7374
I succeeded to reproduce the issue at home as well.
Adding LD_LIBRARY_PATH seem to fix the issue, is it the best option we have to fix that? | 16:21:52 |
| Pol | * Hello,
Context: https://github.com/typst/typst/pull/7374
I succeeded to reproduce the issue at home as well.
Adding LD_LIBRARY_PATH seem to fix the issue, is it the best option we have to fix that? | 16:23:19 |
| Pol | I guess adding LD_LIBRARY_PATH = lib.makeLibraryPath [ pkgs.openssl ]; should be OK, do you confirm this is OK to do this? | 16:37:02 |
 Alyssa Ross | Usually I'd consider that a last resort after actually linking the library to the binary | 16:40:03 |
| Pol | OK I understand, what other option do we have here? | 16:40:30 |
| Alyssa Ross | CARGO_TARGET_${stdenv.hostPlatform.rust.cargoEnvVarTarget}_RUSTFLAGS = "-lssl" | 16:41:11 |
| Alyssa Ross | but the 100% best way to do this is to fix upstream to properly link the library | 16:41:30 |
| Pol | I will add your comment in the PR | 16:41:42 |
