!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

691 Members
Rust156 Servers

Load older messages


SenderMessageTime
24 Jan 2025
@simon.brandner:envs.net@simon.brandner:envs.netBoth feel like a bit of a hack07:53:11
@pnmadelaine:matrix.orgPaul-Nicolas Madelaine changed their profile picture.09:39:05
@tomasajt:matrix.orgToma I don't know if it has been posted already, but if you're wondering what exactly changed in the upstream cargo vendor implementation that broke the FOD hashes, it's the fact that .cargo-checksum now contains a checksum for Cargo.lock as well. 23:58:53
25 Jan 2025
@tomasajt:matrix.orgTomaMost likely this is the culprit: https://github.com/rust-lang/cargo/pull/1481500:17:57
@tomasajt:matrix.orgToma * I don't know if it has been posted already, but if you're wondering what exactly changed in the upstream cargo vendor implementation that broke the FOD hashes, it's the fact that some dependencies now also have Cargo.lock as part of their crate tree. 12:50:08
26 Jan 2025
@niko:nyanbinary.rsnyanbinary 🏳️‍⚧️https://discourse.nixos.org/t/github-action-fails-to-find-glibc-while-running-nix-provisioned-rsync/56831/16 ouch01:05:49
@niko:nyanbinary.rsnyanbinary 🏳️‍⚧️lol01:05:50
@kranzes:matrix.orgIlan Joselevich (Kranzes) Hah, max is funny 01:08:34
@emilazy:matrix.orgemilyshould we maybe FYI what this broke for us?01:09:28
@emilazy:matrix.orgemilyI suspect that the response would be "that's crazy to rely on"01:09:36
@emilazy:matrix.orgemilybut idk, maybe they'd find the Hyrum's law information useful01:09:45
@rrose:ungleich.chrorosen joined the room.10:29:42
@glepage:matrix.orgGaétan Lepage

bacon now requires alsa to build:
https://github.com/Canop/bacon/pull/309

Should we make this build feature optional (withSound / withAlsa) or provide alsa-lib unconditionally ?

16:56:37
@glepage:matrix.orgGaétan Lepage bump PR: https://github.com/NixOS/nixpkgs/pull/377037 16:58:30
@niko:nyanbinary.rsnyanbinary 🏳️‍⚧️should probably fix it though lol22:00:32
@cadecadet:matrix.orgcadecadet joined the room.23:11:57
27 Jan 2025
@tomasajt:matrix.orgToma

If we want to support vendoring multiple packages with the same name and version, we're going to have to create subdirectories.
The question is should we only put the main culprits (the git dependencies) in their own directory, or should we also put every other dependency in a sibling directory?

So the choice is between:

git-01234/foo-1.0.0
git-56789/foo-1.0.0
bar-0.0.1
baz-0.2.0

or

git-01234/foo-1.0.0
git-56789/foo-1.0.0
registry/bar-0.0.1
registry/baz-0.2.0

The issue with the second version is that packages sometimes want to patch the vendor directory, (aka. $cargoDepsCopy) but they assume that there isn't an extra layer of nesting.

A solution would be to do a treewide PR swapping $cargoDepsCopy/foo-* to $cargoDepsCopy/**/foo-*.

17:09:00
@tomasajt:matrix.orgToma *

If we want to support vendoring multiple packages with the same name and version, we're going to have to create subdirectories.
The question is: should we only put the main culprits (the git dependencies) in their own directory, or should we also put every other dependency in a sibling directory?

So the choice is between:

git-01234/foo-1.0.0
git-56789/foo-1.0.0
bar-0.0.1
baz-0.2.0

or

git-01234/foo-1.0.0
git-56789/foo-1.0.0
registry/bar-0.0.1
registry/baz-0.2.0

The issue with the second version is that packages sometimes want to patch the vendor directory, (aka. $cargoDepsCopy) but they assume that there isn't an extra layer of nesting.

A solution would be to do a treewide PR swapping $cargoDepsCopy/foo-* to $cargoDepsCopy/**/foo-*.

17:09:43
@k900:0upti.meK900 IMO <registry name>/<name>-<version> 17:09:51
@k900:0upti.meK900And then fix those packages on a case by case basis17:10:07
@tomasajt:matrix.orgToma also, just realized: * is better than **, since we know the crates will be one layer deep like this. 17:18:26
29 Jan 2025
@kira:jakira.spaceKira joined the room.00:19:22
@angelos_:matrix.organstylianHi, I am trying to build a custom rust package. In my package build I want to use the oxalica rust-overlay because I need to specify the rust version manually. my project structure is like this: /flake.nix (I am using flake-parts) /pkgs/defualt.nix /pkgs/custom-rust-project.nix Is there a way to use oxalica in my custom-rust-project, as input? if yes how? 16:46:03
@angelos_:matrix.organstylianI have managed to get the rust version I need, I will wait a bit before I share my next error :) 17:24:02
@angelos_:matrix.organstylianRedacted or Malformed Event21:34:50
30 Jan 2025
@hive:the-apothecary.club👉@crystallinefire:chat.solarpunk.moe changed their profile picture.01:30:30
@angelos_:matrix.organstylian I am trying to add nix flake in my project. one of my projects is a library. Can I have a nix build .#my-lib for it? If not, how should I handle it? 08:34:54
@angelos_:matrix.organstylianin general, can I get the package version, from Cargo.toml?09:48:19
@angelos_:matrix.organstylian* in general, can I get the package version, from Cargo.toml? (not related to the previews question)09:48:43
@qyliss:fairydust.spaceAlyssa Ross

Does anybody actually use custom rust.platform? It doesn't look like the custom sysroot ever gets its Cargo hash bumped

10:12:55

Show newer messages


Back to Room ListRoom Version: 6