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 5ABB21380DC for ; Wed, 5 Feb 2014 16:07:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 77BE1E0C17; Wed, 5 Feb 2014 16:07:31 +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 7B1FCE0C0D for ; Wed, 5 Feb 2014 16:07:30 +0000 (UTC) Received: from [192.168.11.20] (cpe-72-177-217-176.satx.res.rr.com [72.177.217.176]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: steev) by smtp.gentoo.org (Postfix) with ESMTPSA id 6BEB033F498 for ; Wed, 5 Feb 2014 16:07:29 +0000 (UTC) Message-ID: <1391616442.3160.6.camel@oswin.hackershack.net> Subject: Re: [gentoo-dev] Re: Re: dropping redundant stable keywords From: Steev Klimaszewski To: gentoo-dev@lists.gentoo.org Date: Wed, 05 Feb 2014 10:07:22 -0600 In-Reply-To: <20140205055544.6c3affea@TOMWIJ-GENTOO> References: <52E7DBC1.5020102@gentoo.org> <20140128182304.7d458a17@marga.jer-c2.orkz.net> <20140203062524.GA7467@rathaus.eclipse.co.uk> <20140203104341.2add2760@TOMWIJ-GENTOO> <20140204210319.GA1935@rathaus.eclipse.co.uk> <20140205010833.1bcf8dca@TOMWIJ-GENTOO> <1391559808.3520.2.camel@oswin.hackershack.net> <20140205020742.048cef9f@TOMWIJ-GENTOO> <1391564122.3520.4.camel@oswin.hackershack.net> <20140205024806.7d08cb63@TOMWIJ-GENTOO> <1391570147.3520.7.camel@oswin.hackershack.net> <20140205055544.6c3affea@TOMWIJ-GENTOO> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5 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-Transfer-Encoding: 7bit X-Archives-Salt: b784b48e-a418-4389-b5a9-6bf9f5bd7446 X-Archives-Hash: d611c64982f808f40a7b18810fde9c07 Against my better judgment... On Wed, 2014-02-05 at 05:55 +0100, Tom Wijsman wrote: > On Tue, 04 Feb 2014 21:15:47 -0600 > Steev Klimaszewski wrote: > > > On Wed, 2014-02-05 at 02:48 +0100, Tom Wijsman wrote: > > > On Tue, 04 Feb 2014 19:35:22 -0600 > > > Steev Klimaszewski wrote: > > > > > > > Alright, well, I've tried my best, I give up. Instead of having > > > > something working we should just remove ebuilds of working > > > > packages. > > > > > > s/should/could/ s/ebuilds/stable keyword or last stable version/ > > > > > > It is at the maintainer's discretion; and such decision is to make > > > it possible for a maintainer to move on when he or she can no longer > > > guarantee a working ebuild, to stop being progress-blocked by it. > > > > > > > You know what - this is pure and utter bullshit. > > Why is this pure and utter bullshit? Because I'm attempting to have a discussion with a brick wall. > > > Keeping it around for "slower" arches does NOT block progress. > > Why is keeping it around for "slower" arches not blocking progress? > Let's see... having the software at least available, versus not having access to it at all... which one is progress... THINK TOM THINK. > > I have intimate knowledge with what ACTUALLY happens when people pull > > this bullshit - and that is a system that I can no longer actually > > work on. > > That is also what happens when a maintainer keeps around old versions, > as well as old bugs and support for those old versions; as by doing so, > the attention towards newer versions is lost which causes much huger > breakage than the one you have just brought up. Manpower is limited. > And we attempted to come up with a solution for this, however due to the wording of a page on the interwebs that solution is 100% unacceptable *to you*, a person who is unaffected by it. > > And instead of working towards a fix that actually works > > for people who are ACTUALLY affected by the shitty policy, you hide > > behind definitions and pedantry. > > Why do you think this about the current and/or suggested solution(s)? > > > I'm now going to take a break from Gentoo development because this > > thread has seriously caused my blood to boil based on comments from > > the peanut gallery (you) where things don't actually affect your day > > to day work, but your actions do affect mine. > > Why? How and why are your actions affected by the QA team's actions? > Not the QA team's actions. YOURS. YOUR actions and responses in this thread. And the fact that the QA team allows you to continue to be on it, despite your obvious lack of interest in ACTUALLY having quality assurance. My actions are affected by it because I have to continue to attempt to discuss the issue with others who actually give a shit, and you just swoop in and say no, that absolutely is unacceptable as a solution (even though it doesn't affect me!) because this page here says that it can't - we can change that definition if you'd like. Instead of the line saying: The -* keyword is special. It is used to indicate package versions which are not worth trying to test on unlisted archs. Would changing it to read The -* keyword is special. It is used to indicate package versions which are not for use on unlisted archs. Would that make it acceptable?