This seems to occur whenever a package is attempted to be made which was previously compiled. It appears to attempt to obtain the files from /var/tmp/portage/<package name>/image, however it doesn't realize that the files are not there. Rather than attempting to recompile, it just attempts to tar up an empty directory, tar fails, but emerge does not care and believes the process succeeded. Here's some output with kde-3.1.3 as an example: emerge --buildpkgonly kde Calculating dependencies ...done! >>> emerge (1 of 1) kde-base/kde-3.1.2 to / >>> Unpacking source... >>> Source unpacked. >>> Install kde-3.1.2 into /var/tmp/portage/kde-3.1.2/image/ category kde-base man: prepallstrip: strip: >>> Completed installing into /var/tmp/portage/kde-3.1.2/image/ tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors >>> Done. >>> Regenerating /etc/ld.so.cache... * GNU info directory index is up-to-date. This is very annoying and should be fixed. If anything, portage should alteast not think the process succeeded when it didn't.
Created attachment 15414 [details, diff] fixed
fixed in portage-2.0.49_pre18
