Re: [rt-users] Upgrade question

2013-09-17 Thread Alan Murrell

Quoting Kevin Falcone falc...@bestpractical.com:


4.0.17 was actually added to unstable and testing at the end of
August.  The Debian packager for RT works quite hard.


Ah, I did not know that, though I only run stable in a production  
environment.



  2.) Install RT v4.0.17 on new server.  Import configs and database
from current 4.0.7 server.  Jump to the database schema upgrade part
of the upgrade instructions


This is what I would do.


OK, thanks for the confirmation that that is the way to go (don't  
worry, I won't hold you accountable for anything that goes wrong! lol)


-Alan


--
RT Training in New York, October 8th and 9th: http://bestpractical.com/training


Re: [rt-users] Upgrade question

2013-09-12 Thread Kevin Falcone
On Wed, Sep 11, 2013 at 11:51:52PM -0700, Alan Murrell wrote:
 source install (the repositories are not updated very often, and
 doing a source install will be easier to keep RT updated, IMO)

4.0.17 was actually added to unstable and testing at the end of
August.  The Debian packager for RT works quite hard.

   2.) Install RT v4.0.17 on new server.  Import configs and database
 from current 4.0.7 server.  Jump to the database schema upgrade part
 of the upgrade instructions

This is what I would do.  It's a new server, so you even have plenty
of opportunity to do a test upgrade first.

-kevin


pgpJOuyQ9HUbL.pgp
Description: PGP signature

-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade question

2012-03-02 Thread Thomas Sibley
On 03/02/2012 07:50 AM, Joe Harris wrote:
 We are a virtual shop so I am wondering if I simply clone our 4.0.4
 system, change the name, IP, postfix mail settings and aliases, dump
 and load the database (to a new name) and upgrade the db to 4.0.4
 will it work?  Or do I need to recompile/reconfigure the software and
 change --with-db-database=newdbname?
 
 If I need to reconfigure, is there a simple way of doing that without
 having to go through the entire installation?

You can clone the VM your RT 4.0.4 is running in, but you should also
reconfigure RT and run `make upgrade` again to install any changed files
(before `make upgrade-database`).

When RT installs, it writes into files a few things grabbed from your
./configure line.  To reconfigure (without having to reinstall all the
deps) and make sure you don't miss any changes, you'll want to re-run
./configure on the cloned VM with your tweaked options
(--with-db-database for starters).  You can find the previously used
./configure incant at the top of /opt/rt4/etc/RT_Config.pm.

You might also take the opportunity to upgrade to RT 4.0.5 at the same
time. :)

RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston  March 5  6, 2012