Unable to update a piston-managed directory
James
When doing a 'piston update dir' the app crashes and fails to perform
any changes.
The verbose dump is:
C:\Dev\rapidfire\trunk\endpoint\vendor\plugins\active_message>piston
update .
fatal: Not a git repository (or any of the parent directories): .git
INFO main: Updating from revision 32276 to revision 33091
c:/ruby/1.8.6/lib/ruby/1.8/pathname.rb:709:in `relative_path_from':
different prefix: "C:\\" and "C:/Dev/rapidfire/trunk/endpoint/vendor/
plugins/.active_message.tmp" (ArgumentError)
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/svn/revision.rb:108:in `relative_paths'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/svn/revision.rb:108:in `map'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/svn/revision.rb:108:in `relative_paths'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/svn/revision.rb:50:in `update_to'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/working_copy.rb:225:in `update'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/commands/update.rb:25:in `run'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/commands/update.rb:36:in `start'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/commands/update.rb:34:in `each'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/commands/update.rb:34:in `start'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/cli.rb:67:in `start'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/lib/
piston/cli.rb:121
from c:/ruby/1.8.6/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:31:in `gem_original_require'
from c:/ruby/1.8.6/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:31:in `require'
from c:/ruby/1.8.6/lib/ruby/gems/1.8/gems/piston-2.0.2/bin/
piston:5
from c:/ruby/1.8.6/bin/piston:19:in `load'
from c:/ruby/1.8.6/bin/piston:19
I've tried piston 2.0.6 which produces the same error.
Has anyone else experienced this, or got a work-around, or is it time
to go digging in the code?
On a side note - other things I dislike about piston 2 vs 1:
- complaining about git repos when it knows it's an svn repo
- running commands with no arguments under piston 1 made them check
subdirs, whilst under piston 2 they don't.
- the removal of the 'help' command, forcing me to go back to the
piston website if I forget the name of one of the commands.
François Beausoleil
Le 2009-08-02 à 20:14, James a écrit :
> Has anyone else experienced this, or got a work-around, or is it time
> to go digging in the code?
This is a Subversion WC?
> On a side note - other things I dislike about piston 2 vs 1:
> - complaining about git repos when it knows it's an svn repo
Yes, there are sometimes problems with the way exceptions are caught.
Release early, release often. Sorry for the inconvenience.
> - running commands with no arguments under piston 1 made them check
> subdirs, whilst under piston 2 they don't.
I hadn't verified that behavior. Thanks for that. I'll add feature
tests.
> - the removal of the 'help' command, forcing me to go back to the
> piston website if I forget the name of one of the commands.
This one's been on my agenda.
Bye,
François
James Walker
>
> Hi,
>
> Le 2009-08-02 à 20:14, James a écrit :
>
>> Has anyone else experienced this, or got a work-around, or is it time
>> to go digging in the code?
>
> This is a Subversion WC?
Yes it is
>
>> On a side note - other things I dislike about piston 2 vs 1:
>> - complaining about git repos when it knows it's an svn repo
>
> Yes, there are sometimes problems with the way exceptions are caught.
> Release early, release often. Sorry for the inconvenience.
No worries - it's not impacting the actual application, just a scary warning.
>
>> - running commands with no arguments under piston 1 made them check
>> subdirs, whilst under piston 2 they don't.
>
> I hadn't verified that behavior. Thanks for that. I'll add feature
> tests.
I use it to manage plugins and gems in RoR apps and under version 1.4
if I am in vendor\plugins and do
piston status
then it will tell me of any plugins which are out of date. Under version 2
I have to do
piston status some_plugin_dir
>> - the removal of the 'help' command, forcing me to go back to the
>> piston website if I forget the name of one of the commands.
>
> This one's been on my agenda.
Fair enough :)
Thanks for the rapid replies - it's still a very useful product.
Sergio Cambra .:: entreCables S.L. ::.
> 2009/8/3 François Beausoleil <francois....@gmail.com>:
> > Le 2009-08-02 à 20:14, James a écrit :
> >> - running commands with no arguments under piston 1 made them check
> >> subdirs, whilst under piston 2 they don't.
> >
> > I hadn't verified that behavior. Thanks for that. I'll add feature
> > tests.
>
> I use it to manage plugins and gems in RoR apps and under version 1.4
> if I am in vendor\plugins and do
> piston status
> then it will tell me of any plugins which are out of date. Under version 2
> I have to do
> piston status some_plugin_dir
You can use piston status .
or piston status vendor/plugins from appliation root path
--
Sergio Cambra .:: entreCables S.L. ::.
Mariana Pineda 23, 50.018 Zaragoza
T) 902 021 404 F) 976 52 98 07 E) ser...@entrecables.com