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.py&&bin/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] SVN: zope.applicationcontrol/tags/3.4.2/ Add tag 3.4.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwIDQoACgkQ+gerLs4ltQ6WxwCg0WKkzb9VMqoY52ciwEYACokT xZUAnjJ08soueHn0OnGQYeAiDPplRVS6 =Ekiu -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] [Checkins] SVN: zope.app.testing/trunk/ Switch doctests to use the stdlib ``doctest`` module.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam GROSZER wrote:
> Hello Tres,
>
> Thursday, June 3, 2010, 5:29:41 PM, you wrote:
>
> TS> -BEGIN PGP SIGNED MESSAGE-
> TS> Hash: SHA1
>
> TS> Adam GROSZER wrote:
>
Log message for revision 110723:
Switch doctests to use the stdlib ``doctest`` module.
o Disuse than the deprecated ``zope.testing.doctest`` variant.
Remove a duplicated import.
Changed:
U zope.app.testing/trunk/CHANGES.txt
U zope.app.testing/trunk/src/zope/app/testing/functional.py
U zope.app.testing/trunk/src/zope/app/testing/tests.py
>>> The problem with this is that it just breaks tests that have accented
>>> unicode characters.
>>>
>>> zope.app.testing.functional.FunctionalDocFileSuite breaks, while
>>> zope.testing.doctest.DocFileSuite works.
>>> I don't remember what was the final decision on deprecating
>>> zope.testing.doctest, but this definitely s*cks.
>>>
>>> Thoughts?
>
> TS> What tests are breaking?
>
> Our apps's tests.
> Excerpt is:
>
> # -*- coding: UTF-8 -*-
>
> >>> mail = mailer.prepareEmail(u"Some subject",
> ... u"Some body éáÉÁ",
> ... u"f...@me.com",
> ... u"t...@you.com")
>
>
> With the stdlib doctest prepareEmail gets
> u'Some body \xc3\xa9\xc3\xa1\xc3\x89\xc3\x81'
> Note, it's unicode() and utf-8 encoded at the same time.
> I guess stdlib doctest does not care about # -*- coding: UTF-8 -*-
The stdlib wants any non-ASCII encoding passed to the testsuite
constructor, e.g. (this is from Lib/test/test_doctest.py in Python 2.6)::
If the tests contain non-ASCII characters, we have to specify which
encoding the file is encoded with. We do so by using the `encoding`
parameter:
>>> suite = doctest.DocFileSuite('test_doctest.txt',
... 'test_doctest2.txt',
... 'test_doctest4.txt',
... encoding='utf-8')
>>> suite.run(unittest.TestResult())
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwIBQYACgkQ+gerLs4ltQ5CUQCffTlpUV1CAHKF0+KjQr3Bh5ri
590AnizdczOZQDVPval0w490lgfOhkUx
=Ayqa
-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] zope.wineggbuilder
On 06/03/2010 09:27 AM, Adam GROSZER wrote: > Hello, > > ( > > Now that the Foundation accepted the proposal for the build server > I'll start a package that > - is configurable via a simple ini/cfg file. >This ini/cfg file holds which packages to check and build with which >pythons. > - checks on pypi if the packages/versions have the win binary eggs, when >missing builds and uploads it. > > I think we need a limited number of packages with some handful pythons. > The script ought to be svn up'ed before run each time. So anyone > having svn committer access could tweak it. > Nits and grits to be elaborated with time. Go Adam! :) -- 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] [Checkins] SVN: zope.app.testing/trunk/ Switch doctests to use the stdlib ``doctest`` module.
Hello Tres, Thursday, June 3, 2010, 5:29:41 PM, you wrote: TS> -BEGIN PGP SIGNED MESSAGE- TS> Hash: SHA1 TS> Adam GROSZER wrote: >>> Log message for revision 110723: >>> Switch doctests to use the stdlib ``doctest`` module. >>> >>> o Disuse than the deprecated ``zope.testing.doctest`` variant. >>> >>> Remove a duplicated import. >>> >>> >>> Changed: >>> U zope.app.testing/trunk/CHANGES.txt >>> U zope.app.testing/trunk/src/zope/app/testing/functional.py >>> U zope.app.testing/trunk/src/zope/app/testing/tests.py >> >> The problem with this is that it just breaks tests that have accented >> unicode characters. >> >> zope.app.testing.functional.FunctionalDocFileSuite breaks, while >> zope.testing.doctest.DocFileSuite works. >> I don't remember what was the final decision on deprecating >> zope.testing.doctest, but this definitely s*cks. >> >> Thoughts? TS> What tests are breaking? Our apps's tests. Excerpt is: # -*- coding: UTF-8 -*- >>> mail = mailer.prepareEmail(u"Some subject", ... u"Some body éáÉÁ", ... u"f...@me.com", ... u"t...@you.com") With the stdlib doctest prepareEmail gets u'Some body \xc3\xa9\xc3\xa1\xc3\x89\xc3\x81' Note, it's unicode() and utf-8 encoded at the same time. I guess stdlib doctest does not care about # -*- coding: UTF-8 -*- -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: A physicist is an atom's way of knowing about atoms. -- George Wald ___ 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] [Checkins] SVN: zope.app.testing/trunk/ Switch doctests to use the stdlib ``doctest`` module.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam GROSZER wrote: >> Log message for revision 110723: >> Switch doctests to use the stdlib ``doctest`` module. >> >> o Disuse than the deprecated ``zope.testing.doctest`` variant. >> >> Remove a duplicated import. >> >> >> Changed: >> U zope.app.testing/trunk/CHANGES.txt >> U zope.app.testing/trunk/src/zope/app/testing/functional.py >> U zope.app.testing/trunk/src/zope/app/testing/tests.py > > The problem with this is that it just breaks tests that have accented > unicode characters. > > zope.app.testing.functional.FunctionalDocFileSuite breaks, while > zope.testing.doctest.DocFileSuite works. > I don't remember what was the final decision on deprecating > zope.testing.doctest, but this definitely s*cks. > > Thoughts? What tests are breaking? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwHyl8ACgkQ+gerLs4ltQ5AAgCdGO0V7xMvY/K9CfR+d+WbM0DN NzcAn1sINi7HAG23EmvdH3gqfPnwjRAd =Avts -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] Help updating the copyright attributions
Hello Tres, Thursday, June 3, 2010, 4:12:07 PM, you wrote: >> >> 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. TS> Perhaps if the package's tests are broken before the cleanup, we should TS> leave the cleanup un-done. We defeinitely want to isolate the TS> "abandoned" projects into a separate list, so leaving them in the TS> nightly nag-mail list helps keep them on the radar for that. I'd say not abandoned, but "buildbot missing+other packages moved under it's ass" is the case here. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: Fools live to regret their words, wise men to regret their silence. - Will Henry ___ 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
On 3 June 2010 16:29, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > 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. > >> Subject: FAILED : Zope Buildbot / ztk_win slave-win >> From: jdriessen at thehealthagency.com >> Date: Wed Jun 2 11:06:50 EDT 2010 >> URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014782.html > > Just guessing, as the error message is in Dutch. These failures appear > to be due to Windows' unwillingness to unlink a file which is still > being held open: perhaps this is a sign of a leaked thread / subprocess? Spot on. Changing the buildslave's language is only possible by re-installing it. In the future we may setup a windows 7 buildslave in English. > BTW, thanks very much for expanding our platform coverage! Our pleasure. -- Jan-Jaap Driessen ___ 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] [Checkins] SVN: zope.app.testing/trunk/ Switch doctests to use the stdlib ``doctest`` module.
Hello Tres, > Log message for revision 110723: > Switch doctests to use the stdlib ``doctest`` module. > > o Disuse than the deprecated ``zope.testing.doctest`` variant. > > Remove a duplicated import. > > > Changed: > U zope.app.testing/trunk/CHANGES.txt > U zope.app.testing/trunk/src/zope/app/testing/functional.py > U zope.app.testing/trunk/src/zope/app/testing/tests.py The problem with this is that it just breaks tests that have accented unicode characters. zope.app.testing.functional.FunctionalDocFileSuite breaks, while zope.testing.doctest.DocFileSuite works. I don't remember what was the final decision on deprecating zope.testing.doctest, but this definitely s*cks. Thoughts? -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: A dear old Quaker lady, distinguished for her youthful appearance, was asked what she used to preserve her appearance. She replied sweetly, 'I use for the lips, truth; for the voice, prayer; for the eyes, pity; for the hand, charity; for the figure, uprightness;and for the heart, love. - Jerry Fleishman ___ 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 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. > Subject: FAILED : Zope Buildbot / ztk_win slave-win > From: jdriessen at thehealthagency.com > Date: Wed Jun 2 11:06:50 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014782.html Just guessing, as the error message is in Dutch. These failures appear to be due to Windows' unwillingness to unlink a file which is still being held open: perhaps this is a sign of a leaked thread / subprocess? BTW, thanks very much for expanding our platform coverage! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwHvGYACgkQ+gerLs4ltQ6mTwCfRHZiQWgLZJQlSpLU5C5iDoa7 0MwAnie19P24XcZEhugMz90p2GhF8qg4 =xdDe -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] zope.browser/trunk/buildout.cfg.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan-Jaap Driessen wrote: > The zope.browser trunk was, until recently (r112978), not part of the > buildbot at dev.thehealthagency.com. > The compattest of the zope toolkit will test the released version of > zope.browser [1]. The compattest does not 'see' the zope.browser > buildout.cfg, as it is only looking at the egg. > Feel free to add repos to the `trunks` section of > svn.zope.org/repos/main/Sandbox/janjaapdriessen/buildbot/buildout.cfg > , the changes will be picked up by dev.thehealthagency.com every hour. > 1) > http://dev.thehealthagency.com/buildbot/builders/ztk%20slave-ubuntu32/builds/70/steps/test/logs/stdio I figured out why we haven't seen failing tests: zope.browser's tests are run from within the zopetoolkit buildout, which bypasses each project's own buildout.cfg. I haven't messed with your buildbot stuff, since that the puzzle is solved (even if it existed only in my own mind). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwHui4ACgkQ+gerLs4ltQ6Y8ACgwSb5txe2fZDFvIlNPDLA4oXo f48Anjx6Xn62fD6uM9vPzd8nqqoxVzTW =L/+e -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] SVN: zope.applicationcontrol/tags/3.4.2/ Add tag 3.4.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwHuLAACgkQ+gerLs4ltQ61IwCfalEJkbhCE6EJqXrALciC6XRS xW0An0Tu4LoHjrpi9ZCs27+88RRNF5S6 =cYh+ -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] Help updating the copyright attributions
-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.py&& bin/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. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwHuDcACgkQ+gerLs4ltQ6QwwCgynh6OFEUr4cj8cQURihYhAAW kjYAmwfPPpmS9EyoE2cOA+CFQZP3Q37d =6u5f -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 )
[Zope-dev] Zope Tests: 36 OK, 8 Failed
Summary of messages to the zope-tests list. Period Wed Jun 2 12:00:00 2010 UTC to Thu Jun 3 12:00:00 2010 UTC. There were 44 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 26 from jdriessen at thehealthagency.com. Test failures - 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 Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:06:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014782.html Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:19:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014788.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:22:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014790.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Thu Jun 3 04:09:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014812.html Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Thu Jun 3 04:21:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014817.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Thu Jun 3 04:24:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014818.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:22:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014776.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:24:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014777.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:33:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014778.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:35:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014780.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:08:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014783.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:10:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014784.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:14:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014785.html Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:14:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014786.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:16:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014787.html Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:21:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014789.html Subject: OK : Zope Buildbot / ztk slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 11:28:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014791.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jun 2 21:28:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014792.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jun 2 21:30:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014793.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 2 21:32:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014794.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 2 21:34:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014795.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 2 21:36:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014796.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 2 21:38:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests
Re: [Zope-dev] zope.browser/trunk/buildout.cfg.
On 3 June 2010 05:34, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Tres Seaver wrote: >> Log message for revision 112947: >> This extra has been gone for a month now. >> >> How were we not seeing failing tests? >> >> >> Changed: >> U zope.browser/trunk/buildout.cfg >> >> -=- >> Modified: zope.browser/trunk/buildout.cfg >> === >> --- zope.browser/trunk/buildout.cfg 2010-06-03 03:12:49 UTC (rev 112946) >> +++ zope.browser/trunk/buildout.cfg 2010-06-03 03:19:48 UTC (rev 112947) >> @@ -4,7 +4,7 @@ >> >> [test] >> recipe = zc.recipe.testrunner >> -eggs = zope.browser [test] >> +eggs = zope.browser >> >> [py] >> recipe = zc.recipe.egg > > Can anybody explain why zope.browser's tests have been passing in the > buildbots? The buildout wouldn't even run with the no-longer-there > extra called out like that. > > > Tres. > - -- > === > Tres Seaver +1 540-429-0999 tsea...@palladion.com > Palladion Software "Excellence by Design" http://palladion.com > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkwHIt4ACgkQ+gerLs4ltQ5CwwCeNWA9cDJZgiOqSAMrZmKY9y+K > CF4AoNM7JmPuU1r7lAZiy2pQ3KMvVCP4 > =jxde > -END PGP SIGNATURE- > > ___ > Zope-Dev maillist - zope-...@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 ) > The zope.browser trunk was, until recently (r112978), not part of the buildbot at dev.thehealthagency.com. The compattest of the zope toolkit will test the released version of zope.browser [1]. The compattest does not 'see' the zope.browser buildout.cfg, as it is only looking at the egg. Feel free to add repos to the `trunks` section of svn.zope.org/repos/main/Sandbox/janjaapdriessen/buildbot/buildout.cfg , the changes will be picked up by dev.thehealthagency.com every hour. 1) http://dev.thehealthagency.com/buildbot/builders/ztk%20slave-ubuntu32/builds/70/steps/test/logs/stdio -- Jan-Jaap Driessen ___ 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.wineggbuilder
Hello, ( Now that the Foundation accepted the proposal for the build server I'll start a package that - is configurable via a simple ini/cfg file. This ini/cfg file holds which packages to check and build with which pythons. - checks on pypi if the packages/versions have the win binary eggs, when missing builds and uploads it. I think we need a limited number of packages with some handful pythons. The script ought to be svn up'ed before run each time. So anyone having svn committer access could tweak it. Nits and grits to be elaborated with time. -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: You have a tendency to feel you are superior to most computers. ___ 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
Hello Christian, Thursday, June 3, 2010, 8:20:10 AM, you wrote: CT> If a file doesn't contain any copyright attribution header, it ignores CT> that file. I'd say rather check for it and warn (unless it's __init__.py). Sh*t can happen easily. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: Violence is permissible even desirable occasionally ___ 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 )
