kdelibs fail to (re)install because of a patch failing now. Some time ago it built and installed fine. >>> Emerging (1 of 1) kde-base/kdelibs-4.1.2-r1 * kdelibs-4.1.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking kdelibs-4.1.2.tar.bz2 to /var/tmp/portage/kde-base/kdelibs-4.1.2-r1/work * Applying kdelibs-4.1.1-cmake-modules.patch ... [ ok ] >>> Source unpacked. * Applying kdelibs-4.1.1-cmake-modules.patch ... * Failed Patch: kdelibs-4.1.1-cmake-modules.patch ! * ( /usr/portage/kde-base/kdelibs/files/kdelibs-4.1.1-cmake-modules.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/kde-base/kdelibs-4.1.2-r1/temp/kdelibs-4.1.1-cmake-modules.patch-914210.out * * ERROR: kde-base/kdelibs-4.1.2-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_prepare * environment, line 3215: Called base_src_prepare * environment, line 439: Called base_src_util 'autopatch' * environment, line 486: Called epatch '/usr/portage/kde-base/kdelibs/files/kdelibs-4.1.1-cmake-modules.patch' * environment, line 1628: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: kdelibs-4.1.1-cmake-modules.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-base/kdelibs-4.1.2-r1/temp/environment'. *
Created attachment 171230 [details] .out patch error file /var/tmp/portage/kde-base/kdelibs-4.1.2-r1/temp/kdelibs-4.1.1-cmake-modules.patch-914210.out
Created attachment 171232 [details] emerge --info emerge --info
I have now exactly the same problem with 4.1.3. (I skipped 4.1.2-r1)
Same here with kde-base/kdelibs-4.1.3!
I had the same issues with the 4.1.3 update. Removing "kde-testing" overlay helped.
Sorry. This was a problem with eclass not with kde-testing, so you can add it back. There was update which i missed so every ebuild using kde4-base.eclass was failing on patching. Once again sorry for inconvinience.
