Initial Evolution bug moving script in cvs

[Olav Vitters <olav bkor dhs org>]

I've placed the bug moving script in CVS. This is an initial version.
There are still some bugs in there that I need to fix. The script is in
the bugmasters module under tools/mvbugs.

Quick step-by-step guide:
It works *only* for Bugzilla 2.16 and requires two databases. One
database containing the source data, the other one is the Bugzilla
database where the bugs have to be moved to.
For Ximians 2.10 the dump must be converted to the 2.16 layout. This
is done using a slightly modified checksetup.pl (not in CVS). The
modified checksetup.pl (taken from b.g.o) has unnecessary stuff such as
file permission changes removed. The checksetup.pl/localconfig was also
changed to contain the Ximian priorities, opsys, etc. The following
files are also needed (checksetup.pl depends on these):
  RelationSet.pm, Token.pm, globals.pl

After that the destination database needs to be updated to add the
resolutions from Ximian (notximian, invalid, ...). Once this is done
mvbugs.pl can be used to move the bugs over. The file contains some
variables to configure the products and the information about the two
databases (username, password, etc).

The script is pretty smart and only copies over what it needs. Only
used users/attachments/keywords/... will be copied over (if the dump
contains attachments for other products these will not be copied over).

References to bug numbers and attachments within the comments will be
updated. If a comment references a bug/attachment that isn't moved a
link to bugzilla.ximian.com is given instead (to either show_bug.cgi or
attachment.cgi). Example of the supported references:
  bug 1234
  bug 1234 comment 4
  *** This bug has been marked as a duplicate of 1234 ***
  http://bugzilla.ximian.com/show_bug.cgi?id=1234
  attachment 456
  Created an attachment (id=456)
  http://bugs.ximian.com/showattachment.cgi?attach_id=456
  http://bugzilla.ximian.com/attachment.cgi?id=456
If a comment mentions a bug by using a different method than above the
bug# of attachmentid will not be updated. This can occur if someone
mentioned only the bugnr.

Note that due to a faulty Ximian dump I've been waiting for a while for
a new one. As I need the new dump to continue development this means I
haven't worked on it for a long time (my reason for placing it in CVS).

-- 
Regards,
Olav