bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: "Frédéric Martinsons" <frederic.martinsons@gmail.com>
Cc: bitbake-devel@lists.openembedded.org, martin.jansa@gmail.com
Subject: Re: [bitbake-devel] [PATCH] fetch2: Display all missing checksum at once
Date: Tue, 4 Apr 2023 16:43:02 -0400	[thread overview]
Message-ID: <fc8a7686-5c56-c605-2d69-8afbb8b477d2@mvista.com> (raw)
In-Reply-To: <CA+cAkepKcDJSYMq7tbY=27QTaMq8AQXHqevfmux4ka43A4htQQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]



On 4/4/23 1:07 PM, Frédéric Martinsons wrote:
>
>
> On Tue, 4 Apr 2023 at 18:50, akuster <akuster@mvista.com> wrote:
>
>
>
>     On 4/1/23 11:21 AM, Frederic Martinsons wrote:
>     > From: Frederic Martinsons <frederic.martinsons@gmail.com>
>     >
>     > Instead of only display the first and stop.
>     > For recipe (crago based) that can contains several artifacts
>     > to fetch with their checksum, it will particularly handy
>     > to display all of missing one.
>     >
>     > An example of error message would be
>
>     I am confused. Is this patch supposed to add the pkg version or
>     not?  I
>     am not seeing any. Any ideas?
>
>     I will be holding off branching meta-security until my 4 rust recipes
>     can build again.
>
>     -armin
>
>
> Hello,
>
> This patch is only for showing all missing checksum on crates for a 
> recipe.
> To build the checskum list (with the version), you can use bitbake -c 
> update_crates <your recipe>

update_crates fails when it starts to traverse  into the vendor dir. It 
can't parse the Cargo.toml files correctly.


> and if you start from a pristine, you should have an error which will 
> contain
> all the data you want to copy/paste (if you have this present patch in 
> bitbake)
>
> The naming for pkg and version is already included in 
> cargo-update-recipe-crates.bbclass 
> <https://git.openembedded.org/openembedded-core/tree/meta/classes-recipe/cargo-update-recipe-crates.bbclass?id=1795e98a04ad09b011afcc7cc3bf6dc49475b19a> from oe-core 
> master:
> see 
> https://git.openembedded.org/openembedded-core/commit/?id=1795e98a04ad09b011afcc7cc3bf6dc49475b19a
>


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4581 bytes --]

  reply	other threads:[~2023-04-04 20:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 15:21 [PATCH] fetch2: Display all missing checksum at once frederic.martinsons
2023-04-04 16:49 ` [bitbake-devel] " akuster
2023-04-04 17:07   ` Frédéric Martinsons
2023-04-04 20:43     ` akuster [this message]
2023-04-04 17:07   ` Martin Jansa
2023-04-04 21:08     ` akuster
2023-04-04 21:35       ` Martin Jansa
2023-04-05  5:20         ` Frédéric Martinsons
2023-04-05  9:39           ` Enrico Scholz
2023-04-05  9:51             ` Frédéric Martinsons
2023-04-05 10:14               ` Enrico Scholz
2023-04-05 10:49                 ` Frédéric Martinsons
2023-04-05 11:38           ` akuster
2023-04-05 12:25           ` akuster
2023-04-05 12:51             ` Frédéric Martinsons
2023-04-05 16:26               ` akuster808
2023-04-05 16:32                 ` Frédéric Martinsons

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=fc8a7686-5c56-c605-2d69-8afbb8b477d2@mvista.com \
    --to=akuster@mvista.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=frederic.martinsons@gmail.com \
    --cc=martin.jansa@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;
as well as URLs for NNTP newsgroup(s).