From owner-freebsd-ports-bugs@freebsd.org Mon Jun 19 02:41:16 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59DF2D9347D for ; Mon, 19 Jun 2017 02:41:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4718D84842 for ; Mon, 19 Jun 2017 02:41:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5J2fGwf026371 for ; Mon, 19 Jun 2017 02:41:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 220000] mail/fetchmail placement of CONFIGURE_ARGS is significant Date: Mon, 19 Jun 2017 02:41:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: chalpin@cs.wisc.edu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 02:41:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220000 --- Comment #3 from Corey Halpin --- I suspect you're right that the underlying problem here is something in the ports framework to do with GSSAPI_NONE. I'd like to dig into what that is a= nd ideally fix it in the framework so that any other ports that are similarly affected can also benefit from the fix. However, I'm still having trouble replicating the issue. I did discover a separate issue wherein the stage-qa checks introduced in r438176 do not approve of the python shebang line in libexec/fetchmailconf.= py when the X11 option is off. I have a patch applied to my local fetchmail to work around it. I need to do more testing to clean up that patch before put= ting it into a separate PR. For testing this issue, I've created three poudriere sets with the following contents in their make.conf files: /usr/local/etc/poudriere.d/OpenSSL_base_nogss-make.conf: DEFAULT_VERSIONS+=3D ssl=3Dbase OPTIONS_UNSET+=3D GSSAPI_BASE OPTIONS_SET+=3D GSSAPI_NONE /usr/local/etc/poudriere.d/OpenSSL_port_no23_nogss-make.conf: DEFAULT_VERSIONS+=3D ssl=3Dopenssl OPTIONS_UNSET+=3D GSSAPI_BASE OPTIONS_SET+=3D GSSAPI_NONE security_openssl_UNSET=3DSSL2 SSL3 /usr/local/etc/poudriere.d/LibreSSL_nogss-make.conf: DEFAULT_VERSIONS+=3D ssl=3Dlibressl OPTIONS_UNSET+=3D GSSAPI_BASE OPTIONS_SET+=3D GSSAPI_NONE >From what you've provided, it seems like the OpenSSL_port_no23_nogss flavor corresponds to your i386 configuration and the LibreSSL_nogss flavor corresponds to your amd64 configuration. And I've created a script that runs 'poudriere testport' and checks that li= bssl is linked by the fetchmail binary produced for each of the above flavors on 10.3/i386, 10.3/amd64, 11.0/i386, and 11.0/amd64. In all cases, libssl was linked as expected. I don't currently have an 11.1 environment to test in, = but to the best of my knowledge the ports build system should be working simila= rly on both minor versions of 11.x. Do you see the issue using poudriere on your 11.1 machine when using one of= the above *-make.conf files? If so, then I need to spin up an 11.1 environment = to work on this further. But if not, it would seem to imply that there's somet= hing additional from your environment that I'll need to replicate and further de= bug the issue. TIA for your assistance in tracking down the problem. The quick and dirty patch I used to make stage-qa happy was as follows: diff -ru fetchmail.old/Makefile fetchmail/Makefile --- fetchmail.old/Makefile 2017-06-18 21:30:14.398717000 -0500 +++ fetchmail/Makefile 2017-06-18 21:30:48.066473000 -0500 @@ -87,10 +87,6 @@ @${MKDIR} ${STAGEDIR}${DOCSDIR} cd ${WRKSRC} && ${INSTALL_DATA} ${PORTDOCS} ${STAGEDIR}${DOCSDIR} -post-install-X11-off: - ${INSTALL_SCRIPT} ${WRKDIR}/fetchmailconf ${STAGEDIR}${PREFIX}/bin - ${INSTALL_SCRIPT} ${WRKSRC}/fetchmailconf.py ${STAGEDIR}${PREFIX}/libexec - .include .if ${SSL_DEFAULT:Mopenssl-devel} diff -ru fetchmail.old/pkg-plist fetchmail/pkg-plist --- fetchmail.old/pkg-plist 2017-06-18 21:30:14.399774000 -0500 +++ fetchmail/pkg-plist 2017-06-18 21:32:33.947739000 -0500 @@ -1,8 +1,5 @@ bin/fetchmail -bin/fetchmailconf man/man1/fetchmail.1.gz -man/man1/fetchmailconf.1.gz -%%NO_X11%%libexec/fetchmailconf.py %%NLS%%share/locale/ca/LC_MESSAGES/fetchmail.mo %%NLS%%share/locale/cs/LC_MESSAGES/fetchmail.mo %%NLS%%share/locale/da/LC_MESSAGES/fetchmail.mo @@ -27,6 +24,8 @@ %%NLS%%share/locale/tr/LC_MESSAGES/fetchmail.mo %%NLS%%share/locale/vi/LC_MESSAGES/fetchmail.mo %%NLS%%share/locale/zh_CN/LC_MESSAGES/fetchmail.mo +%%X11%%bin/fetchmailconf +%%X11%%man/man1/fetchmailconf.1.gz %%X11%%%%PYTHON_SITELIBDIR%%/fetchmailconf.py %%X11%%%%PYTHON_SITELIBDIR%%/fetchmailconf.pyc %%X11%%%%PYTHON_SITELIBDIR%%/fetchmailconf.pyo --=20 You are receiving this mail because: You are the assignee for the bug.=