Summary: | kde-base/kdelibs-4.1.3-r1: patch failure during emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nick Baird <gentoo> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output from failed patch log |
Description
Nick Baird
2008-11-12 16:46:53 UTC
Created attachment 171560 [details]
Output from failed patch log
This is already fixed, try syncing your tree again... Reopen if still issue. (In reply to comment #2) > This is already fixed, try syncing your tree again... > Reopen if still issue. > I tried syncing and emerging again both yesterday and today, and I still have the same problem. The ebuild according to my portage tree is still -r1. Did it get a version bump with the fix? Maybe the mirror I use is not up to date. (In reply to comment #2) > This is already fixed, try syncing your tree again... > Reopen if still issue. > I tried syncing and emerging again both yesterday and today, and I still have the same problem. The ebuild according to my portage tree is still -r1. Did it get a version bump with the fix? Maybe the mirror I use is not up to date. I synced again today and I still have the problem. The kdelibs-4.1.3-r1.ebuild contains the following: PATCHES=( "${FILESDIR}/${PN}-4.1.1-cmake-modules.patch" "${FILESDIR}/${PV}-cmake-confe-config.patch" ) but the patch command is failing per the attached log file. Well, this is puzzling. All we can say is that this seems to be a local problem as we had many people testing the patch and it applied to all of them. Reopen the bug if you can duplicate it on another box or if anyone else hits it. (In reply to comment #6) > Well, this is puzzling. All we can say is that this seems to be a local problem > as we had many people testing the patch and it applied to all of them. > Reopen the bug if you can duplicate it on another box or if anyone else hits > it. > I'm having exactly the same problems here, on another box. Try to update your base system. It looks like some problem with epatch (my personal opinion). emerge -NvD system (In reply to comment #5) > I synced again today and I still have the problem. The kdelibs-4.1.3-r1.ebuild > contains the following: > > PATCHES=( "${FILESDIR}/${PN}-4.1.1-cmake-modules.patch" > "${FILESDIR}/${PV}-cmake-confe-config.patch" ) > > but the patch command is failing per the attached log file. > Try syncing your kde-testing overlay... The strange thing is, that I only have this kind of problems with some of the kde 4.1.3 packages, anything else works. Everything worked as I did an "emerge -u --deep world" except of the kde 4.1.3 packages, but I will try it. (In reply to comment #9) > (In reply to comment #5) > > I synced again today and I still have the problem. The kdelibs-4.1.3-r1.ebuild > > contains the following: > > > > PATCHES=( "${FILESDIR}/${PN}-4.1.1-cmake-modules.patch" > > "${FILESDIR}/${PV}-cmake-confe-config.patch" ) > > > > but the patch command is failing per the attached log file. > > > > Try syncing your kde-testing overlay... > > Syncing my kde-testing overlay did work for me - thanks. |