Login | Register
My pages Projects Community openCollabNet
Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Reply to message

* = Required fields
* Subject
* Body
Send reply to
Author (directly in email)
Please type the letters in the image above.

Original message

Author Roland Pope <rpope@jadeworld.com>
Full name Roland Pope <rpope@jadeworld.com>
Date 2004-11-16 15:43:54 PST
Message ----- Original Message -----
From: "Jack Neely" <jjneely at gmail dot com>
> There's a patch on the CVS list that will correct the tracebacks in
> regards to concatinating a tuple. I need to get off my lazy rear and
> make a new release with that patch in it.

I applied the following patch, installed the new version restarted httpd but
it still produced the same error saying "can only concatenate list (not
"tuple") to list"
--- trunk/current/src/xmlrpc.py 2004-10-19 03:15:12 UTC (rev 635)
+++ trunk/current/src/xmlrpc.py 2004-11-02 20:38:47 UTC (rev 636)
@@ -62,6 +62,7 @@
+ fd.write("<value​><array><​data>\n")

     # don't suck the entire data set into memory at once
     row = cursor.fetchone()
@@ -78,6 +79,7 @@

         row = cursor.fetchone()

+ fd.write("</data​></array>​</value>\n")
> As far as the dependancy problem does this include custom packages or
> just stock Whitebox? What exact packages?

The package in question was a custom build of Net_SSLeay.
 Doing the same update using the old 1.4 relase of current worked fine.
One thing I noted here, was that under current-1.4, there were no additional
dependancies required when I uninstalled the old perl-Net-SSLeay with
rpm --nodeps and installed the new perl-Net_SSLeay using 'up2date
When I tried the same thing under current-1.5, the 'up2date perl-Net_SSLeay'
installs 3 devel packages, which I know are required for the build, but not
for the install. So perhaps the dependancies stuff is mucked up on the
server, or maybe it relates to the 'tuple' error and the client is not
sucessfully downloading everything it needs becasue of this.
Anyway, let me know if there is anything else I can do to diagnose this

>Can you crank up the logging and post the Current's logs of that

See attached (This is the log created after the xmlrpc patch was applied).