Bug 15815

Summary: patchtest should warn if git SRC_URI doesn't have a tag=
Product: [Yocto Project Subprojects] Patchwork/Patchtest Reporter: Ross Burton <ross.burton>
Component: Patchtest TestsuiteAssignee: Trevor Gamblin <tgamblin>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: randy.macleod
Version: unspecified   
Target Milestone: 6.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Ross Burton 2025-03-26 17:29:52 UTC 
As of a few days ago, the behaviour of tag= in SRC_URIs with git repositories has changed.  Now, if tag= is set in the SRC_URI and SRCREV is set, bitbake will verify that the tag name matches the SRCREV.

This is good as it stops people having a recipe that eg claims to be v1.2 in PV and comments, but the SRCREV is actually 1.2+malicious or similar.

Somehow, patchtest should identify if this behaviour isn't being set.

Some thoughts:
- Limit to upgrades so that it doesn't trigger on patches that touch recipe
- Something along the lines of: if SRC_URI has git:// repository without a tag= and PV doesn't contain +git, fail.