| 3 Oct 2025 |
|  hash joined the room. | 15:34:57 |
|  @aloisw:julia0815.de left the room. | 16:40:35 |
 Philip Taron (UTC-8) | Could someone interested in Rust-in-Nixpkgs look at this?
https://github.com/NixOS/nixpkgs/pull/443183 | 18:07:28 |
| Philip Taron (UTC-8) | I don't have the time to learn whether this is wise or unwise, and I'd love for someone to tell me one way or the other. | 18:07:56 |
 Alyssa Ross | When I looked at it before I concluded there's not really an alternative IIRC | 18:11:14 |
| Alyssa Ross | We can at least clean them up when they're no longer used. | 18:21:50 |
| 4 Oct 2025 |
|  @aidalgol:tchncs.de left the room. | 00:51:20 |
|  Izdihar changed their profile picture. | 02:44:50 |
|  aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their profile picture. | 08:40:53 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their profile picture. | 08:41:22 |
| 5 Oct 2025 |
|  Miku joined the room. | 09:29:43 |
| 7 Oct 2025 |
|  updown joined the room. | 19:47:46 |
| 8 Oct 2025 |
 niklaskorz | Toma: finally got around to debugging the recent fetchCargoVendor issue in zed-editor | 09:44:10 |
| niklaskorz | I'll proceed as suggested and wrap get_manifest_metadata in a try, to proceed with the next manifests in the iterator on failure | 09:44:38 |
| niklaskorz | (unfortunately means zed-editor will be stuck on an old version for a bit as I missed the staging-next branchoff) | 09:45:04 |
| niklaskorz | https://github.com/NixOS/nixpkgs/pull/449845
Rebuild: linux 26442, darwin 16179
insert "this little maneuver" meme
| 10:08:35 |
| niklaskorz | currently building zed-editor 0.206.7 to verify but the vendoring has already passed, so that part is good to go | 10:09:44 |
 leona | it could maybe make its way to staging-next now, as only a few hundred builds are finished yet. but that would require some coordination over in #staging:nixos.org | 10:48:50 |
| leona | I don't know how important this change is | 10:48:58 |
 K900 | I'd rather not | 10:50:43 |
| K900 | I kinda really don't like that change tbh | 10:51:24 |
| K900 | Like why are we even grabbing random manifests like that | 10:51:37 |
| K900 | Can we not either specify that or resolve the top of workspace correctly | 10:51:47 |
| niklaskorz | Happy to discuss alternatives, and I don't know about the original motivation for the glob, maybe @tomasajt:matrix.org can chime in on that | 11:01:19 |
| niklaskorz | So far zed-editor seems to be the first and only package to be affected, so really not that important | 11:14:38 |
| niklaskorz | I'll just have to deal with a couple of weeks of inquiries from unhappy Zed users, but that's ok 😄 | 11:15:07 |
| niklaskorz | 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 |
| niklaskorz | Or well, I would, but I might have to deal with some kind of hardware failure right now | 13:35:09 |
| niklaskorz | 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 |
| niklaskorz | 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 |
