Test Action / test (amd64, -v, true, micro, debian/2.0.6-2_bpo10+1, https://salsa.debian.org/go-team/packages/micro.git) (pull_request) Failing after 3m25s
Test Action / test (arm, -v, iproute2, import/4.18.0-1ubuntu2_ubuntu18.04.1, https://git.launchpad.net/ubuntu/+source/iproute2) (pull_request) Failing after 37s
Test Action / test (arm64, -v, netcat-openbsd, import/1.206-1ubuntu1, https://git.launchpad.net/ubuntu/+source/netcat-openbsd) (pull_request) Has been cancelled
Recent versions of git do not like to run as root in repos that are not
owned by root. This is commonly the situation when a user checks out
a git repo, then runs a docker container with the repo mounted in it.
The version un debian unstable (1:2.38.1-1) has this issue. The version
in bullseye (1:2.30.2-1) does not have this issue.
git-deborig gives this unhelpful error message:
$ git deborig HEAD
pwd doesn't look like a git repository ..
Regular git gives this more useful error message:
$ git status
fatal: detected dubious ownership in repository at '/data/home/seb/action-debian-package'
To add an exception for this directory, call:
git config --global --add safe.directory /data/home/seb/action-debian-package
This commit fixes the issue by running the recommended command inside
the container, before trying to access the git repo.
Fixes#62.
As you can build multiple binary packages from one source package, those
don't need to have the same name. You can even build only one binary
package which has a completely different name.
The saves way is to match on the package version number.
Adding the correct transformation scope flags here.
https://www.gnu.org/software/tar/manual/html_section/tar_51.html
mentions a way to fix this:
```
In addition, several transformation scope flags are supported, that control to what files transformations apply. These are:
[...]
`S'
Do not apply transformation to symbolic link targets.
```
Jan Wagner
