Provide pywinrm RPM in Fedora/EPEL repos

Hi @diyan,

I find pywinrm an awesome library to interact with Windows, that’s why I’m using it as part of a pull request to oz (https://github.com/clalancette/oz/pull/174) to implement the customization phase for Windows guests.

Unfortunately, one of the stoppers for the PR is that pywinrm is not packaged in the Fedora/EPEL repositories, where the oz RPM and its dependencies are available.

Said that, what do you think about adding support to package pywinrm as an RPM make it available in Fedora/EPEL? (more info: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers)

Thanks!

[hogarthj]

Hi guys - I’ve picked up package maintenance of this in Fedora

It’s now in the testing repos for F23+ and EPEL7 … I’m working on EPEL6 as well but tests are failing there and until I’ve got to the bottom of why I’m not prepared to push it.

If there’s any idea why it’s failing it would help 😃

https://kojipkgs.fedoraproject.org//work/tasks/7477/16197477/build.log

Note that RHEL/CentOS6 has python-requests 2.6.0-3 and I’m not sure right now what, if anything, RH has backported from later versions. I note that the setup.py specifies a 2.9.1 minimum - is there a specific reason for this?

As python-requests is in the base repositories we cannot have a later version in EPEL and if this is a hard dependency that cannot be worked around then python-winrm can’t be packaged for EPEL6 - though users can use a Fedora or EPEL7 control system where it does work.

[hogarthj]

We do have the concept of recommends and suggests (the former installed by default when dnf install python-winrm is used and the latter not) … though that isn’t supported in EPEL and is infrequently used as “weak dependencies” were only recently added to Fedora.

The README is also copied over so users can see there if they want kerberos they shoudl install the requests-kerberos python module.

That said, the README you guys have specifies using pip for it which naturally we don’t ‘support’ on Fedora/EPEL as it has a nasty tendency to mess with RPM install stuff.

What I’ll probably do in this release is add a README.fedora with fedora/epel specific stuff like I do with the owncloud packages and mention installing python{2,3}-requests-kerberos there for kerberos usage.

Since we ship compiled stuff in the RPMs there’s no need for gcc, python-devel etc then on fedora systems to make use of kerberos.

As it stands right now $user does a dnf install python-winrm (for the python2 version or python3-winrm for the py3 one) and then they have that installed ready to use with ansible or whatever.

If they want kerberos rather than the ntlm3 auth then they’ll need to install python-requests-kerberos manually and then configure whatever they need to make use of their tokens.