All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yash Shinde <Yash.Shinde@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com,
	richard.purdie@linuxfoundation.org
Subject: Re: [OE-core] [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0
Date: Mon, 31 Mar 2025 11:21:52 +0530	[thread overview]
Message-ID: <1a1ab4d3-1972-4954-a14f-2f974d0bb04b@windriver.com> (raw)
In-Reply-To: <CANNYZj97RCxTQDccGFATZfGwf9P0u9OkysWR1OVLJyLxeR4bgA@mail.gmail.com>


On 29-03-2025 00:09, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Fri, 28 Mar 2025 at 15:40, Richard Purdie via
> lists.openembedded.org
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
>> On Fri, 2025-03-28 at 07:30 -0700, Yash Shinde via
>> lists.openembedded.org wrote:
>>> From: Yash Shinde <Yash.Shinde@windriver.com>
>>>
>>> Rust stable version updated to 1.85.0
>>> https://blog.rust-lang.org/2025/02/20/Rust-1.85.0.html
>>>
>>> Some of the major updates:
>>>
>>> - Update LIC_FILES_CHKSUM in libstd-rs and rust recipes.
>> How did the license file change? Was the overall recipe LICENSE
>> affected?
>>
>> You need to be clear about what changed and if LICENSE is impacted.
> Also the checksum update for libstd-rs is done in this commit, but for
> rust it's done in 1.85.0->1.85.1 commit, which is incorrect.
>
> The history of changes is here:
> https://github.com/rust-lang/rust/commits/master/COPYRIGHT
>
> The latest change isn't in 1.85, but the unicode sync is - please
> confirm by comparing what's in the 1.84 vs 1.85 tarballs.
>
> Use
>
> License-Update: <describe what changed>
>
> in the commit message.
There was an update in Unicode license from "Unicode-DFS-2016" to 
"Unicode-3.0".
https://github.com/rust-lang/rust/commit/6d2a3e9786ec43a0e0af20386e7046328296ac86

I will update both the checksums in the commit for 1.85.0 update in v2.

Regards,
Yash
>
> Alex


  reply	other threads:[~2025-03-31  5:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 14:30 [PATCH 1/3] rust: Update "do_update_snapshot" task for rust-snapshot.inc Yash.Shinde
2025-03-28 14:30 ` [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0 Yash.Shinde
2025-03-28 14:40   ` [OE-core] " Richard Purdie
2025-03-28 18:39     ` Alexander Kanavin
2025-03-31  5:51       ` Yash Shinde [this message]
2025-03-28 14:50   ` Patchtest results for " patchtest
2025-03-28 15:17   ` [OE-core] " Koen Kooi
2025-03-28 17:51     ` Richard Purdie
2025-03-31  5:52       ` Yash Shinde
2025-03-28 18:02     ` Khem Raj
2025-03-31  5:52       ` Yash Shinde
2025-03-28 20:56   ` Randy MacLeod
2025-03-29 15:26     ` Richard Purdie
2025-03-31  5:53       ` Yash Shinde
2025-03-28 14:30 ` [PATCH 3/3] rust: Upgrade 1.85.0->1.85.1 Yash.Shinde
2025-03-28 14:50   ` Patchtest results for " patchtest

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=1a1ab4d3-1972-4954-a14f-2f974d0bb04b@windriver.com \
    --to=yash.shinde@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=alex.kanavin@gmail.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 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.