RT 3.8 beta 2 now available


#1

We’ve integrated about 350 changes to RT in the last two months as
part of the big push toward RT 3.8.0. Many of those changes were made
to integrate features Best Practical has built or prototyped for
clients over the past several years. Below, please find the high-level
changelog for the differences between RT 3.7.81 and RT 3.7.85 (Beta 1
and Beta 2).

At this point, the known remaining work is mostly related to polishing
the new web-based installation mechanism and cleaning up small issues
as they’re reported.

RT 3.7.85 is NOT RECOMMENDED for production use, however we strongly
urge you to deploy it in your testing environment and provide feedback
to help ensure that RT 3.8.0 is released soon and does what you need
when we release it.

http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz
http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz.sig

Best,
Jesse

Major new features:
* Designed a new default RT 3.8 visual style
* Added support for Rich text / HTML mail composition within RT
* Added support for batched email ‘digests’ (Weekly or daily)
as well as the ability for a user disable mail him or herself
* Added the ability for users to build multiple custom 'dashboards’
out of saved searches, saved graphs and saved charts and to mail
those dashboards as reports on a regular basis.
* Added a new, friendlier web-based installation system.
* Added a Graphviz based visualization of ticket relationships
* Added simple buttons to create new related tickets
* Added simple ‘bookmarks’/‘favorites’ support for tickets
* Added the Ability to subscribe to iCalendar feeds of ticket
start/due
dates in Google Calendar / iCal.app
* Integrated “BrandedQueues” RT extension. Let you specify a
different
subject token per queue
* Integrated RT::Action::ExtractSubjectTag to better support
conversations
between multiple ticketing systems
* Integrated RT::Action::LinearEscalate
* Integrated RT::Action::NotifyGroup

Minor new features:
* EmailInput refactoring, for possible later autocompleter
* Clean up prototype/scriptaculous files
* more cleanups on mysql schema vs. charsets, update upgrade
script as well
* Allow “mailto:” links as nav menu items
* Adding a PreForking variant of our Standalone webserver.
(currently disabled)
* Applied a patch from Brian Nelson to add better display of
"large text"
custom fields.
* The “CreateTicket” widget now supports ticket bodies
* Added Dean Edwards “IE7.js” to make it easier to write cross-
browser styles
* Finally killed code duplicated between RT::EmailParser and
RT::InterfaceEmail

PGP.sig (186 Bytes)


#2

Hi,

I’ve just finished installing this on Centos 5.1 with the following built
from source:

PostgreSQL 8.3.1
Perl 5.10.0
mod_perl 2.0.4

so I can show some screenshots at http://blog.suretecsystems.com

But I’m getting:

[Thu May 08 11:02:59 2008] [error] Couldn’t load RT config file
RT_SiteConfig.pm:\n\nNot a GLOB reference at /opt/rt3/lib/RT/Config.pm
line 555.\nCompilation failed in require at /opt/rt3/lib/RT/Config.pm line
306.\nBEGIN failed–compilation aborted at /opt/rt3/bin/webmux.pl line
92.\nCompilation failed in require at (eval 2) line 1.\n

[Thu May 08 11:02:59 2008] [error] Can’t load Perl file:
/opt/rt3/bin/webmux.pl for server rt.localhost:0, exiting…

Config is just what “make install” provides for RT and Apache config is:

cat /etc/httpd/conf.d/perl.conf
LoadModule perl_module modules/mod_perl.so

<VirtualHost *:80>
ServerName rt.localhost

DocumentRoot /opt/rt3/share/html
AddDefaultCharset UTF-8

# optional apache logs for RT
# ErrorLog /opt/rt3/var/log/apache2.error
# TransferLog /opt/rt3/var/log/apache2.access

PerlRequire "/opt/rt3/bin/webmux.pl"

<Location /NoAuth/images>
    SetHandler default
</Location>
<Location />
    SetHandler perl-script
    PerlResponseHandler RT::Mason
</Location>

as per README.

Tips?

Gavin.


#3
> Hi, > > try 'perl /opt/rt3/etc/RT_SiteConfig.pm' and see if perl complains about > something. Maybe is something you missed in the configuration file.

That won’t work because of Set right?


#4

Try the following patch that should fix config:
=== lib/RT/Config.pm
— lib/RT/Config.pm (revision 12186)
+++ lib/RT/Config.pm (local)
@@ -549,7 +549,7 @@
# SCALAR, ARRAY… and other types with
# the same name
my $entry = ${$pack}{$k};

  •        next unless $entry;
    
  •        next unless $entry && ref($entry) eq 'GLOB';
    
           # get entry for type we are looking for
           my $entry_ref = *{$entry}{ ref($ref) };
    

Also, default RT layout has been changed, check ./configure --help and
try layout RT3On Thu, May 8, 2008 at 2:09 PM, Gavin Henry ghenry@perl.me.uk wrote:

Hi,

I’ve just finished installing this on Centos 5.1 with the following built
from source:

PostgreSQL 8.3.1
Perl 5.10.0
mod_perl 2.0.4

so I can show some screenshots at http://blog.suretecsystems.com

But I’m getting:

[Thu May 08 11:02:59 2008] [error] Couldn’t load RT config file
RT_SiteConfig.pm:\n\nNot a GLOB reference at /opt/rt3/lib/RT/Config.pm
line 555.\nCompilation failed in require at /opt/rt3/lib/RT/Config.pm line
306.\nBEGIN failed–compilation aborted at /opt/rt3/bin/webmux.pl line
92.\nCompilation failed in require at (eval 2) line 1.\n

[Thu May 08 11:02:59 2008] [error] Can’t load Perl file:
/opt/rt3/bin/webmux.pl for server rt.localhost:0, exiting…

Config is just what “make install” provides for RT and Apache config is:

cat /etc/httpd/conf.d/perl.conf
LoadModule perl_module modules/mod_perl.so

<VirtualHost *:80>
ServerName rt.localhost

DocumentRoot /opt/rt3/share/html
AddDefaultCharset UTF-8

# optional apache logs for RT
# ErrorLog /opt/rt3/var/log/apache2.error
# TransferLog /opt/rt3/var/log/apache2.access

PerlRequire "/opt/rt3/bin/webmux.pl"

<Location /NoAuth/images>
    SetHandler default
</Location>
<Location />
    SetHandler perl-script
    PerlResponseHandler RT::Mason
</Location>

as per README.

Tips?

Gavin.


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Best regards, Ruslan.


#5

I’ve made that change:

[Thu May 08 12:39:13 2008] [error] Can’t load Perl file:
/opt/rt3/bin/webmux.pl for server rt.localhost:0, exiting…
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 503.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 505.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 505.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 505.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 505.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 505.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 444.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 445.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 453.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 454.
Use of uninitialized value $name in concatenation (.) or string at
/opt/rt3/lib/RT/Config.pm line 454.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 456.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
Use of uninitialized value $name in hash element at
/opt/rt3/lib/RT/Config.pm line 498.
Use of uninitialized value $name in exists at /opt/rt3/lib/RT/Config.pm
line 501.
[Thu May 08 12:42:35 2008] [error] Couldn’t load RT config file
RT_Config.pm:\n\nNot a SCALAR reference at /opt/rt3/lib/RT/Config.pm line
497.\nCompilation failed in require at /opt/rt3/lib/RT/Config.pm line
306.\nBEGIN failed–compilation aborted at /opt/rt3/bin/webmux.pl line
92.\nCompilation failed in require at (eval 2) line 1.\n
[Thu May 08 12:42:35 2008] [error] Can’t load Perl file:
/opt/rt3/bin/webmux.pl for server rt.localhost:0, exiting…


#6

Hi,

Any more news on this?

It didn’t work for me, as per my follow up e-mail last week.

Thanks.


#7

We’ve integrated about 350 changes to RT in the last two months as
part of the big push toward RT 3.8.0. Many of those changes were made
to integrate features Best Practical has built or prototyped for
clients over the past several years. Below, please find the high-level
changelog for the differences between RT 3.7.81 and RT 3.7.85 (Beta 1
and Beta 2).

At this point, the known remaining work is mostly related to polishing
the new web-based installation mechanism and cleaning up small issues
as they’re reported.

RT 3.7.85 is NOT RECOMMENDED for production use, however we strongly
urge you to deploy it in your testing environment and provide feedback
to help ensure that RT 3.8.0 is released soon and does what you need
when we release it.

http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz
http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz.sig

Best,
Jesse

Major new features:
* Designed a new default RT 3.8 visual style
* Added support for Rich text / HTML mail composition within RT
* Added support for batched email ‘digests’ (Weekly or daily)
as well as the ability for a user disable mail him or herself
* Added the ability for users to build multiple custom 'dashboards’
out of saved searches, saved graphs and saved charts and to mail
those dashboards as reports on a regular basis.
* Added a new, friendlier web-based installation system.
* Added a Graphviz based visualization of ticket relationships
* Added simple buttons to create new related tickets
* Added simple ‘bookmarks’/‘favorites’ support for tickets
* Added the Ability to subscribe to iCalendar feeds of ticket
start/due
dates in Google Calendar / iCal.app
* Integrated “BrandedQueues” RT extension. Let you specify a
different
subject token per queue
* Integrated RT::Action::ExtractSubjectTag to better support
conversations
between multiple ticketing systems
* Integrated RT::Action::LinearEscalate
* Integrated RT::Action::NotifyGroup

Minor new features:
* EmailInput refactoring, for possible later autocompleter
* Clean up prototype/scriptaculous files
* more cleanups on mysql schema vs. charsets, update upgrade
script as well
* Allow “mailto:” links as nav menu items
* Adding a PreForking variant of our Standalone webserver.
(currently disabled)
* Applied a patch from Brian Nelson to add better display of
"large text"
custom fields.
* The “CreateTicket” widget now supports ticket bodies
* Added Dean Edwards “IE7.js” to make it easier to write cross-
browser styles
* Finally killed code duplicated between RT::EmailParser and
RT::InterfaceEmail

PGP.sig (186 Bytes)


#8

Hi all,

Anyone tried to install RT-3.7.85 under Solaris 10? I can’t work around
the syslog problem while executing “make initialize-database” even with
the following in my RT_SiteConfig.pm:

@LogToSyslogConf = ( socket => ‘stream’ ) unless (@LogToSyslogConf);

Also tried “inet” and “native” without success. The above solution does
work for 3.6.6 I am currently running though.

[Thu May 8 04:44:35 2008] [crit]: no connection to syslog available
- /dev/conslog is not a socket at
/opt/csw/share/perl/csw/Log/Dispatch/Syslog.pm line 71
(/opt/rt3-beta/lib/RT.pm:358)
no connection to syslog available

Thanks,

Alan

Jesse Vincent wrote:


#9

All options in 3.8 have to be set using Set() function:
Set( @LogToSyslogConf, socket => ‘stream’ );

No more unless checks, no more difference for arrays or hashes.On Thu, May 8, 2008 at 8:55 AM, Alan Cheng chenga@ias.edu wrote:

Hi all,

Anyone tried to install RT-3.7.85 under Solaris 10? I can’t work around
the syslog problem while executing “make initialize-database” even with
the following in my RT_SiteConfig.pm:

@LogToSyslogConf = ( socket => ‘stream’ ) unless (@LogToSyslogConf);

Also tried “inet” and “native” without success. The above solution does
work for 3.6.6 I am currently running though.

[Thu May 8 04:44:35 2008] [crit]: no connection to syslog available
- /dev/conslog is not a socket at
/opt/csw/share/perl/csw/Log/Dispatch/Syslog.pm line 71
(/opt/rt3-beta/lib/RT.pm:358)
no connection to syslog available

Thanks,

Alan

Jesse Vincent wrote:

We’ve integrated about 350 changes to RT in the last two months as
part of the big push toward RT 3.8.0. Many of those changes were made
to integrate features Best Practical has built or prototyped for
clients over the past several years. Below, please find the high-level
changelog for the differences between RT 3.7.81 and RT 3.7.85 (Beta 1
and Beta 2).

At this point, the known remaining work is mostly related to polishing
the new web-based installation mechanism and cleaning up small issues
as they’re reported.

RT 3.7.85 is NOT RECOMMENDED for production use, however we strongly
urge you to deploy it in your testing environment and provide feedback
to help ensure that RT 3.8.0 is released soon and does what you need
when we release it.

http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz
http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz.sig

Best,
Jesse

Major new features:
* Designed a new default RT 3.8 visual style
* Added support for Rich text / HTML mail composition within RT
* Added support for batched email ‘digests’ (Weekly or daily)
as well as the ability for a user disable mail him or herself
* Added the ability for users to build multiple custom 'dashboards’
out of saved searches, saved graphs and saved charts and to mail
those dashboards as reports on a regular basis.
* Added a new, friendlier web-based installation system.
* Added a Graphviz based visualization of ticket relationships
* Added simple buttons to create new related tickets
* Added simple ‘bookmarks’/‘favorites’ support for tickets
* Added the Ability to subscribe to iCalendar feeds of ticket
start/due
dates in Google Calendar / iCal.app
* Integrated “BrandedQueues” RT extension. Let you specify a
different
subject token per queue
* Integrated RT::Action::ExtractSubjectTag to better support
conversations
between multiple ticketing systems
* Integrated RT::Action::LinearEscalate
* Integrated RT::Action::NotifyGroup

Minor new features:
* EmailInput refactoring, for possible later autocompleter
* Clean up prototype/scriptaculous files
* more cleanups on mysql schema vs. charsets, update upgrade
script as well
* Allow “mailto:” links as nav menu items
* Adding a PreForking variant of our Standalone webserver.
(currently disabled)
* Applied a patch from Brian Nelson to add better display of
"large text"
custom fields.
* The “CreateTicket” widget now supports ticket bodies
* Added Dean Edwards “IE7.js” to make it easier to write
cross-browser styles
* Finally killed code duplicated between RT::EmailParser and
RT::InterfaceEmail



http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.


#10

Hi Ruslan,

All options in 3.8 have to be set using Set() function: Set(
@LogToSyslogConf, socket => ‘stream’ );

Thank you very much for the information. That fixed the syslog problem!

Now I need to figure out why RT is complaining about “Config”… I did
check all required Perl modules are installed (make testdeps and fixdeps).

[Thu May 8 18:35:49 2008] [error] Can’t locate object method "Config"
via package “RT” at /opt/rt3-beta/bin/webmux.pl line 91.\nBEGIN
failed–compilation aborted at /opt/rt3-beta/bin/webmux.pl line
92.\nCompilation failed in require at (eval 249) line 1.\n

Syntax error on line 1100 of /opt/csw/apache/conf/httpd.conf:

Can’t locate object method “Config” via package “RT” at
/opt/rt3-beta/bin/webmux.pl line 91.
BEGIN failed–compilation aborted at /opt/rt3-beta/bin/webmux.pl line 92.
Compilation failed in require at (eval 249) line 1.

Below is the snippet for httpd.conf

General setup for the virtual host

DocumentRoot "/opt/rt3-beta/share/html"
ServerName rt.example.com
ServerAdmin root@localhost
ErrorLog /opt/csw/apache/logs/ssl_error_log
TransferLog /opt/csw/apache/logs/ssl_access_log

AddDefaultCharset UTF-8

PerlModule Apache::DBI
PerlRequire /opt/rt3-beta/bin/webmux.pl  <----- this is line 1100

<Location />
 SetHandler perl-script
 PerlHandler RT::Mason
</Location>

Thanks,

Alan

Ruslan Zakirov wrote:


#11

Greetings:

Has anyone added custom fields where the choices are taken from a query
against an outside database, perhaps by modifying the RT code? I didn’t
see anything about this in the docs, and it didn’t seem like “Include
page” in the CF modification screen would be able to achieve this. If
not, where should I look in the source code -
share/html/Elements/EditCustomField seems like a good starting spot.

That’s a feature we’ve added for RT 3.8. If you’re currently in
development, you might want to start with RT 3.7 - we’re trying to get
3.8 ready for release now (though don’t have a scheduled date)

Did this feature actually make it into 3.8? I haven’t found reference to
it in the changelogs.

gordon

Jesse Vincent wrote:


#12

Greetings:

Has anyone added custom fields where the choices are taken from a
query
against an outside database, perhaps by modifying the RT code? I
didn’t
see anything about this in the docs, and it didn’t seem like “Include
page” in the CF modification screen would be able to achieve this. If
not, where should I look in the source code -
share/html/Elements/EditCustomField seems like a good starting spot.

That’s a feature we’ve added for RT 3.8. If you’re currently in
development, you might want to start with RT 3.7 - we’re trying to
get
3.8 ready for release now (though don’t have a scheduled date)

Did this feature actually make it into 3.8? I haven’t found
reference to
it in the changelogs.

Have a look at lib/RT/CustomFieldValues/External.pm

PGP.sig (186 Bytes)


#13

This is more encouraging - running without SSL works OK.

Thanks,

Alan

Alan Cheng wrote:


#14

Fixed. Misconfiguration in httpd.conf…of course! :slight_smile: Both SSL and
non-SSL work now.

The default “web2” theme looks great.

Thanks,

Alan

Alan Cheng wrote:


#15

We’ve integrated about 350 changes to RT in the last two months as
part of the big push toward RT 3.8.0. Many of those changes were
made to integrate features Best Practical has built or prototyped
for clients over the past several years. Below, please find the high-
level changelog for the differences between RT 3.7.81 and RT 3.7.85
(Beta 1 and Beta 2).

At this point, the known remaining work is mostly related to
polishing the new web-based installation mechanism and cleaning up
small issues as they’re reported.

RT 3.7.85 is NOT RECOMMENDED for production use, however we strongly
urge you to deploy it in your testing environment and provide
feedback to help ensure that RT 3.8.0 is released soon and does what
you need when we release it.

http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz
http://download.bestpractical.com/pub/rt/devel/rt-3.7.85.tar.gz.sig

Best,
Jesse

Jesse,

It seg faults for me on a dev box, RedHat Enterprise Linux 5 with Perl
5.10.0. This box was successfully running 3.6.6 with no issues and
only had a few dependencies which needed upgrading to pass a 3.7.85
’make testdeps’.

It dies in HTML::Mason::Request::alter_superclass(), called from
RT::Interface::Web::Request.

HTML::Mason v1.39
CGI v3.37

I’m also getting this error in the log:
[Sun May 18 05:43:40 2008] [warning]: Use of uninitialized value
$method in string ne at /usr/local/lib/perl5/site_perl/5.10.0/HTML/
Mason/Utils.pm line 40. (/usr/local/lib/perl5/site_perl/5.10.0/HTML/
Mason/Utils.pm:40)

Any ideas?

Regards,
Tom


#16

Jesse

Jesse,

It seg faults for me on a dev box, RedHat Enterprise Linux 5 with
Perl 5.10.0. This box was successfully running 3.6.6 with no issues
and only had a few dependencies which needed upgrading to pass a
3.7.85 ‘make testdeps’.

It dies in HTML::Mason::Request::alter_superclass(), called from
RT::Interface::Web::Request.

When you install HTML::Mason, does it run and pass all its tests?

PGP.sig (186 Bytes)


#17

Jesse

Jesse,

It seg faults for me on a dev box, RedHat Enterprise Linux 5 with
Perl 5.10.0. This box was successfully running 3.6.6 with no issues
and only had a few dependencies which needed upgrading to pass a
3.7.85 ‘make testdeps’.

It dies in HTML::Mason::Request::alter_superclass(), called from
RT::Interface::Web::Request.

When you install HTML::Mason, does it run and pass all its tests?

Yes, all except live tests and CHI. If it was an issue with
HTML::Mason I’d expect 15-subclass.t to fail (as it calls the same
alter_superclass method).

t/01-syntax…ok
t/01a-comp-calls…ok
t/02-sections…ok
t/02a-filter…ok
t/04-misc…ok
t/05-request…ok
t/05a-stack-corruption…ok
t/06-compiler…ok
t/06a-compiler_obj…ok
t/06b-compiler-named-subs…ok
t/07-interp…ok
t/07a-interp-mcr…ok
t/07b-interp-static-source…ok
t/09-component…ok
t/09a-comp_content…ok
t/10-cache…ok
t/10a-cache-1.0x…ok
t/10b-cache-chi…skipped
all skipped: CHI is not installed
t/11-inherit…ok
t/12-taint…ok
t/13-errors…ok
t/14-cgi…ok
t/14a-fake_apache…ok
t/15-subclass…ok
t/17-print…ok
t/18-leak…ok
t/19-subrequest…ok
t/20-plugins…ok
t/21-escapes…ok
t/22-path-security…ok
t/23-leak2…ok
t/24-tools…ok
t/99-pod…ok
t/live/CGIHandler…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/apache-filter…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/cgi-no-handler…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/cgi-with-handler…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/libapreq-no-handler…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/libapreq-with-handler…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/multi-conf…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/no-config…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/set-content-type…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/single-level-server-root…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
t/live/taint…skipped
all skipped: $TestConfig->{is_maintainer} is not true or
$TestConfig->{apache_dir} is not a directory
All tests successful, 12 tests skipped.
Files=44, Tests=542, 27 wallclock secs ( 6.42 cusr + 1.52 csys =
7.94 CPU)


#18

Jesse

Jesse,

It seg faults for me on a dev box, RedHat Enterprise Linux 5 with
Perl 5.10.0. This box was successfully running 3.6.6 with no
issues and only had a few dependencies which needed upgrading to
pass a 3.7.85 ‘make testdeps’.

It dies in HTML::Mason::Request::alter_superclass(), called from
RT::Interface::Web::Request.

When you install HTML::Mason, does it run and pass all its tests?

Yes, all except live tests and CHI. If it was an issue with
HTML::Mason I’d expect 15-subclass.t to fail (as it calls the same
alter_superclass method).

To follow up my own email, this does seem like a HTML::Mason bug as I
can reproduce the SIGSEGV on two machines running perl 5.10.0 and
HTML::Mason 1.39 with the following test script, yet it runs fine on
perl 5.8.8 + HTML::Mason 1.39.

package TestRequest;
use strict;
use warnings;

use base ‘HTML::Mason::Request’;
use HTML::Mason::CGIHandler;

sub foo {
my $class = shift;
$class->alter_superclass( ‘HTML::Mason::Request::CGI’ );
$class->SUPER::new(@_);
}

package main;
my $bar = TestRequest->foo();


#19

I think this has been fixed in RC1 jesse released several days ago.On Wed, May 21, 2008 at 1:01 PM, Tom Lanyon tom@netspot.com.au wrote:

On 20/05/2008, at 5:42 PM, Tom Lanyon wrote:

On 20/05/2008, at 2:05 PM, Jesse Vincent wrote:

Jesse

Jesse,

It seg faults for me on a dev box, RedHat Enterprise Linux 5 with
Perl 5.10.0. This box was successfully running 3.6.6 with no
issues and only had a few dependencies which needed upgrading to
pass a 3.7.85 ‘make testdeps’.

It dies in HTML::Mason::Request::alter_superclass(), called from
RT::Interface::Web::Request.

When you install HTML::Mason, does it run and pass all its tests?

Yes, all except live tests and CHI. If it was an issue with
HTML::Mason I’d expect 15-subclass.t to fail (as it calls the same
alter_superclass method).

To follow up my own email, this does seem like a HTML::Mason bug as I
can reproduce the SIGSEGV on two machines running perl 5.10.0 and
HTML::Mason 1.39 with the following test script, yet it runs fine on
perl 5.8.8 + HTML::Mason 1.39.

package TestRequest;
use strict;
use warnings;

use base ‘HTML::Mason::Request’;
use HTML::Mason::CGIHandler;

sub foo {
my $class = shift;
$class->alter_superclass( ‘HTML::Mason::Request::CGI’ );
$class->SUPER::new(@_);
}

package main;
my $bar = TestRequest->foo();


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.


#20

I think this has been fixed in RC1 jesse released several days ago.

Fantastic! Thanks guys, 3.8.0rc2 now works with perl 5.10.0.

Regards,
Tom