Git install on older versions of Mac OS X broken (again) #196
Comments
|
@eddelbuettel suggests to use Docker:
|
|
We've discussed VMs for our students at length in the past. They solve
some problems, but introduce others, so we're going to stick to native
installs for the foreseeable future.
|
|
@willingc used the installers from sourceforge [1]. I was teaching while @iglpdc and @mckays630 were dealing with the git installation problems but I believe the installer from sourceforge no longer work? [1] http://sourceforge.net/projects/git-osx-installer/files/?source=navbar0 |
|
If you download the appropriate installer, "Snow Leopard" for 10.7 and 10.8 (even though Snow Leopard is 10.6) it has worked for me in the past. |
|
@iglpdc @mckays630 @chendaniely Here's also a github repo for the git-osx-installer files: https://github.com/timcharper/git_osx_installer Out of curiosity, were you trying to use the installers for the most recent version of git when using the git-osx-installers? I found at the SWC event at UCSD that we needed to use an older version of git (1.8) versus 2.x to get git working without huge headaches. Here's what I documented at OpenHatch after another event re: git on osx: https://openhatch.org/wiki/Open_Source_Comes_to_Campus/Curriculum/Laptop_setup/OSX_git I will ask around at PyCon if we can set up easily test envs for the different OSX versions and installs. I've been looking at doing this for OpenHatch anyway. |
|
I opened timcharper/git_osx_installer#43 just now to point the maintainer at this discussion. If anyone has additional details to add, especially which version of Git was giving the "Lazy symbol" error, that would probably be helpful to add either here or there. |
|
Thanks @jiffyclub. |
|
On Fri, Apr 03, 2015 at 10:00:21AM -0700, Matt Davis wrote:
There's earlier “Lazy symbol” discussion in swcarpentry/DEPRECATED-bc#595, |
|
On Fri, Apr 03, 2015 at 10:22:06AM -0700, W. Trevor King wrote:
The wiki has been migrated to 1, but it still lists the “Lazy |
|
@jduckles, @willingc I think that the installer working or not still depends on whether you have Xcode installed. Our setup instructions [1] already link to the correct installer for each version. Also, I found the problem pretty much in any workshop I taught in the last 6 months (I'm almost sure to say that is 10.8.5 every time). Having said that, I didn't actually check that the students were using the correct installer, so it maybe the problem gets fixed now if you use the correct installer, and we were just fixing it in the wrong way (by installing Xcode). Actually, this particular student in the last workshop didn't seem much aware of which version she was using. To fix this, I'm making two changes:
This brings me to @eddelbuettel 's point. There are many reasons for having an outdated OS at our workshops: some students borrow one; some others get one at work, but they don't have admin rights; some have very old laptops that cannot be updated, and most don't think it is necessary. This girl had a very strong point: she bought her laptop a little over a year ago so "it was brand new" so "why update something new". As far as for Docker, I think it cannot beat our current setup, at least in simplicity for a novice learner. You just need 3 one-click installers (git-bash, swc-win-installer, and Anaconda for Win, or the git-osx-installer and/or Xcode, and Anaconda for Mac) to install all the software needed for a workshop. |
|
@iglpdc I beg to differ but I won'd be belabour it. This is a somewhat complicated issue:
|
|
@iglpdc Yes, the student would need to have xcode or the xcode command line tools (a much smaller download) installed. I agree with the suggestion on how to check OS version, which installer to choose, how to install xcode command line tools (if needed) to the setup instructions for OS X. cc/@jdunckles Instructions for setting up xcode command line tools (I think it can also be brew installed): My overall view is that checking the OS X version pre setup would minimize the setup frustration for users. The burden shouldn't be on the student or workshop helpers to guess what might work. Honestly, I dread the set up portion of any workshop (SWC or otherwise). |
|
@eddelbuettel I like Docker. I think that it may be helpful for testing the setup instructions. FWIW I have been at several workshops where |
|
@willingc Agreed re the current IP address issue. Had that too when I once ran, just as a test, boot2docker on my work pc to serve the RStudio Server container: that worked like a charm and stayed up for several months once I knew what the address was. Could do the same for IPython and RStudio Server in one container as I suggested several months back. But all suggestions have issues and nothing dominates so we're back to individual preferences. |
|
@eddelbuettel , @willingc I like Docker too. I think it is a great solution for many development and deployment problems. I just think that some people in our workshops (say, those that cannot/don't update Mac OS X using the App Store) won't be able to complete the setup by themselves. This would put the burden of finishing the setup on our instructors and many of us are also fairly new to the VM world. It maybe be good though, to have Docker containers set up for situations when all is going south, like with this girl in my last workshop. In this case, we could provide instructions for instructors only, saying "ok, all is going wrong, before giving up, you could try to install Docker". Apart from being a nice save, it could be a good way to make our instructors more comfortable with Docker and smooth a possible transition in the future. |
|
@eddelbuettel Yeah, individual preferences. I would do it all in JupyterHub ;) Sometimes, the best path is simply do one's best to make whatever path most pleasant for the end user. As a helper in the moment, I have had folks use wakari.io, tmpnb, or my own laptop (not my preferred option) to get them productive. Which begs the question has anyone tried running this on a Chromebook with or without crouton? The newest version of crouton is quite good (http://www.itworld.com/article/2891142/how-to-run-linux-and-chrome-os-on-your-chromebook.html). I've considered taking one of my Chromebooks to workshops as a backup. |
|
@iglpdc +1 to prior comment 🍰 😎 |
|
FYI @jhamrick wrote a detailed and excellent post on using JupyterHub for teaching (https://developer.rackspace.com/blog/deploying-jupyterhub-for-education/). Not suggesting as a solution for this issue now. Just passing along as an excellent article to those that may be interested. |
|
IMHO, docker solves a different problem than this, which is that of..., eh, a container! In many cases, just providing a common namespace via environment-modules enjoy, F. |
|
On Fri, Apr 03, 2015 at 10:26:48AM -0700, W. Trevor King wrote:
Today at UW we had success following @willingc's suggestion to use |
|
@wking, which version of Git did you install? |
|
On Fri, Apr 10, 2015 at 09:59:30AM -0700, Matt Davis wrote:
git-2.2.1-intel-universal-snow-leopard.dmg. I expect any of the |
|
Okay, that's at odds with @willingc's comment above, but good to have a data point. It's definitely the stated goal of the git-osx-installer that it should work without XCode. |
|
One confounding factor to watch out for is that sometimes people may have installed the OS X command line tools without having installed Xcode. That usually fixes all these problems, so something to watch out for. Not having Xcode isn't always the whole story. |
|
On Fri, Apr 10, 2015 at 10:18:06AM -0700, Matt Davis wrote:
I'll try to check this over the break. I don't use OS X; is there a |
|
Check for |
|
On Fri, Apr 10, 2015 at 10:26:49AM -0700, Matt Davis wrote:
He has nothing at either path, and doesn't remember installing |
|
Cool, seems like good news for it working without Xcode, then. |
|
Great job. Excellent point by Matt on check to see if the command line On 4/10/15 4:05 PM, Matt Davis wrote:
Carol Willing |
|
Is it just that the operating system is installing a stub now? Maybe the fix is to update the instructions to get that stub moved out of the way? |
|
@timcharper, this is Mac OS 10.8, in which I don't think Apple had stubs for command line tools. |
|
Did you use the Mavericks installer, or Snow Leopard one?
Mavericks (10.9) > Mountain Lion (10.8)
|
|
Good point, our instructions currently are giving bad advice about what to download for which Mac OS version. |
|
I've opened swcarpentry/DEPRECATED-site#931 to fix our instructions. It's possible that's what's been causing this problem, though I'm not sure we have enough information from our workshops to say one way or the other. |
|
Will be checking this later tonight, but the issue seems to be documented here [1]. Essentially there is a git wrapper built in OSX that needs xcode installed in You need to run [1] http://superuser.com/questions/666086/issues-installing-git-under-mac-os-x-10-9-mavericks |
|
not sure if this was stated anywhere, but the snowleopard installer is needed on mountain lion. |
|
On Wed, May 13, 2015 at 10:16:51AM -0700, Daniel Chen wrote:
It's stated on the git-osx-installer download page 1, under “Which |
|
I test the git os x installer in a fresh VM; it works. Thanks, @chendaniely, for pointing out the need to use a installer for a version of the operating system that is or predates your present OS. You'd think people could use common sense here, or read the instructions, but.... there are always those... |
|
from the BU workshop with @mkcor, the calling git from |
|
See #204 where I fix our installation instructions to make clear which version of the installer is needed depending on your version of OS X. |
|
I'm closing this issue based on #204. Please reopen it if needed. |
secure hyperlinks to pre-empt server-side HTTPS redirects
The text was updated successfully, but these errors were encountered: