Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 5:40:34 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 7:32:00 PM UTC-5, RjOllos wrote:
>>
>> On Monday, March 17, 2014 5:29:51 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 7:24:58 PM UTC-5, RjOllos wrote:

 On Monday, March 17, 2014 5:14:12 PM UTC-7, RjOllos wrote:
>
> On Monday, March 17, 2014 5:04:04 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:



 On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>
> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:



 On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>
> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>> > Good in theory but it did not work in my case since 
>> something during the 
>> > trac-admin upgrade command is wiping out some rather 
>> important db 
>> > fields. Now that's not to say that I do not have something 
>> > mis-configured. 
>>
>> It is this 'something' that is worrying me. Granted that Trac 
>> upgrades 
>> are solid and reliable, million times tested process it is 
>> unlikely, 
>> that just you'll get hit by a flaw. Experiencing issues I 
>> would repeat 
>> the process with all plugins disabled/uninstalled and just 
>> upgrade Trac 
>> core, upgrade plugins later on, if required. 
>>
>> > This is my first dealing with Trac from this 
>> > prospective. Since I never got the tractickettemplateplugin 
>> to work I am 
>> > wondering if all of this is associated with the BitNami 
>> install of Trac. 
>>
>> Nothing special with BitNami's stack as far as I know from 
>> using it two 
>> times on WinXP. 
>>
>> > Again, I am a novice but I have definitely learned a lot. 
>> Please don't 
>> > take any of this wrong, I sincerely appreciate you guys 
>> helping me and 
>> > your assistance has gotten me this far. 
>>
>> Sure, you're welcome. Still i hope, that we'll finally get a 
>> clue, what 
>> is going on. Did we talk about DEBUG logs from upgrade 
>> process yet? 
>> Mysteries in code do not any good. 
>>
>> Steffen Hoffmann 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.12 (GNU/Linux) 
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>>
>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>> =6ehf 
>> -END PGP SIGNATURE- 
>>
>
> I've tested with Bitnami Trac and can't reproduce the upgrade 
> issue. I think the only thing left is to look at the database in 
> which the 
> upgrade doesn't seem to have gone correctly.
>
> I see now that my manual import of data into the trac.db has 
 distorted the ticket descriptions formatting. Whereas in the 
 original trac 
 instance I had line feeds between the different sections the data 
 import 
 eliminated the line feeds and now the text is end to end like in 
 notepad.

 Steffen told me it was a bad idea to do a manual update. I just 
 couldn't figure out another way to retrieve my time and timechange 
 fields.

>>>
>>> Have you tried using the trac.db file that I sent back to you? 
>>> The database appears to have been upgraded without any issues and 
>>> you could 
>>> just discard that instance that you manually tweaked. 
>>>
>>
>> Sorry, I missed the db you sent. Never got any type of 
>> notification. 
>>
>
> That is strange. I received a notification when receiving the file 
> you sent, so I assume

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Monday, March 17, 2014 7:32:00 PM UTC-5, RjOllos wrote:
>
> On Monday, March 17, 2014 5:29:51 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 7:24:58 PM UTC-5, RjOllos wrote:
>>>
>>> On Monday, March 17, 2014 5:14:12 PM UTC-7, RjOllos wrote:

 On Monday, March 17, 2014 5:04:04 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:

 On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:

 On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 17:55, ONeal Freeman wrote: 
> > Good in theory but it did not work in my case since 
> something during the 
> > trac-admin upgrade command is wiping out some rather 
> important db 
> > fields. Now that's not to say that I do not have something 
> > mis-configured. 
>
> It is this 'something' that is worrying me. Granted that Trac 
> upgrades 
> are solid and reliable, million times tested process it is 
> unlikely, 
> that just you'll get hit by a flaw. Experiencing issues I 
> would repeat 
> the process with all plugins disabled/uninstalled and just 
> upgrade Trac 
> core, upgrade plugins later on, if required. 
>
> > This is my first dealing with Trac from this 
> > prospective. Since I never got the tractickettemplateplugin 
> to work I am 
> > wondering if all of this is associated with the BitNami 
> install of Trac. 
>
> Nothing special with BitNami's stack as far as I know from 
> using it two 
> times on WinXP. 
>
> > Again, I am a novice but I have definitely learned a lot. 
> Please don't 
> > take any of this wrong, I sincerely appreciate you guys 
> helping me and 
> > your assistance has gotten me this far. 
>
> Sure, you're welcome. Still i hope, that we'll finally get a 
> clue, what 
> is going on. Did we talk about DEBUG logs from upgrade process 
> yet? 
> Mysteries in code do not any good. 
>
> Steffen Hoffmann 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
> =6ehf 
> -END PGP SIGNATURE- 
>

 I've tested with Bitnami Trac and can't reproduce the upgrade 
 issue. I think the only thing left is to look at the database in 
 which the 
 upgrade doesn't seem to have gone correctly.

 I see now that my manual import of data into the trac.db has 
>>> distorted the ticket descriptions formatting. Whereas in the 
>>> original trac 
>>> instance I had line feeds between the different sections the data 
>>> import 
>>> eliminated the line feeds and now the text is end to end like in 
>>> notepad.
>>>
>>> Steffen told me it was a bad idea to do a manual update. I just 
>>> couldn't figure out another way to retrieve my time and timechange 
>>> fields.
>>>
>>
>> Have you tried using the trac.db file that I sent back to you? 
>> The database appears to have been upgraded without any issues and 
>> you could 
>> just discard that instance that you manually tweaked. 
>>
>
> Sorry, I missed the db you sent. Never got any type of 
> notification. 
>

 That is strange. I received a notification when receiving the file 
 you sent, so I assumed you'd receive the same style notification.

 You should be able to access it here: 
 https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 5:29:51 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 7:24:58 PM UTC-5, RjOllos wrote:
>>
>> On Monday, March 17, 2014 5:14:12 PM UTC-7, RjOllos wrote:
>>>
>>> On Monday, March 17, 2014 5:04:04 PM UTC-7, ONeal Freeman wrote:



 On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>>>
>>> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:



 On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>>
>>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:

 -BEGIN PGP SIGNED MESSAGE- 
 Hash: SHA1 

 On 15.03.2014 17:55, ONeal Freeman wrote: 
 > Good in theory but it did not work in my case since something 
 during the 
 > trac-admin upgrade command is wiping out some rather 
 important db 
 > fields. Now that's not to say that I do not have something 
 > mis-configured. 

 It is this 'something' that is worrying me. Granted that Trac 
 upgrades 
 are solid and reliable, million times tested process it is 
 unlikely, 
 that just you'll get hit by a flaw. Experiencing issues I would 
 repeat 
 the process with all plugins disabled/uninstalled and just 
 upgrade Trac 
 core, upgrade plugins later on, if required. 

 > This is my first dealing with Trac from this 
 > prospective. Since I never got the tractickettemplateplugin 
 to work I am 
 > wondering if all of this is associated with the BitNami 
 install of Trac. 

 Nothing special with BitNami's stack as far as I know from 
 using it two 
 times on WinXP. 

 > Again, I am a novice but I have definitely learned a lot. 
 Please don't 
 > take any of this wrong, I sincerely appreciate you guys 
 helping me and 
 > your assistance has gotten me this far. 

 Sure, you're welcome. Still i hope, that we'll finally get a 
 clue, what 
 is going on. Did we talk about DEBUG logs from upgrade process 
 yet? 
 Mysteries in code do not any good. 

 Steffen Hoffmann 
 -BEGIN PGP SIGNATURE- 
 Version: GnuPG v1.4.12 (GNU/Linux) 
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 

 iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 

 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
 =6ehf 
 -END PGP SIGNATURE- 

>>>
>>> I've tested with Bitnami Trac and can't reproduce the upgrade 
>>> issue. I think the only thing left is to look at the database in 
>>> which the 
>>> upgrade doesn't seem to have gone correctly.
>>>
>>> I see now that my manual import of data into the trac.db has 
>> distorted the ticket descriptions formatting. Whereas in the 
>> original trac 
>> instance I had line feeds between the different sections the data 
>> import 
>> eliminated the line feeds and now the text is end to end like in 
>> notepad.
>>
>> Steffen told me it was a bad idea to do a manual update. I just 
>> couldn't figure out another way to retrieve my time and timechange 
>> fields.
>>
>
> Have you tried using the trac.db file that I sent back to you? The 
> database appears to have been upgraded without any issues and you 
> could 
> just discard that instance that you manually tweaked. 
>

 Sorry, I missed the db you sent. Never got any type of 
 notification. 

