| Summary: |
RRS: upgrade history stuck at the 2025 addfragments syntax change |
| Product: |
[Yocto Project Subprojects] Recipe Reporting System (RRS)
|
Reporter: |
Tim Orling <tim.orling> |
| Component: |
Recipe Reporting System (RRS) | Assignee: |
Tim Orling <tim.orling> |
| Status: |
IN PROGRESS REVIEW
---
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
|
|
| Version: |
unspecified | |
|
| Target Milestone: |
6.2 M2 | |
|
| Hardware: |
All | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Don't know
|
|---|
rrs_upgrade_history.py stops at the first OE-Core commit after 2025-06-18 and never gets further: the BitBake server it starts fails to parse OE-Core's configuration and then waits for ever. bb.parse.ParseError: ParseError at .../meta/conf/bitbake.conf:824: unparsed line: 'addfragments ${OE_FRAGMENTS_PREFIX} OE_FRAGMENTS OE_FRAGMENTS_METADATA_VARS' For each OE-Core commit the script uses the last BitBake commit before it. BitBake 3b9d7bea9 ("parse/ast: add support for 'built-in' fragments", 2025-06-18) changed addfragments to take four arguments, and OE-Core only switched in e959f916b4 ("bitbake.conf: enable built-in fragments for MACHINE and DISTRO", 2025-06-20). OE-Core commits in between, the first being 8dca5305c9 ("libpng: Add ptest"), get a BitBake they can't be parsed with. The script already has a table of such BitBake ranges (remap_range) to use an earlier BitBake instead, but it maps by BitBake revision only; here the right BitBake depends on whether the OE-Core commit is before or after e959f916b4. On layers.openembedded.org the latest recipe upgrade recorded is from 2025-06-16, which fits the upgrade history being stuck here since then.