<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">Using tags for the yocto builds is not going to help, since the
 way bitbake tries to validate the SHA1s that are already being used in the meta-qt5 and meta-qt6 recipes.</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">Instead, you can add</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0">  QT_MODULE_BRANCH_PARAM:append = ";nobranch=1"<br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0">somewhere in your own configs.
<br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0">This tells bitbake to stop the validation
<span style="font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="ContentPasted0 FluidPluginCopy ContentPasted4">
[1]</span>.<br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0 ContentPasted1">We've included the same workaround
 [2] for all active meta-qt6 branches so that this won't happen with the future releases.<br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0 ContentPasted1"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0 ContentPasted1">-samuli<br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0 ContentPasted1"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0 ContentPasted1 ContentPasted2">[1]
<a href="https://docs.yoctoproject.org/migration-guides/migration-1.6.html?highlight=nobranch#matching-branch-requirement-for-git-fetching" id="LPlnk639059">
https://docs.yoctoproject.org/migration-guides/migration-1.6.html?highlight=nobranch#matching-branch-requirement-for-git-fetching</a><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof ContentPasted0 ContentPasted1 ContentPasted2">[2]
<span style="font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="ContentPasted0 ContentPasted1 FluidPluginCopy ContentPasted3">
<a href="https://codereview.qt-project.org/c/yocto/meta-qt6/+/447775" class="ContentPasted3">https://codereview.qt-project.org/c/yocto/meta-qt6/+/447775</a>
</span><br>
</span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Development <development-bounces@qt-project.org> on behalf of Thiago Macieira <thiago.macieira@intel.com><br>
<b>Sent:</b> 12 January 2023 20:50<br>
<b>To:</b> development@qt-project.org <development@qt-project.org><br>
<b>Subject:</b> Re: [Development] Qt 5.12.12 branches disappeared from code.qt.io?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Thursday, 12 January 2023 07:54:33 PST Jon Trulson wrote:<br>
> The reason this became a problem for me was that meta-qt5's warrior<br>
> branch uses these Qt branches (5.12.12 in my case), and these builds now<br>
> fail.<br>
<br>
They should use the tags, not the branches.<br>
<br>
-- <br>
Thiago Macieira - thiago.macieira (AT) intel.com<br>
  Cloud Software Architect - Intel DCAI Cloud Engineering<br>
<br>
<br>
<br>
_______________________________________________<br>
Development mailing list<br>
Development@qt-project.org<br>
<a href="https://lists.qt-project.org/listinfo/development">https://lists.qt-project.org/listinfo/development</a><br>
</div>
</span></font></div>
</body>
</html>