-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> Christian Theune wrote:
>> Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
>>> I saw the error reports about zope.security and got talked to from a few
>>> people that they had severe problems managing around this. I removed the
>>> 3.4b4 distribution from download.zope.org to allow them to continue
>>> using zopeproject and grokproject until we find a fix.
>>> I wasn't sure about that, so if someone has even worse problems now,
>>> please speak up and I'll put the package back into place again. I hope I
>>> didn't cause any more problems than exist already.
>> Ok. As this affected more packages and Wichert found out how to deal
>> with this in the buildout.cfg of grokproject (zopeproject and other
>> buildout-based projects should be able to derive a workaround for this
>> until it's fixed.)
>> See http://paste.plone.org/16261 for the full buildout.cfg. The most
>> important lines are 11 to 15:
>> recipe = zc.zope3recipes>=0.5.3:application
>> eggs =
> Does this mean the package won't get removed? I just prefer to use a
> situation where I don't get the broken egg in the first place.
You're hosed, then: people are going to release eggs which break
"downstream" applications (think libs in Debian unstable). Until we
segreate the "known good" set away from the "I just did something cool,
please test" set, this problem is unavoidable.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope3-dev mailing list