Migrating from https://gitlab.com/toz12/medilog failed. #677

Open
opened 4 days ago by toz · 4 comments
toz commented 4 days ago

I am trying to move my project from GitLab to Codeberg via the migration page. Unfortunately all I get back is the error message in the subject of this issue. Is there any way for me to troubleshoot whats going on?

My repo is public and I created an access token:

image

After hitting the migrate button it takes a few seconds and then this message appears:
image

Migration worked once, but I forgot to specify the migration items, so I deleted the repo here and tried tried to start all over. Can't get it to work since no matter if the additional migration items are selceted or not.

I am trying to move my project from GitLab to Codeberg via the migration page. Unfortunately all I get back is the error message in the subject of this issue. Is there any way for me to troubleshoot whats going on? My repo is public and I created an access token: ![image](/attachments/dee11dcf-21e1-4d86-a5f2-6d91f5c59062) After hitting the migrate button it takes a few seconds and then this message appears: ![image](/attachments/3c3cde92-e394-4347-bfa4-ccf3be9641e0) Migration worked once, but I forgot to specify the migration items, so I deleted the repo here and tried tried to start all over. Can't get it to work since no matter if the additional migration items are selceted or not.
Collaborator

Hmm, sometimes we have edge cases that break Gitea, e.g. release drafts and other things that are only supported by one platform, but not another. Additionally, the APIs of proprietary platforms change from time to time ...

We're about to deploy the next version of Gitea within a few days, I propose you retry then (maybe it's a bug already fixed). If the problem persists, we can then try to hunt it down.

Hmm, sometimes we have edge cases that break Gitea, e.g. release drafts and other things that are only supported by one platform, but not another. Additionally, the APIs of proprietary platforms change from time to time ... We're about to deploy the next version of Gitea within a few days, I propose you retry then (maybe it's a bug already fixed). If the problem persists, we can then try to hunt it down.
fnetX added the
bug
gitea-related
labels 4 days ago

Could you please add documentation (or point to existing) for:

  • What level access from GitLab PAT is required? Is read_api good enough to get everything?
  • Can the GitLab repo be private and still be migrated?
  • Can the GitLab repo be archived and still be migrated?
  • Should the migration succeed or fail if a selected feature to migrate is not actually enabled in the GitLab repo?

?

Another repo that failed to migrate: https://gitlab.com/AutumnMeowMeow/jexer . The GitLab PAT access level was read_api. The GitLab project is archived.

Could you please add documentation (or point to existing) for: * What level access from GitLab PAT is required? Is read_api good enough to get everything? * Can the GitLab repo be private and still be migrated? * Can the GitLab repo be archived and still be migrated? * Should the migration succeed or fail if a selected feature to migrate is not actually enabled in the GitLab repo? ? Another repo that failed to migrate: https://gitlab.com/AutumnMeowMeow/jexer . The GitLab PAT access level was read_api. The GitLab project is archived.
Collaborator

please test again we deployed new gitea version

please test again we deployed new gitea version
Poster

Unfortunately the error is still there.

Unfortunately the error is still there.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Codeberg/Community#677
Loading…
There is no content yet.