Your message dated Mon, 08 Dec 2008 03:02:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#506621: fixed in gramps 3.0.4-1
has caused the Debian Bug report #506621,
regarding Patch gramps to work with BerkeleyDB 4.7
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
506621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506621
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gramps
Version: 3.0.3-1
Tags: patch

I have included a patch from Fedora which allows gramps to work with
BerkeleyDB 4.7:
http://cvs.fedoraproject.org/viewvc//devel/gramps/gramps-3.0.3-dbcrash.patch?view=markup

                   Joseph Smidt

--- src/gen/db/dbdir.py 2008/04/05 22:04:30 10487
+++ src/gen/db/dbdir.py 2008/11/13 08:07:59 11296
@@ -480,8 +480,13 @@
        # These env settings are only needed for Txn environment
        self.env.set_lk_max_locks(25000)
        self.env.set_lk_max_objects(25000)
-        self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1)  # clean up unused logs
-
+ +        if db.version() < (4, 7):
+            # Python 2.5 log settings
+            self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs
+        else:
+            # Python 2.6 log settings (db version 4.7.25)
+            self.env.set_flags(db.DB_LOG_AUTO_REMOVE, 1)
        # The DB_PRIVATE flag must go if we ever move to multi-user setup
        env_flags = db.DB_CREATE | db.DB_PRIVATE |\
                    db.DB_INIT_MPOOL | db.DB_INIT_LOCK |\
@@ -1556,7 +1561,8 @@
        transaction = BdbTransaction(msg, self.undodb, batch, no_magic)
        if transaction.batch:
            self.env.txn_checkpoint()
-            self.env.set_flags(db.DB_TXN_NOSYNC, 1)      # async txn
+            if db.version() < (4, 7):
+                self.env.set_flags(db.DB_TXN_NOSYNC, 1)      # async txn

            if self.secondary_connected and not transaction.no_magic:
                # Disconnect unneeded secondary indices
@@ -1594,7 +1600,8 @@
        self.txn.commit()
        if transaction.batch:
            self.env.txn_checkpoint()
-            self.env.set_flags(db.DB_TXN_NOSYNC, 0)      # sync txn
+            if db.version() < (4, 7):
+                self.env.set_flags(db.DB_TXN_NOSYNC, 0)      # sync txn

            if not transaction.no_magic:
                # create new secondary indices to replace the ones removed
@@ -1697,7 +1704,12 @@
        # These env settings are only needed for Txn environment
        self.env.set_lk_max_locks(25000)
        self.env.set_lk_max_objects(25000)
-        self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1)  # clean up unused logs
+        if db.version() < (4, 7):
+            # Python 2.5 log settings
+            self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs
+        else:
+            # Python 2.6 log settings (db version 4.7.25)
+            self.env.set_flags(db.DB_LOG_AUTO_REMOVE, 1)

        # The DB_PRIVATE flag must go if we ever move to multi-user setup
        env_flags = db.DB_CREATE | db.DB_PRIVATE |\



--- End Message ---
--- Begin Message ---
Source: gramps
Source-Version: 3.0.4-1

We believe that the bug you reported is fixed in the latest version of
gramps, which is due to be installed in the Debian FTP archive:

gramps_3.0.4-1.diff.gz
  to pool/main/g/gramps/gramps_3.0.4-1.diff.gz
gramps_3.0.4-1.dsc
  to pool/main/g/gramps/gramps_3.0.4-1.dsc
gramps_3.0.4-1_all.deb
  to pool/main/g/gramps/gramps_3.0.4-1_all.deb
gramps_3.0.4.orig.tar.gz
  to pool/main/g/gramps/gramps_3.0.4.orig.tar.gz



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.
James A. Treacy <[EMAIL PROTECTED]> (supplier of updated gramps 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.8
Date: Sun, 07 Dec 2008 21:39:55 -0500
Source: gramps
Binary: gramps
Architecture: source all
Version: 3.0.4-1
Distribution: unstable
Urgency: low
Maintainer: James A. Treacy <[EMAIL PROTECTED]>
Changed-By: James A. Treacy <[EMAIL PROTECTED]>
Description: 
 gramps     - Genealogical Research and Analysis Management Program
Closes: 506621 506818
Changes: 
 gramps (3.0.4-1) unstable; urgency=low
 .
   * New upstream version. Closes: #506621, #506818
Checksums-Sha1: 
 bb9970eceff8b4567bfa5c22adfbcf404cad7881 1165 gramps_3.0.4-1.dsc
 42501cb29b7b6b60006db0ded4a732e838becd45 5830725 gramps_3.0.4.orig.tar.gz
 7c53f1110c19e027355877f24e4d11db67db1f75 11060 gramps_3.0.4-1.diff.gz
 84073ad1b734aeb7c367ea604fa38d83d9c43b58 4696796 gramps_3.0.4-1_all.deb
Checksums-Sha256: 
 926cfda381409511fce4d4fd48419229f48b025b9be234413d394d38c763ebf6 1165 
gramps_3.0.4-1.dsc
 cca1262bb4e15fd018342c49bbe07a1cac96b1307bffdff10c34f3c1518fd792 5830725 
gramps_3.0.4.orig.tar.gz
 c096d26bbd5ac8c5940ae27af6f1c1f10271c4dfcf99d55b69110a9688c2bcc9 11060 
gramps_3.0.4-1.diff.gz
 7c23bc36f12fc493436d0ed926d5451604996f7f2766fc1ed2ebfc3359ad65cd 4696796 
gramps_3.0.4-1_all.deb
Files: 
 8ea84d997bc7b4e8cfb0d96a5d742e72 1165 gnome optional gramps_3.0.4-1.dsc
 7d27020f391ba333b8a9bd490e5bf56e 5830725 gnome optional 
gramps_3.0.4.orig.tar.gz
 ec8525be02728b8d51b7fc5d11168847 11060 gnome optional gramps_3.0.4-1.diff.gz
 5dd19323b79bace411b2dabb873f8434 4696796 gnome optional gramps_3.0.4-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk8irMACgkQE+4lteS3JKQFmACgmuQhD1SudDc+zh045FhXxeMM
pX8AoMbWYKS6ltJgNhSuwm1ucutFCofA
=jAb7
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to