<div dir="ltr">I could do just migrate and the db was setup correctly.</div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-17 16:43 GMT+02:00 Ariel Nunez <span dir="ltr"><<a href="mailto:ingenieroariel@gmail.com" target="_blank">ingenieroariel@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Paolo, the way to do it is to first do a migrate auth and after that you can do a regular syncdb. <div><br></div><div>python manage.py migrate auth</div><div>python manage.py syncdb</div><div><br></div><div>Not sure if that can be avoided - it seems a bit weird to me that a regular syncdb would not work.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-a</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 17, 2016 at 9:40 AM, Paolo Corti <span dir="ltr"><<a href="mailto:pcorti@gmail.com" target="_blank">pcorti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It seems that from Django 1.8 it is needed to run migrate with the<br>
--fake-initial settings<br>
(<a href="http://stackoverflow.com/questions/29760817/how-can-i-resolve-django-content-type-already-exists" rel="noreferrer" target="_blank">http://stackoverflow.com/questions/29760817/how-can-i-resolve-django-content-type-already-exists</a>)<br>
<br>
Though, I am now getting a different error:<br>
<br>
Applying layers.0001_initial...Traceback (most recent call last):<br>
...<br>
django.db.utils.ProgrammingError: relation "layers_attribute" already exists<br>
<span><font color="#888888"><br>
p<br>
</font></span><div><div><br>
On Fri, Jun 17, 2016 at 10:34 AM, Paolo Corti <<a href="mailto:pcorti@gmail.com" target="_blank">pcorti@gmail.com</a>> wrote:<br>
> Hi developers<br>
><br>
> I am trying to install geonode from master (I haven't done this since<br>
> 2.4 was released). I am wondering which is the way to setup a<br>
> developer geonode instance.<br>
><br>
> Once it was possible, following this instructions [1], to generate an<br>
> environment using paver setup, which was taking care of the database<br>
> initial sync.<br>
> Now setup just set geoserver.<br>
><br>
> If I try to create the database, I get this error:<br>
><br>
>   Applying contenttypes.0001_initial...Traceback (most recent call last):<br>
><br>
>   File "./manage.py", line 29, in <module><br>
><br>
>     execute_from_command_line(sys.argv)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/core/management/__init__.py",<br>
> line 354, in execute_from_command_line<br>
><br>
>     utility.execute()<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/core/management/__init__.py",<br>
> line 346, in execute<br>
><br>
>     self.fetch_command(subcommand).run_from_argv(self.argv)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/core/management/base.py",<br>
> line 394, in run_from_argv<br>
><br>
>     self.execute(*args, **cmd_options)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/core/management/base.py",<br>
> line 445, in execute<br>
><br>
>     output = self.handle(*args, **options)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/core/management/commands/migrate.py",<br>
> line 222, in handle<br>
><br>
>     executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/migrations/executor.py",<br>
> line 110, in migrate<br>
><br>
>     self.apply_migration(states[migration], migration, fake=fake,<br>
> fake_initial=fake_initial)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/migrations/executor.py",<br>
> line 148, in apply_migration<br>
><br>
>     state = migration.apply(state, schema_editor)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/migrations/migration.py",<br>
> line 115, in apply<br>
><br>
>     operation.database_forwards(self.app_label, schema_editor,<br>
> old_state, project_state)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/migrations/operations/models.py",<br>
> line 59, in database_forwards<br>
><br>
>     schema_editor.create_model(model)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/backends/base/schema.py",<br>
> line 286, in create_model<br>
><br>
>     self.execute(sql, params or None)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/backends/base/schema.py",<br>
> line 111, in execute<br>
><br>
>     cursor.execute(sql, params)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/backends/utils.py",<br>
> line 79, in execute<br>
><br>
>     return super(CursorDebugWrapper, self).execute(sql, params)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/backends/utils.py",<br>
> line 64, in execute<br>
><br>
>     return self.cursor.execute(sql, params)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/utils.py",<br>
> line 98, in __exit__<br>
><br>
>     six.reraise(dj_exc_type, dj_exc_value, traceback)<br>
><br>
>   File "/home/vagrant/geonode/geonode/env/local/lib/python2.7/site-packages/django/db/backends/utils.py",<br>
> line 62, in execute<br>
><br>
>     return self.cursor.execute(sql)<br>
><br>
> django.db.utils.ProgrammingError: relation "django_content_type" already exists<br>
><br>
><br>
><br>
> I believe it is also important to always keep documentation updated.<br>
> thanks<br>
> p<br>
><br>
> [1] <a href="https://github.com/GeoNode/geonode" rel="noreferrer" target="_blank">https://github.com/GeoNode/geonode</a><br>
><br>
> --<br>
> Paolo Corti<br>
> Geospatial software developer<br>
> web: <a href="http://www.paolocorti.net" rel="noreferrer" target="_blank">http://www.paolocorti.net</a><br>
> twitter: @capooti<br>
> skype: capooti<br>
<br>
<br>
<br>
--<br>
Paolo Corti<br>
Geospatial software developer<br>
web: <a href="http://www.paolocorti.net" rel="noreferrer" target="_blank">http://www.paolocorti.net</a><br>
twitter: @capooti<br>
skype: capooti<br>
_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org" target="_blank">geonode-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Simone </div>
</div>