From: Benny M. <ben...@gm...> - 2008-11-04 08:46:56
|
Ok, I will not have python 2.6 on my system in the near future. Martin, can you open a bug ticket to follow this? I started a wiki page: http://gramps-project.org/wiki/index.php?title=Python2.6 So we can collect python 2.6 issues (normally spring distro's will still ship python 2.5 in tandem), and the bug item can use the wiki page for discussion. Benny 2008/11/4 Martin Steer <mar...@ma...> > "Benny Malengier" <ben...@gm...> writes: > > > It looks like we will have to do some changes to support bsddb 4.7.x, > > and hence probably python 2.6 (as used already in archlinux). My guess > > is that for the releases in the spring this will be an important > > issue! > > It's already spring here. > > > > > Point 1: > > 4.6: db.DB_LOG_AUTOREMOVE > > 4.7: db.DB_LOG_AUTO_REMOVE > > > > Point 2: > > ??? > > Martin, can you tell us what the error is that is raised? > > invalidargerr (22, "Invalid argument -- DB_ENV->log_set_config: > DB_LOG_IN_MEMORY: method not permitted after handle's open method") > 29618: ERROR: _Tool.py: line 255: Failed to start tool. > Traceback (most recent call last): > File "/usr/share/gramps/PluginUtils/_Tool.py", line 251, in gui_tool > tool_class(dbstate, uistate, options_class, name, callback) > File "/usr/share/gramps/plugins/RebuildRefMap.py", line 83, in __init__ > self.db.reindex_reference_map(self.update) > File "/usr/share/gramps/gen/db/dbdir.py", line 1020, in > reindex_reference_map > self.__reindex_reference_map(callback) > File "/usr/share/gramps/gen/db/dbdir.py", line 1083, in > __reindex_reference_map > transaction = self.transaction_begin(batch=True, no_magic=True) > File "/usr/share/gramps/gen/db/dbdir.py", line 1555, in transaction_begin > raise Errors.DbError(msg) > DbError: <unprintable DbError object> > > > Perhaps you can also point to the google page where you found the > > attribute changed name? > > It was just some talk about an svn patch. The following is better: > > < > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/upgrade.4.7/log.html > > > > "In the Berkeley DB 4.7 release, the logging subsystem is configured > using the DB_ENV->log_set_config method instead of the previously used > DB_ENV->set_flags method. > > The DB_ENV->set_flags method no longer accepts the flags DB_DIRECT_LOG, > DB_DSYNC_LOG, DB_LOG_INMEMORY or DB_LOG_AUTOREMOVE. Applications should > be modified to use the equivalent flags accepted by the > DB_ENV->log_set_config method. > > Previous DB_ENV->set_flags flag Replacement DB_ENV->log_set_config flag > DB_DIRECT_LOG DB_LOG_DIRECT > DB_DSYNC_LOG DB_LOG_DSYNC > DB_LOG_INMEMORY DB_LOG_IN_MEMORY > DB_LOG_AUTOREMOVE DB_LOG_AUTO_REMOVE" > > Also: > > < > http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_log_set_config.html > > > > > > > Well, if you don't feel like doing this, no probs. Someone of the core > > team will have to install python 2.6 and new bsddb one of these days > > and start hacking. > > > > I'm happy to help if I can. In dbdir.py I changed two occurrences of: > > self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) > > to: > > self.env.log_set_config(db.DB_LOG_AUTO_REMOVE, 1) > > which seems to be okay, but can't find instances of DB_LOG_INMEMORY, > suggested by the error message, so don't know what to do next. > > By the way, I also noticed a warning on startup that I don't remember > seeing before: > > /usr/share/gramps/ThumbNails.py:31: DeprecationWarning: the md5 module is > deprecated; use hashlib instead > > -- > Martin > |