Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy
On 29/08/13 15:37, Carsten Schoenert wrote:
> Hello Daniel,
>
> On Thu, Aug 29, 2013 at 03:00:58PM +0200, Daniel Pocock wrote:
>> Is icedove 17 likely to appear in backports any time soon? I might try
>> building it on wheezy and run it with the SOGo connector 17 plugin to
>> see if it is more successful
>
> I don't think we will spend much time on getting ID17 in
> wheezy-backports. Christoph has uploaded Icedove 17.0.8-1 yesterday to
> stable-security. So shortly the latest version of Thunderbird will be
> landing in Wheezy thrue stable-security.
Great, thanks for making that available, I've tried 17 and I've filed a
couple of bug reports about upgrade experience but otherwise it works
for me although I haven't yet tried all features I normally use.
> The differences between stable-security and sid are quite marginal. We
> have to work more on the current build problems for soem platforms.
>
> Localy I have the sogo-connector packaged for Icedove 17, but until now
> I don't have it installed yet. For testing surpose I use the 10.0.12 in
> on my laptopt with testing.
> Right now I'm sitting in front of a Wheezy installation with a Icedove
> 17 from stable security. Maybe later I can install the sogo-connector
> here, right now I'm trying to get the next ESR release of Thunderbird
> (until now just 24.0b1) packaged.
>
> If there are no greater problems with my sogo-connector package I can
> provide you a download.
I found the solution to my problem using the connector
I can confirm that both the TB10 and TB17 connectors from upstream work
with the respective icedove versions in wheezy against a DAViCal server
on wheezy.
The reason it didn't work for me in the beginning is because the default
config in DAViCal is for a calendar-only resource.
Somehow, Evolution was able to use the calendar-only resource to store
vCards: that seems like a bug in both DAViCal and Evolution, they
shouldn't allow that. However, that left me thinking there was
something wrong with the SOGo Connector because it couldn't see the
contacts the Evolution could create and retrieve.
When I started looking around in the DAViCal settings, I realised I had
to create another resource for my address book and DAViCal creates a
different URL for that. I put that new address book URL in the SOGo
Connector and it is working.
It would be useful if the connector could give users a helpful error if
they misconfigure it like that, I had no useful error to help me and I
was just guessing what was wrong.
One minor problem left, Icedove address book only allows up to 2 email
addresses per contact but Evolution and Android allow more than 2. It
is not clear to me whether changing those contacts in Icedove's address
book will result in the loss of the extra email addresses when they sync.
Reply to: