From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] Add recipes for 0.9.32 release
Date: Wed, 06 Jul 2011 19:10:44 +0100 [thread overview]
Message-ID: <1309975844.20015.798.camel@rex> (raw)
In-Reply-To: <CAMKF1spy7d0yJu=EnbG-sKwxxgwB1Jz8S0k6D3Fr+KCUpRerjw@mail.gmail.com>
On Wed, 2011-07-06 at 11:06 -0700, Khem Raj wrote:
> On Wed, Jul 6, 2011 at 1:06 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Tue, 2011-07-05 at 23:48 -0700, Khem Raj wrote:
> >> On Tue, Jul 5, 2011 at 2:09 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >> > With this changeset we add new recipes for 0.9.32 and make that default
> >> > preference. Then the git recipe are moved to track the latest master.
> >> > systemd related fixes are separately applied to both git recipe and 0.9.32
> >> > recipes
> >> >
> >> > Both sets work for arm,mips,ppc,x86,x86-64
> >> >
> >> > Thanks
> >> > -Khem
> >> >
> >> >
> >> > The following changes since commit 4eb3abaa5f4b5df0314dc0d503298d65cd203259:
> >> >
> >> > uclibc-0.9.32: Implement execvpe and refresh scheduler functions (2011-07-05 13:53:05 -0700)
> >> >
> >> > are available in the git repository at:
> >> > git://git.openembedded.org/openembedded-core-contrib kraj/uclibc-0.9.32
> >> > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/uclibc-0.9.32
> >> >
> >> > Khem Raj (5):
> >> > uclibc: Add recipes for 0.9.32 release
> >> > tcmode-default: Define UCLIBCVERSION and set it to 0.9.32
> >> > uclibc_git: Move SRCREV past 0.9.32 release
> >>
> >> I have update PV in above commit to 0.9.32+0.9.33-rc0 instead of
> >> 0.9.32+gitr${SRCPV} which is troublesome to use with git
> >
> > Can you expand a little more about what was troublesome with it?
> >
> > Is there a revision being specified for the uclibc git recipe?
>
> since its master git I have to change SRCREV frquently and if I do not bump
> PR it ends up with dependency problems while generating image since
> the SHAs are random
> and they are getting into PV sometimes opkg thinks the version is
> smaller than the previous
> one and opkg does not like it. that aside 0.9.32+0.9.33-rc0 explains
> the recipes PV better IMO
Could you at least add the SRCREV you're using the recipe please? I
didn't look really hard but I couldn't seem to find it when I last
looked...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-06 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 21:09 [PATCH 0/5] Add recipes for 0.9.32 release Khem Raj
2011-07-05 21:09 ` [PATCH 1/5] uclibc: " Khem Raj
2011-07-05 21:09 ` [PATCH 2/5] tcmode-default: Define UCLIBCVERSION and set it to 0.9.32 Khem Raj
2011-07-05 21:09 ` [PATCH 3/5] uclibc_git: Move SRCREV past 0.9.32 release Khem Raj
2011-07-05 21:09 ` [PATCH 4/5] uclibc_git: Implement execvpe and refresh scheduler functions Khem Raj
2011-07-05 21:09 ` [PATCH 5/5] uclibc-0.9.32: " Khem Raj
2011-07-06 6:48 ` [PATCH 0/5] Add recipes for 0.9.32 release Khem Raj
2011-07-06 8:06 ` Richard Purdie
2011-07-06 18:06 ` Khem Raj
2011-07-06 18:10 ` Richard Purdie [this message]
2011-07-06 18:34 ` Khem Raj
2011-07-07 9:52 ` Richard Purdie
2011-07-07 9:52 ` Richard Purdie
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=1309975844.20015.798.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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