All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: alex.kanavin@gmail.com
Cc: "Marko, Peter" <Peter.Marko@siemens.com>,
	"Lau, Karn Jye" <karn.jye.lau@intel.com>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-networking][scarthgap][PATCH] mbedtls: fix git fetcher conflict by using SRC_URI.
Date: Fri, 15 Aug 2025 12:53:29 +0300	[thread overview]
Message-ID: <aJ8Dmd5RBIT1vKgs@nuoska> (raw)
In-Reply-To: <CANNYZj-kk=gwG0G2tbzW1V4ZzZy2CV5NfRRgHXzcbSkoi5hWVA@mail.gmail.com>

Hi,

On Fri, Aug 15, 2025 at 11:39:25AM +0200, Alexander Kanavin via lists.openembedded.org wrote:
> On Fri, 15 Aug 2025 at 11:36, Marko, Peter <Peter.Marko@siemens.com> wrote:
> > This was moved from scathgap-next to scarthgap yesterday, so timing is clear
> > https://lists.openembedded.org/g/openembedded-devel/message/118942
> >
> > The successful autobuilder runs are a mystery.
> > Maybe the code throws only if the sources are not in downloads (e.g. autobuilder has these from master).
> 
> The more worrying scenario is that there was no actual build at any
> point before this landed, I hope that is not the case.
> 
> I don't object to the fixes, just want to find out where the quality
> gating process failed.

FWIW, most users of mbedtls in the Arm firmware land embed the git repo or sources
directly and don't use this recipe. This is problematic for SBOM, CVE security
handling etc but this how things are currently. Users are u-boot, trusted-firmware-a,
trusted-firmware-m, OP-TEE etc. Thus this recipe may have very few users even when
mbedtls is used in a lot of places.

Cheers,

-Mikko


  reply	other threads:[~2025-08-15  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  4:11 [meta-networking][scarthgap][PATCH] mbedtls: fix git fetcher conflict by using SRC_URI karn.jye.lau
2025-08-15  5:52 ` [oe] " Marko, Peter
2025-08-15  6:09   ` Lau, Karn Jye
2025-08-15  6:12     ` Marko, Peter
2025-08-15  8:09       ` Marko, Peter
2025-08-15  9:08         ` Alexander Kanavin
2025-08-15  9:21           ` Lau, Karn Jye
2025-08-15  9:29             ` Alexander Kanavin
2025-08-15  9:34               ` Gyorgy Sarvari
2025-08-15  9:36               ` Marko, Peter
2025-08-15  9:39                 ` Alexander Kanavin
2025-08-15  9:53                   ` Mikko Rapeli [this message]
2025-08-15 11:05                     ` Lau, Karn Jye
2025-08-15 10:28         ` [meta-networking][scarthgap][PATCH v2] [meta-networking][scarthgap][PATCH v2] mbedtls: drop tag parameter from SRC_URI karn.jye.lau
2025-08-15 10:38 ` karn.jye.lau
2025-08-15 10:49 ` karn.jye.lau

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=aJ8Dmd5RBIT1vKgs@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=Peter.Marko@siemens.com \
    --cc=alex.kanavin@gmail.com \
    --cc=karn.jye.lau@intel.com \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.