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-48530-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1ROoWj-0004hx-1p
for garchives@archives.gentoo.org; Fri, 11 Nov 2011 10:40:05 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EA61B21C0DF;
Fri, 11 Nov 2011 10:39:54 +0000 (UTC)
Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181])
by pigeon.gentoo.org (Postfix) with ESMTP id 72DB721C0BB
for <gentoo-dev@lists.gentoo.org>; Fri, 11 Nov 2011 10:39:22 +0000 (UTC)
Received: by gyd10 with SMTP id 10so3422356gyd.40
for <gentoo-dev@lists.gentoo.org>; Fri, 11 Nov 2011 02:39:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=date:from:to:cc:subject:message-id:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
bh=rmrRFwm+64h/vAVJO95DzTwRpsFW5k6Qeh6LlsWj9uU=;
b=OCZ08DFxXJ6ipnEHcSDicQqY9k+NIL1MNz4KA0VLPIGt1CJIaeaChmVILXk+rn/r7D
VFHxr3J04zgCX7d79Gcejog4zgHgE2UnF2KH20CnGwGLxnny5oOfnJPQeWmxqPPffJno
RlticYMg9JjqtFcJUu2JZ1Hfcq4cWPVD4mcKc=
Received: by 10.68.0.129 with SMTP id 1mr22867525pbe.94.1321007961417;
Fri, 11 Nov 2011 02:39:21 -0800 (PST)
Received: from smtp.gmail.com:587 (74-95-192-101-SFBA.hfc.comcastbusiness.net. [74.95.192.101])
by mx.google.com with ESMTPS id wn14sm29102004pbb.5.2011.11.11.02.39.19
(version=TLSv1/SSLv3 cipher=OTHER);
Fri, 11 Nov 2011 02:39:20 -0800 (PST)
Received: by smtp.gmail.com:587 (sSMTP sendmail emulation); Fri, 11 Nov 2011 02:39:18 -0800
Date: Fri, 11 Nov 2011 02:39:18 -0800
From: Brian Harring <ferringb@gmail.com>
To: scarabeus@gentoo.org
Cc: gentoo-dev@lists.gentoo.org, chromium@gentoo.org
Subject: Re: [gentoo-dev] Stop altering of current release ebuilds and
propagate the changes slowly
Message-ID: <20111111103918.GB3812@localhost>
References: <CA+Nrkpf1q4d94RRAVYyqH9Qr41ipkMFW=bn22kTTJ+rc54tRNg@mail.gmail.com>
<20111111093229.GA3812@localhost>
<CA+Nrkpf7sbwhXmDK0By_=5sLR-KeTXmuhfiWQ==widrMzocc-w@mail.gmail.com>
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
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+Nrkpf7sbwhXmDK0By_=5sLR-KeTXmuhfiWQ==widrMzocc-w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Archives-Salt: f64cedd4-1065-4e89-9a7f-076e5d4d6f49
X-Archives-Hash: ba4151b9043ca20a4ff25dda047314bf
On Fri, Nov 11, 2011 at 10:48:15AM +0100, Tom???? Chv??tal wrote:
> 2011/11/11 Brian Harring <ferringb@gmail.com>:
> The build issue was with -cups so useflag was removed and hard
> dependency enabled, fine with me.
> But why the fuck the bump was issued next day still hard-depending on
> it and in day after that this commit arrived in:
>
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/chromium-16.0.912.32.ebuild?r1=1.1&r2=1.2
>
> You are telling me this is build time failure fix, you are telling me
> that people that already had pulled in that cups could not sleep
> thanks to it and survive for another week to get the flag back with
> bump?
I'm telling you to stop fucking bitching about running unstable
software that probably is the fastest moving upstream in the tree in
terms of versions, nor the simplest fucking thing to maintain, let
alone keep everyone happy. Libreoffice I have no doubt is a pain in
the ass to maintain, but I'd take it over chromium any day of the
week.
Realize you're ranting on the ML because /you choose to run unstable/
and don't like that it's changing to deal w/ bugs (let alone the fast
release cycle of dev channel which you're on).
Specifically, you're ranting, and I strongly suspect you didn't bother
talking to the people directly beyond firing off bitching to the ML.
Nice and friendly, that.
As I said, looking through the logs it looks like this isn't
arbitrary random fucking around w/ ebuilds as you're implying above.
Is the cups situation a fuckup? Perhaps, but in digging through the
logs it ain't seeming like it's the norm. It's more seeming like
you're just venting about changes that went out fixing chromium
building for others, and you had to rebuild.
Productive courses of action, enumerated:
1) change your user configuration. You chose to run unstable after
all.
2) talk w/ the devs directly w/ suggestions of how to slow the
releases (doesn't frankly seem all that viable, but hey, it's your
time to burn). Keep in mind your original suggestion was to leave
shit broke in unstable (but hey, at least you don't have to
recompile).
3) add an optional feature to portage enabling you to control the
frequency of rebuilds for an unstable pkg. This way you get your
bleeding edge, just control the level of pain.
Non-produtive courses of action, enumerated:
1) bitching on an ML cc'ing the maintainers rather than going to the
maintainers directly.
2) continuing to argue with me.
~brian