From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb@sourceware.org>
Subject: RE: [ANNOUNCEMENT] GDB 7.5.1 released!
Date: Sun, 02 Dec 2012 19:31:00 -0000 [thread overview]
Message-ID: <008c01cdd0c3$9c206020$d4612060$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20121202160710.GE18566@adacore.com>
> -----Message d'origine-----
> De : gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la part
> de Joel Brobecker
> Envoyé : dimanche 2 décembre 2012 17:07
> À : Alfred M. Szmidt
> Cc : Pierre Muller; gdb@sourceware.org
> Objet : Re: [ANNOUNCEMENT] GDB 7.5.1 released!
>
> > It should be available at ftp.gnu.org as /gnu/gnu-keyring.gpg.
>
> Indeed, I didn't know that. I verfied that my key is in that file.
> I have updated the download page of the GDB website to explain
> where to find the key necessary to verify release tarballs.
> See http://www.sourceware.org/gdb/download/
>
Thanks Joel,
This is the result I get:
$ gpg --verify --keyring gnu-keyring.gpg gdb-7.5.1.tar.bz2.sig
gpg: Signature made Thu Nov 29 11:34:12 2012 CET using DSA key ID FF325CF3
gpg: Good signature from "Joel Brobecker <brobecker@adacore.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the
owner.
Primary key fingerprint: F40A DB90 2B24 264A A42E 50BF 92ED B04B FF32 5CF3
Is the WARNING unavoidable?
Pierre Muller
next prev parent reply other threads:[~2012-12-02 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 13:18 Joel Brobecker
2012-12-01 0:16 ` Pierre Muller
2012-12-02 12:50 ` Joel Brobecker
2012-12-02 12:54 ` Hui Zhu
2012-12-02 14:32 ` Alfred M. Szmidt
2012-12-02 16:07 ` Joel Brobecker
2012-12-02 19:31 ` Pierre Muller [this message]
[not found] ` <50bbac9a.05fd440a.1f72.04a8SMTPIN_ADDED_BROKEN@mx.google.com>
2012-12-02 23:46 ` shawn wilson
2012-12-03 20:57 ` Maciej W. Rozycki
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='008c01cdd0c3$9c206020$d4612060$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox