[ZODB-Dev] Re: VersionLockError

[Florent Guillaume]

(Still replying to myself...)

Of course the problem I feared is still here, we have a lot of objects 
(IITreeSet and some buckets) that are still in the version, and provoke 
an error...

I think I'll have to do a complete rebuild of the catalog.

Florent

Florent Guillaume wrote:
> Ok, thanks to a suggestion from Chris Kratz I managed to fix it and 
> remove the version (I re-modified the object, saved the version and 
> deleted it).
> 
> (I'm sorry, I tried the archives but incorrectly googled for 
> lists.zope.org instead of mail.zope.org...)
> 
> Has this ZODB bug be fixed in later revisions ?
> 
> Florent
> 
> 
> Florent Guillaume wrote:
> 
>> By the way this is with Zope 2.6.1 Linux binary version.
>>
>> Florent Guillaume wrote:
>>
>>> Hi,
>>>
>>> We're having a problem here with a version that doesn't want to go away.
>>> A version /test was created, then some content modified (a CMF skin 
>>> customized) and discarded in this version. Some other people were 
>>> concurrently working elsewhere on the site creating documents, but 
>>> outside of the version.
>>>
>>> Now we're in a state where the version itself says:
>>>   No unsaved work has been done in this version.
>>> The Version Management in the control panel says:
>>>   There are no non-empty versions.
>>> But nevertheless we have one object in the site with a version/lock 
>>> icon in the ZMI, and trying to modify it gives:
>>>   VersionLockError: ("'\\x00\\x00\\x00\\x00\\x00\\x005Z'", '/test')
>>>
>>> Attempting an undo on the version/locked object gives
>>>   Couldn't undo change to '\x00\x00\x00\x00\x00\x005Z' because 
>>> Current and undone versions differ
>>>
>>> So how can we make the version go away?
>>>
>>> Thanks,
>>> Florent
>>>
>>
> 

-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87  http://nuxeo.com  mailto:fg at nuxeo.com