I was (again) trying to set up msync between my phone and my ~x86 gentoo, albeit unsuccessfully. The reason seems to be that msynctool and the required libopensync and libopensync-plugins are totally out of sync in portage.
Here's the situation that I see, but can't resolve.
- msynctool is at version 0.36.
- libopensync-plugin-vformat, libopensync-plugin-file and libopensync-plugin-evolution2 are at 0.39
- libopensync-plugin-synce and libopensync-plugin-sunbird are at 0.22
- all other libopensync-plugins are at 0.36
Now, the easiest way would seem to downgrade (package.mask) everything to 0.36 and forget synce and sunbird, which I tried.
This requires libopensync-plugin-syncml to also be downgraded to 0.36, but the libopensync-plugin-syncml-0.36 ebuild has been removed, because it required libsyncml-0.4, which is now at 0.5.4, and there is no ebuild for libsyncml-0.4.x
So, to all my seeming, it is not possible to use msynctool at all.
Leaving all settings at their defaults results in the following btw:
msynctool: symbol lookup error: msynctool: undefined symbol: osync_plugin_env_num_plugins
Just can't figure it out.
(In reply to comment #0)
> Leaving all settings at their defaults results in the following btw:
> msynctool --listplugins
> Available plugins:
> msynctool: symbol lookup error: msynctool: undefined symbol:
More precisely: msynctool-0.36 and libopensync-0.39. The situation is easily reached by first installing msynctool, then libopensync without masking.
Can confirm this bug.
Seems no one is using gentoo to sync his mobile device ?
Any ideas how to solve this issue ?
(In reply to comment #2)
> Can confirm this bug.
> Seems no one is using gentoo to sync his mobile device ?
> Any ideas how to solve this issue ?
Not with current portage and bugs like this getting no response ;-)
What I did (and use it since without any issues): Instead of downgrading the whole app-pda plethora, I deinstalled the packages in question (opensync*, syncml* etc.) and downloaded, compiled and installed the original source code, vesion 0.22 from opensync.org (actually, one big warning on the site says "0.3x releases introduce major architecture and API changes and are targeted for developers and testers only and may not even compile or are likely to contain severe bugs.
0.3x releases are not recommended for end users or distribution packaging.")
But I suppose this is what being on ~x86 is all about :-)
All of those install (very straightforwardly) into /usr/local, so there is no conflict with the gentoo packages. I even reinstalled some of the gentoo pkgs later, and they happily coexisted.
*** Bug 311073 has been marked as a duplicate of this bug. ***
*** Bug 327205 has been marked as a duplicate of this bug. ***
(In reply to comment #1)
> More precisely: msynctool-0.36 and libopensync-0.39. The situation is easily
> reached by first installing msynctool, then libopensync without masking.
Do not use msynctool for libopensync >= 0.39, use osynctool instead.
There's really nothing we can do here. We can't add plugins that don't exist. We can SLOT libopensync but the tools can't be installed together because the configuration files are incompatible between versions and all overwrite one another. All we can do is provide a plugin for every version we support if one exists and hope some combination works.