Commit graph

18 commits

Author SHA1 Message Date
wiz
6301213966 Reset MAINTAINER -- he stopped working on pkgsrc. 2005-07-27 16:21:16 +00:00
rillig
f795c2e475 Removed trailing white-space. 2005-05-23 08:26:03 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
agc
671d62d2e2 Add RMD160 digests in addition to SHA1 ones. 2005-02-23 16:33:05 +00:00
recht
367eed19fe Build Python with thread support by default and turn the existing
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
2005-01-23 20:41:45 +00:00
recht
4150812b27 add python as category
ok'd a while back at pkgsrcCon by agc and wiz
2004-07-22 09:15:59 +00:00
snj
3423492e81 Add ${PYSITELIB}/ZEO/* to py-ZODB's PLIST. Bump PKGREVISION to 1.
Closes PR pkg/25567.
2004-05-21 22:00:25 +00:00
seb
00cc0486ea Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymore
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-05-17 21:32:33 +00:00
jlam
59bdf89739 If the ${PKGBASE} of a package doesn't match the token passed to
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that
we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-16 18:23:26 +00:00
jlam
9ff0e10340 Reorder location and setting of BUILDLINK_PACKAGES to match template
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-03-05 19:25:06 +00:00
recht
399e4dc610 update to 3.2.1
provided by Michal Pasternak in PR 24657

What's new in ZODB3 3.2.1?
==========================
Release-date: 12-Feb-2004

The storage comparison matrix (Doc/storages.html) was updated.  It
now has current information about Adaptable Persistence (Ape):
http://hathaway.freezope.org/Software/Ape.


What's new in ZODB3 3.2.1 release candidate 1?
==============================================
Release-date: 20-Jan-2004

FileStorage
-----------

Fixed a serious bug in the new pack implementation.  If pack was
called on the storage and passed a time earlier than a previous pack
time, data could be lost.  In other words, if there are any two pack
calls, where the time argument passed to the second call was earlier
than the first call, data loss could occur.  The bug was fixed by
causing the second call to raise a StorageError before performing any
work.

ZEO
---

Fixed a bug in the ZEO authentication implementation that could cause
a properly authenticated connection to fail unexpectedly with a
ValueError -- "Received message without HMAC."

Fixed a bug in the ZEO server's getInvalidations() method.  If it had
the requested invalidations, it would send all the invalidations in
its queue rather than just the requested ones.  This didn't affect
correctness of the cache, but did cause it to throw out valid data.

Fixed a bug that prevented the -m / --monitor argument from working.

Fixed and enhanced the zeopasswd.py script.  It now runs as a script
and supports command-line arguments for all the options that can be
specified in the configuration file.

What's new in ZODB3 3.2.1 beta 1
================================
Release-date: 18-Nov-2003

This code in this release should be identical to the code in Zope
2.7.0 beta 3.

Changed the ZEO server and control process to work with a single
configuration file; this is now the default way to configure these
processes.  (It's still possible to use separate configuration files.)
The ZEO configuration file can now include a "runner" section used by
the control process and ignored by the ZEO server process itself.  If
present, the control process can use the same configuration file.

Fixed a performance problem in the logging code for the ZEO protocol.
The logging code could call repr() on arbitrarily long lists, even
though it only logged the first 60 bytes; worse, it calls repr() even
if logging is currently disabled.  Fixed to call repr() on individual
elements until the limit is reached.

ReadConflictErrors have an experimental new method, ignore().  If a
database connection raises a read conflict, the current transaction
was eventually be aborted.  If the ignore() method is called, it will
allow a transaction to commit after receiving a read conflict.  This
method should be used with great care, because ignoring read conflicts
may allow inconsistent data to be written to the database.

Several bare string exceptions were changed to raise exception
objects.  All these exceptions were in fairly obscure parts of the
code.

Bug fix for Acquisition in ExtensionClass.  Zope Collector #1056:
aq_acquire() ignored the default argument.

The zdaemon.Daemon module was removed, because it is no longer used by
zdaemon.

The ZEO test suite is more robust.  A variety of small changes were
made that make it less likely to fail on slow or loaded machines.
2004-03-03 16:38:16 +00:00
minskim
d81ac16eca Add buildlink3.mk. Requested by the maintainer in PR pkg/24549. 2004-02-25 23:07:51 +00:00
minskim
648cac2774 Add missing header files to PLIST. Bump PKGREVISION. 2004-02-25 21:24:44 +00:00
minskim
8ef531b3de bl3ify 2004-02-25 20:42:17 +00:00
snj
f5f0eca23b Point to a couple of useful URLs. Requested by Michal Pasternak in
PR pkg/24549.

Also slightly change some wording.
2004-02-24 21:11:12 +00:00
wiz
f709ee9ec6 Remove 3 from PKGNAME, per request from the maintainer. 2004-02-24 15:29:40 +00:00
recht
55c72b7c31 py-ZODB also runs with the unthreaded versions of Python 2.2 and 2.3.
Noted by Michal Pasternak (maintainer) in private email.
2004-01-09 09:12:52 +00:00
recht
0f532a64c2 initial import of py-ZODB 3.2 provided by Michal Pasternak
via pkgsrc-wip

The ZODB package is a Python object persistence system. It provides the
Z Object Database separately from Zope so it can be used in non-Zope related
Python applications to provide transparent object-oriented persistency.
2003-12-06 19:52:43 +00:00