Bugzilla Bug 35702

If, for some reason, the distribution can't be unpacked, the ebuild doesn't
notice; it just plows ahead as though everything's ok, and then reports
success.

This bug was triggered by Bug #35701, but is independent of it (fix that bug,
and a different root cause might still trigger this bug).

Reproducible: Always
Steps to Reproduce:
1.See Bug #35701
2.
3.

Actual Results:  
N.B.: "#" comments are "anchors" for the discussion in "Expected Results"

>>> Unpacking j2sdk-1.4.1-01-linux-i586-gcc3.2.bin...
# 1
tar (child): helium\:/dev/nrst29: Cannot open: Input/output error
tar (child): Error is not recoverable: exiting now

[...]

tar: Child returned status 2
tar: Error exit delayed from previous errors
tail: write error: Broken pipe

# 2
>>> Source unpacked.
java
nsplugins
java
nsplugins

>>> Install blackdown-jdk-1.4.1 into /var/tmp/portage/blackdown-jdk-1.4.1/image/
category dev-java
# 3
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/bin': No
such file or directory
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/jre': No
such file or directory
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/lib': No
such file or directory
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/man': No
such file or directory
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/include':
No such file or directory
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/demo': No
such file or directory
cp: cannot stat `/var/tmp/portage/blackdown-jdk-1.4.1/work/j2sdk1.4.1/src.zip':
No such file or directory
/usr/lib/portage/bin/dodoc: COPYRIGHT does not exist.
/usr/lib/portage/bin/dodoc: LICENSE does not exist.
/usr/lib/portage/bin/dodoc: README does not exist.
/usr/lib/portage/bin/dodoc: INSTALL does not exist.
 ESC[32;01m*ESC[0m Not creating symlink for the plugin, because one already
exists
man:
prepallstrip:
strip:

# 4
>>> Completed installing into /var/tmp/portage/blackdown-jdk-1.4.1/image/

[...]

# 5
>>> dev-java/blackdown-jdk-1.4.1 merged.

Expected Results:  
1. This error from tar is as expected (but only in the presence of Bug #35701,
of course)

2. Should have noticed that the source was not in fact unpacked, and bailed
out.

3, 4.  Symptoms of failure to notice the problem at (2).

5. Likewise, but with worse effect:  because this ebuild terminates
"successfully", later ebuilds that depend on this one will fail in mysterious
ways.

Moving this again to java@gentoo.org, so everyone out there can help.

This is fixed in 1.4.2_rc1

Thanks for the input!!