| 18 Feb 2022 |
| Pascal Bach joined the room. | 13:48:13 |
| 19 Feb 2022 |
| brian joined the room. | 15:28:26 |
| 22 Feb 2022 |
[0x4A6F] | colemickens 🏳️🌈: AFAIK cargoLock doesn't work for inclusion into nixpkgs. | 20:41:46 |
colemickens | :( okay, I was a bit afraid of that | 20:42:08 |
| * colemickens isn't sure he gets why/how that is though | 20:42:30 |
[0x4A6F] | I've tried cargoLock in following commit and was send away with this error. | 20:46:14 |
[0x4A6F] | Gazing at rfcs#109... | 20:50:36 |
cole-h | Pretty sure cargoLock is IFD unless you copy the Cargo.lock into the nix expression(s directory) | 20:50:46 |
cole-h | Rather, trying to use cargoLock.lockFile = src + "/Cargo.lock"; is IFD. Referencing the actual file by copying it into Nixpkgs is (maybe? probably?) not. | 20:51:35 |
hexa | yep, copying it into nixpkgs is fine | 21:05:16 |
[0x4A6F] | Thanks, but I'll stick to cargoSha256 for now. Cargo.lock is mostly in pkgs/build-support. | 22:28:40 |
| 27 Feb 2022 |
slby | Hey! If I set cargoRoot, is it also possible to point cargoLock to a different file? | 19:03:03 |
slby | Also if I depend on a crate from the same git repo, but the Cargo.toml has a relative path in it, how can I specify it in nix? | 19:13:07 |
| 28 Feb 2022 |
| Florian | W3F changed their display name from Florian | W3F to Florian | W3F - OoO 02.03.. | 10:14:26 |
| 2 Mar 2022 |
| Florian | W3F changed their display name from Florian | W3F - OoO 02.03. to Florian | W3F. | 08:16:38 |
| 3 Mar 2022 |
| colemickens changed their display name from colemickens 🏳️🌈 to colemickens. | 07:10:15 |
| 4 Mar 2022 |
| nixinator joined the room. | 01:20:18 |
nixinator | i have a problem with rust finding fonts, works ok in 'nix develop' shell with 'cargo test' , however, running a cargo test via the derivations fails :-( | 01:21:38 |
Ralith | rust is a programming language; it does not interact with fonts | 02:05:02 |
Ralith | perhaps you had a problem with the font search logic implemented in a particular crate? | 02:05:26 |
slby | This is the problem that crate2nix gives me:
Caused by:
feature `edition2021` is required
consider adding `cargo-features = ["edition2021"]` to the manifest
crate2nix failed.
Does anyone know where I should specify the manifest? I am using generatedCargoNix
| 10:13:11 |
| Vika (she/her) joined the room. | 20:15:49 |
slby | In reply to @slby:matrix.org
This is the problem that crate2nix gives me:
Caused by:
feature `edition2021` is required
consider adding `cargo-features = ["edition2021"]` to the manifest
crate2nix failed.
Does anyone know where I should specify the manifest? I am using generatedCargoNix
I needed to use the unstable channel, then it worked. | 20:17:38 |
| 5 Mar 2022 |
| hikari joined the room. | 21:17:56 |
| 6 Mar 2022 |
| Niklauz joined the room. | 14:56:30 |
| 7 Mar 2022 |
| Nick Hu joined the room. | 18:33:25 |
Nick Hu | Cross posting from the main nixos channel:
Hi, I'm trying to use naersk to build a rust project, but it seems like both the main-deps derivation and the main derivation are compiling all the dependencies of the project, would anyone be able to help me debug this? | 18:34:02 |
Nick Hu | * Cross posting from the main nixos channel:
Hi, I'm trying to use naersk to build a rust project, but it seems like both the main-deps derivation and the main derivation are compiling all the dependencies of the project, would anyone be able to help me debug this?
| 18:52:27 |
Nick Hu | Before main begins its build phase, naersk has successfully untarred a bunch of stuff into ./target/release/..., and I also confirmed manually that the output tarball of the main-deps derivation is not empty (it's > 100MB) | 18:53:30 |
Nick Hu | But for some reason whenever it starts building it wants to recompile everything | 18:53:47 |