<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> On 08/20/2010 04:20 PM, Rob Crittenden wrote: <blockquote cite="mid:4C6EE395.2070908@redhat.com" type="cite">F-14 introduced a number of changes including an updated krb5 server package and python 2.7. In krb5 the binaries moved from /usr/kerberos/* to /usr/* so some paths need to be adjusted. What I did was include a PATH in the env that covers both of these locations. Python 2.7 made some changes to xmlrpclib and httplib as well that aren't quite backwards compatible. I added some specific version checks so we can do the right thing internally. This is ticket 155 rob <pre wrap=""> <fieldset class="mimeAttachmentHeader"></fieldset> _______________________________________________ Freeipa-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Freeipa-devel@redhat.com">Freeipa-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/freeipa-devel">https://www.redhat.com/mailman/listinfo/freeipa-devel</a></pre> </blockquote> I think that in the explicit path construction you do vic of line 115, you want the kerberos subpath libraries to come before /usr/bin, otherwise it will find the non-kerberized versions of the function. I realize that testing on the Major/Minor is functional, but wouldn't it make more sense to test for the existanec of the newer call, use that if it was avaiable, as opposed to gating on version number? Seems like it would be less prone to breakage. </body> </html>