NEWS Changes in release 2.31 (2024-09-15)
This release fixes a bug in handling the list of removed observations (local network adjustment). This bug did not influence command line tool gama-local, but was fatal for qgama interactive application. Thanks to everyone who has contributed! Ales Here is the GNU gama home page: https://gnu.org/s/gama/ For a summary of changes and contributors, see: https://git.sv.gnu.org/gitweb/?p=gama.git;a=shortlog;h=v2.31 or run this command from a git-cloned gama directory: git shortlog v2.30..v2.31 Here are the compressed sources and a GPG detached signature: https://ftp.gnu.org/gnu/gama/gama-2.31.tar.gz https://ftp.gnu.org/gnu/gama/gama-2.31.tar.gz.sig Use a mirror for higher download bandwidth: https://ftpmirror.gnu.org/gama/gama-2.31.tar.gz https://ftpmirror.gnu.org/gama/gama-2.31.tar.gz.sig Here are the SHA1 and SHA256 checksums: 04396b96f5687f90638558cb5b3143e096f150e8 gama-2.31.tar.gz z8dSMspcz6zwx7GUHZo+Jl3hS0qShaEs5DuvCIn7CCs= gama-2.31.tar.gz Verify the base64 SHA256 checksum with cksum -a sha256 --check from coreutils-9.2 or OpenBSD's cksum since 2007. 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 gama-2.31.tar.gz.sig The signature should match the fingerprint of the following key: pub rsa4096 2020-07-18 [SC] C6E1 824E 0180 B85F 31B0 6B6A CB6C E60D 1B77 FC09 uid Ales Cepek <ce...@gnu.org> If that command fails because you don't have the required public key, or that public key has expired, try the following commands to retrieve or refresh it, and then rerun the 'gpg --verify' command. gpg --recv-keys 1b77fc09 As a last resort to find the key, you can try the official GNU keyring: wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg gpg --keyring gnu-keyring.gpg --verify gama-2.31.tar.gz.sig