[Grok-dev] zc.buildout 1.5.0

[Jeffrey D Peterson]

--
Jeffrey Peterson
bgpete3 at gmail.com


> -----Original Message-----
> From: Gary Poster [mailto:gary.poster at gmail.com]
> Sent: Tuesday, September 07, 2010 1:19 PM
> To: Jeffrey D Peterson
> Cc: grok-dev at zope.org
> Subject: Re: [Grok-dev] zc.buildout 1.5.0
> 
> 
> On Sep 7, 2010, at 1:02 PM, Jeffrey D Peterson wrote:
> 
> > I had the same issue, except it was complaining about zc.buildout
> 1.5.1 for
> > me.
> 
> That's actually what I would expect.
> 
> >
> > Installed bootstrap.py:
> >
> > parser.add_option("-v", "--version", dest="version",
> >                          help="use a specific zc.buildout version")
> >
> > Tried and failed with the bootstrap.py suggested here
> > https://mail.zope.org/pipermail/grok-dev/2010-August/010593.html:
> >
> > parser.add_option("-v", "--version", dest="version", default="1.4.4"
> >                          help="use a specific zc.buildout version")
> >
> > there is no version 1.4.4 of zc.buildout on pypi.
> 
> Not sure the issue there.  Everyone I've heard from before who has need
> to use it has found it.
> 
> http://pypi.python.org/pypi/zc.buildout/1.4.4
> 
> > So, I tried defaulting to
> > 1.5.1 and it did not work.
> 
> With the same conflict error reported earlier?  I expect there is some
> recipe conflict.  I'm happy to try and help if someone gives me a lead
> that doesn't involve me trying to build grok.  I'm even happy to build
> grok if it's necessary.

Yes with the same conflict error.  After you run grokproject and it fails
with that error, cd to the app folder and there is a built buildout.cfg with
1.5.1 defaulted and if you run ./bin/buildout from there it works fine.

> 
> Gary
> 
> >
> > I tried and failed with:
> >
> > parser.add_option("-v", "--version", dest="version", default="1.5.1"
> >                          help="use a specific zc.buildout version")
> >
> > Not sure what the issue really is..
> >
> > Ultimately I succeeded by installing zc.buildout 1.4.3.  I Installed
> it into
> > the site-packages of the python being used.  Though this may not be a
> great
> > solution if you are using the system python, but it works fine in
> > virtualenv.
> >
> > easy_install  zc.buildout==1.4.3
> >
> > --
> > Jeffrey Peterson
> > bgpete3 at gmail.com
> >
> >
> >> -----Original Message-----
> >> From: grok-dev-bounces at zope.org [mailto:grok-dev-bounces at zope.org]
> On
> >> Behalf Of Gary Poster
> >> Sent: Tuesday, September 07, 2010 9:53 AM
> >> To: grok-dev at zope.org
> >> Subject: Re: [Grok-dev] zc.buildout 1.5.0
> >>
> >>
> >> On Sep 7, 2010, at 10:50 AM, <jose at cybergalvez.com> wrote:
> >>
> >>> Wow that looks like it works! Thanks
> >>> Jose
> >>>
> >>>> -------- Original Message --------
> >>>> Subject: Re: [Grok-dev] zc.buildout 1.5.0
> >>>> From: Christian Klinger <cklinger at novareto.de>
> >>>> Date: Tue, September 07, 2010 10:19 am
> >>>> To: grok-dev at zope.org
> >>>>
> >>>>
> >>>> Hello Jose,
> >>>>
> >>>> i think you can do this:
> >>>>
> >>>> grokproject yourproject
> >>>> ...
> >>>> Traceback buildout 1.5.0 ...
> >>>> ...
> >>>>
> >>>> cd yourproject
> >>>> bin/buildout
> >>>>
> >>>> Just call bin/buildout directly in your project.
> >>>> This works for me. But i don't know if it's useful as a general
> >>>> fix for it.
> >>>>
> >>>> Just try it.
> >>>>
> >>>> Christian
> >>>>
> >>>>> I just installed Grok on ubuntu and I received a zc.buildout
> 1.5.0
> >>>>> version conflict trying to create a project. Looking though the
> >> list
> >>>>> server it looks like this might be a know issue. Is this going to
> >> be
> >>>>> fixed soon?
> >>
> >> I saw https://mail.zope.org/pipermail/grok-dev/2010-
> August/010593.html
> >> as a description of the traceback.  I can't tell if that's something
> I
> >> can help with.  I'm willing to work with someone to help fix this
> >> generally if you'd like.
> >>
> >> Gary
> >> _______________________________________________
> >> Grok-dev mailing list
> >> Grok-dev at zope.org
> >> https://mail.zope.org/mailman/listinfo/grok-dev
> >