Re: [gfsd] Quagga: Type errors

[Aaron S. Hawley]

I'm sorta talking to myself here, but I don't mind.

So it appears the synchronization of Quagga's source files between
savannah cvs repository and the main web server is either broke or has
been purposely disabled for the time being.

Is it because of technical difficulties (perhaps like those I had
mentioned last week and have quoted below).  I would be willing to help
get any problems fixed.  I'm willing to wait, too.  Just let me know.
/a

On Wed, 24 Mar 2004, Aaron S. Hawley wrote:

> I intalled a testbed (have others been successful?).
>
> Have the dependencies for Quagga changed since last year?  I use
> Debian/unstable.
>
> I have:
> Apache/1.3.29
> mod_python/2.7.10
> Python/2.1.3+
> MySQLdb/0.9.2 and 0.9.1
>
> MySQLdb seems to be giving the date-related values from the database as
> DateTime objects, which can't be implicitly converted to strings.  Here
> are some selected errors I'm seeing:
>
> ---
> File "/var/www/directory/display-entry.py", line 276, in display_entry
>     req.write (' released on ' + x[2] + '</td></tr>')
>
> TypeError: cannot add type "DateTime" to string
> ---
> File "/var/www/search/fsd-search.py", line 188, in print_result
>     req.write(font("black", "Updated: " + r['updated'], 2))
>
> TypeError: cannot add type "DateTime" to string
> ---
> File "/var/www/directory/display-entry.py", line 389, in display_entry
>     verify = verify + ' on ' + program['license_verified_on']
>
> TypeError: cannot add type "DateTime" to string
> ---
>
> and in places where the call str() was wrapped around these values (for
> example line 183 of display-entry.py), the date is displayed from here as
> "2004-03-23 00:00:00.00"
>
> what is www.gnu.org doing differently? i see it uses:
>
> Apache/1.3.26
> mod_python/2.7.8
> Python/2.1.3
>
> /a