All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: "Bajjuri, Praneeth" <praneeth@ti.com>
Cc: Changqing Li <changqing.li@windriver.com>,
	openembedded-devel@lists.openembedded.org,
	Denys Dmytriyenko <denis@denix.org>
Subject: Re: [meta-oe][dunfell PATCH] thin-provisioning-tools: switch branch from master to main
Date: Mon, 15 Mar 2021 08:48:04 -0700	[thread overview]
Message-ID: <0ad669ca-d9e5-bd46-74f3-13e01f7d6e37@gmail.com> (raw)
In-Reply-To: <938d2927-7eb0-c273-d4a2-6adacb09ecb8@ti.com>

I think yes, this should help dunfell if backported.

On 3/15/21 8:45 AM, Bajjuri, Praneeth wrote:
> 
> 
> On 3/14/2021 8:14 PM, praneeth@ti.com wrote:
>> From: Changqing Li <changqing.li@windriver.com>
> 
> Have observed build errors like the below
> 
> DEBUG: Mirror fetch failure for url 
> git://github.com/jthornber/thin-provisioning-tools;protocol=https 
> (original url: git://github.com/jthornber/thin-provisioning-tools)
> DEBUG: Fetcher failure: Unable to find revision 
> 5e5409f48b5403d2c6dffd9919b35ad77d6fb7b4 in branch master even from 
> upstream
> ERROR: Fetcher failure: Unable to find revision 
> 5e5409f48b5403d2c6dffd9919b35ad77d6fb7b4 in branch master even from 
> upstream
> ERROR: Fetcher failure for URL: 
> 'git://github.com/jthornber/thin-provisioning-tools'. Unable to fetch 
> URL from any source.
> 
> and looked like the switching branch to main was missing on dunfell branch.
> 
> Please advise if this is the right fix.
> 
> 
>>
>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> [cherry pick commit 260809cffdaad4fcd42b0977090f2c467a5474ef to dunfell]
>> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
>> ---
>>   .../thin-provisioning-tools/thin-provisioning-tools_0.8.5.bb    | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git 
>> a/meta-oe/recipes-support/thin-provisioning-tools/thin-provisioning-tools_0.8.5.bb 
>> b/meta-oe/recipes-support/thin-provisioning-tools/thin-provisioning-tools_0.8.5.bb 
>>
>> index 9f89bac22..3f82734ac 100644
>> --- 
>> a/meta-oe/recipes-support/thin-provisioning-tools/thin-provisioning-tools_0.8.5.bb 
>>
>> +++ 
>> b/meta-oe/recipes-support/thin-provisioning-tools/thin-provisioning-tools_0.8.5.bb 
>>
>> @@ -7,7 +7,7 @@ SECTION = "devel"
>>   LIC_FILES_CHKSUM = 
>> "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
>>   S = "${WORKDIR}/git"
>> -SRC_URI = "git://github.com/jthornber/thin-provisioning-tools \
>> +SRC_URI = 
>> "git://github.com/jthornber/thin-provisioning-tools;branch=main \
>>              file://0001-do-not-strip-pdata_tools-at-do_install.patch \
>>              file://use-sh-on-path.patch \
>>   "
>>

  reply	other threads:[~2021-03-15 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  1:14 [meta-oe][dunfell PATCH] thin-provisioning-tools: switch branch from master to main praneeth
2021-03-15 15:45 ` praneeth
2021-03-15 15:48   ` Khem Raj [this message]
2021-03-15 16:16     ` Denys Dmytriyenko
2021-03-16 15:41 ` [oe] " akuster
2021-03-16 16:37   ` Khem Raj
2021-03-16 17:12     ` Denys Dmytriyenko

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=0ad669ca-d9e5-bd46-74f3-13e01f7d6e37@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=changqing.li@windriver.com \
    --cc=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=praneeth@ti.com \
    /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.