>>>
>>> That is strange. I received a notification when receiving the file 
>>> you sent, so I assumed you'd receive the same style notification.
>>>
>>> You should be able to access it here: 
>>> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>>>
>>> Let me know if you encounter any problems.  
>>>
>>
>> Downloaded the db. The same fields are still empty...
>>
>
> How did you determine that they are "empty

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Monday, March 17, 2014 7:24:58 PM UTC-5, RjOllos wrote:
>
> On Monday, March 17, 2014 5:14:12 PM UTC-7, RjOllos wrote:
>>
>> On Monday, March 17, 2014 5:04:04 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:



 On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>>
>> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:



 On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>
>
>
> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>
>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE- 
>>> Hash: SHA1 
>>>
>>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>>> > Good in theory but it did not work in my case since something 
>>> during the 
>>> > trac-admin upgrade command is wiping out some rather important 
>>> db 
>>> > fields. Now that's not to say that I do not have something 
>>> > mis-configured. 
>>>
>>> It is this 'something' that is worrying me. Granted that Trac 
>>> upgrades 
>>> are solid and reliable, million times tested process it is 
>>> unlikely, 
>>> that just you'll get hit by a flaw. Experiencing issues I would 
>>> repeat 
>>> the process with all plugins disabled/uninstalled and just 
>>> upgrade Trac 
>>> core, upgrade plugins later on, if required. 
>>>
>>> > This is my first dealing with Trac from this 
>>> > prospective. Since I never got the tractickettemplateplugin to 
>>> work I am 
>>> > wondering if all of this is associated with the BitNami 
>>> install of Trac. 
>>>
>>> Nothing special with BitNami's stack as far as I know from using 
>>> it two 
>>> times on WinXP. 
>>>
>>> > Again, I am a novice but I have definitely learned a lot. 
>>> Please don't 
>>> > take any of this wrong, I sincerely appreciate you guys 
>>> helping me and 
>>> > your assistance has gotten me this far. 
>>>
>>> Sure, you're welcome. Still i hope, that we'll finally get a 
>>> clue, what 
>>> is going on. Did we talk about DEBUG logs from upgrade process 
>>> yet? 
>>> Mysteries in code do not any good. 
>>>
>>> Steffen Hoffmann 
>>> -BEGIN PGP SIGNATURE- 
>>> Version: GnuPG v1.4.12 (GNU/Linux) 
>>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>>
>>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>>> =6ehf 
>>> -END PGP SIGNATURE- 
>>>
>>
>> I've tested with Bitnami Trac and can't reproduce the upgrade 
>> issue. I think the only thing left is to look at the database in 
>> which the 
>> upgrade doesn't seem to have gone correctly.
>>
>> I see now that my manual import of data into the trac.db has 
> distorted the ticket descriptions formatting. Whereas in the original 
> trac 
> instance I had line feeds between the different sections the data 
> import 
> eliminated the line feeds and now the text is end to end like in 
> notepad.
>
> Steffen told me it was a bad idea to do a manual update. I just 
> couldn't figure out another way to retrieve my time and timechange 
> fields.
>

 Have you tried using the trac.db file that I sent back to you? The 
 database appears to have been upgraded without any issues and you 
 could 
 just discard that instance that you manually tweaked. 

>>>
>>> Sorry, I missed the db you sent. Never got any type of notification. 
>>>
>>
>> That is strange. I received a notification when receiving the file 
>> you sent, so I assumed you'd receive the same style notification.
>>
>> You should be able to access it here: 
>> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>>
>> Let me know if you encounter any problems.  
>>
>
> Downloaded the db. The same fields are still empty...
>

 How did you determine that they are "empty"? I pulled the file off 
 Google drive, dropped it into a Trac 1.0.1 instance and they certainly 
 aren't empty. The ticket created, modified and change timestamps are 
 displaying correctly. There must be so

Re: [Trac] Re: Trac.db questions

[Chris Shelton]

The issue with your query is probably that the time functions do not work
on the modified content of the date/time columns after their format was
changed from seconds to microseconds as a part of the 0.11 to 0.12 database
changes.   From http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.12,
this is mentioned:
"Note that the storage format of timestamps has changed from "seconds since
epoch" to "microseconds since epoch" so you may need to adapt your SQL
queries (see corresponding API
notes
)"

I agree with Ryan that you should just try loading the file into a new Trac
instance.  And, you will need to rework your query to deal with the
modified time fields.

chris


On Mon, Mar 17, 2014 at 8:04 PM, ONeal Freeman  wrote:

>
>
> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>
>>
>>
>> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:

 On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:

 On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 15.03.2014 17:55, ONeal Freeman wrote:
> > Good in theory but it did not work in my case since something
> during the
> > trac-admin upgrade command is wiping out some rather important
> db
> > fields. Now that's not to say that I do not have something
> > mis-configured.
>
> It is this 'something' that is worrying me. Granted that Trac
> upgrades
> are solid and reliable, million times tested process it is
> unlikely,
> that just you'll get hit by a flaw. Experiencing issues I would
> repeat
> the process with all plugins disabled/uninstalled and just upgrade
> Trac
> core, upgrade plugins later on, if required.
>
> > This is my first dealing with Trac from this
> > prospective. Since I never got the tractickettemplateplugin to
> work I am
> > wondering if all of this is associated with the BitNami install
> of Trac.
>
> Nothing special with BitNami's stack as far as I know from using
> it two
> times on WinXP.
>
> > Again, I am a novice but I have definitely learned a lot. Please
> don't
> > take any of this wrong, I sincerely appreciate you guys helping
> me and
> > your assistance has gotten me this far.
>
> Sure, you're welcome. Still i hope, that we'll finally get a clue,
> what
> is going on. Did we talk about DEBUG logs from upgrade process
> yet?
> Mysteries in code do not any good.
>
> Steffen Hoffmann
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/
> =6ehf
> -END PGP SIGNATURE-
>

 I've tested with Bitnami Trac and can't reproduce the upgrade
 issue. I think the only thing left is to look at the database in which 
 the
 upgrade doesn't seem to have gone correctly.

 I see now that my manual import of data into the trac.db has
>>> distorted the ticket descriptions formatting. Whereas in the original 
>>> trac
>>> instance I had line feeds between the different sections the data import
>>> eliminated the line feeds and now the text is end to end like in 
>>> notepad.
>>>
>>> Steffen told me it was a bad idea to do a manual update. I just
>>> couldn't figure out another way to retrieve my time and timechange 
>>> fields.
>>>
>>
>> Have you tried using the trac.db file that I sent back to you? The
>> database appears to have been upgraded without any issues and you could
>> just discard that instance that you manually tweaked.
>>
>
> Sorry, I missed the db you sent. Never got any type of notification.
>

 That is strange. I received a notification when receiving the file you
 sent, so I assumed you'd receive the same style notification.

 You should be able to access it here: https://drive.google.com/file/d/
 0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing

 Let me know if you encounter any problems.

>>>
>>> Downloaded the db. The same fi

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 5:14:12 PM UTC-7, RjOllos wrote:
>
> On Monday, March 17, 2014 5:04:04 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:



 On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>
> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:



 On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>
> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>> > Good in theory but it did not work in my case since something 
>> during the 
>> > trac-admin upgrade command is wiping out some rather important 
>> db 
>> > fields. Now that's not to say that I do not have something 
>> > mis-configured. 
>>
>> It is this 'something' that is worrying me. Granted that Trac 
>> upgrades 
>> are solid and reliable, million times tested process it is 
>> unlikely, 
>> that just you'll get hit by a flaw. Experiencing issues I would 
>> repeat 
>> the process with all plugins disabled/uninstalled and just 
>> upgrade Trac 
>> core, upgrade plugins later on, if required. 
>>
>> > This is my first dealing with Trac from this 
>> > prospective. Since I never got the tractickettemplateplugin to 
>> work I am 
>> > wondering if all of this is associated with the BitNami install 
>> of Trac. 
>>
>> Nothing special with BitNami's stack as far as I know from using 
>> it two 
>> times on WinXP. 
>>
>> > Again, I am a novice but I have definitely learned a lot. 
>> Please don't 
>> > take any of this wrong, I sincerely appreciate you guys helping 
>> me and 
>> > your assistance has gotten me this far. 
>>
>> Sure, you're welcome. Still i hope, that we'll finally get a 
>> clue, what 
>> is going on. Did we talk about DEBUG logs from upgrade process 
>> yet? 
>> Mysteries in code do not any good. 
>>
>> Steffen Hoffmann 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.12 (GNU/Linux) 
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>> =6ehf 
>> -END PGP SIGNATURE- 
>>
>
> I've tested with Bitnami Trac and can't reproduce the upgrade 
> issue. I think the only thing left is to look at the database in 
> which the 
> upgrade doesn't seem to have gone correctly.
>
> I see now that my manual import of data into the trac.db has 
 distorted the ticket descriptions formatting. Whereas in the original 
 trac 
 instance I had line feeds between the different sections the data 
 import 
 eliminated the line feeds and now the text is end to end like in 
 notepad.

 Steffen told me it was a bad idea to do a manual update. I just 
 couldn't figure out another way to retrieve my time and timechange 
 fields.

