On Thu, Jun 4, 2009 at 12:58 AM, Jo Rhett wrote:
> On Jun 3, 2009, at 12:28 PM, Kevin Falcone wrote:
> > I don't think you're doing this from a tarball,
> > you're trying to do it from the installed directory.
>
> Nope, from the extracted tarball in ports directory.
>
> > It gives you an even mor
Everyone has their own way of doing things, but I find upgrading RT is
easiest by essentially installing RT from scratch upon each upgrade and
then soft-linking to the new directory. In this way, upgrades are
straightforward and not hard to follow. For example:
download new RT source
untar/unzip
On Jun 3, 2009, at 12:28 PM, Kevin Falcone wrote:
> I don't think you're doing this from a tarball,
> you're trying to do it from the installed directory.
Nope, from the extracted tarball in ports directory.
> It gives you an even more specific command to run
> at the end of the output from make
Except that your command is just wrong:
$ rt-setup-database --action upgrade --datadir etc/upgrade
...
Enter RT version you're upgrading from: 3.8.2
Going to apply following upgrades:
* 3.8.3
Enter RT version if you want to stop upgrade at some point,
or leave it blank if you want apply above up
On Jun 3, 2009, at 3:17 PM, Jo Rhett wrote:
> On Jun 3, 2009, at 5:30 AM, Kevin Falcone wrote:
>> Yes, there is a database upgrade involved.
>
> $ rt-setup-database --action upgrade --datadir etc/upgrade/3.8.3
> (snip)
> Enter RT version you're upgrading from: 3.8.2
> No DB changes between 3.8.2
On Jun 3, 2009, at 5:30 AM, Kevin Falcone wrote:
> Yes, there is a database upgrade involved.
$ rt-setup-database --action upgrade --datadir etc/upgrade/3.8.3
(snip)
Enter RT version you're upgrading from: 3.8.2
No DB changes between 3.8.2 and 3.8.3
Done.
--
Jo Rhett
Net Consonance : consonant
On Jun 3, 2009, at 5:30 AM, Kevin Falcone wrote:
>> Is a database upgrade needed? When we went from 3.8.2 to .3 it failed
>> saying that group something id already exists.
>
> Yes, there is a database upgrade involved.
Really? Documentation didn't mention that.
> UPGRADING FROM 3.8.2 and earlie
2009/6/3 Kevin Falcone :
>
> On Jun 3, 2009, at 9:20 AM, Gavin Henry wrote:
>
>> Yeah, we use Pg.
>> We got 'relation 'groupmembers1' already exists.
>
> Oh, thats ok. We added an index that existed on MySQL but not on Pg,
> but if you do your own database tuning there is always a chance
> we'll c
Great, thanks! Will run that later and report back.
On 03/06/2009, Kevin Falcone wrote:
>
> On Jun 3, 2009, at 9:20 AM, Gavin Henry wrote:
>
>> Yeah, we use Pg.
>> We got 'relation 'groupmembers1' already exists.
>
> Oh, thats ok. We added an index that existed on MySQL but not on Pg,
> but if y
On Jun 3, 2009, at 9:20 AM, Gavin Henry wrote:
> Yeah, we use Pg.
> We got 'relation 'groupmembers1' already exists.
Oh, thats ok. We added an index that existed on MySQL but not on Pg,
but if you do your own database tuning there is always a chance
we'll conflict with you. Pointers to portabl
Yeah, we use Pg.
We got 'relation 'groupmembers1' already exists.
On 03/06/2009, jmose...@corp.xanadoo.com wrote:
> I see a database upgrade for postgres, but nothing for mysql going from
> 3.8.2 to 3.8.3. Perhaps I'm missing something...
>
>
> James Moseley
>
>
>
> Kevin Falcone wrote:
>
>
>
On Jun 3, 2009, at 9:18 AM, jmose...@corp.xanadoo.com wrote:
> I see a database upgrade for postgres, but nothing for mysql going
> from
> 3.8.2 to 3.8.3. Perhaps I'm missing something...
etc/upgrade/3.8.3/content
It isn't a schema change, but it upgrades things in the database.
-kevin
>
>
I see a database upgrade for postgres, but nothing for mysql going from
3.8.2 to 3.8.3. Perhaps I'm missing something...
James Moseley
Kevin Falcone wrote:
Yes, there is a database upgrade involved.
___
http://lists.bestpractical.com/cgi-
Will do, thanks.
On 03/06/2009, Kevin Falcone wrote:
>
> On Jun 3, 2009, at 6:43 AM, Gavin Henry wrote:
>
>> Is a database upgrade needed? When we went from 3.8.2 to .3 it failed
>> saying that group something id already exists.
>
> Yes, there is a database upgrade involved.
>
> Please send the f
On Jun 3, 2009, at 6:43 AM, Gavin Henry wrote:
> Is a database upgrade needed? When we went from 3.8.2 to .3 it failed
> saying that group something id already exists.
Yes, there is a database upgrade involved.
Please send the full error message and the command you use
to rt-b...@bestpractical.
Is a database upgrade needed? When we went from 3.8.2 to .3 it failed
saying that group something id already exists.
Thanks.
On 01/06/2009, Jesse Vincent wrote:
>
>
>> Second, I just wanted to point out to folks that use WebExternalAuth, and
>> potentially the companion WebFallbackToInternalAuth
On Mon, Jun 01, 2009 at 01:53:38PM -0400, Jesse Vincent wrote:
>
>
> > Second, I just wanted to point out to folks that use
> > WebExternalAuth, and potentially the companion
> > WebFallbackToInternalAuth, that it has been reversed. In RT 3.8.2,
> > it was "...is undefined, the user..." and in 3
On Jun 1, 2009, at 1:51 PM, Paul Hirose wrote:
> First, thank you to the BP team for the update. Making a good
> product better is always welcome :)
>
> Second, I just wanted to point out to folks that use
> WebExternalAuth, and potentially the companion
> WebFallbackToInternalAuth, that i
> Second, I just wanted to point out to folks that use WebExternalAuth, and
> potentially the companion WebFallbackToInternalAuth, that it has been
> reversed. In RT 3.8.2, it was "...is undefined, the user..." and in 3.8.3,
> it is now "...is defined, the user..." so please be careful.
My r
First, thank you to the BP team for the update. Making a good product better
is always welcome :)
Second, I just wanted to point out to folks that use WebExternalAuth, and
potentially the companion WebFallbackToInternalAuth, that it has been reversed.
In RT 3.8.2, it was "...is undefined, the
20 matches
Mail list logo
