| Summary: | usermode-sources-2.6.12-r2.ebuild (update) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Karl H <karl> |
| Component: | New packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | karl, wh7kfbv02 |
| Priority: | Highest | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
updated ebuild for usermode-sources-2.6.12-r2.ebuild
testcase of boot usermode-sources-2.6.12-r2.ebuild (update) usermode-sources-2.6.12-r3.ebuild (add K_GENPATCHES_VER="13" and UNIPATCH_EXCLUDE="1003_linux-2.6.12.3.patch") |
||
|
Description
Karl H
2005-08-19 12:37:28 UTC
Created attachment 66341 [details]
updated ebuild for usermode-sources-2.6.12-r2.ebuild
Created attachment 66342 [details]
testcase of boot usermode-sources-2.6.12-r2.ebuild (update)
We should update to the latest genpatches for security reasons too. How about if you change this line: K_GENPATCHES_VER="8" to: K_GENPATCHES_VER="13" This will probably cause a patch collision in 2.6.12.3, in which case you can add this line directly below: UNIPATCH_EXCLUDE="1003_linux-2.6.12.3.patch" Excluding the whole 2.6.12.3 isn't ideal, but its the best we can easily achieve. Yes, 2.6.12.3 causes a colision with the uml-2.6.12-bs11 patch set. The UNIPATCH_EXCLUDE="1003_linux-2.6.12.3.patch" makes it apply cleany, not ideal but makes it work. I will post the new ebuild attachment with the change. Created attachment 66538 [details]
usermode-sources-2.6.12-r3.ebuild (add K_GENPATCHES_VER="13" and UNIPATCH_EXCLUDE="1003_linux-2.6.12.3.patch")
Thanks for testing that. Committed to CVS. For 2.6.13 and onwards we'll have a better way to exclude conflicting patches. |