Summary: | kernel-2.eclass v1.277 : Algo for determining PATCH_DEPTH goes wrong when all diffs in a patch file refer to /dev/null | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eric F. GARIOUD <eric-f.garioud> |
Component: | Eclasses | Assignee: | Gentoo Kernel Miscellaneous <kernel-misc> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
TEST-CASE-ONLY : ebuild example to reproduce the problem
TEST-CASE : Example of patch inappropriatly patched p0 |
Description
Eric F. GARIOUD
2012-09-27 16:57:34 UTC
In the description above, please read PATCH_DEPTH instead of PATCH_LEVEL. Apologizes. Any reproducible steps so I can see it live? Created attachment 325324 [details]
TEST-CASE-ONLY : ebuild example to reproduce the problem
Ebuild for reproducing the problem which will occur with the ${XPR_2_FILE} patch.
Please set the "experimental" and "urwlocks" use flags.
Created attachment 325328 [details]
TEST-CASE : Example of patch inappropriatly patched p0
TEST-CASE-ONLY : Example of file the algo will incorrectly patch -p0
Used as ${XPR_2_FILE} in the ebuild attached.
(In reply to comment #2) > Any reproducible steps so I can see it live? And, by the way, if you want to actually *see* something, then you are likely to add some code within the unipatch() procedure that will incidentally satisfy the enhancement request I made as part of Bug 436402, so... please... do not clean all your traces after having seen... ;-) OK, having read the eclass more... carefully, I realize that the initial value for PATCH_DEPTH can be specified as part of the UNIPATCH_LIST string. I apologize for the noise. |