From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/8] lldpad: fix installed-vs-shipped
Date: Fri, 11 Dec 2015 14:54:54 +0100 [thread overview]
Message-ID: <20151211135454.GA2248@jama> (raw)
In-Reply-To: <d7b393011e851acffece951cf1ad7c332c19f8c4.1448011904.git.liezhi.yang@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
On Fri, Nov 20, 2015 at 01:32:41AM -0800, Robert Yang wrote:
> Issue: LIN8-1622
>
> Fixed when multilib:
> lldpad-0.9.46: lldpad: Files/directories were installed but not shipped in any package:
> /usr/lib
> Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
> lldpad: 1 installed and not shipped files. [installed-vs-shipped]
>
> This is because /usr/lib/systemd has been moved, but /usr/lib was left
> in multilib, use "rmdir -p" to fix the problem.
>
> (LOCAL REV: NOT UPSTREAM) -- Sent to oe-devel on 20151120
doesn't apply because it was removed a while back:
commit 1a57f561caea01e6a19313af019138c783e9f964
Author: Joe MacDonald <joe_macdonald@mentor.com>
Date: Thu Oct 22 09:46:48 2015 -0400
lldpad: remove obsolete recipe
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> .../recipes-daemons/lldpad/lldpad_0.9.46.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-networking/recipes-daemons/lldpad/lldpad_0.9.46.bb b/meta-networking/recipes-daemons/lldpad/lldpad_0.9.46.bb
> index b191df5..b66344f 100644
> --- a/meta-networking/recipes-daemons/lldpad/lldpad_0.9.46.bb
> +++ b/meta-networking/recipes-daemons/lldpad/lldpad_0.9.46.bb
> @@ -23,7 +23,7 @@ do_configure_prepend() {
> do_install_append () {
> install -m 0755 -d ${D}${systemd_unitdir}
> mv ${D}${prefix}${systemd_unitdir}/* ${D}${systemd_unitdir}/
> - rmdir ${D}${prefix}${systemd_unitdir}
> + rmdir -p --ignore-fail-on-non-empty ${D}${prefix}${systemd_unitdir}
> }
>
> FILES_${PN} += "${systemd_unitdir}"
> --
> 1.7.9.5
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-12-11 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 9:32 [PATCH 0/8] meta-openembedded: fix QA issues Robert Yang
2015-11-20 9:32 ` [PATCH 1/8] netmap-modules: fix for --no-drivers Robert Yang
2015-11-20 9:41 ` Martin Jansa
2015-11-22 6:55 ` Robert Yang
2015-11-20 9:32 ` [PATCH 2/8] lldpad: fix installed-vs-shipped Robert Yang
2015-12-11 13:54 ` Martin Jansa [this message]
2015-11-20 9:32 ` [PATCH 3/8] nbd: use BPN in Files Robert Yang
2015-11-20 9:32 ` [PATCH 4/8] dracut: fix host-user-contaminated Robert Yang
2015-11-20 9:32 ` [PATCH 5/8] cim-schema-exper: " Robert Yang
2015-11-20 9:42 ` Martin Jansa
2015-11-22 6:55 ` Robert Yang
2015-11-20 9:32 ` [PATCH 6/8] ctdb: RDEPENDS on bash Robert Yang
2015-11-20 9:32 ` [PATCH 7/8] ctdb: add PACKAGECONFIG for libtdb Robert Yang
2015-11-20 9:32 ` [PATCH 8/8] netkit-ftp: fixed invalid symlink Robert Yang
2015-11-20 9:35 ` [PATCH 0/8] meta-openembedded: fix QA issues Robert Yang
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=20151211135454.GA2248@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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