Hi Joe, Unfortunately, the steps to upgrade from 1.1-RC1 to 1.1-RC2 using packages have not yet been narrowed now. In fact, the packages need to be upgraded to properly support upgrades.
That's why I have not pushed 1.1-RC2 to my ppa yet. From your log, it looks like Django was not installed in the newly created virtualenv (or maybe it was not even created properly!). My only suggestion would be to backup the existing data (postgres tables and geoserver data dir, as well as custom /etc/geonode files) either manually or with a script [1] and then doing: sudo apt-get purge geonode sudo apt-get install geonode Sorry for the current messy situation, this lack of a clear upgrade path is one of the reasons the 1.1-final release has been delayed. If anyone wants to take the lead at fixing the debian installers to properly support upgrades I can provide the needed guidance. Regards, Ariel. [1] https://github.com/jmwenda/geonode-backup On Wed, Dec 14, 2011 at 9:16 PM, Joe Larson <[email protected]> wrote: > I'm on Ubuntu 10.04 and decided to upgrade/migrate from version > 1.1+RC1-ariel6 to 1.1RC2. I did this by removing the repo entry from > /etc/apt/sources.list.d/ and adding ppa:geonode/release with > add-apt-repository. And then I upgraded with apt-get update/upgrade. Before > I describe the rest - maybe this is a good point to ask (which I should > have done first) - is this even a suggestion migration method? If not, > hopefully others can learn from me. > > During the upgrade I was prompted and kept my local_settings.py (and, *I > think* the web.xml files from a geoserver and a geonetwork folder). Besides > this it seemed to go smoothly, I don't think I can check any kind of > (install) log to post. But when I loaded the page - I got a 500 error. My > catalina.out tomcat6 log didn't show anything obvious to me - if it would > be helpful to post for anyone, let me know. Wondering how else I should > troubleshoot this… > > When I ran `geonode help`: > > Traceback (most recent call last): > File "/var/lib/geonode/bin/django-admin.py", line 2, in <module> > from django.core import management > ImportError: No module named django.core > > So maybe this has something to do with geonode.wsgi or a django env. var. > setting? I'm reaching here…hence the post to the list. Hope I didn't > totally blow it :-S I'll also be hovering in IRC as larso ~joe
