Date: Mon, 13 Jul 2009 16:40:59 GMT From: Steven Friedrich <StevenFriedrich@InsightBB.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/136722: portversion issues Stale lock warning to stdout, should send to stderr Message-ID: <200907131640.n6DGexcZ042664@www.freebsd.org> Resent-Message-ID: <200907131650.n6DGo1ah017453@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 136722 >Category: ports >Synopsis: portversion issues Stale lock warning to stdout, should send to stderr >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: Mon Jul 13 16:50:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Steven Friedrich >Release: 7.2 >Organization: >Environment: >Description: I often use portverion -L'='|tee /dev/tty|wc -l to count how many ports need to be updated. When a stale lock is left behind, portversion emits a Stale lock message to stdout, but should be sending it to stderr. >How-To-Repeat: Issue the command mentioned while portupgrade is running. >Fix: Use stderr instead of stdout as the destination for the Stale lock message. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907131640.n6DGexcZ042664>