> On Sep 17, 2014, at 5:17 AM, [email protected] wrote:
> 
> Revision
> 125415
> Author
> [email protected]
> Date
> 2014-09-17 03:17:24 -0700 (Wed, 17 Sep 2014)
> Log Message
> 
> sysutils/rcm
>   move upstream to github
> 


> --- trunk/dports/sysutils/rcm/Portfile        2014-09-17 10:00:44 UTC (rev 
> 125414)
> +++ trunk/dports/sysutils/rcm/Portfile        2014-09-17 10:17:24 UTC (rev 
> 125415)
> @@ -2,9 +2,9 @@
>  # $Id$
>  
>  PortSystem          1.0
> +PortGroup           github 1.0
>  
> -name                rcm
> -version             1.2.3
> +github.setup        thoughtbot rcm 1.2.3 v
>  maintainers         g5pw openmaintainer
>  categories          sysutils
>  description         rc file (dotfile) management
> @@ -16,8 +16,6 @@
>  license             BSD
>  homepage            https://thoughtbot.github.io/rcm/ 
> -master_sites        ${homepage}dist/
> -
>  checksums           rmd160  7e41b370fa2bd6308a632175c4d5469a3bbcc10b \
>                      sha256  
> 502fd44e567ed0cfd00fb89ccc257dac8d6eb5d003f121299b5294c01665973f

Checksum mismatch, unsurprisingly:


$ port checksum rcm
--->  Fetching distfiles for rcm
--->  Attempting to fetch rcm-1.2.3.tar.gz from 
https://github.com/thoughtbot/rcm/tarball/v1.2.3
--->  Verifying checksums for rcm                                               
             
Error: Checksum (rmd160) mismatch for rcm-1.2.3.tar.gz
Error: Checksum (sha256) mismatch for rcm-1.2.3.tar.gz
Error: Failed to checksum rcm: Unable to verify file checksums
Error: See 
/opt/local/var/macports/logs/_Users_rschmidt_macports_dports_sysutils_rcm/rcm/main.log
 for details.
Error: Follow http://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port rcm failed


It would be unlikely for a project to have hosted on their own web site a 
tarball that was identical to the automatically-generated tarball provided by 
github.

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to