On Wed, Dec 19, 2012 at 8:24 PM, David Boyce <d...@boyski.com> wrote: > http://lmgtfy.com/?q=python+_md5 > http://stackoverflow.com/questions/10306531/python-importerror-no-module-named-md5 >
Well, it certainly isn't obvious to me how this applied to my situation: It only talks about building python, and I did not compile the cygwin version of python. In addition, I already had libopenssl100 (1.0.1c-2) installed (which you can see in the cygcheck.out I sent). However, it turns out to be very close to what is actually wrong for me. Thinking that I *would* have to compile the python project to find out what was going wrong, I began installing a bunch of new packages (gcc, gdb, git, etc). Somewhere along the line I checked again and noticed that the md5 module was working! Figuring you guys would like to know exactly which package it was that fixed things for me, I diff'ed my new cygcheck output with my original, and uninstalled the new ones one-by-one until it broke again. The offending package is libopenssl098 (0.9.8x-1) (compat). And indeed with only that package added, mercurial works just fine now. (Yay) So, it appears there is a package dependency between python2.6 and libopenssl098 that is missing, but most people who need it get it installed via some other package-dependency path. Very minor bug; should I file a bug report somewhere? Or will someone here take it from here? Thanks, --Paul -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple