Re: [Zope-dev] Help updating the copyright attributions
On 06/03/2010 04:12 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan-Wijbrand Kolman wrote: On 6/3/10 8:40 AM, Christian Theune wrote: On 06/02/2010 05:19 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan-Wijbrand Kolman wrote: On 6/2/10 15:11 , Christian Theune wrote: Hi, the ZF needs to finish updating the copyright attributions to state that the Zope code now belongs to the foundation. I've prepared some scripts to help with monitoring which packages need to be updated and also a helper to update most cases. Can you point me to these scripts? $ svn co svn+ssh://svn.zope.org/repos/main/zope.repositorypolicy/trunk\ ~/projects/Zope/zrp $ cd zrp $ /opt/Python-2.6.5/bin/python bootstrap.pybin/buildout $ cd /path/to/other/project $ ~/projects/Zope/zrp/bin/zope-org-check-project ... $ ~/projects/Zope/zrp/bin/zope-org-fix-project ... $ ~/projects/Zope/zrp/bin/zope-org-check-project (should be empty) $ bin/test -v --all $ svn add LICENSE.txt COPYRIGHT.txt $ svn commit -m Conform to repository policy. How do you deal with packages that have broken tests due to broken dependencies? I had z3c.recipe.paster with failing tests. These failed both before and after the copyright-fix. So, assumed I could go ahead with the copyright fix itself. I do want to help out on the important copyright fixing, but I do not have the time right now to also fix each of the packages that I come across. Maybe we could/should make note of the broken packages somewhere. Perhaps if the package's tests are broken before the cleanup, we should leave the cleanup un-done. We defeinitely want to isolate the abandoned projects into a separate list, so leaving them in the nightly nag-mail list helps keep them on the radar for that. Hmm. With the goal of getting the copyright attributions up do date as soon as possible, I think running the tests is a good sanity check. If the same (amount of) tests fail after the fix as before, then I'd go ahead. I agree we should track abandoned projects, though, but I'd separate that issue from the (C) update. This needs to get to a point where we can talk about the whole repository and say it's been updated. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 36 OK, 8 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/3/10 16:29 , Tres Seaver wrote: Zope Tests Summarizer wrote: Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:33:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014779.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:36:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014781.html These failures occur only on OSX: I have no idea how to diagnose them. The ComponentLookupError for '__main__.IFooMarker' shouldn't be able to fail at all. I cannot reproduce those failures using the bin/testall script from the Zope2 egg. I'm guessing the buildbot uses the same script since the number of tests executed matches what I see in my sandboxes. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwIrt4ACgkQRAx5nvEhZLKP5ACfVSpfyR6E70GfGq6k2enNf8ev 6fkAn1S78VG/jmnOPPehW7SC8RmAfeSb =OibX -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Copyright update for z3c.ajax: no buildout, no headers
On 6/3/10 8:20 AM, Christian Theune wrote: Hi, I just fixed up z3c.ajax and it has a quirk that the check doesn't know about: If a file doesn't contain any copyright attribution header, it ignores that file. In this case, z3c.ajax has no headers at all. no setup.py. no buildout. I added the missing license and copyright files to silence the check but I'm relatively sure there's an edge case here. Thoughts? Any ideas yet on situations like these? I found several packages now that do not contain any copyright headers in the python modules, or, sometimes they do in the package itself, but not in the package's test modules. I decided to just go ahead for now silencing the check, my reasoning being: if the copyright-checkscript is updated at some point in time to also check for copyright-less modules, we automatically will have list again of project that need fixing in that regard. OK? regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 25 OK, 4 Failed
Summary of messages to the zope-tests list. Period Thu Jun 3 12:00:00 2010 UTC to Fri Jun 4 12:00:00 2010 UTC. There were 29 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 1 from ct at gocept.com, 10 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED: Repository policy check found errors in 556 projects From: ct at gocept.com Date: Thu Jun 3 21:15:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014820.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Fri Jun 4 04:20:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014844.html Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Fri Jun 4 04:26:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014846.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Fri Jun 4 04:28:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014847.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jun 3 21:29:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014821.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jun 3 21:31:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014822.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Thu Jun 3 21:33:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014823.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Thu Jun 3 21:35:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014824.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Thu Jun 3 21:37:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014825.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Thu Jun 3 21:39:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014826.html Subject: OK : BlueBream template / Python2.7b2 32bit linux From: ccomb at free.fr Date: Thu Jun 3 22:00:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014827.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Thu Jun 3 22:00:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014828.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Thu Jun 3 22:01:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014830.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Thu Jun 3 22:01:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014829.html Subject: OK : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Fri Jun 4 00:06:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014831.html Subject: OK : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Fri Jun 4 00:09:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014832.html Subject: OK : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Fri Jun 4 00:10:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014833.html Subject: OK : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Fri Jun 4 00:29:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014834.html Subject: OK : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Fri Jun 4 00:52:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014835.html Subject: OK : ZTK 1.0 / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Fri Jun 4 01:45:00 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014836.html Subject: OK : ZTK 1.0 / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Fri Jun 4 01:45:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014837.html Subject: OK : ZTK 1.0 / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Fri Jun 4 01:45:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014838.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Fri Jun 4 04:05:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014839.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Fri Jun 4 04:07:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014840.html Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Fri Jun 4 04:11:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014841.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Fri Jun 4
Re: [Zope-dev] Copyright update for z3c.ajax: no buildout, no headers
On 06/04/2010 12:49 PM, Jan-Wijbrand Kolman wrote: On 6/3/10 8:20 AM, Christian Theune wrote: Hi, I just fixed up z3c.ajax and it has a quirk that the check doesn't know about: If a file doesn't contain any copyright attribution header, it ignores that file. In this case, z3c.ajax has no headers at all. no setup.py. no buildout. I added the missing license and copyright files to silence the check but I'm relatively sure there's an edge case here. Thoughts? Any ideas yet on situations like these? I found several packages now that do not contain any copyright headers in the python modules, or, sometimes they do in the package itself, but not in the package's test modules. I decided to just go ahead for now silencing the check, my reasoning being: if the copyright-checkscript is updated at some point in time to also check for copyright-less modules, we automatically will have list again of project that need fixing in that regard. OK? That's what I think and did this morning, too. -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug tracker for zc.table
Hello, I've stubmled upon an issue in zc.table, it can't deal with spaces in column names when sorting (since it uses space as the field separator to pass the sort_on information). I don't have time to look into this right now, but I'd like not to forget it. Is there someplace on Launchpad where I could file a bug for future reference? Wolfgang ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 2.12 and Broken classes
Hello, I observe following change between Zope 2.11 and Zope 2.12, and I am struggling finding a solution in Zope 2.12 for it: 1. Create two objects in a folder in your ZODB, 2. Remove the FS code of those objects, and restart your Zope, 3. Select one of those object and delete it (ZMI, code, whatever), 4. It work in Zope 2.11. In Zope 1.12 you get a pickling error as the folder (container) cannot be pickled, as it is trying to pickle the missing object that have not been deleted at step 3. Does this ring a bell to anyone ? Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 and Broken classes
On Fri, 4 Jun 2010 16:50:59 +0200 Sylvain Viollon sylv...@infrae.com wrote: Hello, Hello, I observe following change between Zope 2.11 and Zope 2.12, and I am struggling finding a solution in Zope 2.12 for it: 1. Create two objects in a folder in your ZODB, 2. Remove the FS code of those objects, and restart your Zope, 3. Select one of those object and delete it (ZMI, code, whatever), 4. It work in Zope 2.11. In Zope 1.12 you get a pickling error as the folder (container) cannot be pickled, as it is trying to pickle the missing object that have not been deleted at step 3. After more testing, I have more information. This bug has been introduced by the release 2.13.0 of ExtensionClass and Persistance packages. Running 2.12.0 of packages make it disappear. I guess I should report this on launchpad ? Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 and Broken classes
On Fri, Jun 4, 2010 at 5:33 PM, Sylvain Viollon sylv...@infrae.com wrote: After more testing, I have more information. This bug has been introduced by the release 2.13.0 of ExtensionClass and Persistance packages. Running 2.12.0 of packages make it disappear. I guess I should report this on launchpad ? Please do. I'm not sure where the bug actually is, we probably need to change the Broken implementation in OFS or unify it with the one from ZODB to fix this. Not sure how ZODB deals with storing references to persistent objects (the optimized kind storing the class name in it) and how that relates to broken objects. This isn't really a new problem, it probably happened to any normal non-extension class already in the past. Those are just less frequent in use. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 and Broken classes
On Fri, 4 Jun 2010 17:38:41 +0200 Hanno Schlichting ha...@hannosch.eu wrote: On Fri, Jun 4, 2010 at 5:33 PM, Sylvain Viollon sylv...@infrae.com wrote: After more testing, I have more information. This bug has been introduced by the release 2.13.0 of ExtensionClass and Persistance packages. Running 2.12.0 of packages make it disappear. I guess I should report this on launchpad ? I reported the bug: https://bugs.edge.launchpad.net/zope2/+bug/589756 Please do. I'm not sure where the bug actually is, we probably need to change the Broken implementation in OFS or unify it with the one from ZODB to fix this. Not sure how ZODB deals with storing references to persistent objects (the optimized kind storing the class name in it) and how that relates to broken objects. It check for subclasses of ZODB.broken.Broken, where OFS.Unintalled.BrokenClass based one are not. But this is only for things inheriting of persistent, where Extension classes (like OFS.Uninstalled.Broken...) does come from Persitance. This isn't really a new problem, it probably happened to any normal non-extension class already in the past. Those are just less frequent in use. Well, it worked before. It's recent optimization done in ExtensionClass that breaked it. Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope-Dev Digest, Vol 83, Issue 6
Tres Seaver wrote: Christian Theune wrote: On 06/03/2010 05:05 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Log message for revision 112936: Add tag 3.4.2 Changed: A zope.applicationcontrol/tags/3.4.2/ I have *no* idea what these messages are about. I was certainly not tagging releases for zope.applicationcontrol today. Worst case: someone has your key? Not too likely -- more likely some weird bzr-svn bug, as the new tags are showing up in projects where I had been merging bzr branches with janitorial cleanups: they appear immediately after the real commit. I have switched over to avoiding 'bzr merge' for now, which seems to have stopped the faux tag creation. I have a theory, but am not sure how to test it: I think that I recall for both affected projects (zope.applicationcontrol, zope.cachedescriptors), I mistakenly attempted to merge a bzr branch for a completely different project. When the merge failed, it left my local branch apparently clean, but it might have messed up the heuristics / bookkeeping which bzr-svn uses to infer tags for the project. FWIW, Tres. Consider using shared repositories with a fresh branch for each merge: http://wiki.bazaar.canonical.com/SharedRepositoryTutorial Basically, you do something like this: bzr init-repo zope.applicationcontrol --format=rich-root-pack #last I checked, bzr-svn liked this format, you can also --format=svn cd zope.applicationcontrol bzr branch lp:zope.applicationcontrol #bzr looks for .bzr in ., which tells it there is a shared storage What this does is allow you to have multiple local branches of something without wasting full repo storage on each one. This func goes back at least to BitKeeper and may be able to use hardlinks to further reduce storage redundancy, though that can lead to pain, suffering, anger, etc.. Best, J ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope-Dev Digest, Vol 83, Issue 6
On Fri, Jun 4, 2010 at 9:06 AM, Justin Ryan justin.r...@reliefgarden.orgwrote: Consider using shared repositories with a fresh branch for each merge: http://wiki.bazaar.canonical.com/SharedRepositoryTutorial Basically, you do something like this: bzr init-repo zope.applicationcontrol --format=rich-root-pack #last I checked, bzr-svn liked this format, you can also --format=svn cd zope.applicationcontrol bzr branch lp:zope.applicationcontrol #bzr looks for .bzr in ., which tells it there is a shared storage Whups, you'd do something like: bzr branch svn://svn.zope.org/public/zope.applicationcontrolmerge-something-branch This gives you a branch merge-something-branch within your zope.applicationcontrol shared repo. What this does is allow you to have multiple local branches of something without wasting full repo storage on each one. This func goes back at least to BitKeeper and may be able to use hardlinks to further reduce storage redundancy, though that can lead to pain, suffering, anger, etc.. Best, J ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )