Debian Bug report logs - #692984
RFP: sogo-connector -- full DAV client for Thunderbird/IceDove

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Joseph Nahmias <joe@nahmias.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ITP: sogo-connector -- full DAV client for Thunderbird/IceDove

Date: Sun, 11 Nov 2012 12:41:14 -0500

Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias <joe@nahmias.net>

* Package name    : sogo-connector
  Version         : 10.0.3
  Upstream Author : Inverse, Inc
* URL             : http://sogo.nu/
* License         : GPL2
  Programming Lang: XUL/Javascriopt
  Description     : full DAV client for Thunderbird/IceDove

 This extension enables Thunderbird/IceDove as a full DAV client for use
 with groupware servers (such as SOGo).  Features include:
 .
  * Event organizers
  * CardDAV support that is generic, so you can use it with any
    address book service (eg. fruux)
  * Support for WebDAV access control lists (ACL)

Message #10 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: Joseph Nahmias <joe@nahmias.net>, 692984@bugs.debian.org, 705488@busg.debian.org

Subject: Re: Bug#692984: ITP: sogo-connector -- full DAV client for Thunderbird/IceDove

Date: Wed, 21 Aug 2013 13:03:14 +0200

Hello Joseph,

On Sun, Nov 11, 2012 at 12:41:14PM -0500, Joseph Nahmias wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Joseph Nahmias <joe@nahmias.net>
> 
> * Package name    : sogo-connector
>   Version         : 10.0.3
>   Upstream Author : Inverse, Inc
> * URL             : http://sogo.nu/
> * License         : GPL2
>   Programming Lang: XUL/Javascriopt
>   Description     : full DAV client for Thunderbird/IceDove
> 
>  This extension enables Thunderbird/IceDove as a full DAV client for use
>  with groupware servers (such as SOGo).  Features include:
>  .
>   * Event organizers
>   * CardDAV support that is generic, so you can use it with any
>     address book service (eg. fruux)
>   * Support for WebDAV access control lists (ACL)

