[Development] Qt 5.12.12 branches disappeared from code.qt.io?

[Samuli Piippo]

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.

Instead, you can add
  QT_MODULE_BRANCH_PARAM:append = ";nobranch=1"
somewhere in your own configs.
This tells bitbake to stop the validation [1].

We've included the same workaround [2] for all active meta-qt6 branches so that this won't happen with the future releases.

-samuli

[1] https://docs.yoctoproject.org/migration-guides/migration-1.6.html?highlight=nobranch#matching-branch-requirement-for-git-fetching
[2] https://codereview.qt-project.org/c/yocto/meta-qt6/+/447775
________________________________
From: Development <development-bounces at qt-project.org> on behalf of Thiago Macieira <thiago.macieira at intel.com>
Sent: 12 January 2023 20:50
To: development at qt-project.org <development at qt-project.org>
Subject: Re: [Development] Qt 5.12.12 branches disappeared from code.qt.io?

On Thursday, 12 January 2023 07:54:33 PST Jon Trulson wrote:
> The reason this became a problem for me was that meta-qt5's warrior
> branch uses these Qt branches (5.12.12 in my case), and these builds now
> fail.

They should use the tags, not the branches.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering



_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20230113/aae20f36/attachment-0001.htm>