>>>
>>> Have you tried using the trac.db file that I sent back to you? The 
>>> database appears to have been upgraded without any issues and you could 
>>> just discard that instance that you manually tweaked. 
>>>
>>
>> Sorry, I missed the db you sent. Never got any type of notification. 
>>
>
> That is strange. I received a notification when receiving the file you 
> sent, so I assumed you'd receive the same style notification.
>
> You should be able to access it here: 
> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>
> Let me know if you encounter any problems.  
>

 Downloaded the db. The same fields are still empty...

>>>
>>> How did you determine that they are "empty"? I pulled the file off 
>>> Google drive, dropped it into a Trac 1.0.1 instance and they certainly 
>>> aren't empty. The ticket created, modified and change timestamps are 
>>> displaying correctly. There must be something else going on here.
>>>
>>>
>>> 
>>> Does the attached query return any results for you?
>>

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 5:04:04 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:

 On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:

 On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 17:55, ONeal Freeman wrote: 
> > Good in theory but it did not work in my case since something 
> during the 
> > trac-admin upgrade command is wiping out some rather important 
> db 
> > fields. Now that's not to say that I do not have something 
> > mis-configured. 
>
> It is this 'something' that is worrying me. Granted that Trac 
> upgrades 
> are solid and reliable, million times tested process it is 
> unlikely, 
> that just you'll get hit by a flaw. Experiencing issues I would 
> repeat 
> the process with all plugins disabled/uninstalled and just upgrade 
> Trac 
> core, upgrade plugins later on, if required. 
>
> > This is my first dealing with Trac from this 
> > prospective. Since I never got the tractickettemplateplugin to 
> work I am 
> > wondering if all of this is associated with the BitNami install 
> of Trac. 
>
> Nothing special with BitNami's stack as far as I know from using 
> it two 
> times on WinXP. 
>
> > Again, I am a novice but I have definitely learned a lot. Please 
> don't 
> > take any of this wrong, I sincerely appreciate you guys helping 
> me and 
> > your assistance has gotten me this far. 
>
> Sure, you're welcome. Still i hope, that we'll finally get a clue, 
> what 
> is going on. Did we talk about DEBUG logs from upgrade process 
> yet? 
> Mysteries in code do not any good. 
>
> Steffen Hoffmann 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
> =6ehf 
> -END PGP SIGNATURE- 
>

 I've tested with Bitnami Trac and can't reproduce the upgrade 
 issue. I think the only thing left is to look at the database in which 
 the 
 upgrade doesn't seem to have gone correctly.

 I see now that my manual import of data into the trac.db has 
>>> distorted the ticket descriptions formatting. Whereas in the original 
>>> trac 
>>> instance I had line feeds between the different sections the data 
>>> import 
>>> eliminated the line feeds and now the text is end to end like in 
>>> notepad.
>>>
>>> Steffen told me it was a bad idea to do a manual update. I just 
>>> couldn't figure out another way to retrieve my time and timechange 
>>> fields.
>>>
>>
>> Have you tried using the trac.db file that I sent back to you? The 
>> database appears to have been upgraded without any issues and you could 
>> just discard that instance that you manually tweaked. 
>>
>
> Sorry, I missed the db you sent. Never got any type of notification. 
>

 That is strange. I received a notification when receiving the file you 
 sent, so I assumed you'd receive the same style notification.

 You should be able to access it here: 
 https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing

 Let me know if you encounter any problems.  

>>>
>>> Downloaded the db. The same fields are still empty...
>>>
>>
>> How did you determine that they are "empty"? I pulled the file off Google 
>> drive, dropped it into a Trac 1.0.1 instance and they certainly aren't 
>> empty. The ticket created, modified and change timestamps are displaying 
>> correctly. There must be something else going on here.
>>
>>
>> 
>> Does the attached query return any results for you?
>>
>
No, but I will assume that the query is just incorrect.

Have you tried putting the trac.db file I sent into your Trac instance? 

-- 
You received this message because you are subscribed t

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>>>
>>> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:



 On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>>
>>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:

 -BEGIN PGP SIGNED MESSAGE- 
 Hash: SHA1 

 On 15.03.2014 17:55, ONeal Freeman wrote: 
 > Good in theory but it did not work in my case since something 
 during the 
 > trac-admin upgrade command is wiping out some rather important db 
 > fields. Now that's not to say that I do not have something 
 > mis-configured. 

 It is this 'something' that is worrying me. Granted that Trac 
 upgrades 
 are solid and reliable, million times tested process it is 
 unlikely, 
 that just you'll get hit by a flaw. Experiencing issues I would 
 repeat 
 the process with all plugins disabled/uninstalled and just upgrade 
 Trac 
 core, upgrade plugins later on, if required. 

 > This is my first dealing with Trac from this 
 > prospective. Since I never got the tractickettemplateplugin to 
 work I am 
 > wondering if all of this is associated with the BitNami install 
 of Trac. 

 Nothing special with BitNami's stack as far as I know from using it 
 two 
 times on WinXP. 

 > Again, I am a novice but I have definitely learned a lot. Please 
 don't 
 > take any of this wrong, I sincerely appreciate you guys helping 
 me and 
 > your assistance has gotten me this far. 

 Sure, you're welcome. Still i hope, that we'll finally get a clue, 
 what 
 is going on. Did we talk about DEBUG logs from upgrade process yet? 
 Mysteries in code do not any good. 

 Steffen Hoffmann 
 -BEGIN PGP SIGNATURE- 
 Version: GnuPG v1.4.12 (GNU/Linux) 
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 

 iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
 =6ehf 
 -END PGP SIGNATURE- 

>>>
>>> I've tested with Bitnami Trac and can't reproduce the upgrade issue. 
>>> I think the only thing left is to look at the database in which the 
>>> upgrade 
>>> doesn't seem to have gone correctly.
>>>
>>> I see now that my manual import of data into the trac.db has 
>> distorted the ticket descriptions formatting. Whereas in the original 
>> trac 
>> instance I had line feeds between the different sections the data import 
>> eliminated the line feeds and now the text is end to end like in notepad.
>>
>> Steffen told me it was a bad idea to do a manual update. I just 
>> couldn't figure out another way to retrieve my time and timechange 
>> fields.
>>
>
> Have you tried using the trac.db file that I sent back to you? The 
> database appears to have been upgraded without any issues and you could 
> just discard that instance that you manually tweaked. 
>

 Sorry, I missed the db you sent. Never got any type of notification. 

>>>
>>> That is strange. I received a notification when receiving the file you 
>>> sent, so I assumed you'd receive the same style notification.
>>>
>>> You should be able to access it here: 
>>> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>>>
>>> Let me know if you encounter any problems.  
>>>
>>
>> Downloaded the db. The same fields are still empty...
>>
>
> How did you determine that they are "empty"? I pulled the file off Google 
> drive, dropped it into a Trac 1.0.1 instance and they certainly aren't 
> empty. The ticket created, modified and change timestamps are displaying 
> correctly. There must be something else going on here.
>
>
> 
> Does the attached query return any results for you?
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
SELECT
  p

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 4:40:14 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:

 On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:

 On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 17:55, ONeal Freeman wrote: 
