-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build/cmd/release: go1.13beta1 contains read-only files #33537
Labels
Milestone
Comments
Interesting. This issue only seems to affect
|
Change https://golang.org/cl/189537 mentions this issue: |
codebien
pushed a commit
to codebien/build
that referenced
this issue
Nov 13, 2019
Binary releases need to build Go and include binaries such as bin/go, bin/gofmt, and others. Previously, this was accomplished by running all.bash script for some GOOS/GOARCH pairs, and make.bash for others where it wasn't viable to run tests as part of the release process. This change makes the release process more consistent by always packaging the release archive file after running make.bash. We still run all.bash in situations where it was previously run, but we do so after the release file has already been created. This avoids the risk of any changes to GOROOT that may occur as part of all.bash (including changing file permissions to be read-only) being included in the final release file. Add a step to check that files in the buildlet's $WORKDIR/go and $WORKDIR/go/bin directories have expected permissions before creating the release file. Fixes golang/go#33537 Updates golang/go#30316 Change-Id: I7d40716dba656a8aca711377f2995df4880166c5 Reviewed-on: https://go-review.googlesource.com/c/build/+/189537 Reviewed-by: Andrew Bonventre <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Compare the following:
Notice how the
u+w
bit is missing from the later archive? This makes extracting in a way that preserves the modes as specified in the archive more challenging since writing theAUTHORS
file will fail since the parent directory is marked as read-only.\cc @dmitshur
The text was updated successfully, but these errors were encountered: