Skip to content

[workspace] Issue updating sub-project without an existing Manifest.toml #4222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nhz2 opened this issue Apr 22, 2025 · 0 comments · May be fixed by #4229
Open

[workspace] Issue updating sub-project without an existing Manifest.toml #4222

nhz2 opened this issue Apr 22, 2025 · 0 comments · May be fixed by #4229
Assignees

Comments

@nhz2
Copy link
Contributor

nhz2 commented Apr 22, 2025

I am using the new workspace feature in the https://github.com/JuliaIO/ChunkCodecs.jl monorepo.

If I clone the repo, which has no Manifest.toml, and update a sub-project, the dependencies are from the registry and not the local versions.

ChunkCodecCore and LibZlib are both sub-projects of the top workspace, and LibZlib depends on ChunkCodecCore.

For example, after:

julia --project=LibZlib -e 'import Pkg; Pkg.update()'

The deps.ChunkCodecCore section in Manifest.toml contains:

[[deps.ChunkCodecCore]]
git-tree-sha1 = "83cc01ac207dde8e10d08c3b1d8bd994c5c0c25e"
uuid = "0b6fb165-00bc-4d37-ab8b-79f91016dbe1"
version = "0.4.2"

If instead I run:

julia --project=. -e 'import Pkg; Pkg.update()'

I get the expected:

[[deps.ChunkCodecCore]]
path = "ChunkCodecCore"
uuid = "0b6fb165-00bc-4d37-ab8b-79f91016dbe1"
version = "0.4.2"
julia> versioninfo()
Julia Version 1.13.0-DEV.427
Commit ff0a9313de7 (2025-04-22 14:02 UTC)
Build Info:
  Official https://julialang.org release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 16 × Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
  WORD_SIZE: 64
  LLVM: libLLVM-19.1.7 (ORCJIT, skylake)
  GC: Built with stock GC
Threads: 1 default, 1 interactive, 1 GC (on 16 virtual cores)
@nhz2 nhz2 added the workspace label Apr 22, 2025
@KristofferC KristofferC self-assigned this May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants