| Summary: | patchwork: test that CVE patches contain the proper formatting | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Component: | Patchwork | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | alejandro.franco, jose.perez.carranza, mariano.lopez |
| Version: | 2.2 | ||
| Target Milestone: | 2.2 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Leonardo Sandoval Gonzalez
2016-03-14 15:05:53 UTC
A link that shows how to create a CVE patch: http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#CVE_Patches Expected to be finished early 2.2M2. My fault, moving it to M1 again. CCB should agree on any milestone movement. This is already implemented but not tested. Sent patches to Leo This check is already implemented on the patchtest-oe suite. The way to validate this check is through 'selftest' implemented on patchtest-oe repo
+ clone patchtest and patchtest-oe (right now these are not public), follow patchtest-oe setup instructions
+ run the following cmd:
cd $patchtest-oe/selftest; ./selftest
+ expected output: no output should be seen on console
|