| 15 Nov 2025 |
|  seapat joined the room. | 17:49:16 |
| 16 Nov 2025 |
|  PixelHamster joined the room. | 10:48:36 |
| PixelHamster | Hi, it's my first time trying to build a package with nix but I seem to have already ran into this issue :')
Is there an easy way for me to run apply this patch or another workaround on the flake that builds my software ? | 10:59:23 |
| PixelHamster | * Hi, it's my first time trying to build a package with nix but I seem to have already ran into this issue :')
Is there an easy way for me to run/apply this patch or another workaround on the flake that builds my software ? | 10:59:37 |
 K900 | Which patch? | 11:08:34 |
| PixelHamster | The allow duplicate deps for cargo vendor or something | 11:22:41 |
| PixelHamster | I have a git package that depends on dpi-1.2.0 from git
and a crates.io package that depends on dpi-1.2.0 from crates.io
and cargo vendor does not like that | 11:23:22 |
 ghpzin | One of the out of tree solutions may handle it fine.
Afaik crane does not:
https://github.com/ipetkov/crane/blob/0cea393fffb39575c46b7a0318386467272182fe/docs/API.md?plain=1#L1063
Maybe crate2nix, naersk or something else can.
Otherwise you could try patching your nixpkgs with rebased patch from that PR, but that may have unintended problems. | 11:55:22 |
| ghpzin | One of the out of tree solutions may handle it fine.
Afaik crane does not:
https://github.com/ipetkov/crane/blob/0cea393fffb39575c46b7a0318386467272182fe/docs/API.md?plain=1#L1063
Maybe crate2nix, naersk or something else can.
Otherwise you could try patching your nixpkgs with rebased patch from that PR, but that may have unintended problems (other than implicit rebuild of everything from nixpkgs that depends on rust). | 11:57:57 |
 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 |
| Pol | Or perhaps you want to do it? | 16:41:51 |
| Alyssa Ross | you're welcome to | 16:41:56 |
| Alyssa Ross | I'm slammed today | 16:41:59 |
| Pol | Same... | 16:42:10 |
| Pol | I'll do it, thanks for the tips | 16:42:14 |
| Alyssa Ross | sometimes whatever crate links the library will have a Cargo feature option to control whether it dlopens or properly links | 16:42:17 |
| 18 Nov 2025 |
|  QuadRadical (Ping) changed their profile picture. | 01:59:42 |
| 19 Nov 2025 |
|  7karni joined the room. | 12:07:30 |
