Package: enigmail / 2:1.9.9-1~deb8u1

Metadata

Package Version Patches format
enigmail 2:1.9.9-1~deb8u1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
0001 avoid eslint during buildtest.patch | (download)

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 avoid eslint during buildtest

eslint is not yet in debian (see https://bugs.debian.org/743404).
once it is packaged, we should remove this patch and allow the full
testsuite to run on the debian buildd infrastructure.

0002 ensure that everything is built before building the .patch | (download)

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 ensure that everything is built before building the xpi.

When building in parallel avoid a race condition.  Without this fix,
"make -j4" sometimes fails.

See, for example:

https://buildd.debian.org/status/fetch.php?pkg=enigmail&arch=all&ver=2%3A1.9.5-3&stamp=1477332121&file=log

0003 Allow re certifying keys that have expired certifica.patch | (download)

package/keyEditor.jsm | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 allow re-certifying keys that have expired certifications.

Some people have made expiring certifications on other keys.  After
such a certification expires, they might want to re-certify with the
same key (e.g. if they've checked with the other person that they're
still using the key).

If this happens, enigmail fails obscurely ("signing failed").

In the log is:

2017-05-15 14:41:15.494 [DEBUG] keyManagmenent.jsm: GpgEditorInterface.processLine: '[GNUPG:] GET_BOOL sign_uid.replace_expired_okay'
2017-05-15 14:41:15.494 [ERROR] Unknown command prompt: [GNUPG:] GET_BOOL sign_uid.replace_expired_okay

I believe this patch should resolve the problem.