Re: bbdb database corrupted
On Mon, Apr 8, 2013 at 1:06 AM, Julien Cubizolles j.cubizol...@free.frwrote: bbdb can't access a lot of my contacts in the .bbdb file anymore. I'm not sure exactly when it started but every time I run bbdb, I get for example: --8---cut here---start-8--- bbdb-format-address-default: Wrong type argument: sequencep, PARIS\ --8---cut here---end---8--- Julien, It is very likely an issue with ASynK. Over the past month I had pushed a number of fixes that handle proper quoting of special characters. When was the last time you ran ASynK? Can you find the record in your .bbdb which has the above text (PARIS) and send that record to me off list (you can change any names or other details - the structure and special characters are what I am interested in). It will help me confirm if one of the recent fixes will help you or not. Also please note - and this is important - before you run ASynK any more move out all the backups from ~/.asynk/backups/ directory. This is to prevent ASynK from deleting any of them in case they are over 7 days old (the default). -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: bbdb database corrupted
On Sun Apr 7 2013 Julien Cubizolles wrote: bbdb can't access a lot of my contacts in the .bbdb file anymore. I'm not sure exactly when it started but every time I run bbdb, I get for example: --8---cut here---start-8--- bbdb-format-address-default: Wrong type argument: sequencep, PARIS\ --8---cut here---end---8--- The message is always about a field with a backslash in it. I'm not sure these backslashes were there before or if they got added behind my back, by emacs or ASynk (that i use to synchronize with google contacts). For the records: It seems rather unlikely to me that the above problem is caused by some recent change in BBDB. However, to look into such a possiblity the starting point would always be a more complete lisp backtrace. -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: bbdb database corrupted
Roland Winkler wink...@gnu.org writes: For the records: It seems rather unlikely to me that the above problem is caused by some recent change in BBDB. However, to look into such a possiblity the starting point would always be a more complete lisp backtrace. You're right, I got a confirmation from the ASynk developper that the corruption has occured through ASynk, and was able to recover a working database through Asynk backups. -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
