Sorry list, I've read through hundreds of messages but I've got to ask... again since the question has been asked in a couple of different forms. Thanks go out in advance to Ken Kilgore and Bryan Fullerton for sharing their methods. THE QUESTION: Are there any formal instructions on upgrading OTRS 2.* versions? I just started a month ago with the 2.02 system on a Debian 3.1 machine and it took me a bit of time to get it right... so I'm not eager to touch the database or fool with permissions again. But the 2.03 bug updates sound like they're worth getting and if we're really going to use this system, then I'll have to tackle this question at some point. I sincerely appreciate any suggestions and I will be sure to publish back to the list any solution other than those put forward by the aforementioned contributors. FYI, their suggestions follow at the end of the mail. Sincere thanks. -- jt Message: 2 Date: Fri, 05 Aug 2005 07:23:59 -0500 From: Ken Kilgore Subject: Re: [otrs] Upgrading from 2.0b4 to 2.0.1 To: "User questions and discussions about OTRS.org" Message-ID: <42F35A5F.30302@kaptkaos.com> Content-Type: text/plain; charset="iso-8859-1" I have done this a few times. Upgraded from 2.0 beta 2 to 2.0 beta 4 and then to 2.0.1. I have OTRS installed in /usr/share running on Debian. Here is the process I used to do the upgrades. 1. Untar the 2.0.1 tar ball into /usr/share. 2. Run otrs/scripts/DBUpdate-to-2.0.mysql.sql 1. mysql -f -u root -p otrs < /usr/share/otrs/scripts/DBUpdate-to-2.0.mysql.sql 2. I used the -f to display errors but ignore them. This way you ignore errors about creating tables that already exist. 3. Run otrs/bin/SetPermissions.sh 4. I had to make a few permission adjustments after this but do not remember what I had to change at the moment. The only issue I have at the moment is a problem with merging tickets. Hope this helps. Ken Kilgore ---------------------------------------------- Message: 6 Date: Mon, 19 Sep 2005 14:58:56 -0400 From: Bryan Fullerton Subject: Re: [otrs] Questions about upgrading. To: "User questions and discussions about OTRS.org" Message-ID: <35de0c30050919115830885b81@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On 9/11/05, Jason Lixfeld wrote:

...

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