versions of objects.

uncommitted data is placed.

  only affects zpkg.

distutils-compatible method but it failed miserably.

(hang). This was accomonied by a critical log message along the
lines of: "RuntimeError: dictionary changed size during iteration".

actively preventing it.

r77078 | gary | 2007-06-25 16:39:45 -0400 (Mon, 25 Jun 2007) | 1 line
r77010 | gary | 2007-06-24 13:19:18 -0400 (Sun, 24 Jun 2007) | 2 lines
r76977 | gary | 2007-06-23 06:57:51 -0400 (Sat, 23 Jun 2007) | 1 line
r76953 | gary | 2007-06-23 00:20:55 -0400 (Sat, 23 Jun 2007) | 1 line

Document conflict resolution. bugfix the situation in which comparing
persistent objects (for instance, as members in BTree set or keys of
BTree) might cause data inconsistency during conflict resolution.
support multidatabase references in conflict resolution.  make it
possible to examine oid and (in some situations) database name of
persistent object references so that I can add some code to
zope.app.keyreference to support these objects (so BTree conflict
resolution can happen at all when keyreferences are used).

2.4 and 2.5.

and 2.5.

Added APIs for removing committed blob data that makes files writable
before removing them and updated code that removes committed blobs or
blob directories to use them.

stack traces.

spurious failures.

that it is specific to blobs. Added logging when we have to copy.

willing to copy when renaming fails.

savepoint storage.

Also added a test for the normal blob case.

if we can't link.

Added support for copying to blob cache when renaming fails.

committed file name.

Make sure that uncommitted data gets cleaned up if w blob is GCed
without committing.