Bug 472348

Summary:	kde-base/kig-4.10.4 Failed Patch: kig-4.10.0-boostpython.patch
Product:	Gentoo Linux	Reporter:	Frank Krömmelbein <kroemmelbein>
Component:	[OLD] KDE	Assignee:	Gentoo KDE team <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	andre.reinke, doug.hunley, gentoo, idoerg, Martin.vGagern, proteuss, zeekec
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	kig-4.10.4-patch kig-4.10.4.ebuild

Description Frank Krömmelbein 2013-06-04 22:56:32 UTC

>>> Emerging (1 of 1) kde-base/kig-4.10.4
 * kig-4.10.4.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                              [ ok ]
>>> Unpacking source...
>>> Unpacking kig-4.10.4.tar.xz to /var/tmp/portage/kde-base/kig-4.10.4/work
>>> Source unpacked in /var/tmp/portage/kde-base/kig-4.10.4/work
>>> Preparing source in /var/tmp/portage/kde-base/kig-4.10.4/work/kig-4.10.4 ...
 * Applying kig-4.10.0-boostpython.patch ...

 * Failed Patch: kig-4.10.0-boostpython.patch !
 *  ( /usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/kde-base/kig-4.10.4/temp/kig-4.10.0-boostpython.patch.out

 * ERROR: kde-base/kig-4.10.4 failed (prepare phase):
 *   Failed Patch: kig-4.10.0-boostpython.patch!
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 3935:  Called kde4-base_src_prepare
 *   environment, line 3040:  Called base_src_prepare
 *   environment, line  944:  Called epatch '/usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch'
 *   environment, line 1925:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=kde-base/kig-4.10.4'`,
 * the complete build log and the output of `emerge -pqv '=kde-base/kig-4.10.4'`.
 * The complete build log is located at '/var/tmp/portage/kde-base/kig-4.10.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/kig-4.10.4/temp/environment'.
 * Working directory: '/var/tmp/portage/kde-base/kig-4.10.4/work/kig-4.10.4'
 * S: '/var/tmp/portage/kde-base/kig-4.10.4/work/kig-4.10.4'

>>> Failed to emerge kde-base/kig-4.10.4, Log file:




content of:
/var/tmp/portage/kde-base/kig-4.10.4/temp/kig-4.10.0-boostpython.patch.out




***** kig-4.10.0-boostpython.patch *****
PWD: /var/tmp/portage/kde-base/kig-4.10.4/work/kig-4.10.4

========================================

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch  < '/usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch'

========================================
patching file CMakeLists.txt
Hunk #2 FAILED at 27.
Hunk #3 succeeded at 41 (offset -1 lines).
Hunk #4 succeeded at 179 with fuzz 2 (offset 6 lines).
Hunk #5 succeeded at 190 (offset 7 lines).
1 out of 5 hunks FAILED -- saving rejects to file CMakeLists.txt.rej
patching file KigConfigureChecks.cmake
patching file cmake/COPYING-CMAKE-SCRIPTS
patching file cmake/FindBoostPython.cmake
Hunk #1 FAILED at 1.
File cmake/FindBoostPython.cmake is not empty after patch, as expected
1 out of 1 hunk FAILED -- saving rejects to file cmake/FindBoostPython.cmake.rej
patching file cmake/modules/FindBoostPython.cmake

patch program exited with status 1
========================================

PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch  < '/usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch'

========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git CMakeLists.txt CMakeLists.txt
|index aa4cc11..647a270 100644
|--- CMakeLists.txt
|+++ CMakeLists.txt
--------------------------
No file to patch.  Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git KigConfigureChecks.cmake KigConfigureChecks.cmake
|index fed38b3..a53ea73 100644
|--- KigConfigureChecks.cmake
|+++ KigConfigureChecks.cmake
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
The next patch would delete the file COPYING-CMAKE-SCRIPTS,
which does not exist!  Applying it anyway.
patching file COPYING-CMAKE-SCRIPTS
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file COPYING-CMAKE-SCRIPTS.rej
The next patch would delete the file FindBoostPython.cmake,
which does not exist!  Applying it anyway.
patching file FindBoostPython.cmake
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file FindBoostPython.cmake.rej
The next patch would delete the file modules/FindBoostPython.cmake,
which does not exist!  Applying it anyway.
patching file modules/FindBoostPython.cmake
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file modules/FindBoostPython.cmake.rej

patch program exited with status 1
========================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  < '/usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch'

========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git CMakeLists.txt CMakeLists.txt
|index aa4cc11..647a270 100644
|--- CMakeLists.txt
|+++ CMakeLists.txt
--------------------------
No file to patch.  Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git KigConfigureChecks.cmake KigConfigureChecks.cmake
|index fed38b3..a53ea73 100644
|--- KigConfigureChecks.cmake
|+++ KigConfigureChecks.cmake
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 111
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/COPYING-CMAKE-SCRIPTS cmake/COPYING-CMAKE-SCRIPTS
|deleted file mode 100644
|index 4b41776..0000000
|--- cmake/COPYING-CMAKE-SCRIPTS
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 139
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/FindBoostPython.cmake cmake/FindBoostPython.cmake
|deleted file mode 100644
|index 6d5f05e..0000000
|--- cmake/FindBoostPython.cmake
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file FindBoostPython.cmake,
which does not exist!  Applying it anyway.
patching file FindBoostPython.cmake
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file FindBoostPython.cmake.rej

patch program exited with status 1
========================================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch  < '/usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch'

========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git CMakeLists.txt CMakeLists.txt
|index aa4cc11..647a270 100644
|--- CMakeLists.txt
|+++ CMakeLists.txt
--------------------------
No file to patch.  Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git KigConfigureChecks.cmake KigConfigureChecks.cmake
|index fed38b3..a53ea73 100644
|--- KigConfigureChecks.cmake
|+++ KigConfigureChecks.cmake
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 111
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/COPYING-CMAKE-SCRIPTS cmake/COPYING-CMAKE-SCRIPTS
|deleted file mode 100644
|index 4b41776..0000000
|--- cmake/COPYING-CMAKE-SCRIPTS
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 139
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/FindBoostPython.cmake cmake/FindBoostPython.cmake
|deleted file mode 100644
|index 6d5f05e..0000000
|--- cmake/FindBoostPython.cmake
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 298
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/modules/FindBoostPython.cmake cmake/modules/FindBoostPython.cmake
|deleted file mode 100644
|index 72aae54..0000000
|--- cmake/modules/FindBoostPython.cmake
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

patch program exited with status 1
========================================

PATCH COMMAND:  patch -p4 -g0 -E --no-backup-if-mismatch  < '/usr/portage/kde-base/kig/files/kig-4.10.0-boostpython.patch'

========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git CMakeLists.txt CMakeLists.txt
|index aa4cc11..647a270 100644
|--- CMakeLists.txt
|+++ CMakeLists.txt
--------------------------
No file to patch.  Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 88
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git KigConfigureChecks.cmake KigConfigureChecks.cmake
|index fed38b3..a53ea73 100644
|--- KigConfigureChecks.cmake
|+++ KigConfigureChecks.cmake
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 111
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/COPYING-CMAKE-SCRIPTS cmake/COPYING-CMAKE-SCRIPTS
|deleted file mode 100644
|index 4b41776..0000000
|--- cmake/COPYING-CMAKE-SCRIPTS
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 139
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/FindBoostPython.cmake cmake/FindBoostPython.cmake
|deleted file mode 100644
|index 6d5f05e..0000000
|--- cmake/FindBoostPython.cmake
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 298
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git cmake/modules/FindBoostPython.cmake cmake/modules/FindBoostPython.cmake
|deleted file mode 100644
|index 72aae54..0000000
|--- cmake/modules/FindBoostPython.cmake
|+++ /dev/null
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

patch program exited with status 1



Reproducible: Always

Comment 1 Brian Pack 2013-06-05 09:27:11 UTC

Emerge of kig fails immediately with "Failed Patch: kig-4.10.0-boostpython.patch!" on my Core i3 laptop.

Comment 2 h0t 2013-06-05 09:27:59 UTC

Created attachment 350194 [details, diff]
kig-4.10.4-patch

Comment 3 h0t 2013-06-05 09:29:56 UTC

Created attachment 350196 [details, diff]
kig-4.10.4.ebuild

Comment 4 h0t 2013-06-05 09:32:36 UTC

It's problem in CMakeLists.txt. I solved it so:
1. create new patch kig-4.10.4-boostpython.path
2. change kig-4.10.4-ebuild 

(see attachments)

Comment 5 Evgeny Bobkin 2013-06-05 11:47:07 UTC

I hit the same issue

Comment 6 Andreas Proteus 2013-06-05 12:41:05 UTC

(In reply to h0t from comment #4)
Patch and ebuild worked here.
Thank you.

Comment 7 Andre Reinke 2013-06-05 17:29:52 UTC

Same issue over here. Patch provided by h0t solves the issue. Thanks!

Comment 8 Andreas K. Hüttel archtester

2013-06-05 20:20:50 UTC

Thanks. Should be fixed, sync in some hours.

Comment 9 Ben Kohler gentoo-dev

2013-06-05 23:12:41 UTC

*** Bug 472446 has been marked as a duplicate of this bug. ***