From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 0F7A076740 for ; Sun, 9 Aug 2015 22:16:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t79MGUJd004389 for ; Sun, 9 Aug 2015 23:16:30 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DRUpyMaLwo7Q for ; Sun, 9 Aug 2015 23:16:30 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t79MGDjZ004370 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 9 Aug 2015 23:16:28 +0100 Message-ID: <1439158573.30467.142.camel@linuxfoundation.org> From: Richard Purdie To: openembedded-core Date: Sun, 09 Aug 2015 15:16:13 -0700 In-Reply-To: <1439158208.30467.140.camel@linuxfoundation.org> References: <1439158208.30467.140.camel@linuxfoundation.org> X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Subject: Re: [PATCH] libpam: Fix patch broken during upgrade 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: Sun, 09 Aug 2015 22:16:34 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Sun, 2015-08-09 at 15:10 -0700, Richard Purdie wrote: > "0x200" became "0200" during the upgrade to libpam 1.2.1 in: > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=88dd997d9941b63ae9eead6690ecf2b785c0740c > and this broke the IMAGE_FEATURES like debug-tweaks. > > I've converted all the values to octal here to match the original > header file convention and make it clearer. > > [YOCTO #8033] > > Signed-off-by: Richard Purdie I'm going to expidite merging this, since if I do, we can roll an M2-rc2 build today which QA can pick up tomorrow. This bug is blocking a lot of testing in M2 and the rebuild is dependent on it. I can then likely get master-next merged and unblock patch merging a bit. Cheers, Richard