I can reproduce the failures in ExtensionClass and also get some weird
errors while trying to buildout the Acquisition package:
aj...@blackmoon:/develop/repository/svn.zope.org/Acquisition/trunk>
bin/buildout
Develop: '/data/develop/repository/svn.zope.org/Acquisition/trunk/.'
Unused options for b
On 23.07.09 12:10, yuppie wrote:
> Hi!
>
>
> SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
> somewhere on sys.path.
>
> So this no longer works in zopectl:
>
> ZDCTL="$SOFTWARE_HOME/Zope2/Startup/zopectl.py"
> exec "$PYTHON" "$ZDCTL" -C "$CONFIG_FILE" "$@"
>
> Therefore mkzop
http://spamsch.blogspot.com/2009/04/how-to-repair-broken-zodb-poskeyerror.html
-aj
On 23.07.09 12:57, Rupesh P Raj wrote:
> Hi,
>
> Using Zope Debug Console, I used a part of the code fsrefs.py to find
> the oid's of POSKeyError:
>
> fs = FileStorage(path, read_only=1)
> undone = {}
>
>
Summary of messages to the zope-tests list.
Period Wed Jul 22 12:00:00 2009 UTC to Thu Jul 23 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Jul 22 20:53:18 EDT 2009
Hi Jim,
But I am using ZODB 3.4.4 :( Are there any other options? How can I find
where this invalid object is being referenced?
Will something like packing resolve this?
Thanks,
Roopesh
On Thu, Jul 23, 2009 at 4:45 PM, Jim Fulton wrote:
> The object is already gone. It's odd that it is in th
The object is already gone. It's odd that it is in the index.
You can try deleting the object from the index and then saving the
index. You might need to use ZODB 3.9 to do that, as I think __del__
was only recently added to file-storage indexes.
Jim
On Thu, Jul 23, 2009 at 6:57 AM, Rupesh P Raj
Hi,
Using Zope Debug Console, I used a part of the code fsrefs.py to find the
oid's of POSKeyError:
fs = FileStorage(path, read_only=1)
undone = {}
noload = {}
for oid in fs._index.keys():
try:
data, serial = fs.load(oid, "")
except (KeyboardInterrupt
On 7/23/09 12:10 PM, yuppie wrote:
> Hi!
>
>
> SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
> somewhere on sys.path.
>
> So this no longer works in zopectl:
>
> ZDCTL="$SOFTWARE_HOME/Zope2/Startup/zopectl.py"
> exec "$PYTHON" "$ZDCTL" -C "$CONFIG_FILE" "$@"
>
> Therefore mkzo
Hi!
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL="$SOFTWARE_HOME/Zope2/Startup/zopectl.py"
exec "$PYTHON" "$ZDCTL" -C "$CONFIG_FILE" "$@"
Therefore mkzopeinstance now creates something like this:
ZDCTL="/