[Bug 1182613] Re: puppet completely broken on saucy

2013-06-03 Thread Robie Basak
Fixed with facter 1.7.0-1ubuntu1 now in Saucy. ** Changed in: puppet (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title:

[Bug 1182613] Re: puppet completely broken on saucy

2013-06-03 Thread Robie Basak
Fixed with facter 1.7.0-1ubuntu1 now in Saucy. ** Changed in: puppet (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-23 Thread Matthias Klose
falling back to ruby1.8 is not a solution. Are there any extensions not yet built for 1.9? If not, please do so. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet

Re: [Bug 1182613] Re: puppet completely broken on saucy

2013-05-23 Thread Stig Sandbeck Mathisen
On Thu, May 23, 2013 at 01:33:28PM -, Matthias Klose wrote: falling back to ruby1.8 is not a solution. Are there any extensions not yet built for 1.9? If not, please do so. At a glance, it looks like facter is not available in the load path of ruby1.9. I'd start looking at the facter

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-23 Thread Robie Basak
The facter merge I prepared in bug 1173265 appears to fix this. Just awaiting sponsorship. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely broken on

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-23 Thread Matthias Klose
falling back to ruby1.8 is not a solution. Are there any extensions not yet built for 1.9? If not, please do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely

Re: [Bug 1182613] Re: puppet completely broken on saucy

2013-05-23 Thread Stig Sandbeck Mathisen
On Thu, May 23, 2013 at 01:33:28PM -, Matthias Klose wrote: falling back to ruby1.8 is not a solution. Are there any extensions not yet built for 1.9? If not, please do so. At a glance, it looks like facter is not available in the load path of ruby1.9. I'd start looking at the facter

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-23 Thread Robie Basak
The facter merge I prepared in bug 1173265 appears to fix this. Just awaiting sponsorship. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely broken on saucy To manage

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-22 Thread Robie Basak
Confirmed. ** Changed in: puppet (Ubuntu) Status: New = Triaged ** Changed in: puppet (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu.

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-22 Thread Robie Basak
Confirmed. ** Changed in: puppet (Ubuntu) Status: New = Triaged ** Changed in: puppet (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title:

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-21 Thread Sidnei da Silva
$ puppet /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:4:in `top (required)' from

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-21 Thread Sidnei da Silva
Apparently the problem is that the default ruby is now 1.9. Running /usr/bin/ruby1.8 /usr/bin/puppet seems to work around the problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu.

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-21 Thread Sidnei da Silva
See also Bug #1093934 which seems to be a similar issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely broken on saucy To manage notifications

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-21 Thread Sidnei da Silva
$ puppet /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:4:in `top (required)' from

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-21 Thread Sidnei da Silva
Apparently the problem is that the default ruby is now 1.9. Running /usr/bin/ruby1.8 /usr/bin/puppet seems to work around the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title:

[Bug 1182613] Re: puppet completely broken on saucy

2013-05-21 Thread Sidnei da Silva
See also Bug #1093934 which seems to be a similar issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely broken on saucy To manage notifications about this bug go