Piston problem

Hi,
I couldn’t find a piston list, please let me know if anyone knows of
one.

I’m having a few problems using piston. I have vendor/rails under
piston control, but when I run a piston update I get the following
message.

Processing ‘vendor/rails’…
Fetching remote repository’s latest revision and UUID
Restoring remote repository to known state at r6736
Updating remote repository to r7144
Processing adds/deletes
svn: ‘vendor/rails/activerecord/test/empty_date_time_test.rb’ does not
exist
/usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/command.rb:43:in
`svn’: Command svn remove --quiet --force
vendor/rails/activerecord/test/empty_date_time_test.rb resulted in an
error: (RuntimeError)

    from 

/usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/commands/update.rb:79:in
update' from /usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/commands/update.rb:65:ineach_line’
from
/usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/commands/update.rb:65:in
update' from /usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/commands/update.rb:10:inrun’
from
/usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/commands/update.rb:9:in
each' from /usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/piston/commands/update.rb:9:inrun’
from
/usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/transat/parser.rb:131:in
execute' from /usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/transat/parser.rb:127:ineach’
from
/usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/transat/parser.rb:127:in
execute' from /usr/lib/ruby/gems/1.8/gems/piston-1.3.3/lib/transat/parser.rb:104:inparse_and_execute’
from /usr/lib/ruby/gems/1.8/gems/piston-1.3.3/bin/piston:10
from /usr/bin/piston:16:in `load’
from /usr/bin/piston:16

What’s wrong here?

How do I clean up after a failed command like this? I suppose I just
svn revert vendor/rails?

Any pointers appreciated.

Cheers,
Jord

I hate to reply to my own post, but anyone have any ideas?

Thanks :slight_smile:

It looks like SVN/Piston are trying to delete a file that should have
been present from r6736 but is not present on your system.

If you do not have any changes in rails to apply, you can always nuke
the whole tree and do a new piston install of the whole tree. At
this point that seems the safest course as there could be other issues.

Michael