what about your ITP for the sogo-connector?
I worked locally with the packaging for this plugin and would like to do
the packaging for Debian because the have since a few weeks a user wish
for for the sogo-connector addon (see #705488).
I have talked to Jeroen about some possible problems with the
sogo-connector. He can provide me/us a personal login to the sogo
instance on the servers on inversa.ca for a better testing of the
package.

Regards
Carsten

Message #15 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: 692984@bugs.debian.org

Cc: c.schoenert@t-online.de, joe@nahmias.net

Subject: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Thu, 29 Aug 2013 14:21:20 +0200

I have a Debian wheezy server running the DAViCal package

On the desktop, I have icedove and iceowl-extension (Calendar).  They
work fine with the DAViCal server for calendar/tasks.  I've also tested
the Evolution client using DAViCal for contacts, that works fine too.

I downloaded upstream's SOGo Connector plugin for ThunderBird 10 and
installed it in icedove.  It appears to install successfully and I can
define a "Remote Address Book", but I can't see any of the contacts in
DAViCal and I can't create any either.

Is the ThunderBird 17 variant of this plugin more likely to work
successfully?

Is the TB10 or TB17 variant unsupported on icedove in any way?  If
upstream only supports Thunderbird and not icedove, is it a problem for
packaging?

Has anybody started a VCS for packaging this?  I would be happy to try
it further and provide feedback.

Message #20 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Jeroen Dekkers <jeroen@dekkers.ch>

To: Daniel Pocock <daniel@pocock.com.au>, 692984@bugs.debian.org

Cc: c.schoenert@t-online.de, joe@nahmias.net

Subject: Re: Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Thu, 29 Aug 2013 14:57:21 +0200

At Thu, 29 Aug 2013 14:21:20 +0200,
Daniel Pocock wrote:
> I have a Debian wheezy server running the DAViCal package
> 
> On the desktop, I have icedove and iceowl-extension (Calendar).  They
> work fine with the DAViCal server for calendar/tasks.  I've also tested
> the Evolution client using DAViCal for contacts, that works fine too.
> 
> I downloaded upstream's SOGo Connector plugin for ThunderBird 10 and
> installed it in icedove.  It appears to install successfully and I can
> define a "Remote Address Book", but I can't see any of the contacts in
> DAViCal and I can't create any either.
> 
> Is the ThunderBird 17 variant of this plugin more likely to work
> successfully?

The plugin is developed for SOGo and only tested on SOGo, so I don't
think the newer version is more likely to work than the older
version...


Kind regards,

Jeroen Dekkers

Message #25 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: Jeroen Dekkers <jeroen@dekkers.ch>

Cc: 692984@bugs.debian.org, c.schoenert@t-online.de, joe@nahmias.net

Subject: Re: Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Thu, 29 Aug 2013 15:00:58 +0200

On 29/08/13 14:57, Jeroen Dekkers wrote:
> At Thu, 29 Aug 2013 14:21:20 +0200,
> Daniel Pocock wrote:
>> I have a Debian wheezy server running the DAViCal package
>>
>> On the desktop, I have icedove and iceowl-extension (Calendar).  They
>> work fine with the DAViCal server for calendar/tasks.  I've also tested
>> the Evolution client using DAViCal for contacts, that works fine too.
>>
>> I downloaded upstream's SOGo Connector plugin for ThunderBird 10 and
>> installed it in icedove.  It appears to install successfully and I can
>> define a "Remote Address Book", but I can't see any of the contacts in
>> DAViCal and I can't create any either.
>>
>> Is the ThunderBird 17 variant of this plugin more likely to work
>> successfully?
> The plugin is developed for SOGo and only tested on SOGo, so I don't
> think the newer version is more likely to work than the older
> version...
>

The way it is described on their web site:

SOGo "connector" plugin: suitable for "horizontal" deployment - generic
CalDAV/CardDAV for any server

SOGo "integrator" plugin: suitable for "vertical" deployment - uses
features specific to SOGo servers

There are many online forum discussions suggesting it works with DAViCal
and others.

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

Message #30 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: Daniel Pocock <daniel@pocock.com.au>, 692984@bugs.debian.org

Cc: Jeroen Dekkers <jeroen@dekkers.ch>, joe@nahmias.net

Subject: Re: Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Thu, 29 Aug 2013 15:37:49 +0200

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.
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.

Regrads
Carsten

Message #33 received at 692984-submitter@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: 692984-submitter@bugs.debian.org

Subject: Re: Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Fri, 30 Aug 2013 20:57:41 +0200

Hello,

On Thu, Aug 29, 2013 at 03:37:49PM +0200, Carsten Schoenert wrote:
> 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.

I have worked again on the packaging of the sogo-connector. My work can
be found on:
https://github.com/tijuca/sogo-connector

I have installed the package xul-ext-sogo-connector*.deb on a Wheezy
installation with the current Icedove 17.0.8-1 from stable-security.
But until now I don't have done any integration into OwnCloud for
example or something else.

So far I can see there seems to be a little problem in the preferences
menu for SoGo connector with some entity problems within the file
/usr/share/xul-ext/sogo-connector/chrome/content/sogo-connector/preferences/edit-category.xul
and the line
<label value="&pref.categories.name.label;" control="categoryName"/>
but I doesn't have investigate this thery much.

The deb package and related files cann be found on:
http://openmct.org/misc/sogo-connector/

If someone found some error or solution, please let me know!
I know that the packaging isn't perfect, but it's for now o.k. I think. ;)

Regards
Carsten

Message #38 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: Carsten Schoenert <c.schoenert@t-online.de>

Cc: 692984@bugs.debian.org, Jeroen Dekkers <jeroen@dekkers.ch>, joe@nahmias.net

Subject: Re: Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Sat, 31 Aug 2013 17:36:18 +0200

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.

Message #45 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: Daniel Pocock <daniel@pocock.com.au>, 692984@bugs.debian.org

Cc: Jeroen Dekkers <jeroen@dekkers.ch>, joe@nahmias.net

Subject: Re: Bug#692984: upstream binary / DAViCal / CardDAV problems on wheezy

Date: Tue, 11 Feb 2014 23:18:06 +0100

Hello Daniel,

I imported the latest upstream version 24 of the sogo-connector and
rebuild the package. The current output of git-buildpackage will be
found on the links I posted earlier.

On Sat, Aug 31, 2013 at 05:36:18PM +0200, Daniel Pocock wrote:
> 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.

I plan to write a wiki page if the package is once available thrue the
repositorys. Your summary above would be good to place then there.

