Bug 15815 - patchtest should warn if git SRC_URI doesn't have a tag=
Summary: patchtest should warn if git SRC_URI doesn't have a tag=
Status: NEW
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest Testsuite (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.1
Assignee: Trevor Gamblin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2025-03-26 17:29 UTC by Ross Burton
Modified: 2026-03-12 15:20 UTC (History)
1 user (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 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.