| 1 |
»Q« wrote: |
| 2 |
> On Sun, 2 Nov 2008 20:34:17 +1100 |
| 3 |
> Adam Carter <Adam.Carter@×××××××××.au> wrote: |
| 4 |
> |
| 5 |
>>> I've got OpenOffice (compiled), v3.0.0 here. It appears broken. |
| 6 |
>>> I haven't tried a lot of things, but this little RTF file |
| 7 |
>>> gets it wedged right |
| 8 |
>>> away: the console that started it says: |
| 9 |
>>> |
| 10 |
>>> error - missing word count in dictionary file |
| 11 |
>>> Hash Manager Error : 4 |
| 12 |
>>> |
| 13 |
>>> So I'm guessing there's a problem in a spell checker. Where would I |
| 14 |
>>> look to solve that? |
| 15 |
>> http://bugs.gentoo.org/show_bug.cgi?id=242020 |
| 16 |
>> |
| 17 |
>> You need to emerge --sync again (there's an update to the ebuild, but |
| 18 |
>> no version increment IIRC) and rebuild openoffice. |
| 19 |
> |
| 20 |
> <whine> |
| 21 |
> I really wish they wouldn't do that, especially for hang or crash |
| 22 |
> bugs. I know people without the problem don't want to recompile OOo, |
| 23 |
> but it's annoying to have to watch bugzilla or the changelog to see if |
| 24 |
> the ebuild has been fixed. |
| 25 |
> </whine> |
| 26 |
|
| 27 |
I agree. This should only be done for build problems, not runtime |
| 28 |
problems. I think there's even a policy in place for that; if it |
| 29 |
doesn't build, change the ebuild. If it crashes at runtime, bump the |
| 30 |
revision. |
Archives