Support hg:: and and bzr:: repo URLs #615

New Issue

GiteaMirror · 2025-11-02T03:30:01-06:00

GiteaMirror commented

2025-11-02 03:30:01 -06:00

Originally created by @lofidevops on GitHub (Apr 5, 2017).

Gitea version (or commit ref): 1.1.0
Git version: 2.9.3
Operating system: Ubuntu 16.10
Database (use [x]):
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Not relevant
Log gist: N/A

Steps to reproduce

Install git-remote-hg package
Confirm git clone "hg::http://selenic.com/repo/hello" works from the command line
Open Gitea
Attempt to create a repository mirror
Enter hg::http://selenic.com/repo/hello as URL

(Repeat with git-remote-bzr package and git clone "bzr::lp:ubuntu/hello" for Bazaar support)

What should happen

Create a Git mirror of the Mercurial repo
Regularly update the mirror (like any other mirror)

What happens instead

Error message: "You are not allowed to import local repositories."

Originally created by @lofidevops on GitHub (Apr 5, 2017). - Gitea version (or commit ref): 1.1.0 - Git version: 2.9.3 - Operating system: Ubuntu 16.10 - Database (use `[x]`): - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Not relevant - Log gist: N/A ## Steps to reproduce * Install `git-remote-hg` package * Confirm `git clone "hg::http://selenic.com/repo/hello"` works from the command line * Open Gitea * Attempt to create a repository mirror * Enter `hg::http://selenic.com/repo/hello` as URL (Repeat with `git-remote-bzr` package and `git clone "bzr::lp:ubuntu/hello"` for Bazaar support) ## What should happen * Create a Git mirror of the Mercurial repo * Regularly update the mirror (like any other mirror) ## What happens instead * Error message: "You are not allowed to import local repositories."

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 03:30:01 -06:00

GiteaMirror closed this issue

2025-11-02 03:30:01 -06:00

GiteaMirror commented

2025-11-02 03:30:02 -06:00

@stale[bot] commented on GitHub (Feb 14, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 14, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:30:02 -06:00

@6543 commented on GitHub (Aug 9, 2022):

I dont see this integrated in the near future and mostly you have to fix things localy ... so it's best to use existing tools to convert them localy and push the converted git

can we close this?

@6543 commented on GitHub (Aug 9, 2022): I dont see this integrated in the near future and mostly you have to fix things localy ... so it's best to use existing tools to convert them localy and push the converted git can we close this?

GiteaMirror commented

2025-11-02 03:30:02 -06:00

@lofidevops commented on GitHub (Aug 9, 2022):

I don't personally have a use-case for this anymore, so happy to close. If only I could search the whole ticket-verse for such issues ;)

@lofidevops commented on GitHub (Aug 9, 2022): I don't personally have a use-case for this anymore, so happy to close. If only I could search the whole ticket-verse for such issues ;)

GiteaMirror commented

2025-11-02 03:30:02 -06:00

@lofidevops commented on GitHub (Aug 9, 2022):

(For others that do still have a use-case, I imagine 6543's suggestion is more reliable than ad-hoc support in Gitea.)

@lofidevops commented on GitHub (Aug 9, 2022): (For others that do still have a use-case, I imagine 6543's suggestion is more reliable than ad-hoc support in Gitea.)

GiteaMirror referenced this issue

2025-11-02 11:47:46 -06:00

[PR #615] [MERGED] Better coverage in pull_test #15491

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#615