yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Anton Antonov <anton.antonov@arm.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-security][PATCH] parsec-service: update from 1.1.0 to 1.2.0-rc1
Date: Fri, 24 Mar 2023 14:34:44 +0200	[thread overview]
Message-ID: <ZB2Y5JBzeg2z10aW@nuoska> (raw)
In-Reply-To: <21387.1679660671564653204@lists.yoctoproject.org>

Hi,

On Fri, Mar 24, 2023 at 05:24:31AM -0700, Anton Antonov wrote:
> Hi Mikko,
> 
> Thank you for the patch. In general I don't mind switching from "cargo bitbake" to "bitbake -c update_crates" for Parsec recipes. But, in this case when you use a git repository instead of a Parsec crate the cargo-update-recipe-crates class includes dependency crates from "fuzz/Cargo.lock" which are not required for Yocto builds.

Ok, will remove these.

> If you urgently need a new Yocto Parsec recipe then please remove all the fuzz/Cargo.lock dependencies. Otherwise we can wait until Parsec 1.2.0 crate released.

parsec-service recipe has been broken for weeks already. I want this
to be resolved and backporting fixes to parsec 1.1.0 doesn't seem to
work.

Cheers,

-Mikko


      reply	other threads:[~2023-03-24 12:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  7:24 [meta-security][PATCH] parsec-service: update from 1.1.0 to 1.2.0-rc1 Mikko Rapeli
2023-03-23 11:45 ` [yocto] " akuster808
2023-03-24 15:05   ` Anton Antonov
2023-03-27  5:36     ` [yocto] " Mikko Rapeli
2023-03-24 12:24 ` Anton Antonov
2023-03-24 12:34   ` Mikko Rapeli [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=ZB2Y5JBzeg2z10aW@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=anton.antonov@arm.com \
    --cc=yocto@lists.yoctoproject.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;
as well as URLs for NNTP newsgroup(s).