Questions about upgrading.

I'm running a CVS installation from July 15th. I think it's around the time of 2.0.0 beta5. I'd like to upgrade to the current release (2.0.2 source) but I'm not sure what the best practice is for doing so. I tried by copying the changed files from my 2.0.0 beta5 install overtop of a clean 2.0.2 source install, but that didn't go as well as I expected. All the tickets were there and at first glance everything worked OK, but when I dug a little deeper, I lost all the ticket history. For example, if I click Zoom on a ticket, I would usually be able to see the history of a ticket. Agent responses, Customer responses, notes, etc. After upgrading to 2.0.2 I see none if that. All I see is a whatever updates have been made to that particular thread of the ticket. Is this something that I'm doing wrong or is this some new expected behavior? I didn't touch the database. What I did to find the changed files was: root@eshara# find . -mtime -58d ./var/log/TicketCounter.log ./var/spool ./var/tmp ./var/tmp/TicketHistoryCache ./var/tmp/TicketHistoryCache/2005 ./var/tmp/TicketHistoryCache/2005/07 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_11_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_21_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_7_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_26_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_2_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_17_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_22_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_1_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_18_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_23_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_13_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_16_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_6_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_27_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_25_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_3_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_9_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_12_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_14_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_15_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_20_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_8_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_4_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_24_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_10_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_19_2005\-07\-31 ./var/tmp/TicketHistoryCache/2005/07/TicketHistoryCache_5_2005\-07\-31 ./var/tmp/Kernel-System-Stats-NewTickets-2005-07.cache ./Kernel/Config/Files/Ticket.xml ./Kernel/Config/Files/TicketPostMaster.pm ./Kernel/Config.pm root@eshara# then copied all these files (which were changed after the system was installed) over to the new fresh installation. Any ideas?

On 9/11/05, Jason Lixfeld
I'm running a CVS installation from July 15th. I think it's around the time of 2.0.0 beta5. I'd like to upgrade to the current release (2.0.2 source) but I'm not sure what the best practice is for doing so.
A bit late, but a reply. :) When I upgrade I do the following: - read the release notes (<ahem>) - move the old ./otrs directory to ./otrs.old - extract the new tarball to ./otrs - cd otrs.old; tar cf - var | (cd ../otrs; tar xpf -) - copy otrs.old/Kernel/Config.pm to otrs/Kernel - copy otrs.old/Kernel/Config/GenericAgent.pm to otrs/Kernel/Config - ditto for any other changed config files (I only have those two) - apply any db updates that are needed - report any bugs ;) That's been my working method for upgrading since v0.5. You especially need to copy the entire var directory if you're using *or have at any time used* ArticleStorageFS, because that's where the articles live by default. If you've only ever used ArticleStorageDB, which is the default now, then they'll be in your DB and you don't have to worry about moving them. Bryan
participants (2)
-
Bryan Fullerton
-
Jason Lixfeld