From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: Remove replace call from MACHINE_ARCH
Date: Thu, 30 Jul 2015 14:13:15 +0100 [thread overview]
Message-ID: <1438261995.11208.109.camel@linuxfoundation.org> (raw)
In-Reply-To: <1438166990-13918-1-git-send-email-adrian.ratiu@ni.com>
On Wed, 2015-07-29 at 13:49 +0300, Ioan-Adrian Ratiu wrote:
> This replace() hack was added to fix Yocto bug #946 [1] with commit id
> 69b3a11. It is time to fix this properly.
I'd love to see this fixed properly. I assume you're volunteering to do
this?
> It should not be an issue
> anymore with libzypp after 4.5 years, but if the initial bug still
> exists, then a more intelligent solution should be used to fix it.
We no longer use libzypp. I believe however that this is a more deeply
rooted rpm issue.
So, what testing did you do of the rpm backend after this change?
Note that we also have to do mappings of TARGET_ARCH ->
TRANSLATED_TARGET_ARCH which is the same issue as this one.
Cheers,
Richard
prev parent reply other threads:[~2015-07-30 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 10:49 [PATCH] bitbake.conf: Remove replace call from MACHINE_ARCH Ioan-Adrian Ratiu
2015-07-30 13:13 ` Richard Purdie [this message]
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=1438261995.11208.109.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adrian.ratiu@ni.com \
--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