From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-45034-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1Q3sg1-0005t6-K1
	for garchives@archives.gentoo.org; Sun, 27 Mar 2011 16:18:54 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 7302E1C01B;
	Sun, 27 Mar 2011 16:18:44 +0000 (UTC)
Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181])
	by pigeon.gentoo.org (Postfix) with ESMTP id 88D491C003
	for <gentoo-dev@lists.gentoo.org>; Sun, 27 Mar 2011 16:18:15 +0000 (UTC)
Received: by wyi11 with SMTP id 11so2206350wyi.40
        for <gentoo-dev@lists.gentoo.org>; Sun, 27 Mar 2011 09:18:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        bh=zhqEUPCAOX07itX2G7HPe5WdcXcKUAwQ4ZFJIW0mB/k=;
        b=MpwV9EsUHFgLYMMwU9VgiPgscbRH/a+e11Ke6/sS/wTmk8Y+MDm+GC93sp22o7fRNp
         eQFDJxnXWLahfURjXHIuRrMhbFSVzi5Qz3OAoGoBpUL3b7Lq07gNQLtzQfe+xxt1FkvY
         XAV4q+A+oJXVzL/N6FeBjs2X+BmTrUu2myIgk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=VazHTcTHTVTgMlWNC7tAJWdp5mSbuzHqnzHQ9EwzqVoeo3DOmgIbtyyrMOlCJgqSHi
         M/PtzNV+0Bi3qSwzUbLmKnev2U+5oJIs/QtHaZtuN7PDiOQ72KjuAQrMpCilvtohq3Xn
         olib23l4bOC+c46Og6TDvkJCu/8SsphGIfV5s=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.227.58.72 with SMTP id f8mr2981400wbh.181.1301242694662; Sun,
 27 Mar 2011 09:18:14 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.227.147.82 with HTTP; Sun, 27 Mar 2011 09:18:14 -0700 (PDT)
Received: by 10.227.147.82 with HTTP; Sun, 27 Mar 2011 09:18:14 -0700 (PDT)
In-Reply-To: <4D8F4F93.6030507@gentoo.org>
References: <20110326055210.E906D20054@flycatcher.gentoo.org>
	<4D8EC104.4090503@gentoo.org>
	<AANLkTik=cLPnD5Y7akyM0xsPgOC7+cvVOh=bj1Opir_y@mail.gmail.com>
	<4D8F3BE8.5050300@gentoo.org>
	<AANLkTikW=5z0ULH6ELC6qPe9QEdyUyDHVCwReLC9=TXM@mail.gmail.com>
	<4D8F4F93.6030507@gentoo.org>
Date: Sun, 27 Mar 2011 12:18:14 -0400
X-Google-Sender-Auth: Nn6bvHh2Th-L15HOIRpmBV6fUco
Message-ID: <AANLkTikLssB6WnJtRKUh3Gv6vrfos5hj=er=aaPSjd-z@mail.gmail.com>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in
 dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Content-Type: multipart/alternative; boundary=20cf3001b43194fc55049f792c19
X-Archives-Salt: 
X-Archives-Hash: e75cf12c2772979550dd4c76eb7d8c51

--20cf3001b43194fc55049f792c19
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mar 27, 2011 11:01 AM, "Tom=C3=A1=C5=A1 Chv=C3=A1tal" <scarabeus@gentoo.=
org> wrote:
> And how exactly you want to track the level of failure for the package?
> Since nobody is watching them already we usually don't know how much
> they fail until somebody tries to emerge them from dev team or notify QA
> by adding as CC to bug...

If a tree falls in the forest...does anybody care?

Broken packages that nobody notices don't cost us much. A tinderbox sweep
will id and tag them for cleaning eventually.

All I'm saying is that the problem is broken packages, so address those, m-=
n
or otherwise.

By all means be proactive about finding maintainers, but let's not go
purging working packages.

As far as how broken is too broken - if it causes the distro headaches,
address it. That could be blockers, or tons of bug reports, or whatever...

Rich

--20cf3001b43194fc55049f792c19
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>On Mar 27, 2011 11:01 AM, &quot;Tom=C3=A1=C5=A1 Chv=C3=A1tal&quot; &lt;<=
a href=3D"mailto:scarabeus@gentoo.org">scarabeus@gentoo.org</a>&gt; wrote:<=
br>
&gt; And how exactly you want to track the level of failure for the package=
?<br>
&gt; Since nobody is watching them already we usually don&#39;t know how mu=
ch<br>
&gt; they fail until somebody tries to emerge them from dev team or notify =
QA<br>
&gt; by adding as CC to bug...</p>
<p>If a tree falls in the forest...does anybody care?</p>
<p>Broken packages that nobody notices don&#39;t cost us much. A tinderbox =
sweep will id and tag them for cleaning eventually. </p>
<p>All I&#39;m saying is that the problem is broken packages, so address th=
ose, m-n or otherwise. </p>
<p>By all means be proactive about finding maintainers, but let&#39;s not g=
o purging working packages.=C2=A0 </p>
<p>As far as how broken is too broken - if it causes the distro headaches, =
address it. That could be blockers, or tons of bug reports, or whatever...<=
/p>
<p>Rich</p>

--20cf3001b43194fc55049f792c19--