Codeberg/Community
54
325
Fork
You've already forked Community
12

Migration from GH fails - Duplicate entry #1822

Closed
opened 2025年03月15日 08:12:31 +01:00 by goetz · 6 comments

Comment

Trying to migrate a public repo from GitHub fails in mostly with duplicate entries failure like:

Error 1062 (23000): Duplicate entry '383413-v1.1.1' for key 'UQE_release_n'

Steps to reproduce:

  • start migration from GitHub with an access token
  • select all but wiki optiion to migrate

Tried workarounds:

  • Migrating this particular repo to a vanilla forgejo instance -> works.
  • Migrating this repo then to codeberg fails with the same error message like in the direct migration attempt from GitHub.
### Comment Trying to migrate a public repo from GitHub fails in mostly with duplicate entries failure like: `Error 1062 (23000): Duplicate entry '383413-v1.1.1' for key 'UQE_release_n'` Steps to reproduce: - start migration from GitHub with an access token - select all but wiki optiion to migrate Tried workarounds: - Migrating this particular repo to a vanilla forgejo instance -> works. - Migrating this repo then to codeberg fails with the same error message like in the direct migration attempt from GitHub.

Hi, did you use the 'Retry migration' functionality?

Hi, did you use the 'Retry migration' functionality?
Author
Copy link

Yes, of course. Always end up in this error message.
As said, migration to a vanilla forgejo instance works for this particular repo but also for others I tried before which also end in a similar error message when trying to migrate to codeberg.

Yes, of course. Always end up in this error message. As said, migration to a vanilla forgejo instance works for this particular repo but also for others I tried before which also end in a similar error message when trying to migrate to codeberg.

@goetz wrote in #1822 (comment):

Yes, of course. Always end up in this error message.

Yes so please don't use this button, remove the repository and start the migration flow again. The 'retry migration' button doesn't try to delete any data that was left by the previous migration; resulting in such errors.

@goetz wrote in https://codeberg.org/Codeberg/Community/issues/1822#issuecomment-3082276: > Yes, of course. Always end up in this error message. Yes so please don't use this button, remove the repository and start the migration flow again. The 'retry migration' button doesn't try to delete any data that was left by the previous migration; resulting in such errors.
Author
Copy link

Thank you. This worked this time.

IMHO than the documentation or labeling is missleading. If the migration fails and a retry button appears, the obvious next step is pushing this.

Could you please point me to the feature in forgejo's codebase, then I would propose a PR if you agree?

Thank you. This worked this time. IMHO than the documentation or labeling is missleading. If the migration fails and a `retry` button appears, the obvious next step is pushing this. Could you please point me to the feature in forgejo's codebase, then I would propose a PR if you agree?

@moderation this is spam with AI hallucinations. Please ban the user.

@moderation this is spam with AI hallucinations. Please ban the user.

@earl-warren
It would be always better to have some more reference, if only your "this" is spam comments remains when things got cleaned up already by a moderator, it is hard for other to understand what "this" was or whether is is gone ;)

@earl-warren It would be always better to have some more reference, if only your "this" is spam comments remains when things got cleaned up already by a moderator, it is hard for other to understand what "this" was or whether is is gone ;)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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#1822
Reference in a new issue
Codeberg/Community
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?