<?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>13425</bug_id>
          
          <creation_ts>2019-07-02 16:03:49 +0000</creation_ts>
          <short_desc>Add bblock and bbunlock helper tools</short_desc>
          <delta_ts>2023-11-16 15:56:26 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>Scripts and Tools</component>
          <version>2.7</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>NEWCOMER</status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>4.3 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Richard Purdie">richard.purdie</reporter>
          <assigned_to name="Julien Stephan">jstephan</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>duy.dang.yw</cc>
    
    <cc>jstephan</cc>
    
    <cc>randy.macleod</cc>
    
    <cc>ross.burton</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>84360</commentid>
    <comment_count>0</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2019-07-02 16:03:49 +0000</bug_when>
    <thetext>It would be nice to be able to lock specific recipes against changes when doing development work. This could be in the form of the bblock X and bbunlock X commands.

The mechanism would use the locked-sigs mechanism which can be seen by:

&quot;bitbake bash -S none&quot;
then looking at the locked-sigs.inc file it generated. These are activated by including the inc file in local.conf.

The lock/unlock commands would use entries of this syntax, probably in a separate file they could maniululate, included from local.conf.

When locked sigs are in operation, a note to the user, similar to the way the &quot;-f&quot; taint files trigger notes to the user would be desirable.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>84370</commentid>
    <comment_count>1</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2019-07-04 10:02:54 +0000</bug_when>
    <thetext>*** Bug 6425 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>84371</commentid>
    <comment_count>2</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2019-07-04 10:05:17 +0000</bug_when>
    <thetext>As a note, tinfoil would have APIs which could implement this (or we&apos;d add them)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85423</commentid>
    <comment_count>3</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2019-10-23 15:24:01 +0000</bug_when>
    <thetext>I hacked up this last week.

https://github.com/rossburton/bb/blob/master/libexec/bb-lockdown

basically uses -S to generate a locked-sigs.inc, removes the lines that we still want to rebuild, then writes an auto.conf to pull the file in.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95315</commentid>
    <comment_count>4</comment_count>
    <who name="Duy Dang">duy.dang.yw</who>
    <bug_when>2023-04-07 07:38:33 +0000</bug_when>
    <thetext>Hi Richard,

I can handle this Bug.
But in what case do people need to lock a specific recipe?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95323</commentid>
    <comment_count>5</comment_count>
    <who name="Duy Dang">duy.dang.yw</who>
    <bug_when>2023-04-10 02:36:08 +0000</bug_when>
    <thetext>Hi Richard, Ross,

Do we create a new parameter for bitbake to do this feature? Or just a script same as Ross&apos; one in poky/scripts ?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95338</commentid>
    <comment_count>6</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2023-04-12 10:34:06 +0000</bug_when>
    <thetext>If for example someone wants to make changes to the rust recipe but doesn&apos;t want rust-native to rebuild every time, they only want to rebuild rust itself. In this case they would lock rust-native.

I think this should be a separate tool and not an option to bitbake. We can use the tinfoil bitbake API if needed though.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95925</commentid>
    <comment_count>7</comment_count>
    <who name="Julien Stephan">jstephan</who>
    <bug_when>2023-07-17 13:11:31 +0000</bug_when>
    <thetext>Hi Duy, Richard and Ross, 
I would be happy to help on this. Duy did you make any progress on this?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95926</commentid>
    <comment_count>8</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2023-07-17 13:40:30 +0000</bug_when>
    <thetext>I&apos;m unaware of any progress beyond my scripts being a demonstration that the concept works.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95927</commentid>
    <comment_count>9</comment_count>
    <who name="Julien Stephan">jstephan</who>
    <bug_when>2023-07-17 13:48:17 +0000</bug_when>
    <thetext>Ok, so I&apos;ll take a look at this</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>95930</commentid>
    <comment_count>10</comment_count>
    <who name="Duy Dang">duy.dang.yw</who>
    <bug_when>2023-07-18 03:17:35 +0000</bug_when>
    <thetext>Hi Julien,
I&apos;m busy recently and cannot handle it. So that&apos;s OK if you can take this bug</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>96109</commentid>
    <comment_count>11</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2023-07-26 21:29:36 +0000</bug_when>
    <thetext>Bulk move to 4.3 M3.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>97268</commentid>
    <comment_count>12</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2023-11-16 15:56:26 +0000</bug_when>
    <thetext>Merged in 2d9ab0cfd7f3cacc347954676f1323342a6b286f.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>