From v at piratweb.com Wed Jun 1 11:56:15 2016 From: v at piratweb.com (Vladislav Vorobiev) Date: Wed, 1 Jun 2016 14:56:15 +0300 Subject: [SyncEvolution] syncevolution-kde + akonadi [ERROR syncevo-dbus-server 00:00:00] child process quit because of signal 11 In-Reply-To: <1464602512.24758.6.camel@intel.com> References: <6413372.GSvTpbh0lX@loenka> <1464602512.24758.6.camel@intel.com> Message-ID: <1944890.DJIBYGnYT0@loenka> Ok, I find out that happens on debian after last update. I tried on other PC, with the same result. My current system is debian stretch (testing) apt source looks like deb http://cdn.debian.net/debian stretch main contrib non-free and # syncevolution-kde deb http://www.estamos.de/download/apt unstable main deb http://downloads.syncevolution.org/apt unstable main apt-cache policy syncevolution-kde Installed 1:1.5.1-1 From 1:1.5.1-1 500 500 http://www.estamos.de/download/apt unstable/main amd64 Packages 500 http://downloads.syncevolution.org/apt unstable/main amd64 sysyncevolution-dbus = .4.99.4-3+b1 libc6 = 2.22-9 and vavvav at loenka:~$ SYNCEVOLUTION_DEBUG=1 gdb --args syncevolution --daemon=no loglevel=10 --export /tmp/calendar.ics funambol calendar GNU gdb (Debian 7.10-1+b1) 7.10 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from syncevolution...done. (gdb) run Starting program: /usr/bin/syncevolution --daemon=no loglevel=10 --export /tmp/calendar.ics funambol calendar [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [DEBUG 00:00:00] checking password property 'password' in config 'funambol' with user identity 'bouillon' [DEBUG 00:00:00] checking password property 'databasePassword' in datastore 'calendar' of config 'funambol' with user identity '' [DEBUG 00:00:00] calendar: slow sync or testing, do full item scan to detect changes Program received signal SIGSEGV, Segmentation fault. 0x00007ffff66101da in strlen () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) backtrace #0 0x00007ffff66101da in strlen () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff660ff0e in strdup () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007fffe5ab2159 in icalvalue_as_ical_string_r () from /usr/lib/libical.so.1 #3 0x00007fffe5aa694b in icalproperty_as_ical_string_r () from /usr/lib/libical.so.1 #4 0x00007fffe5aa0128 in icalcomponent_as_ical_string_r () from /usr/lib/libical.so.1 #5 0x00007fffe5aa0236 in icalcomponent_as_ical_string () from /usr/lib/libical.so.1 #6 0x00007fffe3626344 in KCalCore::ICalFormat::toRawString(QSharedPointer const&) () from /usr/lib/libkcalcore.so.4 #7 0x00007fffe3b15e20 in ?? () from /usr/lib/kde4/akonadi_serializer_kcalcore.so #8 0x00007fffedcd708f in ?? () from /usr/lib/libakonadi-kde.so.4 #9 0x00007fffedcd797f in ?? () from /usr/lib/libakonadi-kde.so.4 #10 0x00007fffedcc0c40 in Akonadi::Item::payloadData() const () from /usr/lib/libakonadi-kde.so.4 #11 0x00007fffee0afdb7 in SyncEvo::AkonadiSyncSource::readItem (this=, luid=..., data=..., raw=) at /data/runtests/work/sources/syncevolution/src/backends/akonadi/akonadisyncsource.cpp:328 #12 0x00007ffff758b0cd in SyncEvo::ExportLUID (raw=0x0, out=0x7aaee0, defDelimiter=..., itemPath=..., haveItem=@0x11a0: , haveNewline=@0x411: , luid=...) at /data/runtests/work/sources/syncevolution/src/syncevo/Cmdline.cpp:684 #13 0x00007ffff75a9668 in boost::_bi::list7, boost::_bi::value, boost::reference_wrapper, std::allocator > >, boost::reference_wrapper, std::allocator > >, boost::reference_wrapper, boost::reference_wrapper, boost::arg<1> >::operator(), std::allocator >&> > (a=..., f=, this=) at /usr/include/boost/bind/bind.hpp:663 #14 boost::_bi::bind_t, boost::_bi::value, boost::reference_wrapper, std::allocator > >, boost::reference_wrapper, std::allocator > >, boost::reference_wrapper, boost::reference_wrapper, boost::arg<1> > >::operator(), std::allocator > > (a1=..., this=) at /usr/include/boost/bind/bind_template.hpp:47 #15 boost::detail::function::void_function_obj_invoker1, boost::_bi::value, boost::reference_wrapper, boost::reference_wrapper, boost::reference_wrapper, boost::reference_wrapper, boost::arg<1> > >, void, std::string const&>::invoke (function_obj_ptr=..., a0=...) at /usr/include/boost/function/function_template.hpp:153 #16 0x00007ffff759273d in boost::function1::operator() (a0=..., this=) at /usr/include/boost/function/function_template.hpp:1013 #17 SyncEvo::Cmdline::processLUIDs(SyncEvo::SyncSource*, boost::function const&) (this=, source=, process=...) at /data/runtests/work/sources/syncevolution/src/syncevo/Cmdline.cpp:1745 #18 0x00007ffff75a6501 in SyncEvo::Cmdline::run (this=0x7fffffffd9d0) at /data/runtests/work/sources/syncevolution/src/syncevo/Cmdline.cpp:1588 #19 0x000000000041a90d in SyncEvo::main (argc=, argv=) at /data/runtests/work/sources/syncevolution/src/syncevolution.cpp:531 Thanks and Regards Vladislav On Monday 30 May 2016 12:01:52 Patrick Ohly wrote: > On Fri, 2016-05-27 at 10:13 +0300, Vladislav Vorobiev wrote: > > Hi, > > > > after some upgrades i run in the strage issue. > > Signal 11 is a segfault. Sounds like something isn't compiled correctly > anymore or some component got broken. What is this upgrade that you ran? > Which OS? Which SyncEvolution binaries (i.e. from distro or > syncevolution.org)? > > > $ SYNCEVOLUTION_DEBUG=3 syncevolution --sync two-way funambol calendar > > [DEBUG 00:00:00] SuspendFlags: (re)activating, currently inactive > > [DEBUG 00:00:00] SuspendFlags: activating signal handler(s) with fds > > 11->10 > > [DEBUG 00:00:00] SuspendFlags: catch signal 2 > > [DEBUG 00:00:00] SuspendFlags: catch signal 15 > > [INFO 00:00:00] addressbook: inactive > > [INFO 00:00:00] memo: inactive > > [INFO 00:00:00] todo: inactive > > [INFO 00:00:00] calendar: starting normal sync, two-way (peer is server) > > [INFO 00:00:00] creating complete data backup of datastore calendar before > > sync (enabled with dumpData and needed for printChanges) > > [ERROR syncevo-dbus-server 00:00:00] child process quit because of signal > > 11 > The actual failing process is the syncevo-dbus-helper, spawned by the > syncevo-dbus-server. To capture the actual segfault, running some item > operations directly under gdb with just one process involved will be the > easiest approach. Do it like this: > > SYNCEVOLUTION_DEBUG=1 gdb --args syncevolution --daemon=no loglevel=10 > --export /tmp/calendar.ics funambol calendar From patrick.ohly at intel.com Wed Jun 1 12:29:09 2016 From: patrick.ohly at intel.com (Patrick Ohly) Date: Wed, 01 Jun 2016 14:29:09 +0200 Subject: [SyncEvolution] syncevolution-kde + akonadi [ERROR syncevo-dbus-server 00:00:00] child process quit because of signal 11 In-Reply-To: <1944890.DJIBYGnYT0@loenka> References: <6413372.GSvTpbh0lX@loenka> <1464602512.24758.6.camel@intel.com> <1944890.DJIBYGnYT0@loenka> Message-ID: <1464784149.4416.3.camel@intel.com> On Wed, 2016-06-01 at 14:56 +0300, Vladislav Vorobiev wrote: > Ok, I find out that happens on debian after last update. > I tried on other PC, with the same result. > My current system is debian stretch (testing) Debian Testing recently went through several ABI breaks. It's quite likely that the available SyncEvolution binaries no longer work on it. I tried improving the build process, but it turned into a major nightmare due to the large number of variations that would have to be supported. May I ask why you were using the binaries from syncevolution.org? Perhaps because the ones from Debian were very old? Tino, how's your update of the Debian package to the latest version going? I saw that Debian Testing doesn't have any SyncEvolution version anymore. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. From tino.keitel+syncevolution at tikei.de Wed Jun 1 13:41:44 2016 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Wed, 1 Jun 2016 15:41:44 +0200 Subject: [SyncEvolution] syncevolution-kde + akonadi [ERROR syncevo-dbus-server 00:00:00] child process quit because of signal 11 In-Reply-To: <1464784149.4416.3.camel@intel.com> References: <6413372.GSvTpbh0lX@loenka> <1464602512.24758.6.camel@intel.com> <1944890.DJIBYGnYT0@loenka> <1464784149.4416.3.camel@intel.com> Message-ID: <20160601134144.GA15310@mac.home> On Wed, Jun 01, 2016 at 14:29:09 +0200, Patrick Ohly wrote: [...] > Tino, how's your update of the Debian package to the latest version > going? I saw that Debian Testing doesn't have any SyncEvolution version > anymore. Hi, I submitted a 1.5.1 package to my sponsor, but he had no time to upload it until now. Meanwhile, I put 1.5.1 packages for Debian Sid built by myself here: http://tikei.de/debian/syncevolution/ If there are any problems with these (like depends on outdated libraries), just let me now and I will rebuild them. If they won't work with stretch, just send me a note and I'll upload packages for stretch. Regards, Tino From v at piratweb.com Wed Jun 1 14:12:47 2016 From: v at piratweb.com (Vladislav Vorobiev) Date: Wed, 1 Jun 2016 17:12:47 +0300 Subject: [SyncEvolution] syncevolution-kde + akonadi [ERROR syncevo-dbus-server 00:00:00] child process quit because of signal 11 In-Reply-To: <20160601134144.GA15310@mac.home> References: <6413372.GSvTpbh0lX@loenka> <1464784149.4416.3.camel@intel.com> <20160601134144.GA15310@mac.home> Message-ID: <1925268.azZDHKZ4DW@loenka> Thank you very much!!! Should upload it to unstable branch. It works. On Wednesday 01 June 2016 15:41:44 Tino Mettler wrote: > On Wed, Jun 01, 2016 at 14:29:09 +0200, Patrick Ohly wrote: > > [...] > > > Tino, how's your update of the Debian package to the latest version > > going? I saw that Debian Testing doesn't have any SyncEvolution version > > anymore. > > Hi, > > I submitted a 1.5.1 package to my sponsor, but he had no time to upload > it until now. > > Meanwhile, I put 1.5.1 packages for Debian Sid built by myself here: > > http://tikei.de/debian/syncevolution/ > > If there are any problems with these (like depends on outdated > libraries), just let me now and I will rebuild them. > > If they won't work with stretch, just send me a note and I'll upload > packages for stretch. > > Regards, > Tino From deloptes at gmail.com Fri Jun 3 20:34:45 2016 From: deloptes at gmail.com (deloptes) Date: Fri, 3 Jun 2016 22:34:45 +0200 Subject: [SyncEvolution] syncevolution 1.5.1 and TDE backends References: <6413372.GSvTpbh0lX@loenka> <1464602512.24758.6.camel@intel.com> <1944890.DJIBYGnYT0@loenka> <1464784149.4416.3.camel@intel.com> <20160601134144.GA15310@mac.home> Message-ID: Tino Mettler wrote: > On Wed, Jun 01, 2016 at 14:29:09 +0200, Patrick Ohly wrote: > > [...] > >> Tino, how's your update of the Debian package to the latest version >> going? I saw that Debian Testing doesn't have any SyncEvolution version >> anymore. > > Hi, > > I submitted a 1.5.1 package to my sponsor, but he had no time to upload > it until now. > > Meanwhile, I put 1.5.1 packages for Debian Sid built by myself here: > > http://tikei.de/debian/syncevolution/ > > If there are any problems with these (like depends on outdated > libraries), just let me now and I will rebuild them. > > If they won't work with stretch, just send me a note and I'll upload > packages for stretch. > > Regards, > Tino Hi, I want to use this opportunity to ask a question I wanted to ask for some time now. I was working on a TDE (Tinity Desktop Env) backends in the past few months and I tried recently to build packages for debian, but failed miserably. I was wondering how I could go ahead with the code now. I would consider the backend as working (I need to improve/change few things in the feature). I am not able to test the wallet because I don't have any account, so the wallet backend code is not tested. The rest is working without major issues. Can you share some ideas please? Thanks in advance regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Fri Jun 10 07:21:37 2016 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Fri, 10 Jun 2016 09:21:37 +0200 Subject: [SyncEvolution] syncevolution 1.5.1 and TDE backends In-Reply-To: References: <6413372.GSvTpbh0lX@loenka> <1464602512.24758.6.camel@intel.com> <1944890.DJIBYGnYT0@loenka> <1464784149.4416.3.camel@intel.com> <20160601134144.GA15310@mac.home> Message-ID: <20160610072135.GA13349@eazy.amigager.de> On Fri, Jun 03, 2016 at 22:34:45 +0200, deloptes wrote: > I was working on a TDE (Tinity Desktop Env) backends in the past few months > and I tried recently to build packages for debian, but failed miserably. > I was wondering how I could go ahead with the code now. I would consider the > backend as working (I need to improve/change few things in the feature). > I am not able to test the wallet because I don't have any account, so the > wallet backend code is not tested. The rest is working without major > issues. > > Can you share some ideas please? Hi, I don't get the real question. If you added your own backend and want to know how to add it to the Debian packaging, you could use the KDE backend (in the syncevolution-libs-kde package) as an example: 1. add a syncevolution-libs-tde backend package to debian/control (use the syncevolution-libs-kde part as a template) 2. add a file debian/syncevolution-libs-tde.install (use debian/syncevolution-libs-kde.install as a template) and insert the backend libs for your TDE backend If you have other questions regarding usage of the Debian packaging, just ask. Regards, Tino _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Fri Jun 10 20:47:59 2016 From: deloptes at gmail.com (deloptes) Date: Fri, 10 Jun 2016 22:47:59 +0200 Subject: [SyncEvolution] syncevolution 1.5.1 and TDE backends References: <6413372.GSvTpbh0lX@loenka> <1464602512.24758.6.camel@intel.com> <1944890.DJIBYGnYT0@loenka> <1464784149.4416.3.camel@intel.com> <20160601134144.GA15310@mac.home> <20160610072135.GA13349@eazy.amigager.de> Message-ID: Tino Mettler wrote: > I don't get the real question. If you added your own backend and want > to know how to add it to the Debian packaging, you could > use the KDE backend (in the syncevolution-libs-kde package) as an example: > > 1. add a syncevolution-libs-tde backend package to debian/control (use > the syncevolution-libs-kde part as a template) > > 2. add a file debian/syncevolution-libs-tde.install (use > debian/syncevolution-libs-kde.install as a template) and insert the > backend libs for your TDE backend > > If you have other questions regarding usage of the Debian packaging, > just ask. > > Regards, > Tino Thanks Tino, this was exactly the answer I was looking for. I don't like reinventing the wheel. You saved me some precious time. regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From v at piratweb.com Wed Jun 1 14:04:40 2016 From: v at piratweb.com (Vladislav Vorobiev) Date: Wed, 1 Jun 2016 17:04:40 +0300 Subject: [SyncEvolution] syncevolution-kde + akonadi [ERROR syncevo-dbus-server 00:00:00] child process quit because of signal 11 In-Reply-To: <1464784149.4416.3.camel@intel.com> References: <6413372.GSvTpbh0lX@loenka> <1944890.DJIBYGnYT0@loenka> <1464784149.4416.3.camel@intel.com> Message-ID: <2015045.xrlmAEPvd8@loenka> > Debian Testing recently went through several ABI breaks. It's quite > likely that the available SyncEvolution binaries no longer work on it. I > tried improving the build process, but it turned into a major nightmare > due to the large number of variations that would have to be supported. > > May I ask why you were using the binaries from syncevolution.org? > Perhaps because the ones from Debian were very old? I use Debian stretch because it the next stable release and current stable too old. Ok I nees syncevolution-kde package because I sync aconadi with funambol Normal syncevolution did't do it for me. It can't sync aconadi sources. https://syncevolution.org/wiki/kde-akonadi https://syncevolution.org/documentation/installation From deloptes at gmail.com Fri Jun 10 21:49:22 2016 From: deloptes at gmail.com (deloptes) Date: Fri, 10 Jun 2016 23:49:22 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends Message-ID: Hi again, 1. the second part of my question is/was what to do with the source code and what would be the best approach? I think the code should go into syncevolution repository. TDE packages would be provided then by TDE. Is it correct assumption and if yes what is the way for doing it? 2. Now following your advise I updated the package files, but it failed to build anyway here is the config (I copy pasted from my test scripts into debian/rules) and the errors I got. I don't get those errors when I compile using automake. I assume this is something to do with dpkg building shared, but I'll be glad if you could help dh_auto_configure -- --prefix=/usr \ --sysconfdir=/etc \ --libexecdir=/usr/lib/x86_64-linux-gnu/syncevolution \ --enable-gui \ --with-rst2man --with-rst2html \ --enable-maintainer-mode \ --enable-core \ --enable-bluetooth \ --enable-tdepimabc \ --enable-tdepimcal \ --enable-tdepimnotes \ --disable-tdewallet \ --enable-sqlite \ --enable-file \ --enable-dav \ --without-gio-gdbus \ --disable-ssl-certificate-check \ --disable-akonadi \ --disable-ebook \ --disable-ecal \ --disable-goa \ --disable-kcalextended \ --disable-kwallet \ --disable-maemocal \ --disable-oauth2 \ --disable-qtcontacts \ --disable-gsso \ --disable-uoa \ --disable-sign dpkg-buildpackage -rfakeroot -b -d -us -uc or dpkg-buildpackage -rfakeroot -b -d -us -uc -aamd64 /usr/bin/ld: /opt/software/SyncEvolution/syncevolution-1.5.1/src/build-synthesis/src/.libs/libsynthesissdk.a(libsynthesissdk_la-SDK_util.o): relocation R_X86_64_PC32 against symbol `StrAllocN' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:5931: recipe for target 'src/syncevo/libsyncevolution.la' failed make[3]: *** [src/syncevo/libsyncevolution.la] Error 1 make[3]: Leaving directory '/opt/software_x64/SyncEvolution/syncevolution-1.5.1' Makefile:11453: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/opt/software_x64/SyncEvolution/syncevolution-1.5.1' Makefile:4473: recipe for target 'all' failed make[1]: *** [all] Error 2 rm src/dbus/glib/stamp-syncevo-session-bindings.h src/dbus/glib/stamp-syncevo-session-glue.h src/dbus/glib/stamp-syncevo-connection-bindings.h src/dbus/glib/stamp-syncevo-server-glue.h src/dbus/glib/stamp-syncevo-server-bindings.h src/dbus/glib/stamp-syncevo-connection-glue.h make[1]: Leaving directory '/opt/software_x64/SyncEvolution/syncevolution-1.5.1' dh_auto_build: make -j1 returned exit code 2 debian/rules:18: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 perhaps this helps too grep PIC config.log configure:9618: checking for gcc option to produce PIC configure:9625: result: -fPIC -DPIC configure:9633: checking if gcc PIC flag -fPIC -DPIC works configure:9651: gcc -c -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_FORTIFY_SOURCE=2 -fPIC -DPIC -DPIC conftest.c >&5 configure:11095: gcc -shared -fPIC -DPIC conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| /bin/grep -lc \>/dev/null 2\>\&1 configure:15166: checking for g++ option to produce PIC configure:15173: result: -fPIC -DPIC configure:15181: checking if g++ PIC flag -fPIC -DPIC works configure:15199: g++ -c -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPIC -DPIC conftest.cpp >&5 lt_cv_prog_compiler_pic='-fPIC -DPIC' lt_cv_prog_compiler_pic_CXX='-fPIC -DPIC' _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Mon Jun 13 11:33:16 2016 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Mon, 13 Jun 2016 13:33:16 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends In-Reply-To: References: Message-ID: <20160613113316.GA20937@eazy.amigager.de> On Fri, Jun 10, 2016 at 23:49:22 +0200, deloptes wrote: [...] > /usr/bin/ld: /opt/software/SyncEvolution/syncevolution-1.5.1/src/build-synthesis/src/.libs/libsynthesissdk.a(libsynthesissdk_la-SDK_util.o): > relocation R_X86_64_PC32 against symbol `StrAllocN' can not be used when > making a shared object; recompile with -fPIC Hi, IIRC this error usually happens if you want to build a dynamic library with -fPIC and try to link it with a static one that was built without. However, I can't see the exact cause of the failure without more context from the build log. Regards, Tino _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Mon Jun 13 11:42:08 2016 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Mon, 13 Jun 2016 13:42:08 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends In-Reply-To: <20160613113316.GA20937@eazy.amigager.de> References: <20160613113316.GA20937@eazy.amigager.de> Message-ID: <20160613114208.GB20937@eazy.amigager.de> On Mon, Jun 13, 2016 at 13:33:16 +0200, Tino Mettler wrote: > On Fri, Jun 10, 2016 at 23:49:22 +0200, deloptes wrote: > > [...] > > > /usr/bin/ld: /opt/software/SyncEvolution/syncevolution-1.5.1/src/build-synthesis/src/.libs/libsynthesissdk.a(libsynthesissdk_la-SDK_util.o): > > relocation R_X86_64_PC32 against symbol `StrAllocN' can not be used when > > making a shared object; recompile with -fPIC > > Hi, > > IIRC this error usually happens if you want to build a dynamic library > with -fPIC and try to link it with a static one that was built without. > > However, I can't see the exact cause of the failure without more > context from the build log. My guess is that the linker error is caused by your mix of the Debian packaging and the embedded build of libsynthesis in your build, where the latter seems to build a static library. In Debian, libsynthesis comes from a separate Debian package, which provides shared libraries. Regards, Tino _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Tue Jun 14 08:52:18 2016 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Tue, 14 Jun 2016 10:52:18 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends In-Reply-To: References: <20160613113316.GA20937@eazy.amigager.de> <20160613114208.GB20937@eazy.amigager.de> Message-ID: <20160614085218.GA7031@eazy.amigager.de> On Mon, Jun 13, 2016 at 16:13:44 +0200, deloptes wrote: > OK, Thank you Tino, > I have the feeling you are right. I'll try to build the debian packages on > the test env, where I will need to install the evolution and kde libs as > well, so that I'll be able to build all available/suggested backends. > > What about merging the code into the syncevolution git tree? > What is the "official" procedure? Hi, that question is better sent to the syncevolution mailing list, as I'm only the Debian maintainer. Regards, Tino _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Mon Jun 27 22:26:47 2016 From: deloptes at gmail.com (deloptes) Date: Tue, 28 Jun 2016 00:26:47 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends References: <20160613113316.GA20937@eazy.amigager.de> <20160613114208.GB20937@eazy.amigager.de> <20160614085218.GA7031@eazy.amigager.de> Message-ID: Tino Mettler wrote: > On Mon, Jun 13, 2016 at 16:13:44 +0200, deloptes wrote: >> OK, Thank you Tino, >> I have the feeling you are right. I'll try to build the debian packages >> on the test env, where I will need to install the evolution and kde libs >> as well, so that I'll be able to build all available/suggested backends. >> >> What about merging the code into the syncevolution git tree? >> What is the "official" procedure? > > Hi, > > that question is better sent to the syncevolution mailing list, as I'm > only the Debian maintainer. > > Regards, > Tino Hi again, I noticed there is no package for stretch - for jessie and sid there is one - what are the plans or what is the story? This is also version 1.4.99 - why not 1.5.1 (I mean at least sid)? https://packages.debian.org/sid/syncevolution I also did not understand how I can get the TDE backends into the syncevolution code tree, or what you would advise to do with backends that target specific desktop environment (TDE)? There are couple of options and I have no idea what is the best way. The TDE team could provide packages, or it could go through the supported distros. What would you advise? Here is reference to TDE: http://www.trinitydesktop.org/ Thanks in advance regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Tue Jun 28 06:32:27 2016 From: patrick.ohly at intel.com (Patrick Ohly) Date: Tue, 28 Jun 2016 08:32:27 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends In-Reply-To: References: <20160613113316.GA20937@eazy.amigager.de> <20160613114208.GB20937@eazy.amigager.de> <20160614085218.GA7031@eazy.amigager.de> Message-ID: <1467095547.13022.14.camel@intel.com> On Tue, 2016-06-28 at 00:26 +0200, deloptes wrote: > I noticed there is no package for stretch - for jessie and sid there is > one - what are the plans or what is the story? > This is also version 1.4.99 - why not 1.5.1 (I mean at least sid)? > > https://packages.debian.org/sid/syncevolution I think it had to be removed because it no longer compiled in stretch. 1.5.1 needs to be uploaded, then it can migrate to stretch again. > I also did not understand how I can get the TDE backends into the > syncevolution code tree, or what you would advise to do with backends that > target specific desktop environment (TDE)? I think it would be best to include it in the upstream release. Then it is easier for distros to enable it, if they want. OTOH, if a distro wants, they can already now grab the SyncEvolution source, add the backend directory from a separate archive or location, and compile both together. But there's one unsolved problem either way: distros most likely use the glib D-Bus bindings. It is the more modern solution. When enabling the TDE backend, distros would have to use the same workaround as you did and switch back to the libdbus-based bindings. Not sure whether that's a viable long term solution. > There are couple of options and I have no idea what is the best way. The TDE > team could provide packages, or it could go through the supported distros. > What would you advise? > > Here is reference to TDE: http://www.trinitydesktop.org/ Are there distros which include TDE or is the normal approach to use the packages prepared by the TDE team for certain distros? If TDE is not included in a distro and SyncEvolution is, then the distro can't compile the TDE backend. In that case the TDE team could try to compile the backend against the SyncEvolution version provided by the distro, but that's tricky - I'm not even sure whether distros install all the header files, and a custom makefile would have to be written for the backend. Another alternative would be to provide SyncEvolution packages as part of TDE, overriding the ones provided by the distro. That's also not a good solution and something that I am currently struggling with in the project, because for example, Ubuntu has non-upstream patches and SyncEvolution must be compiled exactly as chosen by Ubuntu, otherwise the replacement would not work as the original, distro-provided packages. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. From deloptes at gmail.com Tue Jun 28 07:03:55 2016 From: deloptes at gmail.com (deloptes) Date: Tue, 28 Jun 2016 09:03:55 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends References: <20160613113316.GA20937@eazy.amigager.de> <20160613114208.GB20937@eazy.amigager.de> <20160614085218.GA7031@eazy.amigager.de> <1467095547.13022.14.camel@intel.com> Message-ID: Patrick Ohly wrote: > On Tue, 2016-06-28 at 00:26 +0200, deloptes wrote: >> I noticed there is no package for stretch - for jessie and sid there is >> one - what are the plans or what is the story? >> This is also version 1.4.99 - why not 1.5.1 (I mean at least sid)? >> >> https://packages.debian.org/sid/syncevolution > > I think it had to be removed because it no longer compiled in stretch. > 1.5.1 needs to be uploaded, then it can migrate to stretch again. > Thank you Patric, I just realized why https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824426 , perhaps I should try with the git code of syncevolution. >> I also did not understand how I can get the TDE backends into the >> syncevolution code tree, or what you would advise to do with backends >> that target specific desktop environment (TDE)? > > I think it would be best to include it in the upstream release. Then it > is easier for distros to enable it, if they want. OTOH, if a distro > wants, they can already now grab the SyncEvolution source, add the > backend directory from a separate archive or location, and compile both > together. > > But there's one unsolved problem either way: distros most likely use the > glib D-Bus bindings. It is the more modern solution. When enabling the > TDE backend, distros would have to use the same workaround as you did > and switch back to the libdbus-based bindings. Not sure whether that's a > viable long term solution. > I don't know who to ask but I'll discuss this with the TDE people, thanks. This dbus issue is on the todo list as well. >> There are couple of options and I have no idea what is the best way. The >> TDE team could provide packages, or it could go through the supported >> distros. What would you advise? >> >> Here is reference to TDE: http://www.trinitydesktop.org/ > > Are there distros which include TDE or is the normal approach to use the > packages prepared by the TDE team for certain distros? > > If TDE is not included in a distro and SyncEvolution is, then the distro > can't compile the TDE backend. In that case the TDE team could try to > compile the backend against the SyncEvolution version provided by the > distro, but that's tricky - I'm not even sure whether distros install > all the header files, and a custom makefile would have to be written for > the backend. > TDE is not included in a distro. It is installed on top, being independent from other desktops shipped with the distro. This makes the case even more complicated, because if in example Debian ships syncevolution with evolution and akonadi/kde backend, TDE should demand from Debian compiling with tdepim support or provide own (TDE) packages that would add tdepim backend (as you describe below). Same for SuSE etc ... > Another alternative would be to provide SyncEvolution packages as part > of TDE, overriding the ones provided by the distro. That's also not a > good solution and something that I am currently struggling with in the > project, because for example, Ubuntu has non-upstream patches and > SyncEvolution must be compiled exactly as chosen by Ubuntu, otherwise > the replacement would not work as the original, distro-provided > packages. > I understand, thanks again. I think perhaps it's best to merge syncevolution and plugins in TDE and build own packages for now. If you add the code to syncevolution and it goes around several distros, it would be harder to update and I have still few places for improvement, though overall I did not have any issue in the past few months. thanks and regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Thu Jun 30 07:39:32 2016 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Thu, 30 Jun 2016 09:39:32 +0200 Subject: [SyncEvolution] Debian building packages for syncevolution 1.5.1 and TDE backends In-Reply-To: References: <20160613113316.GA20937@eazy.amigager.de> <20160613114208.GB20937@eazy.amigager.de> <20160614085218.GA7031@eazy.amigager.de> Message-ID: <20160630073931.GA4501@eazy.amigager.de> On Tue, Jun 28, 2016 at 00:26:47 +0200, deloptes wrote: > Tino Mettler wrote: > > > On Mon, Jun 13, 2016 at 16:13:44 +0200, deloptes wrote: > >> OK, Thank you Tino, > >> I have the feeling you are right. I'll try to build the debian packages > >> on the test env, where I will need to install the evolution and kde libs > >> as well, so that I'll be able to build all available/suggested backends. > >> > >> What about merging the code into the syncevolution git tree? > >> What is the "official" procedure? > > > > Hi, > > > > that question is better sent to the syncevolution mailing list, as I'm > > only the Debian maintainer. > > > > Regards, > > Tino > > Hi again, > > I noticed there is no package for stretch - for jessie and sid there is > one - what are the plans or what is the story? > This is also version 1.4.99 - why not 1.5.1 (I mean at least sid)? Hi, sorry for the delay. I have serious trouble finding a sponsor to upload the 1.5.1 package. The last info I got is that an upload could happen in a few days (at least this week). Regards, Tino _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From alberto.mardegan at canonical.com Wed Jun 29 15:12:40 2016 From: alberto.mardegan at canonical.com (Alberto Mardegan) Date: Wed, 29 Jun 2016 17:12:40 +0200 Subject: [SyncEvolution] Debug messages Message-ID: <5773E568.5080109@canonical.com> Hi! I'm trying to debug what appears to be an issue in libsignon-glib, which is used in the signon backend. In order to debug it, I need to see the output of the g_debug() calls happening inside that library, but for some reason I can see only one of them: ============== $ G_MESSAGES_DEBUG=all SYNCEVOLUTION_DEBUG=1 syncevolution loglevel=1 --daemon=no --sync two-way google-100 ...sources... [DEBUG 00:00:00] log path -> /home/phablet/.cache/syncevolution, [DEBUG 00:00:00] checking log dir /home/phablet/.cache/syncevolution [DEBUG 00:00:00] logfile: /home/phablet/.cache/syncevolution/google_+100-2016-06-29-18-04/syncevolution-log.html [DEBUG syncevo-local-sync 00:00:00] ForkExecChild: connecting to parent with D-Bus address 11 [DEBUG syncevo-local-sync 00:00:00] child connected to parent [ERROR @google-100] error code from SyncEvolution access denied (remote, status 403): could not obtain OAuth2 token: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.135 was not provided by any .service files [ERROR @google-100] error code from SyncEvolution access denied (remote, status 403): logging into remote service failed: error code from SyncEvolution access denied (remote, status 403): could not obtain OAuth2 token: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.135 was not provided by any .service files [DEBUG @google-100 00:00:18] signon-identity.c:636: identity_session_object_destroyed_cb 636 [ERROR] error code from SyncEvolution access denied (remote, status 403): failure on target side @google-100 of local sync: could not obtain OAuth2 token: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.135 was not provided by any .service files ============== As you can see, in the logs above there *is* a line coming from libsignon-glib, but only one, while all the others (which I'm sure are being executed, and they are all calls to g_debug()) are not visible. Any idea of what could be the reason? Ciao, Alberto _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Wed Jun 29 15:56:18 2016 From: patrick.ohly at intel.com (Patrick Ohly) Date: Wed, 29 Jun 2016 17:56:18 +0200 Subject: [SyncEvolution] Debug messages In-Reply-To: <5773E568.5080109@canonical.com> References: <5773E568.5080109@canonical.com> Message-ID: <1467215778.30662.3.camel@intel.com> On Wed, 2016-06-29 at 17:12 +0200, Alberto Mardegan wrote: > Hi! > I'm trying to debug what appears to be an issue in libsignon-glib, > which is used in the signon backend. > In order to debug it, I need to see the output of the g_debug() calls > happening inside that library, but for some reason I can see only one of > them: > > ============== > $ G_MESSAGES_DEBUG=all SYNCEVOLUTION_DEBUG=1 syncevolution loglevel=1 > --daemon=no --sync two-way google-100 ...sources... > [DEBUG 00:00:00] log path -> /home/phablet/.cache/syncevolution, > [DEBUG 00:00:00] checking log dir /home/phablet/.cache/syncevolution > [DEBUG 00:00:00] logfile: > /home/phablet/.cache/syncevolution/google_+100-2016-06-29-18-04/syncevolution-log.html > [DEBUG syncevo-local-sync 00:00:00] ForkExecChild: connecting to parent > with D-Bus address 11 > [DEBUG syncevo-local-sync 00:00:00] child connected to parent > [ERROR @google-100] error code from SyncEvolution access denied (remote, > status 403): could not obtain OAuth2 token: > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.135 > was not provided by any .service files > [ERROR @google-100] error code from SyncEvolution access denied (remote, > status 403): logging into remote service failed: error code from > SyncEvolution access denied (remote, status 403): could not obtain > OAuth2 token: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The > name :1.135 was not provided by any .service files > [DEBUG @google-100 00:00:18] signon-identity.c:636: > identity_session_object_destroyed_cb 636 > [ERROR] error code from SyncEvolution access denied (remote, status > 403): failure on target side @google-100 of local sync: could not obtain > OAuth2 token: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The > name :1.135 was not provided by any .service files > ============== > > As you can see, in the logs above there *is* a line coming from > libsignon-glib, but only one, while all the others (which I'm sure are > being executed, and they are all calls to g_debug()) are not visible. SyncContext::initMain() unconditionally calls g_log_set_default_handler() to redirect glib output into Logger::glogFunc(), which then logs them according to the current log settings. You are running with a low loglevel. Try bumping that to 10 (or 11, for our UK friends) and I bet you'll see the messages. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.