From owner-freebsd-java@FreeBSD.ORG Mon Oct 27 01:00:03 2014 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6E48DFF; Mon, 27 Oct 2014 01:00:02 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F4E9DD2; Mon, 27 Oct 2014 01:00:02 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id p9so4880453lbv.19 for ; Sun, 26 Oct 2014 17:59:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fdybjZFqgPZJTVWoog1hgpYpxjzj+0x1PoD1UZNYYrE=; b=NvFirNRa60Eyd/hienwJ/r2ts+VTJHjFRdqq459dFGZJ4CugPyMw4trePraQ0jCW3I w+RzD/U2X2fGHbQdbp+VsAmYidHbf/A52qi+8L/D3FRRSI9JSQCV5kcJol/mGYX/cIOe WpqBnoCHMvP0Y7gSJGgK7Ang5rWSA4E5lbyCY7qZyraAfxlSm2OLkir1FNReIcEHIKnZ d7QE00SLfBNW5oJKk5EiAf3hxW6UEkzhlEeDbbRM3rw/yUSqv0Q4ByxAR4jmGW5NRjRZ vIBK7tTcuv9axmDkdjfh0scHcqsmxUD9A4bKB/IF+qHIjZYJ4AmQIk29plA9n/bQTSnx GVYQ== MIME-Version: 1.0 X-Received: by 10.152.21.226 with SMTP id y2mr19989216lae.70.1414371598946; Sun, 26 Oct 2014 17:59:58 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.84.197 with HTTP; Sun, 26 Oct 2014 17:59:58 -0700 (PDT) In-Reply-To: References: <540C2CEC.3020303@ury.york.ac.uk> Date: Sun, 26 Oct 2014 17:59:58 -0700 X-Google-Sender-Auth: FqePAOpE3HUs5mtDcn70pULQ5Mw Message-ID: Subject: Re: Jenkins and PAM problem with JNA 4.1 From: Craig Rodrigues To: Anthony Williams Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "jenkins-admin@freebsd.org" , "freebsd-java@freebsd.org" X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 01:00:03 -0000 On Sun, Oct 26, 2014 at 4:38 PM, Anthony Williams wrote: > > Craig, > > Sorry for the delay in responding - my university course has been taking > up much of my time and I'm finally catching up with emails. > > I'm glad that I could be of use in getting this issue fixed - it's been > interesting learning bits of maven and Jenkins along the way. > > I'll go ahead and close PR https://github.com/jenkinsci/jna/pull/2 once > your fix hits the main release (1.586 you think?). > > Thanks, > Anthony Anthony, You can go ahead and close out your pull request. I have confirmed that my fix to update Jenkins to JNA 4.1 is in the Jenkins code and will be in 1.586. It is in the 1.586 changelog. See: http://jenkins-ci.org/changelog (Click on Upcoming Changes) I also downloaded a Jenkins nightly build and confirmed that this fixes libpam4j on FreeBSD. With this fix, I can now use Unix logins with Jenkins. I've closed out these two Jenkins bugs: "libpam4j problem under FreeBSD 10" https://issues.jenkins-ci.org/browse/JENKINS-21507 "Update jna from 3.3.0-jenkins to 4.1.0 (or newer)" https://issues.jenkins-ci.org/browse/JENKINS-24521 I took your initial patch to JNA version 3.3.0-jenkins, and I went one step further and submitted fixes to upgrade Jenkins core to use JNA version 4.1. JNA version 4.1 had fixes for FreeBSD, but it turns out that the newer JNA had fixes for Windows, Linux/arm, Linux/powerpc and other platforms. I think the Jenkins community was more interested in that, than fixing FreeBSD, but at least by fixing Jenkins for FreeBSD, I fixed other platforms also. :) The Jenkins developers are very nice people, and were quite easy to work with in terms of accepting patches. On the freebsd-testing@freebsd.org mail alias, we are trying to get more people to help with testing FreeBSD. We need help with Jenkins and Java, Python scripting, libvirt, devops/systems administration, libvirt, and writing test scripts. Thank you very much for pointing out the problem and suggesting a fix. Your contribution really helped a lot. I hope that you have time to keep involved with FreeBSD and can help out with future things. If you have any time or interest in helping out in any of the areas I mentioned for testing, please feel free to contribute! Thanks again! -- Craig