Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Oct 2006 14:40:03 GMT
From:      Josh Endries<josh@endries.org>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/104266: The stunnel port doesn't work unattended/without intervention (e.g. with BATCH=1)
Message-ID:  <200610101440.k9AEe3Kr049020@www.freebsd.org>
Resent-Message-ID: <200610101440.k9AEeDbR035995@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         104266
>Category:       ports
>Synopsis:       The stunnel port doesn't work unattended/without intervention (e.g. with BATCH=1)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 10 14:40:13 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Josh Endries
>Release:        6.1
>Organization:
>Environment:
Every machine I have
>Description:
When updating via portupgrade, or normal, the port (I think the configure command) checks for the stunnel user/group and always asks (even if it finds them) to create or remove them. If passing BATCH=1, as one may do in a portupgrade -a command, it asks also and holds up the whole upgrade process.
>How-To-Repeat:
Build security/stunnel
>Fix:
Other ports seem to answer questions like this automatically, maybe that is possible with this also?
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610101440.k9AEe3Kr049020>