[GeoNode-users] database update error

Fri Jul 8 06:51:09 PDT 2016

Dear all,
can you please try again against the latest commits on geonode master?

Best Regards,
Alessio Fabiani.

==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272
mob:   +39 331 6233686

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---------------------------------------------------------------------

On Thu, Jul 7, 2016 at 4:10 PM, Angelos Tzotsos <gcpp.kalxas at gmail.com>
wrote:

> Hi,
>
> I had the same issue when installing GeoNode master on a clean Ubuntu
> Xenial.
> In order to fix it I had to apply the following migrations:
>
> python manage.py migrate layers
> python manage.py migrate documents
> python manage.py migrate actstream
> python manage.py migrate people
> python manage.py migrate admin
> python manage.py migrate guardian
> python manage.py migrate sessions
> python manage.py migrate sites
> python manage.py migrate auth
> python manage.py migrate tastypie
> python manage.py migrate maps
> python manage.py migrate contenttypes
> python manage.py migrate base
> python manage.py migrate upload
> python manage.py migrate groups
> python manage.py migrate services
> python manage.py migrate taggit
>
> Best,
> Angelos
>
>
> On 06/23/2016 11:55 AM, Simone Dalmasso wrote:
>
> Hi Eugenio,
>
> beware that the data model and django version is changed in master. This
> issue happens when using postgres as db and not sqllite. At the moment the
> way to create the new db is by doing
>
> manage.py migrate auth
>
> manage.py migrate sites
>
> manage.py migrate people
>
> manage.py migrate
>
> We will fix this in the future.
>
>
>
>
> 2016-06-23 10:27 GMT+02:00 Eugenio Trumpy <frippe12573 at hotmail.com> <frippe12573 at hotmail.com>:
>
>
> Hi all,
>
> today I was trying to update geonode from git (custom installation on
> ubuntu 14.04).
> I made a backup of the data from geonode and geonode_data db, then I
> created new DBs,
> and I run syncdb --noinput, but something seems not working:
>
> System check identified some issues:
>
> WARNINGS:
> account.EmailConfirmation.created: (fields.W161) Fixed default value
> provided.
>     HINT: It seems you set a fixed date / time / datetime value as default
> for this field. This may not be what you want. If you want to have the
> current date as default, use `django.utils.timezone.now`
> dialogos.Comment.ip_address: (fields.W900) IPAddressField has been
> deprecated. Support for it (except in historical migrations) will be
> removed in Django 1.9.
>     HINT: Use GenericIPAddressField instead.
> Operations to perform:
>   Synchronize unmigrated apps: tasks, dialogos, modeltranslation,
> django_extensions, polymorphic, agon_ratings, gis,
> pinax_theme_bootstrap_account, django_forms_bootstrap, catalogue, humanize,
> geoserver, announcements, storages, user_messages, mptt, friendlytagloader,
> staticfiles, geoexplorer, sitemaps, proxy, account, pinax_theme_bootstrap,
> pagination, autocomplete_light, messages, leaflet, api, avatar, social,
> security
>   Apply all migrations: layers, documents, actstream, people, admin,
> guardian, sessions, djcelery, sites, auth, tastypie, maps, contenttypes,
> base, upload, groups, services, taggit
> Synchronizing apps without migrations:
>   Creating tables...
>     Creating table account_account
>     Creating table account_signupcode
>     Creating table account_signupcodeextended
>     Creating table account_signupcoderesult
>     Creating table account_emailaddress
>     Creating table account_emailconfirmation
>     Creating table account_accountdeletion
>     Creating table avatar_avatar
>     Creating table dialogos_comment
>     Creating table agon_ratings_overallrating
>     Creating table agon_ratings_rating
>     Creating table announcements_announcement
>     Creating table announcements_dismissal
>     Creating table user_messages_thread
>     Creating table user_messages_userthread
>     Creating table user_messages_message
>     Running deferred SQL...
> Traceback (most recent call last):
>   File "manage.py", line 29, in <module>
>     execute_from_command_line(sys.argv)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 354, in execute_from_command_line
>     utility.execute()
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 346, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
> line 394, in run_from_argv
>     self.execute(*args, **cmd_options)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
> line 445, in execute
>     output = self.handle(*args, **options)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py",
> line 25, in handle
>     call_command("migrate", **options)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 120, in call_command
>     return command.execute(*args, **defaults)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
> line 445, in execute
>     output = self.handle(*args, **options)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
> line 179, in handle
>     created_models = self.sync_apps(connection,
> executor.loader.unmigrated_apps)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
> line 318, in sync_apps
>     cursor.execute(statement)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line
> 79, in execute
>     return super(CursorDebugWrapper, self).execute(sql, params)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line
> 64, in execute
>     return self.cursor.execute(sql, params)
>   File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line
> 98, in __exit__
>     six.reraise(dj_exc_type, dj_exc_value, traceback)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line
> 62, in execute
>     return self.cursor.execute(sql)
> django.db.utils.ProgrammingError: relation "people_profile" does not exist
>
> Of course I performed the update of the dbs after run git pull on geonode
> dir.
>
> Can you help me?
>
> Eugenio
>
> _______________________________________________
> geonode-users mailing listgeonode-users at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/geonode-users
>
>
>
> _______________________________________________
> geonode-users mailing listgeonode-users at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/geonode-users
>
>
>
> --
> Angelos Tzotsos, PhD
> OSGeo Charter Memberhttp://users.ntua.gr/tzotsos
>
>
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geonode-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20160708/e1d9f01f/attachment-0001.html>