Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Alex Kiernan <alex.kiernan@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-Core][PATCH] rust: Upgrade 1.68.1 -> 1.68.2
Date: Mon, 10 Apr 2023 19:30:51 +0200	[thread overview]
Message-ID: <2023041017305195b4c7aa@mail.local> (raw)
In-Reply-To: <CAMKF1sq_jvEn5VYmAnRj8HKrXtGAWj8cmD+O6eRHiBqdsLf_EQ@mail.gmail.com>

My current a-full has this patch.

On 10/04/2023 10:21:16-0700, Khem Raj wrote:
> If possible, Can you test this on top of contrib/abelloni/master-next
> for musl target ?
> 
> On Mon, Apr 10, 2023 at 2:42 AM Alex Kiernan <alex.kiernan@gmail.com> wrote:
> >
> > Changes:
> >
> > * Update the GitHub RSA host key bundled within Cargo. The key was
> >   rotated by GitHub on 2023-03-24 after the old one leaked.
> > * Mark the old GitHub RSA host key as revoked. This will prevent Cargo
> >   from accepting the leaked key even when trusted by the system.
> > * Add support for @revoked and a better error message for
> >   @cert-authority in Cargo’s SSH host key verification
> >
> > Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> > ---
> >
> >  meta/recipes-devtools/rust/{cargo_1.68.1.bb => cargo_1.68.2.bb} | 0
> >  .../rust/{libstd-rs_1.68.1.bb => libstd-rs_1.68.2.bb}           | 0
> >  ...t-cross-canadian_1.68.1.bb => rust-cross-canadian_1.68.2.bb} | 0
> >  .../rust/{rust-llvm_1.68.1.bb => rust-llvm_1.68.2.bb}           | 0
> >  meta/recipes-devtools/rust/rust-source.inc                      | 2 +-
> >  meta/recipes-devtools/rust/{rust_1.68.1.bb => rust_1.68.2.bb}   | 0
> >  6 files changed, 1 insertion(+), 1 deletion(-)
> >  rename meta/recipes-devtools/rust/{cargo_1.68.1.bb => cargo_1.68.2.bb} (100%)
> >  rename meta/recipes-devtools/rust/{libstd-rs_1.68.1.bb => libstd-rs_1.68.2.bb} (100%)
> >  rename meta/recipes-devtools/rust/{rust-cross-canadian_1.68.1.bb => rust-cross-canadian_1.68.2.bb} (100%)
> >  rename meta/recipes-devtools/rust/{rust-llvm_1.68.1.bb => rust-llvm_1.68.2.bb} (100%)
> >  rename meta/recipes-devtools/rust/{rust_1.68.1.bb => rust_1.68.2.bb} (100%)
> >
> > diff --git a/meta/recipes-devtools/rust/cargo_1.68.1.bb b/meta/recipes-devtools/rust/cargo_1.68.2.bb
> > similarity index 100%
> > rename from meta/recipes-devtools/rust/cargo_1.68.1.bb
> > rename to meta/recipes-devtools/rust/cargo_1.68.2.bb
> > diff --git a/meta/recipes-devtools/rust/libstd-rs_1.68.1.bb b/meta/recipes-devtools/rust/libstd-rs_1.68.2.bb
> > similarity index 100%
> > rename from meta/recipes-devtools/rust/libstd-rs_1.68.1.bb
> > rename to meta/recipes-devtools/rust/libstd-rs_1.68.2.bb
> > diff --git a/meta/recipes-devtools/rust/rust-cross-canadian_1.68.1.bb b/meta/recipes-devtools/rust/rust-cross-canadian_1.68.2.bb
> > similarity index 100%
> > rename from meta/recipes-devtools/rust/rust-cross-canadian_1.68.1.bb
> > rename to meta/recipes-devtools/rust/rust-cross-canadian_1.68.2.bb
> > diff --git a/meta/recipes-devtools/rust/rust-llvm_1.68.1.bb b/meta/recipes-devtools/rust/rust-llvm_1.68.2.bb
> > similarity index 100%
> > rename from meta/recipes-devtools/rust/rust-llvm_1.68.1.bb
> > rename to meta/recipes-devtools/rust/rust-llvm_1.68.2.bb
> > diff --git a/meta/recipes-devtools/rust/rust-source.inc b/meta/recipes-devtools/rust/rust-source.inc
> > index c8f5a5a9c4c4..6d3a4b131e26 100644
> > --- a/meta/recipes-devtools/rust/rust-source.inc
> > +++ b/meta/recipes-devtools/rust/rust-source.inc
> > @@ -7,7 +7,7 @@ SRC_URI += "https://static.rust-lang.org/dist/rustc-${RUST_VERSION}-src.tar.xz;n
> >              file://0001-Do-not-use-LFS64-on-linux-with-musl.patch;patchdir=${RUSTSRC} \
> >              file://zlib-off64_t.patch;patchdir=${RUSTSRC} \
> >  "
> > -SRC_URI[rust.sha256sum] = "5b8ea94085b65e75c1fa6310e2f90bd706fa80bfcb3544fe26f4037b911d9fb2"
> > +SRC_URI[rust.sha256sum] = "ce1a115f6aafa912b4622906a92b626354973afa9288e2c7750df4dcf3390fc0"
> >
> >  RUSTSRC = "${WORKDIR}/rustc-${RUST_VERSION}-src"
> >
> > diff --git a/meta/recipes-devtools/rust/rust_1.68.1.bb b/meta/recipes-devtools/rust/rust_1.68.2.bb
> > similarity index 100%
> > rename from meta/recipes-devtools/rust/rust_1.68.1.bb
> > rename to meta/recipes-devtools/rust/rust_1.68.2.bb
> > --
> > 2.39.0
> >
> >
> > 
> >

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#179897): https://lists.openembedded.org/g/openembedded-core/message/179897
> Mute This Topic: https://lists.openembedded.org/mt/98172309/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-04-10 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  9:41 [OE-Core][PATCH] rust: Upgrade 1.68.1 -> 1.68.2 Alex Kiernan
2023-04-10 17:21 ` Khem Raj
2023-04-10 17:30   ` Alexandre Belloni [this message]
2023-04-10 18:11     ` Khem Raj
2023-04-11  7:06       ` Khem Raj
2023-04-11  7:18         ` Alex Kiernan
2023-04-11 16:53           ` Alexandre Belloni

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=2023041017305195b4c7aa@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox