From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11191] New: xattr and check-package issue
Date: Wed, 25 Jul 2018 15:24:32 +0000 [thread overview]
Message-ID: <bug-11191-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11191
Bug ID: 11191
Summary: xattr and check-package issue
Product: buildroot
Version: 2018.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
check-package warns about missing indent with xattr line in permissions of
packages, however adding indentation to those lines makes the check-package
script happy but then corresponding xattr entries are then silently ignored
when creating the image.
e.g., this entry will make check-package issue a warning :
...
define TEST_PERMISSIONS
/usr/bin/test f 0755 user0 users - - - - -
|xattr cap_kill+eip
|xattr cap_sys_nice+eip
|xattr cap_sys_time+eip
...
package/test/test.mk:618: expected indent with tabs
However changing it to
define TEST_PERMISSIONS
/usr/bin/test f 0755 user0 users - - - - -
\t|xattr cap_kill+eip
\t|xattr cap_sys_nice+eip
\t|xattr cap_sys_time+eip
...
Will make check-package happy but xattr attributes will not be taken into
account without any error message.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-07-25 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 15:24 bugzilla at busybox.net [this message]
2018-07-25 16:12 ` [Buildroot] [Bug 11191] xattr and check-package issue bugzilla at busybox.net
2018-07-26 0:42 ` bugzilla at busybox.net
2018-07-26 8:17 ` [Buildroot] Handling leading tabs in makedevs [was: [Bug 11191] xattr and check-package issue] Arnout Vandecappelle
2018-08-06 3:12 ` Ricardo Martincoski
2018-08-14 21:20 ` [Buildroot] [Bug 11191] xattr and check-package issue bugzilla at busybox.net
2018-08-16 3:01 ` bugzilla at busybox.net
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=bug-11191-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.