ERROR: while executing gem ... (Zlib :: GzipFile :: Error) not in gzip format

I am developing the Sencha touch 2 application. I followed the " Styling the Sencha Touch UI Application " Touchscreen Application Tutorial ".

I need to install Ruby, Compass and SASS. I installed Ruby using the installer from rubyinstaller.org.

When I execute the following command, I get the expected result, which confirms the correct installation:

C:\>ruby -v ruby 1.9.3p327 (2012-11-10) [i386-mingw32] 

Current source updated:

 C:\>gem sources ** CURRENT SOURCES ** http://rubygems.org/ 

Further, since I am behind the proxy server, I used the following command to install HAML / Compass:

 C:\>gem install -p [proxy:port] compass ERROR: While executing gem ... (Zlib::GzipFile::Error) not in gzip format** 

Can someone help me? I found solutions, such as updating the system, updating the sources of precious stones, but everything is relevant in my system.


Edit:

 C:\>gem install compass 

works great on my private system. When I try to execute the same command from my workstation, I need to use a proxy server as above, and this leads to an error.

+8
ruby sass compass-sass gem sencha-touch
source share
2 answers

I assume ERROR is happening because the web sense in my workplace blocks these downloads.

Solution : I downloaded the necessary gems: chunky_png, fssm, compass, sass, haml , etc. directly from http://rubygems.org/gems and put these gems in my local directory.

After that I tried gem install compass . First, search in your local directory. When finding the necessary gems, installation occurs. No connection to the ruby ​​website required.

Note. Run the team from the path where the gems are located.

for example: I put gems in C: \ Ruby193 \ lib \ ruby ​​\ gems \ 1.9.1 \ gems

So, I run the following command:

C:\Ruby193\lib\ruby\gems\1.9.1\gems>gem install compass

+6
source share

I had a similar problem, it worked on my own laptop, but failed when working with a virtual server (Ubuntu 12.10) that used a proxy.

Following the suggestion I found here , from the command line that I defined:

 export HTTPS_PROXY=proxy-address:proxy-port-number export HTTP_PROXY=proxy-address:proxy-port-number 

and then my gem installation package worked fine.

+2
source share

All Articles