Re: Problem in current svn TRUNK

2007-08-27 Thread Jeremy Dunck
On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote: ... > In any case, I listed the important packages in use on the system: > postgresql-server-8.2.4-5 > python-2.5.1-12 > python-psycopg2-2.0.6-2.5 > python-django-snapshot-5646-1 > > While these are all new packages, the only one which is "unstabl

Re: Problem in current svn TRUNK

2007-07-11 Thread Peter Nixon
On Wed 11 Jul 2007, Michael Radziej wrote: > Hi, > > you're using the alpha version of SuSE ... well ... there might very well > be a problem very deep in one of the libraries. The alpha releases aren't > very reliable. I'd suggest that you try it with another OS. Hi Michael While I agree that t

Re: Problem in current svn TRUNK

2007-07-11 Thread Peter Nixon
On Wed 11 Jul 2007, David Danier wrote: > > Basically django simply exists whenever it gets data based from > > postgresql.. anywhere. syncdb, inspecdb, /admin/ and everything else > > that access the db simple die/exit with an "Aborted" message.. > > As the changeset mentioned earlier was the uni

Re: Problem in current svn TRUNK

2007-07-11 Thread David Danier
> Basically django simply exists whenever it gets data based from postgresql.. > anywhere. syncdb, inspecdb, /admin/ and everything else that access the db > simple die/exit with an "Aborted" message.. As the changeset mentioned earlier was the unicode-merge: Is the datebase-encoding set to uni

Re: Problem in current svn TRUNK

2007-07-11 Thread Marijn Vriens
Yesterday I saw this bug as well when working with a new project and Django trunk. For me it went away when I changed settings.py from: DATABASE_ENGINE = 'postgresql_psycopg2' to DATABASE_ENGINE = 'postgresql' Regards, Marijn Vriens. On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > > > Hi

Re: Problem in current svn TRUNK

2007-07-11 Thread Peter Nixon
Hi Paul The problem was described (as much as it is possible to) in the initial mail to the users list as well as below in the test requested by Russell. Basically django simply exists whenever it gets data based from postgresql.. anywhere. syncdb, inspecdb, /admin/ and everything else that ac

Re: Problem in current svn TRUNK

2007-07-11 Thread Paul Bowsher
Peter, I may be blind, but I can't see anywhere you've actually specified what the bug is. What behaviour is exhibited? On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > > > Cross posted to -devel as this is definitely a bug > > On Wed 11 Jul 2007, Peter Nixon wrote: > > On Wed 11 Jul 2007

Re: Problem in current svn TRUNK

2007-07-11 Thread Peter Nixon
Cross posted to -devel as this is definitely a bug On Wed 11 Jul 2007, Peter Nixon wrote: > On Wed 11 Jul 2007, Russell Keith-Magee wrote: > > On 7/10/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > > > How can I debug this in a way that will provide the developers with > > > more usefull info?