public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Julien STEPHAN <jstephan@baylibre.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] vulkan-samples: enable network during do_unpack
Date: Wed, 17 Aug 2022 21:20:01 +0200	[thread overview]
Message-ID: <Yv0/YY0usjwo1LMZ@mail.local> (raw)
In-Reply-To: <20220817190124.2126652-1-jstephan@baylibre.com>

On 17/08/2022 21:01:24+0200, Julien STEPHAN wrote:
> vulkan-samples uses git submodules and one of the submodules uses lfs
> objects. During the unpack step, the lfs objects are retrieved leading to
> a network failure.
> 
> The correct fix is to fetch lfs objects during the fetch step, but let's
> workaround this issue for now
> 

How can you ensure you are not relying on third parties to sotre the
code you need to build your images then?

> Signed-off-by: Julien STEPHAN <jstephan@baylibre.com>
> ---
>  meta/recipes-graphics/vulkan/vulkan-samples_git.bb | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
> index 41cb4a437d..b45ee22a69 100644
> --- a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
> +++ b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb
> @@ -11,6 +11,11 @@ SRC_URI = "gitsm://github.com/KhronosGroup/Vulkan-Samples.git;branch=master;prot
>             file://0001-framework-core-hpp_vulkan_resource.h-add-header-incl.patch \
>             "
>  
> +# Workaround for network access issue during the do_unpack step
> +# this needs to be fixed in the recipes buildsystem to move
> +# this such that it can be accomplished during do_fetch task
> +do_unpack[network] = "1"
> +
>  UPSTREAM_CHECK_COMMITS = "1"
>  SRCREV = "ee6c1522af8ba9b56f8416c2eedafb440f681085"
>  
> -- 
> 2.37.1
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#169500): https://lists.openembedded.org/g/openembedded-core/message/169500
> Mute This Topic: https://lists.openembedded.org/mt/93089137/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      parent reply	other threads:[~2022-08-17 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 19:01 [PATCH] vulkan-samples: enable network during do_unpack Julien STEPHAN
2022-08-17 19:09 ` [OE-core] " Alexander Kanavin
2022-08-17 19:22   ` Julien Stephan
2022-08-17 19:42     ` Alexander Kanavin
     [not found]     ` <170C3947C33061FA.1805@lists.openembedded.org>
2022-08-17 20:33       ` Alexander Kanavin
2022-08-18  7:02         ` Julien Stephan
2022-08-18 19:45           ` Martin Jansa
2022-08-18 20:00             ` Alexander Kanavin
2022-10-17 12:25               ` Martin Jansa
2022-08-17 19:20 ` Alexandre Belloni [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=Yv0/YY0usjwo1LMZ@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=jstephan@baylibre.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