From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mail.openembedded.org (Postfix) with ESMTP id 64D7D6E660 for ; Mon, 8 Feb 2016 15:22:52 +0000 (UTC) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP; 08 Feb 2016 07:22:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,416,1449561600"; d="scan'208";a="907856687" Received: from jlock-mobl1.gar.corp.intel.com ([10.252.31.93]) by orsmga002.jf.intel.com with ESMTP; 08 Feb 2016 07:22:52 -0800 Message-ID: <1454944971.3396.8.camel@linux.intel.com> From: Joshua G Lock To: openembedded-core@lists.openembedded.org Date: Mon, 08 Feb 2016 15:22:51 +0000 In-Reply-To: <1454885003.27087.344.camel@linuxfoundation.org> References: <1454270130-11287-1-git-send-email-akuster808@gmail.com> <1454885003.27087.344.camel@linuxfoundation.org> X-Mailer: Evolution 3.18.4 (3.18.4-1.fc23) Mime-Version: 1.0 Subject: Re: Stable branch rules [Was: Re: [PATCH][jethro] glibc-locale: fix QA warning] X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 15:22:54 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Sun, 2016-02-07 at 22:43 +0000, Richard Purdie wrote: > On Sun, 2016-01-31 at 11:55 -0800, Armin Kuster wrote: > > From: Armin Kuster > > > > WARNING: QA Issue: glibc-locale: /glibc-binary-localedata-sd > > -in/usr/lib/locale/sd_IN/LC_CTYPE is owned by uid 1000, which is > > the > > same as the user running bitbake. This may be due to host > > contamination [host-user-contaminated] > > > > fix type > > Signed-off-by: Armin Kuster > > --- > >  meta/recipes-core/glibc/glibc-locale.inc | 2 +- > >  1 file changed, 1 insertion(+), 1 deletion(-) > > Enough is enough. > > I cannot tell whether these patches are in master or not or whether > master needs them or not. Master needs this one, its not in master, > its > only being proposed for jethro. Its a mess. > > I am therefore not taking any more stable branch patches at all until > we amend the stable branch rules to state that pull requests and > patches clearly state which branches need a fix, or clearly state why > they don't. I made an attempt at starting to documenting that requirement: https://wiki.yoctoproject.org/wiki/index.php?title=Stable_branch_mainte nance&diff=17480&oldid=17028 'Patches' welcome. Regards, Joshua