-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 2013-01-25 04:06, schrieb Daniel Kahn Gillmor:
On 01/13/2013 02:22 PM, Willi Mann wrote:
Yes, go ahead. Of course, if you manage to allow for a
repeatable build, that would be great.
well i've tried a bit, but haven't gotten it down to a
On 01/25/2013 01:14 PM, Willi Mann wrote:
That's OK. You actually only promised to get closer to a repeatable
build, which you reached, judging from your commits :-)
thanks for your understanding :) I've been frustrated with the build
system for enigmail for years now, and this process
On 01/13/2013 02:22 PM, Willi Mann wrote:
Yes, go ahead. Of course, if you manage to allow for a repeatable
build, that would be great.
well i've tried a bit, but haven't gotten it down to a repeatable build
yet. I figure it's better to push the fixes i have gotten in than to
let banging my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Am 2013-01-13 06:19, schrieb Daniel Kahn Gillmor:
This was reported to upstream, and is fixed in their repo, but
hasn't made it into any released version yet.
The upstream patch (modified for our build layout) is attached
below. I've
On 01/13/2013 05:13 AM, Willi Mann wrote:
I'm fine with you adding the patch and adding yourself as uploader. I
leave it to you to decide whether an upload for a single patch is
justified. While you are at it, you could also add the VCS lines to
debian/control.
ah, good idea. looking at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 2013-01-13 19:50, schrieb Daniel Kahn Gillmor:
ah, good idea. looking at the packaging, i'm tempted to set the
debian/source/format to 3.0 (quilt) as well, since it's already
in basic shape for that. any objections to that change? that
Package: enigmail
Version: 2:1.5.0+id17-1
Severity: normal
Tags: upstream patch
Control: forwarded -1
https://lists.enigmail.net/pipermail/enigmail-users_enigmail.net/2013-January/000437.html
enigmail appears to truncate the last line when displaying decrypted
some PGP/MIME messages.
This was
7 matches
Mail list logo