> > Good in theory but it did not work in my case since something 
> during the 
> > trac-admin upgrade command is wiping out some rather important 
> db 
> > fields. Now that's not to say that I do not have something 
> > mis-configured. 
>
> It is this 'something' that is worrying me. Granted that Trac 
> upgrades 
> are solid and reliable, million times tested process it is 
> unlikely, 
> that just you'll get hit by a flaw. Experiencing issues I would 
> repeat 
> the process with all plugins disabled/uninstalled and just upgrade 
> Trac 
> core, upgrade plugins later on, if required. 
>
> > This is my first dealing with Trac from this 
> > prospective. Since I never got the tractickettemplateplugin to 
> work I am 
> > wondering if all of this is associated with the BitNami install 
> of Trac. 
>
> Nothing special with BitNami's stack as far as I know from using 
> it two 
> times on WinXP. 
>
> > Again, I am a novice but I have definitely learned a lot. Please 
> don't 
> > take any of this wrong, I sincerely appreciate you guys helping 
> me and 
> > your assistance has gotten me this far. 
>
> Sure, you're welcome. Still i hope, that we'll finally get a clue, 
> what 
> is going on. Did we talk about DEBUG logs from upgrade process 
> yet? 
> Mysteries in code do not any good. 
>
> Steffen Hoffmann 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
> =6ehf 
> -END PGP SIGNATURE- 
>

 I've tested with Bitnami Trac and can't reproduce the upgrade 
 issue. I think the only thing left is to look at the database in which 
 the 
 upgrade doesn't seem to have gone correctly.

 I see now that my manual import of data into the trac.db has 
>>> distorted the ticket descriptions formatting. Whereas in the original 
>>> trac 
>>> instance I had line feeds between the different sections the data 
>>> import 
>>> eliminated the line feeds and now the text is end to end like in 
>>> notepad.
>>>
>>> Steffen told me it was a bad idea to do a manual update. I just 
>>> couldn't figure out another way to retrieve my time and timechange 
>>> fields.
>>>
>>
>> Have you tried using the trac.db file that I sent back to you? The 
>> database appears to have been upgraded without any issues and you could 
>> just discard that instance that you manually tweaked. 
>>
>
> Sorry, I missed the db you sent. Never got any type of notification. 
>

 That is strange. I received a notification when receiving the file you 
 sent, so I assumed you'd receive the same style notification.

 You should be able to access it here: 
 https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing

 Let me know if you encounter any problems.  

>>>
>>> Downloaded the db. The same fields are still empty...
>>>
>>
>> How did you determine that they are "empty"? I pulled the file off Google 
>> drive, dropped it into a Trac 1.0.1 instance and they certainly aren't 
>> empty. The ticket created, modified and change timestamps are displaying 
>> correctly. There must be something else going on here.
>>
>> Viewing the table in SQLite Administrator. 
>

I think there is something wrong with the way you are viewing it then. Try 
this:

$ sqlite3 trac.db
sqlite> SELECT id, summary, time, changetime FROM ticket LIMIT 5;
1|Sample Ticket|119706886800|119801905700
2|Create VSS URL handler|119733646200|119801921700
3|Migrate VSS to casmetndev01|1

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Monday, March 17, 2014 4:51:20 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>>>
>>> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:



 On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>>
>>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:

 -BEGIN PGP SIGNED MESSAGE- 
 Hash: SHA1 

 On 15.03.2014 17:55, ONeal Freeman wrote: 
 > Good in theory but it did not work in my case since something 
 during the 
 > trac-admin upgrade command is wiping out some rather important db 
 > fields. Now that's not to say that I do not have something 
 > mis-configured. 

 It is this 'something' that is worrying me. Granted that Trac 
 upgrades 
 are solid and reliable, million times tested process it is 
 unlikely, 
 that just you'll get hit by a flaw. Experiencing issues I would 
 repeat 
 the process with all plugins disabled/uninstalled and just upgrade 
 Trac 
 core, upgrade plugins later on, if required. 

 > This is my first dealing with Trac from this 
 > prospective. Since I never got the tractickettemplateplugin to 
 work I am 
 > wondering if all of this is associated with the BitNami install 
 of Trac. 

 Nothing special with BitNami's stack as far as I know from using it 
 two 
 times on WinXP. 

 > Again, I am a novice but I have definitely learned a lot. Please 
 don't 
 > take any of this wrong, I sincerely appreciate you guys helping 
 me and 
 > your assistance has gotten me this far. 

 Sure, you're welcome. Still i hope, that we'll finally get a clue, 
 what 
 is going on. Did we talk about DEBUG logs from upgrade process yet? 
 Mysteries in code do not any good. 

 Steffen Hoffmann 
 -BEGIN PGP SIGNATURE- 
 Version: GnuPG v1.4.12 (GNU/Linux) 
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 

 iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
 =6ehf 
 -END PGP SIGNATURE- 

>>>
>>> I've tested with Bitnami Trac and can't reproduce the upgrade issue. 
>>> I think the only thing left is to look at the database in which the 
>>> upgrade 
>>> doesn't seem to have gone correctly.
>>>
>>> I see now that my manual import of data into the trac.db has 
>> distorted the ticket descriptions formatting. Whereas in the original 
>> trac 
>> instance I had line feeds between the different sections the data import 
>> eliminated the line feeds and now the text is end to end like in notepad.
>>
>> Steffen told me it was a bad idea to do a manual update. I just 
>> couldn't figure out another way to retrieve my time and timechange 
>> fields.
>>
>
> Have you tried using the trac.db file that I sent back to you? The 
> database appears to have been upgraded without any issues and you could 
> just discard that instance that you manually tweaked. 
>

 Sorry, I missed the db you sent. Never got any type of notification. 

>>>
>>> That is strange. I received a notification when receiving the file you 
>>> sent, so I assumed you'd receive the same style notification.
>>>
>>> You should be able to access it here: 
>>> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>>>
>>> Let me know if you encounter any problems.  
>>>
>>
>> Downloaded the db. The same fields are still empty...
>>
>
> How did you determine that they are "empty"? I pulled the file off Google 
> drive, dropped it into a Trac 1.0.1 instance and they certainly aren't 
> empty. The ticket created, modified and change timestamps are displaying 
> correctly. There must be something else going on here.
>
> Viewing the table in SQLite Administrator. 

>
> 
>
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 2:34:12 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>>
>> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:



 On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>
>
>
> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>
>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE- 
>>> Hash: SHA1 
>>>
>>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>>> > Good in theory but it did not work in my case since something 
>>> during the 
>>> > trac-admin upgrade command is wiping out some rather important db 
>>> > fields. Now that's not to say that I do not have something 
>>> > mis-configured. 
>>>
>>> It is this 'something' that is worrying me. Granted that Trac 
>>> upgrades 
>>> are solid and reliable, million times tested process it is unlikely, 
>>> that just you'll get hit by a flaw. Experiencing issues I would 
>>> repeat 
>>> the process with all plugins disabled/uninstalled and just upgrade 
>>> Trac 
>>> core, upgrade plugins later on, if required. 
>>>
>>> > This is my first dealing with Trac from this 
>>> > prospective. Since I never got the tractickettemplateplugin to 
>>> work I am 
>>> > wondering if all of this is associated with the BitNami install of 
>>> Trac. 
>>>
>>> Nothing special with BitNami's stack as far as I know from using it 
>>> two 
>>> times on WinXP. 
>>>
>>> > Again, I am a novice but I have definitely learned a lot. Please 
>>> don't 
>>> > take any of this wrong, I sincerely appreciate you guys helping me 
>>> and 
>>> > your assistance has gotten me this far. 
>>>
>>> Sure, you're welcome. Still i hope, that we'll finally get a clue, 
>>> what 
>>> is going on. Did we talk about DEBUG logs from upgrade process yet? 
>>> Mysteries in code do not any good. 
>>>
>>> Steffen Hoffmann 
>>> -BEGIN PGP SIGNATURE- 
>>> Version: GnuPG v1.4.12 (GNU/Linux) 
>>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>>
>>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>>> =6ehf 
>>> -END PGP SIGNATURE- 
>>>
>>
>> I've tested with Bitnami Trac and can't reproduce the upgrade issue. 
>> I think the only thing left is to look at the database in which the 
>> upgrade 
>> doesn't seem to have gone correctly.
>>
>> I see now that my manual import of data into the trac.db has 
> distorted the ticket descriptions formatting. Whereas in the original 
> trac 
> instance I had line feeds between the different sections the data import 
> eliminated the line feeds and now the text is end to end like in notepad.
>
> Steffen told me it was a bad idea to do a manual update. I just 
> couldn't figure out another way to retrieve my time and timechange fields.
>

 Have you tried using the trac.db file that I sent back to you? The 
 database appears to have been upgraded without any issues and you could 
 just discard that instance that you manually tweaked. 

>>>
>>> Sorry, I missed the db you sent. Never got any type of notification. 
>>>
>>
>> That is strange. I received a notification when receiving the file you 
>> sent, so I assumed you'd receive the same style notification.
>>
>> You should be able to access it here: 
>> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>>
>> Let me know if you encounter any problems.  
>>
>
> Downloaded the db. The same fields are still empty...
>

How did you determine that they are "empty"? I pulled the file off Google 
drive, dropped it into a Trac 1.0.1 instance and they certainly aren't 
empty. The ticket created, modified and change timestamps are displaying 
correctly. There must be something else going on here.



-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Monday, March 17, 2014 4:15:46 PM UTC-5, RjOllos wrote:
>
> On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>>
>>>
>>>
>>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:



 On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>
> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>> > Good in theory but it did not work in my case since something 
>> during the 
>> > trac-admin upgrade command is wiping out some rather important db 
>> > fields. Now that's not to say that I do not have something 
>> > mis-configured. 
>>
>> It is this 'something' that is worrying me. Granted that Trac 
>> upgrades 
>> are solid and reliable, million times tested process it is unlikely, 
>> that just you'll get hit by a flaw. Experiencing issues I would 
>> repeat 
>> the process with all plugins disabled/uninstalled and just upgrade 
>> Trac 
>> core, upgrade plugins later on, if required. 
>>
>> > This is my first dealing with Trac from this 
>> > prospective. Since I never got the tractickettemplateplugin to work 
>> I am 
>> > wondering if all of this is associated with the BitNami install of 
>> Trac. 
>>
>> Nothing special with BitNami's stack as far as I know from using it 
>> two 
>> times on WinXP. 
>>
>> > Again, I am a novice but I have definitely learned a lot. Please 
>> don't 
>> > take any of this wrong, I sincerely appreciate you guys helping me 
>> and 
>> > your assistance has gotten me this far. 
>>
>> Sure, you're welcome. Still i hope, that we'll finally get a clue, 
>> what 
>> is going on. Did we talk about DEBUG logs from upgrade process yet? 
>> Mysteries in code do not any good. 
>>
>> Steffen Hoffmann 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.12 (GNU/Linux) 
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>> =6ehf 
>> -END PGP SIGNATURE- 
>>
>
> I've tested with Bitnami Trac and can't reproduce the upgrade issue. I 
> think the only thing left is to look at the database in which the upgrade 
> doesn't seem to have gone correctly.
>
> I see now that my manual import of data into the trac.db has distorted 
 the ticket descriptions formatting. Whereas in the original trac instance 
 I 
 had line feeds between the different sections the data import eliminated 
 the line feeds and now the text is end to end like in notepad.

 Steffen told me it was a bad idea to do a manual update. I just 
 couldn't figure out another way to retrieve my time and timechange fields.

>>>
>>> Have you tried using the trac.db file that I sent back to you? The 
>>> database appears to have been upgraded without any issues and you could 
>>> just discard that instance that you manually tweaked. 
>>>
>>
>> Sorry, I missed the db you sent. Never got any type of notification. 
>>
>
> That is strange. I received a notification when receiving the file you 
> sent, so I assumed you'd receive the same style notification.
>
> You should be able to access it here: 
> https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing
>
> Let me know if you encounter any problems.  
>

Downloaded the db. The same fields are still empty...

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 2:12:17 PM UTC-7, ONeal Freeman wrote:
>
>
>
> On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:

 On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 17:55, ONeal Freeman wrote: 
> > Good in theory but it did not work in my case since something during 
> the 
> > trac-admin upgrade command is wiping out some rather important db 
> > fields. Now that's not to say that I do not have something 
> > mis-configured. 
>
> It is this 'something' that is worrying me. Granted that Trac upgrades 
> are solid and reliable, million times tested process it is unlikely, 
> that just you'll get hit by a flaw. Experiencing issues I would repeat 
> the process with all plugins disabled/uninstalled and just upgrade 
> Trac 
> core, upgrade plugins later on, if required. 
>
> > This is my first dealing with Trac from this 
> > prospective. Since I never got the tractickettemplateplugin to work 
> I am 
> > wondering if all of this is associated with the BitNami install of 
> Trac. 
>
> Nothing special with BitNami's stack as far as I know from using it 
> two 
> times on WinXP. 
>
> > Again, I am a novice but I have definitely learned a lot. Please 
> don't 
> > take any of this wrong, I sincerely appreciate you guys helping me 
> and 
> > your assistance has gotten me this far. 
>
> Sure, you're welcome. Still i hope, that we'll finally get a clue, 
> what 
> is going on. Did we talk about DEBUG logs from upgrade process yet? 
> Mysteries in code do not any good. 
>
> Steffen Hoffmann 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
> =6ehf 
> -END PGP SIGNATURE- 
>

 I've tested with Bitnami Trac and can't reproduce the upgrade issue. I 
 think the only thing left is to look at the database in which the upgrade 
 doesn't seem to have gone correctly.

 I see now that my manual import of data into the trac.db has distorted 
>>> the ticket descriptions formatting. Whereas in the original trac instance I 
>>> had line feeds between the different sections the data import eliminated 
>>> the line feeds and now the text is end to end like in notepad.
>>>
>>> Steffen told me it was a bad idea to do a manual update. I just couldn't 
>>> figure out another way to retrieve my time and timechange fields.
>>>
>>
>> Have you tried using the trac.db file that I sent back to you? The 
>> database appears to have been upgraded without any issues and you could 
>> just discard that instance that you manually tweaked. 
>>
>
> Sorry, I missed the db you sent. Never got any type of notification. 
>

That is strange. I received a notification when receiving the file you 
sent, so I assumed you'd receive the same style notification.

You should be able to access it here: 
https://drive.google.com/file/d/0B6br6SyRs711OG1sTjNjRXFYVmM/edit?usp=sharing

Let me know if you encounter any problems.  

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Monday, March 17, 2014 1:11:28 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>>
>>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:

 -BEGIN PGP SIGNED MESSAGE- 
 Hash: SHA1 

 On 15.03.2014 17:55, ONeal Freeman wrote: 
 > Good in theory but it did not work in my case since something during 
 the 
 > trac-admin upgrade command is wiping out some rather important db 
 > fields. Now that's not to say that I do not have something 
 > mis-configured. 

 It is this 'something' that is worrying me. Granted that Trac upgrades 
 are solid and reliable, million times tested process it is unlikely, 
 that just you'll get hit by a flaw. Experiencing issues I would repeat 
 the process with all plugins disabled/uninstalled and just upgrade Trac 
 core, upgrade plugins later on, if required. 

 > This is my first dealing with Trac from this 
 > prospective. Since I never got the tractickettemplateplugin to work I 
 am 
 > wondering if all of this is associated with the BitNami install of 
 Trac. 

 Nothing special with BitNami's stack as far as I know from using it two 
 times on WinXP. 

 > Again, I am a novice but I have definitely learned a lot. Please 
 don't 
 > take any of this wrong, I sincerely appreciate you guys helping me 
 and 
 > your assistance has gotten me this far. 

 Sure, you're welcome. Still i hope, that we'll finally get a clue, what 
 is going on. Did we talk about DEBUG logs from upgrade process yet? 
 Mysteries in code do not any good. 

 Steffen Hoffmann 
 -BEGIN PGP SIGNATURE- 
 Version: GnuPG v1.4.12 (GNU/Linux) 
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 

 iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
 =6ehf 
 -END PGP SIGNATURE- 

>>>
>>> I've tested with Bitnami Trac and can't reproduce the upgrade issue. I 
>>> think the only thing left is to look at the database in which the upgrade 
>>> doesn't seem to have gone correctly.
>>>
>>> I see now that my manual import of data into the trac.db has distorted 
>> the ticket descriptions formatting. Whereas in the original trac instance I 
>> had line feeds between the different sections the data import eliminated 
>> the line feeds and now the text is end to end like in notepad.
>>
>> Steffen told me it was a bad idea to do a manual update. I just couldn't 
>> figure out another way to retrieve my time and timechange fields.
>>
>
> Have you tried using the trac.db file that I sent back to you? The 
> database appears to have been upgraded without any issues and you could 
> just discard that instance that you manually tweaked. 
>

Sorry, I missed the db you sent. Never got any type of notification. 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Monday, March 17, 2014 9:29:56 AM UTC-7, ONeal Freeman wrote:
>
>
>
> On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>>
>> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE- 
>>> Hash: SHA1 
>>>
>>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>>> > Good in theory but it did not work in my case since something during 
>>> the 
>>> > trac-admin upgrade command is wiping out some rather important db 
>>> > fields. Now that's not to say that I do not have something 
>>> > mis-configured. 
>>>
>>> It is this 'something' that is worrying me. Granted that Trac upgrades 
>>> are solid and reliable, million times tested process it is unlikely, 
>>> that just you'll get hit by a flaw. Experiencing issues I would repeat 
>>> the process with all plugins disabled/uninstalled and just upgrade Trac 
>>> core, upgrade plugins later on, if required. 
>>>
>>> > This is my first dealing with Trac from this 
>>> > prospective. Since I never got the tractickettemplateplugin to work I 
>>> am 
>>> > wondering if all of this is associated with the BitNami install of 
>>> Trac. 
>>>
>>> Nothing special with BitNami's stack as far as I know from using it two 
>>> times on WinXP. 
>>>
>>> > Again, I am a novice but I have definitely learned a lot. Please don't 
>>> > take any of this wrong, I sincerely appreciate you guys helping me and 
>>> > your assistance has gotten me this far. 
>>>
>>> Sure, you're welcome. Still i hope, that we'll finally get a clue, what 
>>> is going on. Did we talk about DEBUG logs from upgrade process yet? 
>>> Mysteries in code do not any good. 
>>>
>>> Steffen Hoffmann 
>>> -BEGIN PGP SIGNATURE- 
>>> Version: GnuPG v1.4.12 (GNU/Linux) 
>>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>>
>>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>>> =6ehf 
>>> -END PGP SIGNATURE- 
>>>
>>
>> I've tested with Bitnami Trac and can't reproduce the upgrade issue. I 
>> think the only thing left is to look at the database in which the upgrade 
>> doesn't seem to have gone correctly.
>>
>> I see now that my manual import of data into the trac.db has distorted 
> the ticket descriptions formatting. Whereas in the original trac instance I 
> had line feeds between the different sections the data import eliminated 
> the line feeds and now the text is end to end like in notepad.
>
> Steffen told me it was a bad idea to do a manual update. I just couldn't 
> figure out another way to retrieve my time and timechange fields.
>

Have you tried using the trac.db file that I sent back to you? The database 
appears to have been upgraded without any issues and you could just discard 
that instance that you manually tweaked. 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Saturday, March 15, 2014 5:40:29 PM UTC-5, RjOllos wrote:
>
> On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 15.03.2014 17:55, ONeal Freeman wrote: 
>> > Good in theory but it did not work in my case since something during 
>> the 
>> > trac-admin upgrade command is wiping out some rather important db 
>> > fields. Now that's not to say that I do not have something 
>> > mis-configured. 
>>
>> It is this 'something' that is worrying me. Granted that Trac upgrades 
>> are solid and reliable, million times tested process it is unlikely, 
>> that just you'll get hit by a flaw. Experiencing issues I would repeat 
>> the process with all plugins disabled/uninstalled and just upgrade Trac 
>> core, upgrade plugins later on, if required. 
>>
>> > This is my first dealing with Trac from this 
>> > prospective. Since I never got the tractickettemplateplugin to work I 
>> am 
>> > wondering if all of this is associated with the BitNami install of 
>> Trac. 
>>
>> Nothing special with BitNami's stack as far as I know from using it two 
>> times on WinXP. 
>>
>> > Again, I am a novice but I have definitely learned a lot. Please don't 
>> > take any of this wrong, I sincerely appreciate you guys helping me and 
>> > your assistance has gotten me this far. 
>>
>> Sure, you're welcome. Still i hope, that we'll finally get a clue, what 
>> is going on. Did we talk about DEBUG logs from upgrade process yet? 
>> Mysteries in code do not any good. 
>>
>> Steffen Hoffmann 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.12 (GNU/Linux) 
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
>> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
>> =6ehf 
>> -END PGP SIGNATURE- 
>>
>
> I've tested with Bitnami Trac and can't reproduce the upgrade issue. I 
> think the only thing left is to look at the database in which the upgrade 
> doesn't seem to have gone correctly.
>
> I see now that my manual import of data into the trac.db has distorted the 
ticket descriptions formatting. Whereas in the original trac instance I had 
line feeds between the different sections the data import eliminated the 
line feeds and now the text is end to end like in notepad.

Steffen told me it was a bad idea to do a manual update. I just couldn't 
figure out another way to retrieve my time and timechange fields.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Saturday, March 15, 2014 2:48:07 PM UTC-5, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 17:55, ONeal Freeman wrote: 
> > Good in theory but it did not work in my case since something during the 
> > trac-admin upgrade command is wiping out some rather important db 
> > fields. Now that's not to say that I do not have something 
> > mis-configured. 
>
> It is this 'something' that is worrying me. Granted that Trac upgrades 
> are solid and reliable, million times tested process it is unlikely, 
> that just you'll get hit by a flaw. Experiencing issues I would repeat 
> the process with all plugins disabled/uninstalled and just upgrade Trac 
> core, upgrade plugins later on, if required. 
>
> > This is my first dealing with Trac from this 
> > prospective. Since I never got the tractickettemplateplugin to work I am 
> > wondering if all of this is associated with the BitNami install of Trac. 
>
> Nothing special with BitNami's stack as far as I know from using it two 
> times on WinXP. 
>
> > Again, I am a novice but I have definitely learned a lot. Please don't 
> > take any of this wrong, I sincerely appreciate you guys helping me and 
> > your assistance has gotten me this far. 
>
> Sure, you're welcome. Still i hope, that we'll finally get a clue, what 
> is going on. Did we talk about DEBUG logs from upgrade process yet? 
> Mysteries in code do not any good. 
>
> Steffen Hoffmann 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
> =6ehf 
> -END PGP SIGNATURE- 
>

I am fairly convinced I have either botched the installation or 
mis-configured my trac instance. I say that because I replaced the 
setuptools egg from 2.1 to 3.1 when I tried to use it it kept looking for 
the older version. So I manually found all the pth files that still listed 
the old version. Once I put in the new version it worked fine.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Saturday, March 15, 2014 12:48:07 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 17:55, ONeal Freeman wrote: 
> > Good in theory but it did not work in my case since something during the 
> > trac-admin upgrade command is wiping out some rather important db 
> > fields. Now that's not to say that I do not have something 
> > mis-configured. 
>
> It is this 'something' that is worrying me. Granted that Trac upgrades 
> are solid and reliable, million times tested process it is unlikely, 
> that just you'll get hit by a flaw. Experiencing issues I would repeat 
> the process with all plugins disabled/uninstalled and just upgrade Trac 
> core, upgrade plugins later on, if required. 
>
> > This is my first dealing with Trac from this 
> > prospective. Since I never got the tractickettemplateplugin to work I am 
> > wondering if all of this is associated with the BitNami install of Trac. 
>
> Nothing special with BitNami's stack as far as I know from using it two 
> times on WinXP. 
>
> > Again, I am a novice but I have definitely learned a lot. Please don't 
> > take any of this wrong, I sincerely appreciate you guys helping me and 
> > your assistance has gotten me this far. 
>
> Sure, you're welcome. Still i hope, that we'll finally get a clue, what 
> is going on. Did we talk about DEBUG logs from upgrade process yet? 
> Mysteries in code do not any good. 
>
> Steffen Hoffmann 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 
> 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ 
> =6ehf 
> -END PGP SIGNATURE- 
>

I've tested with Bitnami Trac and can't reproduce the upgrade issue. I 
think the only thing left is to look at the database in which the upgrade 
doesn't seem to have gone correctly.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[Steffen Hoffmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15.03.2014 17:55, ONeal Freeman wrote:
> Good in theory but it did not work in my case since something during the
> trac-admin upgrade command is wiping out some rather important db
> fields. Now that's not to say that I do not have something
> mis-configured.

It is this 'something' that is worrying me. Granted that Trac upgrades
are solid and reliable, million times tested process it is unlikely,
that just you'll get hit by a flaw. Experiencing issues I would repeat
the process with all plugins disabled/uninstalled and just upgrade Trac
core, upgrade plugins later on, if required.

> This is my first dealing with Trac from this
> prospective. Since I never got the tractickettemplateplugin to work I am
> wondering if all of this is associated with the BitNami install of Trac.

Nothing special with BitNami's stack as far as I know from using it two
times on WinXP.

