From: Gary Thomas <gary@mlbassoc.com>
To: Bob Cochran <yocto@mindchasers.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-ppc] recent breakage
Date: Thu, 15 Jan 2015 12:51:41 -0700 [thread overview]
Message-ID: <54B81A4D.5000102@mlbassoc.com> (raw)
In-Reply-To: <54B81740.5080401@mindchasers.com>
On 2015-01-15 12:38, Bob Cochran wrote:
> On 01/15/2015 12:46 PM, Gary Thomas wrote:
>> This commit breaks a build when an image contains udev-extraconf
>>
>> commit d7df92b6f5c1a673341d54d6b064ad2fd7b16d74
>> Author: Ting Liu <ting.liu@freescale.com>
>> Date: Wed Jan 7 17:54:59 2015 +0800
>>
>> udev-extraconf: replace bbappend with own recipe
>>
>> * introduce variable RULE for DPAA FMan ethernet ports name rule.
>> * use 72-fsl-dpaa-persistent-networking.rules for t1024, same as
>> e6500.
>>
>> Signed-off-by: Ting Liu <ting.liu@freescale.com>
>>
>> Since this change, I get this error when building:
>> * check_data_file_clashes: Package udev-rules-qoriq wants to install
>> file
>> /local/diskstation-cutting-edge_2015-01-08/tmp/work/p1022ds-amltd-linux-gnuspe/amanda-server-image/1.0-r0/rootfs/etc/udev/mount.blacklist
>>
>> But that file is already provided by package * udev-extraconf
>
>
> I'm wondering where the root cause is located. The recipe isn't installing the blacklist file. It's just appending to it (if it already exists), so why is there a clash? Does
> the recipe need modification or is the problem in the framework?
One recipe doesn't get to modify the results of a different recipe
so the do_install() step is really creating a second copy of the
blacklist file (which if you don't have udev-extraconf installed
isn't used anyway)
>
> As an aside, should the udev-rules-qoriq recipe see if the blacklists already exist before issuing the append (echo) statements?
>
> Lastly, I think I like having the separate recipe rather than the udev-extraconf append since I can easily just leave it out of my image, which I'm currently doing.
Well I would like to have udev-extraconf in my image (that's
what choices are all about) and this version of udev-rules-qoriq
is making that impossible :-(
>
>>
>> I don't see why this was changed from using .bbappend for
>> the udev-extraconf - it seems wrong headed to me.
>>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-01-15 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:46 [meta-fsl-ppc] recent breakage Gary Thomas
2015-01-15 19:38 ` Bob Cochran
2015-01-15 19:51 ` Gary Thomas [this message]
2015-01-16 1:47 ` ting.liu
2015-08-06 12:13 ` Abdur Rehman
2015-08-10 12:33 ` Ahsan, Noor
2015-08-12 7:45 ` Liu Ting
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=54B81A4D.5000102@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=yocto@mindchasers.com \
/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.