From: Martin Jansa <martin.jansa@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: appears to be inconsistency re: base-files between oe-core and meta-angstrom
Date: Thu, 29 Aug 2013 12:49:13 +0200 [thread overview]
Message-ID: <20130829104913.GM3544@jama> (raw)
In-Reply-To: <alpine.DEB.2.02.1308290628130.4283@oneiric>
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
On Thu, Aug 29, 2013 at 06:29:17AM -0400, Robert P. J. Day wrote:
>
> trying to build a "hardware-bringup-image" defined in angstrom layer
> and running into:
>
> ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/log -> /var/volatile/log
> ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/run -> /run
> ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/tmp -> /var/volatile/tmp
>
> this would *appear* to be because oe-core defines, in
> base-files_3.0.14.bb:
>
> volatiles = "log tmp"
> ... snip ...
> for d in ${volatiles}; do
> ln -sf volatile/$d ${D}${localstatedir}/$d
> done
> ln -snf ../run ${D}${localstatedir}/run
> ln -snf ../run/lock ${D}${localstatedir}/lock
>
> which seems to want to create /var/{run,log,tmp} as symlinks, but over
> in meta-angstrom, we have base-files_3.0.14.bbappend which seems to
> want to create them as actual directories instead:
Expectations from base-files .bbappend and FILESYSTEM_PERMS_TABLES need
to be consistent, is it possible that you're using .bbappend from
angstrom and not FILESYSTEM_PERMS_TABLES set by angstrom config?
conf/distro/include/angstrom-core-tweaks.inc:FILESYSTEM_PERMS_TABLES = "fs-perms-angstrom.txt"
>
> dirs755 += "${localstatedir}/cache \
> ${localstatedir}/run \
> ${localstatedir}/log \
> ${localstatedir}/lock \
> ${localstatedir}/lock/subsys \
> ${localstatedir}/tmp \
> ${localstatedir}/volatile/tmp \
> /run \
> "
>
> or am i misreading something?
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-08-29 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 10:29 appears to be inconsistency re: base-files between oe-core and meta-angstrom Robert P. J. Day
2013-08-29 10:49 ` Martin Jansa [this message]
2013-08-29 11:00 ` Robert P. J. Day
2013-08-29 11:27 ` Martin Jansa
2013-08-29 11:37 ` Robert P. J. Day
2013-08-29 11:49 ` Phil Blundell
2013-08-29 11:56 ` Robert P. J. Day
2013-08-29 11:57 ` Richard Purdie
2013-08-29 16:14 ` Chris Larson
2013-08-30 12:21 ` Robert P. J. Day
2013-08-29 11:49 ` Martin Jansa
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=20130829104913.GM3544@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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