From owner-freebsd-ports@freebsd.org Fri Aug 14 16:58:47 2020 Return-Path: Delivered-To: freebsd-ports@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 33B853C3C20 for ; Fri, 14 Aug 2020 16:58:47 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BSqQb0fz2z3fD6 for ; Fri, 14 Aug 2020 16:58:47 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 14A3A3C3C1F; Fri, 14 Aug 2020 16:58:47 +0000 (UTC) Delivered-To: ports@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 133F63C3FC8 for ; Fri, 14 Aug 2020 16:58:47 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BSqQZ6DS1z3fRx; Fri, 14 Aug 2020 16:58:46 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: from t480.local (189.26.175.87.dynamic.adsl.gvt.net.br [189.26.175.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: dbaio/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 27CB820C33; Fri, 14 Aug 2020 16:58:46 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Date: Fri, 14 Aug 2020 13:58:44 -0300 From: "Danilo G. Baio" To: Stefan Esser Cc: ports@FreeBSD.org Subject: Re: pkg-fallout reports Message-ID: <20200814165844.dxbvy7ztjfilkatx@t480.local> References: <20200813225414.jomrx4cegbp5jqit@t480.local> <2d720267-061b-c802-5670-7daa25d0353c@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="defw7yew2tjgnklt" Content-Disposition: inline In-Reply-To: <2d720267-061b-c802-5670-7daa25d0353c@freebsd.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2020 16:58:47 -0000 --defw7yew2tjgnklt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 14, 2020 at 01:37:19PM +0200, Stefan Esser wrote: > Am 14.08.20 um 00:54 schrieb Danilo G. Baio: > > Hi. > >=20 > > Just sharing this simple project that gathers freebsd-pkg-fallout [1] > > reports into a database for easy filtering: > >=20 > > https://portsfallout.com/fallout > >=20 > >=20 > > I hope it's useful for port maintainers. >=20 > Hi Danilo, >=20 > very useful indeed! >=20 > One thing I noticed: The filtering by maintainer name performs > a sub-string match of the argument, which due to many very short > account names leads to "false positive" matches. >=20 > How about a different match algorithm: >=20 > 1) If argument has no domain part then >=20 > 1.a) attach "@freebsd.org" and check for identity (full length > comparison) >=20 > 1.b) compare argument with name part of maintainer mail address > (sans domain part) >=20 > 2) Compare argument with domain with implied anchor on first > characters >=20 > 3) Sub-string search as currently done >=20 > Stop whenever a step returns a non-empty result. >=20 > This would allow committers to match by their login name and it > should give reasonable results for external maintainers, too. >=20 > Is it possible to suppress or mark results that correspond to > ports that have been fixed or failed only spuriously? > (This might e.g. be implemented if it was known when another > round of package builds have been completed for the architecture > and release that caused a report and the failure has not been > reported again.) Hi Stefan. Thanks for the tips. I'll improve this search form. And about the build fix part, there is nothing yet to mark if some issue was fixed. --=20 Danilo G. Baio (dbaio) --defw7yew2tjgnklt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEORj0UTsjzCy+enIkmpN7LfMuiNcFAl82wsBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDM5 MThGNDUxM0IyM0NDMkNCRTdBNzIyNDlBOTM3QjJERjMyRTg4RDcACgkQmpN7LfMu iNcDkQ//ZdqzOHYLPaLbparIMbU/xJhE3ADk/CO60D34awr0kBBNhBl+zo9t/09B qsHzWmI5WHoYVOYDwug8aADDU2TtxgiaKVYSPuaZh3LkLZKxn7DWvmaCbPID6vTm rVlKkDQZiYtBn+y6bSbncQwsRk0ad5c8dDL2/9XRuRhthpjO1kZzS4CXJVla+9eW ml1PBnIbtOzL0qCT0XiKQChtj0e60gABnI+be2gNJKu7ZF7vNtZWIAPn7iaq+EZb yEFb9DY0bjtMgOIGtnGUPavjqlAnOpD5bjHyBa8XXXnCPDDr39kHlLlWbW4iS1Em 4FKnWfmoIw0uAWLAlItPsRYLErsQp+H4HHkwGnbFHeec5hB6p6BdAvFZNu+BroIf zKDqGRb37SNFPUv31nPyrabseyE4kA020rh7Scu3uXF2+7ujPh6kmhULp/hrTpMg 0t/vzoo8ztNuocQBB6DJCnIxaL7uAxHYFLIu5dQgY5JApUDA2p2ecx4h4ZR4Q29w gQXmjrSZQgi8qniHkvFCWhx+apiT2GA1DE4/txyaI9hKUuClvmWmYKFFrcl9+DnB pXSFM5HMRkmgWFqnypsheIZzGoUi5iHKDd5lr1rBgpMUeILiPPHbXhC/+VWjTYiu St8hdMjG5ebBiSvMyPM2zkET0LhJQhwPDRV/3vogWMYZepPhdwM= =fF4O -----END PGP SIGNATURE----- --defw7yew2tjgnklt--