drush make fails when trying to unzip libraries on Windows 7 [#2120953]

I'm running Windows 7. I had the distinctly not-fun task of upgrading drush on Windows. Because Drush landed in a different location, I had to change the PATH. I think you've gotten reports on that. When I finally DID run drush omega-wizard, it reported that it had not unzipped any of the libraries (true) but had completed correctly????

The dialog during drush ececution was:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\ProgramData\Drush>path
PATH=C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program File
s (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Window
s;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Progra
m Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\
syswow64;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\Wi
relessCommon\;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\
bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program
 Files (x86)\Intel\Services\IPT\;C:\Program Files\Dell\Dell Data Protection\Acce
ss\Advanced\Wave\Gemalto\Access Client\v5\;C:\Program Files (x86)\Common Files\R
oxio Shared\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLS
hared\;C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared\;C:\Progra
m Files (x86)\Common Files\Roxio Shared\OEM\12.0\DLLShared\;C:\Program Files (x8
6)\Roxio\OEM\AudioCore\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Fi
les (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Git\cmd;C:\Progra
m Files (x86)\QuickTime\QTSystem\;C:\ProgramData\Propeople\Drush\;C:\Program Fil
es (x86)\Propeople\Drush\GnuWin32\bin;C:\Program Files (x86)\Propeople\Drush\Php


C:\ProgramData\Drush>path C:\Program Files\Common Files\Microsoft Shared\Windows
 Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemR
oot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\Wind
owsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program File
s\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files\Intel\WiFi\bin\;C:\Progra
m Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\NTRU Cryptosys
tems\NTRU TCG Software Stack\bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG S
oftware Stack\bin\;C:\Program Files (x86)\Intel\Services\IPT\;C:\Program Files\D
ell\Dell Data Protection\Access\Advanced\Wave\Gemalto\Access Client\v5\;C:\Progr
am Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Commo
n Files\Roxio Shared\OEM\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Sh
ared\OEM\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\OEM\12.0\DL
LShared\;C:\Program Files (x86)\Roxio\OEM\AudioCore\;C:\Program Files (x86)\Wind
ows Live\Shared;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program
Files (x86)\Git\cmd;C:\Program Files (x86)\QuickTime\QTSystem\;C:\ProgramData\Dr
ush\;C:\Program Files (x86)\Drush\GnuWin32\bin;C:\Program Files (x86)\Drush\Php

C:\ProgramData\Drush>path
PATH=C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program File
s (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Window
s;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Progra
m Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\
syswow64;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\Wi
relessCommon\;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\
bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program
 Files (x86)\Intel\Services\IPT\;C:\Program Files\Dell\Dell Data Protection\Acce
ss\Advanced\Wave\Gemalto\Access Client\v5\;C:\Program Files (x86)\Common Files\R
oxio Shared\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLS
hared\;C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared\;C:\Progra
m Files (x86)\Common Files\Roxio Shared\OEM\12.0\DLLShared\;C:\Program Files (x8
6)\Roxio\OEM\AudioCore\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Fi
les (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Git\cmd;C:\Progra
m Files (x86)\QuickTime\QTSystem\;C:\ProgramData\Drush\;C:\Program Files (x86)\D
rush\GnuWin32\bin;C:\Program Files (x86)\Drush\Php

C:\ProgramData\Drush>cd \VgServer\xampp\htdocs\ca-ccx\web

C:\VgServer\xampp\htdocs\ca-ccx\web>drush help --filter=omega
All commands in omega: (omega)
 omega-export (oexp)   Exports the theme settings of a given theme from the
                       database to the .info file.
 omega-guard (ogrd)    Runs guard for the given theme including Compass and
                       LiveReload by default.
 omega-revert (orev)   Reverts the theme settings of a given theme by deleting
                       them from the database.
 omega-subtheme        Creates a Omega subtheme.
 (osub)
 omega-wizard (owiz)   Guides you through a wizard for generating a subtheme.

C:\VgServer\xampp\htdocs\ca-ccx\web>drush version
 Drush Version   :  6.0


C:\VgServer\xampp\htdocs\ca-ccx\web>drush omega-wizard
Please enter the name of the new sub-theme [Omega Subtheme]: Omega ca_ccx
Please enter a machine-readable name for your new theme [omega_ca_ccx]:
Please choose a base theme for your new theme
 [0]  :  Cancel

 [1]  :  Ohm (Subtheme of Omega) - Omega based demonstration theme. Serves as a

         best-practice reference for the Omega documentation. Ohm will be

         constantly updated as best practice evolves so shouldn't be used in

         production.

 [2]  :  Omega - A powerful HTML5 base theme framework utilizing tools like

         Sass, Compass, Grunt, Bower, Ruby Version Manager, Bundler and more.
1
Please choose a starterkit for your new theme
 [0]  :  Cancel
 [1]  :  Default: Comes with a well organized Sass setup with heavy use of
         partials. (Provided by Omega)
1
Please choose a destination. This is where your sub-theme will be placed
Please choose a destination type.
 [0]  :  Cancel
 [1]  :  Site (e.g. 'all' or 'example.com')
 [2]  :  Installation profile
 [3]  :  Parent theme
1
Please choose a site.
 [0]  :  Cancel
 [1]  :  all
1
Do you want to keep the starterkit's readme files? (y/n): y
Do you want to enable your new theme? (y/n): y
Do you want to make your new theme the default theme? (y/n): y
Beginning to build libraries.make.                                          [ok]

Make new site in the current directory? (y/n): y
selectivizr downloaded from                                                 [ok]

https://github.com/fubhy/selectivizr/archive/master.zip.
Unable to unzip                                                          [error]

C:\Users\Valerie\AppData\Local\Temp/make_tmp_1382749364_526b14b4bad94/master.zip
.
html5shiv downloaded from                                                   [ok]

https://github.com/fubhy/html5shiv/archive/master.zip.
Unable to unzip                                                          [error]

C:\Users\Valerie\AppData\Local\Temp/make_tmp_1382749364_526b14b4bad94/master.zip
.
respond downloaded from                                                     [ok]

https://github.com/fubhy/respond/archive/master.zip.
Unable to unzip                                                          [error]

C:\Users\Valerie\AppData\Local\Temp/make_tmp_1382749364_526b14b4bad94/master.zip
.
matchmedia downloaded from                                                  [ok]

https://github.com/fubhy/matchmedia/archive/master.zip.
Unable to unzip                                                          [error]

C:\Users\Valerie\AppData\Local\Temp/make_tmp_1382749364_526b14b4bad94/master.zip
.
pie downloaded from https://github.com/fubhy/pie/archive/master.zip.        [ok]

Unable to unzip                                                          [error]

C:\Users\Valerie\AppData\Local\Temp/make_tmp_1382749364_526b14b4bad94/master.zip
.
You have successfully created the theme Omega ca_ccx (omega_ca_ccx)    [success]

in sites/all/themes.

C:\VgServer\xampp\htdocs\ca-ccx\web>

I have made the guess that I can take the downloads from those locations and unzip them into the libraries folder. I guess I'll know pretty soon whether or not that's the right guess.....

Comments

Comment #1

fubhy CreditAttribution: fubhy commented 26 October 2013 at 09:04

Title:	omega-wizard doesn't unzip libraries	» drush make fails when trying to unzip libraries on Windows 7
Version:	7.x-4.0	» 7.x-4.x-dev
Priority:	Major	» Normal
Status:	Active	» Closed (duplicate)

Did you check the Drush issue queue for this? The libraries download runs through "drush make". An error while extracting the archives is an error during drush make and therefore belongs into the Drush issue queue.

You can file an issue against Drush on github: https://github.com/drush-ops/drush/issues

Anyways, your guess is right.. You can put those libraries into YOURTHEME/libraries manually. No problem.

I am closing this as a duplicate as I cannot move it to the Drush issue queue directly since Drush has been moved to github. Please open an issue on github if this problem persists.

Comment #2

vgriffin CreditAttribution: vgriffin commented 27 October 2013 at 03:19

How can I possibly know where the problem comes from or where to post the error? Because users are simply following steps in the Omega, we should be able to file the report against the directions we are following. A statement in the document telling us where to report errors against omega-wizard. The problem would recur if I ran the same request again, which I don't plan on doing.

I had put each top-level directory into site/all/libraries. Is that a problem? It shouldn't be as people

Because we are trying to make a sub-theme from several sources, it would be useful to have a list of the files we should see so we can validate the installation, particularly the libraries.

Comment #3

vgriffin CreditAttribution: vgriffin commented 27 October 2013 at 03:19

I had put each top-level directory into site/all/libraries. Is that a problem? It shouldn't be as people

Because we are trying to make a sub-theme from several sources, it would be useful to have a list of the files we should see so we can validate the installation, particularly the libraries.

Comment #4

fubhy CreditAttribution: fubhy commented 27 October 2013 at 09:19

How can I possibly know where the problem comes from or where to post the error? Because users are simply following steps in the Omega, we should be able to file the report against the directions we are following.

You can't unless you take a look at the code. That's why I told you in my reply how this works internally and where the right place to file this bug is. Again: Omega just invokes "drush make" which is a core Drush command. If it fails to extract archives for you that means that something is wrong with the Drush command. Normally I would have relocated the issue to the Drush issue queue but since Drush is on github now I can't. Hence why I requested that you open an issue in the Drush issue queue on github so they can assist you.

I had put each top-level directory into site/all/libraries. Is that a problem? It shouldn't be as people

No, sites/all/libraries is fine too. There are multiple valid library sources (sites/all/libraries or profiles/YOURPROFILE/libraries or sites/yoursite.com/libraries or sites/all/themes/YOURTHEME/libraries). It just has to be in one of them. The only difference between those library sources is the inheritance. If you place it in your theme's libraries folder then it will only be used by that specific theme. If you place it in sites/all/libraries for example it can be re-used by other themes too.

Because we are trying to make a sub-theme from several sources, it would be useful to have a list of the files we should see so we can validate the installation, particularly the libraries.

All of the libraries are optional. Only you know which ones you want to use. Do you plan to use the Selectivizr polyfill? Okay, download it. Do you want to use HTML5SHIV (recommended)? Okay, download it! It's up to you and which libraries you plan on using. Omega itself has no hard dependencies on either of them.

Comment #5

fubhy CreditAttribution: fubhy commented 27 October 2013 at 09:23

A statement in the document telling us where to report errors against omega-wizard. The problem would recur if I ran the same request again, which I don't plan on doing.

I can't possibly predict every single error that may occur all across Drupal and list them in the Omega Documentation with the proper places where to go in order to report them. It's simply not possible. The way this can only work is: You encounter an error => You file a bug report against the thing that you think caused the error => If it's the right place (e.g. if you file it against Omega and it's indeed an Omega problem) I can fix it => If it's not the right place (e.g. this case) I can point you to the right issue queue or move the issue myself. In this case I can't do that because the issue queue we are talking about is not hosted on drupal.org

Comment #6

vgriffin CreditAttribution: vgriffin commented 2 November 2013 at 03:30

Suggesting IN THE DOCUMENTATION that users consult the drush queue WHICH IS ESSENTIALLY HIDDEN from people trying to follow your directions would have been very helpful, especially for people who have not used drush. I'm not saying that you should fix things in the drush queue. The documentation should simply tell us where to look for things that go wrong using the tool, without which we cannot install a sub-theme. Alternately, for use of the tool, you could suggest that we file the issue in both places. I'm not going to comment further on this. The only way I can transfer info to the drush queue is by copying my initial comments from this report to that queue, which I may do.