[OE-core] [PATCH 01/14] blktool: upgrade 4-7 -> 4-7.1

[Adrian Bunk]

On Thu, Feb 21, 2019 at 12:41:17PM +0000, Richard Purdie wrote:
> Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> ---
>  .../blktool/{blktool_4-7.bb => blktool_4-7.1.bb}                | 2 ++
>  1 file changed, 2 insertions(+)
>  rename meta/recipes-extended/blktool/{blktool_4-7.bb => blktool_4-7.1.bb} (90%)
> 
> diff --git a/meta/recipes-extended/blktool/blktool_4-7.bb b/meta/recipes-extended/blktool/blktool_4-7.1.bb
> similarity index 90%
> rename from meta/recipes-extended/blktool/blktool_4-7.bb
> rename to meta/recipes-extended/blktool/blktool_4-7.1.bb
> index 0e6f7ee6df1..468925e329b 100644
> --- a/meta/recipes-extended/blktool/blktool_4-7.bb
> +++ b/meta/recipes-extended/blktool/blktool_4-7.1.bb
> @@ -9,6 +9,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>  
>  DEPENDS = "glib-2.0"
>  
> +SRC_URI[sha256sum] = "b1e6d5912546d2a4b704ec65c2b9664aa3b4663e7d800e06803330335a2cb764"
> +SRC_URI[md5sum] = "62edc09c9908107e69391c87f4f3fd40"

Adding hashes insted of updating them looks wrong.

>  SRC_URI = "http://snapshot.debian.org/archive/debian/20160728T043443Z/pool/main/b/${BPN}/${BPN}_4.orig.tar.gz;name=tarball \
>...

And the recipe seems to build the stale upstream version 4,
not the Debian-patched package.

In a related note, an actual upgrade 4-7 -> 4-7.1 would have failed 
since the new patch in 4-7.1 is already applied in yocto.

# for this package we're mostly interested in tracking debian patches,
# and not in the upstream version where all development has effectively stopped

This seems to imply that every new "upstream" version requires manual 
checking of the Debian changes, and an automatic upgrade does nothing.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed