From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/3] Fix zypper integration
Date: Thu, 31 Mar 2011 15:35:47 +0100 [thread overview]
Message-ID: <1301582147.24596.109.camel@rex> (raw)
In-Reply-To: <cover.1301516765.git.mark.hatle@windriver.com>
On Wed, 2011-03-30 at 15:29 -0500, Mark Hatle wrote:
> Fix the zypper integration on Bernard (Poky). This is also be necessary
> in master/OE-core as well! (I have not verified that the C++ workaround
> is needed on OE-Core, but the same change for MIPS -is- needed due to
> namespace collision.)
>
> Fixes [YOCTO #827] Zypper not working on ARM. (Note, one of the issues
> resolved actually affects all host types..)
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: mhatle/bernard/zypper
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/bernard/zypper
>
> Thanks,
> Mark Hatle <mark.hatle@windriver.com>
> ---
>
>
> Mark Hatle (3):
> Fix sat-solver & RPM5 integration issue
> Fix integration of zypper and sat-solver
> Workaround for Global C++ Constructor problem on ARM
Merged to master, thanks.
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [OE-core] [PATCH 0/3] Fix zypper integration
Date: Thu, 31 Mar 2011 15:35:47 +0100 [thread overview]
Message-ID: <1301582147.24596.109.camel@rex> (raw)
In-Reply-To: <cover.1301516765.git.mark.hatle@windriver.com>
On Wed, 2011-03-30 at 15:29 -0500, Mark Hatle wrote:
> Fix the zypper integration on Bernard (Poky). This is also be necessary
> in master/OE-core as well! (I have not verified that the C++ workaround
> is needed on OE-Core, but the same change for MIPS -is- needed due to
> namespace collision.)
>
> Fixes [YOCTO #827] Zypper not working on ARM. (Note, one of the issues
> resolved actually affects all host types..)
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: mhatle/bernard/zypper
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/bernard/zypper
>
> Thanks,
> Mark Hatle <mark.hatle@windriver.com>
> ---
>
>
> Mark Hatle (3):
> Fix sat-solver & RPM5 integration issue
> Fix integration of zypper and sat-solver
> Workaround for Global C++ Constructor problem on ARM
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2011-03-31 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 20:29 [PATCH 0/3] Fix zypper integration Mark Hatle
2011-03-30 20:29 ` [PATCH 1/3] Fix sat-solver & RPM5 integration issue Mark Hatle
2011-03-30 20:29 ` [PATCH 2/3] Fix integration of zypper and sat-solver Mark Hatle
2011-03-30 20:29 ` [PATCH 3/3] Workaround for Global C++ Constructor problem on ARM Mark Hatle
2011-03-31 14:35 ` Richard Purdie [this message]
2011-03-31 14:35 ` [OE-core] [PATCH 0/3] Fix zypper integration 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=1301582147.24596.109.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.