Hostea
/
website
3
2
Fork 2
Code Issues 5 Pull Requests Projects Releases Wiki Activity

git >=2.36 is both in 1.16.9 and 1.17
ci/woodpecker/push/woodpecker Pipeline was successful Details

pull/36/head
Loïc Dachary 2022-06-03 14:02:00 +02:00
parent 0e9a9c0c6a
commit 8f1791eb74
Signed by: dachary
GPG Key ID: 992D23B392F9E4F2
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md
View File

@ -22,11 +22,11 @@ This started to show in the past few weeks to [users running the Gitea binary on
### Workarounds
* If using [Gitea docker images](https://hub.docker.com/r/gitea/gitea):
* do not upgrade to 1.16.6, 1.16.7 or 1.16.8, or
* downgrade from 1.16.6, 1.16.7 or 1.16.8 to 1.16.5 (do **not** downgrade from 1.17.x, it may corrupt your the Gitea database)
* upgrade to [Gitea >=1.16.9](https://github.com/go-gitea/gitea/pull/19876) or 1.17, both have git >=2.36
* `git config --global --replace-all safe.directory '*'`
* If the Gitea binary was installed independently of git, upgrade git to a version that is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory) and disable the security check entirely with:
* impersonate the [user dedicated to Gitea](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) (usually git)
* `git config --global --replace-all safe.directory '*'`
* impersonate the [user dedicated to Gitea](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) (usually git)
* `git config --global --replace-all safe.directory '*'`
### Bug fix