Gitea fails with non-release git version number (2.28.0.618.gf4bc123cb7) #5951

New Issue

GiteaMirror · 2025-11-02T06:41:06-06:00

GiteaMirror commented

2025-11-02 06:41:06 -06:00

Originally created by @wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf on GitHub (Sep 5, 2020).

Originally assigned to: @6543 on GitHub.

Gitea version (or commit ref): 1.13.0+dev-545-g913ac9cac
Git version: 2.28.0.618.gf4bc123cb7
Operating system: Arch Linux || Fedora 33 (beta)
Database:
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Not relevant
Log gist:

~/utils/gitea on branch master via ⬢ v14.7.0 via 🐹 v1.15 on 🐳 v19.03.11 took 3m 52s
➜  ./gitea
2020/09/05 20:24:58 cmd/web.go:108:runWeb() [I] Starting Gitea on PID: 1435904
2020/09/05 20:24:58 ...s/setting/setting.go:540:NewContext() [W] Custom config '.../gitea/custom/conf/app.ini' not found, ignore this if you're running first time
2020/09/05 20:24:58 ...dules/setting/git.go:68:newGit() [F] Failed to initialize Git settings%!(EXTRA *log.ColoredValue=Git version missing: Malformed version: 2.28.0.618.gf4bc123cb7)

Description

Recently there has been a change in checking of git version used introduced by bc11caff94896c8c3f9a5c970a77470ed9beb83a.
It causes issues for non-release git builds with versions such as 2.28.0.618.gf4bc123cb7 and makes Gitea fail to run (start).
Build process yields no errors at all, though.

Originally created by @wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf on GitHub (Sep 5, 2020). Originally assigned to: @6543 on GitHub. - Gitea version (or commit ref): [`1.13.0+dev-545-g913ac9cac`](https://github.com/go-gitea/gitea/commit/913ac9cacda864b6f0bcb6225c499bdbd8e9f90d) - Git version: `2.28.0.618.gf4bc123cb7` - Operating system: `Arch Linux` || `Fedora 33 (beta)` - Database: - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [X] Not relevant - Log gist: ```log ~/utils/gitea on branch master via ⬢ v14.7.0 via 🐹 v1.15 on 🐳 v19.03.11 took 3m 52s ➜ ./gitea 2020/09/05 20:24:58 cmd/web.go:108:runWeb() [I] Starting Gitea on PID: 1435904 2020/09/05 20:24:58 ...s/setting/setting.go:540:NewContext() [W] Custom config '.../gitea/custom/conf/app.ini' not found, ignore this if you're running first time 2020/09/05 20:24:58 ...dules/setting/git.go:68:newGit() [F] Failed to initialize Git settings%!(EXTRA *log.ColoredValue=Git version missing: Malformed version: 2.28.0.618.gf4bc123cb7) ``` ## Description Recently there has been a change in checking of `git` version used introduced by [bc11caff94896c8c3f9a5c970a77470ed9beb83a](https://github.com/go-gitea/gitea/commit/bc11caff94896c8c3f9a5c970a77470ed9beb83a). It causes issues for non-release `git` builds with versions such as `2.28.0.618.gf4bc123cb7` and makes Gitea fail to run (start). Build process yields no errors at all, though.

GiteaMirror added the type/bug label 2025-11-02 06:41:06 -06:00

GiteaMirror closed this issue

2025-11-02 06:41:07 -06:00

GiteaMirror commented

2025-11-02 06:41:07 -06:00

@6543 commented on GitHub (Sep 5, 2020):

think this is caused by #12719

@6543 commented on GitHub (Sep 5, 2020): think this is caused by #12719

GiteaMirror commented

2025-11-02 06:41:07 -06:00

@6543 commented on GitHub (Sep 5, 2020):

upstream issue https://github.com/hashicorp/go-version/issues/76

@6543 commented on GitHub (Sep 5, 2020): upstream issue https://github.com/hashicorp/go-version/issues/76

GiteaMirror commented

2025-11-02 06:41:08 -06:00

@wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf commented on GitHub (Sep 5, 2020):

think this is caused by #12719

yep, had to roll back my Gitea instance for the moment.

upstream issue hashicorp/go-version#76

:(

@wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf commented on GitHub (Sep 5, 2020): > think this is caused by #12719 yep, had to roll back my Gitea instance for the moment. > upstream issue hashicorp/go-version#76 :(

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5951