> 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.

Sadly true, maybe I can talk about that with Jeroen in the near future.

> 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.

I don't believe Mozilla will work on such "minor" issues. We can be
happy if Mozilla is making some housekeeping inside the code and
implements some more core requirements like the TLS 1.2 implementation
in the near past.
We will see. :)

Regards
Carsten

Message #50 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Boris Barbour <boris.barbour@ens.fr>

To: 692984@bugs.debian.org

Subject: Expected upload of sogo-connector

Date: Wed, 30 Apr 2014 12:41:12 +0200

I'm interested in obtaining the sogo-connector, as this seems to be the 
only way to sync contacts with owncloud. I'd prefer to get it through 
the debian repositories. The messages above suggest that it could be (or 
has been) uploaded, which is good news. When might we expect it to appear?

Message #55 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: boris.barbour@ens.fr

Cc: 692984@bugs.debian.org

Subject: Re: Bug#692984: Expected upload of sogo-connector

Date: Wed, 30 Apr 2014 13:46:26 +0200

Hello Boris,

Am 30.04.2014 12:41, schrieb Boris Barbour:
> I'm interested in obtaining the sogo-connector, as this seems to be the 
> only way to sync contacts with owncloud. I'd prefer to get it through 
> the debian repositories. The messages above suggest that it could be (or 
> has been) uploaded, which is good news. When might we expect it to appear?

thanks for your interests!
I don't know then the FTP Team will allow the upload of the package, so
sorry, I can't say something promising right now.

You can rebuild the package by yourself using the current repository
which will be found on

  https://github.com/tijuca/sogo-connector

You will probably need a sid chroot to build the package, right know I
always used git-pbuilder and doesn't have cared about backports or so.
But that should not be a big problem to created a wheezy-backport
package too.

-- 
Regards
Carsten

Message #60 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Luca Capello <luca@pca.it>

To: 692984@bugs.debian.org

Cc: Carsten Schoenert <c.schoenert@t-online.de>, boris.barbour@ens.fr, Paul van der Vlis <paul@vandervlis.nl>, Thomas Maass <mase@setho.org>

Subject: Re: Bug#692984: Expected upload of sogo-connector

Date: Tue, 22 Jul 2014 13:59:20 +0200

[Message part 1 (text/plain, inline)]

forcemerge 692984 659291
reassign 705488 wnpp
forcemerge 692984 705488
user contact@itopie.ch
usertags 692984 + itopie.ch-installation
user it@codha.ch
usertags 692984 + codha.ch-installation
thanks

Hi there!

Merging all relevant/duplicate bugs and Cc:ing all the interested
people.

On Wed, 30 Apr 2014 13:46:26 +0200, Carsten Schoenert wrote:
> Am 30.04.2014 12:41, schrieb Boris Barbour:
> > I'm interested in obtaining the sogo-connector, as this seems to be the 
> > only way to sync contacts with owncloud. I'd prefer to get it through 
> > the debian repositories. The messages above suggest that it could be (or 
> > has been) uploaded, which is good news. When might we expect it to appear?
> 
> thanks for your interests!
> I don't know then the FTP Team will allow the upload of the package, so
> sorry, I can't say something promising right now.

The package is still in the NEW queue, please remember to close this bug
when the package will enter Debian, since the current debian/changelog
does not automatically close any bug:

  <https://ftp-master.debian.org/new/sogo-connector_24.0.5-1.html>

> You can rebuild the package by yourself using the current repository
> which will be found on
> 
>   https://github.com/tijuca/sogo-connector

Any reason why this is not on Alioth?

> You will probably need a sid chroot to build the package, right know I
> always used git-pbuilder and doesn't have cared about backports or so.
> But that should not be a big problem to created a wheezy-backport
> package too.

Actually, using a *plain* wheezy chroot is not enough:
=====
[...]
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
The following NEW packages will be installed:
  bsdmainutils{a} debhelper{a} file{a} gettext{a} gettext-base{a}
  groff-base{a} html2text{a} intltool-debian{a} libasprintf0c2{a}
  libcroco3{a} libffi5{a} libgettextpo0{a} libglib2.0-0{a} libmagic1{a}
  libpcre3{a} libpipeline1{a} libunistring0{a} libxml2{a} man-db{a}
  po-debconf{a}
