Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alex Kiernan <alex.kiernan@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bmap-tools: update from 3.4 to 3.5
Date: Fri, 15 Feb 2019 23:16:49 +0000	[thread overview]
Message-ID: <76d71f8af98a4ebe6154ff5b7ebb59ccf989408b.camel@linuxfoundation.org> (raw)
In-Reply-To: <1550178589-15839-1-git-send-email-alex.kiernan@gmail.com>

On Thu, 2019-02-14 at 21:09 +0000, Alex Kiernan wrote:
> bmap-tools 3.5 was released August 2018 but has no release tarball,
> so
> switch to using the git fetcher. Also pull in the fix for
> StopIteration
> being transformed into RuntimeError for Python 3.7.
> 
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>

Unfortunately this triggers a selftest failure:

https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/236

(ignore the virtgl piece, that is something else)

oe-selftest -r wic.Wic2.test_bmap_short
and
oe-selftest -r wic.Wic2.test_bmap_long 

should reproduce. Might be as simple as a missing RDEPENDS.

Cheers,

Richard

> 
>  .../bmap-tools/{bmap-tools_3.4.bb => bmap-tools_3.5.bb}          | 9
> +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
>  rename meta/recipes-support/bmap-tools/{bmap-tools_3.4.bb => bmap-
> tools_3.5.bb} (74%)
> 
> diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
> b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> similarity index 74%
> rename from meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
> rename to meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> index 2aae9a3fe0d8..25d66df623a0 100644
> --- a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb
> +++ b/meta/recipes-support/bmap-tools/bmap-tools_3.5.bb
> @@ -9,12 +9,13 @@ SECTION = "console/utils"
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM =
> "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
> -SRC_URI = "
> https://github.com/intel/${BPN}/releases/download/v${PV}/${BP}.tgz"
> +SRC_URI = "git://github.com/intel/${BPN}"
>  
> -SRC_URI[md5sum] = "883420183611aa137cbaf68a91ef0d7e"
> -SRC_URI[sha256sum] =
> "0064891270c180c190f41925b0f6fb9cecac3056f1168d2592dbe90e5f226c0a"
> +SRCREV = "db7087b883bf52cbff063ad17a41cc1cbb85104d"
> +S = "${WORKDIR}/git"
> +PV .= "+git${SRCPV}"
>  
> -UPSTREAM_CHECK_URI = "https://github.com/intel/${BPN}/releases"
> +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.*)"
>  
>  RDEPENDS_${PN} = "python3-core python3-compression python3-mmap
> python3-setuptools python3-fcntl"
>  
> -- 
> 2.7.4
> 



  parent reply	other threads:[~2019-02-15 23:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 21:09 [PATCH] bmap-tools: update from 3.4 to 3.5 Alex Kiernan
2019-02-14 21:17 ` Alexander Kanavin
2019-02-15 11:27   ` Richard Purdie
2019-02-15 12:15     ` Alexander Kanavin
2019-02-15 14:55     ` Alex Kiernan
2019-02-15 23:16 ` Richard Purdie [this message]
2019-02-16  9:25   ` Alex Kiernan
2019-02-16 11:31     ` Richard Purdie
2019-02-16 12:22       ` Alex Kiernan
2019-02-16 15:08         ` Richard Purdie

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=76d71f8af98a4ebe6154ff5b7ebb59ccf989408b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.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