summaryrefslogtreecommitdiff
path: root/databases/py-ZODB
AgeCommit message (Collapse)AuthorFilesLines
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
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).
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
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.
2006-02-17Add missing files to PLIST. Bump PKGREVISION.wiz2-22/+36
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-3/+4
2005-07-27Reset MAINTAINER -- he stopped working on pkgsrc.wiz1-2/+2
2005-05-23Removed trailing white-space.rillig1-1/+1
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2005-01-23Build Python with thread support by default and turn the existingrecht1-2/+2
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.
2004-07-22add python as categoryrecht1-2/+2
ok'd a while back at pkgsrcCon by agc and wiz
2004-05-21Add ${PYSITELIB}/ZEO/* to py-ZODB's PLIST. Bump PKGREVISION to 1.snj2-2/+177
Closes PR pkg/25567.
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-9/+7
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-03-03update to 3.2.1recht3-113/+120
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-02-25Add buildlink3.mk. Requested by the maintainer in PR pkg/24549.minskim1-0/+22
2004-02-25Add missing header files to PLIST. Bump PKGREVISION.minskim2-2/+6
2004-02-25bl3ifyminskim1-2/+2
2004-02-24Point to a couple of useful URLs. Requested by Michal Pasternak insnj1-2/+8
PR pkg/24549. Also slightly change some wording.
2004-02-24Remove 3 from PKGNAME, per request from the maintainer.wiz1-2/+2
2004-01-09py-ZODB also runs with the unthreaded versions of Python 2.2 and 2.3.recht1-2/+2
Noted by Michal Pasternak (maintainer) in private email.
2003-12-06initial import of py-ZODB 3.2 provided by Michal Pasternakrecht5-0/+532
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-01 05:13:06 +0000