From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] lib/oe/package_manager: update default rpm config %_prefer_color
Date: Sun, 03 May 2020 09:21:20 +0100 [thread overview]
Message-ID: <24fa564f2ed31f3285051048de648f6cb6bf75e0.camel@linuxfoundation.org> (raw)
In-Reply-To: <1588219837-337689-1-git-send-email-changqing.li@windriver.com>
On Thu, 2020-04-30 at 12:10 +0800, Changqing Li wrote:
> From: Changqing Li <changqing.li@windriver.com>
>
> * %_prefer_color is used by rpm to determine which color's ELF file
> is preferred to be installed.
>
> Here are file colors:
> 0 is unknown or other
> 1 is Elf32
> 2 is Elf64
> 3 is (contains) both
>
> if default value set to 7, both 32 and 64 bits's ELF will be
> installed,
> in this condition, when we have 64bits python3 installed first,
> then install lib32-python3 later, 64bits python3 will be overwrited,
>
> file /usr/bin/python3 will be 32bits ELF
> and sys.path will point to /usr/lib, not /usr/lib64, this may cause
> some python3 modules not work. so fixed by remove setting of default
> value 7, and use default value 2 of rpm.
>
> * other distro like fedora also use the default %_prefer_color 2
>
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
> meta/lib/oe/package_manager.py | 2 --
> 1 file changed, 2 deletions(-)
This causes a failure on the autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/1867
Cheers,
Richard
next prev parent reply other threads:[~2020-05-03 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 4:10 [PATCH] lib/oe/package_manager: update default rpm config %_prefer_color Changqing Li
2020-05-03 8:21 ` Richard Purdie [this message]
[not found] <160A7D8AF7F6BE8C.17748@lists.openembedded.org>
2020-05-06 2:39 ` [OE-core] " Changqing Li
2020-05-06 8:09 ` Alexander Kanavin
2020-05-06 8:21 ` Changqing Li
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=24fa564f2ed31f3285051048de648f6cb6bf75e0.camel@linuxfoundation.org \
--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