0 packages upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 9191 kB/9656 kB of archives. After unpacking 25.6 MB will be used.
The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: icedove-dev (>= 24~) but it is not going to be installed.
                                 Depends: mozilla-devscripts (>= 0.32~) but it is not going to be installed.
                                 Depends: python-ply but it is not going to be installed.
Unable to resolve dependencies!  Giving up...
[...]
Abort.
E: pbuilder-satisfydepends failed.
=====

Here is the reason:
=====
$ rmadison icedove-dev | grep wheezy
 icedove-dev | 10.0.12-1          | wheezy            | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
 icedove-dev | 17.0.10-1~deb7u1   | wheezy-security   | ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel
 icedove-dev | 24.5.0-1~deb7u1    | wheezy-security   | s390, sparc
 icedove-dev | 24.6.0-1~deb7u1    | wheezy-security   | amd64, armel, armhf, i386, powerpc, s390x
$ 
=====

I confirm that adding the wheezy-security repository is enought to build
a wheezy-backports without changing anything in the current Debian
sources on GitHub.

Since we currently use this extension, I am interested in a
wheezy-backports and I could maintain it by myself, but only once it
reaches testing and anyway not before the next 3 months.

Thx, bye,
Gismo / Luca

[signature.asc (application/pgp-signature, inline)]

Message #69 received at 692984@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: Luca Capello <luca@pca.it>, 692984@bugs.debian.org

Cc: boris.barbour@ens.fr, Paul van der Vlis <paul@vandervlis.nl>, Thomas Maass <mase@setho.org>

Subject: Re: Bug#692984: Expected upload of sogo-connector

Date: Tue, 22 Jul 2014 20:42:20 +0200

Hello Luca,

Am 22.07.2014 13:59, schrieb Luca Capello:
> Any reason why this is not on Alioth?

there is no special reason, I just started last year the packaging and
wanted the repo putting in some "official" place to let other see the
current state. But I wanted be able to rebase and push my work without
any take care for on person depended on a repository in a more public
place like Alioth.

Once the package is accepted it will move to Alioth.

> Actually, using a *plain* wheezy chroot is not enough:
...
> Here is the reason:
> =====
> $ rmadison icedove-dev | grep wheezy
>  icedove-dev | 10.0.12-1          | wheezy            | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
>  icedove-dev | 17.0.10-1~deb7u1   | wheezy-security   | ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel
>  icedove-dev | 24.5.0-1~deb7u1    | wheezy-security   | s390, sparc
>  icedove-dev | 24.6.0-1~deb7u1    | wheezy-security   | amd64, armel, armhf, i386, powerpc, s390x
> $ 
> =====
> 
> I confirm that adding the wheezy-security repository is enought to build
> a wheezy-backports without changing anything in the current Debian
> sources on GitHub.

I know this circumstance, but thanks for hinting.

> Since we currently use this extension, I am interested in a
> wheezy-backports and I could maintain it by myself, but only once it
> reaches testing and anyway not before the next 3 months.

A backport is heavily depending on entering the testing release, so I
still don't care much about it in the current state. But as you wrote
it's more a question of the chroot to build a backport package. Right
know I would be happy to get the connector into testing before the freeze.

-- 
Regards
Carsten

Message #76 received at 692984-submit@bugs.debian.org (full text, mbox, reply):

From: Carsten Schoenert <c.schoenert@t-online.de>

To: 692984-submit@bugs.debian.org, 692984-done@bugs.debian.org

Date: Fri, 12 Sep 2014 19:02:50 +0200

659291submit@bugs.debian.org, 659291-done@bugs.debian.org,
705488submit@bugs.debian.org, 705488-done@bugs.debian.org,
Cc: control@bugs.debian.org
Bcc: 
Subject: Closing RFP: sogo-connector -- full DAV client for Thunderbird/IceDove
Reply-To: 
In-Reply-To: <1406372094-2616-bts-lucas@debian.org>

Version: 24.0.5-1

Hello there,

now the sogo-connector package is accepted by the ftp-master team and
currently available in the experimental repository, I will close this
various RFP's.

Sogo has released version 24.0.6 in the between times. As soon as
possible I will prepare a new upload after my holidays.

Regards
Carsten

Send a report that this bug log contains spam.