Hi, there is a new release of gnomesword. Just a version bump did it on my site (~amd64). yours, Eicke
Now 2.2.0 (STABLE) released. Previous comment on this bug was in re: 2.1.10. Changelog: 23 Dec 2006 RELEASE 2.2 (STABLE) IS NOW AVAILABLE Merry Christmas! See the download page. A half dozen bug reports have been addressed, a few build issues have been taken care of, and there are some release notes to describe matters that have been fixed, are pending enhancements, or are known not to be supported currently. GnomeSword is now officially no longer beta, but rather production/stable. 09 Dec 2006 2.1.10 has been released. The number of bug fixes and feature enhancements implemented in the last several months is very large indeed. The bug list is empty as of 09 Dec and the feature request list currently shows only items that are not practical or possible to implement right now. 2.1.10 has been released as the 2.2 release candidate, and if no significant problems are found in 2.1.10, the time until we release 2.2 will be short. It is time to show what GnomeSword can do
Created attachment 105537 [details] ebuild for gnomesword-2.2.0 It doesn't work with sword 1.5.8, so you need to edit /etc/portage/package.keywords Just add "app-text/sword"
The above ebuild installs the program, but gnomesword2 crashes. It seems to have configuration problem. I already tried "gnomesword newfiles" without success. It only created bookmark related files. I couldn't find any .config, config, or anything similar. Any advice???? "Don't say 'USE QT VERSION'"!!!
I emerged Sword-1.5.9, then configure, make, make install And it works just fine. Ebuild file must be wrong.
Re-assign wrt Bug 159976
the ebuild from Hamlet Mun works for me (x86)
Upstream has released 2.2.1. I tested Hamlet's ebuild on x86, bumping the version number. It correctly displays Hebrew, Greek and English. Note: the header on the ebuild is out of date
(In reply to comment #4) > I emerged Sword-1.5.9, then configure, make, make install > And it works just fine. > Ebuild file must be wrong. I agree on that. I cannot tell for sure where it comes from, though. I first suspected --as-needed to be the one to blame. But it doesn't seem to be the problem. Now my suspect is the path entries. It would make sense because: * install from ebuild: crash * run from source path: crash when loading first glade file * run after "make install" with default pathes: runs fine * run from source path after "make install": runs fine I think the crash number 2 is somewhere in src/gnome2/utilities.c:229 when it tries to get the glade files. I'll report that upstream an see what they come up with.
Upstream just released 2.2.1, so I bumped Hamlet's ebuild and committed it. Thanks for reporting!
