Cachi2 prefetching is making changes on a Go project's source #707
Comments
arewm
changed the title
|
Yes, this is known (or at least was common with projects requiring <=1.20 and having been processed with >=1.21). Recently we deprecated the |
eskultety
added
bug
eskultety
changed the title
This was referenced Oct 25, 2024
eskultety
added a commit
to eskultety/cachi2
that referenced
this issue
Oct 25, 2024
gomod has been the only backend that prevented us from using a
temporary working copy of the input repository with all package manager
backends. The reason for that was the existence of the:
* '--gomod-vendor'
* '--gomod-vendor-check', and
* '--force-gomod-tidy'
CLI flags that allowed the source repository to be dirtied by us. With
all of those flags now deprecated (treating them as NOOP) we can use a
temporary repository copy with gomod as well.
Resolves: containerbuildsystem#707
Signed-off-by: Erik Skultety <[email protected]>
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running Cach2 on a source repo with the gomod package manager, changes are made to the
go.modfile. This is presumably from runninggo mod tidy. It is also changing the sources when fetching the origin information for the git repository.Cachi2 should not modify the sources that it is run on. Instead, it should operate on a temporary copy of the repository.
The text was updated successfully, but these errors were encountered: