Hello mailing list,
Kevin - We gave up on RT 4. RTFM is not the answer. The problem is
threefold:
- DBI is too new to upgrade the old style DB. People running fedora or
rawhide are going to start yelling at some point when they go to upgrade
if they’re upgrading from an old enough version.
- FCGI changed from being statically linked to a module that this
causes…
- …the new mason’s handling of UTF to break the old DB.
That being said - I made it to 3.8.10 which tells me something goes very
wrong between 3.8.10 and 4.0.0. The docs for External Auth talk
about .08 being current. For 3.8.10, the docs talk about .08_02. CPAN
says .09 is out but the docs on the wiki don’t discuss it. Which one do
I use for a 3.8.10 RT?
Joshua Knarr
Systems Engineer
GSI Commerce, Inc. http://www.gsicommerce.com
E-Mail: knarrj@gsicommerce.com
Office: 610-491-7110
Mobile: 484-636-7371
The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.
- DBI is too new to upgrade the old style DB. People running fedora or rawhide are going to
start yelling at some point when they go to upgrade if they’re upgrading from an old enough
version.
I’m afraid I don’t understand this statement.
You may need to provide an error or log snippet that demonstrates the
problem.
- FCGI changed from being statically linked to a module that this causes…
I’m afraid I don’t understand this statement.
You may need to provide an error or log snippet that demonstrates the
problem.
- …the new mason’s handling of UTF to break the old DB.
I’m afraid I don’t understand this statement.
You may need to provide an error or log snippet that demonstrates the
problem.
That being said - I made it to 3.8.10 which tells me something goes very wrong between 3.8.10
and 4.0.0. The docs for External Auth talk about .08 being current. For 3.8.10, the docs talk
about .08_02. CPAN says .09 is out but the docs on the wiki don’t discuss it. Which one do I
use for a 3.8.10 RT?
Use 0.09
I write the README for RT-Authen-ExternalAuth, I do not maintain the
wiki pages for it. My opinion will always be in the README.
-kevin
Kevin - We gave up on RT 4. RTFM is not the answer. The problem is threefold:
Oh, now that I reread your original thread I see.
You didn’t run any database upgrades between 3.4.5 and 4.0.0 other than
those described in UPGRADING.mysql.
That’s going to cause you problems on 3.8.10 also.
-kevin
So RT 3.8.10 is working swimmingly well except for one possible post
upgrade snag - two users (out of 100+) reported that after RT was
restarted they were logged in as someone else.
Any ideas?On Tue, 2011-06-14 at 15:17 -0400, Kevin Falcone wrote:
On Tue, Jun 14, 2011 at 02:50:24PM -0400, Joshua Knarr wrote:
Kevin - We gave up on RT 4. RTFM is not the answer. The problem is threefold:
Oh, now that I reread your original thread I see.
You didn’t run any database upgrades between 3.4.5 and 4.0.0 other than
those described in UPGRADING.mysql.
That’s going to cause you problems on 3.8.10 also.
-kevin
Joshua Knarr
Systems Engineer
GSI Commerce, Inc. http://www.gsicommerce.com
E-Mail: knarrj@gsicommerce.com
Office: 610-491-7110
Mobile: 484-636-7371
The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.