rickgaribay.net

Space shuttles aren't built for rocket scientists, they're built for astronauts. The goal isn't the ship, its the moon.
posts - 303, comments - 180, trackbacks - 35

My Links

News

Where's Rick?


AgileAlliance deliver:Agile 2019- 4/29
Desert Code Camp, PHX - 10/11
VS Live Austin, TX - 6/3
VS Live SF - 6/17


About Me
Hands on leader, developer, architect specializing in the design and delivery of distributed systems in lean, agile environments with an emphasis in continuous improvement across people, process and technology. Speaker and published author with 18 years' experience leading the delivery of large and/or complex, high-impact distributed solutions in Retail, Intelligent Transportation, and Gaming & Hospitality.

I'm currently a Principal Engineer at Amazon, within the North America Consumer organization leading our global listings strategy that enable bulk and non-bulk listing experiences for our WW Selling Partners via apps, devices and APIs.

Full bio

Note: All postings on this site are my own and don’t necessarily represent the views of my employer.



Check out my publications on Amazon Kindle!





Archives

Post Categories

Published Works

Tuesday, January 14, 2014

fatal: could not read Username for 'https://github.com': No such file or directory

Git logo

If all of a sudden you are unable to clone or push repos and you recently downloaded the latest version of msysgit (AKA Git for Windows) you are not alone.

As discussed here and confirmed here, this appears to be a bug in the 1.85.2 build, which consequently is the latest available build linking from github, which likely means that thousands of developers since the release of 1.85.2 are impacted.

3 options, from simplest on down:

1. Uninstall 1.85.2 and downgrade to a previous version.

2. Switch over to SSH instead.

3. Apply the patch “discussed” here.

Personally, I chose 2 out of sheer laziness and opted out of 3 due to a general lack of motivation resulting from what appears to be more interest in pedantic redirection and passive aggressive replies from project representation than communication and spirit of collaboration (which is supposed to be what OSS is all about).

Hopefully this will be fixed in a new build soon. Hope this helps.

posted @ Tuesday, January 14, 2014 5:05 PM | Feedback (2) | Filed Under [ git ]

Powered by: