[tahoe-dev] migration complete, Trac is back online

[Brian]

>> I'll probably do this in the early afternoon, pacific time, roughly
>> 15 hours from now.

The migration is finished. Trac is now back online.

All [1234] -style TracLinks which reference revisions on the old darcs
trunk have been rewritten to point at git revision hashes on the new git
trunk. The darcs-based Trac branches have been removed. "trunk" now
refers to git. [1234/branch] -style links which reference the old darcs
branches are left unchanged, and are now dangling.

I've also updated many URLs that used ?rev=1234 to point at specific
revisions (usually to reference a specific line of a specific revision
of a source file). Many are broken, however, because they still point to
the old allmydata.org hostname.

There are a surprisingly large number of ways to refer to specific
changeset revisions, and my scripts probably missed a couple. I've
opened ticket #1964 to gather links that need fixing: please add
comments to it when you encounter them. I've also attached some tables
for help when mapping trac's linear notion of darcs branches (e.g.
[1234/cloud-backend]) to darcs revision hashes (which are things you can
look up in a darcs checkout). I believe these tables, plus a copy of a
darcs repo for each of the old darcs-based branches, is sufficient to
figure out what each [1234/cloud-backend] really points to. This should
be enough info to e.g. build a git branch that matches. If/when we build
such branches, we will have enough to update the [1234/cloud-backend]
links to be non-dangling once again.

If you see anything weird, please find me (warner) on IRC, or send mail
to tahoe-dev. This migration required some sqlite surgery, and it's
entirely possible that I broke something. Also, you might make a mental
note of whatever changes you make over the next day or two: if we
discover something really really weird and need to revert to a backup,
you don't want to lose those changes entirely.

cheers,
  -Brian