From g+syncevolution at cobb.uk.net Sun Feb 24 19:56:18 2019 From: g+syncevolution at cobb.uk.net (Graham Cobb) Date: Sun, 24 Feb 2019 19:56:18 +0000 Subject: [SyncEvolution] Invalid signature for SyncEvolution 1.5.3 repo Message-ID: <31e07991-b898-d4b2-1cdc-0c1d3c358744@cobb.uk.net> Hi, I wanted to try out syncevolution with the Windows 10 Debian environment. I tried following the instructions at https://syncevolution.org/blogs/pohly/2018/syncevolution-153, including using apt-key to import the signing key. That stage went fine, but I got the following error from apt-get update: Err:5 https://download.01.org/syncevolution/apt stable InRelease The following signatures were invalid: EXPKEYSIG 9B911472715D06C6 SyncEvolution Reading package lists... Done W: GPG error: https://download.01.org/syncevolution/apt stable InRelease: The following signatures were invalid: EXPKEYSIG 9B911472715D06C6 SyncEvolution E: The repository 'https://download.01.org/syncevolution/apt stable InRelease' is not signed. Graham _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Thu Feb 28 21:15:15 2019 From: patrick.ohly at intel.com (Patrick Ohly) Date: Thu, 28 Feb 2019 22:15:15 +0100 Subject: [SyncEvolution] Invalid signature for SyncEvolution 1.5.3 repo In-Reply-To: <31e07991-b898-d4b2-1cdc-0c1d3c358744@cobb.uk.net> References: <31e07991-b898-d4b2-1cdc-0c1d3c358744@cobb.uk.net> Message-ID: Graham Cobb writes: > I wanted to try out syncevolution with the Windows 10 Debian environment. > > I tried following the instructions at > https://syncevolution.org/blogs/pohly/2018/syncevolution-153, including > using apt-key to import the signing key. That stage went fine, but I got > the following error from apt-get update: > > Err:5 https://download.01.org/syncevolution/apt stable InRelease > The following signatures were invalid: EXPKEYSIG 9B911472715D06C6 > SyncEvolution > Reading package lists... Done > W: GPG error: https://download.01.org/syncevolution/apt stable > InRelease: The following signatures were invalid: EXPKEYSIG > 9B911472715D06C6 SyncEvolution > E: The repository 'https://download.01.org/syncevolution/apt stable > InRelease' is not signed. Consider this my yearly test whether someone is still using the repo ;-} But seriously, sorry for this. I have a yearly reminder for key renewal, but managed to not renew the renewal reminder when I updated the keys last year. I had noticed the issue myself but then didn't have time to deal with it right away. This is all a bit complicated and although I have the steps written down, each year there are new surprises. This year it was that the newly signed repo was still getting rejected. I had to switch to a newer hashing algorithm. Long story short, it should work again. Remember that as users you still need to renew the signing key with: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 43D03AD9 I am wondering whether the one year time limit for the signing key is really worth the effort... Bye, Patrick _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From g+syncevolution at cobb.uk.net Thu Feb 28 23:37:06 2019 From: g+syncevolution at cobb.uk.net (Graham Cobb) Date: Thu, 28 Feb 2019 23:37:06 +0000 Subject: [SyncEvolution] Invalid signature for SyncEvolution 1.5.3 repo In-Reply-To: References: <31e07991-b898-d4b2-1cdc-0c1d3c358744@cobb.uk.net> Message-ID: <2a22e6ae-74f9-7949-df76-6245c2e94a10@cobb.uk.net> On 28/02/2019 21:15, Patrick Ohly wrote: > Long story short, it should work again. Remember that as users you still > need to renew the signing key with: > sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 43D03AD9 Thanks Patrick, that works now. Now I have a different problem: using the 1.5.3 packages I can't get syncevolution to recognise the webdav backends (caldav or carddav). After some debugging, it seems there is a missing dependency on libneon27-gnutls. Installing that allows the webdav backends to be recognised (syncdav.so requires libneon-gnutls.so.27). Graham From tino.keitel+syncevolution at tikei.de Fri Feb 22 10:31:28 2019 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Fri, 22 Feb 2019 11:31:28 +0100 Subject: [SyncEvolution] Newer phones with syncml support In-Reply-To: <1919d27b-9b43-fc0d-d0a1-b632406e4d4f@gmail.com> References: <1919d27b-9b43-fc0d-d0a1-b632406e4d4f@gmail.com> Message-ID: <20190222103128.fkyw677rfnmrhav6@tikei.de> On Tue, Jan 15, 2019 at 00:27:35 +0300, Andrey Butirsky wrote: > Hi, > personally, I don't understand too why we have to give up that easily. > > There is no real alternative indeed, and having to keep all the contacts > in clear text on server at BB service, or organize "home services" for > that is just a ridiculous.. Hi, from my POV, SyncML also requires a "home service" to sync with. Yes, setting up CalDAV/CardDAV requires some knowledge. I use DAViCal. It requires setting up a PostgreSQL database, adjusting the configuration for DAViCal and setting up user accounts using the DACiCal web frontend. However, it's not that hard at all, and could be streamlined with some effort. At the end, you get features like shared calendars, auto-discovery of all addressbooks/calendars assigned to the users (via bindings), cheap background sync over HTTPS without manual interaction and compatibility with current smartphone operating systems. It's also a lot easier to keep multiple devices (more than two) in sync. iOS comes with CalDAV/CardDAV support OOTB. On Android, third party apps are required, as Google internally uses some sort of CalDAV/CardDAV but does not expose it to use it with your own server AFAICS. Regards, Tino _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Sat Feb 23 01:05:24 2019 From: deloptes at gmail.com (deloptes) Date: Sat, 23 Feb 2019 02:05:24 +0100 Subject: [SyncEvolution] Newer phones with syncml support References: <1919d27b-9b43-fc0d-d0a1-b632406e4d4f@gmail.com> <20190222103128.fkyw677rfnmrhav6@tikei.de> Message-ID: Tino Mettler wrote: > from my POV, SyncML also requires a "home service" to sync with. > > Yes, setting up CalDAV/CardDAV requires some knowledge. I use DAViCal. > It requires setting up a PostgreSQL database, adjusting the configuration > for DAViCal and setting up user accounts using the DACiCal web frontend. > However, it's not that hard at all, and could be streamlined with some > effort. > > At the end, you get features like shared calendars, auto-discovery of > all addressbooks/calendars assigned to the users (via bindings), cheap > background sync over HTTPS without manual interaction and compatibility > with current smartphone operating systems. It's also a lot easier to > keep multiple devices (more than two) in sync. > > iOS comes with CalDAV/CardDAV support OOTB. ?On Android, third party > apps are required, as Google internally uses some sort of > CalDAV/CardDAV but does not expose it to use it with your own server > AFAICS. Hi Tino, thank you for sharing. My problems are that firstly I loose something that was working good for so many years and is sufficient for my needs. Second I do not want to access my home network via WLAN and last I do not want to use WLAN on the phone all the time. You may add the lack of choice that is gone as well. But thanks anyway. regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From dclement1 at laposte.net Fri Feb 1 15:08:51 2019 From: dclement1 at laposte.net (Daniel CLEMENT) Date: Fri, 1 Feb 2019 16:08:51 +0100 Subject: [SyncEvolution] Sync daemon must be started manually Message-ID: <1549033731.9883.1.camel@laposte.net> Hello, I have installed Debian "Stretch" (version 9) and I have noticed that the syncevo-dbus-server is not launched at startup. If I "prime" it with a manual sync, then the subsequent automatic syncs indeed work. But how should I get the Syncevolution daemon to start automatically? I have compared with my old install, by I understand that the startup process is different now, and I can't reuse the startup helper script. TIA for any help - best regards, -- Daniel CLEMENT _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution