On Thu, Jul 30, 2015 at 04:31:30PM +0300, Alexander Kanavin wrote:
> Google Code is shutting down soon, so libproxy tarball is now fetched
> from Debian mirrors
> 
> Signed-off-by: Alexander Kanavin <alexander.kana...@linux.intel.com>
> ---
>  meta/recipes-support/libproxy/libproxy_0.4.11.bb | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/meta/recipes-support/libproxy/libproxy_0.4.11.bb 
> b/meta/recipes-support/libproxy/libproxy_0.4.11.bb
> index 9d388d6..06d0b9b 100644
> --- a/meta/recipes-support/libproxy/libproxy_0.4.11.bb
> +++ b/meta/recipes-support/libproxy/libproxy_0.4.11.bb
> @@ -8,12 +8,11 @@ LIC_FILES_CHKSUM = 
> "file://COPYING;md5=4fbd65380cdd255951079008b364516c \
>  
>  DEPENDS = "gconf glib-2.0"
>  
> -SRC_URI = "http://libproxy.googlecode.com/files/libproxy-${PV}.zip \
> +SRC_URI = "${DEBIAN_MIRROR}/main/libp/${BPN}/${BPN}_${PV}.orig.tar.gz \
>             file://0001-test-Include-sys-select.h-for-select.patch \
>            "
> -
> -SRC_URI[md5sum] = "06be230b8b612e64997f8f15af6373aa"
> -SRC_URI[sha256sum] = 
> "3175abcb49c0b37fd82c697927783bf7d53de3884a8559bc594e59caa09bdb04"
> +SRC_URI[md5sum] = "3cd1ae2a4abecf44b3f24d6639d2cd84"
> +SRC_URI[sha256sum] = 
> "dc3f33de54163718f82b3e7c496a7de97f8862578414b8ecaad3cbfe4821864b"

Why has debian mirror different checksums?

Include the diff in commit message and warn premirror maintainers that
they need to drop old file (otherwise it will fail) - which is very
annoying.

>  
>  inherit cmake pkgconfig
>  
> -- 
> 2.1.4
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: martin.ja...@gmail.com

Attachment: signature.asc
Description: Digital signature

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to