Description of problem:
Version 1:1.8.4-4.fc12 is the one available for F12. If it was installed in F10 or F11 then it was currently gnumeric-1.8.4-5.fc10 or gnumeric-1.8.4-5.fc11. That leaves it as an "orphan" on upgrades to F12 and if installed in F12 then
bug #500890 and bug #505001 presumably still there.
Version-Release number of selected component (if applicable):
The latest F12 rpm is in testing at:
This should resolve your bug.
> The latest F12 rpm is in testing at:
This says _F10_, not F12 and a web page under that URL with a title "gnumeric-1.8.4-5.fc10 bugfix update" agrees.
Also a list
shows gnumeric update packages for F10 and F11 but none for F12. Moreover a check on a mirror with updates/testing/12/ notes 312 packages in SRPMS but none of these is gnumeric.
my bad, it seems F12 is not updated with these patches, will do that now.
Try this please
> Try this please ...
I am fully aware that such version does exist in koji and long enough that one wonders why it was not used in F12 distro. The problem is that there are no signed packages in mirrors for Fedora 12 and an upgrade leaves one with
non-working gnumeric as required libraries vanished.
There is quite a few packages in F12 with a similar problem although not for all of these a distro upgrade makes then unfunctional.
gnumeric-1.8.4-6.fc12 has been submitted as an update for Fedora 12.
This should be moved into F12 stable soon, in the meantime can you test and see if it works?
> in the meantime can you test and see if it works?
It does AFAICT after a quick check of 1.8.4-6.fc12 version. Although writing out a file as a "LaTeX table fragment" was very slow. It is true that a resulting LaTeX code was around 13 MB in size and a spreadsheet was created by loading some data in a CSV format and ended up with over 28000 rows but I was already pretty convinced the the whole thing crashed while writing. I was patient enough to find out that it did not.
gnumeric-1.8.4-6.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.