Skip to content

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

@wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf

Description

  • 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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions