From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] netbase: use git fetcher
Date: Fri, 19 Jun 2020 15:57:51 +0800 [thread overview]
Message-ID: <3089b5fa-4998-7a83-52c8-d6a535c60c14@windriver.com> (raw)
In-Reply-To: <16189495E5DBCB85.29686@lists.openembedded.org>
Ping.
Thanks,
On 6/15/20 9:49 AM, Yu, Mingli wrote:
> Hi RP,
>
> On 4/1/20 5:20 PM, Richard Purdie wrote:
>> On Mon, 2020-03-16 at 17:24 +0800, mingli.yu@windriver.com wrote:
>>> From: Mingli Yu <mingli.yu@windriver.com>
>>>
>>> Use git repo as the the previous URL only stores
>>> the latest source file and fails to locate the
>>> source tar file if we don't upgrade timely.
>>>
>>> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
>>> ---
>>> meta/recipes-core/netbase/netbase_6.1.bb | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> Breaks reproducible builds:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/825
>
> I run reproducible build locally with "oe-selftest -r
> reproducible.ReproducibleTests.test_reproducible_builds" and It succeeds
> with this commit.
>
> BTW, the netbase only introduces 3 files as below:
> # rpm -ql netbase
>
> /etc
>
> /etc/protocols
>
> /etc/rpc
>
> /etc/services
>
> And I did the three files' checksum and the checksum turns out to be the
> same when with the commit and without the commit.
>
> Thanks,
> Grace
>
>>
>> Cheers,
>>
>> Richard
>>
>>
>
>
>
prev parent reply other threads:[~2020-06-19 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 9:24 [PATCH] netbase: use git fetcher mingli.yu
2020-03-31 8:09 ` [OE-core] " Yu, Mingli
2020-04-01 9:20 ` Richard Purdie
2020-04-02 1:04 ` Yu, Mingli
2020-04-02 2:37 ` Yu, Mingli
2020-04-02 3:01 ` Anuj Mittal
2020-06-15 1:49 ` Yu, Mingli
[not found] ` <16189495E5DBCB85.29686@lists.openembedded.org>
2020-06-19 7:57 ` Yu, Mingli [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=3089b5fa-4998-7a83-52c8-d6a535c60c14@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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