Ergebnis 1 bis 2 von 2

Thema: Problem mit lxml.cfg

  1. #1
    HTML Newbie
    Registriert seit
    04.06.2011
    Beiträge
    4
    Danke
    0
    Bekam 0 mal "Danke" in 0 Postings

    Standard Problem mit lxml.cfg

    Hallo,

    ich möchte eiegntlich neue xdv-themes installieren und bekomme immer folgende Fehlermeldung. Ich muss an dieser Stelle jedoch auch zugeben, dass ich och relativ neu bin und hoffe, dass mir verziehen wird, wenn es ein dummer Fehler ist...

    Code:
    While:   Installing. Error: Missing option: lxml:recipe *************** PICKED VERSIONS **************** [versions]  *************** /PICKED VERSIONS ***************
    Anbei noch mein Buildout.cfg

    Code:
    ############################################
    #
    # Buildout Configuration File for Standalone Plone
    # ------------------------------------------------
    # $LastChangedDate: 2011-03-03 17:30:15 -0800 (Thu, 03 Mar 2011) $ $LastChangedRevision: 47921 $
    #
    # 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 4 
    # preloaded so that it can install without an Internet connection.
    # If you want to update, uncomment the "http://..." line below,
    # edit it to point to the current version URL, comment out the 
    # "versions.cfg" line and run "bin/buildout" while attached to the 
    # Internet. Generally, you only want to do that as part of a planned migration.
    # Note that if you are updating components, you should also check the versions
    # section at the end of this file, since recipes or components other than
    # those of Zope and Plone may need updating at the same time.
    #
    #extends = 
    #    base.cfg
    #    versions.cfg
    extends =
    #    http://dist.plone.org/release/4.0-latest/versions.cfg
        lxml.cfg
    #    http://good-py.appspot.com/release/collective.xdv/1.0?plone=4.0
        base.cfg
        versions.cfg
    #    develop.cfg
    #    lxml.cfg
        
    
    #versions = versions
    #    http://dist.plone.org/release/4.0-latest/versions.cfg
    
    find-links =
         http://svn.plone.org/svn/collective
    
    ############################################
    # Ports
    # -----
    # Specify the port on which your Zope installation
    # will listen:
    http-address = 8080
    #http-address = 80
    
    
    # If you try to start Zope as root, it will change user id to run as
    # the effective user specified here. This user id must own the var directory
    # of your buildout.
    effective-user = lebensdorf.net
    
    
    ############################################
    # Eggs
    # ----
    # Add an indented line to the eggs section for any Python
    # eggs or packages you wish to include.
    #
    eggs =
        Plone
        PIL==1.1.6
        collective.xdv
        xdvtheme.inventions
        xdvtheme.ld
        xdvtheme.ric
        xdvtheme.blogld
        xdvtheme.blogric
    
    
    # Optional Functionality
    # ----------------------
    # Uncomment the indented lines to include these add-on products.
    # Documentation on all of them, along with many more products,
    # is available at
    # http://plone.org/products/
    #
    # Example products:
    # * LinguaPlone provides tools for building multi-lingual sites
    # * PloneFormGen provides through-the-web form building
    #
    #    Products.LinguaPlone==4.0.1
    #    Products.PloneFormGen==1.6.0
    #
    # Note that versions may be specified here or in the [versions]
    # section below. You should always specify versions that you know
    # are compatible with the Plone release and at an acceptable
    # development level.
    #
    # Commonly used development tools:
    # Several excellent development tools are included in the develop.cfg
    # buildout extension. Read it to learn how to activate these tools.
    
        
    ############################################
    # ZCML Slugs
    # ----------
    # Some eggs need ZCML slugs to tell Zope to
    # use them. This is increasingly rare.
    zcml =
        collective.xdv
        xdvtheme.inventions
        xdvtheme.ld
        xdvtheme.ric
        xdvtheme.blogld
        xdvtheme.blogric
    
        
    ############################################
    # 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.
    # This will dramatically slow Plone.
    # 
    debug-mode = off
    # Add-on developers should turn deprecation warnings on
    deprecation-warnings = off
    # change verbose-security to "on" for useful security errors while developing
    verbose-security = off
    
    
    ############################################
    # 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
    
    
    ############################################
    # Initial User
    # ------------
    # This is the user id and password that will be used to create the initial 
    # user id that will allow you to log in and create a Plone site. This only
    # sets the initial password; it will not allow you to change an already 
    # existing password. If you change the admin password via the web interface,
    # the one below will no longer be valid.
    # If you find yourself locked out of your Zope/Python installation, you may
    # add an emergency user via "bin/plonectl adduser".
    user=admin:gnL89L8B2FIurPGB619s
    
    
    ############################################
    # Parts Specification
    #--------------------
    # Specifies the components that should be included in the buildout.
    # All the basics are in the base.cfg extension; you may add your
    # own if you need them at the end of this file.
    parts =
        lxml
        instance
        zopepy
        zopeskel
        unifiedinstaller
        chown
    
    
    ############################################
    # Versions Specification
    # ----------------------
    # Version information supplied here will "pin" Python packages to a particular
    # version number, even when you use the "newest" flag running buildout.
    # Specifying versions for all packages is a good idea and can prevent
    # accidental changes when you add new packages to your buildout.
    # Note that versions specified here will override those specified earlier
    # in the configuration, including those from the Plone and Zope version
    # config files.
    #
    [versions]
    Cheetah = 2.2.1
    Paste = 1.7.5.1
    PasteScript = 1.7.3
    ZopeSkel = 2.18
    collective.recipe.backup = 1.7
    plone.recipe.command = 1.1
    plone.recipe.osxcontroller = 0.4
    plone.recipe.unifiedinstaller = 4.0rc1
    
    #Required by:
    #PasteScript 1.7.3
    PasteDeploy = 1.3.4
    und die lxml.cfg

    Code:
    [lxml] parts =    staticlxml    pylxml  [pylxml] recipe=zc.recipe.egg interpreter=pylxml eggs=     lxml  [staticlxml] recipe = z3c.recipe.staticlxml egg = lxml
    Hat jemand eine Idee?

    Viele Grüße,
    Ergy
    Achtung: Dies ist ein alter Thread im HTML und Webmaster Forum
    Diese Diskussion ist älter als 90 Tage. Die darin enthaltenen Informationen sind möglicherweise nicht mehr aktuell. Erstelle bitte zu deiner Frage ein neues Thema im Forum !!!!!

  2. #2
    Meister(in)
    Registriert seit
    14.02.2008
    Ort
    München
    Beiträge
    456
    Danke
    0
    Bekam 0 mal "Danke" in 0 Postings

    Standard AW: Problem mit lxml.cfg

    Hallo,

    erstmal hoffe ich das deine lxml.cfg nicht so aussieht wie gepostet sondern schön mehrzeilig. Außerdem wäre eine lxml.cfg die nur dies beinhaltet nicht buildout konform, jede cfg Datei muss mit [buildout] beginnen, parts sind nur dort erlaubt, [lxml] wäre somit falsch und würde sofort ignoriert und fehler geben weil es keinen recipe befehl hat.
    Da du ja schon auf sehr hohem level versuchst dir lxml zu installieren und sagst das du noch recht neu bist gehe ich davon aus das du diese aus einer offiziellen Quelle gezogen hast. Was jetzt typisch wäre, aber nicht nachvollziehbar weil du keinen kompletten Traceback mit geschickt hast, wäre einfach das Fehlen der Abhängigkeiten zu lxml:
    - libxml2
    - libxslt

    also entweder beide installieren und dann nochmal versuchen oder aber direkt das lxml egg anziehen, das benötig auf jden fall die abhängigkeiten, dann funktioniert aber Diazo auch. Wenn es immer noch nicht funktioniert, dann bitte Plattform (OS), Ursprungsinstallation (sieht nach Unified Installer aus) und kompletten Traceback posten.

    Gruss Pumukel
    Geändert von Pumukel (27.06.2011 um 00:29 Uhr)
    Die beste Informationsquelle sind Leute, die versprochen haben, nichts weiterzuerzählen.

    Marcel Mart
    frz. Schriftsteller

Stichworte

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •