[Andreas Jung] > Log message for revision 30558: > > - Collector #1323: applied patch to fix umask problem in zdctl > > Changed: > U Zope/trunk/doc/CHANGES.txt > U Zope/trunk/lib/python/zdaemon/zdctl.py
Andreas, Zope doesn't "own" zdaemon. zdaemon is (so far) *copied* into Zope from repos/main/zdaemon/trunk/. Checkins made to a zdaemon copy from a client project (like Zope) have no effect on the zdaemon code. So, for example, the zdaemon trunk is still broken, the zdaemon copies in Zope3 and in ZODB are still broken, and the changes you checked in to Zope's copy are likely to get lost the next time someone copies zdaemon into Zope. The right way to fix this in Zope is: 1. Apply the patch to repos/main/zdaemon/trunk/. 2. Make a tag of zdaemon trunk. 3. Delete ("svn rm") Zope's copy of zdaemon and commit. 4. From a Zope checkout, "svn propedit svn:externals lib/python", and add a line naming the zdaemon tag you created in step #2. That would make zdaemon like Zope's other external code (the ZopeX3 stuff, assorted ZODB directories, and ZConfig), and the existence of a zdaemon tag (there isn't one now) would make it easy for other projects (like Zope3 and ZODB) to use the _same_ zdaemon code. _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org 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 )