- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
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.
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.
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.
