Bug 10410 - Solve conflict on python-unidiff v1 recipe
Summary: Solve conflict on python-unidiff v1 recipe
Status: RESOLVED FIXED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest Testsuite (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.2 M4
Assignee: Daniela Plascencia
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-10-11 15:25 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-12-06 17:12 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 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.