`ebuild foo.ebuild unpack` does not unpack anything if /var/tmp/portage/${P} exist. # pwd /var/tmp/portage # ls -lah total 0 drwxr-xr-x 2 portage portage 48 Jul 15 15:11 . drwxrwxrwt 10 root root 312 Jul 15 14:15 .. # ebuild /usr/portage/net-analyzer/traceroute/traceroute-1.4_p12-r2.ebuild setup # ls -lah total 0 drwxr-xr-x 4 portage portage 112 Jul 15 15:14 . drwxrwxrwt 10 root root 312 Jul 15 14:15 .. drwxrws--- 2 portage portage 48 Jul 15 15:14 homedir drwxr-xr-x 3 portage portage 72 Jul 15 15:14 traceroute-1.4_p12-r2 # ebuild /usr/portage/net-analyzer/traceroute/traceroute-1.4_p12-r2.ebuild unpack >>> md5 src_uri ;-) traceroute-1.4a12.tar.gz >>> Unpacking source... /usr/lib/portage/bin/ebuild.sh: line 25: cd: /var/tmp/portage/traceroute-1.4_p12-r2/work/traceroute-1.4a12: No such file or directory * Applying traceroute-1.4-target-resolv.patch... * Failed Patch: traceroute-1.4-target-resolv.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/traceroute-1.4_p12-r2/temp/traceroute-1.4-target-resolv.patch-331.out !!! ERROR: net-analyzer/traceroute-1.4_p12-r2 failed. !!! Function epatch, Line 322, Exitcode 0 !!! Failed Patch: traceroute-1.4-target-resolv.patch! !!! If you need support, post the topmost build error, NOT this status message. # rm -rf traceroute-1.4_p12-r2/ # ebuild /usr/portage/net-analyzer/traceroute/traceroute-1.4_p12-r2.ebuild unpack >>> md5 src_uri ;-) traceroute-1.4a12.tar.gz >>> Unpacking source... >>> Unpacking traceroute-1.4a12.tar.gz to /var/tmp/portage/traceroute-1.4_p12-r2/work * Applying traceroute-1.4-target-resolv.patch... [ ok ] >>> Source unpacked.
Why? I don't know, but here's the cause for those that do. :) bash-2.05b# ebuild /usr/portage/net-analyzer/traceroute/traceroute-1.4_p12-r2.ebuild setup bash-2.05b# head -n 1 traceroute-1.4_p12-r2/temp/environment A= bash-2.05b# grep unpack /usr/portage/net-analyzer/traceroute/traceroute-1.4_p12-r2.ebuild src_unpack() { unpack ${A}
I'm having the same problem with an ebuild that I did a ebuild <path to ebuild> unpack. It also had a patch in src_unpack using epatch. Portage 2.0.51_pre13 head -n 1 /var/tmp/portage/gtkhtml-1.1.10-r1/temp/environment A= rm -rf /var/tmp/portage didn't help. A user in the forums with portage-2.0.50-r9 is having the same problem.
If I delete ${A} in DISTFILES I can emerge the ebuild at least.
This is a .51_pre13 specific bug... works fine w/ >2.0.51-r0
