From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai.kang@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 07/10] opkg-utils/update-alternatives: not warn same priorities for multilib
Date: Sat, 29 Sep 2018 13:40:50 +0100 [thread overview]
Message-ID: <51d281559eb5f84b6df309e100eccf2034fd3c5a.camel@linuxfoundation.org> (raw)
In-Reply-To: <a4a18433e51ef85e3beae67625eb477d078e5639.1538199671.git.kai.kang@windriver.com>
On Sat, 2018-09-29 at 13:43 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> update-alternatives is used to handle install file conflicts of
> multilib
> packages in multilib_script.bbclass. And the default priority is used
> for the alternatives which causes QA warning:
>
> > WARNING: core-image-minimal-1.0-r0 do_rootfs: [log_check] core-
> > image-minimal: found 1 warning message in the logfile
> > [log_check] Warn: update-alternatives: libtool has multiple
> > providers with the same priority, please check
> > .../core-image-minimal/1.0-
> > r0/rootfs/usr/lib/opkg/alternatives/libtool for details
>
> The same priorities of alternatives are by design, so eliminate the
> warning for alternatives from multilib packages.
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
Sorry, no, this isn't right either :(
If we read the patch where multilib_scripts were introduced:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=e3497cc22b969e02efa54e4e54e087dbb91d8ced
it says "standardisation amongst the multilibs on how the alternatives
are named and prioritiesd. The priotitisation code needs to be added
but this change means there is somewhere to add it."
so the intent was to allow the user to define which multilib should be
the higher priority and add in some prioritisation code.
The correct way to fix these warning is to add such code, allowing the
user to specify the order of priorities of the multilibs.
Cheers,
Richard
next prev parent reply other threads:[~2018-09-29 12:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 5:43 [PATCH v2 00/10] Fix multilib install conflicts kai.kang
2018-09-29 5:43 ` [PATCH 01/10] cups: fix multilib install file conflicts kai.kang
2018-09-29 5:43 ` [PATCH 02/10] bind: " kai.kang
2018-09-29 5:43 ` [PATCH 03/10] man-db: fix multilib install file conflict kai.kang
2018-09-29 12:44 ` Richard Purdie
2018-09-30 1:02 ` Kang Kai
2018-09-29 5:43 ` [PATCH 04/10] groff: fix multilib install file conflicts kai.kang
2018-09-29 5:43 ` [PATCH 05/10] nss: move create blank certificates to pkg_postinst kai.kang
2018-09-29 12:44 ` Richard Purdie
2018-10-02 15:29 ` Kang Kai
2018-10-02 15:53 ` richard.purdie
2018-10-02 16:33 ` Kang Kai
2018-10-11 7:55 ` Kang Kai
2018-09-29 5:43 ` [PATCH 06/10] libcheck: avoid multilib install file conflict kai.kang
2018-09-29 12:42 ` Richard Purdie
2018-09-30 1:03 ` Kang Kai
2018-09-29 5:43 ` [PATCH 07/10] opkg-utils/update-alternatives: not warn same priorities for multilib kai.kang
2018-09-29 12:40 ` Richard Purdie [this message]
2018-09-29 5:43 ` [PATCH 08/10] os-release: fix install file conflict " kai.kang
2018-09-29 12:37 ` Richard Purdie
2018-09-30 1:07 ` Kang Kai
2018-09-29 5:43 ` [PATCH 09/10] gobject-introspection: fix multilib install file conflicts kai.kang
2018-09-29 5:43 ` [PATCH 10/10] vala: update vapigen-wrapper kai.kang
2018-09-29 12:33 ` Richard Purdie
2018-09-30 1:26 ` Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2018-09-29 5:01 [PATCH 00/10] Fix multilib install conflicts kai.kang
2018-09-29 5:01 ` [PATCH 07/10] opkg-utils/update-alternatives: not warn same priorities for multilib kai.kang
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=51d281559eb5f84b6df309e100eccf2034fd3c5a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.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