Skip to content

changing hierarchical to flat leads to duplicated repos #627

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

Closed
peatsn opened this issue Nov 7, 2016 · 1 comment
Closed

changing hierarchical to flat leads to duplicated repos #627

peatsn opened this issue Nov 7, 2016 · 1 comment
Assignees

Comments

@peatsn
Copy link

peatsn commented Nov 7, 2016

Is switching from hierarchical to flat with not empty repos possible ?
After switching i've got duplications at the storage and in the gitolite.conf

//git_hosting.log

2016-11-01 12:17:41 +0100 [ERROR] move_repositories_tree : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
2016-11-01 12:17:44 +0100 [ERROR] move_repositories_tree : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
2016-11-01 12:17:45 +0100 [ERROR] move_repositories_tree : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
2016-11-01 12:17:47 +0100 [ERROR] move_repositories_tree : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
2016-11-01 12:17:48 +0100 [ERROR] move_repositories_tree : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
2016-11-01 12:17:52 +0100 [ERROR] move_repositories_tree : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
2016-11-01 13:21:53 +0100 [ERROR] move_repositories : the source repository directory is not empty, cannot remove it, exit ! (This repo will be orphan)
@n-rodriguez n-rodriguez self-assigned this Jan 3, 2017
@PowerKiKi
Copy link
Collaborator

As discussed in #732 (comment), issues related to Redmine < 4.0 or severely outdated issues are being closed to help clean up the issue tracker.

If this issue is still relevant to you and you are running Redmine >= 4.0, please open a new issue including all new relevant information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants