Bug 10410

Summary: Solve conflict on python-unidiff v1 recipe
Product: [Yocto Project Subprojects] Patchwork/Patchtest Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: Patchtest TestsuiteAssignee: Daniela Plascencia <daniela.plascencia>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: mhalstead
Version: 2.2   
Target Milestone: 2.2 M4   
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-10-11 15:25:07 UTC 
We need a working recipe defining the python unidiff module [1]. There is one v1 sent to the oe-devel list but apparently, it conflicts with other python module [2]. We need to create a v2 recipe, include it into meta-patchtest layer,  create a new image base on it and launch pt-cronjob to test it. Once all testing is done, v2 recipe should be sent to the oe-devel list.

This recipe is not part of oe-core but because we heavily used it in the test-suite, I find convenient to file a bug.

[1] https://github.com/matiasb/python-unidiff
[2] http://lists.openembedded.org/pipermail/openembedded-devel/2016-September/109088.html
Comment 1 Leonardo Sandoval Gonzalez 2016-10-19 14:00:48 UTC 
Patch is ready (and ACK by Tim Orling) but pending to be sent to the mailing list. This is on track and should be finished before 2.2 release.