* Applying 4405_alpha-sysctl-uac.patch (-p0+) ... [ ok ] * Applying 4450_grsec-2.1.10-2.6.20.6-200704091818.patch (-p0+) ... [ !! ] * Please attach /var/tmp/portage/sys-kernel/hardened-sources-2.6.20-r3/temp/4450_grsec-2.1.10-2.6.20.6-200704091818.err to any bug you may post. !!! ERROR: sys-kernel/hardened-sources-2.6.20-r3 failed. Call stack: ebuild.sh, line 1614: Called dyn_unpack ebuild.sh, line 751: Called qa_call 'src_unpack' environment, line 3891: Called src_unpack ebuild.sh, line 1304: Called kernel-2_src_unpack kernel-2.eclass, line 1008: Called unipatch ' /var/tmp/portage/sys-kernel/hardened-sources-2.6.20-r3/distdir/genpatches-2.6.20-10.base.tar.bz2 /var/tmp/portage/sys-kernel/hardened-sources-2.6.20-r3/distdir/hardened-patches-2.6.20-4.extras.tar.bz2' kernel-2.eclass, line 851: Called die !!! Unable to dry-run patch. !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/log/portage/sys-kernel:hardened-sources-2.6.20-r3:20070515-165552.log'. Reproducible: Always
Created attachment 119379 [details] /var/tmp/portage/sys-kernel/hardened-sources-2.6.20-r3/temp/4450_grsec-2.1.10-2.6.20.6-200704091818.err And BTW... thank you for the revbump to -r3 (including 2.6.20.11). I know 2.6.21 is out and so the interest follows but I really appreciate you guys taking the time to bump 2.6.20 to latest -stable.
(In reply to comment #1) > Created an attachment (id=119379) [edit] > /var/tmp/portage/sys-kernel/hardened-sources-2.6.20-r3/temp/4450_grsec-2.1.10-2.6.20.6-200704091818.err > > > And BTW... thank you for the revbump to -r3 (including 2.6.20.11). I know > 2.6.21 is out and so the interest follows but I really appreciate you guys > taking the time to bump 2.6.20 to latest -stable. Well, I found out why it was failing .. *shrug* .11 introduced a change to arch/sparc64/kernel/pci_iommu.c which is also touched by the grsecurity patch. And that's why it broke; Just uploaded a fresh patch-tarball and updated the ebuild. Once that has mirrored out, please retry it.
Thanks! Merges just fine now. Won't have a chance to actually try it tonight but that is irrelevant here. This bug is resolved, close at your discretion.
(In reply to comment #3) > Thanks! Merges just fine now. Won't have a chance to actually try it tonight > but that is irrelevant here. This bug is resolved, close at your discretion. You're welcome, it works just fine; at least for me.
