Daniel Kahn Gillmor wrote:
> Hi Andy--
> 
> I'm one of the folks working on the debian packaging for enigmail.
> 
> This might be worth reporting on the Debian BTS as well.  Would you
> like to do that, or shall i?  If you have reportbug installed, you
> can just run "reportbug enigmail" and it should walk you through
> the process.

I'll do that - I only paused because reporting against testing is
sometimes frowned upon - especially when there are new releases in the
wings.

> On 02/01/2013 01:53 PM, Andy Ruddock wrote:
>> I've moved to Debian wheezy and unfortunately enigmail fails to
>> check signatures. Debug output produces the error :
>> 
>> Cc[NS_IPCBUFFER_CONTRACTID] is undefined at line 2302 in
>> enigmail.js
>> 
>> Trying to sign mail produces the error :
>> 
>> Cc[NS_IPCBUFFER_CONTRACTID] is undefined at line 1634 in
>> enigmail.js
> 
> your e-mail's User-Agent header suggests that you're using iceape
> (aka seamonkey) 2.7.11 -- is that right?

Yeah I'm using iceape, but the same errors occur when using icedove -
which is to be expected as they both use the same enigmail package.

> unfortunately, i don't see seamonkey 2.7 listed on upstream's 
> compability list at all:
> 
> http://enigmail.net/download/download-static.php
> 
> it seems to skip from 2.5 to 2.8 :(
> 
>> Debian reportbug suggests that a new version is available in 
>> experimental - but it can't be installed because that would break
>> iceape.
> 
> right, enigmail 1.5 wants iceape 2.14 or later, which isn't
> packaged for debian yet.
> 
> Patrick, Olav, other enigmail folks -- i'm pretty sure 2.7 is the 
> version of iceape/seamonkey that we'll be shipping in debian.  Is
> there a specific reason this version was skipped in the enigmail
> compatibility lists?
> 
> --dkg

Thanks for the quick response.

-- 
Andy Ruddock
------------
[email protected] (GPG Key ID 0xB0324245)

_______________________________________________
enigmail-users mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to