[opensuse-factory] gv keysym problem (apLineDel)
[gv-3.6.8-5.7] Starting gv gives Warning: translation table syntax error: Unknown keysym name: apLineDel Warning: ... found while parsing '<Key>apLineDel: GV_Page(page+5) ' Warning: String to TranslationTable conversion encountered errors which in turn causes many shortkeys to fail within gv. This problem has been reported for gentoo, together with a patch (for version 3.7.1, however): http://bugs.gentoo.org/339394 Is it possible that this gets fixed for openSuSE also? Werner -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Jan 05, 2011 at 06:49:41PM +0100, Werner LEMBERG wrote:
[gv-3.6.8-5.7]
Starting gv gives
Warning: translation table syntax error: Unknown keysym name: apLineDel Warning: ... found while parsing '<Key>apLineDel: GV_Page(page+5) ' Warning: String to TranslationTable conversion encountered errors
which in turn causes many shortkeys to fail within gv.
This problem has been reported for gentoo, together with a patch (for version 3.7.1, however):
Is it possible that this gets fixed for openSuSE also?
Yes. And due to the openSUSE Build Service (OBS) you're able to initiate such a change at your own. Here is a rough picture of the required steps: "osc search gv" leads to the location where gv is maintaned, the Publishing project. Call "osc branch Publishing gv" will branch gv in your OBS user area. Then you apply the required changes, add a changelog hunk via "osc vc", call "osc build openSUSE:11.3 x86_64 gv.spec" to test if it builds, "osc add gentoo339394_gv_fix.diff", "osc commit" and see if it also builds on the server; osc submitrequest back to the Publishing project. With the submit request I would also request the maintainer to push it into openSUSE Factory. See http://en.opensuse.org/openSUSE:Build_Service_Collaboration for how it works in detail. If you're used to work with subversion or git the osc tool works for you as well. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Is it possible that this gets fixed for openSuSE also?
Yes. And due to the openSUSE Build Service (OBS) you're able to initiate such a change at your own. Here is a rough picture of the required steps: [...]
Thanks for the instructions; I'll try that if I find some time besides maintaining both FreeType and groff ... Werner -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Jan 05, 2011 at 07:37:23PM +0100, Werner LEMBERG wrote:
Is it possible that this gets fixed for openSuSE also?
Yes. And due to the openSUSE Build Service (OBS) you're able to initiate such a change at your own. Here is a rough picture of the required steps: [...]
Thanks for the instructions; I'll try that if I find some time besides maintaining both FreeType and groff ...
Well, the trouble any of us has more or less. One additional hint is provided by the osc maintainer command. In the particular case it is: osc maintainer Publishing gv This reports the bugowner and maintainer if defined. https://bugzilla.novell.com/show_bug.cgi?id=662578 tracks this issue. Unfortunately I'm not aware of an easy way to pipe an existing report like the initial mail on the factory list into the novell bugzilla. :/ Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (2)
-
Lars Müller -
Werner LEMBERG