Re: severe CSS and JS problems with ZMS latest

Am 31.01.2011 um 11:21 schrieb sascha.gottfried:

> Hi Diez,
>
> you said you forgot passing parameter '-i' the first time. But since  
> version 0.6c7 of easy_install this is the default parameter (you  
> installed 0.6c11 according to ZMS install instructions). Check this  
> here - (http://peak.telecommunity.com/DevCenter/EasyInstall#command-line-options 
> ) .

What do you mean by "default"? There has always been an implicit  
package index of course. But the explicit index one must use for  
installing zope is of course not a default.

>
> That means you invoked the same command the first and the second  
> time. Something else must have been the difference between your  
> buggy ZMS the first time and a smoothly running ZMS the second time.


Nope. I have confirmed that both on OSX and Ubuntu 10.10, passing "-i http://download.zope.org/Zope2/index/2.13.2 
" was the key.

>
> Dear Diez, please investigate this issue to find out, what went  
> wrong. Others must be enabled to recognize a system misconfigured  
> during installation. If there is a bug in newer Zope versions that  
> concerns running the latest ZMS version, please let us know.

Well, the difference is somewhere in this list. I compiled it using my  
virtual environment manager:

(zope_pypi)mac-dir:tmp deets$ python2.7 vem/manager.py compare zope213  
zope_pypi -i

manuel-1.1.1-py2.7.egg                                 |
                                                        | manuel-1.4.1- 
py2.7.egg
mechanize-0.2.3-py2.7.egg                              |
                                                        |  
mechanize-0.2.4-py2.7.egg
pytz-2010l-py2.7.egg                                   |
                                                        | pytz-2010o- 
py2.7.egg
zope.browserresource-3.10.3-py2.7.egg                  |
                                                        |  
zope.browserresource-3.12.0-py2.7.egg
                                                        |  
zope.component-3.10.0-py2.7.egg
zope.component-3.9.5-py2.7.egg                         |
zope.container-3.11.2-py2.7-macosx-10.5-fat3.egg       |
                                                        |  
zope.container-3.12.0-py2.7-macosx-10.5-fat3.egg
zope.publisher-3.12.4-py2.7.egg                        |
                                                        |  
zope.publisher-3.12.6-py2.7.egg
zope.schema-3.7.0-py2.7.egg                            |
                                                        |  
zope.schema-3.7.1-py2.7.egg
zope.security-3.7.4-py2.7-macosx-10.5-fat3.egg         |
                                                        |  
zope.security-3.8.0-py2.7-macosx-10.5-fat3.egg
zope.structuredtext-3.5.0-py2.7.egg                    |
                                                        |  
zope.structuredtext-3.5.1-py2.7.egg
zope.testbrowser-3.10.3-py2.7.egg                      |
                                                        |  
zope.testbrowser-3.11.1-py2.7.egg
                                                        |  
zope.testing-3.10.2-py2.7.egg
zope.testing-3.9.4-py2.7.egg                           |
                                                        |  
zope.testrunner-4.0.0-py2.7.egg
zope.traversing-3.13-py2.7.egg                         |
                                                        |  
zope.traversing-3.13.1-py2.7.egg

The left side are the working virtualenvs packages, the right side the  
ones you get if you install from PyPI only, and only those packages  
that actually differ in the version are shown. As you can see, there  
are quite a few differences there. I can only speculate about which is  
the culprit.


Diez