I fixed this upstream, I'd like this to be applied to RHEL4 too, it's needed for ocfs2console. Silly stray characters in the module file makes it unusable.
Created attachment 112079 [details] Patch lets the module load successfully
Issue tracker 68821
Oracle, in order to help us judge priority of this change, what part of your software relies on the vte python module?
ocfs2console needs it, for the fsck frontend and the node configuration file propagation bits. I don't understand why there is so much delay to apply a simple, straightforward patch that was accepted immediately by the upstream maintainer. Considering that the python module doesn't work *at all* without this patch, I don't see how there can be any worries about regressions.
http://people.redhat.com/wtogami/temp/vte-RHEL4/ Hi Oracle, this is the current candidate package is heading towards RHEL4U2. Could you please verify that it solves this issue? Thanks.
Yes, the new package solves this problem.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-590.html