[Trac] Re: Migrate to TRAC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pavan Balaji skrev 16-07-2008 22:52: | |> Lots of scripting fun with Python, basically. Nothing available right now. | | Is there some documentation on how tickets can be injected into TRAC | from the command line (does it use a SQL back-end)? I can probably | script up something to do this. The link recently posted[1] by Noah on this list might get you started: ~ http://trac.edgewall.org/wiki/TracDev/DataModels [1] http://groups.google.com/group/trac-users/browse_thread/thread/aabfa62d676a1a53/108c1a284823c3bb Best regards, - -- ~ .---. Eirik Schwenke <[EMAIL PROTECTED]> ( NSD ) Harald Hårfagresgate 29Rom 150 ~ '---' N-5007 Bergentlf: (555) 889 13 ~ GPG-key at pgp.mit.edu Id 0x8AA3392C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIgeLcxUW7FIqjOSwRAu0MAKDOS99T1EC3RVVSBc3yi8HqYtZMuACgtun/ mS0eCeOvq8OU29CiVNRobX4= =1QFf -END PGP SIGNATURE- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Migrate to TRAC
> Lots of scripting fun with Python, basically. Nothing available right now. Is there some documentation on how tickets can be injected into TRAC from the command line (does it use a SQL back-end)? I can probably script up something to do this. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Migrate to TRAC
-On [20080716 21:15], Pavan Balaji ([EMAIL PROTECTED]) wrote: >Any suggestions? Lots of scripting fun with Python, basically. Nothing available right now. -- Jeroen Ruigrok van der Werven / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Delirious again, mesmerise my senses, our Souls entwine one more time... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Migrate to TRAC
>> I'm trying to migrate a large project that previous used req >> (http://www.ccs.neu.edu/software/ccs/req) for bug tracking, to use TRAC. >> Is there a way to migrate previously existing bug reports from req to >> TRAC, other than manually entering them into TRAC through the web interface? > > The website is a bit unclear to me, how does req store its tickets? A > mailbox? Yes. It uses a directory structure to separate active requests, resolved requests, etc.: - $ ls active errors etc faq resolved - Within each directory, each request is listed as a separate mailbox format file: $ cd active; ls 122 2217 2716 2949 3226 3381 3481 3555 3654 3716 3806 3942 3989 4018 4089 4151 4184 657 125 2228 2797 3004 3270 3422 3492 3559 3662 3721 3825 3944 3993 4023 4110 4154 4185 678 1323 2299 2798 3013 3284 3444 3509 3572 3667 3725 3831 3950 3996 4029 4122 4156 4186 846 136 239 2802 3090 3301 3452 3515 3581 3672 3745 3838 3967 4000 4030 4126 4167 4187 864 187 2418 2849 3093 3340 3468 3534 3590 3673 3778 3844 3981 4001 4041 4137 4173 4188 2003 242 2881 3141 3349 3469 3540 3591 3683 3790 3853 3982 4004 4048 4139 4175 630 212 261 2900 3153 3356 3476 3549 3606 3685 3792 3897 3985 4008 4056 4141 4176 631 2132 2626 2932 3163 3376 3479 3554 3620 3688 3801 3924 3986 4010 4059 4147 4183 656 Any suggestions? Thanks. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Migrate to TRAC
-On [20080716 09:47], Pavan Balaji ([EMAIL PROTECTED]) wrote: >I'm trying to migrate a large project that previous used req >(http://www.ccs.neu.edu/software/ccs/req) for bug tracking, to use TRAC. >Is there a way to migrate previously existing bug reports from req to >TRAC, other than manually entering them into TRAC through the web interface? The website is a bit unclear to me, how does req store its tickets? A mailbox? -- Jeroen Ruigrok van der Werven / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Death is that state where one exists only in the memories of others... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
