I didn't run into this particular issue, but I grabbed the trunk version of alternatives.py from git, added it as my own module (after a file rename), and it seemed to work okay under the new name... seems like it's broken in 1.9.0.1 and I assume will be formally fixed in 1.9.0.2 or whatever is next.
On Saturday, April 11, 2015 at 2:29:13 PM UTC-4, Nico K. wrote: > > What I have noticed is that the installed version of alternatives.py does > not seem to match what's currently in github, the version installed by pip > seems to be many revisions back. > > I even went as far as removing ansible completely and reinstalling, making > sure there are no mix-ups with old installations and what have you, but a > clean pip install gives me ansible 1.9.0.1 with as it seems an outdated > version of the alternatives module. > > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9a64cdcf-a496-4234-ba9d-3f37e340e3ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
