On 18 November 2026 the master branch of meta-sunxi changed its declared compatibility from wrynose to blacksail. The layer has no wrynose branch, so no branch of meta-sunxi now declares the current LTS release. Teams that build Wrynose images for Allwinner boards from master need to pin the layer before their next fetch. In the same period Yocto 6.1 Blacksail was released, and the wrynose branch of meta-xilinx moved its default release from v2026.1 to v2026.2.
This report covers what changed in Yocto layers between 20 October and 19 November 2026, as shown on the TECH VEDA Yocto layers tracker, which was read on 19 November 2026 and shows a last check of 15 November 2026. It is the first report on this tracker, so each “before” value is the one recorded at the weekly refresh of 18 October 2026 unless the table says otherwise. Each “now” value was read again on 19 November from the layer’s own repository or from the Yocto Project. Dates are those sources’ commit and release dates, not tracker edit dates. Where a repository has moved since the last check, the table gives the repository’s value and says what the page shows.
What changed in Yocto layers
| Item | Before | Now | Date of change (committer date for a branch head) | Source |
|---|---|---|---|---|
| meta-sunxi, compatibility declared on master | wrynose, with no wrynose branch | blacksail, still with no wrynose branch. The tracker page still shows wrynose, the value at its last check. | 18 November 2026 | meta-sunxi repository, commit ab1095e and conf/layer.conf on master |
| Yocto 6.1 Blacksail | Listed as upcoming (record of 1 November 2026) | Released; stable release supported until April 2027 | 21 October 2026 (release announcement) | Yocto Project announcement and releases page |
| meta-xilinx, wrynose branch | Head of 16 September 2026; default XILINX_RELEASE_VERSION v2026.1 | Head 9ad7d68; default v2026.2; kernel recipe linux-xlnx 6.18.40. The tracker page shows a head of 26 October and v2026.1. | 11 November 2026 | meta-xilinx repository, meta-xilinx-core/conf/layer.conf on wrynose |
| meta-st-stm32mp, branches | One Wrynose branch recorded, wrynose_v26.02.18, building Linux 6.6 | A second branch, plain wrynose, head 54ca599, whose only kernel recipes are for Linux 6.18.37 | 13 November 2026 (head of the plain branch; first recorded on 8 November) | meta-st-stm32mp repository |
| meta-selinux, wrynose branch | Head of 6 June 2026 | Head 83b7423 | 12 November 2026 | meta-selinux repository |
| meta-freescale, wrynose branch | Head b23da7c, 16 October 2026 | Head d5003de | 12 November 2026 | meta-freescale repository |
meta-imx, branch wrynose-6.18.37-2.1.0 | Head of 8 September 2026 | Head 2eb758f | 10 November 2026 | meta-imx repository |
| meta-ti, wrynose branch | Head of 8 October 2026 | Head c4c910b | 12 November 2026 | meta-ti repository |
| meta-tegra, wrynose branch | Head of 8 October 2026 | Head 30ea3e5. The tracker page shows 11 November. | 16 November 2026 | meta-tegra repository |
| meta-qcom, wrynose branch | Head 793056c, 15 October 2026 | Head 215d5ad. The tracker page shows 15 November. | 18 November 2026 | meta-qcom repository |
| meta-openembedded, wrynose branch | Head f28a144, 6 October 2026 | Head c0fcd7c | 9 November 2026 | meta-openembedded repository |
| meta-mender, wrynose branch | Head af44bda, 15 October 2026 | Head fe71e2b. The tracker page shows 10 November. | 18 November 2026 | meta-mender repository |
| meta-swupdate, wrynose branch | Head 80f749c, 16 October 2026 | Head dcd42c7. The tracker page shows 13 November. | 18 November 2026 | meta-swupdate repository |
| meta-virtualization, wrynose branch | Head 28075796, 4 October 2026 | Head f27e259. The tracker page shows 5 November. | 16 November 2026 | meta-virtualization repository |
meta-qt6, branch lts-6.8 | Head 1fe3c3aa, 10 October 2026 | Head ff142e8. The tracker page shows 13 November. | 18 November 2026 | meta-qt6 repository |
meta-sunxi master now declares only blacksail: pin the layer for Wrynose builds
The tracker’s finding for meta-sunxi was that the layer declared wrynose on master and had no wrynose branch, so a Wrynose build had to use master. On 18 November 2026 a commit changed LAYERSERIES_COMPAT_sunxi from wrynose to blacksail, and it was merged to master on the same day. The only other branch, walnascar, declares walnascar, a release the Yocto Project lists as end of life.
BitBake compares the series a layer declares with the series of the core layer and stops with an error when they do not match, so a Wrynose build that fetches the current master of meta-sunxi stops at that check. What the LTS release does and does not maintain for you is explained in What the Yocto LTS Covers, and What It Does Not.
Who is affected: Wrynose builds that take their machine configuration from meta-sunxi, which carries Allwinner boards of the Orange Pi, NanoPi, Banana Pi and OLinuXino families.
What to do, and by when:
- Before the next fetch of master: pin meta-sunxi to commit
a08678762dbb9c4bdad392e0153cd544ae351865, dated 30 October 2026. It is the last commit on master that declares wrynose. - This month: decide who maintains the layer for your product. Master is now developed against Blacksail, so fixes you need on Wrynose have to be carried in your own copy.
raghu@techveda.org:~$ grep LAYERSERIES_COMPAT meta-sunxi/conf/layer.conf
raghu@techveda.org:~$ git -C meta-sunxi checkout a08678762dbb9c4bdad392e0153cd544ae351865meta-xilinx wrynose now defaults to v2026.2: decide before the next layer update
The repository history shows that the default XILINX_RELEASE_VERSION on the wrynose branch was still v2026.1 at the commit of 26 October. On 11 November 2026 the branch rel-v2026.2 was merged into wrynose. The default is now v2026.2, and the kernel recipe at the head is linux-xlnx 6.18.40, still in the 6.18 series.
Who is affected: Zynq UltraScale+ MPSoC products on Wrynose whose manifest follows the branch head. A manifest pinned by commit is not affected until the pin moves.
What to do: if you follow the branch head, your next layer update selects the v2026.2 recipes. Either plan a regression test, or pin the layer to commit d0d780700c061c4ca6007680d0e3b03f2dad7641 of 26 October 2026, the last commit on the wrynose branch with the v2026.1 default. The rel-v2026.1 branch is not a substitute, because it declares scarthgap. This report read only the repository and makes no statement about a release announcement from AMD.
Yocto 6.1 Blacksail is released: check which branch each layer is fetched from
On 1 November the tracker still listed Blacksail as upcoming. The Yocto Project announced the 6.1 release on 21 October 2026, and its releases page lists Blacksail as a stable release until April 2027, not as an LTS. Wrynose remains the LTS release, listed until April 2030.
This matters for Wrynose products because master branches follow the newest release. On 19 November the master branches of meta-raspberrypi, meta-qcom and meta-tegra declare only blacksail. Each of the three has a wrynose branch; meta-sunxi does not.
Who is affected: any Wrynose product whose manifest names master for a layer. What to do this week: for each of the Yocto layers in the manifest, name the wrynose branch or a commit on it, so that a change on master cannot alter the release the layer declares to your build.
meta-selinux moved after five months: review the new commits
The wrynose branch of meta-selinux had a head of 6 June 2026 on 18 October. Its head is now a commit of 12 November 2026 that backports a reference policy change. Wrynose products that enable SELinux through this layer should read the commits added since their pin, and test the services they confine before taking them.
Unchanged but worth noting
- meta-st-stm32mp: the tagged release branch
wrynose_v26.02.18still has a head of 17 August 2026 and still builds Linux 6.6. Last verified 19 November 2026. - meta-rockchip: the wrynose branch head is still the commit of 8 April 2026. Last verified 19 November 2026.
Next dates
The Yocto Project release calendar plans these releases in the next 60 days. Each date is a week commencing, and each is the project’s plan, not a confirmed release date.
- 6.1.1 Blacksail: week commencing 23 November 2026
- 6.0.5 Wrynose: week commencing 30 November 2026
- 5.0.22 Scarthgap: week commencing 7 December 2026
- 6.1.2 Blacksail: week commencing 4 January 2027
- 6.0.6 Wrynose: week commencing 18 January 2027
What was checked and what could not be verified
Checked on 19 November 2026: the live page for Yocto layers; the eleven BSP layer and ten software layer repositories on it, each read with git for the branch head and for LAYERSERIES_COMPAT; and the Yocto Project releases page, release calendar and 6.1 announcement.
Not verified, or different between sources: the Yocto Project releases page gives September 2026 as the original release month of 6.1, while the announcement is dated 21 October 2026; this report uses the announcement date. The activity labels of 18 October are not in the record, so no change of label is reported. The tracker rows for meta-freescale and meta-tegra still describe Blacksail as not yet released. Differences between the page and the repositories are marked in the table.
Key takeaways
- Among the Yocto layers tracked, meta-sunxi no longer declares Wrynose on any branch. Pin it to the commit of 30 October 2026 if you build Wrynose from it.
- The wrynose branch of meta-xilinx now defaults to v2026.2.
- Blacksail is released and is not an LTS. For Wrynose products, fetch Yocto layers from their wrynose branch, not from master.
Frequently asked questions
Which branch of meta-sunxi declares Wrynose on 19 November 2026?
None. The master branch declares blacksail since a commit of 18 November 2026, the walnascar branch declares walnascar, and the repository has no wrynose branch. The last commit on master that declares wrynose is a08678762dbb, dated 30 October 2026.
Is Yocto 6.1 Blacksail an LTS release?
No. The Yocto Project lists Blacksail as a stable release until April 2027. Wrynose is the LTS release, listed until April 2030.
When is the next Wrynose point release planned?
The Yocto Project release calendar plans 6.0.5 for the week commencing 30 November 2026. This is a plan, and the calendar gives a week, not a day.

