MonaSearch bugs

Asked by Hendrik Maryns

Hi there,

the server on which I host my Trac instance is going to be shut down in the near future. I’d like to import all bugs into Launchpad. Is this possible?

I installed the Trac plugin as described in https://help.launchpad.net/Bugs/TracPlugin, but now I no longer know what to do.

Project: monasearch
Bug tracker: monasearch-bugs

Cheers, H.

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
Graham Binns Edit question
Last query:
Last reply:
Whiteboard:
I'm in touch with Hendrick by email and waiting for a response --gmb 2009-06-26
Revision history for this message
Graham Binns (gmb) said :
#1

Hi Hendrik, thanks for your question.

Unfortunately the Trac Launchpad plugin isn't capable of mirroring all the bugs, comments and patches from a Trac instance to Launchpad just yet.

However, we have an exporter script for Trac that will allow you to dump the entire Trac database into an XML export file which we can then import into Launchpad. The way things usually work is:

1) You provide the XML dump
2) We import the XML dump onto a demo instance of Launchpad so that you can check the import is sane
3) Once you're happy with the results of step 2 (we can repeat it if necessary) we import the bugs into the Launchpad production database.

Is this a suitable solution for you? If so, I'll prepare the script and send it to you within a couple of days so you can get cracking.

Revision history for this message
Hendrik Maryns (hamaryns) said :
#2

Sounds good. Please give me some more instructions, I’ll get to it soon.

Revision history for this message
Graham Binns (gmb) said :
#3

Excellent! I'll prepare the script for you (it's still got some code in it specific to another project; I've not yet had chance to make it suitable for general use). Once I've done that I'll forward it to you and we can take it from there. I'll send it to you by Monday at the latest.

Revision history for this message
Hendrik Maryns (hamaryns) said :
#4

Hi there,

Is something going to happen here? I haven’t heard anything for a while now and it seems like the server that is hosting the project is about to be shut down soon, so it is getting urgent!

Revision history for this message
Hendrik Maryns (hamaryns) said :
#5

I am following the instructions I found in another answer: https://answers.edge.launchpad.net/malone/+question/73758, but:

# ./migrate.py /home/server/svn/trac/db/ /home/server/svn/trac/attachments/ monasearch-trac
WARNING:root:Methods redefined (Person) in ['set'] ... At your own risks
Traceback (most recent call last):
  File "./migrate.py", line 495, in <module>
    sys.exit(main(sys.argv[1:]))
  File "./migrate.py", line 466, in main
    db = TracDb(trac_db, attachments_dir)
  File "./migrate.py", line 147, in __init__
    database=filename)
  File "/root/trac-launchpad-migrator/db_backend.py", line 99, in __init__
    self._init_backend(backend_name)
  File "/root/trac-launchpad-migrator/db_backend.py", line 141, in _init_backend
    self.connect()
  File "/root/trac-launchpad-migrator/db_backend.py", line 154, in connect
    self._db = self._db_module.connect(**self._params)
sqlite3.OperationalError: unable to open database file

Or did I use the wrong arguments? With the db file as argument, I get this:

 # ./migrate.py /home/server/svn/trac/db/trac.db /home/server/svn/trac/attachments/ monasearch-trac
WARNING:root:Methods redefined (Person) in ['set'] ... At your own risks
[ticket 3] pb with owner Chris
Traceback (most recent call last):
  File "./migrate.py", line 495, in <module>
    sys.exit(main(sys.argv[1:]))
  File "./migrate.py", line 479, in main
    for attachment in db.get_attachments(ticket):
  File "./migrate.py", line 233, in get_attachments
    data = open(attachment_filename).read()
IOError: [Errno 2] No such file or directory: '/home/server/svn/trac/attachments/9/mylyn-context.zip'

In both cases, no output file.

Revision history for this message
Hendrik Maryns (hamaryns) said :
#6

Seems like the correct command was

./migrate.py /home/server/svn/trac/db/trac.db /home/server/svn/trac/attachments/ticket/ monasearch-trac

So you need the /ticket/ directory after attachments, and the db file explicitly.

Revision history for this message
Graham Binns (gmb) said :
#7

Hi Hendrick,

I sent you an email a couple of days ago requesting that you re-send me your Trac export. I've yet to receive a reply, so I'm just checking that my email actually reached you :).

Additionally, it would be a good idea for you to upgrade your copy of the trac-launchpad-migrator to version 0.1.2 (or the tip of trunk). Version 0.1.2 includes certain bug fixes which may make the migration smoother.

Regards,

Graham

Revision history for this message
Hendrik Maryns (hamaryns) said :
#8

I did send it to you *and* I replied to your mail, sending it again. Strange. Can I maybe upload it here?

Revision history for this message
Graham Binns (gmb) said :
#9

> I did send it to you *and* I replied to your mail, sending it again. Strange. Can I maybe upload it here?

That's very strange. I've seen neither the original nor your reply, and can find neither in my spam trap. Hmm.

The best thing for you to do, I think, would be to upload the xml file to somewhere on the web (there's nowhere in LP that's appropriate for it really) and then paste a URL; I'll grab it from there.

Revision history for this message
Hendrik Maryns (hamaryns) said :
#10

Right, it’s at http://tcl.sfs.uni-tuebingen.de/~hendrik/monasearch-trac.xml. Note that I do get your mails. I used the tip of the migrator.

Revision history for this message
Graham Binns (gmb) said :
#11

On Fri, Jun 26, 2009 at 04:37:08PM -0000, Hendrik Maryns wrote:
> Question #69864 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/69864
>
> Status: Answered => Open
>
> Hendrik Maryns is still having a problem:
> Right, it’s at http://tcl.sfs.uni-tuebingen.de/~hendrik/monasearch-
> trac.xml. Note that I do get your mails. I used the tip of the
> migrator.

Fantastic! This looks okay so far; I'll do a test import locally on
Monday and we'll take it from there.

--
Graham Binns | PGP Key: EC66FA7D

Revision history for this message
Graham Binns (gmb) said :
#12

Hi Hendrik,

I've done the import locally and it ran fine. I'll try to get it up on a
demo server for you today so that you can check it over.

Regards,

Graham

Revision history for this message
Graham Binns (gmb) said :
#13

Hi Hendrik,

I sent you an email a couple of days ago detailing how to check out the demo import that I did of the MonaSearch bugs. Have you had a chance to take a look at it yet? If not, or if you haven't received my mail, please let me know.

Cheers,

Graham

Revision history for this message
Graham Binns (gmb) said :
#14

Hi Hendrik,

I've disabled the EC2 instance for now since it was just consuming money :). Please ping me on IRC when you have time to review the demo import and I'll get it running again for you.

Cheers,

Graham

Revision history for this message
Graham Binns (gmb) said :
#15

Hi Hendrik,

Sorry that this question appears to have got lost in the wash a bit. Do you still want to go ahead with the import?

Revision history for this message
Graham Binns (gmb) said :
#16

Marking needs info for organisation purposes.

Revision history for this message
Hendrik Maryns (hamaryns) said :
#17

It seems the 2009-07-01 email didn’t reach me. Sorry for the money it cost you :-s

I am no longer working on this project, but I asked my successor to answer.

Revision history for this message
Graham Binns (gmb) said :
#18

Hi Hendrik,

Did you manage to talk to your successor at the project?

Revision history for this message
Hendrik Maryns (hamaryns) said :
#19

Hi Graham

Thanks for your efforts. I mailed him, and I will repeat that now, but that’s all I can do now. I am no longer involved and have other things on my mind now (managing a class of 14-year olds, getting them to do maths :-))

Cheers

Revision history for this message
Curtis Hovey (sinzui) said :
#20

I am forcing this question to be expired because no one involved in the mona project want to pursue a bug import.