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

Cannot update existing repo after upgrade to v1.1 #1224

Closed
2 of 7 tasks
tullo opened this issue Mar 12, 2017 · 9 comments
Closed
2 of 7 tasks

Cannot update existing repo after upgrade to v1.1 #1224

tullo opened this issue Mar 12, 2017 · 9 comments
Labels
Milestone

Comments

@tullo
Copy link

tullo commented Mar 12, 2017

Just updated to 1.1 and tried to update a wiki page through the browser for a quick test. That failed!

Then I cloned the wiki repo to my laptop, updated the wiki page. Pushing the change to server failed! Se error log below.

The Release Notes say: "The SSH keys can potentially break, make sure to regenerate the authorized keys" so I run the command through the Admin Panel.
Also removed my public ssh key from the user and added it again.

What else can I do? I am still not able to update the existing wiki / repo

OTOH creating a NEW repo and updating that works!


git push -v
Pushing to ssh://[email protected]:10022/anda/devtools.wiki.git
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 307 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: No help topic for 'update'
remote: error: hook declined to update refs/heads/master
To ssh://[email protected]:10022/anda/devtools.wiki.git
! [remote rejected] master -> master (hook declined)


  • Gitea version (or commit ref): docker pull gitea/gitea:1.1
  • Git version: 2.8.3
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

...

Screenshots

If this issue involves the Web Interface, please include a screenshot

@strk
Copy link
Member

strk commented Mar 12, 2017 via email

@lunny lunny added the type/bug label Mar 12, 2017
@lunny lunny added this to the 1.2.0 milestone Mar 12, 2017
@lunny
Copy link
Member

lunny commented Mar 12, 2017

I think I know what's happened. I will send a PR to fix this.

@lunny
Copy link
Member

lunny commented Mar 12, 2017

@tullo, you can resolve this on your Admin Panel, execute Resync pre-receive, update and post-receive hooks of all repositories. will resolve your problem.

@tullo
Copy link
Author

tullo commented Mar 12, 2017

@lunny tried that, but did not help unfortunately

@mmozeiko
Copy link

mmozeiko commented Mar 13, 2017

I see same error happening for my wiki pages after upgrade to 1.1.0. But I can push to repositories. Only editing wiki pages makes server show http 500 error page.

Log shows:

2017/03/13 08:09:35 [...routers/repo/wiki.go:487 EditWikiPost()] [E] EditWikiPage: Push: exit status 1 - remote: No help topic for 'update'
remote: error: hook declined to update refs/heads/master
To /var/lib/gitea/git/USER/REPO.wiki.git
 ! [remote rejected] master -> master (hook declined)
error: failed to push some refs to '/var/lib/gitea/git/USER/REPO.wiki.git'

@lunny
Copy link
Member

lunny commented Mar 13, 2017

@mmozeiko are you sure Resync pre-receive, update and post-receive hooks of all repositories. can not resolve this?

@mmozeiko
Copy link

Yes, tried running running resync hooks, nothing changed.

Now I've noticed that hooks/update file is different for newly created repository wiki.
I copied this newly created update file to all the old repositories (only wiki page repos) and now editing works for me!

@lunny
Copy link
Member

lunny commented Mar 13, 2017

@mmozeiko Yes. manually do that will let you work. But it's strange why the Resync pre-receive, update and post-receive hooks of all repositories. didn't work.

@lunny
Copy link
Member

lunny commented Apr 28, 2017

@tullo #1227 should fix this issue

@lunny lunny closed this as completed Apr 28, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
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

4 participants