9249 2016-03-14 15:05:53 +0000 patchwork: test that CVE patches contain the proper formatting 2017-12-06 16:52:16 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork 2.2 x86 Multiple RESOLVED FIXED Medium+ normal 2.2 M2 1 leonardo.sandoval.gonzalez mariano.lopez alejandro.franco jose.perez.carranza mariano.lopez --- --- No (bug/feature does not impact docs) oldest_to_newest 59941 0 leonardo.sandoval.gonzalez 2016-03-14 15:05:53 +0000 CVE patchtes sent to the openembedded mailing list should be tested with patchtest/patchwork for proper format. Proper format at least means indicating the CVE number in the summary and the string 'CVE: CVE-<number>' in the patch description area. An example for correct formatting would be http://patchwork.openembedded.org/patch/117791/ 59946 1 leonardo.sandoval.gonzalez 2016-03-14 17:09:53 +0000 A link that shows how to create a CVE patch: http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#CVE_Patches 62962 2 leonardo.sandoval.gonzalez 2016-06-14 14:14:42 +0000 Expected to be finished early 2.2M2. 63309 3 leonardo.sandoval.gonzalez 2016-06-23 19:51:52 +0000 My fault, moving it to M1 again. CCB should agree on any milestone movement. 63556 4 leonardo.sandoval.gonzalez 2016-06-30 20:31:51 +0000 This is already implemented but not tested. 63787 5 mariano.lopez 2016-07-11 13:19:26 +0000 Sent patches to Leo 64278 6 leonardo.sandoval.gonzalez 2016-07-21 16:34:36 +0000 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