| 15 Nov 2025 |
 niklaskorz | if you need to patch a dependency's own code then the common solution is to do that in your package's postPatch on $cargoDepsCopy | 14:28:20 |
 K900 | Bleh | 14:28:54 |
 @ghpzin:envs.net | fetchCargoVendor is just runCommand at the very end, so you can probably do the same on top of it.
Or applyPatches on top. | 14:33:25 |
| @ghpzin:envs.net | fetchCargoVendor is just runCommand at the very end, so you can probably do the same inside.
Or applyPatches on top. | 14:33:40 |
|  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: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 | 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 |
