View previous topic :: View next topic |
Author |
Message |
Punchcutter Guru
Joined: 11 Feb 2007 Posts: 354
|
Posted: Tue Jun 11, 2013 2:20 am Post subject: kde-sunset: bad patch kdelibs-3.5.10-kde4-apps.patch |
|
|
Hi all..... trying to install a new machine with partial KDE3.5 environment via kde-sunset overlay, but run into the following when building kdelibs. Anyone have any clues that might help me? In spite of the given advice ("you need to fix the relative paths in patch"), delving into the patch and trying to fix it myself would not be the first thing I would try to do Thanks in advance for any help.
Code: | * Applying kdelibs-3.5.10-kde4-apps.patch ...
* Rejected Patch: kdelibs-3.5.10-kde4-apps.patch !
* ( /var/lib/layman/kde-sunset/kde-base/kdelibs/files/kdelibs-3.5.10-kde4-apps.patch )
*
* Your patch uses relative paths '../':
* 3:+++ ../kdelibs-new/kio/kio/kservice.cpp 2009-05-21 01:53:22.000000000 +0200
* ERROR: kde-base/kdelibs-3.5.10-r10 failed (unpack phase):
* you need to fix the relative paths in patch
*
* Call stack:
* ebuild.sh, line 93: Called src_unpack
* environment, line 4701: Called epatch '/var/lib/layman/kde-sunset/kde-base/kdelibs/files/kdelibs-3.5.10-kde4-apps.patch'
* environment, line 2309: Called die
* The specific snippet of code:
* die "you need to fix the relative paths in patch";
*
* If you need support, post the output of `emerge --info '=kde-base/kdelibs-3.5.10-r10'`,
* the complete build log and the output of `emerge -pqv '=kde-base/kdelibs-3.5.10-r10'`.
* This ebuild used the following eclasses from overlays:
* /var/lib/layman/kde-sunset/eclass/kde.eclass
* /var/lib/layman/kde-sunset/eclass/kde-functions.eclass
* /var/lib/layman/kde-sunset/eclass/qt3.eclass
* This ebuild is from an overlay named 'kde-sunset': '/var/lib/layman/kde-sunset/'
* The complete build log is located at '/var/tmp/portage/kde-base/kdelibs-3.5.10-r10/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/kde-base/kdelibs-3.5.10-r10/temp/environment'.
* Working directory: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r10/work/kdelibs-3.5.10'
* S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r10/work/kdelibs-3.5.10'
>>> Failed to emerge kde-base/kdelibs-3.5.10-r10, Log file:
|
|
|
Back to top |
|
|
basiaf n00b
Joined: 25 Feb 2005 Posts: 44 Location: Dortmund
|
Posted: Tue Jun 11, 2013 9:16 pm Post subject: |
|
|
you can change the file /var/lib/layman/kde-sunset/kde-base/kdelibs/files/kdelibs-3.5.10-kde4-apps.patch from
Code: | --- ./kio/kio/kservice.cpp 2008-02-13 10:41:06.000000000 +0100
+++ ../kdelibs-new/kio/kio/kservice.cpp 2009-05-21 01:53:22.000000000 +0200
|
to
Code: | --- kio/kio/kservice.cpp 2008-02-13 10:41:06.000000000 +0100
+++ kio/kio/kservice.cpp 2009-05-21 01:53:22.000000000 +0200 |
and remanifest
Code: | ebuild kdelibs-3.5.10-r10.ebuild digest |
to keep the changes make a copy in a local overlay, otherwise they will be lost on next layman sync. |
|
Back to top |
|
|
Punchcutter Guru
Joined: 11 Feb 2007 Posts: 354
|
Posted: Wed Jun 12, 2013 8:50 am Post subject: |
|
|
Thanks! This is very helpful advice. I think I can handle it, but... can you remind me how to "remanifest"? |
|
Back to top |
|
|
basiaf n00b
Joined: 25 Feb 2005 Posts: 44 Location: Dortmund
|
Posted: Wed Jun 12, 2013 12:45 pm Post subject: |
|
|
just run this in the directory the ebuild lies in (e.g. /var/lib/layman/kde-sunset/kde-base/kdelibs)
basiaf wrote: |
Code: | ebuild kdelibs-3.5.10-r10.ebuild digest |
|
|
|
Back to top |
|
|
Punchcutter Guru
Joined: 11 Feb 2007 Posts: 354
|
Posted: Wed Jun 12, 2013 7:30 pm Post subject: |
|
|
Gah.... somehow my eyes failed to see your original code snippet about the ebuild command... in that case just smack me and say: I already told you
So.... anyway, I thought that I could create a new "fixed" ebuild of this under my /usr/local/portage local overlay, and have portage find the new ebuild there, but the remanifest failed with an error. I guess because nothing else from KDE 3.5 is in that directory. So my /usr/local/portage copy now serves as a backup, but what if I wanted to force portage to use that one instead of the one from the main tree? Is that possible, or even desirable?
Well, kdelibs is now building happily along, so thanks again |
|
Back to top |
|
|
|