From: Thomas Danckaert <post@thomasdanckaert.be>
To: mbakke@fastmail.com
Cc: guix-devel@gnu.org
Subject: Re: wrong key used for signing
Date: Wed, 29 Mar 2017 09:55:58 +0200 (CEST) [thread overview]
Message-ID: <20170329.095558.467722765658034015.post@thomasdanckaert.be> (raw)
In-Reply-To: <87y3vptuxw.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1.1: Type: Text/Plain, Size: 983 bytes --]
(now actually including the signature... sigh)
From: Marius Bakke <mbakke@fastmail.com>
Subject: Re: wrong key used for signing
Date: Tue, 28 Mar 2017 15:03:23 +0200
>> If you can send a signed message (using key D77D54FD according to
>> my
>> books) containing the public key of the key used to sign these
>> commits
>> (so they can be verified), I think that is proof enough. Assuming
>> you
>> admit to making them, of course :-)
>
> To be clear, simply "vouching" for the commits in a signed message
> is
> good enough for me. It would be good to have the signing key for
> future
> reference, but if you don't want to disclose it I'm fine with that.
As Leo found out, it's just an old key (that I didn't intend to use
anymore, I should probably just revoke it). For now, I signed it
with the new key (find it here:
http://http-keys.gnupg.net/pks/lookup?search=0x91E12B08&op=vindex).
For sake of completeness: I vouch for the commits referenced in the
attached log.
Thomas
[-- Attachment #1.2: commit.log --]
[-- Type: Text/Plain, Size: 2198 bytes --]
commit e1abe244f3810e5a1bb82ed70c2290e54d87ac95
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 14:16:54 2017 +0100
gnu: libreoffice: Update to 5.3.1.2.
* gnu/packages/libreoffice.scm (libreoffice): Update to 5.3.1.2.
[inputs]: Add libstaroffice and libzmf.
[arguments]: Remove reference to removed patch; unpack xmlsec
1.2.23 tarball.
(xmlsec-src-libreoffice): Update to version 1.2.23 tarball.
commit 5dc2875fa279739e79c3ea7bc0bbd85814c25dcc
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 13:57:18 2017 +0100
gnu: orcus: Update to 0.12.1.
* gnu/packages/libreoffice.scm (orcus): Update to 0.12.1.
[inputs]: Add python.
commit 65cb686e887d8e6311f48c716f8fd29d409db5d0
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 13:53:56 2017 +0100
gnu: libetonyek: Update to 0.1.6.
* gnu/packages/libreoffice.scm (libetonyek): Update to 0.1.6.
[arguments]: Add phase 'autoreconf, because configure.ac is
patched. Add
configure flag "--with-mdds=1.2".
[inputs]: Add liblangtag.
[native-inputs]: Add autoconf and automake.
* gnu/packages/patches/libetonyek-build-with-mdds-1.2.patch: New
file.
* gnu/local.mk (dist_patch_DATA): Add it.
commit c2afb00f1145e136d0a97632cbd0a8dc3ccc2ca8
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 13:37:57 2017 +0100
gnu: Add libstaroffice.
* gnu/packages/libreoffice.scm (libstaroffice): New variable.
commit 4e70c654d52c0d93069f8ceec0face6f24cb249e
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 12:25:29 2017 +0100
gnu: ixion: Update to 0.12.2.
* gnu/packages/libreoffice.scm (ixion): Update to 0.12.2.
[inputs]: Replace python-2 by python.
commit 9adf830916a244c857187be02b18b25603551781
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 12:19:22 2017 +0100
gnu: mdds: Upgrade to 1.2.2.
* gnu/packages/boost.scm (mdds): Upgrade to 1.2.2.
commit 5bcb40fc37b065672c3a88811dfb170a6d44908a
Author: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Fri Mar 24 11:58:22 2017 +0100
gnu: Add libzmf.
* gnu/packages/libreoffice.scm (libzmf): New Variable.
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-29 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:25 wrong key used for signing Thomas Danckaert
2017-03-28 8:47 ` Marius Bakke
2017-03-28 13:03 ` Marius Bakke
2017-03-28 18:40 ` Leo Famulari
2017-03-29 7:38 ` Thomas Danckaert
2017-03-29 7:55 ` Thomas Danckaert [this message]
2017-03-28 18:35 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170329.095558.467722765658034015.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.