Browse files

g2migr name changed to reflect it's only a *pre*-migration checklist

  • Loading branch information...
1 parent 550e7e9 commit dbb2fa375aa96dfaeaac418b9a18c8f29d4f3208 @sitaramc committed Jul 3, 2012
Showing with 22 additions and 9 deletions.
  1. +10 −0 emergencies.mkd
  2. +2 −1 files.mkd
  3. +1 −1 g2incompat.mkd
  4. +3 −2 g2migr-example.mkd
  5. +1 −1 g2migr.mkd
  6. +1 −1 install.mkd
  7. +1 −0 master-toc.mkd
  8. +3 −3 rc.mkd
10 emergencies.mkd
@@ -136,6 +136,16 @@ the answer, but here's a list of files you should blow away.
If you think neither of those is the cause, email me.
+## #nonstd non-standard configs that'll trip you up
+ * having sshd setup to put the authorized\_keys file somewhere other than
+ the default (which is in .ssh in the hosting user's home directory).
+ * having sshd setup to not allow incoming ssh for the hosting user. Check
+ things like 'Allowusers' setting in /etc/ssh/sshd\_config etc.
+ * having the home directory in a partition that is mounted noexec.
## #ngp things that are not gitolite problems
There are several things that appear to be gitolite problems but are not. I
3 files.mkd
@@ -21,7 +21,8 @@ Now you have
./ ../ check-g2-compat* doc/ .git/ install* src/ t/
If we were an existing user, we'd run the migration checker 'check-g2-compat'
-(see [here][g2migr]). For now we're only interested in "gitolite/src", so:
+(start [here][migr] for all migration info). For now we're only interested in
+"gitolite/src", so:
$ ls -aF gitolite/src
./ ../ commands/ gitolite* Gitolite/ gitolite-shell* syntactic-sugar/ triggers/ VREF/
2 g2incompat.mkd
@@ -1,7 +1,7 @@
# #g2incompat incompatibility with g2
This page expands on some incompatibilities that were only briefly mentioned
-in the [migration][g2migr] page.
+in the [pre-migration][g2migr] page.
## #g2i-name NAME rules
5 g2migr-example.mkd
@@ -92,8 +92,9 @@ This is a quick and dirty program to catch some of the big issues.
or that might end up giving *more* access to someone if migrated as-is.
It does NOT attempt to catch all the differences described in the docs.
- INFO 'see docs' usually means doc/g2migr.mkd
- (online at
+ INFO 'see docs' usually means the pre-migration checklist in
+ "g2migr.html"; to get there, start from the main migration
+ page at
checking rc file...
NOTE GL_ADMINDIR is in the right place; assuming you did not mess with
2 g2migr.mkd
@@ -1,4 +1,4 @@
-# #g2migr migrating from g2
+# #g2migr pre-migration checklist
<font color="red"> **This document is a *MUST* read if you are currently using
g2 and want to move to g3.** </font>
2 install.mkd
@@ -191,7 +191,7 @@ are the steps:
1. Check the [dev-status][] page to make sure all the features you want have
been implemented in g3.
-2. Read the [g2 migration][g2migr] page to see what changes affect you and
+2. Read the [pre-migration][g2migr] page to see what changes affect you and
your users, and how much time it might take you to migrate. (The closer
you were to a default install of the old gitolite, the less time a
migration will take.)
1 master-toc.mkd
@@ -16,6 +16,7 @@
* [clean][]ing out a botched install
* [common][ce] errors
* [uncommon][ue] errors
+ * [non-standard configs][nonstd] that'll trip you up
* things that are [not gitolite problems][ngp]
6 rc.mkd
@@ -1,9 +1,9 @@
# the "rc" file (`$HOME/.gitolite.rc`)
**NOTE**: if you're migrating from g2, there are some settings that MUST be
-dealt with **before** running `gitolite setup`; please read the [g2
-migration][g2migr] page and linked pages, and especially the one on
-[presetting the rc file][rc-preset].
+dealt with **before** running `gitolite setup`; please read the
+[migration][migr] page and linked pages, and especially the one on "presetting
+the rc file"

0 comments on commit dbb2fa3

Please sign in to comment.