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

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

Closed
6543 opened this issue Jan 28, 2020 · 9 comments
Closed

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

6543 opened this issue Jan 28, 2020 · 9 comments

Comments

@6543
Copy link
Member

6543 commented 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

@6543
Copy link
Member Author

6543 commented 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
Copy link
Member Author

6543 commented Jan 28, 2020

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

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Mar 28, 2020
@6543
Copy link
Member Author

6543 commented Mar 31, 2020

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

@stale stale bot removed the issue/stale label Mar 31, 2020
@stale
Copy link

stale bot commented 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 stale bot added issue/stale and removed issue/stale labels May 30, 2020
@stale
Copy link

stale bot commented 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 stale bot added issue/stale and removed issue/stale labels Jul 30, 2020
@zeripath
Copy link
Contributor

@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?

@6543
Copy link
Member Author

6543 commented Jul 30, 2020

No didn't had a deeper look into this jet

@6543 6543 closed this as completed Sep 17, 2020
@6543
Copy link
Member Author

6543 commented Sep 18, 2020

local tested - works now with current master

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants