Well, I have a 3gig ZODB that we have been using fine with Zope 2.5.1 / ZEO 1.0. Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to come up fine, but when trying to start the ZEO client it pretty much sucked. I really should include the log file it produced but it's quite long. I put it up at http://eng.purdue.edu/people/sydelko/zope_2.6a1_log_1 It ended up dying at the end, but that I think I can fix. I'd really like someone to clue me into why everything else complained. --andy.
I have failed as well to upgrade a Zope 2.5.1/ZEO 1.0 installation to 2.6.0a1. I tried to start *the very same instance* that runs successfully under 2.5.1 with 2.6.0a1. This is what I found out: * The Catalog problem you see comes from Products.PluginIndexes.TextIndex.Splitter.ZopeSplitter not exporting 'Splitter' anymore. I should really have been kept for bw compatibility. Workaround is to copy ZopeSplitter's __init__.py from 2.5.1. * ZEO 1.0 ClientStorage does not work and I have no clue why it would not find trigger.py anymore. Do I *need* ZEO 2.0a1 for 2.6.0a1? There is nothing in the release notes. Traceback (most recent call last): File "/Zope-2.6.0a1/z2.py", line 832, in ? asyncore.loop() File "/Zope-2.6.0a1/lib/python/ThreadedAsync/LoopCallback.py", line 100, in loop _start_loop(map) File "/Zope-2.6.0a1/lib/python/ThreadedAsync/LoopCallback.py", line 70, in _start_loop apply(cb, (map,) + args, kw or {}) File "/home/zeo6/lib/python/ZEO/ClientStorage.py", line 215, in becomeAsync File "/home/zeo6/lib/python/ZEO/ClientStorage.py", line 556, in getWakeup ImportError: No module named trigger * Formulator Formulator failed to install due to ZODB conflict errors until I put get_transaction.commit() into Formulator's initialize(); twice, after the help registrations. * New Startup: Will the new startup stuff also be available for ther ZEO server's start.py? Until 2.5.1 I was able to run ZEO server & client in-place (from the same directory). This is harder with 2.6.0. I needed some file permission trickery (which defeats many of the benefits of the new startup) to make it work. * Besides: Z2.pid is created very late. I cannot ./stop a half-started Instance (not even a ZEO client waiting for the server!). Could we create the pid file earlier? Rgds, Stefan --On Montag, 17. Juni 2002 16:23 -0500 Andrew Sydelko <andrew@sydelko.org> wrote:
Well, I have a 3gig ZODB that we have been using fine with Zope 2.5.1 / ZEO 1.0.
Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to come up fine, but when trying to start the ZEO client it pretty much sucked.
I really should include the log file it produced but it's quite long. I put it up at http://eng.purdue.edu/people/sydelko/zope_2.6a1_log_1
It ended up dying at the end, but that I think I can fix.
I'd really like someone to clue me into why everything else complained.
-- BLOWFISH, n. - Preference for beef.
"SHH" == Stefan H Holek <stefan@epy.co.at> writes:
SHH> * ZEO 1.0 ClientStorage does not work and I have no clue why it SHH> would not find trigger.py anymore. Do I *need* ZEO 2.0a1 for 2.6.0a1? SHH> There is nothing in the release notes. ZEO 2.0 and Zope 2.6 are independent releases. You can use Zope 2.6 with ZEO 1.0, and you can use ZEO 2.0 with Zope 2.5. The CVS trunk currently has ZEO 2.0. This change was made a couple weeks ago, independently of the Zope 2.6 release cycle. It may be that you interpreted that change on the ZEO trunk as an indicator that you must use it. I am able to run ZEO 1.0 on Zope 2.6. Does the ZEO test suite pass for you? That's spelled: python utilities/testrunner.py -d lib/python/ZEO assuming that you installed ZEO in the lib/python directory. If they don't pass, can you send me the failures. Most of the ZEO tests run correctly, but I see a few failures caused by a change to the test framework in Zope 2.6. Here's an example: ERROR: checkUndoCommitVersion (testZEO.ZEOFileStorageTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/home/jeremy/src/Zope/lib/python/ZODB/tests/TransactionalUndoVersionStorage.py", line 113, in checkUndoCommitVersion revid = self._dostore(oid, revid, description='packable%d' % i) TypeError: _dostore() got an unexpected keyword argument 'description' I'll fix these problems for a ZEO 1.0.1, but they don't indicate a serious problem. SHH> Traceback (most recent call last): SHH> File "/Zope-2.6.0a1/z2.py", line 832, in ? SHH> asyncore.loop() SHH> File SHH> "/Zope-2.6.0a1/lib/python/ThreadedAsync/LoopCallback.py", SHH> line 100, SHH> in loop SHH> _start_loop(map) SHH> File SHH> "/Zope-2.6.0a1/lib/python/ThreadedAsync/LoopCallback.py", SHH> line 70, SHH> in _start_loop SHH> apply(cb, (map,) + args, kw or {}) SHH> File "/home/zeo6/lib/python/ZEO/ClientStorage.py", line 215, SHH> in SHH> becomeAsync SHH> File "/home/zeo6/lib/python/ZEO/ClientStorage.py", line 556, SHH> in getWakeup SHH> ImportError: No module named trigger If you check the ZEO 1.0 tarball, you'll find a trigger module in it. Perhaps something was corrupted in your installation. SHH> * New Startup: SHH> Will the new startup stuff also be available for ther ZEO SHH> server's start.py? Until 2.5.1 I was able to run ZEO server & SHH> client in-place (from the same directory). This is harder with SHH> 2.6.0. I needed some file permission trickery (which defeats SHH> many of the benefits of the new startup) to make it work. I don't quite follow. Can you explain exactly what went wrong when you tried to run the server and client from the same directory? I assume this is a problem with ZEO 2.0. What do you mean by "the new startup stuff"? Jeremy
--On Dienstag, 18. Juni 2002 11:28 -0400 Jeremy Hylton <jeremy@zope.com> wrote:
I am able to run ZEO 1.0 on Zope 2.6. Does the ZEO test suite pass for you? That's spelled:
Yes, the tests pass with the two exceptions you mentioned.
If you check the ZEO 1.0 tarball, you'll find a trigger module in it. Perhaps something was corrupted in your installation.
I am starting the *very same* instance that works with 2.5.1 under 2.6.0a1. Yes, trigger.py is there. I am stumped myself. The client starts up completely, but than blows up on the trigger import. This is the logfile: 2002-06-18T19:35:33 INFO(0) client Trying to connect to server: ('127.0.0.1', 8091) ------ 2002-06-18T19:35:33 INFO(0) ClientStorage Connected to storage ------ 2002-06-18T19:35:33 INFO(0) ZODB Opening database for mounting: '142837952_1021730381.442598' ------ 2002-06-18T19:35:33 INFO(0) ZODB Mounted database '142837952_1021730381.442598' at /temp_folder ------ 2002-06-18T19:35:43 INFO(0) ZServer HTTP server started at Tue Jun 18 19:35:43 2002 Hostname: phoenix Port: 8080 Traceback (most recent call last): File "/Zope-2.6.0a1-src/z2.py", line 831, in ? asyncore.loop() File "/Zope-2.6.0a1-src/lib/python/ThreadedAsync/LoopCallback.py", line 100, in loop _start_loop(map) File "/Zope-2.6.0a1-src/lib/python/ThreadedAsync/LoopCallback.py", line 70, in _start_loop apply(cb, (map,) + args, kw or {}) File "/home/zeo6/lib/python/ZEO/ClientStorage.py", line 215, in becomeAsync File "/home/zeo6/lib/python/ZEO/ClientStorage.py", line 555, in getWakeup ImportError: No module named trigger I am going to investigate whether this is an artefact of my instance but I am not sure where to start...
I don't quite follow. Can you explain exactly what went wrong when you tried to run the server and client from the same directory? I assume this is a problem with ZEO 2.0. What do you mean by "the new startup stuff"?
- Collector #1: UNIX security fixes: make starting Zope as 'root' secure, stop using 'nobody', warn of insecure umasks Things like setting the sticky bit on var/, chdir to var/, umask 077 in the start file, creating the pid file *before* dropping root. Maybe more. When running ZEO 1.0 Data.fs.lock (and Data.fs.tmp) cannot be owned by root. ZEO_SERVER.pid is owned by the unprivileged user as well. Ok, "many" is overstated, I admit. ;-) Thanks, Stefan -- BLOWFISH, n. - Preference for beef.
To get rid of the ImportError I had to add 'import trigger' to ZEO/__init__.py I do not currently have an explanation as to why it works with 2.5.1 but stopped doing so with 2.6.0 (at least for me). Python is the very same (2.1.3, LFS enabled). Just to mention it again: ZE0 1.0, Zope 2.6.0a1 Rgds, Stefan -- BLOWFISH, n. - Preference for beef.
Stefan H. Holek wrote:
Z2.pid is created very late. I cannot ./stop a half-started Instance (not even a ZEO client waiting for the server!). Could we create the pid file earlier?
Actually Z2.pid *is* now created earlier than with 2.5.1, the setuid stuff for root startups was moved after the Z2.pid creation to stop a potential security issue. I don't see any reason it couldn't be created before the servers are started, however. Others may have reasons why.
"AS" == Andrew Sydelko <andrew@sydelko.org> writes:
AS> Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to AS> come up fine, but when trying to start the ZEO client it pretty AS> much sucked. It looks like you would have had the same problems without ZEO. It would be helpful if you could try running Zope without ZEO, just with FileStorage. AS> I really should include the log file it produced but it's quite AS> long. I put it up at AS> http://eng.purdue.edu/people/sydelko/zope_2.6a1_log_1 AS> It ended up dying at the end, but that I think I can fix. AS> I'd really like someone to clue me into why everything else AS> complained. The errors in the log are all about failures to import specific modules. (Let me know if I missed something else.) Failed to import class Splitter from module Products.PluginIndexes.TextIndex.Splitter.ZopeSplitter When I import Products...ZopeSplitter, I see a module with a Splitter attribute bound to a function. The other import problem I see is Zope Could not import Products.HTMLDocument Is HTMLDocument a standard product or a 3rd party product? I don't see one in my 2.6 checkout. If it's 3rd part, then I expect it needs to be upgrade to work with 2.6. Jeremy
On Tue, 18 Jun 2002 11:20:21 -0400 "Jeremy Hylton" <jeremy@zope.com> wrote:
"AS" == Andrew Sydelko <andrew@sydelko.org> writes:
AS> Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to AS> come up fine, but when trying to start the ZEO client it pretty AS> much sucked.
It looks like you would have had the same problems without ZEO. It would be helpful if you could try running Zope without ZEO, just with FileStorage.
Hmm... The first time I copied the 3gig Data.fs over and tried to start Zope a few times. After fiddling with the permissions of the var directory it finally started, but the Data.fs was only 2MB! So I copied it again. And once again, the 3gig Data.fs is blown away! What am I doing wrong??? What are the permissions of the "var" folder supposed to be? I'm starting Zope with: python Zope/z2.py -w 8080 -F 8081 -W 8082 -u httpd
AS> I really should include the log file it produced but it's quite AS> long. I put it up at AS> http://eng.purdue.edu/people/sydelko/zope_2.6a1_log_1
AS> It ended up dying at the end, but that I think I can fix.
AS> I'd really like someone to clue me into why everything else AS> complained.
The errors in the log are all about failures to import specific modules. (Let me know if I missed something else.)
Failed to import class Splitter from module Products.PluginIndexes.TextIndex.Splitter.ZopeSplitter
When I import Products...ZopeSplitter, I see a module with a Splitter attribute bound to a function.
I don't understand what you're saying here. Do you mean it works without complaining for you? In the past I have deleted all the Products that were in the Products Control Panel to fix a similar bug. Is that the case here as well?
The other import problem I see is
Zope Could not import Products.HTMLDocument
Is HTMLDocument a standard product or a 3rd party product? I don't see one in my 2.6 checkout. If it's 3rd part, then I expect it needs to be upgrade to work with 2.6.
HTMLDocument is a 3rd party product. Is there a document that says what has changed enough since 2.5.1 that would break products? and how to fix them? This is frustrating... --andy.
Andrew Sydelko wrote:
The errors in the log are all about failures to import specific modules. (Let me know if I missed something else.)
Failed to import class Splitter from module Products.PluginIndexes.TextIndex.Splitter.ZopeSplitter
When I import Products...ZopeSplitter, I see a module with a Splitter attribute bound to a function.
I don't understand what you're saying here. Do you mean it works without complaining for you? In the past I have deleted all the Products that were in the Products Control Panel to fix a similar bug. Is that the case here as well?
I explained in the Collector how to fix this problem back in March. http://collector.zope.org/Zope/181 -- Steve Alexander
"AS" == Andrew Sydelko <andrew@sydelko.org> writes:
AS> On Tue, 18 Jun 2002 11:20:21 -0400 "Jeremy Hylton" AS> <jeremy@zope.com> wrote:
> "AS" == Andrew Sydelko <andrew@sydelko.org> writes:
AS> Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to AS> come up fine, but when trying to start the ZEO client it pretty AS> much sucked.
It looks like you would have had the same problems without ZEO. It would be helpful if you could try running Zope without ZEO, just with FileStorage.
AS> Hmm... The first time I copied the 3gig Data.fs over and tried AS> to start Zope a few times. After fiddling with the permissions AS> of the var directory it finally started, but the Data.fs was AS> only 2MB! AS> So I copied it again. And once again, the 3gig Data.fs is blown AS> away! What am I doing wrong??? What are the permissions of the AS> "var" folder supposed to be? I'm starting Zope with: It wouldn't surprise me if this is a completely unrelated problem. Any chance that the python your using to test doesn't have large file support? Check by importing test.test_largefile. We recently discovered that there's a bad interaction between ZODB and Python without large file support running on a platform that supports large files. In this specific configuration, os.path.exists() returns false for files >2 GB and ZODB creates a new Data.fs. Jeremy
Jeremy Hylton wrote:
We recently discovered that there's a bad interaction between ZODB and Python without large file support running on a platform that supports large files. In this specific configuration, os.path.exists() returns false for files >2 GB and ZODB creates a new Data.fs.
Wow... "bad" is not a strong enough word for this bug, especially if you run into it without a backup. How about "harrowing". ;-) Shane
On Tue, 18 Jun 2002 12:19:19 -0400 "Jeremy Hylton" <jeremy@zope.com> wrote:
It wouldn't surprise me if this is a completely unrelated problem. Any chance that the python your using to test doesn't have large file support? Check by importing test.test_largefile.
Yeah, you're right, I don't have largefile support. But I normally don't need it because it's just a ZEO client. And I've been trying to get python to compile with largefile support and I can't. I'm using Debian woody (and no, I don't want to use the installed python2.1 package). Can someone tell me exactly how to compile python 2.1.3 with LFS support?
We recently discovered that there's a bad interaction between ZODB and Python without large file support running on a platform that supports large files. In this specific configuration, os.path.exists() returns false for files >2 GB and ZODB creates a new Data.fs.
Yeah, that's a bad thing. I'm glad this wasn't my only copy (although it takes 15 minutes to get a new copy since it's so large.) --andy.
"AS" == Andrew Sydelko <andrew@sydelko.org> writes:
AS> Can someone tell me exactly how to compile python 2.1.3 with LFS AS> support? I don't have the URL handy, but it's section 8.1.1 of the manual IIRC. Look for large file support in the library reference. Worked for me without problem on a RH 7.2 system. Jeremy
On Tue, 18 Jun 2002 23:01:57 -0400 "Jeremy Hylton" <jeremy@zope.com> wrote:
"AS" == Andrew Sydelko <andrew@sydelko.org> writes:
AS> Can someone tell me exactly how to compile python 2.1.3 with LFS AS> support?
I don't have the URL handy, but it's section 8.1.1 of the manual IIRC. Look for large file support in the library reference.
Worked for me without problem on a RH 7.2 system.
Yeah, and it's not working for me. I will try some more tomorrow... An earlier question was: What are the correct permissions for the "Zope/var" folder with a startup of "python z2.py -u httpd" --andy.
"JH" == Jeremy Hylton <jeremy@zope.com> writes:
JH> I don't have the URL handy, but it's section 8.1.1 of the JH> manual IIRC. Look for large file support in the library JH> reference. http://www.python.org/doc/current/lib/posix-large-files.html -Barry
Hi, I'm not really sure if this is the right place to discuss this, so if you think I should go somewhere else, let me know. Zope can be used for a lot of different purposes, but one of them definitely is groupware and there a lot of people I have been trying to convince to use Zope prefer Exchange for the simple reason of integration with Outlook. Now, Outlook is not as closed as you might expect and I have been thinking about ways to integrate Outlook with Zope. If you could make Outlook cooperate with Zope in a way that Outlook would create and use public folders that are stored on Zope, lots of really interesting applications would be possible, ie like sharing agenda's and having a zope interface to it too for html rendering and allowing emails to be moved from outlook directly to Zope. I see three strategies to achieve this: 1) Add a MAPI server interface to Zope. With a plug in for Outlook like the one from Bynari Outlook users could then manipulate Zope objects. The MAPI interface would have to render Zope objects as MAPI folders and messages. 2) Reverse engineer Exchange and implement the relevant MAPI interfaces in Zope. This would be the most transparent way, but it would also be very complicated and would depend a lot on the whims of Microsoft as far as interface changes go, never a very confortable position. 3) Write a plug in a la Bynari's InsightConnector, but then one that doesn't communicate with MAPI, but directly with Zope, using one of the standard by Zope supported protocols. So, I would prefer the third one, but I don't have much of clue how to do this. Does anybody have any pointers where to start, ie documents or example implementations. Are there any projects like this already going on? Any help is appreciated. Douwe Osinga
Add a fourth to your list: WebDAV, which is making progress towards replacing the native Exchange protocol. I have a book on building exchange applications that documents this pretty well. Greg Stein, as OSCOM in Zurich, gave a talk in which he noted Microsoft's intentions to do this. In fact, this is the way that Ximian avoided reverse-engineering the Exchange protocol in Ximian Connector. If you install the Outlook Web Access support in Exchange 2000, you turn on DAV as an API for Exchange. You want the reverse, though, and I Outlook (AFAIK) isn't able to create a folder that is pointed at an Exchange-via-DAV source. Thus, you'd have to do some scripting. But that's a lot easier (and less prone to crashes) than writing a MAPI source, I believe. MS has an ADO provider for DAV, so you could treat this as integrating ADO and Outlook. I spent some time over Christmas doing some Python scripting of Outlook data. --Paul douwe@oberon.nl wrote:
Hi,
I'm not really sure if this is the right place to discuss this, so if you think I should go somewhere else, let me know.
Zope can be used for a lot of different purposes, but one of them definitely is groupware and there a lot of people I have been trying to convince to use Zope prefer Exchange for the simple reason of integration with Outlook.
Now, Outlook is not as closed as you might expect and I have been thinking about ways to integrate Outlook with Zope. If you could make Outlook cooperate with Zope in a way that Outlook would create and use public folders that are stored on Zope, lots of really interesting applications would be possible, ie like sharing agenda's and having a zope interface to it too for html rendering and allowing emails to be moved from outlook directly to Zope.
I see three strategies to achieve this: 1) Add a MAPI server interface to Zope. With a plug in for Outlook like the one from Bynari Outlook users could then manipulate Zope objects. The MAPI interface would have to render Zope objects as MAPI folders and messages.
2) Reverse engineer Exchange and implement the relevant MAPI interfaces in Zope. This would be the most transparent way, but it would also be very complicated and would depend a lot on the whims of Microsoft as far as interface changes go, never a very confortable position.
3) Write a plug in a la Bynari's InsightConnector, but then one that doesn't communicate with MAPI, but directly with Zope, using one of the standard by Zope supported protocols.
So, I would prefer the third one, but I don't have much of clue how to do this. Does anybody have any pointers where to start, ie documents or example implementations. Are there any projects like this already going on?
Any help is appreciated.
Douwe Osinga
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
"BAW" == Barry A Warsaw <barry@zope.com> writes: "JH" == Jeremy Hylton <jeremy@zope.com> writes:
JH> I don't have the URL handy, but it's section 8.1.1 of the manual JH> IIRC. Look for large file support in the library reference. BAW> http://www.python.org/doc/current/lib/posix-large-files.html Actually, these are the instructions for Python 2.2.1. Most Zope users will want http://www.python.org/doc/2.1.3/lib/posix-large-files.html The instructions have changed! Jeremy
On 6/19/02 1:29 PM, "Jeremy Hylton" <jeremy@zope.com> wrote:
"BAW" == Barry A Warsaw <barry@zope.com> writes: "JH" == Jeremy Hylton <jeremy@zope.com> writes:
JH> I don't have the URL handy, but it's section 8.1.1 of the manual JH> IIRC. Look for large file support in the library reference.
BAW> http://www.python.org/doc/current/lib/posix-large-files.html
Actually, these are the instructions for Python 2.2.1. Most Zope users will want http://www.python.org/doc/2.1.3/lib/posix-large-files.html
The instructions have changed!
We have Python on FreeBSD, installed via the ports system. Is there a way to tell if a given version of Python has large file support built in via the interpreter (ie - is there a magic flag in os|posix that can be checked?). The machine is serving as a ZEO server to clients in various data centers. It had a 1.5 Gigabyte Data.fs as of last night (prior to packing). I want to make sure we don't run into an overwritten Data.fs situation. -- Jeffrey P Shell www.cuemedia.com
"JPS" == Jeffrey P Shell <Jeffrey> writes:
JPS> We have Python on FreeBSD, installed via the ports system. Is JPS> there a way to tell if a given version of Python has large file JPS> support built in via the interpreter (ie - is there a magic JPS> flag in os|posix that can be checked?). The best thing to do is "import test.test_largefile" which will run all the large file tests. There's no magic flag or status attribute available. JPS> The machine is serving as a ZEO server to clients in various JPS> data centers. It had a 1.5 Gigabyte Data.fs as of last night JPS> (prior to packing). I want to make sure we don't run into an JPS> overwritten Data.fs situation. If there is only a single server, then you shouldn't run into the overwritten data.fs problem. Either the server will fail when it hits 2GB, because it doesn't have LFS, or it will not fail, because it does have LFS. The overwrite would only occur if you changed the Python binary from one that did have LFS to one that didn't have LFS. (Perhaps by moving the file to a different machine with a different binary.) Jeremy
Andrew Sydelko wrote:
On Tue, 18 Jun 2002 12:19:19 -0400 "Jeremy Hylton" <jeremy@zope.com> wrote:
Can someone tell me exactly how to compile python 2.1.3 with LFS support?
Hi Andrew Maybe this Howto by Seb Beacon could help ? http://www.zope.org/Members/beacon/install_instructions --- Flynt
"F" == flynt <flynt@gmx.ch> writes:
F> Maybe this Howto by Seb Beacon could help ? F> http://www.zope.org/Members/beacon/install_instructions These instructions don't look correct to me. The problem is that they don't follow the Python 2.1.x instructions for building with large file support. While it might work on some platforms, I expect the instructions in the docs are better. I certainly wouldn't recommend editing config.h by hand. Also, it mentions --without-pymalloc and --with-threads which are already the defaults for Python 2.1 and 2.2. Jeremy
On Tuesday 18 Jun 2002 5:19 pm, Jeremy Hylton wrote:
We recently discovered that there's a bad interaction between ZODB and Python without large file support running on a platform that supports large files. In this specific configuration, os.path.exists() returns false for files >2 GB and ZODB creates a new Data.fs.
I have run into similar problems before - where the file did not exist, and a hard error would have been nicer than creating a new database. This has bugged me enough that I decided to do it differently in DirectoryStorage; there is a seperate mkds script.
"AS" == Andrew Sydelko <andrew@sydelko.org> writes:
Failed to import class Splitter from module Products.PluginIndexes.TextIndex.Splitter.ZopeSplitter
When I import Products...ZopeSplitter, I see a module with a Splitter attribute bound to a function.
AS> I don't understand what you're saying here. Do you mean it works AS> without complaining for you? In the past I have deleted all the AS> Products that were in the Products Control Panel to fix a AS> similar bug. Is that the case here as well? The problem is that the alpha release had a bug that made it impossible to load Splitter objects from the database. Andreas fixed the bug on Monday, so you could copy the changed file Zope/lib/python/Products/PluginIndexes/TextIndex/Splitter/ZopeSplitter/__init__.py or you could delete whatever objects are related to the text index.
The other import problem I see is
Zope Could not import Products.HTMLDocument
Is HTMLDocument a standard product or a 3rd party product? I don't see one in my 2.6 checkout. If it's 3rd part, then I expect it needs to be upgrade to work with 2.6.
AS> HTMLDocument is a 3rd party product. Is there a document that AS> says what has changed enough since 2.5.1 that would break AS> products? and how to fix them? The traceback in the log indicates that the problem is related to InterfaceBase. (IIRC, I don't have that browser window open any more.) I think that Jim changed the Interface package just before the alpha, backporting changes from the Zope3 package. Maybe Jim can summarize what people need to do to update their code. AS> This is frustrating... I agree that it is frusterating, but I think it's hard to have an alpha release that works perfectly with all known third party extensions. Jeremy
participants (12)
-
Andrew Sydelko -
barry＠zope.com -
douwe＠oberon.nl -
flynt -
Jeffrey P Shell -
jeremy＠zope.com -
Matt Behrens -
Paul Everitt -
Shane Hathaway -
Stefan H. Holek -
Steve Alexander -
Toby Dickenson