uninitialized constant QemuToolkit::Vmadm::FileUtils
Example:
root@gazoo ~ # gem install qemu-toolkit Fetching: qemu-toolkit-0.3.1.gem (100%) Successfully installed qemu-toolkit-0.3.1 1 gem installed Installing ri documentation for qemu-toolkit-0.3.1... Installing RDoc documentation for qemu-toolkit-0.3.1... root@gazoo ~ # vmadm create myvm3
uninitialized constant QemuToolkit::Vmadm::FileUtils
Further info:
root@gazoo ~ # ruby -v ruby 1.9.3p194 (2012-04-20) [i386-solaris2.11]
Ruby was installed from Theo's OmniOS package - INDEX ACTION VALUE PACKAGE pkg.descr set Ruby 1.9 (1.9.3-p194) pkg:/omniti/runtime/ruby-19@1.9.3.194-0.151002 pkg.summary set Ruby 1.9 pkg:/omniti/runtime/ruby-19@1.9.3.194-0.151002
Comments (5)
-
repo owner -
repo owner Catch me on irc (kschiess in #omnios) and we'll try to figure out what happens, ok?
-
repo owner - changed status to on hold
Bug is on hold until I can reproduce this. I don't have the faintest clue why this happens.
-
Thanks, all fixed ... the issue was that 0.3.0 was still in the path, not 0.3.1. Uninstalling both showed that 0.3.0 was still installed, installing 0.3.1 showed that my path still pointed to 0.3.0.
-
repo owner - changed status to resolved
- Log in to comment
Thanks for the report.
I've just reconstructed an empty system with omniti/runtime/ruby-19 on it and cannot reproduce this - my commands always work.
Can try uninstalling the gem totally and reinstalling it? The sequence
# gem uninstall qemu-toolkit -> answer yes at the prompt # gem install qemu-toolkit
would achieve that. I guess you have old binaries laying around.