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

How can I update gitea? #3817

Closed
san127127 opened this issue Apr 19, 2018 · 4 comments
Closed

How can I update gitea? #3817

san127127 opened this issue Apr 19, 2018 · 4 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@san127127
Copy link

I updated my gitea from 1.3.2 to 1.4.0 by replacing "gitea-1.3.2-windows-4.0-386.exe" by "gitea-1.4.0-windows-4.0-386.exe".

After doing this, I can't push anything onto the server. When I try to push, I got this line on command line "remote: ./hooks/pre-receive.d/gitea: line 2: D:/Version Control/Gitea/gitea-1.3.2-windows-4.0-386.exe: No such file or directory" because those hooks contains a path to the old gitea exe.

It seems there is no migration guide for this. How can I update gitea? Am I supposed to update those hooks one by one manually?

@lafriks lafriks added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Apr 19, 2018
@lafriks
Copy link
Member

lafriks commented Apr 19, 2018

It is recommended to use more generic name like gitea.exe (just rename after download) to not have such issues.

In admin options (https://<your-domain>/admin) there is option (Resync pre-receive, update and post-receive hooks of all repositories.) to rewrite all hooks with new path:
image

@san127127
Copy link
Author

Thanks, I will try this tomorrow.
I don't think I am the only one having this problem, maybe this is worth mentioning in docs.

@lafriks
Copy link
Member

lafriks commented Apr 20, 2018

Yes we would need some help on docs, so if you can submit PR for that it would be great

@techknowlogick
Copy link
Member

@csleead I'm closing this ticket now, but feel free to re-open if needed.

@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
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

3 participants