Some ebuilds fail to install because of an apparently failed "cp -pPR" or "cp -pR" giving messages like * * ERROR: dev-java/sun-jdk-1.6.0.15 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 2791: Called die * The specific snippet of code: * cp -pPR $dirs "${D}/opt/${P}/" || die "failed to copy"; * The die message: * failed to copy * * 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/dev-java/sun-jdk-1.6.0.15/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-java/sun-jdk-1.6.0.15/temp/environment'. * or * * ERROR: x11-libs/libxcb-1.1.90.1 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 3179: Called x-modular_src_install * environment, line 3977: Called die * The specific snippet of code: * make DESTDIR="${D}" install || die; * The die message: * (no error message) * * 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/x11-libs/libxcb-1.1.90.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libxcb-1.1.90.1/temp/environment'. * Running the cp manually in the appropiate directory does not show any errors and copies correctly (exit code 0). The man page of cp does however not say anything about exit codes. At least one other person has exactly the same problem as seen here: http://www.gentooforum.de/post/122241/x11-libs-libxcb-1-1-90-1-installation-schl-gt-fehl.html
Created attachment 200670 [details] libxcb-1.1.90.1 build.log
Created attachment 200671 [details] sun-jdk-1.6.0.15 build.log
Created attachment 200672 [details] emerge --info
Sorry but.. One bug for one package since they have different maintainers.
This bug is about sun-jdk install issues only, issues on libxcb have been split out to bug 280938. Thanks for the reports!
Created attachment 200769 [details] file with "0" in it to trick bugzilla into letting me obsolete an attachment
No idea what can be wrong. What filesystem and mount options is /var/tmp/portage on? Can you add '-v' to the ebuild's cp command to see where it exactly fails? Will using FEATURES="-sandbox" do any difference?
/var/tmp type tmpfs (rw,nosuid,nodev) With FEATURES=-sandbox the error is gone. But I don't understand why. I think we need to strace the cp command with and without sandbox.
please try re-emerging sandbox
I have the exact same issue. I managed to solve it by modifying line 72 in the ebuild from this: cp -pPR $dirs "${D}/opt/${P}/" || die "failed to copy" Into this: cp -PR --preserve=mode,ownership $dirs "${D}/opt/${P}/" || die "failed to copy" (following on what the meaning of -p is) Essentially, I removed the attempt to copy timestamps. The culprit maybe the fact that I am using ReiserFS and chose to set the 'noatime' mount option. I don't have the time to test this at the moment, as I have a working workaround. So if it helps anyone, I did my part of the job ;)
> So if it helps anyone, I did my part of the job ;) Yes, it was a big help since #gentoo was not. glad you posted. Here is more specific direction for anyone else. I also edited lines 78 and 82 to be: #78 was -- cp -pP src.zip "${D}/opt/${P}/" || die... cp -PR --preserve=mode,ownership src.zip "${D}/opt/${P}/" || die "failed to copy" #82 was -- cp -pPR demo sample "${D}/opt/${P}/" || die... cp -PR --preserve=mode,ownership demo sample "${D}/opt/${P}/" || die "failed to copy" # vi /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0.15.ebuild (edit line 72 according to bug report) # cd /usr/portage/dev-java/sun-jdk # ebuild sun-jdk-1.6.0.15.ebuild digest >>> Creating Manifest for /usr/portage/dev-java/sun-jdk digest.assumed 9 sun-jdk-1.4.2.19::j2sdk-1_4_2_19-linux-i586.bin sun-jdk-1.4.2.19::jce_policy-1_4_2.zip sun-jdk-1.5.0.20::jdk-5.0u20-dlj-linux-amd64.bin sun-jdk-1.5.0.20::jdk-5.0u20-dlj-linux-i586.bin sun-jdk-1.5.0.21::jdk-5.0u21-dlj-linux-amd64.bin sun-jdk-1.5.0.21::jdk-5.0u21-dlj-linux-i586.bin sun-jdk-1.6.0.15::jdk-6u15-dlj-linux-i586.bin sun-jdk-1.6.0.16::jdk-6u16-dlj-linux-amd64.bin sun-jdk-1.6.0.16::jdk-6u16-dlj-linux-i586.bin # emerge sun-jdk
this version is not in tree anymore. reopen if the problem persists with the versions that are in tree.
