Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m especially interested in knowing if there are any backward compatibility problems, since there should definitely be none. I''ll email out a changelog in the next few days. In the meantime, please open tickets for any problems you find with the current code. I would *really* like to be able to release 0.24.0 next week, but I know we''d all like this release to be stable, so we all need to help test beforehand. Thanks, Luke 1 - Not as close as I wanted to be (about 20 open tickets) but most of them are of the hunt-and-fix variety rather than refactoring. -- The most overlooked advantage to owning a computer is that if they foul up there''s no law against wacking them around a little. -- Joe Martin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Nov 27, 2007, at 9:45 PM, Luke Kanies wrote:> I''ll email out a changelog in the next few days. In the meantime, > please open tickets for any problems you find with the current code.Would you like them tagged in any specific way so you can easily list what''s filed as test results blocking release? Is tagging for misspiggy enough? -- Jeff McCune Systems Manager The Ohio State University Department of Mathematics
Luke Kanies <luke@madstop.com> writes:> I would *really* like to be able to release 0.24.0 next week, but I > know we''d all like this release to be stable, so we all need to help > test beforehand.Is there an easy way to run the new version without installing it? That is, can I clone master and then run the new version in place? This is probably a basic Ruby question but I haven''t found the answer yet.
On Nov 29, 2007, at 9:28 AM, Mark Plaksin wrote:> Luke Kanies <luke@madstop.com> writes: > >> I would *really* like to be able to release 0.24.0 next week, but I >> know we''d all like this release to be stable, so we all need to help >> test beforehand. > > Is there an easy way to run the new version without installing it? > That > is, can I clone master and then run the new version in place? This is > probably a basic Ruby question but I haven''t found the answer yet.I have a small wrapper script that works pretty well for me: PUPPET_BASE="/path/to/puppet.git" export RUBYLIB="${PUPPET_BASE}/lib" export PATH="${PUPPET_BASE}/bin" That''s all that should be necessary, though there''s a bit more you can do. If you use git, you''ll be able to quickly switch from 0.23.2 to head without changing anything else, as git keeps everything in the same folder when you switch branches. You can make sure the proper library will be loaded by typing "gemwhich puppet" -- Jeff McCune Systems Manager The Ohio State University Department of Mathematics
On Nov 29, 2007, at 8:24 AM, Jeff McCune wrote:> On Nov 27, 2007, at 9:45 PM, Luke Kanies wrote: >> I''ll email out a changelog in the next few days. In the meantime, >> please open tickets for any problems you find with the current code. > > Would you like them tagged in any specific way so you can easily list > what''s filed as test results blocking release? Is tagging for > misspiggy enough?I''m apparently the only one reviewing tickets, and I''m reviewing them just about every day at this point, so you shouldn''t need to tag them. -- Hanlon''s razor: Never attribute to malice that which can adequately be explained by stupidity. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Nov 29, 2007, at 8:28 AM, Mark Plaksin wrote:> Luke Kanies <luke@madstop.com> writes: > >> I would *really* like to be able to release 0.24.0 next week, but I >> know we''d all like this release to be stable, so we all need to help >> test beforehand. > > Is there an easy way to run the new version without installing it? > That > is, can I clone master and then run the new version in place? This is > probably a basic Ruby question but I haven''t found the answer yet.Yep -- set RUBYLIB=$puppet/lib. The only hitch is that you''ll likely want to use sudo, and it will mostly likely reset that variable, but there are multiple ways to resolve that (see sudo''s man page). -- Football is a mistake. It combines the two worst elements of American life. Violence and committee meetings. -- George F. Will --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies <luke@madstop.com> writes:> On Nov 29, 2007, at 8:28 AM, Mark Plaksin wrote: > >> Luke Kanies <luke@madstop.com> writes: >> >>> I would *really* like to be able to release 0.24.0 next week, but I >>> know we''d all like this release to be stable, so we all need to help >>> test beforehand. >> >> Is there an easy way to run the new version without installing it? >> That >> is, can I clone master and then run the new version in place? This is >> probably a basic Ruby question but I haven''t found the answer yet. > > Yep -- set RUBYLIB=$puppet/lib. The only hitch is that you''ll likely > want to use sudo, and it will mostly likely reset that variable, but > there are multiple ways to resolve that (see sudo''s man page).Hmm. Maybe I''m missing something. I tried setting RUBYLIB but the ruby man page says that *appends* to Ruby''s load path. And when I run puppet from a git clone I get this: /usr/lib/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb:6: warning: already initialized constant ResourceOverride which seems to say it''s using the installed Puppet code (or at least part of it) and not the new code. The new Puppet *does* work pointing at a 0.23.2 server :) But I want to make sure I''m testing the right way and can test the new code on the server too.
On Nov 29, 2007, at 11:36 AM, Mark Plaksin wrote:> Hmm. Maybe I''m missing something. I tried setting RUBYLIB but the > ruby > man page says that *appends* to Ruby''s load path. And when I run > puppet > from a git clone I get this: > > /usr/lib/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb:6: > warning: already initialized constant ResourceOverrideI don''t think you''re missing anything... I think this is the reason I stopped installing puppet and instead *exclusively* use RUBYLIB to make sure it''s working properly. Sorry I don''t have an alternative, but you should be able to just move /usr/lib/site_ruby/1.8/puppet out of the way while you test. Cheers, -- Jeff McCune Systems Manager The Ohio State University Department of Mathematics
On Nov 29, 2007, at 10:36 AM, Mark Plaksin wrote:> Hmm. Maybe I''m missing something. I tried setting RUBYLIB but the > ruby > man page says that *appends* to Ruby''s load path. And when I run > puppet > from a git clone I get this: > > /usr/lib/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb:6: > warning: already initialized constant ResourceOverride > > which seems to say it''s using the installed Puppet code (or at least > part of it) and not the new code. The new Puppet *does* work pointing > at a 0.23.2 server :) But I want to make sure I''m testing the > right way > and can test the new code on the server too.I think that problem is because of how Puppet automatically loads files, rather than a ruby problem. In my experience you can safely ignore that issue. -- Calamities are of two kinds: misfortunes to ourselves, and good fortune to others. -- Ambrose Bierce --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Thu, 2007-11-29 at 16:36 +0000, Mark Plaksin wrote:> Hmm. Maybe I''m missing something. I tried setting RUBYLIB but the ruby > man page says that *appends* to Ruby''s load path.The manpage is wrong .. the code really does prepend RUBYLIB. You can verify that by running "RUBYLIB=/foo:/bar ruby -e ''puts $:''"> And when I run puppet > from a git clone I get this: > > /usr/lib/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb:6: warning: already initialized constant ResourceOverrideIIRC, that''s a bad interaction of puppet''s autoloading code with RUBYLIB. The autoloading code (specifically loadall) looks through all paths on RUBYLIB for files it likes; it doesn''t have the same notion of "found something here, stop looking" - getting that to work would actually be quite hard. This specific issue happens because resourceoverride.rb was removed from git, but was part of the puppet version you have installed. What I did to get around that was to mv /usr/lib/site_ruby/1.8/puppet{,.unused} while testing with my git checkout. David