From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 00/10] Fix multilib install conflicts
Date: Sat, 29 Sep 2018 13:01:14 +0800 [thread overview]
Message-ID: <cover.1538197206.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit 3bbbe25ae74e120f7d3452685f0cae2245d7b14d:
glibc-package.inc: correct intention for deleting /usr/lib as needed (2018-09-27 23:41:41 +0100)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib kangkai/ML-sep29
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/ML-sep29
Kai Kang (10):
cups: fix multilib install file conflicts
bind: fix multilib install file conflicts
man-db: fix multilib install file conflict
groff: fix multilib install file conflicts
nss: move create blank certificates to pkg_postinst
libcheck: avoid multilib install file conflict
opkg-utils/update-alternatives: not warn same priorities for multilib
os-release: fix install file conflict for multilib
gobject-introspection: fix multilib install file conflicts
vala: update vapigen-wrapper
meta/recipes-connectivity/bind/bind_9.11.4.bb | 4 +-
meta/recipes-core/os-release/os-release.bb | 6 +-
...ot-warn-same-priorities-for-multilib.patch | 30 +++++++++
.../opkg-utils/opkg-utils_0.3.6.bb | 1 +
meta/recipes-devtools/vala/vala.inc | 4 +-
meta/recipes-extended/cups/cups.inc | 3 +
meta/recipes-extended/groff/groff_1.22.3.bb | 4 +-
meta/recipes-extended/man-db/man-db_2.8.3.bb | 3 +
...nfigure.ac-make-GIR_DIR-configurable.patch | 65 +++++++++++++++++++
.../gobject-introspection_1.58.0.bb | 10 ++-
.../libcheck/libcheck_0.12.0.bb | 5 ++
meta/recipes-support/nss/nss_3.38.bb | 32 +++++----
12 files changed, 147 insertions(+), 20 deletions(-)
create mode 100644 meta/recipes-devtools/opkg-utils/opkg-utils/update-alternatives-not-warn-same-priorities-for-multilib.patch
create mode 100644 meta/recipes-gnome/gobject-introspection/gobject-introspection/0001-configure.ac-make-GIR_DIR-configurable.patch
--
2.18.0
next reply other threads:[~2018-09-29 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 5:01 kai.kang [this message]
2018-09-29 5:01 ` [PATCH 01/10] cups: fix multilib install file conflicts kai.kang
2018-09-29 5:01 ` [PATCH 02/10] bind: " kai.kang
2018-09-29 5:01 ` [PATCH 03/10] man-db: fix multilib install file conflict kai.kang
2018-09-29 5:01 ` [PATCH 04/10] groff: fix multilib install file conflicts kai.kang
2018-09-29 5:01 ` [PATCH 05/10] nss: move create blank certificates to pkg_postinst kai.kang
2018-09-29 5:01 ` [PATCH 06/10] libcheck: avoid multilib install file conflict kai.kang
2018-09-29 5:01 ` [PATCH 07/10] opkg-utils/update-alternatives: not warn same priorities for multilib kai.kang
2018-09-29 5:01 ` [PATCH 08/10] os-release: fix install file conflict " kai.kang
2018-09-29 5:01 ` [PATCH 09/10] gobject-introspection: fix multilib install file conflicts kai.kang
2018-09-29 5:01 ` [PATCH 10/10] vala: update vapigen-wrapper kai.kang
2018-09-29 6:03 ` ✗ patchtest: failure for Fix multilib install conflicts Patchwork
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=cover.1538197206.git.kai.kang@windriver.com \
--to=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