{tools}[GCCcore/14.2.0] uv v0.7.13 #23143
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated software
|
Contributor
|
Why/How does this fail? I made easybuilders/easybuild-easyblocks#3482 for exactly this use case in my previous PRs of uv. Maybe this is another side of the issue but I'd expect it works.
This is what we cannot do and the reason by this 2nd folder was introduced: Cargo doesn't like workspaces/multi-crates in a vendor folder. We would need to split them up. But using this git-folder approach worked before and is much easier. |
Contributor
Author
|
It fails with Looking at what we have, there is only a single .cargo-checksum.json at all, and it's inside the there also needs to be something for itself, which is also a crate: Comparing to what though maybe there are multiple valid ways to get it to work. Currently, we are at least one |
Contributor
|
Test report by @Flamefire |
Contributor
|
I see, previously we didn't had workspaces with a top-level package. I added support for that to my refactoring PR easybuilders/easybuild-easyblocks#3665 where it was (semi-)easy to support. With that this case works (see above report) |
Collaborator
|
Test report by @Thyre |
Member
|
@Micket Can we un-draft this? |
…asyconfigs into 20250619001459_new_pr_uv0713
Member
|
@boegelbot please test @ jsc-zen3 |
Collaborator
|
@boegel: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3430627549 processed Message to humans: this is just bookkeeping information for me, |
Collaborator
|
Test report by @boegelbot |
boegel
requested changes
Oct 22, 2025
Member
|
Test report by @boegel edit: please ignore, rebuild of Rust was happening (in context of #24331)... |
Member
|
Test report by @boegel |
Member
|
Going in, thanks @Micket! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(created using
eb --new-pr)Draft because it currently doesn't work.
I'm hitting a problem with the vendored git crates.
It's specifically
pubgrubhttps://github.com/astral-sh/pubgrub which also containsversion-ranges.Cargo easyblock is currently generating the following config.toml:
but in this scenario, the git top-level directory,
pubgrub, itself is also a crate.So, we really need to (also) point to
/dev/shm/uv/0.7.13/GCCcore-14.2.0/easybuild_vendor_git/annoyingly enough.Comparing with cargos own vendoring strategy, it puts
version-rangesandpubgrubinto thevendordirectory directly.I'd like @Flamefire opinion on this.
Depends on: