Skip site navigation (1) Skip section navigation (2)

Re: code.pgadmin.org broken?

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: code.pgadmin.org broken?
Date: 2012-06-17 14:29:07
Message-ID: 1339943347.2027.14.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgadmin-hackers
On Sun, 2012-06-17 at 22:19 +0800, Magnus Hagander wrote:
> On Sun, Jun 17, 2012 at 10:13 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
> > Hi there,
> >
> > The trac instance on code.pgadmin.org seems utterly broken:
> >
> > <class 'locale.Error'>  Python 2.6.6: /usr/bin/python
> > Sun Jun 17 14:12:42 2012
> >
> > A problem occurred in a Python script. Here is the sequence of function
> > calls leading up to the error, in the order they occurred.
> >
> > etc etc
> >
> > Have you done a Python update?
> >
> 
> No. I had patched the *DNS* package.
> 

Hmmm, /me trying to understand how patching the DNS package could have
that kind of effect.

> restarting the webserver fixed it. Sorry about that, and thanks for
> pointing it out.
> 

Thanks a lot.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com


In response to

pgadmin-hackers by date

Next:From: pgAdmin TracDate: 2012-06-17 14:33:33
Subject: [pgAdmin III] #364: Make good use of new SQL functions pg_backup_in_progress() and pg_backup_start_time()
Previous:From: Magnus HaganderDate: 2012-06-17 14:19:15
Subject: Re: code.pgadmin.org broken?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group