!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

673 Members
Rust151 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
16 Nov 2025
@pixelhamster:matrix.orgPixelHamsterI 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 that11:23:22
@ghpzin:envs.net@ghpzin:envs.net 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:envs.net@ghpzin:envs.net 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:matrix.orgniklaskorzPatching the lockfile to make sure it only uses one version of dpi is also an option14:14:58
@pixelhamster:matrix.orgPixelHamstercargo generates the lock file, that's not a maintainable solution 16:04:27
@pixelhamster:matrix.orgPixelHamsterI've tried naersk but it sadly couldn't fetch the correct repository, I made an issue on their bug tracker for it16:05:15
17 Nov 2025
@kttns0ut:matrix.org@kttns0ut:matrix.org left the room.02:30:11
@drupol:matrix.orgPol joined the room.16:20:52
@drupol:matrix.orgPol 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
@drupol:matrix.orgPol * 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
@drupol:matrix.orgPol 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
@qyliss:fairydust.spaceAlyssa RossUsually I'd consider that a last resort after actually linking the library to the binary16:40:03
@drupol:matrix.orgPolOK I understand, what other option do we have here?16:40:30

Show newer messages


Back to Room ListRoom Version: 6