All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Daniel Dragomir <daniel.dragomir@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libgcc-common: Fix file ownership for installed files
Date: Tue, 20 Jan 2015 15:55:51 +0000	[thread overview]
Message-ID: <CAJTo0LY9L3vzJ+5EJsov04Dh1D9wCfVj7HHOQ-HcmA79mzG8+w@mail.gmail.com> (raw)
In-Reply-To: <1421677653-1166-1-git-send-email-daniel.dragomir@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On 19 January 2015 at 14:27, Daniel Dragomir <daniel.dragomir@windriver.com>
wrote:

> Fix two QA warnings caused by setting the wrong user and group for
> files installed in the destination directory on do_install task.
>
> WARNING: log_check: There is a warn message in the logfile
> WARNING: log_check: Matched keyword: [warn]
> WARNING: log_check: warning: user xxxx does not exist - using root
>
> WARNING: log_check: There is a warn message in the logfile
> WARNING: log_check: Matched keyword: [warn]
> WARNING: log_check: warning: group xxxx does not exist - using root
>

This worries me.  Why is libgcc installing files with the wrong owners, and
is libgcc special or are other packages also installing files with the
wrong owners?  If this is a libgcc-specific problem and files are installed
with the wrong owners then fixing the install process seems like a better
fix.

Ross

[-- Attachment #2: Type: text/html, Size: 1340 bytes --]

  reply	other threads:[~2015-01-20 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 14:27 [PATCH] libgcc-common: Fix file ownership for installed files Daniel Dragomir
2015-01-20 15:55 ` Burton, Ross [this message]
2015-01-22 13:32   ` Dragomir, Daniel

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=CAJTo0LY9L3vzJ+5EJsov04Dh1D9wCfVj7HHOQ-HcmA79mzG8+w@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=daniel.dragomir@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.