Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

SQLite and make not installed on Windows 7 #41

Open
iglpdc opened this issue Jan 12, 2016 · 19 comments
Open

SQLite and make not installed on Windows 7 #41

iglpdc opened this issue Jan 12, 2016 · 19 comments
Assignees

Comments

@iglpdc
Copy link

iglpdc commented Jan 12, 2016

I'm in a workshop with a machine that has Windows 7 Home Edition Service Pack 1 32-bit machine. The installer installs nano and the rest of tools but neither SQLite nor make.

@iglpdc
Copy link
Author

iglpdc commented Jan 12, 2016

Maybe related to #34

@ethanwhite
Copy link
Contributor

Can you report the output of ls ~/.swc and cat .bash_profile?

@iglpdc
Copy link
Author

iglpdc commented Jan 12, 2016

error

We get this error after running the installer. There is no ./swc or .bash_profile in the home dir.

@iglpdc
Copy link
Author

iglpdc commented Jan 12, 2016

Ok, so the story is not exactly as I told it. The installer didn't finish running (giving the error above) and nothing was installed (so no ~/.swc or .bash_profile were created.

We fix it by creating these files by hand, downloading the binaries from the website in the installer, and adding ./swc to the path in .bash_profile.

@wking
Copy link
Contributor

wking commented Jan 12, 2016

On Tue, Jan 12, 2016 at 09:52:42AM -0800, Ivan Gonzalez wrote:

The installer didn't finish running (giving the error above) and
nothing was installed (so no ~/.swc or .bash_profile were
created.

That sounds like “the installer crashed before accomplishing anything
at all”. My guess is that we need a 32-bit build of the Inno Setup
installer. Until then, folks hitting this on machines with Python
installed should be able to download the Python script and run it from
a terminal.

@ethanwhite
Copy link
Contributor

I would think if this was a 32-bit vs. 64-bit issue we'd have run into it by now, but I could be wrong.

My looking around on this suggested it might just be an edge case with a system that has some configuration issue somewhere.

If someone can test on another 32-bit system and confirm one way or the other that would be helpful.

@MelissaJia
Copy link

I'm having the same problem also working on a 32 bit system but had no problem with 64 utilizing the same software

@embray
Copy link
Contributor

embray commented Apr 14, 2016

Just to be sure, do we support a 32-bit version of the installer?

@MelissaJia
Copy link

Possibly but not an easy to use one like swcarpentryinstaller.exe. However, you can use sqlite via the firefox addon without installing sqlite first.

@justbennet
Copy link

The installer doesn't seem to add either nano nor make to the GitBash shell's prompt nor to the Windows system path. Files get installed into ~/.swc/[bin|lib|share] and I can set the path manually and things appear to work.

Should ~/.swc/lib/nano and ~/.swc/lib/make/bin get added to the WIndows PATH, or a .profile or .bash_profile get created in the user's home directory?

@wking
Copy link
Contributor

wking commented Apr 26, 2016

On Tue, Apr 26, 2016 at 01:19:44PM -0700, justbennet wrote:
“Should ~/.swc/lib/nano and ~/.swc/lib/make/bin get added to the
WIndows PATH, or a .profile or .bash_profile get created in the
user's home directory?”

Yes 1. If you have ~/.swc but no changes to ~/.bash_profile, I
expect the installer crashed before completing.

@justbennet
Copy link

Yes, it does seem to crash. Running from a command window that doesn't close gives me this

C:\Program Files (x86)\swc-installer>swc-windows-installer.exe
Preparing your Software Carpentry awesomeness!
installer version 0.3
create nosetests entrypoint C:\Users\hayden.swc\bin\nosetests
existing installation at C:\Users\hayden.swc\lib\make
existing installation at C:\Users\hayden.swc\lib\make
existing installation at C:\Users\hayden.swc\lib\nano
existing installation at C:\Users\hayden.swc\share\nanorc
Traceback (most recent call last):
File "swc-windows-installer.py", line 326, in
File "swc-windows-installer.py", line 295, in main
File "swc-windows-installer.py", line 202, in install_sqlite
File "swc-windows-installer.py", line 141, in zip_install
File "swc-windows-installer.py", line 72, in download
File "urllib2.pyc", line 154, in urlopen
File "urllib2.pyc", line 431, in open
File "urllib2.pyc", line 449, in _open
File "urllib2.pyc", line 409, in _call_chain
File "urllib2.pyc", line 1240, in https_open
File "urllib2.pyc", line 1197, in do_open
urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate ve
rify failed (_ssl.c:590)>

@wking
Copy link
Contributor

wking commented Apr 26, 2016 via email

@justbennet
Copy link

I had no issues when I manually went to the URL from the source code using Firefox on the same Windows VM.

@wking
Copy link
Contributor

wking commented Apr 26, 2016

On Tue, Apr 26, 2016 at 02:14:47PM -0700, justbennet wrote:
“I had no issues when I manually went to the URL from the source code
using Firefox on the same Windows VM.”

I think Firefox uses its own certificate store, while Python is using
a system certificate store 1. In a Python 3.4+ shell, can you run:

$ python3
Python 3.4.3 (default, Jan 29 2016, 13:29:49)
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.

import ssl
context = ssl.create_default_context()
context.get_ca_certs()

or similar? Or you can poke around in the CA and ROOT system stores
referenced by 1.

@carpenterbennet
Copy link

I will try that tomorrow or the next day.

@justbennet
Copy link

Yes, Comodo was not present. After a couple of consultations with Google, I found and installed the certificates to the system store. This is good to know.

How likely is this issue to crop up? With @wking's guidance, I got through it, but I would probably not have done the morning of a workshop.

I am only testing this because we are offering people a chance to come get help with installing the software prior to a workshop tomorrow, and I am not a native Windows speaker.

wking added a commit that referenced this issue Apr 28, 2016
This avoids issues with the user's certificate store [1] by skipping
SSL.  That means that middlemen will know you're asking for the shell
zip, but they'd probably be able to guess something similar from the
size of the response payload anyway.  All of our other fetches are
already over HTTP, and we don't have to worry about verifying the
server because we have cryptographically-strong hashes for verifying
the file they sent us.

[1]: #41 (comment)
wking added a commit that referenced this issue Apr 28, 2016
This avoids issues with the user's certificate store [1] by skipping
TLS.  That means that middlemen will know you're asking for the shell
zip, but they'd probably be able to guess something similar from the
size of the response payload anyway.  All of our other fetches are
already over HTTP, and we don't have to worry about verifying the
server because we have cryptographically-strong hashes for verifying
the file they sent us.

[1]: #41 (comment)
@wking
Copy link
Contributor

wking commented Apr 28, 2016

On Thu, Apr 28, 2016 at 02:17:49PM -0700, justbennet wrote:

I got through it, but I would probably not have done the morning of
a workshop.

Fix floated in #48.

@debpaul
Copy link

debpaul commented Nov 23, 2016

I have the same issue trying to install on an old Windows 7 Enterprise. The installer doesn't finish, so I get sqlite not found. This is a win 64-bit machine.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants