[Grok-dev] task: reproducing and reporting a mr.developer issue

[Vincent Fretin]

Hi,

You need to do bin/buildout after you checkout/activate a package.
You can do:
bin/develop rb
which do the previously done "bin/buildout -c thegood.cfg"

Vincent

On Tue, Jan 26, 2010 at 11:13 PM, Martijn Faassen
<faassen at startifact.com> wrote:
> Hi there,
>
> When we were using mr.developer at the Grok sprint last week, we ran
> into the following issue when testing the zopetoolkit and/or the
> groktoolkit:
>
> When you use bin/develop co to check out a package, it will check it
> out. In some cases it will however not "unpin" the version, even though
> mr.developer to my understanding is supposed to do. This means that the
> equivalent of this doesn't happen:
>
> [version]
> zope.foo =
>
> Instead therefore, it won't use the checked out version at all but run
> tests against the pinned version in the ztk.cfg file (for instance):
>
> [version]
> zope.foo = 1.2.3
>
> This can be very misleading to say the least. The workaround is to put a
> manual unpin in the buildout.cfg.
>
> Could someone:
>
> * reproduce this with the ZTK or Groktk?
>
> * create a minimal test case
>
> * figure out how to report a bug report to the mr.developer developers
>
> * and report the bug?
>
> Regards,
>
> Martijn
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>