установка collective.xdv на Plone3.3.2 FreeBSD 7.2

[alexvesna]

Ставил, как у Дениса написано.http://plone.org/documentation/tutorial/
advanced-xdv-theming/tutorial-all-pages

На bin/buildout выпадает с ошибкой о слишком большом количестве
аргументов в связи с установкой lxml. Может быть, у кого-нить есть
опыт на сей случай? Очень хочется попробовать xdv.

Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:139144: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'initThreadDictRef'
src/lxml/lxml.etree.c:139144:: Too many arguments.
src/lxml/lxml.etree.c:139145: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'initParserDict'
localhost# src/lxml/lxml.etree.c:139145: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'initParserDict'
src/lxml/lxml.etree.c:139145:: Too many arguments.
localhost# src/lxml/lxml.etree.c:139146: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'initXPathParserDict'
src/lxml/lxml.etree.c:139146:: Too many arguments.
src/lxml/lxml.etree.c:139147: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'initDocDict'
localhost# src/lxml/lxml.etree.c:139147: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'initDocDict'
src/lxml/lxml.etree.c:139147:: Too many arguments.
localhost# src/lxml/lxml.etree.c:139148: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'findImpliedContext'
src/lxml/lxml.etree.c:139148:: Too many arguments.
src/lxml/lxml.etree.c:139149: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'pushImpliedContextFromParser'
localhost# src/lxml/lxml.etree.c:139149: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'pushImpliedContextFromParser'
src/lxml/lxml.etree.c:139149:: Too many arguments.
src/lxml/lxml.etree.c:139150: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'pushImpliedContext'
localhost# src/lxml/lxml.etree.c:139150: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'pushImpliedContext'
src/lxml/lxml.etree.c:139150:: Too many arguments.
src/lxml/lxml.etree.c:139151: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'popImpliedContext'
localhost# src/lxml/lxml.etree.c:139151: error: 'struct
__pyx_vtabstruct_4lxml_5etree__ParserDictionaryContext' has no member
named 'popImpliedContext'
src/lxml/lxml.etree.c:139151:: Too many arguments.
src/lxml/lxml.etree.c:139165: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_createParserInputBuffer'
localhost# src/lxml/lxml.etree.c:139165: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_createParserInputBuffer'
src/lxml/lxml.etree.c:139165:: Too many arguments.
src/lxml/lxml.etree.c:139165: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__createParserInputBuffer'
undeclared (first use in this function)
localhost# src/lxml/lxml.etree.c:139165: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__createParserInputBuffer'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:139166: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_createParserInput'
localhost# src/lxml/lxml.etree.c:139166: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_createParserInput'
src/lxml/lxml.etree.c:139166:: Too many arguments.
src/lxml/lxml.etree.c:139166: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__createParserInput'
undeclared (first use in this function)
localhost# src/lxml/lxml.etree.c:139166: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__createParserInput'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:139167: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_readDtd'
localhost# src/lxml/lxml.etree.c:139167: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_readDtd'
src/lxml/lxml.etree.c:139167:: Too many arguments.
src/lxml/lxml.etree.c:139167: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__readDtd' undeclared (first
use in this function)
localhost# src/lxml/lxml.etree.c:139167: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__readDtd' undeclared (first
use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:139168: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_readDoc'
localhost# src/lxml/lxml.etree.c:139168: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'_readDoc'
src/lxml/lxml.etree.c:139168:: Too many arguments.
localhost# src/lxml/lxml.etree.c:139168: error:
'__pyx_f_4lxml_5etree_18_FileReaderContext__readDoc' undeclared (first
use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:139169: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'copyToBuffer'
localhost# src/lxml/lxml.etree.c:139169: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FileReaderContext' has no member named
'copyToBuffer'
src/lxml/lxml.etree.c:139169:: Too many arguments.
localhost# src/lxml/lxml.etree.c:139273: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FilelikeWriter' has no member named
'_createOutputBuffer'
src/lxml/lxml.etree.c:139273:: Too many arguments.
src/lxml/lxml.etree.c:139273: error:
'__pyx_f_4lxml_5etree_15_FilelikeWriter__createOutputBuffer'
undeclared (first use in this function)
localhost# src/lxml/lxml.etree.c:139273: error:
'__pyx_f_4lxml_5etree_15_FilelikeWriter__createOutputBuffer'
undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:139274: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FilelikeWriter' has no member named
'write'
src/lxml/lxml.etree.c:139274:: Too many arguments.
src/lxml/lxml.etree.c:139275: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FilelikeWriter' has no member named
'close'
localhost# src/lxml/lxml.etree.c:139275: error: 'struct
__pyx_vtabstruct_4lxml_5etree__FilelikeWriter' has no member named
'close'
src/lxml/lxml.etree.c:139275:: Too many arguments.
src/lxml/lxml.etree.c:139543: error: 'struct
__pyx_vtabstruct_4lxml_5etree_XSLT' has no member named
'_run_transform'
localhost# src/lxml/lxml.etree.c:139543: error: 'struct
__pyx_vtabstruct_4lxml_5etree_XSLT' has no member named
'_run_transform'
src/lxml/lxml.etree.c:139543:: Too many arguments.
src/lxml/lxml.etree.c:139543: error:
'__pyx_f_4lxml_5etree_4XSLT__run_transform' undeclared (first use in
this function)
localhost# src/lxml/lxml.etree.c:139543: error:
'__pyx_f_4lxml_5etree_4XSLT__run_transform' undeclared (first use in
this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:140440: error: 'xmlParserVersion' undeclared
(first use in this function)
localhost# src/lxml/lxml.etree.c:140440: error: 'xmlParserVersion'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:140590: error: 'LIBXML_VERSION' undeclared
(first use in this function)
localhost# src/lxml/lxml.etree.c:140590: error: 'LIBXML_VERSION'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:141400: error:
'__pyx_v_4lxml_5etree___DEFAULT_ENTITY_LOADER' undeclared (first use
in this function)
localhost# src/lxml/lxml.etree.c:141400: error:
'__pyx_v_4lxml_5etree___DEFAULT_ENTITY_LOADER' undeclared (first use
in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:141409: error:
'__pyx_f_4lxml_5etree__local_resolver' undeclared (first use in this
function)
localhost# src/lxml/lxml.etree.c:141409: error:
'__pyx_f_4lxml_5etree__local_resolver' undeclared (first use in this
function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:141418: error: 'XML_PARSE_NOENT'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:141418: error: 'XML_PARSE_NOCDATA' undeclared
(first use in this function)
localhost# src/lxml/lxml.etree.c:141418: error: 'XML_PARSE_NOCDATA'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:141418: error: invalid operands to binary |
localhost# src/lxml/lxml.etree.c:141418: error: invalid operands to
binary |
Invalid null command.
localhost# src/lxml/lxml.etree.c:141418: error: 'XML_PARSE_NONET'
undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:141418: error: invalid operands to
binary |
Invalid null command.
localhost# src/lxml/lxml.etree.c:141418: error: invalid operands to
binary |
Invalid null command.
localhost# src/lxml/lxml.etree.c:141678: error: 'XML_PARSE_RECOVER'
undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:141678: error: 'HTML_PARSE_NONET'
undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:141678: error: invalid operands to
binary |
Invalid null command.
localhost# src/lxml/lxml.etree.c:141678: error: invalid operands to
binary |
Invalid null command.
localhost# src/lxml/lxml.etree.c:142170: error:
'XML_XPATH_NUMBER_ERROR' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142180: error:
'XML_XPATH_UNFINISHED_LITERAL_ERROR' undeclared (first use in this
function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142190: error:
'XML_XPATH_VARIABLE_REF_ERROR' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142200: error:
'XML_XPATH_INVALID_PREDICATE_ERROR' undeclared (first use in this
function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142210: error:
'XML_XPATH_UNCLOSED_ERROR' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142220: error:
'XML_XPATH_INVALID_CHAR_ERROR' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142255: error:
'XML_XPATH_UNDEF_VARIABLE_ERROR' undeclared (first use in this
function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142265: error:
'XML_XPATH_UNDEF_PREFIX_ERROR' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142275: error:
'XML_XPATH_UNKNOWN_FUNC_ERROR' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142285: error:
'XML_XPATH_INVALID_OPERAND' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142295: error:
'XML_XPATH_INVALID_TYPE' undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142305: error:
'XML_XPATH_INVALID_ARITY' undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:142315: error: 'XML_XPATH_INVALID_CTXT_SIZE'
undeclared (first use in this function)
localhost# src/lxml/lxml.etree.c:142315: error:
'XML_XPATH_INVALID_CTXT_SIZE' undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:142325: error: 'XML_XPATH_INVALID_CTXT_POSITION'
undeclared (first use in this function)
localhost# src/lxml/lxml.etree.c:142325: error:
'XML_XPATH_INVALID_CTXT_POSITION' undeclared (first use in this
function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142663: error: 'LIBXSLT_VERSION'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:142675: error: 'xsltLibxsltVersion' undeclared
(first use in this function)
localhost# src/lxml/lxml.etree.c:142675: error: 'xsltLibxsltVersion'
undeclared (first use in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142687: error:
'__pyx_v_4lxml_5etree_XSLT_DOC_DEFAULT_LOADER' undeclared (first use
in this function)
Badly placed ()'s.
localhost# src/lxml/lxml.etree.c:142687: error: 'xsltDocDefaultLoader'
undeclared (first use in this function)
Badly placed ()'s.
src/lxml/lxml.etree.c:142696: error:
'__pyx_f_4lxml_5etree__xslt_doc_loader' undeclared (first use in this
function)
localhost# src/lxml/lxml.etree.c:142696: error:
'__pyx_f_4lxml_5etree__xslt_doc_loader' undeclared (first use in this
function)
Badly placed ()'s.
error: Setup script exited with error: command '/usr/bin/gcc' failed
with exit status 1
localhost# error: Setup script exited with error: command '/usr/bin/
gcc' failed with exit status 1
error:: Too many arguments.
localhost# An error occured when trying to install lxml 2.2.4.Look
above this message for any errors thatwere output by easy_install.
While:
Installing instance.
Getting distribution for 'lxml'.
Error: Couldn't install: lxml 2.2.4

[Denys Mishunov]

Добрый день,

On Dec 2, 2009, at 11:14 PM, alexvesna wrote:

> Ставил, как у Дениса написано.http://
> plone.org/documentation/tutorial/
> advanced-xdv-theming/tutorial-all-pages

Саша, можно посмотреть buildout.cfg?

--
Best regards,
Denys Mishunov

mailto:denys.m...@gmail.com
IRC: spliter(#plone)

[alexvesna]

ага, конечно. с закомменченными следами экспериментов :)
Именно в этом виде я и получаю ошибку. Plone из коробки, поставлен
UnifiedInstaller

############################################
#
# Buildout Configuration File for Standalone Plone
# ------------------------------------------------
# $LastChangedDate: 2009-11-04 15:23:13 -0800 (Wed, 04 Nov 2009) $
$LastChangedRevision: 29671M $
#
# After making changes in this configuration file,
# you should run bin/buildout to update the components.
#
# ALWAYS back up all Plone/Zope data and components
# before changing configuration.
#
# Running "bin/buildout" will update your installation,
# installing missing components as necessary.
#
# Use "bin/buildout -n" to update many components here to the newest
# available releases.
# This will update the add-on products you've added in the eggs=
lines.
# This will not, however, upgrade Plone itself (or anything else
you've
# pinned with a version specification). To upgrade Plone itself, see
the
# comments in "Plone Component Versions".
#
# Tutorial instructions for using zc.buildout for
# configuration management are available at:
# http://plone.org/documentation/tutorial/buildout
# Full details at http://pypi.python.org/pypi/zc.buildout
#
############################################


[buildout]

############################################
# Plone Component Versions
# ------------------------
# This version of the Unified Installer has the components
# of Plone 3.3.2 preloaded so that it can install without
# an Internet connection.
# If you want to update, uncomment the "extends = http://..." below,
# edit it to point to the current version URL,
# comment out the "extends = versions.cfg" line
# and run "bin/buildout -n" while attached to the Internet.
# Generally, you only want to do that as part
# of a planned migration.
#
#extends = http://dist.plone.org/release/3.3.2/versions.cfg
extends = versions.cfg
http://good-py.appspot.com/release/collective.xdv/1.0

versions = versions



############################################
# Ports
# -----
# Specify the port on which your Zope installation
# will listen:
http-address = 8080


############################################
# Eggs
# ----
# Add an indented line to the eggs section for any Python
# eggs or packages you wish to include.
#
eggs =
Plone
collective.lineage
collective.xdv [Zope2.10]

# Optional Functionality
# ----------------------
# Uncomment the indented lines to include these products.
# Documentation on all of them, along with many more products,
# is available at
# http://plone.org/products/
#
# Commonly used products:
# * LinguaPlone provides tools for building multi-lingual sites
# * Products.CacheSetup adds the "CacheFu" Plone speedup kit
# * PloneHelpCenter is a simple knowledge base
# * PloneFormGen provides through-the-web form building
#
Products.LinguaPlone
Products.CacheSetup
Products.PloneHelpCenter
Products.PloneFormGen
#
# Commonly used development tools:
# * Clouseau uses AJAX to provide a Python prompt inside Plone
# * DocFinderTab puts an object documentation inspector in the Zope
Management Interface
# * Gloworm is a Firebug-like viewlet inspector and customizer
# * plone.reload allows you to refresh Python code and ZCML
configuration
# without restarting Zope. Note that to use plone.reload, you'll
also
# need to uncomment the "zcml" entry for it below.
#
# Products.Clouseau
# Products.DocFinderTab
# Products.Gloworm
# plone.reload


############################################
# ZCML Slugs
# ----------
# Some eggs need ZCML slugs to tell Zope to
# use them. Eggs with names beginning with "Products."
# usually don't need this.
zcml =
# plone.reload
# collective.lineage

############################################
# Development Eggs
# ----------------
# You can use paster to create "development eggs" to
# develop new products/themes. Put these in the src/
# directory.
# You will also need to add the egg names in the
# eggs section above, and may also need to add them
# to the zcml section.
#
# Provide the *paths* to the eggs you are developing here:
develop =
# src/my.package


############################################
# Debug Mode
# ----------
# Change debug-mode to "on" to run in development mode.
#
debug-mode = on


############################################
# Backup Directory
# ----------------
# Sets the target directory for the bin/backup and bin/snapshotbackup
# commands. Default is inside this project's var directory, but
ideally
# this should be on a separate volume or backup server.
#
backups-dir=${buildout:directory}/var



############################################
############################################
# Buildout instructions beyond this point are
# usually only changed by experienced developers.


# Beyond here there be dragons!


eggs-directory=/usr/local/Plone/buildout-cache/eggs
download-cache=/usr/local/Plone/buildout-cache/downloads
newest = false
parts =
zope2
productdistros
instance
zopepy
zopeskel
precompile
chown
unifiedinstaller
backup
# lxml




# Add additional egg download sources here. dist.plone.org contains
archives
# of Plone packages.
find-links =
http://dist.plone.org
http://download.zope.org/ppix/
http://download.zope.org/distribution/
http://effbot.org/downloads

# unzip all eggs for easier debugging
unzip = true

# let's share our Zope install
zope-directory = /usr/local/Plone


# This section installs the components of Zope 2.
# Zope operating instances are created elsewhere.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2install
[zope2]
recipe = plone.recipe.zope2install
# update zope by updating this URL:
url = ${versions:zope2-url}
# fake eggs are required to satisfy Zope dependencies while
# zope is not yet eggified.
fake-zope-eggs = true
additional-fake-eggs =
ZConfig
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'.
# For options see http://pypi.python.org/pypi/plone.recipe.distros
[productdistros]
recipe = plone.recipe.distros
urls =
nested-packages =
version-suffix-packages =


# Use this section to install and configure a Zope operating
# instance.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
[instance]
recipe = plone.recipe.zope2instance
zope2-location = ${zope2:location}
# The line below sets only the initial password. It will not change an
# existing password.
user = admin:zonenstraaldev
http-address = ${buildout:http-address}
effective-user = plone
# change debug-mode to "on" to run in development mode
debug-mode = ${buildout:debug-mode}
# change verbose-security to "on" for detailed security
# errors while developing
verbose-security = off
# change deprecation-warnings to "on" to get log warnings
# for deprecated usages.
deprecation-warnings = off


# If you want Zope to know about any additional eggs, list them here.
# e.g. eggs = ${buildout:eggs} my.package
eggs =
${buildout:eggs}


# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =
${buildout:zcml}


products =
${buildout:directory}/products
${productdistros:location}


# You may also control the environment variables for the instance.
environment-vars =
PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs


# installs a zopepy python interpreter that runs with your
# full Zope environment
[zopepy]
recipe = zc.recipe.egg
eggs = ${instance:eggs}
interpreter = zopepy
extra-paths = ${instance:zope2-location}/lib/python
scripts = zopepy


# installs paster and Zopeskel
[zopeskel]
recipe = zc.recipe.egg
eggs =
PasteScript
ZopeSkel


# compiles .py files in ./parts and ./products so that they don't
# need to be compiled by the daemon
# For options see http://pypi.python.org/pypi/plone.recipe.precompiler
[precompile]
recipe = plone.recipe.precompiler


# This recipe is used to set permissions -- and ownership for root
mode installs
# For options see http://pypi.python.org/pypi/plone.recipe.command
[chown]
recipe = plone.recipe.command
command =
chmod 600 .installed.cfg
find ${buildout:directory} -type d -name var -exec chown -R $
{instance:effective-user} \{\} \;
find ${buildout:eggs-directory} -type d -name LC_MESSAGES -exec
chown -R ${instance:effective-user} \{\} \;
find ${buildout:directory} -name runzope -exec chown $
{instance:effective-user} \{\} \;
update-command = ${chown:command}


# This recipe installs the plonectl script and a few other convenience
# items.
# For options see http://pypi.python.org/pypi/plone.recipe.unifiedinstaller
[unifiedinstaller]
recipe = plone.recipe.unifiedinstaller<=4.0dev
user = ${instance:user}
primary-port = ${instance:http-address}
sudo-command =sudo


# This recipe builds the backup, restore and snapshotbackup commands.
# For options see http://pypi.python.org/pypi/collective.recipe.backup
[backup]
recipe = collective.recipe.backup
location = ${buildout:backups-dir}/backups
snapshotlocation = ${buildout:backups-dir}/snapshotbackups

#[versions]
#lxml = 2.2.2
#zc.buildout =

#[lxml]
#recipe = z3c.recipe.staticlxml
#egg = lxml
#force = false

[Denys Mishunov]

Саша, 2 момента:

On Dec 3, 2009, at 11:28 AM, alexvesna wrote:

> extends = versions.cfg
> http://good-py.appspot.com/release/collective.xdv/1.0
>
> versions = versions

...

> #[versions]
> #lxml = 2.2.2
> #zc.buildout =

1) Вы одновременно пытаетесь
использовать 2 [versions] одновременно. То
есть Вы берете [version] из versions.cfg и плюс
[versions] а buildout.cfg (если Вы раскомментите
этот кусок). Наскеолько я понимаю lxml =
2.2.2 не подхватывается билдаутом потому
как ошибка четко говорит:

> localhost# An error occured when trying to install lxml 2.2.4

В случае если Вы расширяете versions.cfg
кладите

lxml = 2.2.2
zc.buildout =

в versions.cfg и уберите всю секцию [versions] из
buildout.cfg

2) А теперь самое интересное - секции
[versions] и [lxml] Вам вообще не нужны на FreeBSD
(конечно если lxml там уже установлен).
Читаем туториал:

"""
[buildout]
…
extends =
…
http://good-py.appspot.com/release/collective.xdv/1.0
…
eggs =
…
collective.xdv [Zope2.10]

... This should be enough if you’re not on Mac OS
"""

Если же lxml у Вас не установлен, то в
секции [lxml] Вам не нужно "мастерить"
статический lxml:

> #[lxml]
> #recipe = z3c.recipe.staticlxml
> #egg = lxml
> #force = false

эта опция только для Mac OS.

Резюмируя выше изложенное - проверьте
установлен ли у Вас lxml. Если да, то
следуйте первому пути без [version] и [lxml].
Если же lxml не установлен, то нужно
поиграть с [versions] и [lxml], но:
- скорее всего [versions] Вам не понадобится
- recipe = z3c.recipe.staticlxml только для Mac OS и Вам
эту строчку добавлять не нужно

Попробуйте и сообщите о прогрессе
пожалуйста :)

[alexvesna]

Спасибо, Денис!

Зря только, наверное, я выложил бильдаут с закомменченными строками
(#). Сбивает с толку :) Они же не работают. Если их не принимать во
внимание, то получим рекомендованный описанием путь добавления
инструкций в бильдаут и именно он дает сии ошибки. Я стал
экспериментировать с versions и проч., когда оно не поставилось, как
описано.

Как играть с [versions] и [lxml] ума не приложу. Вчера весь день играл
уже, а потом сюда написал :) :(

Пойду сыграю в versions.cfg

Сообщу о результатах

[alexvesna]

Сообщаю...

Добавил в version.cfg

lxml = 2.2.2
zc.buildout =

получил ту же проблему, только с другим названием :) Весь лог не
привожу. Он идентичный. Различие только в финальной части.

Installing instance.
Getting distribution for 'lxml==2.2.2'.
Error: Couldn't install: lxml 2.2.2

Может можно еще как-нибудь установить lxml можно?

PS. Перед отправкой поста сделал новую инстанцию. Взял ее buildout.cfg
и добавил в него, рекомендованные описанием, строки. Не заработало,
увы. Ошибка та же.

[Бессарабова Ирина]

попробуйте через easy_install lxml

03.12.09, 05:09, "alexvesna" <alex...@gmail.com>:

[alexvesna]

уже. результат аналогичный

[Бессарабова Ирина]

Странно. По идеи обычная питоновская библиотека, должна и ставиться обычно. На fedora7 у меня поставилась, например. Посмотрите тут: http://codespeak.net/lxml/installation.html - может что-то найдете полезное. На крайняк, конечно, можно их исходников собрать ....

03.12.09, 06:17, "alexvesna" <alex...@gmail.com>:

> уже. результат аналогичный
>
>
> >
>
>

[alexvesna]

Спасибо, Ира!

очень странно. Документ, на который ссылаетесь я уже читал. Проблему
не решил. Ставить из исходников я ни разу не пытался, но мне кажется
это не совсем "чистый" путь. В том смысле, что даже если это удастся
сделать, то в будущем можно (теоретически) ожидать каких-нить заморок
с миграцией. Чертовски жаль, что не получается. Есть проект, на
котором можно было бы применить именно такой подход к theming.

[Denys Mishunov]

On Dec 3, 2009, at 4:37 PM, alexvesna wrote:

> Есть проект, на
> котором можно было бы применить
> именно такой подход к theming.

Саша, а на другой оси пробовали? Я не
слышал о проблемах с lxml на FreeBSD, но
может это каким-то образом связано.
Поспрашиваю у людей. Если будет
желание все таки пробовать на FreeBSD советую написать
в delivera...@lists.coactivate.org лист (само собой
с предварительно регистрацией). Это
лист рассылки тех кто работает с
Deliverance. Так как XDV это и есть Deliverance
(только на XSLT) вопрос будет более чем
уместен.

Более того Вы может захотите
использовать чистый XDV (не collective.xdv) -
подход к созданию темы все равно будет
такой же как и в collective.xdv. Посмотрите buildout тут - http://svn.plone.org/svn/collective/bu
ildout/uber/plone3.x-xdv/

Это основной buildout (сделан Мартином
Аспели) для работы с XDV через nginx.
Почитайте README.txt.

Удачи

[alexvesna]

На другой оси не пробовал. Мне надо на FreBSD, так как на рабочем
сервере она установлена. Все ссылки посмотрю обязательно, ну и
проблему опишу. Спасибо!

[alexvesna]

Спасибо за "наводку", Денис. Laurence Dowe ответил, что для правильной
работы надо, чтобы перед установкой collective.xdv УЖЕ были
установлены пакеты libxml2 и libxslt. Заработало сразу.

Может быть есть смысл добавить этот момент в наставление?

Больше всем спасибо за поддержку.

[Denys Mishunov]

On Dec 3, 2009, at 7:33 PM, alexvesna wrote:

> Спасибо за "наводку", Денис. Laurence Dowe
> ответил, что для правильной
> работы надо, чтобы перед установкой
> collective.xdv УЖЕ были
> установлены пакеты libxml2 и libxslt.
> Заработало сразу.

Отлично. Рад что Лоуренс помог.

> Может быть есть смысл добавить этот
> момент в наставление?

Хммм... возможно. Попробую найти время
что бы добавить эту информацию в
туториал - с альфами Плон 4 и
приближающимся Рождеством времени на
все не хватает :)

P.S. Саша, на будущее - моя фамилия в
английской транскрипции - Mishunov (а не
Mishuniv как Вы написали в deliverance developers) ;)
а фамилия Лоуренса - Rowe (а не Dowe) :)

Удачи!

[alexvesna]

Пардон, исправлюсь. В клавиши не смотрел :)