On Sat, 2012-08-11 at 21:34 +0200, Tino Keitel wrote: > On Mon, Aug 06, 2012 at 20:47:18 +0200, Tino Keitel wrote: > > On Mon, Aug 06, 2012 at 17:50:04 +0200, Patrick Ohly wrote: > > > > [...] > > > > > Tino, can you check whether your upcoming update fixes this issue? > > > > > > If it doesn't, then perhaps try switching to GIO D-Bus. Actually, I am > > > surprised that it is not used by default already. configure should pick > > > it when gio-2.0 >= 2.30. Do you perhaps configure with > > > --without-gio-dbus? > > > > Could it be that this is caused by a missing build depencency? At least > > the build log looks fine: > > > > https://buildd.debian.org/status/fetch.php?pkg=syncevolution&arch=i386&ver=1.2.99.1-1&stamp=1341042365 > > > > The configure summary shows this: > > > > GIO GDBus: yes > > Hi Patrick, > > did you see something obvious in the build log?
I double-checked. Debian's syncevo-dbus-server does use GIO D-Bus; what I saw must have been an indirect call to libdbus (happens later, via gvfs). > I think I got the same > issue with 1.2.99.4 (can't really check as I'm on vacation). I'll have another look. -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
