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
cmd/go: flag modcacherw does not take effect in the target package #64282
Comments
@marjus45, I'm not able to reproduce the behavior you report:
Did you run any other commands before or after the |
Huh. Apparently it has something to do with running as
|
Bisecting now. |
|
@gopherbot, please backport to Go 1.21. This was a regression in Go 1.21 and has no clear workaround. |
Backport issue(s) opened: #64497 (for 1.21). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/546635 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?I tested this on a clean Debian container.
go env
OutputWhat did you do?
modcacherw
flag withgo install
:go-containerregistry@v0.16.1
has read only permissions while their dependencies (go-cmp
) has read-write permissions, as expected.What did you expect to see?
I expected to see the directory
go-containerregistry@v0.16.1
to have read-write permissions, since I have set the flagmodcacherw
.What did you see instead?
Instead
go-containerregistry@v0.16.1
has read only permissions.I thinks this is a regression, since up to
v1.20
I confirmed that it worked as expected.The text was updated successfully, but these errors were encountered: