github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[Update] gitea to the latest gitea version: 1.9.0+rc2, which makes it impossible to push #3660

New Issue
Closed
opened 2025-11-02 05:20:53 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 05:20:53 -06:00
Owner
Copy Link

Originally created by @zhanghenxiao on GitHub (Jul 24, 2019).

image

Originally created by @zhanghenxiao on GitHub (Jul 24, 2019). ![image](https://user-images.githubusercontent.com/24770824/61779262-f4ca3080-ae32-11e9-8c27-c7d49a914e67.png)
GiteaMirror added the issue/not-a-bug label 2025-11-02 05:20:53 -06:00
GiteaMirror commented 2025-11-02 05:20:54 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 24, 2019):

There is no code in 1.9 that can create that message. That's from the 1.8 branch.

You're not running 1.9.

@zeripath commented on GitHub (Jul 24, 2019): There is no code in 1.9 that can create that message. That's from the 1.8 branch. You're not running 1.9.
GiteaMirror commented 2025-11-02 05:20:54 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 24, 2019):

If you're definitely running 1.9 as the http server then presumably you have both the 1.8 and 1.9 binaries installed and you've changed the path to gitea for 1.9. In which case you will need to run the admin task to update/recreate the authorized_keys file.

@zeripath commented on GitHub (Jul 24, 2019): If you're definitely running 1.9 as the http server then presumably you have both the 1.8 and 1.9 binaries installed and you've changed the path to gitea for 1.9. In which case you will need to run the admin task to update/recreate the authorized_keys file.
GiteaMirror commented 2025-11-02 05:20:55 -06:00
Author
Owner
Copy Link

@jwegner commented on GitHub (Jul 27, 2019):

@zeripath
I experienced similar problems, push, fetch didn't work. Your advice to regenerate keys worked for me. I had to regenerate the hooks too, after that everything worked as expected. Thank you :)

@jwegner commented on GitHub (Jul 27, 2019): @zeripath I experienced similar problems, push, fetch didn't work. Your advice to regenerate keys worked for me. I had to regenerate the hooks too, after that everything worked as expected. Thank you :)
GiteaMirror commented 2025-11-02 05:20:55 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 27, 2019):

No problems. I'll close this as invalid - as it's not a bug with Gitea but your install.

@zeripath commented on GitHub (Jul 27, 2019): No problems. I'll close this as invalid - as it's not a bug with Gitea but your install.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3660
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?