pik update actually downdates the pik, no way to get back up #138

agrimm · 2012-07-09T01:49:14Z

If I'm in pik 0.3.0.pre , and try to update to 0.3.0.RC1, I get downdated(?) to 0.2.8. There doesn't seem to be a way of getting back up to 0.3.0.pre without building my own gem, as there's no gems available for 0.3.0.pre or 0.3.0.RC1 .

C:\Users\agrimm>pik --version
pik 0.3.0.pre on Microsoft Windows [Version 6.1.7601]
by Gordon Thiesfeld ([email protected])

C:\Users\agrimm>pik use 1.9.2

C:\Users\agrimm>ruby --version
ruby 1.9.2p136 (2010-12-25) [i386-mingw32]

C:\Users\agrimm>pik update

----------------------------------------------------------------------------

*  If you're upgrading from a version <= 0.1.1, you'll want to delete the pik.ba
t file
   from all of your ruby versions. Gem uninstall should do the trick.

*  Install pik to a location that's in your path, but someplace other than your
ruby\bin dir
   If you're upgrading from a more recent version, pik_install will overwrite th
e older files as needed.

    >path
      PATH=C:\tools\;C:\ruby\186-p368-mingw32\bin;C:\WINDOWS\system32;C:\WINDOWS


    >pik_install C:\tools

*  If this is a first-time install, add all the versions of ruby that you want t
o use with pik

    >pik add
    Adding:  186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
     Located at:  c:/ruby/186-p368-mingw32/bin

    >pik add C:\ruby\IronRuby-091\bin
    Adding:  091: IronRuby 0.9.1.0 on .NET 2.0.0.0
     Located at:  C:/ruby/IronRuby-091/bin

    >pik add C:\ruby\jruby-1.4.0RC1\bin
    Adding:  140: jruby 1.4.0RC1 (ruby 1.8.7 patchlevel 174) (2009-09-30 80c263b
) (Java HotSpot(TM) Client VM 1.6.0_14) [x86-java]
     Located at:  C:/ruby/jruby-1.4.0RC1/bin


----------------------------------------------------------------------------

Successfully installed pik-0.2.8
1 gem installed
Installing ri documentation for pik-0.2.8...
Installing RDoc documentation for pik-0.2.8...
Thank you for using pik.

mkdir -p C:\pik
mkdir -p C:\Users\agrimm/.pik
Installing to C:\pik

cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik_ru
nner.exe C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ba
t C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ps
1 C:\pik

creating C:\Users\agrimm/.pik/.pikrc

pik is installed

if you want to use pik with git bash, add the following line to your ~/.bashrc:

  [[ -s $USERPROFILE/.pik/.pikrc ]] && source $USERPROFILE/.pik/.pikrc


C:\Users\agrimm>pik --version
** Adding:  192: ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
 Located at:  C:\pik\rubies\ruby-1.9.2-p136\bin
pik 0.2.8

C:\Users\agrimm>pik update --version 0.3.0.RC1
pik 0.2.8

----------------------------------------------------------------------------

*  If you're upgrading from a version <= 0.1.1, you'll want to delete the pik.ba
t file
   from all of your ruby versions. Gem uninstall should do the trick.

*  Install pik to a location that's in your path, but someplace other than your
ruby\bin dir
   If you're upgrading from a more recent version, pik_install will overwrite th
e older files as needed.

    >path
      PATH=C:\tools\;C:\ruby\186-p368-mingw32\bin;C:\WINDOWS\system32;C:\WINDOWS


    >pik_install C:\tools

*  If this is a first-time install, add all the versions of ruby that you want t
o use with pik

    >pik add
    Adding:  186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
     Located at:  c:/ruby/186-p368-mingw32/bin

    >pik add C:\ruby\IronRuby-091\bin
    Adding:  091: IronRuby 0.9.1.0 on .NET 2.0.0.0
     Located at:  C:/ruby/IronRuby-091/bin

    >pik add C:\ruby\jruby-1.4.0RC1\bin
    Adding:  140: jruby 1.4.0RC1 (ruby 1.8.7 patchlevel 174) (2009-09-30 80c263b
) (Java HotSpot(TM) Client VM 1.6.0_14) [x86-java]
     Located at:  C:/ruby/jruby-1.4.0RC1/bin


----------------------------------------------------------------------------

Successfully installed pik-0.2.8
1 gem installed
Installing ri documentation for pik-0.2.8...
Installing RDoc documentation for pik-0.2.8...
Thank you for using pik.

mkdir -p C:\pik
mkdir -p C:\Users\agrimm/.pik
Installing to C:\pik

cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik_ru
nner.exe C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ba
t C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ps
1 C:\pik

creating C:\Users\agrimm/.pik/.pikrc

pik is installed

if you want to use pik with git bash, add the following line to your ~/.bashrc:

  [[ -s $USERPROFILE/.pik/.pikrc ]] && source $USERPROFILE/.pik/.pikrc


C:\Users\agrimm>ruby --version
ruby 1.9.2p136 (2010-12-25) [i386-mingw32]

C:\Users\agrimm>gem list --remote --all pik

*** REMOTE GEMS ***

pik (0.2.8, 0.2.7, 0.2.6, 0.2.5, 0.2.4, 0.2.3, 0.2.2, 0.2.1, 0.2.0, 0.1.1, 0.1.0
)
pikachu (0.0.1)
piki_doc (0.0.2.2)
pikl (0.3.0 ruby x86-mswin32, 0.2.8 ruby x86-mswin32, 0.2.7 ruby x86-mswin32, 0.
2.6 ruby x86-mswin32, 0.2.5 ruby x86-mswin32, 0.2.4, 0.2.3 ruby x86-mswin32, 0.2
.2 ruby x86-mswin32, 0.2.1, 0.2.0, 0.1.0)

C:\Users\agrimm>

The text was updated successfully, but these errors were encountered:

luislavena · 2012-07-10T00:54:31Z

Hello,

I believe that is happening because Pik is using RubyGems as mechanism
to update itself, but there hasn't been a 0.3.0x release to RubyGems:

http://rubygems.org/gems/pik/versions

That could satisfy the installation rules.

Since most likely you installed Pik not using the gem, doing an
update in the rubygems-way will downgrade you to latest gem-released
version.

I'll keep this open to investigate further, but it will be better that
use the same mechanism you used to install 0.3.0.pre to install rc1
version.

On Sun, Jul 8, 2012 at 10:49 PM, Andrew Grimm
[email protected]
wrote:

If I'm in pik 0.3.0.pre , and try to update to 0.3.0.RC1, I get downdated(?) to 0.2.8. There doesn't seem to be a way of getting back up to 0.3.0.pre without building my own gem, as there's no gems available for 0.3.0.pre or 0.3.0.RC1 .

C:\Users\agrimm>pik --version
pik 0.3.0.pre on Microsoft Windows [Version 6.1.7601]
by Gordon Thiesfeld ([email protected])

C:\Users\agrimm>pik use 1.9.2

C:\Users\agrimm>ruby --version
ruby 1.9.2p136 (2010-12-25) [i386-mingw32]

C:\Users\agrimm>pik update

----------------------------------------------------------------------------

*  If you're upgrading from a version <= 0.1.1, you'll want to delete the pik.ba
t file
   from all of your ruby versions. Gem uninstall should do the trick.

*  Install pik to a location that's in your path, but someplace other than your
ruby\bin dir
   If you're upgrading from a more recent version, pik_install will overwrite th
e older files as needed.

    >path
      PATH=C:\tools\;C:\ruby\186-p368-mingw32\bin;C:\WINDOWS\system32;C:\WINDOWS


    >pik_install C:\tools

*  If this is a first-time install, add all the versions of ruby that you want t
o use with pik

    >pik add
    Adding:  186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
     Located at:  c:/ruby/186-p368-mingw32/bin

    >pik add C:\ruby\IronRuby-091\bin
    Adding:  091: IronRuby 0.9.1.0 on .NET 2.0.0.0
     Located at:  C:/ruby/IronRuby-091/bin

    >pik add C:\ruby\jruby-1.4.0RC1\bin
    Adding:  140: jruby 1.4.0RC1 (ruby 1.8.7 patchlevel 174) (2009-09-30 80c263b
) (Java HotSpot(TM) Client VM 1.6.0_14) [x86-java]
     Located at:  C:/ruby/jruby-1.4.0RC1/bin


----------------------------------------------------------------------------

Successfully installed pik-0.2.8
1 gem installed
Installing ri documentation for pik-0.2.8...
Installing RDoc documentation for pik-0.2.8...
Thank you for using pik.

mkdir -p C:\pik
mkdir -p C:\Users\agrimm/.pik
Installing to C:\pik

cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik_ru
nner.exe C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ba
t C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ps
1 C:\pik

creating C:\Users\agrimm/.pik/.pikrc

pik is installed

if you want to use pik with git bash, add the following line to your ~/.bashrc:

  [[ -s $USERPROFILE/.pik/.pikrc ]] && source $USERPROFILE/.pik/.pikrc


