From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 01/14] blktool: upgrade 4-7 -> 4-7.1
Date: Fri, 22 Feb 2019 17:14:23 +0200 [thread overview]
Message-ID: <20190222151423.GA24699@localhost> (raw)
In-Reply-To: <20190221124130.25733-1-richard.purdie@linuxfoundation.org>
On Thu, Feb 21, 2019 at 12:41:17PM +0000, Richard Purdie wrote:
> Signed-off-by: Richard Purdie <richard.purdie@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
prev parent reply other threads:[~2019-02-22 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 12:41 [PATCH 01/14] blktool: upgrade 4-7 -> 4-7.1 Richard Purdie
2019-02-21 12:41 ` [PATCH 02/14] curl: upgrade 7.63.0 -> 7.64.0 Richard Purdie
2019-02-21 12:41 ` [PATCH 03/14] gnupg: upgrade 2.2.12 -> 2.2.13 Richard Purdie
2019-02-21 12:41 ` [PATCH 04/14] gst-examples: upgrade to latest revision Richard Purdie
2019-02-21 12:41 ` [PATCH 05/14] less: upgrade 530 -> 549 Richard Purdie
2019-02-21 12:41 ` [PATCH 06/14] libassuan: upgrade 2.5.2 -> 2.5.3 Richard Purdie
2019-02-21 12:41 ` [PATCH 07/14] libxau: upgrade 1.0.8 -> 1.0.9 Richard Purdie
2019-02-21 12:41 ` [PATCH 08/14] netbase: upgrade 5.5 -> 5.6 Richard Purdie
2019-02-21 12:41 ` [PATCH 09/14] pkgconf: upgrade 1.5.3 -> 1.6.0 Richard Purdie
2019-02-21 12:41 ` [PATCH 10/14] readline: upgrade 7.0 -> 8.0 Richard Purdie
2019-02-21 12:41 ` [PATCH 11/14] sbc: upgrade 1.3 -> 1.4 Richard Purdie
2019-02-21 12:41 ` [PATCH 12/14] xf86-input-libinput: upgrade 0.28.1 -> 0.28.2 Richard Purdie
2019-02-21 12:41 ` [PATCH 13/14] xkeyboard-config: upgrade 2.25 -> 2.26 Richard Purdie
2019-02-21 12:41 ` [PATCH 14/14] gnu-config: upgrade to 20181128 revision Richard Purdie
2019-02-22 15:14 ` Adrian Bunk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190222151423.GA24699@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox