[Pkg-mozext-maintainers] Regression update for Thunderbird in jessie-security (aka oldstable)?
c.schoenert at t-online.de
Mon Jul 31 20:38:19 UTC 2017
Am 31.07.2017 um 11:55 schrieb Daniel Kahn Gillmor:
> Hi Carsten--
> Thank you very much for your work for keeing thunderbird ESR up-to-date
> in debian. Sorry that enigmail is an ongoing problem for that work.
no worries. In the past we had also xul-ext-foxyproxy-standard that also
made sometimes troubles. And in all this kind of issues brings up some
spice into the 'typical' workflow.
> On Fri 2017-07-28 10:56:48 +0200, Carsten Schoenert wrote:
>> We need some auto testing stuff that will help to discover such problems
>> early as there are also some other typical extensions that maybe break
>> by every new ESR version of Thunderbird.
> I think this is a great idea. I wrote mail to the enigmail mailing list
> earlier this month to see whether there was any existing work we could
> piggy-back off of:
> I got some interesting pointers/suggestions in response, but no specific
> I'd welcome help from anyone who wants to write a full-stack test that
> we could use for an enigmail autopkgtest, though.
> I'm imagining an autopkgtest that does (at least) the following:
> * sets up a local MTA (postfix?)
> * sets up a local IMAP server (dovecot?)
> * creates accounts Alice and Bob on both servers
> - both accounts should be able to send and receive mail
> * creates two thunderbird profiles (maybe using different system user accounts?)
> * triggers the enigmail setup process on both accounts
> * exchanges keys between the accounts (how?)
> * Alice sends encrypted mail to Bob
> * Bob reads encrypted mail
> With that in place, we could talk about embellishing the test suite to
> include things like attachments, multiparty mail, etc.
> Does this seem feasible/useful? Is anyone interested in working on this
> with me?
The last days I was also talking about that with Guido to check the
possibilities for testing Thunderbird itself more automatically and also
after such tests some typical extensions. I'm very interested in doing
these kind of things as this make my life as a co-maintainer more easy
as the tests will show immediately if something is not working well
Unfortunately I've no knowledge about how to do some GUI related testing
and interactions. So I would need some kind of scaffolding there I can
OTOH there should be something possible by the XUL language itself, the
extensions are doing the same in the core.
So o.k., i guess the list you wrote up is a good start for now. I will
see what the outcome of the next two weeks will be. But even if don't we
have something ready then we should try to keep some focus on this in
the next time.
>> Hopefully we find some time to talk about that all at DebCamp/DebConf?
> Sadly, i won't make it to debconf this year.
Meeh, that's said. :(
Don't make this the common case, you wasn't also seen in Capetown! :P
More information about the Pkg-mozext-maintainers