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 255FB1381F3 for ; Sun, 20 Oct 2013 14:03:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 82B5FE0AC5; Sun, 20 Oct 2013 14:03:42 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AB534E0996 for ; Sun, 20 Oct 2013 14:03:41 +0000 (UTC) Received: from [192.168.1.101] (unknown [124.78.108.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrick) by smtp.gentoo.org (Postfix) with ESMTPSA id 2568C33EF56 for ; Sun, 20 Oct 2013 14:03:39 +0000 (UTC) Message-ID: <5263E30E.1090404@gentoo.org> Date: Sun, 20 Oct 2013 22:05:02 +0800 From: Patrick Lauer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130426 Thunderbird/17.0.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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [Bug 488318] media-video/mpv[luajit] - Keyword request on alpha, arm, ppc, ppc64, sparc References: <20131019190144.7858709c@marga.jer-c2.orkz.net> <20131019194329.41f538b0@TOMWIJ-GENTOO> <5263ADEC.9000000@gentoo.org> <5263B32F.1080302@gentoo.org> <5263C14E.8020709@gentoo.org> In-Reply-To: <5263C14E.8020709@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 09dfb5a2-99f2-4ec9-b67f-f160f2803117 X-Archives-Hash: f8c4b4441ac07b387bb235803548cb29 On 10/20/2013 07:41 PM, Markos Chandras wrote: > On 10/20/2013 11:40 AM, Patrick Lauer wrote: > >>> The affected packages can slowly be fixed. It's not like they are >>> totally broken but it's more like of another way to tell you that >>> a few QA problems exist and that it would be nice to fix them >>> whenever you find some time. > >> You mean situations where there is user-visible breakage in the >> dependency graphs? > >> If I were a member of the QA team (which for various reasons I've >> never been allowed to be, which is quite hilarious) I'd ask you to >> remember the "repoman || die" motto we beat into every new recruit >> and/or ask you to honourably disable your commit privileges. > > > No I never meant broken depgraphs. Well for broken deps, repoman does > not let you commit. If you use --force to workaround broken deps, > well, then you get what you deserve. Sadly that's not true - for ebuild additions and most keyword changes repoman works well. But you can make things fail in many creative ways, like ... - stale or only partially up-to-date checkout - package.mask changes - accidental stable keyword removal - accidental slot or useflag removal - failed commits (easy to accidentally overlook) and so on. Most of that affects reverse dependencies, which are not checked by default - a good part of the depgraph breakage could be avoided if everyone ran full-tree scans, but that's extremely time-consuming (I'm burning 120 CPU-minutes @ 3.4Ghz amd64 for a full tree scan) and inconvenient. So for now I just hope that my constant bug-nagging motivates people to be a bit more careful :)