C:\Users\agrimm>pik --version
** Adding:  192: ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
 Located at:  C:\pik\rubies\ruby-1.9.2-p136\bin
pik 0.2.8

C:\Users\agrimm>pik update --version 0.3.0.RC1
pik 0.2.8

----------------------------------------------------------------------------

*  If you're upgrading from a version <= 0.1.1, you'll want to delete the pik.ba
t file
   from all of your ruby versions. Gem uninstall should do the trick.

*  Install pik to a location that's in your path, but someplace other than your
ruby\bin dir
   If you're upgrading from a more recent version, pik_install will overwrite th
e older files as needed.

    >path
      PATH=C:\tools\;C:\ruby\186-p368-mingw32\bin;C:\WINDOWS\system32;C:\WINDOWS


    >pik_install C:\tools

*  If this is a first-time install, add all the versions of ruby that you want t
o use with pik

    >pik add
    Adding:  186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
     Located at:  c:/ruby/186-p368-mingw32/bin

    >pik add C:\ruby\IronRuby-091\bin
    Adding:  091: IronRuby 0.9.1.0 on .NET 2.0.0.0
     Located at:  C:/ruby/IronRuby-091/bin

    >pik add C:\ruby\jruby-1.4.0RC1\bin
    Adding:  140: jruby 1.4.0RC1 (ruby 1.8.7 patchlevel 174) (2009-09-30 80c263b
) (Java HotSpot(TM) Client VM 1.6.0_14) [x86-java]
     Located at:  C:/ruby/jruby-1.4.0RC1/bin


----------------------------------------------------------------------------

Successfully installed pik-0.2.8
1 gem installed
Installing ri documentation for pik-0.2.8...
Installing RDoc documentation for pik-0.2.8...
Thank you for using pik.

mkdir -p C:\pik
mkdir -p C:\Users\agrimm/.pik
Installing to C:\pik

cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik_ru
nner.exe C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ba
t C:\pik
cp C:/pik/rubies/ruby-1.9.2-p136/lib/ruby/gems/1.9.1/gems/pik-0.2.8/tools/pik.ps
1 C:\pik

creating C:\Users\agrimm/.pik/.pikrc

pik is installed

if you want to use pik with git bash, add the following line to your ~/.bashrc:

  [[ -s $USERPROFILE/.pik/.pikrc ]] && source $USERPROFILE/.pik/.pikrc


C:\Users\agrimm>ruby --version
ruby 1.9.2p136 (2010-12-25) [i386-mingw32]

C:\Users\agrimm>gem list --remote --all pik

*** REMOTE GEMS ***

pik (0.2.8, 0.2.7, 0.2.6, 0.2.5, 0.2.4, 0.2.3, 0.2.2, 0.2.1, 0.2.0, 0.1.1, 0.1.0
)
pikachu (0.0.1)
piki_doc (0.0.2.2)
pikl (0.3.0 ruby x86-mswin32, 0.2.8 ruby x86-mswin32, 0.2.7 ruby x86-mswin32, 0.
2.6 ruby x86-mswin32, 0.2.5 ruby x86-mswin32, 0.2.4, 0.2.3 ruby x86-mswin32, 0.2
.2 ruby x86-mswin32, 0.2.1, 0.2.0, 0.1.0)

C:\Users\agrimm>

Reply to this email directly or view it on GitHub:
#138

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

agrimm · 2012-07-10T01:05:11Z

I'll keep this open to investigate further, but it will be better that
use the same mechanism you used to install 0.3.0.pre to install rc1
version.

The mechanism I used to install 0.3.0.pre was the Windows installer. When installing pik, I assumed that the reason there wasn't a 0.3.0.rc1 version of Windows installer was that creating a Windows installer was a tedious process, and therefore I should use the Windows installer version merely to bootstrap myself to get the latest version. However, I'll keep your advice in mind in future.

zhon · 2013-03-22T21:40:20Z

Maybe the documentation could explain this better.

zhon mentioned this issue Mar 28, 2013

Which version of pik should we be using? #146

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

pik update actually downdates the pik, no way to get back up #138

pik update actually downdates the pik, no way to get back up #138

agrimm commented Jul 9, 2012

luislavena commented Jul 10, 2012

agrimm commented Jul 10, 2012

zhon commented Mar 22, 2013

pik update actually downdates the pik, no way to get back up #138

pik update actually downdates the pik, no way to get back up #138

Comments

agrimm commented Jul 9, 2012

luislavena commented Jul 10, 2012

AREA 17

agrimm commented Jul 10, 2012

zhon commented Mar 22, 2013