> Again, I am a novice but I have definitely learned a lot. Please don't
> take any of this wrong, I sincerely appreciate you guys helping me and
> your assistance has gotten me this far. 

Sure, you're welcome. Still i hope, that we'll finally get a clue, what
is going on. Did we talk about DEBUG logs from upgrade process yet?
Mysteries in code do not any good.

Steffen Hoffmann
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf
2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/
=6ehf
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Saturday, March 15, 2014 9:55:13 AM UTC-7, ONeal Freeman wrote:
>
>
>
> On Saturday, March 15, 2014 10:45:30 AM UTC-5, hasienda wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 15.03.2014 14:24, ONeal Freeman wrote: 
>> > Because of time constraints and the need to get the new instance 
>> online, 
>> > I used SQLite Administrator by Orbmu2k to export the table data from 
>> > those 0.10.4 tables with time/timechange fields into a csv and then 
>> > using the same application to import into the new 1.0.1 tables. 
>> > 
>> > I had to do it twice since the first time I exported data with a comma 
>> > as the delimiter which caused data import issues. Second export I used 
>> a 
>> > pipe as the delimiter. 
>>
>> Bad idea to do so much by hand. I bet this causes the issues you 
>> experience now. Standard way is to shutdown you old Trac appliance, or 
>> do a db hot-copy with trac-admin, copy/move that db to new location and 
>> do an 
>>  trac-admin  upgrade to the whole environment. 
>>
>> See extensive upgrading guidelines in the authoritative Trac wiki 
>> documentation for more details [1]. 
>>
>> Steffen Hoffmann 
>>
>>
>> [1] http://trac.edgewall.org/wiki/TracUpgrade 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.12 (GNU/Linux) 
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlMkdZYACgkQ31DJeiZFuHf1FgCfQB4PIrMGV3xa6K80VHiUVQ6m 
>> LoAAn06Pw094h3K9M42e4Ghs4OHOb64K 
>> =8CGR 
>> -END PGP SIGNATURE- 
>>
>
> Good in theory but it did not work in my case since something during the 
> trac-admin upgrade command is wiping out some rather important db fields. 
> Now that's not to say that I do not have something mis-configured. This is 
> my first dealing with Trac from this prospective. Since I never got the 
> tractickettemplateplugin to work I am wondering if all of this is 
> associated with the BitNami install of Trac. Again, I am a novice but I 
> have definitely learned a lot. Please don't take any of this wrong, I 
> sincerely appreciate you guys helping me and your assistance has gotten me 
> this far. 
>

The upgrade appears to have been successful on Linux:
 - Trac 1.0.1
 - Python 2.7.4
 - SQLite 3.7.15.2

I'll send the file back to you so that you can evaluate and determine if 
you spot any issues. If you don't spot anything, at least you can use the 
upgraded copy rather than the one you had to manually modify.

Next I'll do some testing on Windows to try and spot the issue you 
experienced. Could you also send me a copy of the file that has the 
timestamp problem?

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Saturday, March 15, 2014 10:45:30 AM UTC-5, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 15.03.2014 14:24, ONeal Freeman wrote: 
> > Because of time constraints and the need to get the new instance online, 
> > I used SQLite Administrator by Orbmu2k to export the table data from 
> > those 0.10.4 tables with time/timechange fields into a csv and then 
> > using the same application to import into the new 1.0.1 tables. 
> > 
> > I had to do it twice since the first time I exported data with a comma 
> > as the delimiter which caused data import issues. Second export I used a 
> > pipe as the delimiter. 
>
> Bad idea to do so much by hand. I bet this causes the issues you 
> experience now. Standard way is to shutdown you old Trac appliance, or 
> do a db hot-copy with trac-admin, copy/move that db to new location and 
> do an 
>  trac-admin  upgrade to the whole environment. 
>
> See extensive upgrading guidelines in the authoritative Trac wiki 
> documentation for more details [1]. 
>
> Steffen Hoffmann 
>
>
> [1] http://trac.edgewall.org/wiki/TracUpgrade 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMkdZYACgkQ31DJeiZFuHf1FgCfQB4PIrMGV3xa6K80VHiUVQ6m 
> LoAAn06Pw094h3K9M42e4Ghs4OHOb64K 
> =8CGR 
> -END PGP SIGNATURE- 
>

