From: Johannes R. <rag...@ad...> - 2014-09-17 01:35:43
|
I had the same problem. And squashed it: Good old good-py.appspot.com to the rescue! If you use this version pin, you're fine, at least for installing: http://good-py.appspot.com/release/plone/3.3.6 Here is a example partial buildout: https://github.com/thet/buildout-base/blob/master/etc/plone3.cfg Cheers, Johannes On Thu, 2014-09-11 at 08:37 -0500, Nathan Van Gheem wrote: > That's odd. Doesn't seem like anything should be pulling in that > version of plone.protect. > > > Can you run buildout with the -vvvvv option so you get more output and > see what is going wrong? > > > Either the version pinning isn't working or somethign your are > depending on is requiring newer versions than what you're pinning? > > On Thu, Sep 11, 2014 at 7:56 AM, Luca Fabbri <lu...@ke...> wrote: > On Thu, Sep 11, 2014 at 2:51 PM, robert <ro...@re...> > wrote: > > thanks Luca, > > > > here are the two thre files involved: > > robert > > > > Try to add to your versions "Products.CMFPlone = 4.0b1" (the > compatibility shim version). Don't be scared: 4.0.b1 in the > right > version for Plone 3! > > > > > > ---------------------------------------- > > buildout.cfg > > ---------------------------------------- > > [buildout] > > parts = > > # lxml > > instance > > test > > coverage-report > > zopepy > > zopeskel > > checkversions > > mkrelease > > # omelette > > > > extends = > > packages.cfg > > > > # Packages to check out/update when buildout is run > > auto-checkout = > > # plone-customizations > > > > # Make sure buildout always attempts to update packages > > always-checkout = force > > > > # Static lxml build. > > # Uncomment the ``lxml`` line in the ``parts`` list at the > top of this file > > # to use this, which may be necessary on Mac OS X in > particular > > [lxml] > > recipe = z3c.recipe.staticlxml > > egg = lxml > > > > # Development Zope instance. Installs the ``bin/instance`` > script > > [instance] > > recipe = plone.recipe.zope2instance > > http-address = 8080 > > user = admin:admin > > verbose-security = on > > eggs = > > ${eggs:main} > > ${eggs:devtools} > > > > products = > > ${buildout:directory}/products > > > > enable-product-installation=on > > > > # Test runner. Run: ``bin/test`` to execute all tests > > [test] > > recipe = zc.recipe.testrunner > > eggs = ${eggs:test} > > defaults = ['--auto-color', '--auto-progress'] > > > > # Coverage report generator. > > # Run: ``bin/test --coverage=coverage`` > > # and then: ``bin/coveragereport`` > > [coverage-report] > > recipe = zc.recipe.egg > > eggs = z3c.coverage > > scripts = coveragereport > > arguments = ('parts/test/coverage', 'coverage') > > > > # Installs the ``bin/zopepy`` interpreter. > > [zopepy] > > recipe = zc.recipe.egg > > eggs = > > ${eggs:main} > > ${eggs:devtools} > > interpreter = zopepy > > > > # Installs ZopeSkel, which can be used to create new > packages > > # Run: ``bin/zopeskel`` > > [zopeskel] > > recipe = zc.recipe.egg > > eggs = ZopeSkel > > > > # Tool to help check for new versions. > > # Run: ``bin/checkversions versions.cfg`` > > [checkversions] > > recipe = zc.recipe.egg > > eggs = z3c.checkversions [buildout] > > > > # Tool to make releases > > # Run: ``bin/mkrelease --help`` > > [mkrelease] > > recipe = zc.recipe.egg > > eggs = jarn.mkrelease > > > > # Installs links to all installed packages to > ``parts/omelette``. > > # On Windows, you need to install junction.exe first > > [omelette] > > recipe = collective.recipe.omelette > > eggs = > > ${eggs:main} > > ${eggs:devtools} > > > > ---------------------------------------- > > packages.cfg > > ---------------------------------------- > > [buildout] > > extensions = mr.developer > > extends = > > # Known good sets of eggs we may be using > > http://dist.plone.org/release/3.3.6/versions.cfg > > versions.cfg > > #http://dist.plone.org/release/4.3.3/versions.cfg > > > > versions = versions > > unzip = true > > > > # Egg sets > > [eggs] > > main = > > Plone > > Products.LinguaPlone > > Products.PloneFormGen > > Products.Formulator > > Products.PloneLanguageTool > > # plone-customizations > > test = > > # plone-customizations [test] > > devtools = > > plone.reload > > # Products.PDBDebugMode > > Products.PrintingMailHost > > Products.DocFinderTab > > plone.app.debugtoolbar > > > > # Checkout locations for packages > > # Packages can be checked out with ``bin/develop`` or > > # automatically when buildout is run by listing them in > > # the ``auto-checkout`` option in ``buildout.cfg``. > > [sources] > > #plone-customizations = fs plone-customizations > > > > ---------------------------------------- > > versions.cfg > > ---------------------------------------- > > > > [versions] > > # Buildout > > mr.developer = 1.20 > > collective.recipe.omelette = 0.12 > > > > # Development tools > > Products.DocFinderTab = 1.0.4 > > Products.PDBDebugMode = 1.3.1 > > Products.PrintingMailHost = 0.7 > > z3c.coverage = 1.2.0 > > jarn.mkrelease = 3.5 > > setuptools-git = 0.4.2 > > setuptools-hg = 0.4 > > plone.app.debugtoolbar = 1.0a2 > > > > # ZopeSkel > > ZopeSkel = 3.0a1 > > Cheetah = 2.2.1 > > Paste = 1.7.5.1 > > PasteScript = 1.7.5 > > PasteDeploy = 1.5.0 > > templer.buildout = 1.0a2 > > templer.core = 1.0b3 > > templer.plone = 1.0a1 > > templer.zope = 1.0a2 > > > > # JBOT > > lazy = 1.0 > > z3c.jbot = 0.7.1 > > > > # robert > > plone.app.i18n=2.0.1 > > plone.app.controlpanel=2.1 > > Products.ATContentTypes=2.0.2 > > CMFPlone=3.3.6 > > > > > > Am 11.09.2014 um 13:30 schrieb Luca Fabbri: > > > >> On Thu, Sep 11, 2014 at 9:20 AM, robert <ro...@re...> > wrote: > >>> > >>> thanks nathan, > >>> > >>> As you can ses in the versions file which I copied below, > I do pin > >>> CMFPlone=3.3.6 > >> > >> The right way to do this is pinning "Products.CMFPlone", > not only > >> "CMFPlone" but for Plone <4 you must use "Plone" (so: Plone > = 3.3.6). > >> > >> However the problem is not here. Are you extending also the > official > >> Plone version from > http://dist.plone.org/release/3.3.6/versions.cfg > >> (using extends = ...) ? > >> > >> Please, paste the whole buildout.cfg > >> > >> > >> > >> > >>> However, builoud tries to install Products.CMFPlone and > therefore > >>> produces > >>> the following error: > >>> > >>> Installing instance. > >>> While: > >>> Installing instance. > >>> Error: There is a version conflict. > >>> We already have: plone.protect 1.1 > >>> but Products.CMFPlone 5.0a2 requires > 'plone.protect>=3.0.0a1'. > >>> > >>> thanks for your help > >>> Robert > >>> > >>> [versions] > >>> # Buildout > >>> mr.developer = 1.20 > >>> collective.recipe.omelette = 0.12 > >>> > >>> # Development tools > >>> Products.DocFinderTab = 1.0.4 > >>> Products.PDBDebugMode = 1.3.1 > >>> Products.PrintingMailHost = 0.7 > >>> z3c.coverage = 1.2.0 > >>> jarn.mkrelease = 3.5 > >>> setuptools-git = 0.4.2 > >>> setuptools-hg = 0.4 > >>> plone.app.debugtoolbar = 1.0a2 > >>> > >>> # ZopeSkel > >>> ZopeSkel = 3.0a1 > >>> Cheetah = 2.2.1 > >>> Paste = 1.7.5.1 > >>> PasteScript = 1.7.5 > >>> PasteDeploy = 1.5.0 > >>> templer.buildout = 1.0a2 > >>> templer.core = 1.0b3 > >>> templer.plone = 1.0a1 > >>> templer.zope = 1.0a2 > >>> > >>> # JBOT > >>> lazy = 1.0 > >>> z3c.jbot = 0.7.1 > >>> > >>> # robert > >>> plone.app.i18n=2.0.1 > >>> plone.app.controlpanel=2.1 > >>> Products.ATContentTypes=2.0.2 > >>> CMFPlone=3.3.6 > >>> Am 10.09.2014 um 22:02 schrieb Nathan Van Gheem: > >>> > >>> What does your buildout look like? It seems like you're > not pinning > >>> versions > >>> for plone 3.3.6 > >>> > >>> > >>> On Wed, Sep 10, 2014 at 2:42 PM, robert <ro...@re...> > wrote: > >>>> > >>>> Hi there > >>>> for a migration project I try to install plone 3.3.6. > >>>> Now buildout tries to install plone 5.0a2 .. > >>>> > >>>> and eventually buildout breaks with the following > message: > >>>> > >>>> While: > >>>> Installing instance. > >>>> Error: There is a version conflict. > >>>> We already have: plone.protect 1.1 > >>>> but Products.CMFPlone 5.0a2 requires > 'plone.protect>=3.0.0a1'. > >>>> > >>>> how can I prevent buildout to install plone 5.0a2 > >>>> > >>>> thanks for your help > >>>> robert > >>>> > >>>> > >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ > >>>> Want excitement? > >>>> Manually upgrade your production database. > >>>> When you want reliability, choose Perforce > >>>> Perforce version control. Predictably reliable. > >>>> > >>>> > >>>> > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > >>>> _______________________________________________ > >>>> Plone-Users mailing list > >>>> Plo...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/plone-users > >>> > >>> > >>> > >>> > >>> -- > >>> Nathan Van Gheem > >>> Solutions Architect > >>> Wildcard Corp > >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Want excitement? > >>> Manually upgrade your production database. > >>> When you want reliability, choose Perforce > >>> Perforce version control. Predictably reliable. > >>> > >>> > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > >>> _______________________________________________ > >>> Plone-Users mailing list > >>> Plo...@li... > >>> https://lists.sourceforge.net/lists/listinfo/plone-users > >>> > >> > >> > > > > > > > -- > -- luca > > twitter: http://twitter.com/keul > linkedin: http://linkedin.com/in/lucafbb > blog: http://blog.keul.it/ > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Plone-Users mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-users > > > > > > -- > Nathan Van Gheem > Solutions Architect > Wildcard Corp > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Plone-Users mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-users -- programmatic web development di(fh) johannes raggam / thet python plone zope development plone framework team member mail: of...@pr... web: http://programmatic.pro http://bluedynamics.com |