OpenOffice Emerge Problem

defconfoo · n00b Joined: 11 Feb 2003 Posts: 19

I'm having a problem emerging OpenOffice 1.0.2. It always stops after having done an md5checksum:

Skraut · Posted: Sun Mar 02, 2003 7:27 pm Post subject:

I got the exact same thing yesterday. I posted the same question, and really didn't get any response. I have noticed in my short time using Gentoo that some days things that don't work yesterday will work today. In fact I was able to emerge samba today and had other errors on it a few days ago. I just plan on emerging and unmerging Openoffice-bin and trying the regular openoffice every couple days.

Sorry I can't be any more help, it stumped me too. A red star is not exactly the most descriptive of error messages.

Ian · Posted: Sun Mar 02, 2003 8:31 pm Post subject:

of course, it means the soviets have taken over gentoo! :p

i don't know if i can help any, but i just emerge openoffice last night/this morning, and it just finished about 10 minutes ago.

maybe you could try an "emerge rsync" until it gets around the red star?

as i said, i don't think i can help much, but another rsync never hurt anyone (well, until you eat up all the bandwidth

).

eean · Posted: Mon Mar 03, 2003 6:14 am Post subject: Same problem

I'm having the exact same problem. Its really pretty baffling, I almost feel like figuring out how one goes about debugging python programs to figure out just what it thinks its doing.

I had hard drive trouble, so my installation of Gentoo is only a few days old. In other words, I havn't had much time to screw things up.

Skraut · Posted: Mon Mar 03, 2003 1:33 pm Post subject:

Well something to further this and hopefully find a solution:

when trying to emerge openoffice with gnoportage I got the following further information.

krjoseph · Posted: Mon Mar 03, 2003 2:46 pm Post subject: Check your java config

The only time I have had problems with openoffice emerge was when Blackdown was not set as my system java virtual machine. I did get an error telling me to set my jvm correctly, but who knows if that always works. It is at least something to check.

do 'java-config --help' to get the right syntax (sorry I'm at work on Windows). I think 'java-config --list-available-vms' will show you what is installed.

Then 'java-config --set-system-vm=blackdown-jdk-1.3.1' if you do not have it set.

Good luck.

Skraut · Posted: Mon Mar 03, 2003 4:01 pm Post subject:

I've tried the Blackdown 1.4.1 JDK and JRE both, and with both I get the same error as above

eean · Posted: Mon Mar 03, 2003 4:58 pm Post subject: Did a bug report

I just filed a bug report. You can follow its progress at:
https://bugs.gentoo.org/show_bug.cgi?id=16750

ef11 · n00b Joined: 07 Jan 2003 Posts: 16

I've had similar problems/trips with 1.0.2 openoffice.

Not to restate things, but the ebuild states that this is "extreme alpha" and that it won't work with any java implementation but blackdown.

I'm rather new to this whole gentoo thing (which I love) but I can't help but ask if this ebuild is ready to be unmasked?

P.S. I've masked it so that 'update world' flows smoothly.

eean · Posted: Mon Mar 03, 2003 8:29 pm Post subject: Solution

Apparently there is a bug in portage where it hangs on ewarn and eerrors that are blank. So, the solution is to go ahead and comment out all the ewarns and eerrors that are blank.
Here is the ebuild where I did this:
http://monroe.nu/openoffice-1.0.2-r1.ebuild

I think I catched them all. The problem was that I had to set my Java VM, and the message was surronded by blank eerror's.

sethbc · n00b Joined: 03 Dec 2002 Posts: 16

please don't version bump ebuilds when you fix them. I know its not in portage, but if one of these poor fools installs it in portdir_overlay it will totally hax them when i DO release -r1 (which should happen shortly). Like i said, best bet, upgrade your portage....

emerge sync ; emerge portage

if you're really snazzy...sync and then

ACCEPT_KEYWORDS="~arch" emerge portage...but -r8 may be stable any time now

eean · Posted: Wed Mar 05, 2003 3:34 pm Post subject: That is the case

Actually, what happened in my case is that I did an emerge sync without thinking, so it deleted my ebuild file. Then the emerge failed when it apparently later needed to refer to it. I was using ccache, so it wasn't terrible, but still not a good thing.

But yes, the version of portage that came a few hours after I posted that message fix's the bug.