From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Anders Darander <anders@chargestorm.se>
Subject: Re: [meta-qt5][PATCH] qtbase: fix QA warning of host uid leakage
Date: Thu, 15 Oct 2015 21:48:58 +0200 [thread overview]
Message-ID: <20151015194858.GF2588@jama> (raw)
In-Reply-To: <1444933287-26444-1-git-send-email-anders@chargestorm.se>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Thu, Oct 15, 2015 at 08:21:27PM +0200, Anders Darander wrote:
> Two files in /usr/lib, were own by the uid of the build process.
>
> Signed-off-by: Anders Darander <anders@chargestorm.se>
> ---
> recipes-qt/qt5/qtbase_git.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-qt/qt5/qtbase_git.bb b/recipes-qt/qt5/qtbase_git.bb
> index 39d02a9..99ac208 100644
> --- a/recipes-qt/qt5/qtbase_git.bb
> +++ b/recipes-qt/qt5/qtbase_git.bb
> @@ -232,6 +232,8 @@ do_install_append() {
> chown -R root:root ${D}/${OE_QMAKE_PATH_QT_FONTS}
> fi
> cp -a ${B}/lib/libqt* ${D}${libdir}
Can we use install instead of cp to resolve this issue instead of chmod?
> + chown root:root ${D}${libdir}/libqtpcre.prl
> + chown root:root ${D}${libdir}/libqtpcre.a
> # Remove example.pro file as it is useless
> rm -f ${D}${OE_QMAKE_PATH_EXAMPLES}/examples.pro
>
> --
> 2.6.1
>
> --
> _______________________________________________
> 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-10-15 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 18:21 [meta-qt5][PATCH] qtbase: fix QA warning of host uid leakage Anders Darander
2015-10-15 19:48 ` Martin Jansa [this message]
2015-10-19 6:06 ` Anders Darander
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=20151015194858.GF2588@jama \
--to=martin.jansa@gmail.com \
--cc=anders@chargestorm.se \
--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