On Wed, 27 Nov 2002 05:54:27 -0500
[EMAIL PROTECTED] wrote:
Zope-Dev -- confirmation of subscription -- request 616673
We have received a request from 193.63.123.17 for subscription of your
email address, [EMAIL PROTECTED], to the [EMAIL PROTECTED]
mailing list. To confirm the request,
The DateTime bug in 2.6.0 breaks all of my sites. This must be true for very
many other people.
If we collectively want use of Zope to multiply 10x, I don't think it's a great
idea to let a major bug like that stay in the latest-and-greatest release.
Can we have a bugfix release?
seb
Someone posted already a fix for this problem. It should not be hard to fix
this single problem by exchanging the DateTime.py file on your sites
-aj
--On Mittwoch, 27. November 2002 11:18 + seb bacon [EMAIL PROTECTED]
wrote:
The DateTime bug in 2.6.0 breaks all of my sites. This must be
Someone posted already a fix for this problem. It should not be hard to fix
this single problem by exchanging the DateTime.py file on your sites
That really doesn't matter. The official release on
http://www.zope.org/Products still has the bug.
--
/Magnus
Andreas Jung wrote:
Someone posted already a fix for this problem. It should not be hard to fix
this single problem by exchanging the DateTime.py file on your sites
I'll echo my earlier comment: Whatever happened to release early, release often?
Why is this not happening with Zope?
cheers,
From: Andreas Jung [EMAIL PROTECTED]
Someone posted already a fix for this problem. It should not be hard to
fix
this single problem by exchanging the DateTime.py file on your sites
Yep, it's on http://www.zope.org/Members/regebro/ somewhere.
But I agree that it's time for a bugfix release
Someone posted already a fix for this problem. It should not be
hard to fix this single problem by exchanging the DateTime.py file
on your sites
I'll echo my earlier comment: Whatever happened to release early,
release often?
Why is this not happening with Zope?
Because it doesn't
Guido van Rossum wrote:
Why is this not happening with Zope?
Because it doesn't apply. Release early, release often is for
bleeding edge developers.
Says who? I thought the idea behind it was to get the releases out early, so you
can find the bugs faster and get the releases more stable
Says who? I thought the idea behind it was to get the releases out
early, so you can find the bugs faster and get the releases more
stable more quickly...
I guess what I'm saying is that for a version 2.x.y, x should behave
as you describe while y should go up as often as a bug is
On 27 Nov 2002, 11:18 seb bacon wrote:
Can we have a bugfix release?
Me too. I'd like to get the fix for Issue 597
(http://collector.zope.org/Zope/597) in such a bugfix release.
ZCTextIndex, quite different from the old TextIndex, currently is
almost unusuable outside the US, because it
From: Andreas Jung [EMAIL PROTECTED]
Someone posted already a fix for this problem. It should not be hard to
fix
this single problem by exchanging the DateTime.py file on your sites
Yep, it's on http://www.zope.org/Members/regebro/ somewhere.
But I agree that it's time for a bugfix
Hi, started seeing quite a few of these showing up in one of our server's logs:
--
2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not remove
documentId -869933785 from index companies. This should not happen.
exceptions.KeyError: -869933785
This is Zope 2.6.0, hence the
--On Mittwoch, 27. November 2002 18:08 + Chris Withers
[EMAIL PROTECTED] wrote:
Hi, started seeing quite a few of these showing up in one of our server's
logs:
--
2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not
remove documentId -869933785 from index companies.
On Wed, 2002-11-27 at 12:31, Wolfgang Strobl wrote:
On 27 Nov 2002, 11:18 seb bacon wrote:
Can we have a bugfix release?
Me too. I'd like to get the fix for Issue 597
(http://collector.zope.org/Zope/597) in such a bugfix release.
ZCTextIndex, quite different from the old TextIndex,
I guess what I'm saying is that for a version 2.x.y, x should behave
as you describe while y should go up as often as a bug is discovered
and fixed...
That means we either waste a lot more time doing releases, or the
releases become a lot more shoddy, hardly more than a snapshot from
--On Mittwoch, 27. November 2002 13:17 -0500 Chris McDonough
[EMAIL PROTECTED] wrote:
On Wed, 2002-11-27 at 12:31, Wolfgang Strobl wrote:
On 27 Nov 2002, 11:18 seb bacon wrote:
Can we have a bugfix release?
Me too. I'd like to get the fix for Issue 597
(http://collector.zope.org/Zope/597)
I am assigned to fix this. I will make time to do it over the holiday. Time
has been extremely short for me (and basically all of us at ZC) lately, so
your patience is appreciated.
I'm assuming we will not have bug day before 2.6.1, but perhaps one shortly
thereafter is in order?
-Casey
On
From: Chris McDonough [EMAIL PROTECTED]
Sometimes
going through the CVS logs for the module in which the bug is in, you
can tell who has most recently been involved in that code and send them
an email about the bug.
Heh. Never worked for me. Ah well, now I can fix things myself instead. :-)
Andreas Jung wrote:
--On Mittwoch, 27. November 2002 18:08 + Chris Withers
[EMAIL PROTECTED] wrote:
Hi, started seeing quite a few of these showing up in one of our
server's
logs:
--
2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not
remove documentId -869933785
This usually happens when there are duplicates in the indexed keywords and
the record isn't updated before unindexing. Shouldn't cause any problems,
though it isn't nice. This can be easily fixed by changing the KeywordIndex'
index_object method to make keywords unique before indexing.
-
Hi !
Zope 2.6.0 have a problem for non 'iso-8859-1' user.
And Collector 623 is still incollect now.
http://collector.zope.org/Zope/623
It's serious problem for CJK(I'm Japanese).
So I make patch for 2.6.0.
http://www005.upp.so-net.ne.jp/zope260-i18n-20021123.diff
1.Install
$ cd $(INST_HOME)
$
Sorry
http://www005.upp.so-net.ne.jp/nakagami/zope260-i18n-20021123.diff
http://www005.upp.so-net.ne.jp/zope260-i18n-20021123.diff
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
--On Donnerstag, 28. November 2002 01:48 +0100 Wolfram Kerber
[EMAIL PROTECTED] wrote:
This usually happens when there are duplicates in the indexed keywords and
the record isn't updated before unindexing. Shouldn't cause any problems,
though it isn't nice. This can be easily fixed by changing
23 matches
Mail list logo