From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: cnf/
Date: Sun, 2 Nov 2014 03:02:35 +0000 (UTC) [thread overview]
Message-ID: <1414896823.2fcdb5f36face97b4a8ce74831d287bd1dd9c2bf.zmedico@gentoo> (raw)
commit: 2fcdb5f36face97b4a8ce74831d287bd1dd9c2bf
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 1 20:55:34 2014 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sun Nov 2 02:53:43 2014 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=2fcdb5f3
Add btrfs.* to default PORTAGE_XATTR_EXCLUDE (527636)
In bug #527636 a user reported that install-xattr failed to copy
btrfs.compression attributes when doins was installing a file from
$FILESDIR. It is unlinkly that a package will have a valid use for
btrfs.* attributes when installing files to $D. Therefore, exclude
btrfs.* attributes in order to avoid reports like this in the
future.
X-Gentoo-Bug: 527636
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=527636
Acked-by: Brian Dolbec <dolsen <AT> gentoo.org>
---
cnf/make.globals | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/cnf/make.globals b/cnf/make.globals
index 013c556..dd99618 100644
--- a/cnf/make.globals
+++ b/cnf/make.globals
@@ -122,9 +122,10 @@ PORTAGE_ELOG_MAILFROM="portage@localhost"
# Signing command used by repoman
PORTAGE_GPG_SIGNING_COMMAND="gpg --sign --digest-algo SHA256 --clearsign --yes --default-key \"\${PORTAGE_GPG_KEY}\" --homedir \"\${PORTAGE_GPG_DIR}\" \"\${FILE}\""
+# btrfs.* attributes are irrelevant, see bug #527636.
# Security labels are special, see bug #461868.
# system.nfs4_acl attributes are irrelevant, see bug #475496.
-PORTAGE_XATTR_EXCLUDE="security.* system.nfs4_acl"
+PORTAGE_XATTR_EXCLUDE="btrfs.* security.* system.nfs4_acl"
# *****************************
# ** DO NOT EDIT THIS FILE **
next reply other threads:[~2014-11-02 3:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 3:02 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-10 22:59 [gentoo-commits] proj/portage:master commit in: cnf/ Sam James
2023-10-13 10:19 Sam James
2023-08-03 21:15 Sam James
2023-08-03 21:15 Sam James
2022-04-11 20:17 Mike Gilbert
2022-02-06 19:19 Zac Medico
2021-11-16 21:17 Zac Medico
2020-05-03 20:32 Zac Medico
2019-10-21 18:07 Michał Górny
2019-09-26 0:03 Zac Medico
2019-07-05 5:39 Michał Górny
2019-04-19 5:16 Zac Medico
2018-12-12 18:41 Michał Górny
2018-08-12 10:05 Zac Medico
2018-07-11 18:01 Zac Medico
2018-05-11 7:48 Michał Górny
2017-12-11 2:27 Zac Medico
2017-08-02 8:06 Michał Górny
2017-01-06 22:13 Brian Dolbec
2017-01-06 18:00 Brian Dolbec
2017-01-06 18:00 Brian Dolbec
2015-12-15 8:40 Brian Dolbec
2015-03-10 17:53 Zac Medico
2013-07-25 22:00 Zac Medico
2013-05-10 4:09 Zac Medico
2013-01-21 16:52 Zac Medico
2013-01-21 16:48 Zac Medico
2012-11-05 8:52 Zac Medico
2012-09-06 20:06 Zac Medico
2012-08-17 21:36 Zac Medico
2012-08-05 8:13 Zac Medico
2012-07-23 17:45 Zac Medico
2012-07-09 21:03 Zac Medico
2012-07-06 6:43 Zac Medico
2012-05-05 16:41 Zac Medico
2011-12-22 4:30 Zac Medico
2011-12-22 4:22 Zac Medico
2011-12-21 21:45 Zac Medico
2011-11-11 21:23 Zac Medico
2011-08-26 3:52 Zac Medico
2011-06-03 5:24 Zac Medico
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=1414896823.2fcdb5f36face97b4a8ce74831d287bd1dd9c2bf.zmedico@gentoo \
--to=zmedico@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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