Re: [bitbake-devel] [PATCH] fetch:crate: create versioned 'name' entries

[Enrico Scholz <enrico.scholz@sigma-chemnitz.de>]

Richard Purdie <richard.purdie@linuxfoundation.org> writes:

>> > It will break cargo related recipes which were created between
>> > 2023-03-16 and 2023-03-31.  Packages before this date do not
>> > contain sha256sum and after this date, they have an explicit
>> > 'name' (which matches the one generated by my patch).
>> 
>> Ok, I guess these dates match my patches series, if I do things
>> rights, I handle all the recipes I know of (in meta-openembedded and
>> openembedded-core at least) 
>
> This now gives me a problem as rc1 for 4.2 built yesterday. I'm
> guessing we don't want a stable release series with one form for urls
> for six months and a different one in master?
>
> Does this mean I need to scrap rc1, merge this, wait for the recipe
> updates and then rebuild the release?

To avoid breaking builds:

1. OE recipes without explicit ';name=' need to be updated; this can be
   done by 'bitbake -c update_crates'.  Afais, this affects only
   
   | meta/recipes-devtools/python/python3-bcrypt_4.0.1.bb
   | meta/recipes-devtools/python/python3-cryptography_39.0.2.bb

   and in oe-meta

   | meta-oe/recipes-core/uutils-coreutils/uutils-coreutils_0.0.17.bb
   | meta-python/recipes-devtools/python/python3-pyruvate_1.1.2.bb

2. the patch can be applied to bitbake

3. [optionally] change cargo-update-recipe-crates.bbclass to remove the
   explicit (and now redundant) ';name=' from generated SRC_URI list.
   This can be done post-mickledore



Enrico