permission problem when trying 'pik install 1.9.2'

[Grant Birchmeier]

I installed pik for the first time. When I ran 'pik install 1.9.2', I
got a strange permission error, pasted below.

Can anyone advise what's causing this, and if there is a workaround?

This is WinXP, and I my user has all rights. I don't think there
should be any permission issue.

Thanks
-Grant

==Terminal paste==
C:\Documents and Settings\Grant Birchmeier>pik install 1.9.2
INFO: Installing ruby-1.9.2-p136

INFO: Downloading: http://rubyforge.org/frs/download.php/73723/ruby-1.9.2-p136-i386-mingw32.7z
to: C:\Documents and Settings\Grant Birchmeier\.pik\downloads
\ruby-1.9.2-p136-i386-mingw32.7z

ruby-1.9.2-p136-i386-min...7z: 100% |oooooooooo| 5.8MB/ 5.8MB Time:
00:00:09
INFO: Extracting: C:\Documents and Settings\Grant Birchmeier\.pik
\downloads\ruby-1.9.2-p136-i386-mingw32.7z
to: C:\Documents and Settings\Grant Birchmeier\.pik\rubies
\ruby-1.9.2-p136


There was an error.
Error: Permission denied - C:\Documents and Settings\Grant
Birchmeier/.pik/rubies/ruby-1.9.2-p136/ruby-1.9.2-p136-i386-mingw32/
bin or C:\Documents and Settings\Grant Bir
chmeier/.pik/rubies/ruby-1.9.2-p136/bin

in: fileutils.rb:506:in `rename'
in: fileutils.rb:506:in `mv'
in: fileutils.rb:1397:in `fu_each_src_dest'
in: fileutils.rb:1411:in `fu_each_src_dest0'
in: fileutils.rb:1395:in `fu_each_src_dest'
in: fileutils.rb:495:in `mv'
in: pik/installer.rb:48:in `mv_r'
in: pik/installer.rb:82:in `extract'
in: pik/installer.rb:81:in `each'
in: pik/installer.rb:81:in `extract'
in: pik/installer.rb:74:in `each'
in: pik/installer.rb:74:in `extract'
in: pik/commands/install_command.rb:29:in `execute'
in: pik_runner:27

[Luis Lavena]

On Thu, Aug 25, 2011 at 12:50 PM, Grant Birchmeier <gr...@grantb.net> wrote:
> I installed pik for the first time.  When I ran 'pik install 1.9.2', I
> got a strange permission error, pasted below.
>
> Can anyone advise what's causing this, and if there is a workaround?
>
> This is WinXP, and I my user has all rights.  I don't think there
> should be any permission issue.
>

There could be two possible causes: path with spaces or permissions.

Since you indicate permissions is not the issue, could be the path with spaces.

I assume you're testing pik 0.3.0.pre release, correct?

Would you mind setting PIK_HOME environment variable to something
different? like C:\Tools? (previous creation of the directory?)

E.g.:

mkdir C:\Tools
SET PIK_HOME=C:\Tools
pik install 1.9.2

Thank you.
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry