Bug 13567 - Add QA check for recipes that use AUTOREV by default
Summary: Add QA check for recipes that use AUTOREV by default
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 5.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-10-02 17:51 UTC by Joshua Watt
Modified: 2026-01-07 21:11 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Watt 2019-10-02 17:51:15 UTC 
Recipes should not be using AUTOREV by default since it causes problems for reprodibibilty and security (see https://lists.yoctoproject.org/pipermail/yocto/2019-June/045574.html).

Adding an (optional) QA check to ensure that all recipes built are not using AUTOREV can help detect these recipes and configurations. Additionally, we may want to consider making this QA check enabled by default in reproducible_build.bbclass, since AUTOREV and reproducibility are not compatible.
Comment 1 Ross Burton 2019-10-03 12:33:23 UTC 
I'm not sure why this would be a QA check: you can't accidentally use autorev and if a distro is using it then they did so out of choice.

Maybe reproducible.bbclass should just throw a qa error itself if autorev is enabled?
Comment 2 Randy MacLeod 2023-10-24 14:24:23 UTC 
Bulk move from 4.99 or 0.00 to 5.99