[Chris McDonough]
> This merge has been done.
Woo hoo! Thank you, Chris!
I since stitched in ZODB 3.6.0b2, which is the most recent 3.6
(internal) release. That didn't seem to create any new problems.
> Since "zopectl test " no longer appears to do the right
> thing
Sorry, never used it, don'
This merge has been done.
Since "zopectl test " no longer appears to do the right
thing and I can't seem to get test.py to run anything except the entire
test suite, I didn't create any new tests because I wouldn't have had
the time to create tests and run them iteratively.
That said, all existin
On Fri, 2005-10-28 at 10:12 -0400, Tim Peters wrote:
> Ah, it's the properties on lib/python that are screwing us here! Chris, throw
>
> svn revert lib/python
>
> into the mix too. That got me unstuck. The problem is that both Jim
> and I (at least) changed the set of externals listed in l
[Tim Peters]
>>> Jim redid the way Zope trunk stitches in Zope3 since you last looked
>>> at this, and that can create some mechanical problems (of the kinds
>>> you're seeing, in fact). The svn docs probably won't help.
>>> Suggestion (which is repetition of what I suggested before this
>>> happe
On Oct 28, 2005, at 9:19 AM, Jim Fulton wrote:
svn:externals suck. A lot. As Tim suggested, you could throw away
this check out and start over. A simpler thing you could do is to
remove the zope directory and do an svn up.
That sounds reasonable, but I've done both of those things and no joy
Chris McDonough wrote:
Jim redid the way Zope trunk stitches in Zope3 since you last looked
at this, and that can create some mechanical problems (of the kinds
you're seeing, in fact). The svn docs probably won't help.
Suggestion (which is repetition of what I suggested before this
happened, bu
