guile checksum seems off

[mwette]

It seems guile has been upgrade to newly released 2.2.0, but I'm convinced the checksums are off. The portfile lists no maintainer, so here I am.

Macports reports:

root# port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.4.1 installed,
MacPorts base version 2.4.1 downloaded.
--->  Updating the ports tree
root# port clean --all guile
--->  Cleaning guile
root# port upgrade guile
--->  Computing dependencies for guile
--->  Fetching distfiles for guile
--->  Attempting to fetch guile-2.2.0.tar.gz from https://distfiles.macports.org/guile
--->  Attempting to fetch guile-2.2.0.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/guile
--->  Attempting to fetch guile-2.2.0.tar.gz from http://mirror.cc.columbia.edu/pub/software/gnu/guile
--->  Attempting to fetch guile-2.2.0.tar.gz from http://mirrors.ibiblio.org/gnu/ftp/gnu/guile
--->  Verifying checksums for guile                                             
Error: Checksum (rmd160) mismatch for guile-2.2.0.tar.gz
Error: Checksum (sha256) mismatch for guile-2.2.0.tar.gz
Error: Failed to checksum guile: Unable to verify file checksums
Error: See /opt/local/var/macports/logs/_Users_mwette_proj_macports_ports_lang_guile22/guile/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

If I "port edit guile" I find:

checksums           rmd160  ae8d90f55e4c82d60e4ba7e5c161a5a1e4a4e7c5 \
                    sha256  ee8073c4582bb4f06412452fdf5dd185aae607441f1313c824f4}}}

If I compute dist I have from gnu.org I find

mwette$ shasum -a 256 guile-2.2.0.tar.gz 
ef1e9544631f18029b113911350bffd5064955c208a975bfe0d27a4003d6d86b  guile-2.2.0.tar.gz

[ryandesign (Ryan Carsten Schmidt)]

guile has not been updated to 2.2.0. It is at version 2.0.14. See:

​https://github.com/macports/macports-ports/commits/master/lang/guile

Your guile 2.2.0 portfile seems to be one you created yourself, in the directory /Users/mwette/proj/macports/ports/lang/guile22.

If you would like the official port to be updated to 2.2.0, you could file a ticket for that.