Hi,
I see. I just looked at my *pgp* keys and found the one below:
3EB2E2ECCB2F040A26CB7F2192B68B71531B6686
The key belongs to an old email account of myself that does not
exist anymore ([email protected]). In the meantime
I had changed the email provider. My *ftp* uploads to the gnu project
are scripted and the upload script (or, *pgp* for that matter) was not
aware of that change.
I use *pgp* very rarely (actually only for GNU uploads) and I have no
idea what I need to do to get rid of the key (and where else it is stored).
Having that said, I would like to point out that the *.tar.gz* files at
*gnu.org*
are, by definition, always out of date. If you use them then they produce
a GNU APL interpreter with existing bugs (at the time of the release) that
were fixed in the meantime. In the GNU APL 1.9 case, the release was in
June 2024 and therefore the tar.gz files on the GNU mirrors still have all
bugs that were fixed since June 2024.
The preferred way of fetching GNU APL is *subversion* (aka. *svn*) or, if
that is not possible) with *git*. See:
https://savannah.gnu.org/svn/?group=apl 🙂
<https://savannah.gnu.org/svn/?group=apl>
or, for masochists:
https://savannah.gnu.org/git/?group=apl 🙁
*SVN* is always up-to-date, and *git* is almost up-to-date in regard
to fixed errors.
Best Regards,
Jürgen Sauermann
*PS: *you should still be able to unpack the tar files if you want. *SVN*
and *git* fetch the files directly without packing and unpacking the files.
In the *ftp* era it was simple to transfer a single tar file, but these days
it is simpler to fetch the files directly with *SVN*.
If you have an idea how I can get rid of the *pgp* key then please let
me know.
On 11/16/25 00:58, [email protected] wrote:
could you please explain in which context that signing key occurs and for what
it is being used in
that context?
Of course. It's been a while since I've done such, so may I have not made some
basic error in this:
$ gpg --verify apl-1.9.tar.gz.sig
gpg: assuming signed data in 'apl-1.9.tar.gz'
gpg: Signature made Sat 29 Jun 2024 06:40:52 AM CDT
gpg: using RSA key 3EB2E2ECCB2F040A26CB7F2192B68B71531B6686
gpg: Can't check signature: No public key
$
