[Zope-dev] Attention: cvs to subversion transition DONE (I hope :)
The conversion is done. All trunk development should be done in the subversion repository for Zope (Zope 2), Zope3, ZODB, ZConfig, and zdaemon. (zLOG is not broken out as a separate project because it's now only used by Zope.) For information on using the Zope subversion repository, see: http://dev.zope.org/Subversion and especially: http://dev.zope.org/Subversion/ZopeSVNFAQ I'm gonna wait a few days before removing files from the CVS head, just to be safe. :) I will check in some marker files, warning people to work in svn. Finally, before the conversion, I tagged the cvs head with the cvs-to-svn-conversion tag. If you have outstanding head work, you should be able to update to that tag and then use cvs diff to generate patch files to be applied to subversion checkouts. Jim Jim Fulton wrote: I'm about to begin the conversion now. Please don't make any more changes to the Zope, Zope3, ZODB, ZConfig, zLOG, or zdaemon CVS heads. Jim Jim Fulton wrote: I plan to do the transition tomorrow, Tuesday may 11. I'll begin at 10am US/Eastern and be done by 5pm US/Eastern. During this time, I ask that no one make checkins to the CVS head for those projects. The first thing I will do is to tag the head with the tag: 'cvs-to-svn-conversion'. When I'm done, I will remove all files from the heads of the preojects in CVS, except README.txt files giving subversion access instructions. Jim Jim Fulton wrote: Jim Fulton wrote: Sorry for the false start. I totally missed a flaw in subversion's handling of text-file line endings. I suspect that this is fixable, but it's not going to be fixed today. I think that this issue has been resolved. I have updated my cvs to svn conversion software to set the svn:eol-style property to native on text files so that they will get Windows line endings when checked out on Windows and Unix line endings when checked out on Unix-based systems. I've updated the demonstration repository with the results of this conversion. Note that it's possible that existing checkouts will need to be discarded, as I've totallly rebuilt the repository. To browse the respository: http://svn.zope.org/ To do a read-only checkout: svn co svn://svn.zope.org/repos/main/project/trunk or, to do a writable checkout: svn co svn+ssh://svn.zope.org/repos/main/project/trunk Developers who add new files will need to set the svn:eol-style property on new text files. There are ways to automate this and we'll provide some guidence on this at: http://dev.zope.org/Subversion BTW, someone has done some work on that Wiki, which was a copy of dev.zope.orf/CVS, to convert the CVS references and instructions to refer to and document Subversion instead. Thanks! I think that there is still a good bit of work to do. Volunteer help would be much appreciated. I'm thinking of trying again to do the cvs to svn conversion of the main-line development branches (cvs heads) on Tusday May 11. This would entail moving ZODB, Zope 2, and Zope 3 head development to subversion (along with ZConfig, zdaemon, and zLOG). Any objections? Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Attention: cvs to subversion transition May 11
I'm about to begin the conversion now. Please don't make any more changes to the Zope, Zope3, ZODB, ZConfig, zLOG, or zdaemon CVS heads. Jim Jim Fulton wrote: I plan to do the transition tomorrow, Tuesday may 11. I'll begin at 10am US/Eastern and be done by 5pm US/Eastern. During this time, I ask that no one make checkins to the CVS head for those projects. The first thing I will do is to tag the head with the tag: 'cvs-to-svn-conversion'. When I'm done, I will remove all files from the heads of the preojects in CVS, except README.txt files giving subversion access instructions. Jim Jim Fulton wrote: Jim Fulton wrote: Sorry for the false start. I totally missed a flaw in subversion's handling of text-file line endings. I suspect that this is fixable, but it's not going to be fixed today. I think that this issue has been resolved. I have updated my cvs to svn conversion software to set the svn:eol-style property to native on text files so that they will get Windows line endings when checked out on Windows and Unix line endings when checked out on Unix-based systems. I've updated the demonstration repository with the results of this conversion. Note that it's possible that existing checkouts will need to be discarded, as I've totallly rebuilt the repository. To browse the respository: http://svn.zope.org/ To do a read-only checkout: svn co svn://svn.zope.org/repos/main/project/trunk or, to do a writable checkout: svn co svn+ssh://svn.zope.org/repos/main/project/trunk Developers who add new files will need to set the svn:eol-style property on new text files. There are ways to automate this and we'll provide some guidence on this at: http://dev.zope.org/Subversion BTW, someone has done some work on that Wiki, which was a copy of dev.zope.orf/CVS, to convert the CVS references and instructions to refer to and document Subversion instead. Thanks! I think that there is still a good bit of work to do. Volunteer help would be much appreciated. I'm thinking of trying again to do the cvs to svn conversion of the main-line development branches (cvs heads) on Tusday May 11. This would entail moving ZODB, Zope 2, and Zope 3 head development to subversion (along with ZConfig, zdaemon, and zLOG). Any objections? Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Zope head broken on cygwin?
I'm surprised it works for you under OpenBSD. The HEAD is broken Works meant it did not produce the same error on OpenBSD on the second startup. I didn't go further. currently because database mounts don't work. See the thread started by http://mail.zope.org/pipermail/zope-dev/2004-April/022684.html for more info. Thanks for the heads up, I must have missed this thread. Regards, Sandor ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [ZODB-Dev] Re: BTrees strangeness (was [Zope-dev] Zope 2.X BIG Session problems - blocker - our site dies - need help of experience Zope developer, please)
Hi Chris, Chris McDonough wrote at 2004-5-11 00:54 -0400: ... So what do folks think of this error-case transaction isolation patch? Michael's original patch is preserved here (although it didn't survive cut and paste from my mail client in a pristine way, you'll get the idea): http://www.plope.com/Members/chrism/transaction_isolation_error.patch/file_view Personally it looks fine to me. It wraps each error invocation in its own transaction. Please revisit the discussion (mostly between Toby and me) on zope-dev about how to fix this problem. Toby convinced me that error handling should take place in the same transaction as the original request (and not in its own). His main argument: the traceback can contain references to persistent objects that should not be there. If they are written to ZODB in any way, all kinds of dubious inconsistencies can occur. Meanwhile, I saw several questions in the mailing lists of people that wanted to access the SESSION object during error handling (probably) because it contained useful information for error handling. This is impossible when the transaction is aborted before error handling. -- Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [ZODB-Dev] Re: BTrees strangeness (was [Zope-dev] Zope 2.X BIG Session problems - blocker - our site dies - need help of experience Zope developer, please)
On Tue, 2004-05-11 at 13:04, Dieter Maurer wrote: Hi Chris, Chris McDonough wrote at 2004-5-11 00:54 -0400: ... So what do folks think of this error-case transaction isolation patch? Michael's original patch is preserved here (although it didn't survive cut and paste from my mail client in a pristine way, you'll get the idea): http://www.plope.com/Members/chrism/transaction_isolation_error.patch/file_view Personally it looks fine to me. It wraps each error invocation in its own transaction. Please revisit the discussion (mostly between Toby and me) on zope-dev about how to fix this problem. Toby convinced me that error handling should take place in the same transaction as the original request (and not in its own). His main argument: the traceback can contain references to persistent objects that should not be there. If they are written to ZODB in any way, all kinds of dubious inconsistencies can occur. Meanwhile, I saw several questions in the mailing lists of people that wanted to access the SESSION object during error handling (probably) because it contained useful information for error handling. This is impossible when the transaction is aborted before error handling. Right. I will try to work up another patch then. - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
