Skip to content
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

Drop build info from julia version stored in manifest #2995

Merged

Conversation

IanButterworth
Copy link
Sponsor Member

Having the full build info was proving too noisy for checked-in manifests on master

@DilumAluthge
Copy link
Member

See e.g. JuliaRegistries/General#39745 and JuliaRegistries/General#39836 for the motivation.

@@ -302,7 +305,7 @@ function resolve_versions!(env::EnvCache, registries::Vector{Registry.RegistryIn
@warn "julia version requirement for project not satisfied" _module=nothing _file=nothing
end
else
env.manifest.julia_version = VERSION
env.manifest.julia_version = dropbuild(VERSION)
Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@staticfloat I think the test failures mean that the branch above this is being used in regular pkg usage (where julia_version isn't supplied in the context) which IIUC shouldn't be happening.
Otherwise, I can't find anywhere else that manifest.julia_version is set.

Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you print out the current stack trace in the above branch and run the tests again?

@IanButterworth IanButterworth added the backport 1.7 Change should be backported to release-1.7 label Feb 18, 2022
@IanButterworth IanButterworth merged commit 487fdd1 into JuliaLang:master Feb 18, 2022
@IanButterworth IanButterworth deleted the ib/manifest_version_dropbuild branch February 18, 2022 22:29
@IanButterworth IanButterworth added backport 1.6 Change should be backported to release-1.6 backport 1.8 Change should be backported to release-1.8 labels Feb 18, 2022
fredrikekre pushed a commit that referenced this pull request Mar 18, 2022
fredrikekre pushed a commit that referenced this pull request Mar 18, 2022
fredrikekre pushed a commit that referenced this pull request Mar 18, 2022
@fredrikekre fredrikekre removed the backport 1.6 Change should be backported to release-1.6 label Mar 18, 2022
KristofferC pushed a commit that referenced this pull request May 24, 2022
@KristofferC KristofferC mentioned this pull request May 24, 2022
11 tasks
@KristofferC KristofferC removed the backport 1.8 Change should be backported to release-1.8 label May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 1.7 Change should be backported to release-1.7
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants