Imported repository are empty
Closed
Imported repository are empty
Created by: Spy-Seth
Hi,
I've convert some old SVN repository to Git. Now I'm trying to import them in my gitlab instance and I'm not sure if this a bug.
So, I've made some bare repository and move them on my /home/git/repositories/ directory. Here an example of the content of this directory :
root@walter:/home/git/gitlab# tree /home/git/repositories/notaresse-bare.git/
../repositories/notaresse-bare.git/
├── branches
├── config
├── description
├── HEAD
├── hooks
│ ├── applypatch-msg.sample
│ ├── commit-msg.sample
│ ├── post-update.sample
│ ├── pre-applypatch.sample
│ ├── pre-commit.sample
│ ├── prepare-commit-msg.sample
│ ├── pre-push.sample
│ ├── pre-rebase.sample
│ └── update.sample
├── info
│ └── exclude
├── objects
│ ├── info
│ └── pack
│ ├── pack-bbe55732631a2276438270207496fb136e6416d4.idx
│ └── pack-bbe55732631a2276438270207496fb136e6416d4.pack
└── refs
├── heads
│ ├── iteration-objet
│ ├── master
│ └── tags
│ ├── Notaresse_r1
│ ├── Notaresse-r1
│ └── Notaresse-r2
└── tags
10 directories, 20 filesWe can see, I've three tags in this repo. To be sure this repo is own by git:git and I have put the 777 permissions
Now I start the import with the import command run in Gitlab home : sudo -u git -H bundle exec rake gitlab:import:repos RAILS_ENV=production.
Everything them to be fine :
root@walter:/home/git/gitlab# sudo -u git -H bundle exec rake gitlab:import:repos RAILS_ENV=production
Processing...
* Skipping wiki repo
[...]
Processing agenda-bare.git
2014-03-01T21:20:09Z 9653 TID-ovp7ts1b4 INFO: Sidekiq client with redis options
* Created agenda-bare (agenda-bare.git)
Processing notaresse-bare.git
* Created notaresse-bare (notaresse-bare.git)
Processing horloge-binaire-bare.git
* Created horloge-binaire-bare (horloge-binaire-bare.git)
[...]
Done!Now if I open this new repo in the Gitlab webview, I see an empty repository.
And if I explore the content on disk it seems some information are missing. The refs/tags directory is empty (objects/packs too) :
root@walter:/home/git/gitlab# tree /home/git/repositories/spy-seth/notaresse-bare.git/
../repositories/spy-seth/notaresse-bare.git/
├── branches
├── config
├── description
├── HEAD
├── hooks
│ ├── applypatch-msg.sample
│ ├── commit-msg.sample
│ ├── post-update.sample
│ ├── pre-applypatch.sample
│ ├── pre-commit.sample
│ ├── prepare-commit-msg.sample
│ ├── pre-push.sample
│ ├── pre-rebase.sample
│ ├── update -> /home/git/gitlab-shell/hooks/update
│ └── update.sample
├── info
│ └── exclude
├── objects
│ ├── info
│ └── pack
└── refs
├── heads
└── tags
9 directories, 14 filesSo my mistake or is a gitlab issue ?
I use the last version (6.6.4) of Gitlab, and the check command do not show any error on my installation.
root@walter:/home/git/gitlab# sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...
Git configured for git user? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 1.7.9 ? ... OK (1.8.0)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ...
Armand Abric / Solr overview presentation ... ok
[...]
Armand Abric / Binary clock ... repository is empty
Armand Abric / agenda-bare ... repository is empty
Armand Abric / notaresse-bare ... repository is empty
Armand Abric / horloge-binaire-bare ... repository is empty
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
/home/git/repositories: OK
/home/git/.ssh/authorized_keys: OK
Test redis-cli executable: redis-cli 2.8.6
Send ping to redis server: PONG
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
Armand Abric / Solr overview presentation ... yes
[...]
Armand Abric / Binary clock ... yes
Armand Abric / agenda-bare ... yes
Armand Abric / notaresse-bare ... yes
Armand Abric / horloge-binaire-bare ... yes
Projects have satellites? ...
Armand Abric / Solr overview presentation ... yes
[...]
Armand Abric / Binary clock ... can't create, repository is empty
Armand Abric / agenda-bare ... can't create, repository is empty
Armand Abric / notaresse-bare ... can't create, repository is empty
Armand Abric / horloge-binaire-bare ... can't create, repository is empty
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/local/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.5)
Checking GitLab ... FinishedHere some environment information :
root@walter:/home/git/gitlab# sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
System information
System: Debian 6.0.9
Current User: git
Using RVM: no
Ruby Version: 2.0.0p353
Gem Version: 2.0.14
Bundler Version:1.5.3
Rake Version: 10.1.1
GitLab information
Version: 6.6.4
Revision: 42e34ae
Directory: /home/git/gitlab
DB Adapter: postgresql
URL: ...
HTTP Clone URL: ...
SSH Clone URL: ...
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 1.8.0
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/local/bin/gitCreated by: Razer6
Thanks for your interest in GitLab. We don't use the GitHub issue tracker for feature requests. Please use http://feedback.gitlab.com/ for this purpose or create a pull request implementing this feature. Have a look at the contribution guidelines for more information.
By Administrator on 2014-06-20T21:33:46 (imported from GitLab project)
