From owner-freebsd-jail@freebsd.org Sat Aug 20 16:01:52 2016 Return-Path: Delivered-To: freebsd-jail@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 E41AEBC00F8 for ; Sat, 20 Aug 2016 16:01:52 +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 B9D0C143B for ; Sat, 20 Aug 2016 16:01:52 +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 u7KG1qI7060791 for ; Sat, 20 Aug 2016 16:01:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 211353] mail/sendmail failing during staging under poudriere FreeBSD 11+ Date: Sat, 20 Aug 2016 16:01:52 +0000 X-Bugzilla-Reason: CC 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 Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: marino@FreeBSD.org X-Bugzilla-Flags: 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-jail@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Aug 2016 16:01:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211353 --- Comment #3 from Kubilay Kocak --- (In reply to John Marino from comment #2) Closing an issue is implicitly taking responsibility for it in the same way= a commit in the tree is, as a decision is being made by the closer, whether w= ith a change (commit) or not (rejected, feedback timeout). The scope is (can) n= ot limited to the commit as any followup as a result of that commit is also implicitly related to the issue. The other reason for assignment is for accurate statistics and reporting (w= ho did what when), and the fact that the default assignee of all ports issues being freebsd-ports-bugs (empty or unassigned), so that notifications go somewhere lest they never get actioned(read: assigned then resolved). If everyone used the issue tracker and not mailing lists, then issues would go from unassigned to assigned in that case. Having real assignees set as early as possible reduces the noise:signal rat= io for every one else at all points during an issues lifetime, which still rem= ains high. Issues being inaccurately or incompletely classified in the past, assignee = or any field, is only evidence of inconsistent/adhoc issue tracking practices,= not of a defacto standard. If this constitutes a genuine impact or burden on you, please email bugmeis= ter@ where we can aim to understand the issue in more detail and discuss it in a more amenable manner and place. --=20 You are receiving this mail because: You are on the CC list for the bug.=