-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2012 09:00 PM, Zope tests summarizer wrote:
> [6]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
> https://mail.zope.org/pipermail/zope-tests/2012-March/059167.html
>
>
> [7]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit
> https://mail
2012/3/12 Tres Seaver :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/11/2012 09:00 PM, Zope tests summarizer wrote:
>
>> [6] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
>> https://mail.zope.org/pipermail/zope-tests/2012-March/059167.html
>>
>>
>> [7] FAILED ZTK 1.0dev / Pytho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/12/2012 11:26 AM, Gediminas Paulauskas wrote:
> 2012/3/12 Tres Seaver :
>> AFAIK, ZTK 1.0 is pinned to 'ZODB=3.9.7'; I don't know what is
>> causing something to require 'ZODB>=3.10'. Maybe a newly-released
>> package has snuck into the mix?
>
Today I was unable to build zodbbrowser using its bleeding-edge.cfg
which unpins all package versions. It was unable to install ZODB3.
I can reproduce the same error with pip:
$ virtualenv test
$ test/bin/pip install ZODB3
Downloading/unpacking ZODB3
Downloading ZODB3-3.10.5.win32.zip
On Mon, Mar 12, 2012 at 10:55 PM, Marius Gedminas wrote:
> http://pypi.python.org/pypi/ZODB3/3.10.5 contains various proper win32
> eggs in addition to that .win32.zip. The PyPI page for 3.10.4 did not
> have any weird .win32.zip files.
>
> Can someone please remove that "dumb" binary file which
This is the summary for test reports received on the
zope-tests list between 2012-03-11 00:00:00 UTC and 2012-03-12 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
On Mon, Mar 12, 2012 at 6:13 PM, Hanno Schlichting wrote:
> On Mon, Mar 12, 2012 at 10:55 PM, Marius Gedminas wrote:
>> http://pypi.python.org/pypi/ZODB3/3.10.5 contains various proper win32
>> eggs in addition to that .win32.zip. The PyPI page for 3.10.4 did not
>> have any weird .win32.zip fil
