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 DDF7C1388C1 for ; Thu, 3 Mar 2016 20:52:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 39FD121C010; Thu, 3 Mar 2016 20:51:58 +0000 (UTC) Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 46E7421C007 for ; Thu, 3 Mar 2016 20:51:57 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id d205so24246176oia.0 for ; Thu, 03 Mar 2016 12:51:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=IRauLoviuWdD4wJvZPgbVDjP8Db75oDt4q9Fhiwto9A=; b=0JszygnJHzvCP+iDaYeR2nKtMsT4W023spd0lIxn/INwi4lMNTo13uXwTWQRzRtaWi 69krmq93x9Tzv9j2kvk6Enkg97EQwJpXZukcdLHeQ60M8S5tNH3WLDQJGce6Z3AOSCNR 09iQKdXKF6Dw/qLVRZGvPyN3GO8WMg6eSfpBC4Rusna8zZVz3FtckVmiH2JTVMKf5ptb tOC3+K3emdqoowCaqPap3YbqaZppBVVxaq+I+U+HRLTsZhixJ8Un3kQ9nvBeqGJj1X6k QqSExqqC5WXzYfY2c5C7Drp3ahCpLrkFATTeL9cHL/H/G+YLn9ikE44jKI3nHwnADkPm XhDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=IRauLoviuWdD4wJvZPgbVDjP8Db75oDt4q9Fhiwto9A=; b=CibKNB8L3CSulseDm13q5MF/mQ0cH6h9ZsLG/XRDcW8DDzwlXyuCYk+Oq7rWXJIGP5 xcxUKn0AtG+Mqd0aQ1QnW/Ny0jG2Pma0OYTnmlrbD+ugKbP7IuNYDnR+CeQ/Qb1yV57v mc3ItPOe2ZApuwORvYJ6IdlKUCnVvdjQwKbnQuWWovIl5ahslL5O7coHwlERQqoiI8s/ o5PjknwpPkRtrLUVv4nAqz8S8w+VLe371qb/9C8tsvHCj6PY836QNu1miC06ETDoW5VD vVobD88M2+HN0AYHJd8C1csH5xv420zcqcdQ2hKn+MAJ2BL1EzsRJU9q1SF9/ElTKzFy xvfw== X-Gm-Message-State: AD7BkJIEiuc7MJrYn+AaCug59PBkFaKSHN7xq/4XOP31zhEm6KRMgr3PAq0tGRHdIAtWfaR62LFgQY6NyUAWgg== X-Received: by 10.202.202.143 with SMTP id a137mr3316415oig.28.1457038316207; Thu, 03 Mar 2016 12:51:56 -0800 (PST) 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 Received: by 10.202.207.69 with HTTP; Thu, 3 Mar 2016 12:51:16 -0800 (PST) In-Reply-To: <20160209193039.GQ7732@vapier.lan> References: <20160201185501.GB28175@ultrachro.me> <201602012216.54035.dilfridge@gentoo.org> <20160202013330.GT7732@vapier.lan> <201602032236.01473.dilfridge@gentoo.org> <20160209193039.GQ7732@vapier.lan> From: Raymond Jennings Date: Thu, 3 Mar 2016 12:51:16 -0800 Message-ID: Subject: Re: [gentoo-dev] [Fwd: [gentoo-automated-testing] BROKEN: repository became broken!] To: gentoo-dev Content-Type: multipart/alternative; boundary=001a1134faf2430350052d2b2bb5 X-Archives-Salt: c16f80d8-3456-4ace-8828-23ab8819e496 X-Archives-Hash: a64bed15f5372475833ee68e533a52ba --001a1134faf2430350052d2b2bb5 Content-Type: text/plain; charset=UTF-8 I think best of all would be the good discipline not to break the tree in the first place. Is this something that Repoman could have caught? If no, should it in the future? On Tue, Feb 9, 2016 at 11:30 AM, Mike Frysinger wrote: > On 03 Feb 2016 22:35, Andreas K. Huettel wrote: > > Am Dienstag, 2. Februar 2016, 02:33:30 schrieb Mike Frysinger: > > > > I took the liberty of doing (2) and reverted the commit. Not sure why > > > > this needs so much discussion; after all a broken tree is always > > > > suboptimal. > > > > > > unless things are on fire (which i don't think this was), i don't > > > generally clamor for 0-day fixes. if we can find a better fix in > > > a day or so, then i'm happy for that. i dislike repos with history > > > that is just a constant stream of land, revert, land, revert, land. > > > > > > not that i'm saying your revert was wrong ... just airing my > > > general personal preferences. > > > > You're right of course... but there's one thing we have to keep in mind. > > > > We're not running a project were releases are made from the vcs. The vcs > *is* > > the release... and whatever is out there gets pushed to users. > > > > This is why my personal preference is more to revert if I'm not sure > that the > > fix will happen soon. > > which is why you weigh the impact on users. how many people are actually > affected and for how long ? in this case, fairly sure no actual user saw > the failure on their system. > -mike > --001a1134faf2430350052d2b2bb5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think best of all would be the good discipline not = to break the tree in the first place.

Is this something that R= epoman could have caught?=C2=A0 If no, should it in the future?

On Tue, Feb 9, 2016= at 11:30 AM, Mike Frysinger <vapier@gentoo.org> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">On 03 Feb 2016 22:35, Andrea= s K. Huettel wrote:
> Am Dienstag, 2. Februar 2016, 02:33:30 schrieb Mike Frysinger:
> > > I took the liberty of doing (2) and reverted the commit. Not= sure why
> > > this needs so much discussion; after all a broken tree is al= ways
> > > suboptimal.
> >
> > unless things are on fire (which i don't think this was), i d= on't
> > generally clamor for 0-day fixes.=C2=A0 if we can find a better f= ix in
> > a day or so, then i'm happy for that.=C2=A0 i dislike repos w= ith history
> > that is just a constant stream of land, revert, land, revert, lan= d.
> >
> > not that i'm saying your revert was wrong ... just airing my<= br> > > general personal preferences.
>
> You're right of course... but there's one thing we have to kee= p in mind.
>
> We're not running a project were releases are made from the vcs. T= he vcs *is*
> the release... and whatever is out there gets pushed to users.
>
> This is why my personal preference is more to revert if I'm not su= re that the
> fix will happen soon.

which is why you weigh the impact on users.=C2=A0 how many people ar= e actually
affected and for how long ?=C2=A0 in this case, fairly sure no actual user = saw
the failure on their system.
-mike

--001a1134faf2430350052d2b2bb5--