Bug 13190

Summary: RRS cannot handle multiple recipes with same PN
Product: [Yocto Project Subprojects] Recipe Reporting System (RRS) Reporter: Paul Eggleton <bluelightning>
Component: Recipe Reporting System (RRS)Assignee: Unassigned <unassigned>
Status: NEW --- QA Contact: apoorv sangal <apoorvsangal>
Severity: normal    
Priority: Medium+ CC: bluelightning, randy.macleod, tgamblin, tim.orling, Venkatasainath.Ravikanti, yi.zhao
Version: unspecified   
Target Milestone: 6.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Paul Eggleton 2019-02-20 20:36:35 UTC 
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.
Comment 1 Paul Eggleton 2019-11-28 20:20:30 UTC 
The code got merged for this - now we need to pick a time for upgrading layers.openembedded.org.
Comment 2 Randy MacLeod 2021-04-29 15:39:50 UTC 
Paul, Tim, Did this upgrade happen already?
Comment 3 Randy MacLeod 2021-05-20 15:42:03 UTC 
Might be fixed already... Paul?
Comment 4 Trevor Gamblin 2021-11-25 19:38:58 UTC 
Paul, can you confirm if this is still an issue?
Comment 5 Randy MacLeod 2022-04-13 00:24:08 UTC 
Tim, is this fix enabled with the latest update of layer index or is this a different workflow?
Comment 6 Randy MacLeod 2023-06-15 13:58:41 UTC 
Yi, it would be good if you could work on this before M3.
Comment 7 Trevor Gamblin 2023-09-14 15:56:09 UTC 
Moved to M4.
Comment 8 Randy MacLeod 2023-10-30 15:29:11 UTC 
Bulk move to 5.0 M1. -- Randy
Comment 9 Randy MacLeod 2023-12-21 21:06:16 UTC 
William, please check and report on the status of this old bug since you are learning about RRS.
Comment 10 Randy MacLeod 2024-07-22 21:07:21 UTC 
Clearly not urgent so moving to 5.99 as a Medium+ .
If someone wants to work on this problem, that would be great!