Nix Rust | 641 Members | |
| Rust | 147 Servers |
| Sender | Message | Time |
|---|---|---|
| 8 Oct 2025 | ||
| So far zed-editor seems to be the first and only package to be affected, so really not that important | 11:14:38 | |
| I'll just have to deal with a couple of weeks of inquiries from unhappy Zed users, but that's ok 😄 | 11:15:07 | |
| replacing it with a topdown Path.walk + checking for existence of Cargo.toml now (so it automatically checks the topmost Cargo.toml first) | 13:17:44 | |
| Or well, I would, but I might have to deal with some kind of hardware failure right now | 13:35:09 | |
| oh wow, after some digging I suspect the source of the issue has never been the ordering (although strictly speaking, Path.glob does indeed not guarantee any order)... | 13:49:00 | |
| the failing dependency in question, candle-book, is explicitly excluded by its workspace manifest but still specifies the edition to be inherited from the workspace (which is the source of the cargo metadata failure) | 13:49:40 | |
| might not need a staging PR or fix in fetchCargoVendor after all then, checking if we can do with some patching here | 13:50:22 | |
| doesn't look like it, as we currently have no way to sneak in patches between fetchcargovendor staging and final output | 14:14:22 | |
| so either way the try block is the only real immediate solution (short of the upstream crate fixing its mess) | 14:14:40 | |
| 16:36:56 | ||
| Are anyone interested in integrating RedoxOS with NixOS? I see there has been some efforts to do this before, but it seems to be dormant now. But the Redox OS project seems very promising as a inovative, modern and secure system which would harmonize with nix too. https://gitlab.redox-os.org/redox-os/redox/-/issues/1552 | 16:54:36 | |
| * Is anyone interested in integrating RedoxOS with NixOS? I see there has been some efforts to do this before, but it seems to be dormant now. But the Redox OS project seems very promising as a inovative, modern and secure system which would harmonize with nix too. https://gitlab.redox-os.org/redox-os/redox/-/issues/1552 | 16:54:46 | |
| https://github.com/nix-community/redoxpkgs | 16:55:35 | |
| Afaik the first step would be to bring back relibc | 16:55:47 | |
| @zmitchell:matrix.org looked into this but responded here why he stopped: https://bsky.app/profile/z-mitchell.bsky.social/post/3liahxpqjls2i | 16:56:37 | |
| 17:13:58 | ||
| Too bad relibc was not maintained. https://github.com/NixOS/nixpkgs/blob/1598da9c7d99ba7a769393c04c3c44e8acf55d92/pkgs/top-level/aliases.nix#L2318 | 17:28:51 | |
| So the original build was a mess. Downlaoding tarballs from dropbox and more. But to be able to cross compile we need relibc to work. | 20:32:24 | |
| I might be on board with experimenting a bit as I'm personally interested in Redox | 21:03:39 | |
| I tried to build relibc now, but it requires a lot of experimental rust features to build | 21:04:57 | |
| I wonder if the easiest way is to build relibc inside a redox vm | 21:06:09 | |
you mean -Z build-std=core,alloc,compiler_builtins? | 21:07:10 | |
| because we support those without nightly on nixpkgs now, technically | 21:07:57 | |
| things like #[target_feature(enable = "tbm")] | 21:08:14 | |
| hm target_feature shouldn't require nightly though? | 21:10:22 | |
| now that, on the other hand: | 21:23:13 | |
| 21:23:16 | |
| I'd be surprised if we end up packaging redox's downstream rustc fwiw | 21:23:47 | |
| but last development update says they "just need to finish up" moving to upstream so maybe that's not too much of a concern | 21:25:05 | |
| 9 Oct 2025 | ||
| I'm trying to package a python package using
But it fails with
The
Am I supposed to do something extra to fetch this dep? | 12:02:50 | |