From owner-freebsd-python@freebsd.org Tue Sep 24 02:39:13 2019 Return-Path: Delivered-To: freebsd-python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4E456F39CA for ; Tue, 24 Sep 2019 02:39:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46clkn1PjVz3P1j for ; Tue, 24 Sep 2019 02:39:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 30357F39C9; Tue, 24 Sep 2019 02:39:13 +0000 (UTC) Delivered-To: python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2FFF5F39C8 for ; Tue, 24 Sep 2019 02:39:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46clkn0W1Qz3P1h for ; Tue, 24 Sep 2019 02:39:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EA2FA20848 for ; Tue, 24 Sep 2019 02:39:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8O2dCjn019883 for ; Tue, 24 Sep 2019 02:39:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8O2dCku019882 for python@FreeBSD.org; Tue, 24 Sep 2019 02:39:12 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 240774] security/py-fido2: Update to 0.7.1 Date: Tue, 24 Sep 2019 02:39:13 +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: grembo@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2019 02:39:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240774 --- Comment #6 from Kubilay Kocak --- (In reply to Michael Gmelin from comment #3) It does for maintainer-feedback flag (issue level), but not for maintainer-approval (attachment flag/level), so that, the flag state (?) and the value (maintainer email) has to be added manually. It could be automated, but there's issues/considerations: https://wiki.freebsd.org/KubilayKocak/Bugzilla/Roadmap#MAINTAINER_approval_= of_patches Re "Severity "(Affects *)" field, the distinctions are: 1) bugs vs features ("updates" are more like features, unless they only fix bugs), so maintainer updates are almost always 'affects only me' on that ba= sis.=20 2) Objective vs subjective severity. It's difficult to say how many 'actual' people are effected, say based on usage/popularity guesses, but one can 'cl= ass' the issue severity based on some objective properties, like: a) global/unconditional bug: Affects many/all b) conditional bug: Affects some. Like a bug with a particular port OPTIO= N or specific base binary argument or other specific condition or set of conditi= ons I'll write something about up in the triaging guidelines. Thanks for asking= :) --=20 You are receiving this mail because: You are on the CC list for the bug.=