-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Issue Attachments do not migrate on Gitea to Gitea migration #17863
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
Comments
@lunny Hey, thanks for classifying the issue. Is there any comment on this? We are still migrating from an "old" Gitea server to a "new" one and missing all the attachements. |
This is a missed feature when migrating from Gitea to Gitea. |
Any feedback on this issue to be implemented going forward? |
There is a workaround, you could just copy all data from old server to new. The migration is not an accurate 1-to-1 copy, it might lose something. |
#14601 is the first step in this direction ... |
Do attachments migrate from GitLab to Gitea? |
they should but that's unrelated question ... I would suggest to use the chat for such |
I have done my migration from GitLab to Gitea (1.15~1.16), the attachments were not migrated. There could be a manual workaround method: copy the attachments from GitLab to a directory, and serve them correctly by a HTTP server like nginx. |
Gitea Version
1.15.6 built with GNU Make 4.1, go1.16.9
Git Version
2.33.1.windows.1
Operating System
Windows Server 2022
How are you running Gitea?
Windows Service
Database
PostgreSQL
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Description
We have the issue of attachments not being migrated from 1 Gitea repository (1.15.6) to Gitea (1.15.6).
Looking into the go code, it appears there is no such code implemented to carry attachments over. That should be verified.
Screenshots
Failed migration on try.gitea.io:

Images as they appear after the migration:

The text was updated successfully, but these errors were encountered: