Your message dated Fri, 14 Sep 2007 21:17:14 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#441152: fixed in db4.4 4.4.20-10 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: libdb4.4 Version: 4.4.20-9 Severity: grave Justification: totally breaks postgrey (don't hesitate to shoot back if it turns out that postgrey or libberkeleydb-perl is using libdb4.4 the wrong way :-) See #441069: txn_begin seems to fail with 4.4.20-9. Downgrading to 4.4.20-8 makes the problem go away (doesn't matter which version the database was created with.) cheers -- vbi P.S.: I didn't reassign the bug because I want to keep it open against postgrey as documentation for "my" users. -- Penetration testing ... [is] expensive, and you'll get a thick report when the testing is done. [...] Probably the safest thing you can do with the report, after you read it, is shred it. -- Bruce Schneier http://www.schneier.com/blog/archives/2007/05/is_penetration.html
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---Source: db4.4 Source-Version: 4.4.20-10 We believe that the bug you reported is fixed in the latest version of db4.4, which is due to be installed in the Debian FTP archive: db4.4-doc_4.4.20-10_all.deb to pool/main/d/db4.4/db4.4-doc_4.4.20-10_all.deb db4.4-util_4.4.20-10_amd64.deb to pool/main/d/db4.4/db4.4-util_4.4.20-10_amd64.deb db4.4_4.4.20-10.diff.gz to pool/main/d/db4.4/db4.4_4.4.20-10.diff.gz db4.4_4.4.20-10.dsc to pool/main/d/db4.4/db4.4_4.4.20-10.dsc libdb4.4++-dev_4.4.20-10_amd64.deb to pool/main/d/db4.4/libdb4.4++-dev_4.4.20-10_amd64.deb libdb4.4++_4.4.20-10_amd64.deb to pool/main/d/db4.4/libdb4.4++_4.4.20-10_amd64.deb libdb4.4-dev_4.4.20-10_amd64.deb to pool/main/d/db4.4/libdb4.4-dev_4.4.20-10_amd64.deb libdb4.4-tcl_4.4.20-10_amd64.deb to pool/main/d/db4.4/libdb4.4-tcl_4.4.20-10_amd64.deb libdb4.4_4.4.20-10_amd64.deb to pool/main/d/db4.4/libdb4.4_4.4.20-10_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Weimer <[EMAIL PROTECTED]> (supplier of updated db4.4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Fri, 14 Sep 2007 21:39:44 +0200 Source: db4.4 Binary: libdb4.4-tcl libdb4.4 libdb4.4++ db4.4-util db4.4-doc libdb4.4++-dev libdb4.4-dev Architecture: source amd64 all Version: 4.4.20-10 Distribution: unstable Urgency: low Maintainer: Debian Berkeley DB Maintainers <[EMAIL PROTECTED]> Changed-By: Florian Weimer <[EMAIL PROTECTED]> Description: db4.4-doc - Berkeley v4.4 Database Documentation [html] db4.4-util - Berkeley v4.4 Database Utilities libdb4.4 - Berkeley v4.4 Database Libraries [runtime] libdb4.4++ - Berkeley v4.4 Database Libraries for C++ [runtime] libdb4.4++-dev - Berkeley v4.4 Database Libraries for C++ [development] libdb4.4-dev - Berkeley v4.4 Database Libraries [development] libdb4.4-tcl - Berkeley v4.4 Database Libraries for TCL [module] Closes: 441152 Changes: db4.4 (4.4.20-10) unstable; urgency=low . * Revert "Revert mutexes to upstream defaults.". Closes: #441152. . If you have already converted your databases to the changed environment format of 4.4.20-9, run "db4.4_recover -h /path/to/environment" for each affected database environment. Updates from 4.4.20-8.1 and earlier do not need this step. Files: e1a0da40c9f08c2d3fe9775f0ad107c7 1163 libs standard db4.4_4.4.20-10.dsc 8a60c8ff2118ff5653d7468ed97b2b19 24741 libs standard db4.4_4.4.20-10.diff.gz 02a0aaaa7b52a055abdee8d5e3a051a3 4901668 libs optional db4.4-doc_4.4.20-10_all.deb 719451c48f0400fba01d9d28f18cb2a0 487038 libs standard libdb4.4_4.4.20-10_amd64.deb 995ac15390611559f2442480a0c62d7f 607478 libdevel extra libdb4.4-dev_4.4.20-10_amd64.deb 3c6f5dd1af28036a1238c1bb2271cebe 520284 libs optional libdb4.4++_4.4.20-10_amd64.deb f3098b5719b15c1f0660ef130e081848 1242804 libdevel extra libdb4.4++-dev_4.4.20-10_amd64.deb c9954ffdf4c387723d059c75214ab209 1209176 interpreters extra libdb4.4-tcl_4.4.20-10_amd64.deb ed44d1271a7e385ad1d65f657b191bbc 99620 utils optional db4.4-util_4.4.20-10_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRursdb97/wQC1SS+AQIELQf+N9DG3Jp/9qMGRpGMZM5wPuXHVoUqLF2T VsoqayIyvvYwCohzVWuOH3kMx73SjR9YA+AIo5/KdpjyPZmAj9DMjVPAZE8+651X BD4nggAHruFJwvZ8tXfH+UeP+gzcQSmjwySHNJx0ls6x8w6yiiFWUvoHiQoun2Kb vsC2eJMTuWz7fyUPv6Y8u/O7EOCU65sQIA65qxIKgL0HaNvtPVfv2w/VOz2J6ja2 5XvNJWv/6uF/6Lt6fqZC+LQGfllBLozB0PWAXr0AkyqrIdKkJUAHwWI+FfAhcIDv Lif5ByBymI+OopECmZpbD+v9DxA86f4c8boyhw8EzY9Atn50P6gQKQ== =JJ0G -----END PGP SIGNATURE-----
--- End Message ---
