From 4d6f803a222c2f49c3ea6ed53366732f929dffaa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Dachary?= Date: Sun, 15 May 2022 16:39:29 +0200 Subject: [PATCH 1/2] blog: safe.directory: s/--system/--global/ --- content/blog/2022-05-15-upgrades.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/blog/2022-05-15-upgrades.md b/content/blog/2022-05-15-upgrades.md index 8f5ea73..88b5cee 100644 --- a/content/blog/2022-05-15-upgrades.md +++ b/content/blog/2022-05-15-upgrades.md @@ -26,11 +26,11 @@ This started to show in the past few weeks to [users running the Gitea binary on * downgrade from 1.16.6 or 1.16.7 to 1.16.5 (do **not** downgrade from 1.17.x, it may corrupt your the Gitea database) * 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 --system --replace-all safe.directory '*'` + * `git config --global --replace-all safe.directory '*'` ### Bug fix -The [bug fix](https://github.com/go-gitea/gitea/pull/19707) is for Gitea to ensure `git config --system --replace-all safe.directory '*'` is set on its [dedicated user](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) when it initializes. It is effective on the condition that the git CLI version is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory). +The [bug fix](https://github.com/go-gitea/gitea/pull/19707) is for Gitea to ensure `git config --global --replace-all safe.directory '*'` is set on its [dedicated user](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) when it initializes. It is effective on the condition that the git CLI version is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory). ### Bug fix rationale From ba88230385f690c737f0c0545fadfae7df4f605c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Dachary?= Date: Sun, 15 May 2022 16:47:55 +0200 Subject: [PATCH 2/2] more explicit title for the second blog post --- ...d => 2022-05-15-unsafe-repository-is-owned-by-someone-else.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename content/blog/{2022-05-15-upgrades.md => 2022-05-15-unsafe-repository-is-owned-by-someone-else.md} (100%) diff --git a/content/blog/2022-05-15-upgrades.md b/content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md similarity index 100% rename from content/blog/2022-05-15-upgrades.md rename to content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md