Re: zope-tests - FAILED: 4, OK: 40, UNKNOWN: 2
Gediminas Paulauskas <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <CAH+bPgg0ZUAVcFT34fhmWBZCqij5EDxqBNicVw-958OsjykjKQ@mail.gmail.com> |
2011/11/20 Tres Seaver <[email protected]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/19/2011 03:18 PM, Wolfgang Schnerring wrote: >> * Tres Seaver <[email protected]> [2011-11-19 14:31]: >>>> [1] UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux >>>> https://mail.zope.org/pipermail/zope-tests/2011-November/052856.html >>>> >>>> >>>> > [2] UNKNOWN UNKNOWN : Zope-trunk-alltests Python-2.6.6 : Linux >>>> https://mail.zope.org/pipermail/zope-tests/2011-November/052857.html >>> >>> >>>> > These two are also tied to the missing zope.publisher 3.13.0 release. >> >> Mea culpa about the missing release; I don't actually know what >> happened, since I use zest.releaser, so there isn't all that much >> that should go wrong, usually. And I certainly didn't notice anything >> was amiss. Sorry about that. I've uploaded the release just now. >> >>>> [3] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit >>>> https://mail.zope.org/pipermail/zope-tests/2011-November/052845.html >>> >>> >>>> > We need to tie ZTK 1.0dev to a backward-compatible branch of >>> zope.publisher (no longer the trunk). >> >> Ah. Right, that makes sense. 3.12.x then? > > Yep: I would make the 3.12 branch from the trunk as of r121101 (tiny fix > after 3.12.6). Then we update the ZTK 1.0 and 1.1 dev setup to use that > branch. I have made a 3.12 branch (from r123091) and updated ZTK 1.0 to use it. ZTK 1.1 is fine. -- Gediminas _______________________________________________ Zope-Dev maillist - [email protected] 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 )