* Applying 1000_linux-2.6.34.1.patch (-p0+) ... [ ok ] * Applying 2700_nouveau-acpi-lid-open-undefined-fix.patch (-p0+) ... [ ok ] * Applying 2720_vgarrb-add-missing-define.patch (-p0+) ... [ ok ] * Applying 2900_xconfig-with-qt4.patch (-p0+) ... [ ok ] * Applying 4200_fbcondecor-0.9.6.patch (-p0+) ... [ ok ] * Applying patch-2.6.34-ck1.patch (-p0+) ... [ !! ] * Please attach /var/tmp/portage/sys-kernel/ck-sources-2.6.34-r2/temp/patch-2.6.34-ck1.err to any bug you may post. emerge -pqv sys-kernel/ck-sources-2.6.34-r2 [ebuild NS ] sys-kernel/ck-sources-2.6.34-r2 [2.6.34-r1] USE="-build -deblob -symlink" Reproducible: Always
Created attachment 238617 [details] build.log
Created attachment 238619 [details] patch-2.6.34-ck1.err
Created attachment 238621 [details] emerge --info =sys-kernel/ck-sources-2.6.34-r2
*** Bug 328101 has been marked as a duplicate of this bug. ***
This fails due to changes made by 2.6.34.1, so I'm going to remove sys-kernel/ck-sources-2.6.34-r2 and wait for ck2.
(In reply to comment #5) > This fails due to changes made by 2.6.34.1, so I'm going to remove > sys-kernel/ck-sources-2.6.34-r2 and wait for ck2. > Yes,I've masked it,too.But ck-sources-2.6.34-r2 == linux-2.6.34.1 ??? It seems ck-sources-2.6.34-r2.ebuild using the same linux-kernel,which ck-sources-2.6.34-r1.ebuild used,is it?
ck-sources-2.6.34-r2 uses genpatches 4 for 2.6.34 which includes patch 2.6.34.1.
(In reply to comment #7) > ck-sources-2.6.34-r2 uses genpatches 4 for 2.6.34 which includes patch > 2.6.34.1. > If I rename ck-sources-2.6.34-r2.ebuild to ck-sources-2.6.34.1-r2.ebuild,Is it feasible ?
patch-2.6.34.1.bz2 causes the error, to be precise: both patches: 2.6.34.1 and ck1 touch the same files (same contexts). So renaming the ebuild won't do anything, I don't see what you want to achieve with this rename anyway. Let's wait for ck2.
(In reply to comment #9) > patch-2.6.34.1.bz2 causes the error, to be precise: both patches: 2.6.34.1 and > ck1 touch the same files (same contexts). So renaming the ebuild won't do > anything, I don't see what you want to achieve with this rename anyway. Let's > wait for ck2. > all right,thanks a lot,man.>_<. Good night..(China)