Deluge
Code: Select all
maximax glade # emerge -v deluge
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] net-p2p/deluge-1.0.2 [1.0.0] USE="gtk" 0 kB [0=>1]
Total: 1 package (1 upgrade), Size of downloads: 0 kB
Portage tree and overlays:
[0] /usr/portage
[1] /usr/local/portage
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) net-p2p/deluge-1.0.2
* deluge-1.0.2.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking deluge-1.0.2.tar.gz to /var/tmp/portage/net-p2p/deluge-1.0.2/work
* Applying setup.patch ...
* Failed Patch: setup.patch !
* ( /usr/local/portage/net-p2p/deluge/files/setup.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-7377.out
*
* ERROR: net-p2p/deluge-1.0.2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2707: Called epatch '/usr/local/portage/net-p2p/deluge/files/setup.patch'
* environment, line 1396: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
* The die message:
* Failed Patch: setup.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/net-p2p/deluge-1.0.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-p2p/deluge-1.0.2/temp/environment'.
* This ebuild is from an overlay: '/usr/local/portage/'
*
>>> Failed to emerge net-p2p/deluge-1.0.2, Log file:
>>> '/var/tmp/portage/net-p2p/deluge-1.0.2/temp/build.log'
* GNU info directory index is up-to-date.Code: Select all
maximax glade # cat /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-7377.out
***** setup.patch *****
=======================
PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/net-p2p/deluge/files/setup.patch
=======================
patching file setup.py
Hunk #1 FAILED at 51.
Hunk #2 FAILED at 304.
2 out of 2 hunks FAILED -- saving rejects to file setup.py.rej
=======================
PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/net-p2p/deluge/files/setup.patch
=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig 2008-07-15 14:54:35.000000000 +0200
|+++ setup.py 2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
=======================
PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/net-p2p/deluge/files/setup.patch
=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig 2008-07-15 14:54:35.000000000 +0200
|+++ setup.py 2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
=======================
PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/net-p2p/deluge/files/setup.patch
=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig 2008-07-15 14:54:35.000000000 +0200
|+++ setup.py 2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
=======================
PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/net-p2p/deluge/files/setup.patch
=======================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- setup.py.orig 2008-07-15 14:54:35.000000000 +0200
|+++ setup.py 2008-07-15 14:54:57.000000000 +0200
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
Code: Select all
maximax glade # cat /var/tmp/portage/net-p2p/deluge-1.0.2/temp/build.log
>>> Unpacking source...
>>> Unpacking deluge-1.0.2.tar.gz to /var/tmp/portage/net-p2p/deluge-1.0.2/work
* Applying setup.patch ...
* Failed Patch: setup.patch !
* ( /usr/local/portage/net-p2p/deluge/files/setup.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/net-p2p/deluge-1.0.2/temp/setup.patch-7377.out
*
* ERROR: net-p2p/deluge-1.0.2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2707: Called epatch '/usr/local/portage/net-p2p/deluge/files/setup.patch'
* environment, line 1396: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
* The die message:
* Failed Patch: setup.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/net-p2p/deluge-1.0.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-p2p/deluge-1.0.2/temp/environment'.
* This ebuild is from an overlay: '/usr/local/portage/'
* What is the problem?
Thanks in advance.