register configuration: ....................................................................................................................................................................................................................................................................................................................................................................................ACCESS DENIED unlink: /opt/OpenOffice.org1.0.2/delme * Removing build root from registry... * Fixing permissions... * Installing Menu shortcuts (need "gnome" or "kde" in USE)... install: cannot stat `/var/tmp/portage/openoffice-bin-1.1.0/image//opt/OpenOffice.org1.1.0/share/kde/net//.order': No such file or directory /usr/sbin/ebuild.sh: line 183: /var/tmp/portage/openoffice-bin-1.1.0/image//usr/share/gnome/apps/OpenOffice.org/*: No such file or directory man: prepallstrip: strip: strip: opt/OpenOffice.org1.1.0/program/python-core-2.2.2/bin/python opt/OpenOffice.org1.1.0/program/getstyle-gnome opt/OpenOffice.org1.1.0/program/crash_report.bin opt/OpenOffice.org1.1.0/program/msgbox-gnome opt/OpenOffice.org1.1.0/program/setup.bin opt/OpenOffice.org1.1.0/program/pagein opt/OpenOffice.org1.1.0/program/spadmin.bin opt/OpenOffice.org1.1.0/program/soffice.bin opt/OpenOffice.org1.1.0/program/gnomeint opt/OpenOffice.org1.1.0/program/pluginapp.bin opt/OpenOffice.org1.1.0/program/pkgchk.bin opt/OpenOffice.org1.1.0/program/jvmsetup.bin opt/OpenOffice.org1.1.0/program/javaldx opt/OpenOffice.org1.1.0/program/crash_report_with_gtk.bin >>> Completed installing into /var/tmp/portage/openoffice-bin-1.1.0/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-openoffice-bin-1.1.0-13322.log" open_wr: /opt/OpenOffice.org1.0.2/foo.tmp unlink: /opt/OpenOffice.org1.0.2/delme --------------------------------------------------------------------------------
I should add that the install was not successful because of this. Perhaps the 1.0.2-bin ebuild was the source of the problem? If so, the current ebuild should at least give directions for fixing this instead of just failing.
same problem here.
Was the same for me, except that the directory was "/opt/OpenOffice.org1.0.0". I solved it through removing the file .sversionrc in root's home. The ebuild then installs successfully. .sversionrc was installed to /root when i emerged OO-bin-1.0.0 _ages_ ago. Uninstalling older versions of OO-bin (<1.1.0) before emerging OO-bin-1.1.0 didn't solve this issue.
same here
i hate this, it compiles very very long and then fails when merging into system. how about a big fat warning, not to upgrade ?
i get the same error (once again, open office sucks) i already removed my old bin installation, wanted to try the src one, but noticed that tcsh was a dep, and decided to try 1.1.0 bin... i'll paste the output incase it helps anyone (btw, goddamn this big is old) register configuration: .................................................................................................................................................................................................................................................................................................................................................................................... * Removing build root from registry... * Fixing permissions... * Installing Menu shortcuts (need "gnome" or "kde" in USE)... /usr/sbin/ebuild.sh: line 185: /var/tmp/portage/openoffice-bin-1.1.0/image//usr/share/gnome/apps/OpenOffice.org/*: No such file or directory man: prepallstrip: strip: strip: opt/OpenOffice.org1.1.0/program/python-core-2.2.2/bin/python opt/OpenOffice.org1.1.0/program/getstyle-gnome opt/OpenOffice.org1.1.0/program/crash_report.bin opt/OpenOffice.org1.1.0/program/msgbox-gnome opt/OpenOffice.org1.1.0/program/setup.bin opt/OpenOffice.org1.1.0/program/pagein opt/OpenOffice.org1.1.0/program/spadmin.bin opt/OpenOffice.org1.1.0/program/soffice.bin opt/OpenOffice.org1.1.0/program/gnomeint opt/OpenOffice.org1.1.0/program/pluginapp.bin opt/OpenOffice.org1.1.0/program/pkgchk.bin opt/OpenOffice.org1.1.0/program/jvmsetup.bin opt/OpenOffice.org1.1.0/program/javaldx opt/OpenOffice.org1.1.0/program/crash_report_with_gtk.bin >>> Completed installing into /var/tmp/portage/openoffice-bin-1.1.0/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-openoffice-bin-1.1.0-16610.log" open_wr: /proc/self/maps open_wr: /proc/self/maps <it repeats this open_wr line like 20 more times> so :) can we curse here? ;) j/k
the /proc/self/maps is Bug 31972
The /proc/self/maps issue should be solved for recent portage versions. For openoffice-1.1.1 (to be released soon) we will try to fix some things and take a look again at the install locations etc. Be patient though OpenOffice is a dragon to build so testing takes too much time.
