Traceback on piston up

[jsmullyan]

After a recent piston upgrade to piston 2.0.2, piston explodes as
follows when I attempt a piston up:

$ piston up/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/
active_support/dependencies.rb:440:in `load_missing_constant':
uninitialized constant Piston::Commands::Up (NameError)
from /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/
active_support/dependencies.rb:80:in `const_missing'
from /usr/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/piston/cli.rb:66:in
`const_get'
from /usr/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/piston/cli.rb:66:in
`start'
from /usr/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/piston/cli.rb:121
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from /usr/lib/ruby/gems/1.8/gems/piston-2.0.2/bin/piston:5
from /usr/bin/piston:19:in `load'
from /usr/bin/piston:19

Anyone know how I can remediate this?

[François Beausoleil]

Abbreviations aren't implemented. Use the full "update" or "upgrade"
commands.

Thanks!
--
François Beausoleil
http://blog.teksol.info/
http://piston.rubyforge.org/