Re-sign automake116 packages for compatibility with CentOS 9

[andrey-utkin]

In an effort to add CI testing of RNP on CentOS 9 I have hit an issue that CentOS 9's package manager refuses to read the ribose-automake116* packages:

 + sudo dnf -y -q install clang gcc gcc-c++ make autoconf automake libtool bzip2 gzip bison byacc bzip2-devel gettext-devel ncurses-devel python3 ribose-automake116 ruby-devel zlib-devel cmake texinfo
warning: Signature not supported. Hash algorithm SHA1 not available.
warning: Signature not supported. Hash algorithm SHA1 not available.
warning: Signature not supported. Hash algorithm SHA1 not available.
warning: Signature not supported. Hash algorithm SHA1 not available.
warning: Signature not supported. Hash algorithm SHA1 not available.
warning: Signature not supported. Hash algorithm SHA1 not available.
Problem opening package ribose-automake116-1.1-1.el7.x86_64.rpm
Problem opening package ribose-automake116-automake-1.16.1-1.el7.noarch.rpm
Problem opening package ribose-automake116-runtime-1.1-1.el7.x86_64.rpm
Error: GPG check FAILED

There is a discussion of the same issue happening on another project which also publishes their own RPM packages: k3s-io/k3s#5588 . They have pinpointed it that the packages are rejected because they are signed with SHA1 which has been deprecated. There is a patch which was confirmed to fix it: https://github.com/k3s-io/k3s-selinux/pull/32/files . As I understand the signer could alternatively disable SHA1 signing in gnupg's config.

[ribose-jeffreylau]

Related: https://www.starlab.io/blog/adding-sha256-digests-to-rpms

[ribose-jeffreylau]

@andrey-utkin The automake rpms have been re-signed correctly, hopefully!