Hi there, I see that there are upgrade instructions fro 2.2* to 2.3* but what about 2.3.2 to 2.3.4 Are there any special considerations. I would assume that it wouldn't be a simple as dragging the new folder in there since I would loose config settings and the likes. Mik
Hello all, I'm in a similar situation as Mik. I would like to upgrade from 2.3.1 to 2.3.4, but we have enough changes in various files that I cannot simply drag the new directories over the old ones and call it good. Is there some documentation for, what should be, a fairly simple upgrade without the drama of losing important configuration changes? Dave Buice -----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Mik Rose Sent: Thursday, January 22, 2009 3:21 PM To: User questions and discussions about OTRS. Subject: [otrs] Upgrade steps from 2.3.2 to 2.3.4? Hi there, I see that there are upgrade instructions fro 2.2* to 2.3* but what about 2.3.2 to 2.3.4 Are there any special considerations. I would assume that it wouldn't be a simple as dragging the new folder in there since I would loose config settings and the likes. Mik _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
We have a heavily customised installation of OTRS and upgrades can be abit of a nightmare, what I tend to resort to is putting the existing and new insallation directories side by side and using something like dirdiff to go through both directories and isolate what has changed, and move those changes into our existing installation correcting any of our customisations as I go (long and tedious process). It would be nice to get some kind of diff/delta patch updates (ours is from a source based installation) so we only need to update the files which have changed instead of having to go through everything in the tar.gz file. Steve Buice, David R wrote:
Hello all,
I'm in a similar situation as Mik. I would like to upgrade from 2.3.1 to 2.3.4, but we have enough changes in various files that I cannot simply drag the new directories over the old ones and call it good.
Is there some documentation for, what should be, a fairly simple upgrade without the drama of losing important configuration changes?
Dave Buice
-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Mik Rose Sent: Thursday, January 22, 2009 3:21 PM To: User questions and discussions about OTRS. Subject: [otrs] Upgrade steps from 2.3.2 to 2.3.4?
Hi there,
I see that there are upgrade instructions fro 2.2* to 2.3* but what about 2.3.2 to 2.3.4
Are there any special considerations. I would assume that it wouldn't be a simple as dragging the new folder in there since I would loose config settings and the likes.
Mik
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- Steven Carr Senior Network Security Engineer - Khipu Networks Ltd. support@khipu-networks.com - www.khipu-networks.com Secure - Compliant - Infrastructure Registered Office: Fairfax House, 15 Fulwood Place, London WC1V 6AY Registered in England. Company Number 5218573
Hi, what is this like at a system with less individual settings? Is it here sufficient to replace all files except for the Config.pm? Markus -----Ursprüngliche Nachricht----- Von: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] Im Auftrag von Buice, David R Gesendet: Donnerstag, 22. Januar 2009 22:03 An: otrs@otrs.org Betreff: Re: [otrs] Upgrade steps from 2.3.2 to 2.3.4? Hello all, I'm in a similar situation as Mik. I would like to upgrade from 2.3.1 to 2.3.4, but we have enough changes in various files that I cannot simply drag the new directories over the old ones and call it good. Is there some documentation for, what should be, a fairly simple upgrade without the drama of losing important configuration changes? Dave Buice -----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Mik Rose Sent: Thursday, January 22, 2009 3:21 PM To: User questions and discussions about OTRS. Subject: [otrs] Upgrade steps from 2.3.2 to 2.3.4? Hi there, I see that there are upgrade instructions fro 2.2* to 2.3* but what about 2.3.2 to 2.3.4 Are there any special considerations. I would assume that it wouldn't be a simple as dragging the new folder in there since I would loose config settings and the likes. Mik _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Sent: Friday, January 23, 2009 3:16 AM Subject: Re: [otrs] Upgrade steps from 2.3.2 to 2.3.4?
Hi,
what is this like at a system with less individual settings? Is it here sufficient to replace all files except for the Config.pm?
Markus
I you have made modifications to the 'core system' files which would/could be modified during an upgrade; this upgrade process is potentially very difficult. These files could be modified during the upgrade as such loosing their modification. If you have done this it is highly recommended that you build any upgrades in an alternate location (or server) first. I have integrated my mod in a custom theme and used this in most cases. This has some good an bad side but has been mostly favorable; performed a major upgrade last year that went seamlessly. If your modifications have been solely to config.pm (or other custom files) or via the system configuration webpage, upgrades should not cause you any problems. This is where OTRS' expects you to customize. LQ
OTRS Administrators, I was able to upgrade my OTRS installation from 2.3.1 to 2.3.4 without stepping on the files I had modified for my customer. I have OTRS installed on a Solaris 10 server. Here are the steps that I followed: 1. I downloaded the file otrs-2.3.4.tar.gz from http://otrs.org to the directory /lapps where otrs 2.3.1 is installed. 2. I "gunzipped" and "untarred" the file. OTRS 2.3.1 is in this directory as /lapps/otrs. 3. I ran the command 'dircmp -s -w 120 otrs otrs-2.3.4 > /tmp/otrsdiff'. This command does a directory comparison. The -s argument suppresses messages about identical files. The -w argument changes the width of the report from default 72 to 120 making it more legible. 4. The first part of the report shows which files are unique to the compared directories. I ignored the unique files in 'otrs' and copied the unique files from 'otrs-2.3.4' into 'otrs'. 5. The second part of the report shows which files are different between the two directories. Whenever I change a file in OTRS I make a backup of the original file with a datestamp and my initials added to the file, e.g. Ticekt.pm.20090204.db. I went through the second part of the report line by line. Whatever files in 'otrs' I had not backed up (and therefore never modified) I replaced with the files from 'otrs-2.3.4'. 6. I was left with six files that I had modified that were 'different' in 2.3.4. I ran the 'diff' command between the 'otrs' and 'otrs-2.3.4' files. If the only difference between the files was my modifications than I left the files alone. If there were changes in the 'otrs-2.3.4' file that were outside of my modifications than I carefully edited the 'otrs' file so that the 2.3.4 changes were included. Perhaps there is an easier way to upgrade but these steps worked for me. Kind regards, David Buice Infrastructure Specialist/SDC-INT 2032653 ITIL Foundation Certified EDS, an HP Company PSIC Operations 7000 Chicago Rd. Warren, MI 48092-1663 Mailstop 430-202-380 Tel: +01 586 575-4525 Fax: +01 586 575-0090 Mobile: +01 248 249-9122 E-mail: david.buice@eds.com We deliver on our commitments so you can deliver on yours.
participants (5)
-
Buice, David R -
LQ Marshall -
Markus Hummel -
Mik Rose -
Steven Carr