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 B303B1384B4 for ; Tue, 8 Dec 2015 02:20:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5994D21C04C; Tue, 8 Dec 2015 02:19:57 +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 55F32E08A2 for ; Tue, 8 Dec 2015 02:19:56 +0000 (UTC) Received: from greysprite.dite (cpe-74-77-145-97.buffalo.res.rr.com [74.77.145.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: blueness) by smtp.gentoo.org (Postfix) with ESMTPSA id E7F4034085D for ; Tue, 8 Dec 2015 02:19:53 +0000 (UTC) Subject: Re: [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages To: gentoo-dev@lists.gentoo.org References: <20151206153611.2a132d2c.mgorny@gentoo.org> From: "Anthony G. Basile" Message-ID: <56663E47.20902@gentoo.org> Date: Mon, 7 Dec 2015 21:19:51 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 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 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: e47cff69-7881-49a8-9ed2-6bc294bc6d68 X-Archives-Hash: e4fe036f53ee3ccf900ec2afece67313 On 12/7/15 7:27 PM, Rich Freeman wrote: > On Mon, Dec 7, 2015 at 7:05 PM, Alec Warner wrote: >> 2) Unclear ownership of the problem. One guy makes a commit, 100 packages >> break. Who is responsible? Its really murky. This is really the toughest >> problem to me. > It isn't murky at all. Nobody should ever commit something that > simply breaks something else. Sometimes it is unforseen, and that > might be ok if it is rare, but the committer can still go and revert > their commit and sort things out. Does that include stuff that breaks on systems using musl instead of glibc? Or uclibc? or eudev instead of udev. What about openrc vs systemd? Shall I go on? Of course its murky. If you disagree, I'll be more than happy to pull out dozens of emails where people object when their stuff breaks other people's stuff with the infamous "why should we support that shit?" Anyhow, if the emails are easily filter or have an easy out, I see no problem. Murky or not. -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : blueness@gentoo.org GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA