ah, i see from http://www.buildout.org/docs/tutorial.html that since
zopeproject's buildout.cfg defaults to "newest=false", the "-n" option
is needed to update any modules. i need to learn buildout.
that fixed all conflicts and exceptions. now i see z3c, but no "Modules
and Subpackages" below it (unlike the many packages below zope and other
links), even tho i added z3c.form, z3c.formui, and z3c.formjs to the
setup.py file. maybe the z3c packages dont declare themselves to be
buildout did give this error several times:
Download error: unknown url type: svn -- Some packages may not be found!
but buildout claimed that it "Got" versions of each of the 3 packages i
specified (and several dependencies as well).
Michael Howitz wrote:
> Am 18.05.2009 um 17:05 schrieb John:
>> thanks michael. i did as you suggested, but buildout said:
> [snipped some error messages]
>> i dont really need to see z3c in apidoc, but if my general approach
>> of adding versions to resolve conflicts is wrong, i'd like to know
>> what i should do instead.
> There where several new versions of the zope packages which are not
> backwards compatible. Your approach is correct there are way too many
> new versions.
> If you did this:
>>> After running bin/zopeproject, edit proj/buildout.cfg, comment out
>>> the following line:
>>> extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg
> Then this is wrong:
>>> Run bin/buildout to install the new packages.
> You should run:
> bin/buildout -n
> to get all the new packages. Sorry, my fault.
> Yours sincerely,
Zope3-users mailing list