By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2442 - Ruby: uninitialized constant Qt::TQt in qtruby.rb
Summary: Ruby: uninitialized constant Qt::TQt in qtruby.rb
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: amd64 Kubuntu Precise
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: R14.0.3
  Show dependency treegraph
 
Reported: 2015-05-05 05:41 CDT by Chucky
Modified: 2015-12-06 09:28 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments
fix proposal formatted as a unified diff (626 bytes, patch)
2015-05-05 05:41 CDT, Chucky
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chucky 2015-05-05 05:41:18 CDT
Created attachment 2505 [details]
fix proposal formatted as a unified diff

== PATCH PROPOSAL ATTACHED


== Context
 - I've installed TDE bindings for Ruby
 - I've adapted my env var RUBYLIB (as I've a 1.8.7):
 $ export RUBYLIB=/opt/trinity/lib/ruby/1.9.1:/opt/trinity/lib/ruby/1.9.1/Qt:/opt/trinity/lib/ruby/1.9.1/x86_64-linux


== Symptoms

When running 
 $ rbqtapi -h
I get the following error:
-----------8<--------------------------8<--------------------
/opt/trinity/lib/ruby/1.9.1/Qt/qtruby.rb:182: uninitialized constant Qt::TQt (NameError)
        from /opt/trinity/lib/ruby/1.9.1/Qt.rb:1:in `require'
        from /opt/trinity/lib/ruby/1.9.1/Qt.rb:1
        from /opt/trinity/bin/rbqtapi:11:in `require'
        from /opt/trinity/bin/rbqtapi:11
-----------8<--------------------------8<--------------------


== Solution

I've patched qtruby.rb and it works very well. Please find the fix as an attachment.

As you can see by reading this VERY SMALL PATCH, the bug has nothing to do with my Ruby version (which is what I thought at first).


== Notes

I am using Ruby 1.8.7 under Kubuntu Precise x86_64

I cannot truly understand why such a bug is not more visible to other people, even if they're using Ruby 1.9.1.
Comment 1 Chucky 2015-05-05 05:45:10 CDT
Status updated as a patch proposal is attached to this report.
Comment 2 Slávek Banko 2015-12-06 09:28:06 CST
Pushed to GIT in hash f46bd0ca (master) and 1b41f605 (r14.0.x).

Thank you for your contribution!