Good in theory but it did not work in my case since something during the 
trac-admin upgrade command is wiping out some rather important db fields. 
Now that's not to say that I do not have something mis-configured. This is 
my first dealing with Trac from this prospective. Since I never got the 
tractickettemplateplugin to work I am wondering if all of this is 
associated with the BitNami install of Trac. Again, I am a novice but I 
have definitely learned a lot. Please don't take any of this wrong, I 
sincerely appreciate you guys helping me and your assistance has gotten me 
this far. 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[Steffen Hoffmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15.03.2014 14:24, ONeal Freeman wrote:
> Because of time constraints and the need to get the new instance online,
> I used SQLite Administrator by Orbmu2k to export the table data from
> those 0.10.4 tables with time/timechange fields into a csv and then
> using the same application to import into the new 1.0.1 tables. 
> 
> I had to do it twice since the first time I exported data with a comma
> as the delimiter which caused data import issues. Second export I used a
> pipe as the delimiter.

Bad idea to do so much by hand. I bet this causes the issues you
experience now. Standard way is to shutdown you old Trac appliance, or
do a db hot-copy with trac-admin, copy/move that db to new location and
do an
 trac-admin  upgrade to the whole environment.

See extensive upgrading guidelines in the authoritative Trac wiki
documentation for more details [1].

Steffen Hoffmann


[1] http://trac.edgewall.org/wiki/TracUpgrade
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlMkdZYACgkQ31DJeiZFuHf1FgCfQB4PIrMGV3xa6K80VHiUVQ6m
LoAAn06Pw094h3K9M42e4Ghs4OHOb64K
=8CGR
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Friday, March 14, 2014 6:57:40 PM UTC-5, ONeal Freeman wrote:
>
>
>
> On Friday, March 14, 2014 2:12:17 PM UTC-5, RjOllos wrote:
>>
>> On Friday, March 14, 2014 8:24:10 AM UTC-7, ONeal Freeman wrote:
>>>
>>>
>>>
>>> On Thursday, March 13, 2014 6:16:53 PM UTC-5, RjOllos wrote:



 On Thursday, March 13, 2014 1:26:59 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 13.03.2014 21:00, ONeal Freeman wrote: 
> > I just determined that the trac-admin  upgrade is 
> wiping 
> > out the time and timechange fields. 
>
> Which db upgrade do you mean, a Trac core upgrade module? 
>
> Steffen Hoffmann 
>
>
> PS: Despite of posting below the last message text it has been hard to 
> spot that comment to yourself in your latest message. Would you try to 
> do the e-mail message threading more obviously, please? 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 
> vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu 
> =ptrw 
> -END PGP SIGNATURE- 
>


 I would look at whether the other fields involved in the seconds -> 
 microseconds timestamp conversion also exhibit the problem. The fields are 
 shown here:

 http://trac.edgewall.org/browser/trunk/trac/upgrades/db25.py?marks=20-28&rev=12014

 Knowing the exact steps you took, and the System Information (e.g. 
 SQLite and Python versions) on both systems would also be helpful in 
 helping us sort through the issue.

>>>
>>> Use trac-admin hotcopy to backup from trac 0.10.4 on linux server with 
>>> python 2.5 and sqlite 2.8.17
>>>
>>> I do a straight windows drag and drop over-writing the default 
>>> environment created by the BitNami install; trac 1.0.1 using python 2.7.5 
>>> and sqlite 3.7.6.2 
>>>
>>
>> Would it be possible to either?:
>>  * Send the trac.db file for Trac 0.10.4 (if no proprietary data is in 
>> the database)
>>  * If trac.db contains data you don't want to release, create a new Trac 
>> environment on 0.10.4 with some dummy data that demonstrates the upgrade 
>> issue, and send over an archive of the environment.
>>
>> Is there a size limit I can upload? The db is 38MB 
>  
>

Because of time constraints and the need to get the new instance online, I 
used SQLite Administrator by Orbmu2k to export the table data from those 
0.10.4 tables with time/timechange fields into a csv and then using the 
same application to import into the new 1.0.1 tables. 

I had to do it twice since the first time I exported data with a comma as 
the delimiter which caused data import issues. Second export I used a pipe 
as the delimiter.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Friday, March 14, 2014 2:12:17 PM UTC-5, RjOllos wrote:
>
> On Friday, March 14, 2014 8:24:10 AM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Thursday, March 13, 2014 6:16:53 PM UTC-5, RjOllos wrote:
>>>
>>>
>>>
>>> On Thursday, March 13, 2014 1:26:59 PM UTC-7, hasienda wrote:

 -BEGIN PGP SIGNED MESSAGE- 
 Hash: SHA1 

 On 13.03.2014 21:00, ONeal Freeman wrote: 
 > I just determined that the trac-admin  upgrade is wiping 
 > out the time and timechange fields. 

 Which db upgrade do you mean, a Trac core upgrade module? 

 Steffen Hoffmann 


 PS: Despite of posting below the last message text it has been hard to 
 spot that comment to yourself in your latest message. Would you try to 
 do the e-mail message threading more obviously, please? 
 -BEGIN PGP SIGNATURE- 
 Version: GnuPG v1.4.12 (GNU/Linux) 
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 

 iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 
 vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu 
 =ptrw 
 -END PGP SIGNATURE- 

>>>
>>>
>>> I would look at whether the other fields involved in the seconds -> 
>>> microseconds timestamp conversion also exhibit the problem. The fields are 
>>> shown here:
>>>
>>> http://trac.edgewall.org/browser/trunk/trac/upgrades/db25.py?marks=20-28&rev=12014
>>>
>>> Knowing the exact steps you took, and the System Information (e.g. 
>>> SQLite and Python versions) on both systems would also be helpful in 
>>> helping us sort through the issue.
>>>
>>
>> Use trac-admin hotcopy to backup from trac 0.10.4 on linux server with 
>> python 2.5 and sqlite 2.8.17
>>
>> I do a straight windows drag and drop over-writing the default 
>> environment created by the BitNami install; trac 1.0.1 using python 2.7.5 
>> and sqlite 3.7.6.2 
>>
>
> Would it be possible to either?:
>  * Send the trac.db file for Trac 0.10.4 (if no proprietary data is in the 
> database)
>  * If trac.db contains data you don't want to release, create a new Trac 
> environment on 0.10.4 with some dummy data that demonstrates the upgrade 
> issue, and send over an archive of the environment.
>
> Is there a size limit I can upload? The db is 38MB 
 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Friday, March 14, 2014 8:24:10 AM UTC-7, ONeal Freeman wrote:
>
>
>
> On Thursday, March 13, 2014 6:16:53 PM UTC-5, RjOllos wrote:
>>
>>
>>
>> On Thursday, March 13, 2014 1:26:59 PM UTC-7, hasienda wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE- 
>>> Hash: SHA1 
>>>
>>> On 13.03.2014 21:00, ONeal Freeman wrote: 
>>> > I just determined that the trac-admin  upgrade is wiping 
>>> > out the time and timechange fields. 
>>>
>>> Which db upgrade do you mean, a Trac core upgrade module? 
>>>
>>> Steffen Hoffmann 
>>>
>>>
>>> PS: Despite of posting below the last message text it has been hard to 
>>> spot that comment to yourself in your latest message. Would you try to 
>>> do the e-mail message threading more obviously, please? 
>>> -BEGIN PGP SIGNATURE- 
>>> Version: GnuPG v1.4.12 (GNU/Linux) 
>>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>>
>>> iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 
>>> vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu 
>>> =ptrw 
>>> -END PGP SIGNATURE- 
>>>
>>
>>
>> I would look at whether the other fields involved in the seconds -> 
>> microseconds timestamp conversion also exhibit the problem. The fields are 
>> shown here:
>>
>> http://trac.edgewall.org/browser/trunk/trac/upgrades/db25.py?marks=20-28&rev=12014
>>
>> Knowing the exact steps you took, and the System Information (e.g. SQLite 
>> and Python versions) on both systems would also be helpful in helping us 
>> sort through the issue.
>>
>
> Use trac-admin hotcopy to backup from trac 0.10.4 on linux server with 
> python 2.5 and sqlite 2.8.17
>
> I do a straight windows drag and drop over-writing the default environment 
> created by the BitNami install; trac 1.0.1 using python 2.7.5 and sqlite 
> 3.7.6.2 
>

Would it be possible to either?:
 * Send the trac.db file for Trac 0.10.4 (if no proprietary data is in the 
database)
 * If trac.db contains data you don't want to release, create a new Trac 
environment on 0.10.4 with some dummy data that demonstrates the upgrade 
issue, and send over an archive of the environment.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[ONeal Freeman]

On Thursday, March 13, 2014 6:16:53 PM UTC-5, RjOllos wrote:
>
>
>
> On Thursday, March 13, 2014 1:26:59 PM UTC-7, hasienda wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- 
>> Hash: SHA1 
>>
>> On 13.03.2014 21:00, ONeal Freeman wrote: 
>> > I just determined that the trac-admin  upgrade is wiping 
>> > out the time and timechange fields. 
>>
>> Which db upgrade do you mean, a Trac core upgrade module? 
>>
>> Steffen Hoffmann 
>>
>>
>> PS: Despite of posting below the last message text it has been hard to 
>> spot that comment to yourself in your latest message. Would you try to 
>> do the e-mail message threading more obviously, please? 
>> -BEGIN PGP SIGNATURE- 
>> Version: GnuPG v1.4.12 (GNU/Linux) 
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>>
>> iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 
>> vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu 
>> =ptrw 
>> -END PGP SIGNATURE- 
>>
>
>
> I would look at whether the other fields involved in the seconds -> 
> microseconds timestamp conversion also exhibit the problem. The fields are 
> shown here:
>
> http://trac.edgewall.org/browser/trunk/trac/upgrades/db25.py?marks=20-28&rev=12014
>
> Knowing the exact steps you took, and the System Information (e.g. SQLite 
> and Python versions) on both systems would also be helpful in helping us 
> sort through the issue.
>

Use trac-admin hotcopy to backup from trac 0.10.4 on linux server with 
python 2.5 and sqlite 2.8.17

I do a straight windows drag and drop over-writing the default environment 
created by the BitNami install; trac 1.0.1 using python 2.7.5 and sqlite 
3.7.6.2 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[RjOllos]

On Thursday, March 13, 2014 1:26:59 PM UTC-7, hasienda wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 13.03.2014 21:00, ONeal Freeman wrote: 
> > I just determined that the trac-admin  upgrade is wiping 
> > out the time and timechange fields. 
>
> Which db upgrade do you mean, a Trac core upgrade module? 
>
> Steffen Hoffmann 
>
>
> PS: Despite of posting below the last message text it has been hard to 
> spot that comment to yourself in your latest message. Would you try to 
> do the e-mail message threading more obviously, please? 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 
> vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu 
> =ptrw 
> -END PGP SIGNATURE- 
>


I would look at whether the other fields involved in the seconds -> 
microseconds timestamp conversion also exhibit the problem. The fields are 
shown here:
http://trac.edgewall.org/browser/trunk/trac/upgrades/db25.py?marks=20-28&rev=12014

Knowing the exact steps you took, and the System Information (e.g. SQLite 
and Python versions) on both systems would also be helpful in helping us 
sort through the issue.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Trac.db questions

[Steffen Hoffmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 13.03.2014 21:00, ONeal Freeman wrote:
> I just determined that the trac-admin  upgrade is wiping
> out the time and timechange fields.

Which db upgrade do you mean, a Trac core upgrade module?

Steffen Hoffmann


PS: Despite of posting below the last message text it has been hard to
spot that comment to yourself in your latest message. Would you try to
do the e-mail message threading more obviously, please?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3
vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu
=ptrw
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

[Trac] Re: Trac.db questions

[ONeal Freeman]

On Thursday, March 13, 2014 12:00:15 PM UTC-5, ONeal Freeman wrote:
>
> I am migrating trac 0.10.4 from a linux server onto a new trac instance 
> 1.0.1 on windows server.
>
> I copied over the trac.db to keep our existing tickets. 
>
> I have just noticed that the ticket.time, ticket.changetime, and 
> ticket_change.time fields are 0 in the copied db although those fields are 
> correct in the original backed up db.
>
> Has anyone else experienced this?
>
> I am thinking that this was caused by the trac-admin upgrade command or 
> the installation of the TracTicketTemplatePlugin which apparently adds a 
> new table, ticket_template_store to the db.
>
> Am I suppose to do a import of some sort to preserve my data?
>
> Thanks in advance for assistance.
> O'Neal
>
> I just determined that the trac-admin  upgrade is wiping out 
> the time and timechange fields.
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.