Skip to content

rust: bump uuid to 1.23 and switch to using a workspace#568

Draft
davide125 wants to merge 4 commits into
AsahiLinux:mainfrom
davide125:uuid
Draft

rust: bump uuid to 1.23 and switch to using a workspace#568
davide125 wants to merge 4 commits into
AsahiLinux:mainfrom
davide125:uuid

Conversation

@davide125
Copy link
Copy Markdown
Member

Bump to what's shipped in Fedora

Signed-off-by: Davide Cavalca <dcavalca@fedoraproject.org>
davide125 added 2 commits May 5, 2026 13:58
Apparently we're supposed to use a workspace for path-based dependencies
that are in-tree, otherwise cargo can get confused.

Signed-off-by: Davide Cavalca <dcavalca@fedoraproject.org>
Signed-off-by: Davide Cavalca <dcavalca@fedoraproject.org>
@davide125 davide125 requested a review from svenpeter42 as a code owner May 5, 2026 21:00
@davide125 davide125 marked this pull request as draft May 5, 2026 21:00
@davide125 davide125 changed the title rust: bump uuid to 1.23 rust: bump uuid to 1.23 and switch to using a workspace May 5, 2026
Signed-off-by: Davide Cavalca <dcavalca@fedoraproject.org>
@flokli
Copy link
Copy Markdown
Contributor

flokli commented May 6, 2026

I can confirm this fixes the build for me when using nixpkgs tooling, which currently fails like this on main:

error: failed to get `uuid` as a dependency of package `rust v0.1.0 (/build/source/rust)`

Caused by:
  failed to load source for dependency `uuid`

Caused by:
  Unable to update registry `crates-io`

Caused by:
  failed to update replaced source registry `crates-io`

Caused by:
  failed to load checksum `.cargo-checksum.json` of rust v0.1.0

Caused by:
  failed to read `/build/source/rust/.cargo-checksum.json`

Caused by:
  No such file or directory (os error 2)
make: *** [Makefile:216: build/librust.a] Error 101
make: *** Waiting for unfinished jobs....

nixpkgs commit: flokli/nixpkgs@89b9af1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants