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 5BAF4138247 for ; Sun, 3 Nov 2013 16:54:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E301CE0A9F; Sun, 3 Nov 2013 16:53:53 +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 08D9CE0A4A for ; Sun, 3 Nov 2013 16:53:52 +0000 (UTC) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 02C4733EFE6 for ; Sun, 3 Nov 2013 16:53:51 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id q58so1264089wes.14 for ; Sun, 03 Nov 2013 08:53:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Vw9e994/38XGJCrXehR8NY/V9Ecyn9KV+yuVo4UldxA=; b=cLXyP4UY1GgATPzmzqidbf87B2SNmYc+GzuyxWhtdWilX2oHWWB8CAUl8BnjoayQG6 GMWHEMi6JPlFRilflhhyb+Z3HnWlyGmWDcHqAdmFsFf4JStv+1k+HgtOXtf385rt1q9Y fflkrdVkNuXdaA2p2dO6zypDDdVvrFKrwH4hZYsMylWmt3cDZTVsBTULLdXhsAI3Hy8o W7YjoDAv+qIUcQs2B1vgyTg0pH2wkjzS5Z4TptVoThSHBwyZKz1lqpUvl6ecGskzfyS+ 8PEgsoOz9eqa3lis1V1Nc78v26ndeokNRobQ1sJtcMKPFhjH8fjn5Rpt4CJjooINZLX5 lygg== 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 X-Received: by 10.180.182.193 with SMTP id eg1mr9444322wic.49.1383497629192; Sun, 03 Nov 2013 08:53:49 -0800 (PST) Received: by 10.194.39.231 with HTTP; Sun, 3 Nov 2013 08:53:49 -0800 (PST) In-Reply-To: <5276736B.9030208@gentoo.org> References: <5274FB3D.8080508@gentoo.org> <20131102145126.3c1f6cd7@TOMWIJ-GENTOO> <20131102160330.0e6eaa5e@gentoo.org> <52755089.6090808@gentoo.org> <20131102213530.24388cda@gentoo.org> <52756723.9090300@gentoo.org> <20131102230940.233a8e4b@gentoo.org> <52758879.70200@gentoo.org> <20131103004526.64f6e789@gentoo.org> <52761127.1060106@gmail.com> <5276736B.9030208@gentoo.org> Date: Sun, 3 Nov 2013 11:53:49 -0500 Message-ID: Subject: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec From: Mike Gilbert To: Gentoo Dev Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 0ca299fb-5634-4be6-8653-c76175203a93 X-Archives-Hash: 008fc938bbe94225bc14e62b9d7e6b35 On Sun, Nov 3, 2013 at 11:01 AM, Anthony G. Basile wrote: > Getting back to my original post: I want to make the python team aware of > the needs of releng and exercise care in the future when making a commit > where "alarm bells" go off. An email to releng@ or gentoo-dev@ asking "will > this mess up your stuff" would have been sufficient as we then could have > tested. I don't know if any deeper lesson can be learned. I don't expect > anyone to have super cow powers and forsee every eventuality. Don't be > afraid to use the community. > I think we were rushing to come up with a solution for a problem that really only affected ~arch, and in the process we caused some problems for a few stable or mixed-arch users. It was rushed because we started getting bugs and IRC pings with words like "QA violation" about the original /var/db/pkg sed hack we had employed. I think a little patience by all parties would have helped. As you say, if we had taken the time to ping some people to test it, the situation may have been avoided.