GetPaid and five.intid 0.4.2

[Hannes Calitz]

Has anyone got GetPaid working with five.intid 0.4.2?

I want to try out Dexterity, and it uses five.intid 0.4.2. When trying
to update Five, I get the following error when running buildout:

The version, 0.4.2, is not consistent with the requirement,
'five.intid==0.3.0'.
While:
  Installing getpaid.
Error: Bad version 0.4.2

Anyone got any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Rob LaRubbio-2]

Currently getpaid asks for five.intid 0.3.0 in getpaid.recipe.release.  To move it up we'd have to bundle a new recipe release for testing.

-Rob

On Wed, Aug 19, 2009 at 10:11 PM, hannesc <hannesc@...> wrote:

Has anyone got GetPaid working with five.intid 0.4.2?

I want to try out Dexterity, and it uses five.intid 0.4.2. When trying
to update Five, I get the following error when running buildout:

The version, 0.4.2, is not consistent with the requirement,
'five.intid==0.3.0'.
While:
 Installing getpaid.
Error: Bad version 0.4.2

Anyone got any ideas?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[David Glick]

On Aug 20, 2009, at 8:09 AM, Rob LaRubbio wrote:

> Currently getpaid asks for five.intid 0.3.0 in  
> getpaid.recipe.release.  To move it up we'd have to bundle a new  
> recipe release for testing.

It's really a pain that the getpaid release recipe pins the versions  
of non-getpaid packages.  It makes it very difficult to use getpaid in  
any case where a newer version of one of those packages is required by  
some other product.

Why can't whatever getpaid egg it is that requires five.intid just  
declare a dependency on five.intid>=0.3.0 (and <= whatever the maximum  
version its compatible with, if there are more recent releases that  
are known to be incompatible)?

David

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Brandon Craig Rhodes]

David Glick <dglick@...> writes:

> It's really a pain that the getpaid release recipe pins the versions
> of non-getpaid packages. ...Why can't whatever getpaid egg it is that
> requires five.intid just declare a dependency on five.intid>=0.3.0
> (and <= whatever the maximum version its compatible with, if there are
> more recent releases that are known to be incompatible)?

Our experience with Grok was that the product broke roughly every other
week (and sometimes even a bit more often than that) because people
would release new versions of things with which we wound up being
somehow incompatible.  Only by pinning versions exactly with "==" were
we able to assure that a Grok site deployed successfully today would
successfully deploy next week.  Otherwise, a web site deployed to three
different servers over a period of, say, three weeks, wound really be
three slightly different web sites instead of being identical. :-)

But, yes, it causes a headache when building a site out of several
different pieces. :-/

--
Brandon Craig Rhodes   brandon@...   http://rhodesmill.org/brandon

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[David Glick]

On Aug 20, 2009, at 9:25 AM, Brandon Craig Rhodes wrote:

> Our experience with Grok was that the product broke roughly every  
> other
> week (and sometimes even a bit more often than that) because people
> would release new versions of things with which we wound up being
> somehow incompatible.  Only by pinning versions exactly with "==" were
> we able to assure that a Grok site deployed successfully today would
> successfully deploy next week.  Otherwise, a web site deployed to  
> three
> different servers over a period of, say, three weeks, wound really be
> three slightly different web sites instead of being identical. :-)
>
> But, yes, it causes a headache when building a site out of several
> different pieces. :-/

I guess there's no silver bullet.  But the annoying bit about the  
getpaid recipe is that even if I *know* a particular version of  
five.intid works with both getpaid and something else, there's no way  
I can force it to use something different than the version that is  
encoded in getpaid.recipe.release.

I'd love to see getpaid stop using its special recipe and move to  
pinning its dependencies via extending the versions block of a known  
good set, like most other large Zope-based frameworks (Zope itself,  
Plone, dexterity) are doing these days.

David

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hannes Calitz]

2009/8/20 David Glick <dglick@...>

I guess there's no silver bullet.  But the annoying bit about the
getpaid recipe is that even if I *know* a particular version of
five.intid works with both getpaid and something else, there's no way
I can force it to use something different than the version that is
encoded in getpaid.recipe.release.

I'd love to see getpaid stop using its special recipe and move to
pinning its dependencies via extending the versions block of a known
good set, like most other large Zope-based frameworks (Zope itself,
Plone, dexterity) are doing these days.

David

This is something I'd also love to see happen. It would really make life so much simpler in the long run.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hannes Calitz]

Just to revisit this subject.

I have updated the recipe on my side and removed the version pinning
from it. Instead I created a versions.cfg file to be use in the build
out. This enables the user to change the version numbers as they see
fit (eg my five.intid problem mentioned previously). They both seem to
be working perfectly. Where can I submit these for review?

Thanks
Hannes

On Aug 21, 5:09 am, Hannes Calitz <hann...@...> wrote:

> 2009/8/20 David Glick <dgl...@...>
>
>
>
>
>
> > I guess there's no silver bullet.  But the annoying bit about the
> > getpaid recipe is that even if I *know* a particular version of
> > five.intid works with both getpaid and something else, there's no way
> > I can force it to use something different than the version that is
> > encoded in getpaid.recipe.release.
>
> > I'd love to see getpaid stop using its special recipe and move to
> > pinning its dependencies via extending the versions block of a known
> > good set, like most other large Zope-based frameworks (Zope itself,
> > Plone, dexterity) are doing these days.
>
> > David
>
> This is something I'd also love to see happen. It would really make life so
> much simpler in the long run.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hannes Calitz]

* UPDATE
I have commited the changes to the recipe to the repository under getpaide.recipe.release/branches/1.9.1. The versions block is under getpaid.versions. I have tested it and it seems to be working 100%.

Hannes

2009/9/3 hannesc <hannesc@...>

Just to revisit this subject.

I have updated the recipe on my side and removed the version pinning
from it. Instead I created a versions.cfg file to be use in the build
out. This enables the user to change the version numbers as they see
fit (eg my five.intid problem mentioned previously). They both seem to
be working perfectly. Where can I submit these for review?

Thanks
Hannes

On Aug 21, 5:09 am, Hannes Calitz <hann...@...> wrote:
> 2009/8/20 David Glick <dgl...@...>

>
>
>
>
>
> > I guess there's no silver bullet.  But the annoying bit about the
> > getpaid recipe is that even if I *know* a particular version of
> > five.intid works with both getpaid and something else, there's no way
> > I can force it to use something different than the version that is
> > encoded in getpaid.recipe.release.
>
> > I'd love to see getpaid stop using its special recipe and move to
> > pinning its dependencies via extending the versions block of a known
> > good set, like most other large Zope-based frameworks (Zope itself,
> > Plone, dexterity) are doing these days.
>
> > David
>

> This is something I'd also love to see happen. It would really make life so
> much simpler in the long run.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---