Bug/problem in 2.0.14 with PerlFreshRestart!

Hi!

I installed last weekend, 2.0.14 and Mason1.1201 and get a lot
of troubles. The problem is that i couldn´t authentificate in
RT, if I turned off “PerlFreshRestart”.

I get the login mask, but after
submit, nothings happend, not even a message about incorrect
password/login

If I enable it, i come into trouble with my installation. I run two
independant RT installations on the machine. But when I turn on
"PerlFreshRestart" the second instance, shows an error message and in
the log I could read

This works in 2.0.13 with Mason 1.05. My quick solution was to downgrade
to Mason 1.0.5.

Something I don´t understand is that when I installed Mason1.1201
and run the CPAN-Shell and let me show with r all outdated modeules,
there was Mason::Apache::Handler, when I tried to force the install, the
CPAN module automically downgrades to Mason1.0.5

bye
Sven Sternberger Tel.: +49 (0) 40 8998 4397
Desy Email: sven.sternberger@desy.de
Notkestr. 85
D-22607 Hamburg

“SS” == Sven Sternberger sven.sternberger@desy.de writes:

SS> Something I don´t understand is that when I installed Mason1.1201
SS> and run the CPAN-Shell and let me show with r all outdated modeules,
SS> there was Mason::Apache::Handler, when I tried to force the install, the
SS> CPAN module automically downgrades to Mason1.0.5

If you look at the output of the “r” command, you’ll see the version
numbers. Numerically, the one in 1.05 is “newer” than the one in
1.1201. There is a discussion about this on the mason devel list.
There is no good solution today for it.

“SS” == Sven Sternberger sven.sternberger@desy.de writes:

SS> Something I don´t understand is that when I installed Mason1.1201
SS> and run the CPAN-Shell and let me show with r all outdated modeules,
SS> there was Mason::Apache::Handler, when I tried to force the install, the
SS> CPAN module automically downgrades to Mason1.0.5

If you look at the output of the “r” command, you’ll see the version
numbers. Numerically, the one in 1.05 is “newer” than the one in
1.1201. There is a discussion about this on the mason devel list.
There is no good solution today for it.

Apart from the Mason developers releasing the intended ‘1.12.01’, rather
than the broken version numbering ‘1.1201’. Theres a lot in a dot.

Regards,

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B             Operations/Security