tea doesn't understand ssh URL as displayed by Gitea #431
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#431
Loading…
Reference in New Issue
Block a user
No description provided.
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?
I have a personal Gitea instance installed on a Raspberry Pi at home as a docker container which I am using to manage my own Git repositories.
To avoid a conflict with the SSH daemon running on the host, I assigned Gitea's built-in sshd a non-default port (2222) both on docker and in the Gitea configuration. Because the usual syntax (
git@gitea.jotoho.de:jotoho/somerepo.git
) would cause git to connect with the wrong daemon, Gitea correctly displays the SSH URL asssh://git@gitea.jotoho.de:2222/jotoho/somerepo.git
.This works in Git but after upgrading from tea
0.7.1
to0.8.0
, I noticed that tea now fails to correctly determine the location of the repository from the origin remote. Usinggitea.jotoho.de:jotoho/somerepo.git
as the remote URL by configuring gitea.jotoho.de's user and port in the SSH config works as expected but this requires an additional step (making the config entry) and results in a situation where the URL dispensed by Gitea is incompatible with tea.Because of this I would request that support for
ssh://
-URLs be (re-)added.If it would help in making a patch for this, I am willing to provide a temporary account on the instance for debugging/testing purposes and test the PR myself. Unfortunately, I am not familiar with the Go programming language so I can't solve the problem myself.
This will be a regression from #391, which we forgot to mark as breaking :(
Interesting that this worked for you before 0.8.0, as the report in #380 was about exactly this case not working ?
What do you have configured in
SSHHost
in your tea config? (check withtea logins edit
).You can probably fix this by just changing this value to
gitea.jotoho.de:2222
. If not, I'll have to look deeper into thisHey @noerw,
the only changes made between the Gitea URL working and it deciding to break were:
0.8.0
(after informing the archlinux maintainer that the package was outdated and waiting for him to publish the new version to the repo)1.15.3
to1.15.4
(current)I had determined that an issue with the instance upgrade was (extremely) unlikely given the specifics of this problem, so I filed this issue here instead of the Gitea repo.
Changing the ssh host from
gitea.jotoho.de
togitea.jotoho.de:2222
inside the tea config makes the URL given by Gitea work.(It also breaks the trick with the ssh config - presumably since it doesn't recognize the
gitea.jotoho.de
short-hand asgitea.jotoho.de:2222
but this is good enough for me.)The change I made to my tea config:
The old ssh config entry I keep talking about (
~/.ssh/config
):I had chosen
gitea.jotoho.de
as the name for this host in the configuration (in contrast to something even shorter likegitea
) because that used to make both git and tea<0.8.0
happy while still being less typing for me.