UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when
upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out
solutions for some of you, but not all.
I've spent a lot of time trying to figure out solutions, find the
common
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading to
1.7 (or, in some cases, 1.6). We've managed to figure out solutions for
some of you, but not all.
I've spent a lot of time trying to figure out solutions, find the common
cases, and figure out
database upgrade issues before when upgrading to
1.7 (or, in some cases, 1.6). We've managed to figure out solutions for
some of you, but not all.
I've spent a lot of time trying to figure out solutions, find the common
cases, and figure out a fix. Today, I have one that should fix
try it again on a pristine 1.5.5 database.
--Steve
On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading to
1.7 (or, in some cases, 1.6). We've managed to figure out solutions for
some
2013 19:08:48 +
I may try it again on a pristine 1.5.5 database.
--Steve
On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading to 1.7
(or, in some cases, 1.6). We've managed
-packages/webkit-1.0',
'/usr/lib/python2.6/site-packages']
Server time:Fri, 1 Mar 2013 19:08:48 +
I may try it again on a pristine 1.5.5 database.
--Steve
On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade
: Fri, 1 Mar 2013 19:08:48 +
I may try it again on a pristine 1.5.5 database.
--Steve
On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading to
1.7 (or, in some cases, 1.6
, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading
to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for
some of you, but not all.
I've spent a lot of time trying to figure out
/python2.6/site-packages']
Server time:Fri, 1 Mar 2013 19:08:48 +
I may try it again on a pristine 1.5.5 database.
--Steve
On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading
AM UTC-8, Christian Hammond
wrote:
Hi everyone,
So some of you have hit database upgrade issues before when upgrading
to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions
for
some of you, but not all.
I've spent a lot of time trying to figure out solutions, find
Hi everyone,
So some of you have hit database upgrade issues before when upgrading to 1.7
(or, in some cases, 1.6). We've managed to figure out solutions for some of
you, but not all.
I've spent a lot of time trying to figure out solutions, find the common cases,
and figure out a fix. Today
Hi guys,
I wanted to condense the three active threads on database upgrade issues.
The things you all have in common is that you're upgrading from older
versions using an older Django Evolution that all had a bug causing blank
hinted schema evolutions, which could cause problems when upgrading
Hi Christian,
Here is what the output for the version
Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
[GCC 4.5.2] on linux2
Type help, copyright, credits or license for more information.
(InteractiveConsole)
from django_evolution.models import Version
print Version.objects.all()
[Version:
Upon further testing, it seems something has changed with this release and
LDAP authentication.
I was able to log into RB with a local user, however all LDAP users can not
log in. Do you know what has changed with the LDAP backend authentication?
The RB log shows the following message
14 matches
Mail list logo
