| Summary: | bitbake-setup: specifying fixed revisions causes spurious update | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Clayton Casciato <ccasciato> |
| Component: | bitbake | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | alex.kanavin, poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | 6.0 | ||
| Target Milestone: | 6.0 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Clayton Casciato
2026-03-05 02:48:57 UTC
Hi, Alexander This appears to resolve the unexpected behavior. Using a new Setup, I tested the following revision changes: fixed -> fixed -> branch -> equivalent fixed Thank you! Hello Clayton, thanks for testing. Can you also check the v2 please? https://patchwork.yoctoproject.org/project/bitbake/list/?series=44205 v2 looks good. Test sequence: init with branch -> fixed -> fixed -> equivalent branch Merged into bitbake master. Thanks! |