Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CreatePost, initRepository: git.InitRepository: exit status 129 - error: unknown option `object-format' #28927

Closed
kegri opened this issue Jan 25, 2024 · 1 comment · Fixed by #28928
Labels

Comments

@kegri
Copy link

kegri commented Jan 25, 2024

Description

Cannot create or migrate repositories. Throws error 500.

Gitea Version

1.22.0+dev-605-g071b7b2a0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/kegri/1ef7cfb5d1cbe41b0be01772a72629b5

Screenshots

image

Git Version

No response

Operating System

No response

How are you running Gitea?

I'm running gitea through docker.

Database

MySQL/MariaDB

@kegri kegri added the type/bug label Jan 25, 2024
techknowlogick pushed a commit that referenced this issue Jan 25, 2024
This should fix #28927

Technically older versions of Git would support this flag as well, but
per #28466 that's the version
where using it (object-format=sha256) left "experimental" state.

`sha1` is (currently) the default, so older clients should be unaffected
in either case.

Signed-off-by: jolheiser <john.olheiser@gmail.com>
henrygoodman pushed a commit to henrygoodman/gitea that referenced this issue Jan 31, 2024
This should fix go-gitea#28927

Technically older versions of Git would support this flag as well, but
per go-gitea#28466 that's the version
where using it (object-format=sha256) left "experimental" state.

`sha1` is (currently) the default, so older clients should be unaffected
in either case.

Signed-off-by: jolheiser <john.olheiser@gmail.com>
silverwind pushed a commit to silverwind/gitea that referenced this issue Feb 20, 2024
This should fix go-gitea#28927

Technically older versions of Git would support this flag as well, but
per go-gitea#28466 that's the version
where using it (object-format=sha256) left "experimental" state.

`sha1` is (currently) the default, so older clients should be unaffected
in either case.

Signed-off-by: jolheiser <john.olheiser@gmail.com>
Copy link

Automatically locked because of our CONTRIBUTING guidelines

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant