From: Scott Garman <scott.a.garman@intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] gzip: upgrade to 1.5
Date: Mon, 25 Jun 2012 08:36:40 -0700 [thread overview]
Message-ID: <4FE88588.2040703@intel.com> (raw)
In-Reply-To: <4FE54C99.4040602@linux.intel.com>
On 06/22/2012 09:56 PM, Saul Wold wrote:
> On 06/22/2012 10:25 AM, Scott Garman wrote:
>> LIC_FILES_CHKSUM updated due to trivial copyright date change.
>>
>> Use new update-alternatives syntax.
>>
>
> I think you also need an update to PREFERRED_VERSION for gzip-native in
> tcmode-default.inc, not sure why I missed this earlier.
Ah, I missed that. I've pushed an additional commit to my pull request
branch to address this:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/recipe-upgrades-oe&id=c42d223d572eb25f3296452a64461985df20ddcf
The reason I missed it was for "trivial" recipe upgrades like this I was
bitbake'ing the individual recipes themselves for each architecture, not
full images. I'll try to include at least one image when doing build
tests in the future, although something like sato is what ends up making
these build tests take forever.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-06-25 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 17:25 [PATCH 0/2] Recipe upgrades - gzip and sudo Scott Garman
2012-06-22 17:25 ` [PATCH 1/2] gzip: upgrade to 1.5 Scott Garman
2012-06-23 4:56 ` Saul Wold
2012-06-25 15:36 ` Scott Garman [this message]
2012-06-22 17:25 ` [PATCH 2/2] sudo: upgrade to 1.8.5p2 Scott Garman
2012-06-25 16:26 ` [PATCH 0/2] Recipe upgrades - gzip and sudo Saul Wold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE88588.2040703@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox