On Thu, Jan 05, 2012 at 07:20:19PM -0600, Bruce Guenter wrote:
> > Are you using 0.2x opensync, or the devel tree (upcoming 0.4x)?
>
> I've been using 0.39 on Gentoo.
If you're using the devel tree of opensync (all 0.3x versions are development
versions), you might consider switching to the latest git version.
I have a git repo called binary-meta, which builds opensync 0.2x and 0.3x/0.4x
as well as some of the plugins. It does source builds as well as Debian
and RPM package builds. Gentoo is one that I haven't tackled.
In any case, my opensync development is happening on git branches
that you can see here:
http://repo.or.cz/w/opensync.git (scroll to the bottom to see the forks)
The latest opensync tree is not the above repo, but this fork:
http://repo.or.cz/w/opensync/opensync-cdf.git
If you want to build using binary-meta, grab the following tree first, which
will grab the others it needs, including Barry:
http://repo.or.cz/w/opensync/binary-meta.git
If repo.or.cz gives you disconnect problems, just keep trying. Sometimes
it has load trouble.
Once you have binary-meta, see the README files for more information, and
the help text when you type 'make'.
Binary-meta is the source of the next Barry release, when it happens.
The next Barry release is planned to include opensync dependencies and
some plugins as well. Ideally, I want it easy for people to add Barry
to their apt-get sources or yum repos and keep up to date that way with
binary packages. If you know someone on the Gentoo side who would like
to help make an ebuild for binary-meta, that would be great, since tracking
that tree is where the latest changes appear, not SVN anymore.
Ok, onward to your actual problem :-)
> Here's what I did:
>
> osynctool --addgroup g
> osynctool --addmember g barry-sync
> osynctool --addmember g file-sync
> osynctool --configure g 1
> # stuck in the PIN and turned off everything but memos
> # the default config includes debug info turned on
> osynctool --configure g 2
> # put in a real path
> osynctool --discover g
> osynctool --sync g
>
> This, of course, prints out a lot of info, and ends with:
>
> Received an entry 1571527172 (vjournal) from member 1 (barry-sync).
> Changetype ADDED
> note sink of member 1 of type barry-sync just sent all changes
> Main sink of member 1 of type barry-sync just sent all changes
> All clients sent changes or error
> All changes got mapped
> All conflicts have been reported
> The sync failed: Couldn't find Object Type Engine for Object Type "note"
> while preparing for write phase.
> Main sink of member 2 of type file-sync just disconnected
> note sink of member 1 of type barry-sync had an error: Broken Pipe
> Main sink of member 1 of type barry-sync had an error: Broken Pipe
> All clients have disconnected
I did a quick test here with the latest code, and it worked for me, but
I had to change the file-sync <ObjType> block to <ObjType>note</ObjType>.
When I did the discover, it showed a mismatch (file-sync defaults to contact)
until I changed it. Even when syncing, though, it didn't give me an error,
it just didn't sync two different types.
I suspect that either you're missing a plugin, or there's a bug in your
older version of opensync.
Try osynctool --listformats and see if a 'memo' format with 'note' object type
is available.
- Chris
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
