Summary: | app-office/abiword-2.8.4 version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thorsten Vollmer <thorsten> |
Component: | New packages | Assignee: | GNOME Office (OBSOLETE) <gnome-office+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | awaters1, follettoonip, Ikonta, jer, kanelxake, mail, nikoli, pacho, tesoro302, zsolt |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.abisource.com/release-notes/2.8.2.phtml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
abiword-2.7.2.ebuild
diff for easier review The build log of failed attemp to compile AbiWord 2.7.2 fix build failures with libtool-1 new dependency on media-libs/jpeg abiword-2.7.6.ebuild strace of russian localized interface abiword 'Help -> Search' click abiword-2.7.10.ebuild abiword 2.8.2 sample ebuild |
Description
Thorsten Vollmer
2009-06-01 14:30:49 UTC
Created attachment 193150 [details]
abiword-2.7.2.ebuild
Created attachment 193151 [details, diff]
diff for easier review
please this is a dev release... Feel free to use the ebuild for reference, once 2.8 is available. I do not expect many changes. Thanks for your efforts. In a distant past, Gentoo used to have development releases in its main tree (masked, of course). Now they are in some obscure overlays. This is unnecessarily complicated. But I’m off topic... I meant to say that Abiword 2.7 is a huge improvement and seems very stable. Thanks for the ebuild, Thorsten! (In reply to comment #1) > Created an attachment (id=193150) [edit] > abiword-2.7.2.ebuild > As a check for bug http://bugs.gentoo.org/show_bug.cgi?id=272410 I've tryed to build AbiWord 2.7.2. But this attemp failed. The build.log will be attached. Created attachment 193860 [details]
The build log of failed attemp to compile AbiWord 2.7.2
Created attachment 193947 [details]
fix build failures with libtool-1
(In reply to comment #8) > Created an attachment (id=193947) [edit] > fix build failures with libtool-1 > Thank you. The update to AbiWord-2.7.2 fixes at least the problem with exporting to pdf (the crash at print command should be fixed too). But after this update most commands in 'help' menu (in Russian translation) doesn't works and hangs up the application. It's much less actual, than crash at printing, but, I think, should be fixed. Actual dev version is 2.7.5 Renaming of the ebuild works Like gilles said, it's a dev release and not a stable release... (In reply to comment #11) > Like gilles said, it's a dev release and not a stable release... > However stable release doesn't support open office 3.x odt format. At least for me it was unable to open until emerge this dev. versions please stop arguing. gnome-office does not have the man-power to maintain develepment releases in tree for now so abiword as well as gnumeric will have to wait for an upstream _stable_ release to hit the tree. I too am displeased with 2.6 series status but that's all we'll have for a while. (In reply to comment #12) > (In reply to comment #11) > > Like gilles said, it's a dev release and not a stable release... > > > > However stable release doesn't support open office 3.x odt format. At least for > me it was unable to open until emerge this dev. versions > Feel free to write an ebuild and to commit/push it into your own overlay renaming to 2.7.6 works. runs and works fine. finally a functioning odt importer plugin. (In reply to comment #9) > But after this update most commands in ‘help’ menu (in Russian translation) > doesn’t works and hangs up the application. I cannot reproduce this problem. Please provide a backtrace if you still experience these hangs. Created attachment 197382 [details]
new dependency on media-libs/jpeg
(In reply to comment #16) > I cannot reproduce this problem. Please provide a backtrace if you still > experience these hangs. > I've updated to 2.7.6 and built it with debug USE on. The problem with the Help menu are the same. For example I click 'Help -> Search'. And (when AbiWord was started from gdb) see nothing. After a time (any action doesn't take a response) in console I see just: ** (abiword:13620): WARNING **: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. DEBUG: SEVIOR: e->button = 1 DEBUG: hit new tab DEBUG: SettingTabStop: 138.6mm DEBUG: m_draggingCenter = 10153 DEBUG: iTab: -2, m_draggingTab: -1 DEBUG: TopRuler: Tab Stop [138.6mm/L0,122.4mm/L0,124.9mm/L0] DEBUG: !!!!!!!!!!Created CR ID number 4 Doc UUID c5200ff0-6d36-11de-9e1a-d0462676efc5 DEBUG: fl_DocListener::change DEBUG: SectionBreak from start DEBUG: SectionBreak from start DEBUG: Doing view notification DEBUG: SectionBreak from start DEBUG: fp_Page:: Total avail after margins subtracted 13957 DEBUG: Page number 0 DEBUG: NumWrapped 0 DEBUG: Scroll Adjustment set to 0 upper 12280.000000 size 12345.000000 DEBUG: Scroll Adjustment set to 0 upper 12280.000000 size 12345.000000 and the clean window of AbiWord again. (In reply to comment #18) > (In reply to comment #16) > > I cannot reproduce this problem. Please provide a backtrace if you still > > experience these hangs. > > > I've updated to 2.7.6 and built it with debug USE on. > The problem with the Help menu are the same. > For example I click 'Help -> Search'. > And (when AbiWord was started from gdb) see nothing. > After a time (any action doesn't take a response) in console I see just: > for me help works fine. help opens in a browser (firefox) window. did you have installed a browser on your system? (In reply to comment #18) Did I understand correctly that AbiWord is completely unresponsive after clicking the menu item? If this is true, a stack trace would show where the execution stops. AbiWord calls gtk_show_uri to launch the web browser, and thus the actual problem might be unrelated to AbiWord. Created attachment 197990 [details]
abiword-2.7.6.ebuild
Added use flags for clipart, emacs, print, templates, tidy, and vim.
Default enable for clipart, print, spell, and templates.
emacs and vim only set key bindings, they don't pull in either.
Enable support for gnome-vfs.
(In reply to comment #20) > Did I understand correctly that AbiWord is completely unresponsive after > clicking the menu item? If this is true, a stack trace would show where the > execution stops. > AbiWord calls gtk_show_uri to launch the web browser, and thus the actual > problem might be unrelated to AbiWord. > If started normally (not via gdb or strace) abiword window becomes completely unresponsive. P.S. Yes, I have two browsers installed: firefox 3.0 and lynx. With what language is built your abiword (which works correctly), and/or localized your system? Created attachment 198011 [details]
strace of russian localized interface abiword 'Help -> Search' click
(In reply to comment #21) > Created an attachment (id=197990) You have added too many USE flags. Why do you want to use gnome-vfs when gio/gvfs is available? You gain nothing. Why do you want to disable printing when it does not reduce the dependencies? The key bindings are enabled by default and can be selected at runtime. [1] Again, no need for USE flags. 1: You may need to add KeyBindingsCycle=”1“ to your AbiWord profile. (In reply to comment #22) > Yes, I have two browsers installed: firefox 3.0 and lynx. Could you please try if 'gnome-open http://www.abisource.com/help/ru-RU/search.html' starts a web browser on your system? gnome-open is part of gnome-base/libgnome. (In reply to comment #25) > Could you please try if 'gnome-open > http://www.abisource.com/help/ru-RU/search.html' starts a web browser on your > system? gnome-open is part of gnome-base/libgnome. > I've checked it without gnome-open and seen that the documentation is available only for three languages: * English * French * Polish I'm not shure about localization of this issue (ebuild, localization pack or AbiWord itself). But I think, the action of click 'Help' items should first contains check the availability of requested item for selected language and only after that try to open it in a browser (availability of browser should be also checked). P.S. Excuse me my English. (In reply to comment #26) > (In reply to comment #25) > > Could you please try if 'gnome-open > > http://www.abisource.com/help/ru-RU/search.html' starts a web browser on your > > system? gnome-open is part of gnome-base/libgnome. > > > I’ve checked it without gnome-open and seen that the documentation is available > only for three languages: Please do test gnome-open. If gnome-open fails similarly, your problem is not with AbiWord. (In reply to comment #27) > Please do test gnome-open. If gnome-open fails similarly, your problem is not > with AbiWord. > You was right: $ gnome-open http://www.abisource.com/help/ru-RU/search.html Ошибка отображения URL: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (In reply to comment #28) > You was right: > $ gnome-open http://www.abisource.com/help/ru-RU/search.html > Ошибка отображения URL: DBus error org.freedesktop.DBus.Error.NoReply Thanks for your feedback. I am pretty sure that your problems with AbiWord and gnome-open have the same root because both programs use the same API to launch the web browser. dbus-monitor should give you an idea of what goes wrong. Please file a separate report if you need more help on this issue. BTW, currently installed version of AbiWord (2.7.6) again crashes at print command. But it causes only at real print, export to pdf works fine, wrint peview --- also OK (attemping to print via print preview window send a connamd to the printer and printer prints some symbols, but not the requested document.). Created attachment 202704 [details]
abiword-2.7.10.ebuild
* re-add dependency on libxml2, which was accidentally removed
* remove workaround for libtool-1; libtool-1.5.26 was used for this release
(In reply to comment #30) > BTW, currently installed version of AbiWord (2.7.6) again crashes at print command. Sergey, please start AbiWord from a shell with 'GTK_MODULES=foo abiword' and ignore the warning. Does it still crash? (In reply to comment #32) > Sergey, please start AbiWord from a shell with 'GTK_MODULES=foo abiword' and > ignore the warning. Does it still crash? > Currently I've updated to abiword-2.7.10 The bug with printing was posted to upstream http://bugzilla.abisource.com/show_bug.cgi?id=12341 If done as you recommended AbiWord prints the selected page successfully and not crashes. (In reply to comment #33) > If done as you recommended AbiWord prints the selected page successfully > and not crashes. The bug with printing was posted to upstream Thanks for testing. I am not convinced that this is a bug in AbiWord. The nature of the workaround and the stack trace indicate a problem with Gentoo's GTK+. We are at 2.8.1 now... any progress? http://www.abisource.com/downloads/abiword/2.8.1/source/abiword-2.8.1.tar.gz Please, make ebuild for it. I downloaded abiword-2.7.10.ebuild and renamed it to abiword-2.8.1 and it seems to work okay for now. I'm not sure how the plugins are handled though. The new version of abiword actually includes all of the plugins from the abiword-plugins package inside the source tarball now. I didn't look at it very hard but it looks as if you can only enable everything with the --enable-plugins option (someone correct me if I am wrong on this though), so in addition to changing the name of the ebuild, the --enable-plugins option and all of the dependencies from abiword-plugins has to be put into the ebuild as well. Maybe we can just have a 'plugins' USE flag for them? If I have time later tonight I will make an ebuild for it. I was under the impression from reading ./configure --help " --enable-plugins ="foo bar baz", list of plugins to build. Use --disable-plugins to disable plugin loading support, resulting in a smaller binary size. " that the parameters to enable plugins would be the directories listed under the plugins/ directory. I'll look into this more to see if it is true or not (In reply to comment #38) > The new version of abiword actually includes all of the plugins from the > abiword-plugins package inside the source tarball now. I didn't look at it > very hard but it looks as if you can only enable everything with the > --enable-plugins option (someone correct me if I am wrong on this though), so > in addition to changing the name of the ebuild, the --enable-plugins option and > all of the dependencies from abiword-plugins has to be put into the ebuild as > well. > > Maybe we can just have a 'plugins' USE flag for them? If I have time later > tonight I will make an ebuild for it. > Nobody has had the time to look "officially" on this yet for inclusion into portage? Has anyone found a non-workaround solution for the printing issue? We are at 2.8.2 now. (In reply to comment #42) > We are at 2.8.2 now. Sure, so update the Summary. :) (In reply to comment #43) > > Sure, so update the Summary. :) > I tried this with other bugs but normaly I can't do that. "You tried to change the Summary field from app-office/abiword-2.8.2 version bump to app-office/abiword-2.8.2 version bump cant , but only the assignee or reporter of the bug, or a sufficiently empowered user may change that field." Created attachment 225907 [details]
abiword 2.8.2 sample ebuild
this is a sample ebuild for 2.8.2 based off of the earlier versions posted
-for some reason putting --enable-builtin-plugins in G2CONF wouldn't work properly so I moved it into src_configure and used econf.
-not all of the plugins that could be enabled are exposed in the use flags
-first ebuild so give feedback please
I've been working on a cleaned up ebuild yesterday, hopefully will push it before next week. Thanks all for your patience. commited with hopefully the same level of flexibility the old abiword+abiword-plugins had. Thanks everyone. Thanks for providing this ebuild, Gilles. It exposed a bug in AbiWord’s build system. The compilation will fail if dev-cpp/asio is not installed and USE=collab is _not_ set. See http://bugzilla.abisource.com/show_bug.cgi?id=12701 (You may need to patch plugin-configure.m4 instead.) (In reply to comment #48) > Thanks for providing this ebuild, Gilles. It exposed a bug in AbiWord’s build > system. The compilation will fail if dev-cpp/asio is not installed and > USE=collab is _not_ set. We find that bug reports with generally 50 comments usually don't work that well any more, so please file a NEW bug report for that issue. It's basically unrelated to getting the ebuild into the tree in the first place, which is what this bug is about. |