discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug fix release to address broken nib loading...


From: Yavor Doganov
Subject: Re: Bug fix release to address broken nib loading...
Date: Sat, 08 Jun 2024 11:54:34 +0300
User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (Gojō) APEL-LB/10.8 EasyPG/1.0.0 Emacs/29.3 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

On Wed, 05 Jun 2024 03:26:09 +0300,
Gregory Casamento wrote:
> Let us do another release of GUI to address the recent issue with
> nib loading.

Thanks for making a new release; this kind of regression is certainly
important enough to warrant it.

I don't know what went wrong but it looks like the signature at
ftp.gnustep.org is bad:

$ gpg --verify --verbose gnustep-gui-0.31.1.tar.gz.sig 
gpg: enabled compatibility flags:
gpg: assuming signed data in 'gnustep-gui-0.31.1.tar.gz'
gpg: Signature made  6.06.2024 (чт) 12:39:51 EEST
gpg:                using DSA key 83AAE47CE829A4146EF83420CA868D4C99149679
gpg:                issuer "gnustep-maintainer@gnu.org"
gpg: using pgp trust model
gpg: BAD signature from "GNUstep Maintainer <gnustep-maintainer@gnu.org>" 
[unknown]
gpg: binary signature, digest algorithm SHA1, key algorithm dsa1024

For Debian it doesn't matter much because even a good signature is
rejected by current dpkg:

dpkg-source: info: verifying ./gnustep-base_1.30.0.orig.tar.gz.asc
gpgv: Signature made Wed May 29 19:34:34 2024 UTC
gpgv:                using DSA key 83AAE47CE829A4146EF83420CA868D4C99149679
gpgv:                issuer "gnustep-maintainer@gnu.org"
gpgv: Note: signatures using the SHA1 algorithm are rejected
gpgv: Can't check signature: Bad public key
dpkg-source: warning: cannot verify upstream tarball signature for 
./gnustep-base_1.30.0.orig.tar.gz: no acceptable signature found

I'm pretty sure I told Ivan about this some time ago.  (It's not a
problem that impedes our work but would be nice to fix in the near
future.)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]