Dear Package Maintainers

Sleepycat released a new version of its Berkeley DB, version 4.2. It is binary compatible with version 4.1 and 4.0 according to

<http://www.sleepycat.com/download/patchlogs.shtml>

but fixes some serious bugs on MacOS X with more than one processor. From

<http://www.sleepycat.com/update/4.2.52/if.4.2.52.html>

41. Fix a bug where Berkeley DB mutex locking code for OS X was not multi-processor safe. [#8255]


Therefore i think it would be nice if we could update all packages depending on db4 or db41 to db42. This is already in fink unstable and seems to behave well. I also discussed this in short on #fink with Max and he agrees that we should update to the new version.


The packages in question are (-ssl variants omitted):

apache2
apr
berkeleydb-pm560
berkeleydb-pm561
berkeleydb-pm580
berkeleydb-pm581
bind9
cyrus-sasl2
drac1
drac1
gift-openft
kdesdk3
lilypond
lilypond-unstable
open-cobol
open-cobol
openldap-ssl
php4-apache2-ssl
python23
python23-nox
python23-socket-ssl
python23-socket-ssl
samba-ldap
sawfish
sylpheed-ssl

At least that is what a quick grep gave me.

Tell me what you think,
Chris.

PS: Why am i bringing this up?
a) because i think it would help the "fink case" to upgrade
b) since i want to release subversion 0.35.1 (beta) which now recommends db4.2




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to