Georges Varouchas

workaround : * if running `git status` shows that `go.mod` or `go.sum` is modified, run `git checkout HEAD -- go.mod go.sum` * if you just want to compile `mysqld_exporter`, run...

workaround : * if running `git status` shows that `go.mod` or `go.sum` is modified, run `git checkout HEAD -- go.mod go.sum` * if you just want to compile `mysqld_exporter`, run...

Some other issues show users confused by this message : #534 - build failed on FreeBSD part of his issue is to have run `go mod tidy` when no version...

@BurntSushi : is there some way to group the issues related to the `ignore` crate ? or perhaps an issue, which describes the various points that need to be clarified...

This issue was fixed in #1125 It wasn't part of version 1.0 or 1.1, it was merged in 1.1.1-rc. You would have to run version 1.1.1-rc or later.

#1396 currently allows to fix the first error, another error is triggered at a later step : ``` ERROR: 2022/12/07 22:54:15.269275 CompressAndEncrypt: compress: archive/tar: invalid tar header ``` ### Please...

running `docker-compose build golang ubuntu s3 pg pg_build_docker_prefix` from my command line triggers the very same error

As a temporary patch on my system, I disabled the apparmor rules for /usr/sbin/runc Following the documentation to disable one single apparmor profile (link on help.ubuntu.com: [Disable one profile](https://help.ubuntu.com/community/AppArmor#Disable_one_profile) )...