ports/67762: portupgrade of stunnel asks for input even when run with BATCH=1
Linus Sjoberg
lsjoberg at aland.net
Wed Jun 9 18:00:57 UTC 2004
>Number: 67762
>Category: ports
>Synopsis: portupgrade of stunnel asks for input even when run with BATCH=1
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jun 09 18:00:42 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Linus Sjoberg
>Release: 4.10-STABLE
>Organization:
>Environment:
FreeBSD hal9000.alcom.aland.fi 4.10-STABLE FreeBSD 4.10-STABLE #17: Wed Jun 2 09:32:15 EEST 2004 root at hal9000.alcom.aland.fi:/usr/obj/usr/src/sys/HAL i386
>Description:
When doing a ports upgrade using
# BATCH=1 portupgrade -a
you expect all upgrades to be performed without any interaction with the user. This is not true for stunnel.
When I checked my portupgrade today it was hung waiting for input with the prompt:
"Remove group stunnel? [y/n]"
Appearently this is due to the stunnel deinstall-script. After entering a 'n' the upgrade continued as espected.
Either the deinstall should not ask the question or otherwise stunnel should not be upgraded when running portupgrade when BATCH is set.
>How-To-Repeat:
I have not tried to reproduce this, but it should suffice to run portupgrade with BATCH set when there is a newer stunnel available.
>Fix:
Check for BATCH in stunnel Makefile.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list