[08:21:22] <is_null> hi all, i don't understand how to use allow-external to install apt: http://dpaste.com/16HMDAE
[08:21:39] <is_null> using pip -v install apt --allow-external https://launchpad.net/python-apt/ --allow-external https://launchpad.net/python-apt/+download but it still complains: Not searching https://launchpad.net/python-apt/+download (from https://pypi.python.org/simple/apt/) for files because external urls are disallowed. Not searching https://launchpad.net/python-apt/ (from https://pypi.python.org/simple/apt/) for fi
[08:21:45] <is_null> les because external urls are disallowed.
[08:26:39] <is_null> tried --allow-unverified apt too
[10:03:13] <ionelmc> looks like someone needs to fix their package
[17:32:11] <Wooble> jwhite007: do you have a weird umask setting? :/
[17:35:28] <jwhite007> Wooble: hmm.. not sure. would that be in my env variables?
[17:36:19] <jwhite007> Wooble: wouldn't that have affected the initial install too?
[17:38:59] <Wooble> jwhite007: if it's read-only, that was on the initial install, no?
[17:39:56] <jwhite007> Wooble: the read-only is in the latest numpy tests downloaded today.
[17:40:13] <jwhite007> Wooble: it may be a repo error.
[17:42:31] <jwhite007> Wooble: i.e., the repo maintainer may have not set things up properly.
[17:54:39] <jwhite007> Wooble: the pip upgrade of numpy on my python3 works wonderfully. i bet that there's something wrong with the numpy pip repo for python2.
[17:57:25] <ionelmc> jwhite007: repo error? what's the result of running `umask`?
[17:58:11] <ionelmc> can never figure out them numbers
[19:33:11] <tubbo> hi guys, i'm trying to reinstall the 1pass utility with pip, and it seems to succeed but i get the "Symbol not found: _SSLv2_method" error when i try to run `1pass` in my shell. is there a way to get pip to rebuild native extensions so that m2crypto can sense the new location of my openssl libraries?
[19:33:22] <tubbo> this happened when i upgraded openssl/libssl
[19:36:09] <tdsmith> pip install -U --force-reinstall --no-use-wheel foo should do it. you aren't maybe on OS X 10.11 are you?
[19:37:03] <tubbo> tdsmith: no, brew just updated openssl out from under me when i upgraded phantomjs earlier today
[19:39:17] <tdsmith> if you've force-linked openssl you'll run into trouble because the relative position of /usr/lib and /usr/local/lib are different in the default os x include and linker search paths
[19:42:04] <tdsmith> if you didn't run brew cleanup, you can run brew switch openssl 1.0.0 (or whatever version you had previously installed; check with brew info openssl)
[20:03:16] <tdsmith> your best option is probably to run `brew edit openssl`, delete the line containing `no-ssl2`, and then `brew reinstall openssl --build-from-source`
[20:04:03] <tdsmith> assuming m2crypto builds against 1.0.2