From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 266791384B4 for ; Sun, 6 Dec 2015 14:36:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F328821C021; Sun, 6 Dec 2015 14:36:24 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0E8BF21C013 for ; Sun, 6 Dec 2015 14:36:23 +0000 (UTC) Received: from pomiot (d202-251.icpnet.pl [109.173.202.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 3453333D3C7; Sun, 6 Dec 2015 14:36:21 +0000 (UTC) Date: Sun, 6 Dec 2015 15:36:11 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Subject: [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages Message-ID: <20151206153611.2a132d2c.mgorny@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/uzDOCcgZ7Ialxg2MhJyCnT4"; protocol="application/pgp-signature" X-Archives-Salt: 7ba62eff-18e8-4742-a908-7d56099665d1 X-Archives-Hash: 8705b5a62f0d6b1823f59ca6a658029e --Sig_/uzDOCcgZ7Ialxg2MhJyCnT4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, As you have seen multiple times, I'm running a minimalistic CI service for Gentoo that checks the repository for major issues using pkgcheck. So far it's automation is limited to sending a mail to dedicated gentoo-automated-testing@lists.gentoo.org mailing list on breakage changes. From there, I compare the results to recent git log and mail the developers at fault, pointing out the bad commit. A few developers have already subscribed to the mailing list to check if they haven't caused any new breakages and fix them quickly. For others, it's pretty much just me caring to check, which also means that when I'm not around things are left broken. Automating the blaming process has been suggested multiple times already but I so far considered it not worth the effort. Mostly because many of the issues are indirect, and trying to automatically figure them out from combination of the pkgcheck report and recent commits would be hard, and could cause false positives. For example, some of the depgraph breakages happen because of package.mask changes -- figuring that out automatically wouldn't be easy, and the script could blame an irrelevant commit in the package. However, it was suggested recently that I could make it mail the maintainers of the affected packages. Even though most often it's not them who are at fault, it was suggested that they'd prefer to know that their packages are broken. So what do you think? Would it be fine to mail the package maintainers whenever their packages break? Would it be a problem if I just CC-ed all the maintainers on the gentoo-automated-testing mails? Please note that the breakages are catched per-package, and the script wouldn't be able to respect restrict=3D"" or hand-written maintainer descriptions ;-). --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/uzDOCcgZ7Ialxg2MhJyCnT4 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJWZEfbXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOo8wQAIixNw+1LYFe6CA3oQm+or2s F3oWlE7ZWxdtyOZAn9Bz7xwhJcsReadLeUuQuS4oiggo3eIVz5o0KHnrHP+qX7tT VUhEoCygCQzcXrtNr+us7ia2P49ybqcLIHUJvNOzyYB/3mVLRRVvSZgmHub70hjN D84D7eTYNhQ/SyOx2OQJbPA6u/voZV2EowqjHFgaM+bUgOnrX6Y1LHzyElqIOQ8w NvHTLMk891BaFa1VWBJq6vaPoCP8YWURvENQ7lbhtbXaE9TRp+bfZcDgkoOsu9nU 2pocSa8DuQVB1q8/jKFORC1MHXmR/fAoCHdupXrlpzdXkrhK8vAfVEiEFueGM5Cy o2LWWNBYY5lGSjpLPftkwEly3VKtTLC2PtWhLfTfzdeX9E5gzTNnVaS4esxzulaI uZkYmg4KsYFQH71cv8R9oH9/0xfj1VPcqPHjzwL2P9ElYSqUv9T+mrTE0tP0Z5Op G2mWpmOpr0Pdz5hFoiYZa9qzp2Cr6S8qRgxeixAdOmdVMEcrO/kyiuvu49lSZmNE 4Xx3nPQFgt5gxsnOkZ4f6/OjYl7Rony9XsSmpENhyzAQXE1/jpuiIyjG+zpLSUQy mBiF1UiQKHH2JygFn75iQRSYJekIbwMibZaBjULURRiNvngJDeN7Yfz4m90bqTGP i0jge6M9GZl+M0cOtJBN =K5Lw -----END PGP SIGNATURE----- --Sig_/uzDOCcgZ7Ialxg2MhJyCnT4--