Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Apr 2015 15:57:26 +0000
From:      bugzilla-noreply@freebsd.org
To:        perl@FreeBSD.org
Subject:   maintainer-feedback requested: [Bug 199354] security/p5-Crypt-SSLeay is all of a sudden interactive during build
Message-ID:  <bug-199354-14331-o6RbuSQ1yk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199354-14331@https.bugs.freebsd.org/bugzilla/>
References:  <bug-199354-14331@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
Trond.Endrestol@ximalas.info has reassigned Bugzilla Automation
<bugzilla@FreeBSD.org>'s request for maintainer-feedback to perl@FreeBSD.org:
Bug 199354: security/p5-Crypt-SSLeay is all of a sudden interactive during
build
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199354



--- Description ---
For better or worse, although I gather the latter, security/p5-Crypt-SSLeay
went interactive some time ago, and the issue is independent of running
"portupgrade -fprv security/p5-Crypt-SSLeay" or "make -C
/usr/ports/security/p5-Crypt-SSLeay build".

Here's an example:

===============================================================================
=
Output from
'/usr/ports/workdirs/usr/ports/security/p5-Crypt-SSLeay/work/Crypt-SSLeay-0.72/
openssl-version':
OpenSSL 1.0.2a 19 Mar 2015
1000201f
===============================================================================
=
The test suite can attempt to connect to public servers to ensure that the
code is working properly. If you are behind a strict firewall or have no
network connectivity, these tests may fail (through no fault of the code).
Do you want to run the live tests (y/N)? [N]

The build sits idle waiting for me to hit the enter key. Sure, this could be
avoided by setting BATCH=yes in the environment, I haven't tried, but I guess
that workaround is more the exception than the rule. Maybe I'm wrong.

Any thoughts?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199354-14331-o6RbuSQ1yk>