#975115 webext-dav4tbsync and webext-tbsync out of sync

#975115#5
Date:
2020-11-19 08:08:57 UTC
From:
To:
Hi,

Thank you very much for maintaining and updating the tbsync packages in
Debian. The current version of webext-dav4tbsync is now compatible with
thunderbird 78 but it cannot be used as it seems to be out of sync with
webext-tbsync.

When I try to add a new "CalDAV & CardDAV" account tbsync tells me:
---
Provider "CalDAV & CardDAV" for TbSync is not yet installed.

Click on the following link to open the info page of the missing
synchronization provider. There you will find further information about
the provider and you will have the option to install it:

https://tbsync.jobisoft.de/beta/TB78/DAV-4-TbSync.xpi

[...]
---


I've already set-up CalDAV accounts a while ago when it was still
working. These accounts are shown in tbsync with a red exclamation mark
(instead of being active) and the following error is displayed:
--- This account requires the DAV synchronization provider, which is currently not installed. https://tbsync.jobisoft.de/beta/TB78/DAV-4-TbSync.xpi --- Although, of course, the most recent Debian packages for webext-dav4tbsync (1.23-1, but probably not the mentioned beta version) and webext-tbsync (2.18-2) are installed and show up in TB's add-ons section as enabled. I would be great to have working set of tbsync packages in Debian again. Kind regards Tom
#975115#10
Date:
2020-11-19 11:24:04 UTC
From:
To:
Which branch do you use (buster or sid)

Which version of webext-tbsync and webext-eas4tbsync do you have installed?

Regards

#975115#15
Date:
2020-11-22 22:44:08 UTC
From:
To:
I'm also having problems with this on sid. When I open the thunderbird addon
manager, I see tbsync, dav4tbsync, and eas4tbsync all installed and enabled.
All of these come from the debian packages. However, when I open the tbsync
config window it claims that dav4tbsync is not installed. There is no such
problem with eas4tbsync (webext-eas4tbsync 1.20-1), which works fine.

#975115#20
Date:
2020-11-23 06:11:16 UTC
From:
To:
Hello,

Can you provide a screenshot of the window with that message. Please
provide another screenshot of

Options - Add-Ons

where I can see the status of that packages.

I can't reproduce this problem.

Regards

Mechtilde

Am 22.11.20 um 23:44 schrieb Carl Suster:

#975115#25
Date:
2020-11-23 06:42:33 UTC
From:
To:
Hi Mechtilde,

I've attached 3 screenshots: the first shows the addons page. The second shows the tbsync preferences window with that message. The selected account, labelled Google, is one that I set up earlier this year when I had thunderbird 68 and older versions of the tbsync packages when everything was working. Now that account has the red warning icon and the message shown. The third screenshot shows what I see if I try to add a new CalDAV account in tbsync.

Cheers,
Carl

#975115#30
Date:
2020-11-23 06:45:45 UTC
From:
To:
I've just noticed this message in the debug log for tbsync about the
provider failing to load:

    ** Mon Nov 23 2020 17:43:57 GMT+1100 (AEDT) **
    [Initializing module] : <messenger>

    ** Mon Nov 23 2020 17:43:57 GMT+1100 (AEDT) **
    [TbSync init] : Done

    ** Mon Nov 23 2020 17:43:57 GMT+1100 (AEDT) **
    [EventLog] : FAILED to load provider <dav>
    API version mismatch, TbSync@Beta 2.4 vs dav@2.4

#975115#35
Date:
2020-11-24 19:04:44 UTC
From:
To:
Hi

Thanks, Mechtilde for your fast reply and sorry for my delayed answer. I
didn't realize I had to subscribe to "my own" bugs...

Thanks, Carl for providing the necessary information in the meantime.

I'm using Backports of your tbsync-packages for Buster (with the latest
thunderbird).

But of course, I've tested under sid as well (a fresh install in a new
VM before I opened the bug) with the same result.

I'm happy to help testing or provide more info.

Regards
Tom

#975115#40
Date:
2020-11-24 22:38:59 UTC
From:
To:
Hi Mechtilde,

I've just upgraded to tbsync 2.19-1 and now I have the opposite problem: tbsync
recognises that dav4tbsync is is installed, but claims that eas4tbsync is
missing.

The situation for the EAS provider is now similar to what I reported above. The
debug log shows:

    ** Wed Nov 25 2020 09:14:49 GMT+1100 (AEDT) **
    [EventLog] : FAILED to load provider <eas>
    API version mismatch, TbSync@2.4 vs eas@Beta 2.4

    ** Wed Nov 25 2020 09:14:52 GMT+1100 (AEDT) **
    [Loaded provider] : dav::CalDAV & CardDAV (1.23)

There's also a message in the log concerning the DAV provider, though it's
perhaps unrelated:

    Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]

    promisifiedHttpRequest/<@chrome://dav4tbsync/content/includes/network.js:515:64
    promisifiedHttpRequest@chrome://dav4tbsync/content/includes/network.js:494:12
    sendRequest@chrome://dav4tbsync/content/includes/network.js:428:33

I wonder if it's just that the providers need a stricter versioned dependency
relationship with the main tbsync package to reflect whatever API version
checks tbsync is doing internally?

Cheers,
Carl

#975115#45
Date:
2021-01-11 15:41:20 UTC
From:
To:
Hi everyone,

just installed webext-dav4tbsync on buster (incl. tbsync 2.18-1~deb10u1)
and was bitten by this bug.

Then I downloaded tbsync 2.18 from TB addons, unzip'ed both tbsync xpi
and ran a diff on them:

Only in orig/: CONTRIBUTORS.md
Only in orig/: LICENSE
Only in orig/: README.md
Only in orig/_locales: Readme.txt
diff -urb orig/content/modules/providers.js
dpkg/content/modules/providers.js
--- orig/content/modules/providers.js   2020-08-28 18:07:42.000000000 +0200
+++ dpkg/content/modules/providers.js   2020-10-16 13:38:49.000000000 +0200
@@ -14,10 +14,10 @@
    defaultProviders: {
      "dav" : {
        name: "CalDAV & CardDAV",
-      homepageUrl: "https://addons.thunderbird.net/addon/dav-4-tbsync/"},
+      homepageUrl:
"https://tbsync.jobisoft.de/beta/TB78/DAV-4-TbSync.xpi"},
      "eas" : {
        name: "Exchange ActiveSync",
-      homepageUrl: "https://addons.thunderbird.net/addon/eas-4-tbsync/"},
+      homepageUrl:
"https://tbsync.jobisoft.de/beta/TB78/EAS-4-TbSync.xpi"},
    },

    loadedProviders: null,
diff -urb orig/content/tbsync.jsm dpkg/content/tbsync.jsm
--- orig/content/tbsync.jsm     2020-10-16 12:50:02.000000000 +0200
+++ dpkg/content/tbsync.jsm     2020-10-16 13:38:49.000000000 +0200
@@ -27,7 +27,7 @@
    addon: null,
    version: 0,
    debugMode: false,
-  apiVersion: "2.4",
+  apiVersion: "Beta 2.4",

    prefs: Services.prefs.getBranch("extensions.tbsync."),

diff -urb orig/manifest.json dpkg/manifest.json
--- orig/manifest.json  2020-10-16 13:40:28.000000000 +0200
+++ dpkg/manifest.json  2020-10-16 13:38:49.000000000 +0200
@@ -1,13 +1,14 @@
  {
    "applications": {
      "gecko": {
+  "update_url": "https://tbsync.jobisoft.de/beta/TB78/update-tbsync.json",
        "id": "tbsync@jobisoft.de",
        "strict_min_version": "78.0",
        "strict_max_version": "78.*"
      }
    },
    "manifest_version": 2,
-  "name": "TbSync",
+  "name": "TbSync [Beta Release Channel]",
    "version": "2.18",
    "author": "John Bieling",
    "homepage_url": "https://github.com/jobisoft/TbSync",

After that I replaced the dpkg included tbsync@jobisoft.de.xpi with the
TB addons download and got no more error.

HTH

Jan-Marek

#975115#50
Date:
2021-01-11 19:16:49 UTC
From:
To:
Ok - so - the API string in buster is actually:

$ rgrep "2\.4"
dav/content/provider.js:    static getApiVersion() { return "2.4"; }
eas/content/provider.js:    static getApiVersion() { return "Beta 2.4"; }
dpkg/content/tbsync.jsm:  apiVersion: "Beta 2.4",

So now EAS complains for me :-) But since I don't need that, I removed
it. But IMHO neither webext-eas4tbsync nor webext-tbsync should be
"Beta". I guess it's fixed for sid, where webext-tbsync is newer and
webext-eas4tbsync got a "version bump to 2.4" in 1.20-2.

HTH

Jan-Marek

#975115#55
Date:
2022-05-25 19:35:29 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
dav4tbsync, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 975115@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mechtilde Stehmann <mechtilde@debian.org> (supplier of updated dav4tbsync package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 25 May 2022 21:02:25 +0200
Source: dav4tbsync
Architecture: source
Version: 2.0.2~git20210801+08e4df1da-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers <pkg-mozext-maintainers@alioth-lists.debian.net>
Changed-By: Mechtilde Stehmann <mechtilde@debian.org>
Closes: 975115
Changes:
 dav4tbsync (2.0.2~git20210801+08e4df1da-3) unstable; urgency=medium
 .
   * Source only upload
   * Closes old and fixed bug (Closes: #975115)
Checksums-Sha1:
 974c357f12da7c7ce564744d365e86f98650e0de 2140 dav4tbsync_2.0.2~git20210801+08e4df1da-3.dsc
 011860da87fa291c1d5661c86ac6b3e340597c01 10240 dav4tbsync_2.0.2~git20210801+08e4df1da-3.debian.tar.xz
 e58d8aa13d8b1e1fed28dd61c9048d7d23f62a09 5890 dav4tbsync_2.0.2~git20210801+08e4df1da-3_amd64.buildinfo
Checksums-Sha256:
 209047506768454704ee4ea723d4eca468029185fe50bf434ab0eddc351f09e0 2140 dav4tbsync_2.0.2~git20210801+08e4df1da-3.dsc
 aaf05f7f2edbb9087b0ec7753410e1f0ca080b65e7e04f6278181cf7832a3501 10240 dav4tbsync_2.0.2~git20210801+08e4df1da-3.debian.tar.xz
 3be7931e0eef9c2aeab916b178a3d38bb42658c21469e860ef2d3c7b16f9d9dd 5890 dav4tbsync_2.0.2~git20210801+08e4df1da-3_amd64.buildinfo
Files:
 447af811187e15892c59f8bb98b17f95 2140 mail optional dav4tbsync_2.0.2~git20210801+08e4df1da-3.dsc
 c1c46a78c84e283a81d44620e992d771 10240 mail optional dav4tbsync_2.0.2~git20210801+08e4df1da-3.debian.tar.xz
 463e86ef06eb3047ff8512bde14ba6b7 5890 mail optional dav4tbsync_2.0.2~git20210801+08e4df1da-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmKOgmcACgkQ8od7uhQa
rX/BHQ//YdusbzGkUyTHAgGGPKEeD5k6HQ2sRly+duVjcMV3gb9s6zvQLGzdnnat
L9goEPPVcAB7E2EXeKULGoNWy/eyyGSJdq4u1AlC4el3FPJMccb2UH/GwArDStLR
xoeQbrCpAT7zQ3zGuAiTcr27w7K0wjm86DLzkxR2xfxscmeekZvpcxlNbOcXltNF
zy9QG3QOF2pBX2SsSgXFP838WyGGRYmXWzlvQaKzUWMC2sk/He5rAankc5Oh1mC9
VWzsx2UrC4gs/Q4ErRXOTkZDb1UlEerglWYNNpKeFMiM98lknFEM7OzbtyAHCodN
Lfg5aYQVcDMTqah7wiD0WzT07Az7WZghr991k2SD5ERu+1N2foUAhnKGE9Dn3KqP
IIQ/h1+QVhv0r854zqY7EjNWv4CraIdteT10+pLZla1GyfaQxZksBU7m4oXrffMy
lBkUjU4jpVVM0iUUjSc1pxXjl2Obr6Rytb/ZqN2V5ilbe2KTTMeuN8j8hR/cku/0
x4SlJwZU97KwgdsXpVkMTlE0HAIAgjVMhtwgbrK8cpwHABNTuNhBak9UEuEPS9fX
XMmKbkEpJtd2fhDTn02iTvFo8IV/KXLNiPQRDfpFMjTiV60R7qLC40hKw+fXfzr+
kvl07zp7YaK7aukZp1N+vDuNKD8oSdNCV7gj/FYokN7SJrjBmVk=
=QJOS
-----END PGP SIGNATURE-----