Well that's really strange. I merged OpenOffice 1.0.1, it installed itself without any error msg, but there's nothing in the /opt dir, really nothing, except a few dirs and config files...
Same experience here.At least I didn't notice any errors. But soffice is at /var/tmp/portage/openoffice-1.0.1-r1/image/opt/OpenOffice.org1.0.1/program/, where invoking it brings up the installation dialog, but it has a lot of errors copying files once it's entered into. Aborted after it got past a dozen files or so it couldn't copy. It had begun to create its directory structure where I'd selected by then.
running var/tmp/portage/openoffice-1.0.1-r1/image/opt/OpenOffice.org1.0.1/setup also begins the process, but it also has errors finding the files it wants to copy to the installation.
This is an odd bug. Have you guys tried to qmerge it? maybe something in the ebuild made it die before it was merged. You SURE there weren't any errors? did it say it was merged successfully?
When I emerge OpenOffice or OpenOffice-bin, I get a few error messages. Initializing installation program.......... * Removing build root from registy... egrep: /var/tmp/portage/openoffice-1.0.1-r1/image//opt/OpenOffice.org1.0.1/*: No such file or directory * Fixing permissions... chmod: failed to get attributes of `/var/tmp/portage/openoffice-1.0.1-r1/image//opt/OpenOffice.org1.0.1/share/config/webcast/*.pl': No such file or directory ln: creating symbolic link `/var/tmp/portage/openoffice-1.0.1-r1/image//opt/OpenOffice.org1.0.1/program/spadmin' to `soffice': No such file or directory I didn't notice them the first couple times I emerged openoffice-bin. After that, it looks almost like the ebuild was successful, it ends like this: * ****************************************************************** * To start OpenOffice.org, run: * * $ ooffice * * Also, for individual components, you can use any of: * * oocalc, oodraw, ooimpress, oomath or oowriter * * ****************************************************************** >>> Regenerating /etc/ld.so.cache... >>> app-office/openoffice-1.0.1-r1 merged. >>> Recording app-office/openoffice in "world" favorites file... * GNU info directory index is up-to-date. But, when I try to run any of those programs, I get an error message about a bad symlink, because there is no /opt/OpenOffice.org1.0.1/program directory. Like I said, it happens with openoffice and openoffice-bin. Thanks, Miles Gazic
are you having space issues? openoffice is a really big package, how much space is available in your /var/tmp?
I downloaded OOo_1.0.1_LinuxIntel_install.tar.gz from openoffice.org (The ebuild uses a file of the same name, it's probably the same one) and tried to run the setup program after I extracted it. The setup program had an unpacking progress bar that went a little over half way, but then quit. Perhaps it's a problem with dependencies for the binary package instead of the ebuild?
Not sure if this will help but it worked for me(tm). ;) openoffice wants a dotted directory with it's name and was trying to create this directories when merging(?) oosetup tries to create a version specific subdirectory. I did mkdir (dot)openoffice. Then re-emerged the ap and it started fine. bus_drivr
if nothing is in the /opt directory its almost always becuase you're out of space... as far as the tar.gz failing, thats more openoffice than anything else, your best bet is to retray openoffice or openoffice-bin i'm marking this as invalid as the original bug submitted was due to space limitations
I also have the same problem. I don't see any problems with available space in portage directory or in opt, but the situation _could_ have been different while emerging. Or maybe some other directory is used? Anyhow, it would be nice if the lack of diskspace caused the ebuild to abort...
