emerge soappy-0.11.6-r1 failes with: ================================================== <snip> >>> Unpacking source... >>> Unpacking SOAPpy-0.11.6.tar.gz to /var/tmp/portage/soappy-0.11.6-r1/work * Applying soappy-0.11.6-future-imports.patch ... * Failed Patch: soappy-0.11.6-future-imports.patch ! * ( /usr/portage/dev-python/soappy/files/soappy-0.11.6-future-imports.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/soappy-0.11.6-r1/temp/soappy-0.11.6-future-imports.patch-1 3329.out !!! ERROR: dev-python/soappy-0.11.6-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_unpack ebuild.sh, line 708: Called src_unpack soappy-0.11.6-r1.ebuild, line 29: Called epatch '/usr/portage/dev-python/soa ppy/files/soappy-0.11.6-future-imports.patch' eutils.eclass, line 341: Called die !!! Failed Patch: soappy-0.11.6-future-imports.patch! !!! If you need support, post the topmost build error, and the call stack if rel evant. ================================================== cat /var/tmp/portage/soappy-0.11.6-r1/temp/soappy-0.11.6-future-imports.patch-1 3329.out: ================================================== ***** soappy-0.11.6-future-imports.patch ***** ============================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-python/soappy/files/soappy-0.11.6-future-imports.patch ============================================== patching file SOAPpy/Client.py Hunk #1 FAILED at 40. 1 out of 1 hunk FAILED -- saving rejects to file SOAPpy/Client.py.rej <snip> ================================================== hmmmm, ll /var/tmp/portage/soappy-0.11.6-r1/work: ================================================== total 0 drwxr-xr-x 9 root root 400 2004-09-11 05:09 SOAPpy-0.11.6 ================================================== Aha! It seems the ebuild tries to apply the patch in te wrong directory...
Looks like $Id was being substituted by cvs (in the patch) making it no longer apply. I think I fixed this, please sync in about an hour, try the merge again, and close this bug if it works.
Works like a charm, thanks for the quick fix :D
