Re: [ansible-project] Ansible 2.0 -- the "new" correct way to update??

2016-01-20 Thread Rilindo Foster
I switched over to Homebrew to install current release of Ansible (after 
removing the prior release with pip).
--
Rilindo Foster


On Jan 18, 2016, at 2:07 PM, Chris Short 
mailto:ch...@chrisshort.net>> wrote:

It seems to me that the issue revolves around upgrading setuptools. I'm totally 
okay with uninstalling and reinstalling Ansible but I am curious about "better" 
ways of upgrading if people would like to share them.

On Friday, January 15, 2016 at 11:29:58 AM UTC-5, Slim Slam wrote:
As you may recall, I had to uninstall Ansible 1.9.4 in order to install Ansible 
2.0.0.0. But now, upgrading to Ansible 2.0.0.2 succeeds but has no effect.
I'm on MacOSX El Capitan (10.11.2)

$ ansible --version
ansible 2.0.0.0
  config file =
  configured module search path = Default w/o overrides
$

$ sudo -H pip install --upgrade ansible --user python
Password:
Collecting ansible
  Downloading ansible-2.0.0.2.tar.gz (1.5MB)
100% || 1.5MB 258kB/s
Requirement already up-to-date: python in 
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload
Requirement already up-to-date: paramiko in /Library/Python/2.7/site-packages 
(from ansible)
Requirement already up-to-date: jinja2 in /Library/Python/2.7/site-packages 
(from ansible)
Requirement already up-to-date: PyYAML in /Library/Python/2.7/site-packages 
(from ansible)
Collecting setuptools (from ansible)
  Using cached setuptools-19.2-py2.py3-none-any.whl
Requirement already up-to-date: pycrypto>=2.6 in 
/Library/Python/2.7/site-packages (from ansible)
Requirement already up-to-date: ecdsa>=0.11 in 
/Library/Python/2.7/site-packages (from paramiko->ansible)
Requirement already up-to-date: MarkupSafe in /Library/Python/2.7/site-packages 
(from jinja2->ansible)
Installing collected packages: setuptools, ansible
  Running setup.py install for ansible
Successfully installed ansible-2.0.0.2 setuptools-1.1.6
$


$ ansible --version
ansible 2.0.0.0
  config file =
  configured module search path = Default w/o overrides
$

What is the correct way to handle updates going forward?

--
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to 
ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/3e8b46dc-f085-4a7b-a855-440403543cd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/02386FE7-3751-410D-B0DB-55A22ABD8830%40connectedhealth.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ansible-project] Ansible 2.0 -- the "new" correct way to update??

2016-01-15 Thread Jeff
There is no need to use sudo with --user. You should pick one or the other.

sudo will install as root into /usr/local/bin, whereas --user installed 
into your home directory under .local/

On Friday, January 15, 2016 at 10:39:29 AM UTC-6, Slim Slam wrote:
>
> Ok, so going forward, it appears that I need to uninstall the old version, 
> and then install the new version.
>
> On Friday, January 15, 2016 at 10:34:26 AM UTC-6, Brian Coca wrote:
>>
>> The problem is with a new 'protection' in OS X 'el capitan' which 
>> breaks the pip update, this is not restricted to Ansible but to any 
>> pip package you install with sudo. 
>>
>> https://github.com/ansible/ansible/issues/13820 
>>
>>
>> -- 
>> Brian Coca 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/280e033a-ed24-4db3-b697-396a396a4002%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ansible-project] Ansible 2.0 -- the "new" correct way to update??

2016-01-15 Thread Slim Slam
Ok, so going forward, it appears that I need to uninstall the old version, 
and then install the new version.

On Friday, January 15, 2016 at 10:34:26 AM UTC-6, Brian Coca wrote:
>
> The problem is with a new 'protection' in OS X 'el capitan' which 
> breaks the pip update, this is not restricted to Ansible but to any 
> pip package you install with sudo. 
>
> https://github.com/ansible/ansible/issues/13820 
>
>
> -- 
> Brian Coca 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/9fcba249-f066-4903-9e79-c09327a30ab0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ansible-project] Ansible 2.0 -- the "new" correct way to update??

2016-01-15 Thread Brian Coca
The problem is with a new 'protection' in OS X 'el capitan' which
breaks the pip update, this is not restricted to Ansible but to any
pip package you install with sudo.

https://github.com/ansible/ansible/issues/13820


-- 
Brian Coca

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAJ5XC8kK64NgomMDpoz8Dw6LrbstMh%2BSrTpjZQd_nrUK6%2Bqktw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-project] Ansible 2.0 -- the "new" correct way to update??

2016-01-15 Thread Slim Slam
As you may recall, I had to uninstall Ansible 1.9.4 in order to install 
Ansible 2.0.0.0. But now, upgrading to Ansible 2.0.0.2 succeeds but has no 
effect.
I'm on MacOSX El Capitan (10.11.2)

$ ansible --version
ansible 2.0.0.0
  config file =
  configured module search path = Default w/o overrides
$

$ sudo -H pip install --upgrade ansible --user python
Password:
Collecting ansible
  Downloading ansible-2.0.0.2.tar.gz (1.5MB)
100% || 1.5MB 258kB/s
Requirement already up-to-date: python in /System/Library/Frameworks/Python.
framework/Versions/2.7/lib/python2.7/lib-dynload
Requirement already up-to-date: paramiko in /Library/Python/2.7/site-packages 
(from ansible)
Requirement already up-to-date: jinja2 in /Library/Python/2.7/site-packages 
(from ansible)
Requirement already up-to-date: PyYAML in /Library/Python/2.7/site-packages 
(from ansible)
Collecting setuptools (from ansible)
  Using cached setuptools-19.2-py2.py3-none-any.whl
Requirement already up-to-date: pycrypto>=2.6 in 
/Library/Python/2.7/site-packages 
(from ansible)
Requirement already up-to-date: ecdsa>=0.11 in 
/Library/Python/2.7/site-packages 
(from paramiko->ansible)
Requirement already up-to-date: MarkupSafe in /Library/Python/2.7/site-packages 
(from jinja2->ansible)
Installing collected packages: setuptools, ansible
  Running setup.py install for ansible
Successfully installed ansible-2.0.0.2 setuptools-1.1.6
$


$ ansible --version
ansible 2.0.0.0
  config file =
  configured module search path = Default w/o overrides
$

What is the correct way to handle updates going forward?

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a5cbe175-c357-4afc-a952-542cc61f7c2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.