From: Gyorgy Sarvari <skandigraun@gmail.com>
To: raj.khem@gmail.com, d.schultz@phytec.de
Cc: openembedded-devel@lists.openembedded.org, upstream@lists.phytec.de
Subject: Re: [oe] [meta-networking][PATCH] meta-networking: mbedtls: Remove tag from SRC_URI
Date: Fri, 15 Aug 2025 07:53:43 +0200 [thread overview]
Message-ID: <63158bab-8681-4e23-af58-418e2874ea78@gmail.com> (raw)
In-Reply-To: <CAMKF1sqM_bVMcSJ+929XJ8DK_4_NDhDN75KtnTtF=Rz+bRkFgQ@mail.gmail.com>
On 8/15/25 04:06, Khem Raj via lists.openembedded.org wrote:
> I wonder why it works on autobuilder. Can you try with bitbake -ccleanall ?
> and see if fetching works. I can see the SRCREV is same as v3.6.4 tag.
Was this patch meant for scarthgap, where mbedtls got just broken due to
this rev vs tag issue?
> On Thu, Aug 14, 2025 at 3:51 PM Daniel Schultz via
> lists.openembedded.org <d.schultz=phytec.de@lists.openembedded.org>
> wrote:
>> This recipe uses SRCREV as well as defines a tag in the SRC_URI.
>> Only use SRCREV since this will generate an error.
>>
>> Fix following error:
>> [...] FetchError: Fetcher failure: Conflicting revisions
>> (c765c831e5c2a0971410692f92f7a81d6ec65ec2 from SRCREV and v3.6.4
>> from the url) found, please specify one valid value
>>
>> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
>> ---
>> meta-networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta-networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb b/meta-networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb
>> index 88b50a406b..a0dc6a689a 100644
>> --- a/meta-networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb
>> +++ b/meta-networking/recipes-connectivity/mbedtls/mbedtls_3.6.4.bb
>> @@ -23,7 +23,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=379d5819937a6c2f1ef1630d341e026d"
>> SECTION = "libs"
>>
>> S = "${WORKDIR}/git"
>> -SRC_URI = "gitsm://github.com/Mbed-TLS/mbedtls.git;protocol=https;branch=mbedtls-3.6;tag=v${PV} \
>> +SRC_URI = "gitsm://github.com/Mbed-TLS/mbedtls.git;protocol=https;branch=mbedtls-3.6 \
>> file://run-ptest \
>> "
>>
>> --
>> 2.25.1
>>
>>
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#118953): https://lists.openembedded.org/g/openembedded-devel/message/118953
>> Mute This Topic: https://lists.openembedded.org/mt/114709547/6084445
>> Group Owner: openembedded-devel+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [skandigraun@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
next prev parent reply other threads:[~2025-08-15 5:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 22:50 [meta-networking][PATCH] meta-networking: mbedtls: Remove tag from SRC_URI Daniel Schultz
2025-08-15 2:06 ` [oe] " Khem Raj
2025-08-15 5:50 ` Marko, Peter
2025-08-15 22:55 ` Daniel Schultz
2025-08-15 5:53 ` Gyorgy Sarvari [this message]
2025-08-15 9:08 ` Alexander Kanavin
2025-08-15 9:24 ` Gyorgy Sarvari
2025-08-15 22:55 ` Daniel Schultz
2025-08-18 7:40 ` Andrey Zhizhikin
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=63158bab-8681-4e23-af58-418e2874ea78@gmail.com \
--to=skandigraun@gmail.com \
--cc=d.schultz@phytec.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=upstream@lists.phytec.de \
/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.