Hi-

These errors come from the sf version of manage.cgi.

Software error:
Can't use string ("<data_block><dt_assoc><item key=") as a symbol ref while 
"strict refs" in use at 
/usr/lib/perl5/site_perl/5.6.0/i686-linux/XML/Parser/Expat.pm line 456, 
<GEN12> line 2.
For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error 
message and the time and date of the error. Content-type: text/html

Software error:
Can't locate object method "ToLower" via package "main" at 
/usr/lib/perl5/5.6.0/utf8_heavy.pl line 30, <GEN12> line 2.
For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error 
message and the time and date of the error. Content-type: text/html


The first error was repeated two more times after the second, but there's 
no reason to duplicate it here.  I haven't made an attempt to fix these 
yet, since they appear to come from Perl modules, I'm guessing the modules 
don't like the way their functions are being called.

If anyone has already fixed these, what are the changes to make?  I looked 
in the dev-list archive and sf bug tracker, but couldn't find a 
solution.  I believe my Expat is pretty recent.


More broadly speaking, are you (OpenSRS developers/management) planning to 
put code into cvs on sf, or just use SourceForge for tarball releases?  I 
realize you are probably already set up with your own internal revision 
control system, so it might be a pain to check updates/changes in over at 
sf all the time (could you do it daily or weekly or automate it?) but what 
is the point of using sf and asking RSPs to try out the code and submit bug 
reports/fixes and contribute code, if we have to implement the fixes 
ourselves or wait for you to roll another tarball?

Currently it seems like you want to have two versions of the software - a 
lightweight "official version" and a fat "sf-version" - and that both are 
developed and maintained entirely by OpenSRS staff, though the fat version 
will contain some user-contributed code.  To me, the point of using sf and 
going with an open development model is that updates/changes/fixes can be 
available outside of a tarball release that the maintainers packaged.

I appreciate all the hard work you have done and commend you for making the 
step and commitment to getting set up on SourceForge, I'm just looking for 
clarification on how you intend to use it.

-Russ





Reply via email to