Re: [Setup] buildout UnknownExtra error
On Wed, Nov 18, 2009 at 09:44, lovis j.s...@fz-juelich.de wrote: Vitaliy Podoba-2 wrote: I got the same problem while re-running my old 3.0.6 plone buildout. Seems like problem is in a newly updated zope2instance recipe (4.0a1) at pypi. Adding prefer-final = true hi vitaliy, thank you for your reply. this is a solution for my problem, too. gruss juergen -- View this message in context: http://n2.nabble.com/buildout-UnknownExtra-error-tp4017714p4024161.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. ___ Setup mailing list Setup@lists.plone.org http://lists.plone.org/mailman/listinfo/setup Please do yourself a favor and pin all your eggs. You can get a list of versions with dumppickedversions. You can ensure that your production environment has only picked versions by setting that option I mentioned earlier. prefer-final does not solve the root cause of your problem. Your buildout did not break because it installed beta software by default, your buildout broke because you do not define which version of the software you want to use. As soon as the recipe has a stable 4.0 release, you will have the same problems as before! dumppickedversions will only be able to create a list of good working versions if you have a working buildout. So if you wait until your buildouts break again, you will have a lot of work. If you create all version pinnings, you might help others in the near future if you post your picked versions here. There is afaik no list of stable versions that work with plone 3.1.x Best regards, Patrick ___ Setup mailing list Setup@lists.plone.org http://lists.plone.org/mailman/listinfo/setup
Re: [Setup] buildout UnknownExtra error
Vitaliy Podoba-2 wrote: Hi lovis, I got the same problem while re-running my old 3.0.6 plone buildout. Seems like problem is in a newly updated zope2instance recipe (4.0a1) at pypi. Adding prefer-final = true to my [buildout] section made my buildout run with old stable version of zope2instance recipe thus w/o any issues. Relevant post: http://www.netsight.co.uk/blog/2009/11/17/configuring- buildout-to-prefer-stable-releases Hope it helps, /Vitaliy Podoba ___ Setup mailing list Setup@lists.plone.org http://lists.plone.org/mailman/listinfo/setup hi vitaliy, thank you for your reply. this is a solution for my problem, too. gruss juergen -- View this message in context: http://n2.nabble.com/buildout-UnknownExtra-error-tp4017714p4024161.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. ___ Setup mailing list Setup@lists.plone.org http://lists.plone.org/mailman/listinfo/setup
[Setup] buildout UnknownExtra error
hi,
yesterday i tried to buildout my project and i got a UnknownExtra error (see
below). all approaches (remove fake-eggs, devel-eggs, ..., or use plone 3.3,
...) to fix the problem are dont help. my plone version is 3.1. I have two
systems, one for develpment and one deployment (with a zeo server), on both
systems is the error equivalent.
(the first error message was that setuptools have to upgrade to version
0.6c11)
i very grateful for any help.
here are my buildout.cfg
[buildout]
parts =
plone
zope2
productdistros
instance
zopepy
omelette
extensions = buildout.eggtractor
tractor-src-directory = src
tractor-target-parts = instance
# Add additional egg download sources here. dist.plone.org contains archives
# of Plone packages.
find-links =
http://download.zope.org/ppix
http://dist.plone.org
http://download.zope.org/distribution
http://effbot.org/downloads
# Add additional eggs here
# elementtree is required by Plone
eggs =
elementtree
#plone.reload
Products.ATVocabularyManager
simplon.plone.ldap
Products.ATReferenceBrowserWidget
icg.policy
icg.TerenoTheme
collective.uploadify
Products.PloneFlashUpload
Products.CompoundField
#atreal.massloader
Products.TALESField
#collective.JUpload
#TerenoSkin
#Products.LDAPUserFolder
#Products.LDAPMultiPlugins
#Products.PloneLDAP
#simplon.plone.ldap
# Reference any eggs you are developing here, one per line
# e.g.: develop = src/my.package
develop =
src/icg.policy
src/icg.TerenoTheme
# src/TerenoSkin
[plone]
recipe = plone.recipe.plone=3.1.1,3.2dev
#recipe = plone.recipe.plone=3.2
#new:
eggs=
products=
zope2-url=
[zope2]
recipe = plone.recipe.zope2install
url = ${plone:zope2-url}
fake-zope-eggs = true
additional-fake-eggs =
#new:
location=./parts/zope2
# ZConfig
# ZODB3
# pytz
# Use this section to download additional old-style products.
# List any number of URLs for product tarballs under URLs (separate
# with whitespace, or break over several lines, with subsequent lines
# indented). If any archives contain several products inside a top-level
# directory, list the archive file name (i.e. the last part of the URL,
# normally with a .tar.gz suffix or similar) under 'nested-packages'.
# If any archives extract to a product directory with a version suffix, list
# the archive name under 'version-suffix-packages'.
[productdistros]
recipe = plone.recipe.distros
urls =
nested-packages =
version-suffix-packages =
[instance]
#this on approach to fix the problem
recipe = plone.recipe.zope2instance=2.12.0b4dev
zope2-location = ${zope2:location}
user = XXX
http-address =
debug-mode = on
verbose-security = on
# If you want Zope to know about any additional eggs, list them here.
# This should include any development eggs you listed in develop-eggs above,
# e.g. eggs = ${buildout:eggs} ${plone:eggs} my.package
eggs =
${buildout:eggs}
${plone:eggs}
# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =
plone.reload
Products.ATVocabularyManager
simplon.plone.ldap
icg.policy
collective.uploadify
#Products.LDAPUserFolder
#Products.LDAPMultiPlugins
#Products.PloneLDAP
#simplon.plone.ldap
products =
${buildout:directory}/products
${productdistros:location}
#new
#${plone:products}
../
[zopepy]
recipe = zc.recipe.egg
eggs = ${instance:eggs}
interpreter = zopepy
extra-paths = ${zope2:location}/lib/python
scripts = zopepy
[omelette]
recipe = collective.recipe.omelette
eggs = ${instance:eggs}
products =
${instance:products}
../
[zopeskel]
recipe = zc.recipe.egg
eggs =
PasteScript
ZopeSkel
# Automatically add eggs to PyDev project path
[pydev]
recipe = pb.recipes.pydev
pydevproject_path =${buildout:directory}/.pydevproject
eggs = ${instance:eggs}
extra_paths = ${zope2:location}/lib/python/
* here are the output from buildout ***
Installing 'buildout.eggtractor'.
We have the best distribution that satisfies 'buildout.eggtractor'.
Picked: buildout.eggtractor = 0.6
Installing 'plone.recipe.distros #=3.1.1,3.2dev'.
We have the best distribution that satisfies 'plone.recipe.distros'.
Picked: plone.recipe.distros = 1.5
Installing 'plone.recipe.zope2install'.
We have the best distribution that satisfies 'plone.recipe.zope2install'.
Picked: plone.recipe.zope2install = 3.2
Installing 'plone.recipe.zope2instance=2.12.0b4dev'.
We have the best distribution that satisfies
'plone.recipe.zope2instance=2.12.0b4dev'.
Picked: plone.recipe.zope2instance = 4.0a1
Getting required 'Zope2=2.12.1'
required by plone.recipe.zope2instance 4.0a1.
We have the best distribution that satisfies 'Zope2=2.12.1'.
Picked: Zope2 = 2.12.1
Getting required 'zc.recipe.egg'
required by plone.recipe.zope2instance 4.0a1.
We have the
Re: [Setup] buildout UnknownExtra error
On Tue, Nov 17, 2009 at 11:22, lovis j.s...@fz-juelich.de wrote: hi, yesterday i tried to buildout my project and i got a UnknownExtra error (see below). all approaches (remove fake-eggs, devel-eggs, ..., or use plone 3.3, ...) to fix the problem are dont help. my plone version is 3.1. I have two systems, one for develpment and one deployment (with a zeo server), on both systems is the error equivalent. (the first error message was that setuptools have to upgrade to version 0.6c11) i very grateful for any help. here are my buildout.cfg [...] recipe = plone.recipe.zope2instance=2.12.0b4dev Why do you pin plone.recipe.zope2instance to this version? This tries to install zope 2.12. Thats not a good idea if you intent to run plone3 and plone4 is not yet stable. Depending on what you are trying to accomplish, the answers are different. So what are you trying? Do you want to upgrade to a newer plone version, or do you have buildout that was working and isn't any longer and you just want it to run again? Best regards, Patrick ___ Setup mailing list Setup@lists.plone.org http://lists.plone.org/mailman/listinfo/setup
Re: [Setup] buildout UnknownExtra error
Patrick Gerken wrote:
On Tue, Nov 17, 2009 at 11:22, lovis j.s...@fz-juelich.de wrote:
hi,
yesterday i tried to buildout my project and i got a UnknownExtra error
(see
below). all approaches (remove fake-eggs, devel-eggs, ..., or use plone
3.3,
...) to fix the problem are dont help. my plone version is 3.1. I have
two
systems, one for develpment and one deployment (with a zeo server), on
both
systems is the error equivalent.
(the first error message was that setuptools have to upgrade to version
0.6c11)
i very grateful for any help.
here are my buildout.cfg
[...]
recipe = plone.recipe.zope2instance=2.12.0b4dev
Why do you pin plone.recipe.zope2instance to this version?
This tries to install zope 2.12. Thats not a good idea if you intent
to run plone3
and plone4 is not yet stable.
Depending on what you are trying to accomplish, the answers are different.
So what are you trying? Do you want to upgrade to a newer plone version,
or do you have buildout that was working and isn't any longer and you just
want
it to run again?
Best regards,
Patrick
___
Setup mailing list
Setup@lists.plone.org
http://lists.plone.org/mailman/listinfo/setup
hi patrick,
first thank you for your reply.
i just want to run again my buildout. (no upgrade)
recipe = plone.recipe.zope2instance=2.12.0b4dev
this line was only a approach to fix the problem.
without the condition the same error occures.
i have modiefied my buidlout.cfg to ensure that zope 2.10.6-final (this is
the version that is installed yet) will be installed. but it seems that even
with the conditions (=2.10.6-final see attached buildout.cfg), buildout
installs zope 2.12 (see attached buildout output)
i don't know if i do any errors in the buildout.cfg with the conditions or
url (zope-url). also i don't know on which statement i have to append the
condition (on zope2install, zope2instance or i have to specify the zope-url)
i have conditioned Products.CMFDefault (Products.CMFDefault=2.1.2) because
a new version of Products.CMFDefault (2.2.0-alpha ) is available and Zope
dependency is increased to version 2.12.0b3dev
thank you for your help
gruss
juergen
here is the new buildout.cfg
[buildout]
parts =
plone
zope2
productdistros
instance
zopepy
omelette
extensions = buildout.eggtractor
tractor-src-directory = src
tractor-target-parts = instance
# Add additional egg download sources here. dist.plone.org contains archives
# of Plone packages.
find-links =
http://download.zope.org/ppix
http://dist.plone.org
http://download.zope.org/distribution
http://effbot.org/downloads
# Add additional eggs here
# elementtree is required by Plone
eggs =
elementtree
#plone.reload
#Products.ATVocabularyManager
#simplon.plone.ldap
Products.ATReferenceBrowserWidget
icg.policy
icg.TerenoTheme
collective.uploadify
Products.PloneFlashUpload
Products.CompoundField
#atreal.massloader
Products.TALESField
#collective.JUpload
#TerenoSkin
#Products.LDAPUserFolder
#Products.LDAPMultiPlugins
#Products.PloneLDAP
#simplon.plone.ldap
Products.CMFDefault=2.1.2
# Reference any eggs you are developing here, one per line
# e.g.: develop = src/my.package
develop =
src/icg.policy
src/icg.TerenoTheme
[plone]
recipe = plone.recipe.plone=3.1.1,3.2dev
#recipe = plone.recipe.plone=3.2
[zope2]
recipe = plone.recipe.zope2install2.10.6-final
#url = ${plone:zope2-url}
url = http://www.zope.org/Products/Zope/2.10.6/Zope-2.10.6-final.tgz
fake-zope-eggs = true
additional-fake-eggs =
#new:
#location=./parts/zope2
# ZConfig
# ZODB3
# pytz
# Use this section to download additional old-style products.
# List any number of URLs for product tarballs under URLs (separate
# with whitespace, or break over several lines, with subsequent lines
# indented). If any archives contain several products inside a top-level
# directory, list the archive file name (i.e. the last part of the URL,
# normally with a .tar.gz suffix or similar) under 'nested-packages'.
# If any archives extract to a product directory with a version suffix, list
# the archive name under 'version-suffix-packages'.
[productdistros]
recipe = plone.recipe.distros
urls =
nested-packages =
version-suffix-packages =
[instance]
recipe = plone.recipe.zope2instance2.10.6-final
zope2-location = ${zope2:location}
user = XXX
http-address = XXXx
debug-mode = on
verbose-security = on
# If you want Zope to know about any additional eggs, list them here.
# This should include any development eggs you listed in develop-eggs above,
# e.g. eggs = ${buildout:eggs} ${plone:eggs} my.package
eggs =
${buildout:eggs}
${plone:eggs}
# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =
plone.reload
Re: [Setup] buildout UnknownExtra error
On Tue, Nov 17, 2009 at 16:24, lovis j.s...@fz-juelich.de wrote: hi patrick, first thank you for your reply. i just want to run again my buildout. (no upgrade) In that case, start using the option allow-picked-versions = False at least for your deployment configuration Your buildout will then fail, telling you that it picked some package at version X That means, that you did not specify a version in your buildout config, and because you forbid buildout to choose versions on its own, it will not build. So next thing to do is to create a separate cfg with version information and let your buildout.cfg extend from that. You might call it picked-versions.cfg and add all versions that are not pinned yet. If you would still have a running buildout config, you could now experiment with the buildout dumppickedversions that would give you all versions ready to dump into a picked-versions.cfg http://pypi.python.org/pypi/buildout.dumppickedversions/0.4 Since this is not possible any longer, try to regenerate that list with a small shell script and your egg directory on your deployment environment. I am afraid to say that this might not be enough for fixing everything, but that should help you to straighten things out. Things get easier with plone 3.2, where plone provides a list of good versions under an url such as http://dist.plone.org/release/3.2/versions.cfg That you could add to your buildout.cfg, but for plone 3.1 this does not exist as far as I know. this versions.cfg might still be a start, since you can be sure that packages should have a higher version than specified there. You might get faster help on irc.freenode.org btw. #zope.de for example. Best regards and good luck! Patrick ___ Setup mailing list Setup@lists.plone.org http://lists.plone.org/mailman/listinfo/setup
