You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently imported a lot of git repositories from another gitblit server. I figured
the quickest way to do this would be to just rsync the repo's over to the new server.
I realise I could have set up a federation etc, but due to connectivity issues, rsync
was a lot easier.
However some repositories have owners which do not exist in the new gitblit installation.
The admin user is not able to modify them, I can only fix it by editing the config
file.
What steps will reproduce the problem?
1. Create a git(blit) repo on gitblit server 1, with owner "FOO"
2. Copy the git folder over to gitblit server 2 (rsync), not having a user named "FOO"
What is the expected output? What do you see instead?
I expect gitblit to either delete unknown users automatically from the list, or display
them anyway for me to manually remote them in the repository page. I see an 2 empty
lists, and i'm not able to change any owner, not even existing ones. See the attached
screenshot.
What version of the product are you using? On what operating system?
Current latest gitblit master (3e0c6ca8a65bd4b076cac1451c9cdfde4be1d4b8), on Ubuntu
14.04 running Tomcat 7 and OpenJDK (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1) 64 bit.
Please provide any additional information below.
I solved the issue by manually editing the config files in the repositories. I have
"basic auth" enabled rather than form based auth.
I could not reproduce your exact symptoms: I had a list of potential owners to choose
from. But I do confirm that your missing owner was not displayed. I have pushed a
fix to display & preserve your missing owner.
Originally reported on Google Code with ID 480
Reported by
robindegen
on 2014-08-05 16:15:11- _Attachment: empty list.png
![empty list.png](https://storage.googleapis.com/google-code-attachments/gitblit/issue-480/comment-0/empty list.png)_
The text was updated successfully, but these errors were encountered: