[Bug] Cant Force Push LFS-enabled to NON-LFS repo #4740

New Issue

GiteaMirror · 2025-11-02T06:01:21-06:00

GiteaMirror commented

2025-11-02 06:01:21 -06:00

Originally created by @6543 on GitHub (Jan 28, 2020).

when converting a repo to use LFS i have to create a new one. i cant reupload to the old repo ...

see: https://discourse.gitea.io/t/convert-existing-repository-in-gitea-to-one-using-git-lfs/1848

Originally created by @6543 on GitHub (Jan 28, 2020). when converting a repo to use LFS i have to create a new one. i cant reupload to the old repo ... see: https://discourse.gitea.io/t/convert-existing-repository-in-gitea-to-one-using-git-lfs/1848

GiteaMirror closed this issue

2025-11-02 06:01:22 -06:00

GiteaMirror commented

2025-11-02 06:01:23 -06:00

@6543 commented on GitHub (Jan 28, 2020):

git push --force

produce:

Locking support detected on remote "origin". Consider enabling it with:
  $ git config lfs.https://code.net/user/repo.git/info/lfs.locksverify true
ref master:: Error in git rev-list --stdin --objects --not --remotes=origin --: exit status 128 fatal: bad object 5cef6f90554c99060e8de94d423b4775f92120f8

error: failed to push some refs to 'ssh://git@code.net:22/user/repo.git'

push to new repos works just fine

@6543 commented on GitHub (Jan 28, 2020): git push --force produce: ``` Locking support detected on remote "origin". Consider enabling it with: $ git config lfs.https://code.net/user/repo.git/info/lfs.locksverify true ref master:: Error in git rev-list --stdin --objects --not --remotes=origin --: exit status 128 fatal: bad object 5cef6f90554c99060e8de94d423b4775f92120f8 error: failed to push some refs to 'ssh://git@code.net:22/user/repo.git' ``` push to new repos works just fine

GiteaMirror commented

2025-11-02 06:01:23 -06:00

@6543 commented on GitHub (Jan 28, 2020):

2nd thought: since the init commit is different this may cause the problem

@6543 commented on GitHub (Jan 28, 2020): 2nd thought: since the init commit is different this may cause the problem

GiteaMirror commented

2025-11-02 06:01:23 -06:00

@stale[bot] commented on GitHub (Mar 28, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 28, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:01:23 -06:00

@6543 commented on GitHub (Mar 31, 2020):

need more time to infestiage - will look at this later ...

@6543 commented on GitHub (Mar 31, 2020): need more time to infestiage - will look at this later ...

GiteaMirror commented

2025-11-02 06:01:24 -06:00

@stale[bot] commented on GitHub (May 30, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 30, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:01:24 -06:00

@stale[bot] commented on GitHub (Jul 30, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 30, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:01:24 -06:00

@zeripath commented on GitHub (Jul 30, 2020):

@6543 sorry I missed this. I'm not quite sure from what you've written how to reproduce this. Did you ever get to the bottom of the problem? Is the failure definitely coming from Gitea?

@zeripath commented on GitHub (Jul 30, 2020): @6543 sorry I missed this. I'm not quite sure from what you've written how to reproduce this. Did you ever get to the bottom of the problem? Is the failure definitely coming from Gitea?

GiteaMirror commented

2025-11-02 06:01:24 -06:00

@6543 commented on GitHub (Jul 30, 2020):

No didn't had a deeper look into this jet

@6543 commented on GitHub (Jul 30, 2020): No didn't had a deeper look into this jet

GiteaMirror commented

2025-11-02 06:01:25 -06:00

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

local tested - works now with current master

@6543 commented on GitHub (Sep 18, 2020): local tested - works now with current master

GiteaMirror referenced this issue

2025-11-02 13:37:12 -06:00