Hi Kurt,

On Jun 18, 2014, at 11:27 AM, khindenb...@macports.org wrote:

> Revision
> 121140
> Author
> khindenb...@macports.org
> Date
> 2014-06-18 10:27:18 -0700 (Wed, 18 Jun 2014)
> Log Message
> 
> duplicity: update to 0.6.24 - closes #42473
> Modified Paths
> 
> trunk/dports/sysutils/duplicity/Portfile
> Diff
> 
> Modified: trunk/dports/sysutils/duplicity/Portfile (121139 => 121140)
> 
> --- trunk/dports/sysutils/duplicity/Portfile  2014-06-18 17:01:35 UTC (rev 
> 121139)
> +++ trunk/dports/sysutils/duplicity/Portfile  2014-06-18 17:27:18 UTC (rev 
> 121140)
> @@ -6,7 +6,7 @@
>  
>  name                duplicity
>  categories          sysutils
> -version             0.6.22
> +version             0.6.24
>  set stable_series   [join [lrange [split ${version} .] 0 1] .]-series
>  platforms           darwin
>  license             GPL-2
> @@ -26,8 +26,8 @@
>  homepage            http://duplicity.nongnu.org/
>  master_sites        
> https://launchpad.net/duplicity/${stable_series}/${version}/+download
>  
> -checksums           rmd160  b34bc75120a3a744383153d51a179042f82b216b \
> -                    sha256  
> 6f489b0445681f0697488f3d4097b4c56a7fe8a5fea5fadd2e431724039c5a12
> +checksums           sha1 1d0bab80cb9465080179307d969e292c7145c714 \
> +                    rmd160 ff6c6dc84d609a390e7bb3d018a4f31030c8b826
You replaced the sha256 checksum with the obsolete sha1. Please restore the 
(updated) sha256 checksum as that and rmd160 are the preferred checksums 
because they are more secure. See the guide entry about this [1]. If upstream 
provides sha1, then it is fine to also keep it, otherwise it should be removed. 

[1] <https://guide.macports.org/index.html#reference.phases.checksum>

>  
>  python.default_version 27
>  
> @@ -42,6 +42,7 @@
>  
>  depends_run-append  port:py${python.version}-boto \
>                      port:py${python.version}-paramiko \
> +                    port:py${python.version}-lockfile \
>                      port:ncftp
>  
>  depends_lib-append  port:librsync \
> _______________________________________________
> macports-changes mailing list
> macports-chan...@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-changes

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to