Missing "pull mirror" button #2383

Open
opened 2026-02-17 11:41:44 +01:00 by bzt · 4 comments

Comment

First, thank you for your work, I like codeberg very much!

I have one issue though, there's no way to pull from a mirror. Automatic pull mirrors are turned off, and I totally understand that part, but would it be possible to add a "Manually pull from mirror" button on the "Settings" page perhaps? Strictly a manual button. Without the only workaround I know is to delete the repository and then migrate again. I guess this isn't ideal for your servers either, it wastes your precious resources.

ATM, I'm having trouble migrating from gitlab, I get the error Error 1205 (HY000): Lock wait timeout exceeded; try restarting transaction, but no matter if I restart after a while, I keep getting this error. Having a manual pull button would save me from re-migrating things and would be really really appreciated.

Thanks,
bzt

### Comment First, thank you for your work, I like codeberg very much! I have one issue though, there's no way to pull from a mirror. Automatic pull mirrors are turned off, and I totally understand that part, but would it be possible to add a "Manually pull from mirror" button on the "Settings" page perhaps? Strictly a manual button. Without the only workaround I know is to delete the repository and then migrate again. I guess this isn't ideal for your servers either, it wastes your precious resources. ATM, I'm having trouble migrating from gitlab, I get the error `Error 1205 (HY000): Lock wait timeout exceeded; try restarting transaction`, but no matter if I restart after a while, I keep getting this error. Having a manual pull button would save me from re-migrating things and would be really really appreciated. Thanks, bzt
Member

You mean something like the sync button for forks?
Screenshot_20260217-123426_1
Sounds like an interesting idea 🤔

You mean something like the sync button for forks? ![Screenshot_20260217-123426_1](/attachments/f6d86bb6-aa83-4bbb-b685-9269ef3ce062) Sounds like an interesting idea 🤔
Member

Workaround

@bzt wrote in #2383 (comment):

Without the only workaround I know is to delete the repository and then migrate again.

The safest workaround would be to pull the GIT references locally from Gitlab and push them from Codeberg.

Initial set-up:

git clone GITLAB_URL project
cd project
git remote add codeberg CODEBERG_URL

Manual update:

cd project
git pull origin
git push --force codeberg

Migration issue

@bzt wrote in #2383 (comment):

ATM, I'm having trouble migrating from gitlab, I get the error Error 1205 (HY000): Lock wait timeout exceeded; try restarting transaction, but no matter if I restart after a while, I keep getting this error.

Do you run the migration with token? Issues, releases, etc. disabled?

### Workaround @bzt wrote in https://codeberg.org/Codeberg/Community/issues/2383#issue-3507464: > Without the only workaround I know is to delete the repository and then migrate again. The safest workaround would be to pull the GIT references locally from Gitlab and push them from Codeberg. #### Initial set-up: ```sh git clone GITLAB_URL project cd project git remote add codeberg CODEBERG_URL ``` #### Manual update: ```sh cd project git pull origin git push --force codeberg ``` ### Migration issue @bzt wrote in https://codeberg.org/Codeberg/Community/issues/2383#issue-3507464: > ATM, I'm having trouble migrating from gitlab, I get the error `Error 1205 (HY000): Lock wait timeout exceeded; try restarting transaction`, but no matter if I restart after a while, I keep getting this error. Do you run the migration with token? Issues, releases, etc. disabled?
Author

You mean something like the sync button for forks?

Yes, exactly. Something like:

> You mean something like the sync button for forks? Yes, exactly. Something like:
Author

You mean something like the sync button for forks?

Yes, exactly. Something like:

codeberg_pull_button

The safest workaround would be to pull the GIT references locally

Thanks, but this involves double network traffic and double local storage space which I'd prefer to avoid. It would be better if codeberg could pull the changes from the mirror directly.

Do you run the migration with token? Issues, releases, etc. disabled?

No token, no issues, no releases, just the code repo. It finally worked, btw, the repo in question was this.

> You mean something like the sync button for forks? Yes, exactly. Something like: ![codeberg_pull_button](/attachments/9dcf4256-03e3-4495-a635-8e915f6c312f) > The safest workaround would be to pull the GIT references locally Thanks, but this involves double network traffic and double local storage space which I'd prefer to avoid. It would be better if codeberg could pull the changes from the mirror directly. > Do you run the migration with token? Issues, releases, etc. disabled? No token, no issues, no releases, just the code repo. It finally worked, btw, the repo in question was [this](https://codeberg.org/bzt/meg4).
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2383
No description provided.