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 D89B3138010 for ; Mon, 17 Sep 2012 12:24:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EC99821C00C; Mon, 17 Sep 2012 12:23:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 83564E049A for ; Mon, 17 Sep 2012 12:22:58 +0000 (UTC) Received: from localhost (pc-234-79-101-190.cm.vtr.net [190.101.79.234]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id 8809733C319 for ; Mon, 17 Sep 2012 12:22:57 +0000 (UTC) Date: Mon, 17 Sep 2012 09:22:50 -0300 From: Alexis Ballier To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog profiles.desc Message-ID: <20120917092250.61d9f75a@gentoo.org> In-Reply-To: <201209162206.19807.vapier@gentoo.org> References: <20120828002311.815E120987@flycatcher.gentoo.org> <201209151848.03566.vapier@gentoo.org> <20120916120100.670c0578@gentoo.org> <201209162206.19807.vapier@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.12; x86_64-pc-linux-gnu) 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-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: c7a4dd24-3169-46a7-bd68-7a33784917a9 X-Archives-Hash: a1b1129bf9fa4537addabe0140eaf455 On Sun, 16 Sep 2012 22:06:19 -0400 Mike Frysinger wrote: > On Sunday 16 September 2012 11:01:00 Alexis Ballier wrote: > > also, you are missing some bug # for the 'broken deps' part. > > packages that have gained broken deps when the profile was marked > > 'dev', or that you committed with your profile.desc locally > > modified, do not count and are your fault actually... > > wrong. if i'm version bumping a package and i see broken amd64-fbsd > deps, that is not my problem. sounds like i'll simply de-keyword it > in the future and let someone else pick up the pieces. why do you want to treat amd64-fbsd different than other arches ? just to make the work of those that want to maintain that arch a pain ? you know, standard procedure is to drop keywords and file a bug when a new dep comes in a new version. deps that are _already_ broken should not happen because, heh, the profile is marked stable... in case this happens there's nothing sane to do, better use repoman --force and file an urgent bug to the arch team. > do a repoman on the tree. there are multiple packages coming back > right now with broken amd64-fbsd deps. if people do not file bugs and think it's fine to commit packages with broken deps, or silently dekeyword just because they can like you suggested in the first paragraph, this will not change anytime soon. and no thanks, i wont be doing repoman checks on the tree, i had been doing this for x86-fbsd, spending hours fixing the mess i could, and had to re-do it every couple of months because every other dev was committing packages with broken deps. now, would you please file bugs when you see such broken packages and let the keywording level be sanitized ? thanks