At the moment the RRS has trouble dealing with the situation where multiple recipes have the same name (PN); e.g. linux-yocto in OE-Core; as far as the recipe upgrade logic is concerned they are all the same recipe, *but* the recipe upgrade records have to be associated with a single (current) recipe object so the first one in the database gets picked. Thus, you will see only one of the recipes show up in the RRS recipe list, and worse if you click on it it may not show the same recipe version as the one listed in the recipe list. Fixing this may be tricky because of the aforementioned linking of history with current recipes - e.g. there might have been three versions at one point in history and only two versions currently, so which recipe object gets the history? Relatedly, those maintainers who are assigned to such recipes will have recipe counts/percentages that don't make sense.
The code got merged for this - now we need to pick a time for upgrading layers.openembedded.org.
Paul, Tim, Did this upgrade happen already?
Might be fixed already... Paul?
Paul, can you confirm if this is still an issue?
Tim, is this fix enabled with the latest update of layer index or is this a different workflow?
Yi, it would be good if you could work on this before M3.
Moved to M4.
Bulk move to 5.0 M1. -- Randy
William, please check and report on the status of this old bug since you are learning about RRS.
Clearly not urgent so moving to 5.99 as a Medium+ . If someone wants to work on this problem, that would be great!