GNU bug report logs - #54559
libtool-2.4.7 released [stable]

Previous Next

Full log

Message #14 received at 54559 <at> debbugs.gnu.org (full text, mbox):

From: Nick Bowler <nbowler <at> draconx.ca>
To: Alex Ameen <alex.ameen.tx <at> gmail.com>
Cc: info-gnu <at> gnu.org, autotools-announce <at> gnu.org, 54559 <at> debbugs.gnu.org
Subject: Re: bug#54559: libtool-2.4.7 released [stable]
Date: Fri, 25 Mar 2022 22:01:00 -0400

On 2022-03-25, Alex Ameen <alex.ameen.tx <at> gmail.com> wrote:
> Howdy, Libtoolers!
>
> After a long hiatus, the Libtool Team is pleased to announce the release of
> libtool 2.4.7.

Congratulations on the release!

> [*] Use a .sig file to verify that the corresponding file (without the
> .sig suffix) is intact.  First, be sure to download both the .sig file
> and the corresponding tarball.  Then, run a command like this:
>
>    gpg --verify libtool-2.4.7.tar.gz.sig
>
> If that command fails because you don't have the required public key,
> then run this command to import it:
>
>    gpg --keyserver keys.gnupg.net --recv-keys 6EAC957F8EEB55C0
>
> and rerun the 'gpg --verify' command.

I believe these instructions need to be updated.  It does not seem to be
possible to retrieve the public key by this method.  My understanding is
that the keys.gunupg.net service has been totally dead for the better
part of a year now.

  % gpg --keyserver keys.gnupg.net --recv-keys 6EAC957F8EEB55C0
  gpg: keyserver receive failed: No data

Cheers,
  Nick

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.