Cool.  That brought it back.  Under versions, I now see this:

Zope Zope -1.-1.-1 

Thanks,
Chris




Ian McCracken <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
01/29/2007 12:33 PM
Please respond to
General discussion of using zenoss system <[email protected]>


To
General discussion of using zenoss system <[email protected]>
cc

Subject
Re: [zenoss-users] Trunk migrated to Zope 2.10.1






>From Eric Newton: 

I think this is the minimal conversion steps (worked for me): 

   $ zenoss stop 
   $ cd /your/inst/directory 
   $ rm -rf build/Zope* 
   $ svn update 
   $ rm -rf $ZENHOME/Products/Five 
   $ make zope-install 
   $ zenoss start 


Chris Friedline wrote: 

/usr/local/zenoss/Products$ svn update 
At revision 3957. 

/usr/local/zenoss/Products$ ls -l | grep Five 
drwxr-xr-x  8 zenoss zenoss  4096 2007-01-29 11:38 Five 

Looks like the Five is still there.  Any other thoughts? 

Thanks, 
Chris 


Ian McCracken <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED] 
01/29/2007 12:24 PM 

Please respond to
General discussion of using zenoss system <[email protected]>



To
General discussion of using zenoss system <[email protected]> 
cc

Subject
Re: [zenoss-users] Trunk migrated to Zope 2.10.1








Chris,

For some reason, your Products directory didn't update. Do an svn up; it 
should delete the Five directory (we're using the version of Five bundled 
with Zope).

Ian

Chris Friedline wrote: 

After an upgrade, the following occurs in zenbuild.log 

creating events database using zenevent build... 
creating database 
loading schema 
ERROR 1359 (HY000) at line 80: Trigger already exists 
loading stored procedures 
events database created and loaded 
Traceback (most recent call last): 
 File "/usr/local/zenoss/Products/ZenModel/zenbuild.py", line 29, in ? 
   from Products.ZenUtils import Security 
 File "/usr/local/zenoss/Products/ZenUtils/__init__.py", line 1, in ? 
   from Products.CMFCore.DirectoryView import registerDirectory 
 File "/usr/local/zenoss/Products/CMFCore/__init__.py", line 20, in ? 
   import PortalObject, PortalContent, PortalFolder 
 File "/usr/local/zenoss/Products/CMFCore/PortalObject.py", line 22, in ? 
   from PortalFolder import PortalFolder 
 File "/usr/local/zenoss/Products/CMFCore/PortalFolder.py", line 31, in ? 
   from CMFCatalogAware import CMFCatalogAware 
 File "/usr/local/zenoss/Products/CMFCore/CMFCatalogAware.py", line 28, in 
? 
   from utils import _dtmldir 
 File "/usr/local/zenoss/Products/CMFCore/utils.py", line 47, in ? 
   from Products.PageTemplates.Expressions import getEngine 
 File 
"/usr/local/zenoss/lib/python/Products/PageTemplates/Expressions.py", line 
34, in ? 
   from Products.Five.browser.providerexpression import 
Z2ProviderExpression 
 File "/usr/local/zenoss/Products/ZenModel/__init__.py", line 25, in ? 
   import os 
 File "/usr/local/zenoss/Products/Five/monkey.py", line 26, in monkeyPatch 

 File "/usr/local/zenoss/Products/Five/i18n.py", line 22, in ? 
ImportError: cannot import name MessageID 

Thanks, 
Chris 


Ian McCracken <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED] 
01/29/2007 10:57 AM 

Please respond to
General discussion of using zenoss system <[email protected]>



To
General discussion of using zenoss system <[email protected]> 
cc

Subject
[zenoss-users] Trunk migrated to Zope 2.10.1










All,

The trunk has been migrated to Zope 2.10.1. This will require a simple 
reinstallation for those of you running bleeding-edge Zenoss. Briefly:

1.        Go to your zenossinst directory and 'svn up'; if you've deleted 
the directory, check it out again with: 
'svn co http://dev.zenoss.org/svn/trunk/inst zenossinst'. 
2.        Run zenossinst/install.sh. 
That's it!_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users 

NOTE: The information contained in this message may be privileged and 
confidential and protected from disclosure. If the reader of this message 
is not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please 
notify us immediately by replying to the message and deleting it from your 
computer.
--------------------------------------
VCU Health System
http://www.vcuhealth.org 


_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users 
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users 

NOTE: The information contained in this message may be privileged and 
confidential and protected from disclosure. If the reader of this message 
is not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please 
notify us immediately by replying to the message and deleting it from your 
computer.
--------------------------------------
VCU Health System
http://www.vcuhealth.org 


_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

NOTE: The information contained in this message may be privileged and 
confidential and protected from disclosure. If the reader of this message 
is not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please 
notify us immediately by replying to the message and deleting it from your 
computer.
--------------------------------------
VCU Health System
http://www.vcuhealth.org
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to