Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Zope>
  3. DB
zope version conflict when using buildout
robert at redcor
Jan 7, 2009, 10:05 PM
Post #1 of 5 (6720 views)
Permalink
when I run buildout, I get the following version conflict error.
this same buildout used to work without problem some weeks before.

zope@salice:~/poellinger> bin/buildout
Updating plone.
Updating zope2.
Updating fake eggs
Updating productdistros.
Installing instance.
Download error: unknown url type: svn -- Some packages may not be found!
While:
Installing instance.
Error: There is a version conflict.
We already have: ZODB3 0.0
but zope.index 3.5.0 requires 'ZODB3>=3.8.0b1'.

how can I fix this?
thanks
robert

my buildout.cfg is following:

[buildout]
extensions = buildout.eggtractor
tractor-src-directory = src
tractor-target-parts = instance
parts =
plone
zope2
productdistros
instance
zopepy

# 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

# Add additional eggs here
# elementtree is required by Plone
eggs =
elementtree
Products.Poi
borg.project
Products.LinguaPlone
collective.dancing
Products.Ploneboard

# Reference any eggs you are developing here, one per line
# e.g.: develop = src/my.package
develop =

[plone]
recipe = plone.recipe.plone>=3.1.1,<3.2dev

[zope2]
recipe = plone.recipe.zope2install
url = ${plone:zope2-url}
fake-zope-eggs = true
additional-fake-eggs = ZODB3
skip-fake-eggs =
zope.testing
zope.component
zope.i18n
zope.sendmail

# 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.zope2instance
zope2-location = ${zope2:location}
user = admin:admin
http-address = 8110
#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 =
Products.Poi
borg.project
Products.LinguaPlone
collective.dancing
Products.Ploneboard

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

[zopepy]
recipe = zc.recipe.egg
eggs = ${instance:eggs}
interpreter = zopepy
extra-paths = ${zope2:location}/lib/python
scripts = zopepy
_______________________________________________
Zope-DB mailing list
Zope-DB@zope.org
http://mail.zope.org/mailman/listinfo/zope-db
Re: zope version conflict when using buildout [ In reply to ]
jens at dataflake
Jan 7, 2009, 11:58 PM
Post #2 of 5 (6547 views)
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jan 8, 2009, at 07:05 , robert rottermann wrote:

> when I run buildout, I get the following version conflict error.
> this same buildout used to work without problem some weeks before.
>
> zope@salice:~/poellinger> bin/buildout
> Updating plone.
> Updating zope2.
> Updating fake eggs
> Updating productdistros.
> Installing instance.
> Download error: unknown url type: svn -- Some packages may not be
> found!
> While:
> Installing instance.
> Error: There is a version conflict.
> We already have: ZODB3 0.0
> but zope.index 3.5.0 requires 'ZODB3>=3.8.0b1'.
>
> how can I fix this?

That "fake eggs" stuff is dangerous, those eggs advertise their
version number as "0.0". Try to exclude the ZODB3 egg from the fake
eggs list.

jens

P.S.: This is not a ZODB issue, but an issue with the fake eggs stuff,
and should be brought up on the Plone list.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkllsjkACgkQRAx5nvEhZLL7eACeIZntx+4qPxBkQR+BRpUU5CEm
fbMAn0GJyAT/EPSh9XMqhf3W7QI24Onb
=d2PI
-----END PGP SIGNATURE-----
_______________________________________________
Zope-DB mailing list
Zope-DB@zope.org
http://mail.zope.org/mailman/listinfo/zope-db
Re: zope version conflict when using buildout [ In reply to ]
robert at redcor
Jan 8, 2009, 12:06 AM
Post #3 of 5 (6537 views)
Permalink
thanks
and sorry for the wrong list.
robert
Jens Vagelpohl schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Jan 8, 2009, at 07:05 , robert rottermann wrote:
>
>> when I run buildout, I get the following version conflict error.
>> this same buildout used to work without problem some weeks before.
>>
>> zope@salice:~/poellinger> bin/buildout
>> Updating plone.
>> Updating zope2.
>> Updating fake eggs
>> Updating productdistros.
>> Installing instance.
>> Download error: unknown url type: svn -- Some packages may not be
>> found!
>> While:
>> Installing instance.
>> Error: There is a version conflict.
>> We already have: ZODB3 0.0
>> but zope.index 3.5.0 requires 'ZODB3>=3.8.0b1'.
>>
>> how can I fix this?
>
> That "fake eggs" stuff is dangerous, those eggs advertise their
> version number as "0.0". Try to exclude the ZODB3 egg from the fake
> eggs list.
>
> jens
>
> P.S.: This is not a ZODB issue, but an issue with the fake eggs stuff,
> and should be brought up on the Plone list.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
>
> iEYEARECAAYFAkllsjkACgkQRAx5nvEhZLL7eACeIZntx+4qPxBkQR+BRpUU5CEm
> fbMAn0GJyAT/EPSh9XMqhf3W7QI24Onb
> =d2PI
> -----END PGP SIGNATURE-----
> _______________________________________________
> Zope-DB mailing list
> Zope-DB@zope.org
> http://mail.zope.org/mailman/listinfo/zope-db
>
>

_______________________________________________
Zope-DB mailing list
Zope-DB@zope.org
http://mail.zope.org/mailman/listinfo/zope-db
Re: zope version conflict when using buildout [ In reply to ]
onsombal at yahoo
Jan 8, 2009, 5:25 AM
Post #4 of 5 (6522 views)
Permalink
I encountered the same problem yesterday. My buildout was working perfectly
and then suddenly failed. The culprit turned out to be "collective.dancing"
or at least one of its dependencies -- I'm not sure which. I do know that
once I removed "collective.dancing" from my buildout, everything worked
fine.

I see "collective.dancing" is also in your buildout.

The interesting thing is that "collective.dancing" has been in my buildout
for some time now, so something else has changed with or related to that
package.

Regards... Jim


robert rottermann wrote:
>
> when I run buildout, I get the following version conflict error.
> this same buildout used to work without problem some weeks before.
>
> zope@salice:~/poellinger> bin/buildout
> Updating plone.
> Updating zope2.
> Updating fake eggs
> Updating productdistros.
> Installing instance.
> Download error: unknown url type: svn -- Some packages may not be found!
> While:
> Installing instance.
> Error: There is a version conflict.
> We already have: ZODB3 0.0
> but zope.index 3.5.0 requires 'ZODB3>=3.8.0b1'.
>
> how can I fix this?
> thanks
> robert
>
> my buildout.cfg is following:
>
> [buildout]
> extensions = buildout.eggtractor
> tractor-src-directory = src
> tractor-target-parts = instance
> parts =
> plone
> zope2
> productdistros
> instance
> zopepy
>
> # 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
>
> # Add additional eggs here
> # elementtree is required by Plone
> eggs =
> elementtree
> Products.Poi
> borg.project
> Products.LinguaPlone
> collective.dancing
> Products.Ploneboard
>
> # Reference any eggs you are developing here, one per line
> # e.g.: develop = src/my.package
> develop =
>
> [plone]
> recipe = plone.recipe.plone>=3.1.1,<3.2dev
>
> [zope2]
> recipe = plone.recipe.zope2install
> url = ${plone:zope2-url}
> fake-zope-eggs = true
> additional-fake-eggs = ZODB3
> skip-fake-eggs =
> zope.testing
> zope.component
> zope.i18n
> zope.sendmail
>
> # 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.zope2instance
> zope2-location = ${zope2:location}
> user = admin:admin
> http-address = 8110
> #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 =
> Products.Poi
> borg.project
> Products.LinguaPlone
> collective.dancing
> Products.Ploneboard
>
> products =
> ${buildout:directory}/products
> ${productdistros:location}
> ${plone:products}
>
> [zopepy]
> recipe = zc.recipe.egg
> eggs = ${instance:eggs}
> interpreter = zopepy
> extra-paths = ${zope2:location}/lib/python
> scripts = zopepy
> _______________________________________________
> Zope-DB mailing list
> Zope-DB@zope.org
> http://mail.zope.org/mailman/listinfo/zope-db
>
>

--
View this message in context: http://www.nabble.com/zope-version-conflict-when-using-buildout-tp21346401p21351731.html
Sent from the Zope - DB mailing list archive at Nabble.com.

_______________________________________________
Zope-DB mailing list
Zope-DB@zope.org
http://mail.zope.org/mailman/listinfo/zope-db
Re: zope version conflict when using buildout [ In reply to ]
chris at simplistix
Jan 9, 2009, 3:45 AM
Post #5 of 5 (6512 views)
Permalink
Jim Biggs wrote:
> I encountered the same problem yesterday. My buildout was working perfectly
> and then suddenly failed. The culprit turned out to be "collective.dancing"
> or at least one of its dependencies -- I'm not sure which. I do know that
> once I removed "collective.dancing" from my buildout, everything worked
> fine.
>
> I see "collective.dancing" is also in your buildout.
>
> The interesting thing is that "collective.dancing" has been in my buildout
> for some time now, so something else has changed with or related to that
> package.

collective.dancing, in my extremely limited experience of it (a customer
of mine broke their plohn buildout in exactly the way described here) is
an absolute abomination and should be avoided at all costs...

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-DB mailing list
Zope-DB@zope.org
http://mail.zope.org/mailman/listinfo/zope-db

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal