Skip to content

adopting linux repo from existing local mirror repo causes 500 #29043

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

Closed
muhamad opened this issue Feb 4, 2024 · 6 comments
Closed

adopting linux repo from existing local mirror repo causes 500 #29043

muhamad opened this issue Feb 4, 2024 · 6 comments
Labels

Comments

@muhamad
Copy link

muhamad commented Feb 4, 2024

Description

I'm using git version 2.43.0.windows.1 and gitea 1.21.5

I do have a local bare mirror linux kernel repo from https://github.com/torvalds/linux and I get the following error

error

even when I try to clone it directly from GitHub using GitHub migration I still get the same error.

Gitea Version

1.21.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

2.43.0

Operating System

Windows 10 22H2

How are you running Gitea?

As a windows service using SQLite as my backend.

Database

SQLite

@lunny
Copy link
Member

lunny commented Feb 4, 2024

2.6.11 doesn't exist on github https://github.com/torvalds/linux/tags?after=v2.6.12-rc3

@wxiaoguang
Copy link
Contributor

Also see this: unable to PushUpdateAddTag to Repo: unable to get tag Commit: object does not exist #28843

And maybe this: slice bounds out of range in function: /modules/git.newSignatureFromCommitline #28840

@lunny
Copy link
Member

lunny commented Feb 4, 2024

Duplicate of #28843

@lunny lunny closed this as completed Feb 4, 2024
@lunny lunny marked this as a duplicate of #28843 Feb 4, 2024
@muhamad
Copy link
Author

muhamad commented Feb 4, 2024

@lunny I understand that tag 2.6.11 doesn't exist, Shouldn't gitea ignore such error and continue on migration?

@lunny
Copy link
Member

lunny commented Feb 5, 2024

@lunny I understand that tag 2.6.11 doesn't exist, Shouldn't gitea ignore such error and continue on migration?

I think we can do that in a PR. Let's follow #28843

Copy link

Automatically locked because of our CONTRIBUTING guidelines

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

No branches or pull requests

3 participants