ASynK: Announcing experimental support for BBDB file format ver 9

[Sriram Karra]

There has been some interest in having ASynK support BBDB file format ver 9 support in ASynK. I have just pushed out an experimental branch called 'bbdb-format-v9' which should seamlessly start supporting v9. You should not see any change to your workflow, including the case where you had a BBDB file that you were syncing with another database (google contacts, say), and that BBDB file was recently upgraded to format ver 9 by BBDBv3.

Caveat: please treat this as alpha quality code for testing purposes. That said I am very interested in hearing how it works for you, and happy to address bug reports.

Happy syncing.

-Karra

[Barak A. Pearlmutter]

Sriram,

Assuming no one else is already doing so, would it make sense for me
to package ASynK for Debian (and hence Ubuntu etc)? On the one hand,
I'm packaging bbdb3 so I could make sure they stay in sync, e.g., with
file formats and such. On the other hand, I'm not a Python person, and
I assume ASynK will be making a Python3 transition soon in light of
Unicode considerations etc, but I wouldn't be much help in shaking
things down.

--Barak.

[Roland Winkler]

On Sat May 26 2018 Sriram Karra wrote:
> There has been some interest in having ASynK support BBDB file
> format ver 9 support in ASynK. I have just pushed out an

> experimental branch called 'bbdb -format-v9' which should
> seamlessly start supporting v9.

I do not know anything about how ASynK works. I only have a vague
understanding that it lives in its own world in the sense that it
uses python and not elisp. However, as always, I'll be happy to
hear about suggestions to improve BBDB, which includes its
interaction with other packages (that may be written in elisp or
other languages).

Roland

[Barak A. Pearlmutter]

Will do!

Any hints regarding configuration, safety, etc, would be welcome.

I'll do the initial packaging on branch "debian" of
https://github.com/barak/ASynK

(And if it slips off my radar, feel free to remind me.)

--Barak.

[Barak A. Pearlmutter]

I've pushed a preliminary packaging to https://github.com/barak/ASynK
branch "debian", if anyone could build/install/test it I'd be
appreciative.

git clone https://github.com/barak/ASynK
cd ASynK
git checkout debian
dpkg-checkbuilddeps
(apt-get install anthing-missing)
fakeroot debian/rules binary
dpkg --install ../asynk*.deb
asynk --test-this-backup-your-data-first

I've called it version 2.2.0 per the git tag, even though setup.py has
version='0.4.1'

--Barak.

[Sriram Karra]

Hi Barak,

H. Dieter Wilhelm (who chimed in earlier on this thread) did reach out to me earlier on the same topic, but I do not recall where that landed. I am totally happy to have a stable version of ASynK made into a debian package, but I have not used Debian or any Linux on any personal machine in ages. So I am not sure I can do anything to help. 

One thing though is I have not yet merged the support for bbdb format ver9 into master. That might be a more appropriate thing to do. Let me take a look at one or two bug reports I got with that experimental branch, and make a formal release and you can repackage as you see fit.

-Sriram

--
Find ASynK useful? Consider leaving a tip at this Bitcoin address: 1KarraEGixRyScZ9qFHdekxNkgpPTuzWBc
---
You received this message because you are subscribed to the Google Groups "ASynK Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to asynk+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dave Goldberg]

I've finally got around to trying this. I cloned the repository, did git branch -u remotes/origin/bbdb-format-v9 and git checkout -f. Built it per the directions, and set up a profile. I am now able to get data moving in both directions (bbdb and google) but the bbdb file always ends up corrupted. I've reset a couple times (restore bbdb from backup and delete/recreate the profile and restore google to yesterday) and tried unidirectional sync in both directions (by changing the order when recreating the profile). It seems that when I go from bbdb to google entries with multiple phone numbers which are stored as arrays instead of strings get screwed up as quotes are added in correctly (at least that's my interpretation). If I go from google to bbdb some entries error on "something is not a list" but I can't figure out what's wrong looking at the entry.

Is this still just a case of the software's not there yet (and if so I'd be happy to help with testing as I'm not much of a coder) or am I doing something wrong and getting the wrong code?

Thanks,

--
Dave Goldberg
david.g...@verizon.net