[PATCH] bmap-tools: update to latest git master

[PATCH] bmap-tools: update to latest git master

[Diego]

Update to latest revision of git master to include, among other
improvements, support for zstd compression format.

Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
---
 meta/recipes-support/bmap-tools/bmap-tools_3.5.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
index 7c4db85b32..694c5f09be 100644
--- a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
+++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 SRC_URI = "git://github.com/intel/${BPN}"
 
-SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
+SRCREV = "a17f0e3ff8669dd3b1c44a741ae4f8162155faed"
 S = "${WORKDIR}/git"
 PV .= "+git${SRCPV}"
 
-- 
2.21.3

Re: [OE-core] [PATCH] bmap-tools: update to latest git master

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

You can't generally update to a random development commit, especially if PV
stays the same. Please ask upstream to make a new release.

Alex

On Thu, 14 May 2020 at 16:22, Diego <diego.rondini@kynetics.com> wrote:

> Update to latest revision of git master to include, among other
> improvements, support for zstd compression format.
>
> Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
> ---
>  meta/recipes-support/bmap-tools/bmap-tools_3.5.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> index 7c4db85b32..694c5f09be 100644
> --- a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> +++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM =
> "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
>  SRC_URI = "git://github.com/intel/${BPN}
> <http://github.com/intel/$%7BBPN%7D>"
>
> -SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
> +SRCREV = "a17f0e3ff8669dd3b1c44a741ae4f8162155faed"
>  S = "${WORKDIR}/git"
>  PV .= "+git${SRCPV}"
>
> --
> 2.21.3
>
> 
>

[-- Attachment #2: Type: text/html, Size: 2093 bytes --]

Re: [OE-core] [PATCH] bmap-tools: update to latest git master

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

Another option is to backport the needed patch.

Alex

On Thu, 14 May 2020 at 19:31, Alexander Kanavin via lists.openembedded.org
<alex.kanavin=gmail.com@lists.openembedded.org> wrote:

> You can't generally update to a random development commit, especially if
> PV stays the same. Please ask upstream to make a new release.
>
> Alex
>
> On Thu, 14 May 2020 at 16:22, Diego <diego.rondini@kynetics.com> wrote:
>
>> Update to latest revision of git master to include, among other
>> improvements, support for zstd compression format.
>>
>> Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
>> ---
>>  meta/recipes-support/bmap-tools/bmap-tools_3.5.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> index 7c4db85b32..694c5f09be 100644
>> --- a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> +++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM =
>> "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>>
>>  SRC_URI = "git://github.com/intel/${BPN}
>> <http://github.com/intel/$%7BBPN%7D>"
>>
>> -SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
>> +SRCREV = "a17f0e3ff8669dd3b1c44a741ae4f8162155faed"
>>  S = "${WORKDIR}/git"
>>  PV .= "+git${SRCPV}"
>>
>> --
>> 2.21.3
>>
>>
>> 
>

[-- Attachment #2: Type: text/html, Size: 2676 bytes --]

Re: [OE-core] [PATCH] bmap-tools: update to latest git master

[Diego]

[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]

Hi Alexander,

On Thu, May 14, 2020 at 7:31 PM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> You can't generally update to a random development commit, especially if
> PV stays the same. Please ask upstream to make a new release.
>
>
Thank you for your feedback, I understand your point.
The odd thing is that the situation is already broken, as what's in oe-core
master right now is not bmap-tools release 3.5, but some "random
development commit" in between 3.5 and current master:
http://git.openembedded.org/openembedded-core/commit/meta/recipes-support/bmap-tools?id=3fbee26af2f3263180f75652b5dd6e50adb1d8fe

https://github.com/intel/bmap-tools/commits/master
Release 3.5:
https://github.com/intel/bmap-tools/commit/14b411a65c371e273fe599bee9e52bd9f9b751e1
Commit in oe-core:
https://github.com/intel/bmap-tools/commit/db7087b883bf52cbff063ad17a41cc1cbb85104d

What do you suggest?

Thanks
Diego Rondini


> Alex
>
> On Thu, 14 May 2020 at 16:22, Diego <diego.rondini@kynetics.com> wrote:
>
>> Update to latest revision of git master to include, among other
>> improvements, support for zstd compression format.
>>
>> Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
>> ---
>>  meta/recipes-support/bmap-tools/bmap-tools_3.5.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> index 7c4db85b32..694c5f09be 100644
>> --- a/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> +++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
>> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM =
>> "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>>
>>  SRC_URI = "git://github.com/intel/${BPN}
>> <http://github.com/intel/$%7BBPN%7D>"
>>
>> -SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
>> +SRCREV = "a17f0e3ff8669dd3b1c44a741ae4f8162155faed"
>>  S = "${WORKDIR}/git"
>>  PV .= "+git${SRCPV}"
>>
>> --
>> 2.21.3
>>
>> 
>>
>

[-- Attachment #2: Type: text/html, Size: 3970 bytes --]

Re: [OE-core] [PATCH] bmap-tools: update to latest git master

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

On Thu, 14 May 2020 at 22:59, Diego Rondini <diego.rondini@kynetics.com>
wrote:

> Hi Alexander,
>
> On Thu, May 14, 2020 at 7:31 PM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
>> You can't generally update to a random development commit, especially if
>> PV stays the same. Please ask upstream to make a new release.
>>
>>
> Thank you for your feedback, I understand your point.
> The odd thing is that the situation is already broken, as what's in
> oe-core master right now is not bmap-tools release 3.5, but some "random
> development commit" in between 3.5 and current master:
>
> http://git.openembedded.org/openembedded-core/commit/meta/recipes-support/bmap-tools?id=3fbee26af2f3263180f75652b5dd6e50adb1d8fe
>
> https://github.com/intel/bmap-tools/commits/master
> Release 3.5:
>
> https://github.com/intel/bmap-tools/commit/14b411a65c371e273fe599bee9e52bd9f9b751e1
> Commit in oe-core:
>
> https://github.com/intel/bmap-tools/commit/db7087b883bf52cbff063ad17a41cc1cbb85104d
>
> What do you suggest?
>

Right - generally we need to trust that version updates don't do this, and
there's no easy way to detect this. The recipe already does:
PV .= "+git${SRCPV}"
which is the standard way to mark "random development commits", so I'd say
resubmit your patch with an explanation in the commit log
that you're merely bumping one development snapshot to a newer development
snapshot.

[-- Attachment #2: Type: text/html, Size: 2697 bytes --]