-----BEGIN PGP SIGNED MESSAGE-----
On 11/14/2011 04:50 PM, Christophe Combelles wrote:
> Le 14/11/2011 01:52, Christophe Combelles a écrit :
>> Le 13/11/2011 14:22, Tres Seaver a écrit :
>>> If somebody who cares about the KGS could look at these failures
>>> and figure out why knew versions are slipping into the mix, that
>>> would be great. Otherwise, we should just quit testing it.
>> The initial build process of the kgs has no versions pinned, so it
>> was being built with some of the latests libs that fail under
>> python2.4. I have added versions in the toplevel buildout.cfg so
>> that it shouldn't fail again.
>> I don't know if someone is interested but we have enough minor
>> versions upgrade available to be able to release a maintenance
>> versions of the KGS: 3.4.2
don't understand why r123334 was needed to "fix" the KGS buildout: I
thought the KGS was "pinned" by virtue of using its 'versions.cfg' file:
(Actually, I don't know what the intended relationship is between that
file and http://download.zope.org/zope3.4/3.4.1/controlled-packages.cfg ).
Actually, I thought we were supposed to have a PyPI-like index which
ensured that no unwanted versions would creep in, e.g.::
Can somebody who remembers how that dance was supposed to work enlighten us?
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -