<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13190</bug_id>
          
          <creation_ts>2019-02-20 20:36:35 +0000</creation_ts>
          <short_desc>RRS cannot handle multiple recipes with same PN</short_desc>
          <delta_ts>2026-07-23 15:17:00 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Recipe Reporting System (RRS)</product>
          <component>Recipe Reporting System (RRS)</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>6.99</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Paul Eggleton">bluelightning</reporter>
          <assigned_to name="Unassigned">unassigned</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>randy.macleod</cc>
    
    <cc>tgamblin</cc>
    
    <cc>tim.orling</cc>
    
    <cc>Venkatasainath.Ravikanti</cc>
    
    <cc>yi.zhao</cc>
          
          <qa_contact name="apoorv sangal">apoorvsangal</qa_contact>
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>83052</commentid>
    <comment_count>0</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2019-02-20 20:36:35 +0000</bug_when>
    <thetext>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&apos;t make sense.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85665</commentid>
    <comment_count>1</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2019-11-28 20:20:30 +0000</bug_when>
    <thetext>The code got merged for this - now we need to pick a time for upgrading layers.openembedded.org.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>90181</commentid>
    <comment_count>2</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-04-29 15:39:50 +0000</bug_when>
    <thetext>Paul, Tim, Did this upgrade happen already?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>90439</commentid>
    <comment_count>3</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2021-05-20 15:42:03 +0000</bug_when>
    <thetext>Might be fixed already... Paul?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>92073</commentid>
    <comment_count>4</comment_count>
    <who name="Trevor Gamblin">tvgamblin</who>
    <bug_when>2021-11-25 19:38:58 +0000</bug_when>
    <thetext>Paul, can you confirm if this is still an issue?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>93018</commentid>
    <comment_count>5</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2022-04-13 00:24:08 +0000</bug_when>
    <thetext>Tim, is this fix enabled with the latest update of layer index or is this a different workflow?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95723</commentid>
    <comment_count>6</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2023-06-15 13:58:41 +0000</bug_when>
    <thetext>Yi, it would be good if you could work on this before M3.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>96451</commentid>
    <comment_count>7</comment_count>
    <who name="Trevor Gamblin">tgamblin</who>
    <bug_when>2023-09-14 15:56:09 +0000</bug_when>
    <thetext>Moved to M4.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>97070</commentid>
    <comment_count>8</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2023-10-30 15:29:11 +0000</bug_when>
    <thetext>Bulk move to 5.0 M1. -- Randy</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>97645</commentid>
    <comment_count>9</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2023-12-21 21:06:16 +0000</bug_when>
    <thetext>William, please check and report on the status of this old bug since you are learning about RRS.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>99421</commentid>
    <comment_count>10</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2024-07-22 21:07:21 +0000</bug_when>
    <thetext>Clearly not urgent so moving to 5.99 as a Medium+ .
If someone wants to work on this problem, that would be great!</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>