Bug 11432 - patchtest-oe: detect patches being added without modifying SRC_URI
Summary: patchtest-oe: detect patches being added without modifying SRC_URI
Status: RESOLVED DUPLICATE of bug 13005
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest Testsuite (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 4.99
Assignee: Anuj Mittal
QA Contact:
URL:
Whiteboard:
: 11601 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-04-28 02:36 UTC by Paul Eggleton
Modified: 2019-03-05 10:18 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

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 Paul Eggleton 2017-04-28 02:36:54 UTC 
During this release we had a CVE fix go in but the commit only added the patch but didn't add the patch to SRC_URI in order to ensure it got applied:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3a769fce06180012803da863598b03e611227783

It does appear that this was a mistake in the original submission rather than something that happened between the submission and the patch merging. We need to  detect where a patch file is being added but no corresponding change to a SRC_URI value is being made in a recipe or an inc file.
Comment 1 Daniela Plascencia 2017-08-17 20:38:59 UTC 
Moving to M4 waiting for an execution error (bitbake/tinfoil related) to be solved.
Comment 2 Daniela Plascencia 2017-10-02 15:45:14 UTC 
Moving to 2.5 M1, I'll work on enhancements on such milestone.
Comment 4 Leonardo Sandoval Gonzalez 2017-11-28 17:13:13 UTC 
There was a false positive thus commit was reverted.
Comment 5 Leonardo Sandoval Gonzalez 2017-11-28 17:14:07 UTC 
*** Bug 11601 has been marked as a duplicate of this bug. ***
Comment 6 Anuj Mittal 2019-03-05 10:18:05 UTC 
Duplicate and Changqing Li has fix for 13005.

*** This bug has been marked as a duplicate of bug 13005 ***